How is the Legal Entity Hierarchy request working ?
What does one input in the request and what is the return containing ?
Does one enter an OrgID and get data about the whole tree structure containing this OrgID? What's the basic idea behind it? What's the "RCP ID" that seems to be an important field in that request?
Thanks for hints and info.
Bernard
Best Answer
-
RCP ID
Description of the RCP ID: "System-generated code used to uniquely identify a legal entity (resolving duplication)".
To get a field description you can either:
A) Create a request template in the GUI and select a field:
Run an API query to get the full list of fields and descriptions. In this case do a GET to this endpoint (note it contains the template name as parameter, at the end):
"https://hosted.datascopeapi.reuters.com/RestApi/v1/Extractions/GetValidContentFieldTypes(ReportTemplateType=ThomsonReuters.Dss.Api.Extractions.ReportTemplates.ReportTemplateTypes'LegalEntityHierarchy')
Hierarchy positioning
In my response to the other query last November I just displayed the first item in the result set, but note the results are returned in no specific order. If you run that query and look at the Relationship Type field content you will see a list of IsAffiliatedWith entries, followed by a set of IsParentOf entries, which seems to confirm your suggestion that this request returns all entities below the input entity. I think you are right, but honestly, I'm not sure, that is a content query that I cannot answer. For that I suggest you directly contact the TRTH support team via MyRefinitiv. In the product field, select "Thomson Reuters Tick History v2".
0
Answers
-
@BTh,
The legal entity hierarchy allows you to see companies, who belong to them (subsidiaries), who they belong to (parents), and affiliates.
Here is an example body of the request using the API, using a RIC as the instrument identifier. I used the instrument 0700.HK which is Tencent Holdings, on the Hong Kong exchange:
{
"ExtractionRequest": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.LegalEntityHierarchyExtractionRequest",
"ContentFieldNames": [
"Node/Level", "Official Name", "Relationship Type",
"Derived Parent Official Name", "Derived Ultimate Parent Official Name",
"Immediate Parent Official Name", "Ultimate Parent Official Name",
"Related Official Name"
],
"IdentifierList": {
"@odata.type": "#ThomsonReuters.Dss.Api.Extractions.ExtractionRequests.EntityIdentifierList",
"EntityIdentifiers": [ { "Identifier": "0700.HK", "IdentifierType": "Ric" } ]
},
"Condition": { "DeltaDays": -1 }
}
}The "DeltaDays": -1 condition means that we want all the historical data. If you only wanted the changes of the last N days, let us say the last week, you could set "DeltaDays": 7.
You can make the same request in the GUI, by searching for the instrument, then clicking on it. Then click in the left column menu on Legal Entity, then on More Entity Details, and finally on Hierarchy, which will take you here:
I don't see any RCP ID in the request parameters. Can you tell me where you found it ?
0 -
See also this query, on the same topic.
0 -
The RCP ID is a field mentioned in the DSS.Api.examples app for the LegalEntityHierarchy request:
ContentFieldNames = new[] {
"ID", "ID Type", "Immediate Parent ID", "Immediate Parent Official Name",
"Immediate Parent RCP ID", "Node/Level", "Official Name", "RCP ID",
"Source RCP ID", "Ultimate Parent ID", "Ultimate Parent Official Name", "Ultimate Parent RCP ID",
"User Defined Identifier"}
In your answer to the former query last November, you mention the "first element" of the response. Does that mean that basically this request returns all entities below the input entity, i.e. it should be used for the hierarchy "head" and delivers all the entities linked to this head ?
Bernard
0
Categories
- All Categories
- 6 AHS
- 36 Alpha
- 166 App Studio
- 6 Block Chain
- 4 Bot Platform
- 18 Connected Risk APIs
- 47 Data Fusion
- 33 Data Model Discovery
- 682 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
- 2 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.8K Refinitiv Data Platform
- 622 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
- 84 Workspace SDK
- 11 Element Framework
- 5 Grid
- 18 World-Check Data File
- 1 Yield Book Analytics
- 46 中文论坛