Missing TR.RICCode data on 12/11/2018
We collect some information daily and save it to the db. I had no problem to collect that field for the tickers for last 15 days.
Yesterday I've got "Unable to collect data for the field 'TR.RICCode' and some specific identifier(s)." for 21 tickers:
SURV10A.MX
SURV10BF1.MX
SURV10BF2.MX
SURV10BF3.MX
SURV10BFE.MX
SURV10BFS.MX
SURV10BFX.MX
SURV10BOE1.MX
SURV20A.MX
SURV20BF1.MX
SURV20BF2.MX
SURV20BFE.MX
SURV20BOE1.MX
SURV40A.MX
SURV40BF1.MX
SURV40BF2.MX
SURV40BF3.MX
SURV40BFE.MX
SURV40BFS.MX
SURV40BFX.MX
SURV40BOE1.MX
I've contacted Helpdesk and they couldn't reproduce the issue.
Today I re-ran the request. Those tickers are not even present in RSearch results anymore.
Also this ticker DRIV.MX was in the RSearch result first time today, but has no TR.RICCode as well.
I've had the conversation about TR.RIC and TR.RICCode and if I remember correctly those fields should always be available.
Could you check what's wrong with them?
Best Answer
-
@igorg this is a content related question. I would advise you to ask the support desk to refer you to an exchange specialist supporting the exchange, in this case it is Bolsa Mexicana de Valores.
When you get 'Unable to collect data for all requested fields.' while accessing standard reference fields like TR.AssetCategory or TR.AssetCategoryCode, it means that there is no record of this instrument in the fundamental database.
When you have a RIC and can see it in the quote app, it only means that it was created on the real-time system. It can be a test ric, an automatically created instrument for an exchange that has not been populated yet, an error, etc. Only a content specialist who owns that dataset can answer your question with confidence.
DRIV.MX does not look like anything at this point, just a placeholder for something.
SURV*.MX look like funds to me, however, they were not classified correctly, possibly by mistake. I can get their TR.RICCode field though, if you still can't let me know.
Hope this helps.
0
Answers
-
Our process is : collect all *.MX tickers using RSearch , then requests for ISIN, SEDOL and TR.RICCode using Dex2.
Today I don't have a problem with SURV*.MX because they are not returned in RSearch query
0
Categories
- All Categories
- 3 Polls
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 34 Data Model Discovery
- 690 Datastream
- 1.4K DSS
- 629 Eikon COM
- 5.2K Eikon Data APIs
- 11 Electronic Trading
- 1 Generic FIX
- 7 Local Bank Node API
- 3 Trading API
- 2.9K Elektron
- 1.4K EMA
- 255 ETA
- 559 WebSocket API
- 39 FX Venues
- 15 FX Market Data
- 1 FX Post Trade
- 1 FX Trading - Matching
- 12 FX Trading – RFQ Maker
- 5 Intelligent Tagging
- 2 Legal One
- 25 Messenger Bot
- 3 Messenger Side by Side
- 9 ONESOURCE
- 7 Indirect Tax
- 60 Open Calais
- 280 Open PermID
- 45 Entity Search
- 2 Org ID
- 1 PAM
- PAM - Logging
- 6 Product Insight
- Project Tracking
- ProView
- ProView Internal
- 23 RDMS
- 2K Refinitiv Data Platform
- 716 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
- 27 DACS Station
- 121 Open DACS
- 1.1K RFA
- 106 UPA
- 194 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 95 Workspace SDK
- 11 Element Framework
- 5 Grid
- 19 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛