This table links the parties and the addresses. There might be more than one address per party. Via this association table it is possible to use different address files concurrently.
Name | Helptext Description | Data Type | Len | Codetable |
---|---|---|---|---|
INR | Internal Unique ID | Text | 8 | |
PTYINR | INR of Associated Party | Text | 8 | |
NAM | Name | Text | 40 | |
PRI | Priority Marker | Text | 1 | |
ENO | Running Counter for External Identification | Text | 3 | |
OBJTYP | Object type | Text | 6 | |
OBJINR | Object INR | Text | 8 | |
OBJKEY | Alternate Technical Key of Associated Address | Text | 24 | |
USG | Coded Usage of Address [xxxxxx] | Text | 3 | Embedded |
VER | Version | Text | 4 | |
BIC | BIC of Address (Optional) | Text | 11 | |
ADRSTA | Address Status | Text | 1 | Embedded |
PTYTYP | Type of Party | Text | 15 | |
PTYEXTKEY | External Key Used to Uniquely Identify a Party | Text | 24 | |
TID | TradeConnect ID | Text | 23 | |
LOCCTY | Country of Domicile | Text | 2 | CTYTXT |
CLC | Clearing Code (for Banks) | Text | 35 | |
BICTAR | BIC of Address (Optional) Target Address | Text | 11 | |
SGPFLG | Party with sanctions | Text | 1 | |
LEI | Legal Entity Identifier | Text | 20 | |
ETGEXTKEY | Entitygroup | Text | 8 | |
GETFLDNRM | Field holding the normalized search fields. | Text | 115 |
Unique internal ID of a record within the table. The INR is a text field, which is created by retrieving the next valid entry from the counter of this table. The field INR is used to enable links from other tables to this table.
For contractdata the INR also links the two tables xxD and xxT as associated entries hold the same INR.
This field is used to define the identification number (INR) of the Party associated with this address. N.B.: Each address in the database is associated with a Party. Party refers to a legal entity. Each Party has at least one address associated with it, and a Party can have several addresses or locations.
Replicated copy of the Name column of the ADR table or an otherwise created field used to describe the address.
If multiple addresses are assigned to a party, the priority marker is used to designate an address as the main address for party. This address will then be taken for corresponding with the party in daily processing.
If multiple addresses have been assigned to a party, the counter shows the serial number of the current address associated to the party.
The object type designates the table name or some other descriptions that display the storage space of the addresses assigned to a party The default setting is ADR (internal address file of the application) The object type can vary if the addresses are not stored in an ADR file, for instance, but on a HOST computer or some other systems.
Unique ID (INR) of the object stored in the table identified by the Object Type field.
AThis specifies the primary key of the object stored in the table identified by the Object Type field. If this table, however, has no identification number (INR) this field is used to identify the entry in the table. If the table does have an INR, the field holds a copy of the External Key or a similar field used to identify the address.
This field is used to specify the type of usage for the associated address. “Add. Local address” will enable the usage of the additional address only locally whereas “additional address” enables the usage of the additional address similar to the usage of the party.
Code | Text |
---|---|
MAA | Main Address |
MAB | Additional Address |
This field holds the version counter used to keep track of the history of an entry of this table. The individual versions are managed by entries in the SLG table.
Copy of the column from the ADR table.
Copy of the column from the PTY table.
Code | Text |
---|---|
T | Temporary |
Downloaded |
Copy of the column from the PTY table.
Copy of the External Key column from the PTY table.
Copy of the column from the ADR table.
This field contains the code of the country for the address.
This field is used to indicate the national clearing system code of the address. E.g.: CHIPS universal identifier (US) , or CHAPS branch sort code (UK), etc . Exception: German BLZ should additionally be entered to the separate field BLZ. Reason: BLZ has been defined in pre-IBAN-times to handle the german Bankleitzahl. When dealing with IBAN account numbers all clearing codes are expected the field 'Clearing Code'.
This field holds the external key of the owning entity group to identify the logical owner of this entry. This field is filled automatically during insert and is used as filter when accessing the database. Without special implementation only entries of the currently active entity group are visible to the user.
Replicated copy of the column of the ADR table.
Field holding the concatenated and normalized sum of all search fields used by quick search. This is one of the fields set in a SdbSetNRMFields method defined in the table definition module.
If this flag is not empty this party is a sanctioned party. This make a warning popup in business transactions. X = ticked empty = not ticked
LEI is an important (but not mandatory) identifier for ISO.
The ISO 17442 standard defines the Legal Entity Identifier (LEI). It is a unique 20-character alphanumeric code assigned to all entities that are counterparties to financial transactions. The code itself is neutral, with no embedded intelligence or country codes that could create unnecessary complexity for users.
It should primarily be used as identifier for corporates. For banks the main identifier code should always be a BIC.