"SDate" and "Period" parameters of get_data function

Hi everyone,
Thanks to the insights from another user's thread on this forum, I was able to create a function that retrieves the historical constituents of the SP1500 at a specific point in time (specifically, at the end of each year). My ultimate goal is to get a list of firms which where constantly part of the SP1500 between 2004-12-31 and 2006-12-31.
While the function works as intended, I'm having trouble understanding the purpose of the "SDate" and "Period" parameters. I would really appreciate some help in clarifying how these parameters function.
From what I gather, "FY0" likely refers to Fiscal Year 0, but I'm unsure of its exact role within the function. Additionally, the date appears in two places—once after "SPSUP" and again as a parameter. Could someone explain the difference between these two date references?
Thanks in advance for your help!
dates = ['2004-12-31', '2005-12-31', '2006-12-31']
#Create empty dataframe
SP1500_Complete = pd.DataFrame(columns=['Instrument', ' Company Common Name', 'Organization PermID', 'Date'])
# get S&P1500 constituents at the end of each year
for date in dates:
SP1500, er = ek.get_data(f'0#.SPSUP({date})', fields=['TR.CommonName', 'TR.OrganizationID'], parameters={'SDate': f'{date}', 'Period': 'FY0'})
SP1500['Date'] = date
print(SP1500)
SP1500_Complete = SP1500_Complete.append(SP1500, ignore_index=True) #Append dataframe
Best Answer
-
Hi @flammers ,
You can find more information about the params from Workspace DIB app. If you select one of fields, select parameters on the right and click the question mark of the respective params, a box with explanations will appear. Including the screenshots below:
Sdate:
Period:
If you have further questions about the params, the best help can we received from our content team by raising a content query via my.refinitiv.com or Help&Support section in Workspace.
Additionally, please have a look into the following article which introduces a python object to get historical constituents easily:
Building historical index constituents | Devportal (lseg.com)
Hope this helps.
Best regards,
Haykaz
0
Answers
-
Hi @aramyan.h
Thank you very much for your assistance and the helpful article. Greatly appreciated!
0 -
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 683 Datastream
- 1.4K DSS
- 613 Eikon COM
- 5.2K Eikon Data APIs
- 10 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 248 ETA
- 552 WebSocket API
- 37 FX Venues
- 14 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 23 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 275 Open PermID
- 44 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 22 RDMS
- 1.9K Refinitiv Data Platform
- 626 Refinitiv Data Platform Libraries
- 5 LSEG Due Diligence
- 1 LSEG Due Diligence Portal API
- 4 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.2K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 12 World-Check Customer Risk Screener
- 1K World-Check One
- 46 World-Check One Zero Footprint
- 45 Side by Side Integration API
- 2 Test Space
- 3 Thomson One Smart
- 10 TR Knowledge Graph
- 151 Transactions
- 143 REDI API
- 1.8K TREP APIs
- 4 CAT
- 26 DACS Station
- 121 Open DACS
- 1.1K RFA
- 104 UPA
- 191 TREP Infrastructure
- 228 TRKD
- 915 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛