RIC and It's Service name
Best Answer
-
Thanks for reaching out to us.
You are using Consumer 450 which connects to Refinitiv Real-Time Optimized (RTO). The main real-time service on RTO is ELEKTRON_DD. If it returns "The record could not be found", it indicates that those RICs may be invalid or delisted.
Please share some RICs that return "The record could not be found" so we can verify them. Otherwise, you can contact the content support team directly via MyRefinitiv to verify those RICs.
0
Answers
-
Hello @Maha Rana Parthap Sing
The "record not found " message indicates that the RIC name is invalid or does not exist. I highly recommend you contact the Content Support team to verify if the RICs you need are available on the Cloud. You can contact the team directly via the https://my.refinitiv.com/content/mytr/en/helpandsupport.html website.
0 -
Hi @Jirapongse and @wasin.w ,
Thanks for the inputs. Ill reach out to content team for data related queries.
I have around 13K RICS now. I would like to know among these 13K how many RICS are valid and how many are invalid? Is there any UI where I can upload these RICS and find if those are valid or invalid.
Regards,
Rana
0 -
Hello @Maha Rana Parthap Sing,
RIC search tool can be used to look up a specific instrument.
I do not know of a GUI tool that accepts bulk submission of RICs. You can check with Refinitiv content support for the authoritative answer from the content perspective.
Using EMA consumer 450, an approach can be to capture output, note all invalid RICs that result in image response:
StatusMsg
streamId="5"
domain="MarketPrice Domain"
state="Closed / Suspect / Not found / '**The record could not be found'"
name="JPY=2"
nameType="1"
serviceId="257"
serviceName="ELEKTRON_DD"
StatusMsgEndand remove them from your list. Or you can note all valid RICs that result in image response, and to form a new list.
An alternative approach, if you have Datascope select access, HistoricalBulkSearch can be an option, this will require a bit of coding- to read in your list of instruments, structure into HistoricalBulkSearch request, submit the request and parse the result.
Hope that this information helps
0 -
For now, I will note all invalid RICS programmatically. Thanks for the inputs.
0
Categories
- All Categories
- 6 AHS
- 37 Alpha
- 161 App Studio
- 4 Block Chain
- 4 Bot Platform
- 16 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
- 367 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
- 59 Workspace SDK
- 9 Element Framework
- 5 Grid
- 13 World-Check Data File
- Yield Book Analytics
- 46 中文论坛