| Name | Helptext Description | Data Type | Len | Codetable |
|---|---|---|---|---|
| INR | Internal Unique ID | Text | 8 | |
| OWNREF | Our Reference | Text | 16 | |
| NAM | Externally Displayed Name to Identify the Contract | Text | 80 | |
| OPNTRNINR | TRNINR which opened contract | Text | 8 | |
| CREDAT | Date Created | Date | 12 | |
| CLSDAT | Date Closed | Date | 12 | |
| EXPDAT | Expiry Date | Date | 12 | |
| OPNDAT | Opening Date | Date | 12 | |
| OWNUSR | Resp. User | Text | 8 | <fixed-length> |
| VER | Version | Text | 4 | |
| CHATO | Our Charges to | Text | 1 | CHADET |
| STACTY | Country Code (Risk Country) | Text | 2 | CTYTXT |
| STAGOD | Goods Code (for Statistics) | Text | 6 | GODCOD |
| ACCDAT | Accepted on | Date | 12 | |
| AMENBR | Number of Amendments | Numeric | 2 | |
| DOCSTA | Document Set Status | Text | 1 | Embedded |
| RESFLG | Reserved Contract | Text | 1 | Embedded |
| AMEDAT | Date of Last Amendment | Date | 12 | |
| REJFLG | Direct rejection | Text | 1 | |
| TOLAMT | Tolerance Amount | Numeric | 18 | |
| TOLCUR | Currency of Tolerance Amount | Text | 3 | CURTXT |
| ETYEXTKEY | Entity | Text | 8 | |
| PRDCOD | Product Code | Text | 6 | PRDCOD |
| PRDSUB | Product Subtype | Text | 6 | PRDSUB |
| PRDVAR | Product Variant | Text | 6 | PRDVAR |
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 holds the INR of the transaction which opened/issued the contract.
This date field identifies the date the entry was physically added to the database.
This fields indicates the closing date of a contract. If an entry has been made, the contract is closed and may no longer be used to process business transactions except special transactions like Settling Charges or Common Messages.
The field holds the opening/issuing date of the contract. If this field is set, the contract has been legally established and it might be used for business transactions. This date describes the point in time when this contract became legally binding. This might be a date prior to the creation date, when the contract was legally binding before it was stored in the database.
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.
This field contains the type of goods shipped. The goods code is used to evaluate contracts by the type of goods. The codetable can be customized by the bank according to their needs.
This field is used to store the number of amendments made to the contract so far. This field is automatically updated from the relevant amendment transaction.
The current status of the document set is stored in this field.
| Code | Text |
|---|---|
| A | Payment Undertaking pre-opened |
| B | Payment Undertaking opened |
| C | Payment Undertaking accepted |
| D | Payment Undertaking settled |
| E | Payment Undertaking closed |
| Code | Text |
|---|---|
| Normal Contract | |
| X | Reserved Contract |
This field contains the date of the last amendment processed under the contract. If it is empty the contract is still in its original condition. This date is automatically updated by the relevant amendment transactions.
This flag is set in the (pre)opening transaction in case an incoming message is rejected. The contract is closed directly.
This field holds the external key of the owning entity 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 are visible to the user.