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 contains the reference number of the manual contract being established. The reference number can be up to 16 characters long. This field should be defined as a database key field to optimize performance. This field can be used to search for a manual contract within the database.

This field holds the descriptive name displayed in the application to describe and to search for a contract. Within the default configuration this field is set by a default rule based on the contract amount and the main party and cannot be modified by the user.

This field holds the User ID of the person responsible for handling this contract.

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.

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 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.

This field contains the date of expiry of the manual contract.

This field contains the date of the instruction order received.

This field contains the reference of the addressee.

This field contains the reference of the applicant.

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.

The field can be used for statistical reasons and allows the bank to evaluate the country risks it has entered by issuing the manual contract.

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.

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.

If this flag is checked, automated periodic settlements can be generated per system pending transaction (SPT).

If this flag is checked, automated balance statements can be generated per system pending transaction (SPT).

If balance statements are created per system pending transaction (SPT), the date set in reference date is used. Manuel execution sets this date to today.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of the three fields “product code” (PRDCOD), “product subtype” (PRDSUB) and “Product Variant” (PRDVAR), providing a bank product, a sub differentiation and individual variants if needed.

Here the “product code” PRDCOD shall identify the business sector together with some key criteria like confirmed or unconfirmed LC in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of the three fields “product code” (PRDCOD), “product subtype” (PRDSUB) and “Product Variant” (PRDVAR), providing a bank product, a sub differentiation and individual variants if needed.

Here the PRDSUB shall identify the business sector specific bankside defined products adding some key sub criteria in a cross business sectors unique identification.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of the three fields “product code” (PRDCOD), “product subtype” (PRDSUB) and “Product Variant” (PRDVAR), providing a bank product, a sub differentiation and individual variants if needed.

Here the product variant is intended as possible extension to setup specific variants below the product and subproduct code.