Factset data not updating for latest quarters

Created by Shivani Zinjurke, Modified on Tue, 25 Mar at 1:17 PM by Shivani Zinjurke

 

Written by:

 Shivani Zinjurke

Written on:

03/August/2024

Description:

 

The issue was reported that for some quarters (Latest Quarters) were not updated in BM for the ticker (Screenshots below). In below example, we can see that for MDB peer, Q1 26 quarter was not updated and data was not updated for the FCF.

https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/88066214846/original/XuGHOFCD67MZCa4EUCpS1mx4xnhhlb4Qnw.png?1721653393

 

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 Daily excel file if the data is showing in the file or not. OneDrive - Virtua Exchange. The data in this file contains the source data which we receive from the Factset. If the data is not available in the Daily Factset excel file, we need to check in the source table by using 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;


2. If data is available in the source table. Check if the company mapping is correct in factset. Using below query in Snowflake:

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


3. If mapping is correct, check the subscriptions.

Log into https://um.indigotools.com/um/Client/Clients (User Management) and search for the ticker. Click on Apps tab and Check the ‘To date’ for the Factset App. 

We have 2 Factset services: BM Factset (Named: Factset) and other is CES Factset. 

For BM issues we need to check the service date of ‘Factset’.

 https://s3-ap-south-1.amazonaws.com/ind-cdn.freshdesk.com/data/helpdesk/attachments/production/88066219796/original/lyg190mx9GgZlbq6he5a0HBdKyzOYO1MAA.png?1721655857

 

  1. If the subscription of the client is expired. The data will not be fetched for the ticker. 
  2. Confirm with Manisha Jha or Prasad Manavarthi for the dates and change the date in UM (User Management).
  3. After the subscription was updated. The data can be seen now.

 

 



Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article