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

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

This field holds the User ID of the person responsible for handling this 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 date field specifies when the expiry date of the shipping guarantee.

This field specifies the date when the bank has received the order to issue a shipping guarantee.

Contract status flag. If not empty, the contract has been reserved and only a few basic fields have to be filled in. Visible in 'Info shipping Guarantee'. Invisible in all other transactions.

This field can be used for statistical reasons and allows the bank to evaluate the country risks.

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 flag indicates the party who has requested the issuance of the shipping guarantee.

This field is used to indicate that the goods are released under shipping guarantee.

This field indicates the type of transport document (e.g. Bill of Lading) which is securing this shipping guarantee.

This field indicates the number of the transport document (e.g. number of Bill of Lading).

This field indicates the date of the transport document (e.g. bill of ladingl) which is presented under this shipping guarantee.

This field indicates how the goods have been shipped (e.g. via sea, air or a combination of different transport modes).

This field specifies the place of transfer (in the case of a multimodal transport document), the place of receipt (in the case of a road, rail or inland waterway transport document or a courier or express delivery service document), the place of dispatch or the place of shipment to be indicated on the transport document.

This field specifies the final destination of the goods shipped under the underlying contract.

If this flag is set, goods are released to the applicant. Otherwise, goods can be released to another party.

This field contains the date of the received utilization.

This field contains the unique identifcation number of the parent contract.

This field contains the technical INR of the linked contract, e.g. in case the shipping guarantee is connected to an import document set, this field contains the INR of that contract.

This field contains the type of the parent contract.

This field contains the technical database table name of the linked contract, e.g. in case the shipping guarantee is connected to an import document set, this field contains “BRD”.

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.

Initial version to support the differentiation of predefined bank products cross business sectors.

This organizational solution is made up of three fields product code (PRDCOD), product subtype (PRDSUB) and Product variant (PRDVAR) , 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 product code (PRDCOD), product subtype (PRDSUB) and Product variant (PRDVAR) , 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 product code (PRDCOD), product subtype (PRDSUB) and Product variant (PRDVAR) , if needed.

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