ek.get_timeseries CLOSE for Mutual Funds
I am trying to pull closing values for ARTQX.O but get a CLOSE value of NaN , can you please advise why and if a different syntax needed using get_timeseries.
I'm raising this on behalf of a client.
ek.get_timeseries(["MSFT.O"],fields="CLOSE",start_date=get_date_from_today(start_date),end_date=get_date_from_today(end_date),corax="adjusted")
Best Answer
-
@James.Perkins, I found an old Python program I wrote that can extract the NAV history of a fund using RIC directly. You can give it a try.
ek.get_data('ARTQX.O',['TR.FundNAV.Date', 'TR.FundNAV'], {'SDate':'20120-01-01', 'EDate':'2019-05-26', 'Curn':'Native'})
Your way to specify the date range for latest data should also work. I found using the TR.FundNAV has a more timely updates of the latest price as I now see the 14.95 as the latest price but the TR.NETASSETVAL seems stays at the previous one: 14.40.
0
Answers
-
I believe this is not a technical question related to the Eikon API but some content question about mutual funds.
Generally mutual funds do not report “close” price, as “close” price should mean the price after the trading session ends for the day in an exchange. So close price is for instruments trading in an exchange like stocks or ETFs, not mutual funds.
The sample fund you showed is not an ETFs nor exchange listed based on Lipper database, so it does not has close price. It does have NAV price reported daily. Please notes, mutual funds’ NAV price usually reports on the night-time of the same day or the next day and typically lag behind “close” price reported for the stocks in the same market.
0 -
Thanks. Appreciated the response. After further review I think the issue here is that for Mutual Funds most of the reference data (including historical NAVs) are actually stored on an associated Lipper RIC Code (every Fund has a real-time RIC ; i.e. in this case ARTQX.O which would line up with an exchange ticker), as well as an associated Lipper RIC (i.e. LP40063921) .
You can retrieve the Lipper RIC code by using the field TR.LipperRICCode , then access the field TR.NETASSETVAL historically.
ek.get_data('ARTQX.O',["TR.LipperRICCode"])
ek.get_data('LP40063921',['TR.NETASSETVAL(SDate=0,EDate=-4,Frq=D).date',
'TR.NETASSETVAL(SDate=0,EDate=-4,Frq=D)'])
If there is a better solution for pulling historical NAVs for Mutual Funds please share ; ideally would like to not have to convert the ticket --> RIC --> Lipper RIC since it's an extra step.
0
Categories
- All Categories
- 6 AHS
- 39 Alpha
- 162 App Studio
- 4 Block Chain
- 5 Bot Platform
- 17 Connected Risk APIs
- 47 Data Fusion
- 30 Data Model Discovery
- 608 Datastream
- 1.3K DSS
- 577 Eikon COM
- 4.9K Eikon Data APIs
- 7 Electronic Trading
- Generic FIX
- 7 Local Bank Node API
- Trading API
- 2.7K Elektron
- 1.3K EMA
- 236 ETA
- 519 WebSocket API
- 33 FX Venues
- 10 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 20 Messenger Bot
- 2 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 59 Open Calais
- 264 Open PermID
- 39 Entity Search
- 2 Org ID
- PAM
- PAM - Logging
- 8.4K Private Comments
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 20 RDMS
- 1.4K Refinitiv Data Platform
- 370 Refinitiv Data Platform Libraries
- 3 Refinitiv Due Diligence
- LSEG Due Diligence Portal API
- 3 Refinitiv Due Dilligence Centre
- Rose's Space
- 1.1K Screening
- 18 Qual-ID API
- 13 Screening Deployed
- 23 Screening Online
- 10 World-Check Customer Risk Screener
- 990 World-Check One
- 44 World-Check One Zero Footprint
- 45 Side by Side Integration API
- Test Space
- 3 Thomson One Smart
- 1.2K TR Internal
- Global Hackathon 2015
- 2 Specialists Who Code
- 10 TR Knowledge Graph
- 150 Transactions
- 142 REDI API
- 1.7K TREP APIs
- 4 CAT
- 21 DACS Station
- 117 Open DACS
- 1.1K RFA
- 103 UPA
- 172 TREP Infrastructure
- 224 TRKD
- 886 TRTH
- 5 Velocity Analytics
- 5 Wealth Management Web Services
- 60 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛