Check points for Factset issues

Created by Shivani Zinjurke, Modified on Mon, 28 Jul at 3:08 PM by Shivani Zinjurke

Description

Factset data is usually updated in the BM editor automatically once we open the peer. We primarily have 8 Factset elements that are used in the application:

1) EBIT

2) EBITDA

3) EPS

4) EPS_GAAP

5) EPS_NONGAAP

6) FCF

7) SALES

Excel Data Upload: FactSet data fetched by Virtua is saved and uploaded to the following OneDrive location: Here's the link OneDrive - Virtua Exchange

The mapping is done from the ‘Element mapping’ (BM editor > Edit > Element Mapping).

Steps to reproduce the issue

1. Open BM editor and click on Edit.

2. Click on blue ‘Factset’ icon.

3. Map the Factset elements with the line items/elements.

4. Once the changes are done. Save the template and let the peers process through offline.

Queries

We will be taking example of GFS ticker.

1. MDM tables (Zeus.CoSecurity, Zeus.CoAttribute, Zeus.Company)

SELECT distinct cs.CoID, cs.*, ca.*, c.*

FROM Zeus.CoSecurity cs

Inner JOIN Zeus.CoAttribute ca ON cs.CoID = ca.CoID

Inner JOIN Zeus.Company c ON cs.CoID = c.CoID

where cs.Ticker IN ('GFS')

and cs.IsPrimary= 1

2. DWH database

SELECT * FROM VirtuaMaster.Universe where ticker like GFS;

3. FSmapping in Snowflake:

SELECT * FROM "DWCONTROLDB"."PUBLIC"."FSCOMPANYMAPPING" WHERE ISIN='KYG393871085';

4. ACTIVECOMPANDPEERSDETAILS table in Snowflake:

Select * from DWCONTROLDB.PUBLIC.ACTIVECOMPANDPEERSDETAILS WHERE Ticker like GFS;

5. FS repopulation table

http://192.168.5.110/app/wm-automation#/fs_repopulation

Note: Insert ISIN if not present

6. Source table:

There are 6 tables. Please check the sheet https://app.snowflake.com/jua05830/ega44896/w1KRYGVVn6Kk#query .

Below is an example:

SELECT i.isin,un.UNITFACTOR,d.* FROM "FACTSET"."SYM_V1"."SYM_ISIN" i

JOIN "FACTSET"."SYM_V1"."SYM_COVERAGE" c ON i.fsym_id = c.fsym_id

JOIN "FACTSET"."FE_V4"."FE_BASIC_CONH_AF" d ON d.fsym_id = c.fsym_regional_id

JOIN "FACTSET"."REF_V2"."FE_ITEM_MAP" un ON d.fe_item = un.fe_item

WHERE i.isin in ('KYG393871085')// AND CONS_END_DATE is null

ORDER BY CONS_START_DATE DESC;

7. DWH SP:

SP is provided to check if the DWH is updated or not:

CALL SPT_GetCompEstPostReleaseDateValues_QandY(Enter_DWCompanyID);

Below queries can also be run to check the data:

Select * from DWHACTUALDATA.PUBLIC.DWESTFINALVALUES_Q order by REPORTDATE desc LIMIT 100;

8. Offset:

http://192.168.5.110/app/wm-automation#/periodoffset

Change the offset if required for the ticker as per below information:

Calculating the Offset The offset value needs to be calculated based on the rules mentioned below: -

• Quarter Period Offset (PeriodOffset)

Rule	Quarter Offset	Example
Year End Date >= 1st Jan and <= 15 Feb	4	Annual Period End Date is 05-02-2023
Year End Date > 15 Feb and <= 15 May	3	Annual Period End Date is 10-04-2023
Year End Date > 15 May and <= 15 Aug	2	Annual Period End Date is 15-07-2023
Year End Date > 15 Aug and <= 15 Nov	1	Annual Period End Date is 25-08-2023
Year End Date > 15 Nov and <= 31 Dec	4	Annual Period End Date is 10-12-2023

• FY Period Offset(FYPeriodOffset)

Rule	FY Offset	Example
Year End Date >=1 Jan and <= 30 Jun	1	Annual Period End is 31-03-2023
Year End Date >=1 Jul and <= 31 Dec	0	Annual Period End is 12-07-2023

Step 3: Updating the Database Tables

These values are to be updated in the below tables:

Table	Column	Value
ClientDB.clientmanage_company	PeriodOffset	Quarter Offset value
VirtuaMaster.Company	PeriodOffset	Quarter Offset value
	FYPeriodOffset	FY Offset value

Written By:	Shivani Zinjurke
Written On:	28/July/2025