This type of object the CCI entry refers to. This is the table the contract is stored in.

This field contains the identification number (INR) of the 'relevant object' for this entry. The table for the relevant object is stored in the object type field.

The field holds the reference of the associated contract.

This field holds the descriptive name displayed in the application to describe and to search for a contract.

This field holds the User ID of the person responsible for the associated 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 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 field describes the validity of the associated contract.

The field holds the role that serves as the direct partner address abroad in the associated contract, (if this role is available). Usually this is the issuing bank or the main partner bank where the local bank maintains direct relations. If this field is set, this role acts as the partner abroad. However, this does not automatically mean that this role is associated to an address or that a used party entry for that role exists.

This field contains the identification number (INR) of the address (PTA) entry identified by the Role of Bank field of the associated contract. If no PTA is used for the specified role this field might be empty.

This field contains the INR of the PTY entry. If PTY/PTA is not used, then the field can remain blank.

The field holds the role which acts as direct local partner address in the associated contract, if this type is available. Usually this role is the role of the client of the local bank where the bank has a direct relation to. If this field is set that role acts as the local partner but does not mean that this role is associated to an address or that a used party entry of that role exists.

This field contains the identification number (INR) of the address entry identified by the Role of Customer field of the associated contract. If no address is used for the specified role this field might be empty.

This field contains the INR of the PTY entry. If PTY/PTA is not used, then the field can remain blank.

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 table of the parent object is stored in field 'Parent Type', if exists. This field contains the unique identifcation number of the parent contract.

This field contains the type of the parent 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.

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.

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.

Initial version to support the differentiation of predefined bank products cross business sectors. This organizational solution is made up of three fields PRDCOD, PRDSUB and PRDVAR providing a bank product, a sub differentiation and individual variants if needed. Here the 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 three fields PRDCOD, PRDSUB and 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 three fields PRDCOD, PRDSUB and 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.

This field is defaulted with the country code of the receiver of the L/C and therefore indicates the risk country of the L/C. It is used for statistical reasons and allows the issuing bank to evaluate the country risks it has entered by issuing the L/C.