## Entity servicer-instrument data

### Details of entity servicer-instrument data

Name | servicer-instrument data
Code | servicer_instrument_data
Parent | Logical Data Model 'AnaCredit GLO per bank LDM'
Comment | Servicer-instrument data is the combination of servicer and instrument that indicates which servicer services which instrument. This entity type is a subset of the counterparty-instrument data from the regulation.
Parent Entity | <None>
rowcount reporting indicator | entity type with reported rowcount

### List of attributes of the entity servicer-instrument data

Name | Code | Comment | Data Type | Domain | Mandatory | Primary Identifier | Foreign Identifier
reporting agent identifier | reporting_agent_identifier |  | Variable characters (50) | riad counterparty domain | X | X | X
observed agent identifier | obsrvd_agnt_cd | Observed agent identifier is a number, assigned by De Nederlandsche Bank, that uniquely identifies the observed agent. | Variable characters (50) | riad counterparty domain | X | X | X
counterparty identifier | counterparty_identifier |  | Variable characters (60) | identifier domain | X | X | X
counterparty role | entty_rl | Role of the counterparty in an instrument. | Variable characters (25) | counterparty-instrument role type | X | X | X
contract identifier | cntrct_id | An identifier applied by the reporting agent to uniquely identify each contract. Each contract must have one contract identifier. This value will not change over time and cannot be used as the contract identifier for any other contract. Each contract identifier must be unique for each contract that generates credit risk for the same observed agent. This identifier must not be reused at any point in time to identify a different contract with the same observed agent. | Variable characters (60) | identifier domain | X | X | X
instrument identifier | instrmnt_id | An identifier applied by the reporting agent to uniquely identify each instrument under a single contract. Each instrument must have one instrument identifier. This value will not change over time and cannot be used as the instrument identifier for any other instrument under the same contract. Each instrument identifier must be unique for each contract, i.e. all instruments embedded in a single contract are to be assigned a different instrument identifier, and these must not be reused at any point in time to identify a different instrument within the contract. However, instruments associated with different contracts may use the same identifier. | Variable characters (60) | identifier domain | X | X | X
reporting reference date | reporting_reference_date |  | Date | reporting reference date | X | X | X

### List of relationships of the entity servicer-instrument data

Name | Code | Generate | Entity 2 | Entity 1 | Dependent Role | Entity 1 -> Entity 2 Role Cardinality | Entity 2 -> Entity 1 Role Cardinality
has servicer via | instrument_has_servicer_via_servicer_instrument_data | X | instrument | servicer-instrument data | servicer-instrument data -> instrument | 1,1 | 1,n
services instrument via | servicer_services_instrument_via_servicer_instrument_data | X | servicer-instrument data | servicer | servicer-instrument data -> servicer | 1,n | 1,1

### List of identifiers of the entity servicer-instrument data

Name | Code | Parent | Primary Identifier
servicer-instrument data PK | servicer_instrument_data_pk | Entity 'servicer-instrument data' | X

Previous
Home
Next