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 Participation The reference number can be up to 16 characters long. This field should be defined as a database key field to optimize the performance. This field can be used to search for a Participationt 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 contract amount and main party and cannot be modified by the user.

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 field contains the participation portion in percent of the underlying obligation. If entered manually the participation amount is calculated automatically.

This flag indicates whether or not the participation is made public to the risk party of the underlying obligation. If activated, no messages are send to the risk party.

This field contains the reference of the risk party.

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 is used to store the number of amendments made to the contract so far. This field is automatically updated from the relevant amendment transaction.

This field indicates whether the contract is available by sight payment, deferred payment, acceptance, negotiation or mixed payment.

This field contains the bank/role that is authorized to pay, accept, negotiate or transfer an obligation under a deferred payment for the contract.

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 expiry date of the participation.

This field contains the place where the L/C expires.

This field specifies the type of L/C of the underlying contract.

This field further qualifies the contract amount and becomes important when checking documents presented under the contract. If the code “not exceeding” is used, no tolerance is permitted. If the code “according to UCP” is used, allowances are granted based on stipulations provided in Article 30 of the UCP.

This field specifies the positive tolerance to the nominal amount of the underlying contract as percentage plus that amount. In order to calculate the maximum amount (e.g. the maximum risk of the bank), the positive tolerance amount is added to the nominal amount.

This field specifies the negative tolerance to the nominal amount of the underlying contract as percentage minus that amount.

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 User ID of the person responsible for handling this contract.

This date field specifies the latest date of shipment under the underlying obligation.

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 indicates whether or not partial shipments (shipment in more than one lot) are permitted under the contract.

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

This field indicates whether or not transshipment is allowed under the contract. Transshipment is the shipment of goods to an intermediate destination, from where they are transported to another destination. One reason for this is the change in the means of transport during shipment (e.g. from ship to road transport).

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 is defaulted with the country code of the risk party of the underlying L/C or guarantee and therefore indicates the risk country of the participation. It is used for statistical reasons and allows the bank to evaluate the country risks it may have reduced by entering into an participation contract.

The field holds the opening/issuing date of the underlying contract for which the participation is booked.

This field contains the expiry date of the L/C or guarantee.

This field contains the name of the correspondent bank.

This field contains the long name of the risk party.

This field contains the reference of the correspondent bank.

Contract status flag. If not empty, the contract has been reserved and only a few basic fields have to be filled in. Visible in 'Pre-Opening a Participation' (PATPOP) and 'Info Participation' (INFPAD). Invisible in all other transactions.

This (invisible) field defines, if the amount or the percentage is confirmed in a partially confirmed contract.

Based on this information, the percentage or amount are protected and calculated from the other field.

This field is defaulted from risk country and therefore indicates the risk country of the participation. It is used for statistical reasons and allows the bank to evaluate the country risk that is reduced by entering into an participation contract.

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 key of the fasttrack definition, which was used to create this 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 specifies the business module of the underlying contract.

This field holds the undertaking type of the guarantee or standby L/C. The codetable is identical as in GID.GARTYP except for Direct Pay.

This field indicates whether or not partial shipments (shipment in more than one lot) are allowed under the contract. Other conditions must be stated elsewhere in the message.

This field indicates whether or not transshipment is allowed under the contract. Transshipment is the shipment of goods to an intermediate destination, from where they are transported to another destination. One reason for this is the change in the means of transport during shipment (e.g. from ship to road transport). Other conditions must be stated elsewhere in the message.

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.