question

Upvotes
Accepted
646 21 31 40

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?

eikoneikon-com-api
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
4.6k 26 7 22

@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.

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

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

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.