How can I transcode from normal RIC to delisted RIC so that I can query the price?

Hi Team,
I am writing on behalf of Mr. Max Zhu. How can he transcode from normal RIC to delisted RIC so that he can query the price?
"For example, for PEUP.PA I need to transcode to PEUP.PA^A21. In order to do that, I need to query the delist date. Can you advise how to query the delist date? Is there an attribute I can use with get_data?"
Best Answer
-
I think you can use TR.RetireDate field to get the delist date.
This forum is not the best place to ask about content questions.
For an authoritative answer to any content questions, the best resource is the Refinitiv Content Helpdesk.
This forum is dedicated to things specific to the use of Eikon APIs.
The moderators here do not have deep expertise in every type of content available through Eikon.
The Refinitiv Content Helpdesk can be reached using Contact Us capability in your Eikon application.
Or by calling the Helpdesk number in your country.
Or at https://my.refinitiv.com/0
Answers
-
I would like to add more information.
The suffix format is
^<month><year>
month is A, B, C, D, ... , L (Jan to Dec)
So PEUP.PA delisted in January 2021.
So the delist RIC is PEUP.PA^A21
0 -
This doesn't seem always work. eg, '000030.KS'
0 -
Hi @Max.Zhu
I think 000030.KS is not a valid RIC anymore so you cannot pass it to the get_data()
The workaround is to search for it.
#pip install refinitiv.dataplatform
import refinitiv.dataplatform as rdp
rdp.open_desktop_session('xxxxxxxxx')
rdp.search(query="000030.KS",filter = "startswith(RIC,'000030.KS')")0 -
hmmm is this the same Eikon access token I should put in?
also I don't understand why things need to be handled differently? Under what circumstance a RIC will be considered `invalid`?
rdp.open_desktop_session('xxxxxxxxx')
0 -
Hi @Max.Zhu
You can use the same app key as Eikon Data API.
I am not a content expert but I can say that the RIC is considered invalid if it does not exist in the system.
In this case 000030.KS does not exist in the system anymore.
A simple API call can verify this:
However, if you need to clarify when the RIC after delisted will become invalid, you can contact the content helpdesk to get the clarification.
0 -
surely 000030.KS still exists in the system because 000030.KS^B19 is still working.... but sure I will raise to support
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
- 684 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
- 629 Refinitiv Data Platform Libraries
- 4 LSEG Due Diligence
- 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
- 86 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛