Factset data not showing for some/all elements in the BM editor

Description:

The issue maybe reported that data of some or all elements is not updating in the BM for a particular peer or multiple peers in the same template even after clicking on the update button. In the below example, we can see that the FCF element was not updated.

The issue could be because of the element mapping or the data was not received from Factset. I have already covered the points to check, how to check if the peers have received the data from the source and if the same has been updated in the DWH tables. Please refer documentation (https://virtuaresearchinc.freshdesk.com/a/solutions/articles/88000057710 ) for detailed explanation.

Steps to reproduce:

1. Log into Vbench link and click on Benchmarking/Competitive Intelligence.
2. Enter ticker and select the template.
3. Select the peer from the list and check the Factset elements.

Resolution:

1. Check in the source table if the data is present or not. We can check the data in the Daily excel file or by running the below queries.

Basic table contain - EPS and SALES

Advance table contain - EPS_GAAP, EPS_NONGAAP, FCF, EBIT and EBITDA

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 (ISINNo)// AND CONS_END_DATE is null

ORDER BY CONS_START_DATE DESC;

SELECT i.isin,un.UNITFACTOR,cz.* 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_QF" cz ON cz.fsym_id = c.fsym_regional_id

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

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

ORDER BY CONS_START_DATE DESC;

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_ADVANCED_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 (' ISINNo ') // AND CONS_END_DATE is null

ORDER BY FE_FP_END DESC;

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_ADVANCED_CONH_QF" 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 (' ISINNo ') // AND CONS_END_DATE is null

ORDER BY FE_FP_END DESC;

1. Check if the data has been updated in the DWH tables:

Select * from Public.DWESTFINALVALUES_Q where dwcompanyid = DWCompanyID ; 

Select * from Public.DWESTIMATEVALUES_Y where dwcompanyid = DWCompanyID ;

StoredProcedure: CALL SPT_GetCompEstPostReleaseDateValues_QandY(); 

*NOTE: Cons_Start_Date in Source Table is same as Reported date in DWH.

1. If the data is present in the DWH as well. Check the element mapping of the Factset element.

1. Click on edit in the BM editor.
2. Click on blue Factset icon.

3. Check the Factset element mapping:

1. If the factset element is not mapped correctly, inform the analyst. 
2. After the mapping is done. Click on Apply. Save the template and publish it.

Written by: Shivani Zinjurke

Date: 03/August/2024