RIC change

Hello, I am using Reuters DSS and had a question on RIC change and tracking. Currently I get a set of terms and conditions data every night based on a list of RICs previously stored. If a RIC has changed will a request with the old RIC bring back data with the new RIC. If so then how long will DSS still support lookup by the old RIC?
I am thinking of using one of the User Defined fields to keep track of the old ric so that I can match up requests when the RIC changes (hope this makes sense). Is there anyting I should be wary of by following this approach? Is there a better way to do this? I dont have access to the TRTH service for finding historical changes..
Many Thanks
Best Answer
-
@neil.gallagher, sorry for the late reply.
If a RIC has changed will a request with the old RIC bring back data with the new RIC
No. Requests must be made with the current name, not an old name.
Is there a better way to do this?
For your use case (daily request for a set of RICs), the best approach is to use the RIC maintenance reports. They contain: Deletions, Renames, Currency Conversions, Delists, Relists, File Code Updates and Stock Split Adjustment Factors.
There are 2 things you need to do:
1. Set-up: enable RIC maintenance reports in the user preferences in the GUI:
2. Daily: process the RIC maintenance reports
2.a. Retrieve the report file. Note that if there are no changes, the file is empty.
2.b. Process the file to extract the information you require. For instance, you can extract RIC renames, and modify your data requests accordingly to use the latest name.
Further references
The report is in CSV format, a detailed description can be found here.
.Net SDK tutorial 3 introduces this topic, see in particular here and (much further down) under heading "Retrieving the extracted data".. .Net SDK tutorial 4 describes the preference setting and file retrieval for a scheduled extraction.
The REST API Tutorial 10 also covers this (using Postman) for a scheduled request.
0
Answers
-
Many thanks for the answer.
The reason I asked the question is that I've noticed that I can retrieve latest security details when I use an old sedol or isin but seemingly not ric. Are there any guidelines on this as regards specific security identifiers? Thanks again
0 -
@neil.gallagher, for a data related query like this one, the best and speediest way to receive an answer is to to contact your assigned product specialist directly. Alternatively you can open a content-related enquiry via My Account or call the Thomson Reuters Help Desk directly.
0 -
@Christiaan Meihsl - Does this maintenance report also cover off CUSIP changes as well? My customer is having a difficult time keeping up with them and their system ends up creating a new one and keeps the old one thus having 2 records. Here is their inquiry verbatim:
We get retired/old CUSIPs
from custodians in some cases and will use it for new security creation.
In IDC it would determine that we were referencing a security by a retired
CUSIP and give us the data we requested and fix the CUSIP for us in that
dataset. Datascope continues to keep shells of securities with a RIC for
some time after a CUSIP change and we end up creating a security based on the
shell of the retired CUSIP. What is the correct logic for determining if
the security data we requested is from a retired CUSIP so that we can perform
some other query to find the current/valid CUSIP?0 -
Q: Does this maintenance report also cover off CUSIP changes as well?
A: As far as I know, it does not. Even though DSS delivers cross reference data, it is a RIC centric product, and the maintenance report contents reflect that.
For the correct logic to handle retired CUSIPs, please direct this to the help desk, as that query is not related to software development, and our moderators do not have the required deep expertise in all the content sets available through our products to answer your question.
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
- 687 Datastream
- 1.4K DSS
- 622 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
- 254 ETA
- 557 WebSocket API
- 38 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
- 276 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
- 676 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
- 104 UPA
- 193 TREP Infrastructure
- 229 TRKD
- 918 TRTH
- 5 Velocity Analytics
- 9 Wealth Management Web Services
- 90 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 48 中文论坛