LTD - Transfer L/C Data

LTD is the main data table for the Transfer L/C contract.
All technical important fields have to be defined here.
Large text blocks should be defined in LTT.

/

INR

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 LTD. The field INR is used to enable links from other tables to this table. It also links the two tables LTD and LTT as associated entries hold the same INR.

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 transfer being established. The reference number can have a maximum size of 16 characters. This field can be used to search for any transfer from the database.

This field contains the reference number of the transferrable L/C. The reference can be up to 16 characters long. This field can be used to search for any transferrable L/C from the database.

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 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 date field holds the date when the entry was physically added to the database. This may happen when opening the contract, when reserving the reference number or when, for other reasons, a contract is added to the database.

This date field identifies the date the entry was physically added to the database.

This checkbox activates the Parties panel which enables the storage of additional addresses for the transfer.

This field contains the date of the last amendment which has been processed under the transfer L/C.

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 counts the number of all initiated amendments under the Transfer L/C. An amendment is initiated when the first transaction of an amendment is finally stored.

The field is technically incremented after loading of the contract in init of all amending transactions (lttamr, lttram, lttame), if not an already existing amendment is further processed.

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 transfer L/C is available by sight payment, deferred payment, acceptance, negotiation or mixed payment.

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

This field indicates the bank authorized to pay, accept, negotiate or incur a deferred payment for the transfer L/C.

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 field defines whether the charges and commissions of the issuing bank are borne by the applicant side (=“U”), by the beneficiary side (=“B”) or others. According to the selection entered in this field, the roles in the second settlement grid (own commission/charges) are defaulted.

This field defines whether the fees and commissions of the bank using using the application is to be borne by the 1st beneficiary or 'bourne by client' (='U'), of the advising bank or 'bourne by abroad' (='B') or by other parties. Depending on the selection made in this field, the roles in the second settlement table (own commission / fees) are proposed.

Meaning 'borne by abroad': If, in the fee settlement field, 'borne by abroad' was selected or if the field is not completed, then the own fees will be proposed in the settlement to the debit of the 1st beneficiary.

Meaning of 'borne by abroad': Own fees in the settlement are proposed to the debit of the advising bank or the 2nd beneficiary.

Meaning of 'Others': No role is proposed on the fees in the settlement panel.

This fields holds the closing date of a contract. If this field is set, the contract is closed and may no longer be used for transaction processing of business transactions. The date specifies the date when the closing took place.

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 confirmation instructions for the receiver of the transfer L/C, e.g. the advising bank (ADV). According to SWIFT regulations, one of the following code words must be selected: “Without”, “May add” or “Confirm”.

This field contains the confirmation instructions for the receiver of the transfer L/C, e.g. the advising bank (ADV). According to SWIFT regulations, one of the following code words must be selected: “Without”, “May add” or “Confirm”.

This date field specifies when the transfer L/C expires.

This field contains the date the transfer L/C expires. The date cannot be after the original expiry date.

This field contains the place of expiry of the transfer L/C.

This field contains the place of expiry of the transfer L/C.

This field specifies the type of the transfer L/C according to UCP.

This field contains the type of transfer to be processed.

This field further qualifies the documentary credit amount and becomes important when checking documents presented under the transfer L/C. If the code “not exceeding” is used, no amount tolerance is allowed. If the code “according to UCP” is used, allowances in credit amount are granted according to what is stipulated in article 39 of the UCP.

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 relative to the transfer L/C amount as a percentage plus that amount. The total amount may not exceed the total amount of original L/C including all other transfers L/C's.

The total amount may not exceed the total amount of original L/C including all other transfers. 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 relative to the transfer L/C amount as a percentage minus that 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 a 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.

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 who is responsible for handling this contract. This field is an optional field. Within Demobank it is initially filled with the user ID of the user creating/opening the contract.

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

This field contains information regarding additional identification of the account used for the reimbursement authorization for the transfer.

This field contains information regarding additional identification of the account used for the reimbursement authorization for the transfer.

This field contains the charges code regarding the charges of the reimbursement bank.

This field contains the charges code regarding the charges of the reimbursement bank.

This checkbox has to be enabled in case advising bank of the transfer should be allowed to claim reimbursement against documents presented by 2nd beneficiaries. If enabled reimbursing bank instructions have to be completed.

This checkbox has to be checked if the bank advising the transfer is to be allowed to claim reimbursement against documents presented by the 2nd beneficiary. If checked, instructions to the reimbursing bank have to be completed.

This field specifies the latest date for loading on board/dispatch/taking in charge. This date may not be later than the expiry date of the transfer L/C and the original conditions.

This field specifies the latest date for loading on board/dispatch/ transfer. This date cannot be later than the expiry date of the transfer L/C and the original conditions.

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

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 whether or not partial shipments are permitted under the transfer L/C.

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 or place of delivery to be indicated on the transport document.

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

This field specifies whether or not transshipments are permitted under the transfer L/C.

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 is defaulted with the country code of the receiver of the transfer L/C and therefore indicates the risk country of the L/C. It is used for statistical reasons in order to evaluate the country risks it has entered by issuing the transfer L/C.

This field is used to specify the country code for statistical purposes. This country code may be the same as that of the second beneficiary or a different country. The country code specified here is used to obtain country-based statistics.

This field counts the number of document sets which have been received (RCVDAT filled) from the second beneficiary under the transfer L/C. This number is not decreased when the document set is settled or closed.

This field counts the number of document sets which have been received from the second beneficiary under the transfer L/C. This number is not decreased when the document set is settled or closed.

This field counts the number of document sets which have been advised (e.g. via SWIFT MT 750 or MT754) to the issuing bank (OWN) but the physical documents have not been received yet (RCVDAT empty). When the physical documents are received (RCVDAT filled), the count of ADVNBR is decreased.

This field counts the number of document sets which have been advised (e.g. via SWIFT MT 750 or MT754) to the issuing bank (OWN) but the physical documents have not been received yet (date of receipt of documents is empty). When the physical documents are received (date of receipt of documents is filled), the count of number of advised utilizations is decreased.

This checkbox shows whether a Red/Green Clause is incorporated in the conditions of the transfer.

This checkbox shows whether a Red/Green Clause is incorporated in the conditions of the transfer.

This field holds the version counter to keep track of the version history of an LTD entry. The individual versions are controlled by entries in the SLG table.

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 INR of the export L/C on which this transfer L/C is based on.

This field contains the internal unique ID (INR) of the export L/C on which this transfer is based.

This flag indicates whether documents of the first beneficiary have already been received. Usually this flag is set, when documents of the second beneficiary are registered in TRN LTTDCK.

This flag indicates whether documents of the first beneficiary have already been received. Usually this flag is set, when documents of the second beneficiary are registered in transaction 'Receiving Documents from 2nd Beneficiary'.

This field specifies the port of loading or airport of departure to be indicated on the transport document.

This field specifies the port or airport of departure indicated on the transport document.

This field specifies the port of discharge or airport of destination to be indicated on the transport document.

This field contains the port or airport of destination, where the goods shipped under the L/C are unloaded. This is not necessarily the place of delivery.

This field specifies the rules the transfer L/C is subject to.

This field specifies the rules governing the contract.

This field specifies details to the applicable rules in case applicable rules is set to “any other rules”.

This field specifies details to the applicable rules in case applicable rules is set to “any other rules”.

This field specifies details to the rules the transfer L/C is subject to for reimbursements.

This field specifies the rules governing the reimbursement authorization.

This field contains the date of the original authorization to reimburse

This field contains the date of the original authorization to reimburse

This table is defined on entity level with separate entries for each entity. This field holds the EXTKEY 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 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 holds the INR of the transaction which opened the contract.

This field holds the INR of the transaction which opened/issued the contract.

Former LEDINR. Contains the INR of the parent contract

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

This field contains the type of the parent contract.

This field contains the type of the parent contract.

This field indicates whether or not partial shipments (shipment in more than one lot) are allowed under the L/C.

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 transshipments are allowed under the L/C. Transshipment (German “Umladung”) is the shipment of goods to an intermediate destination, and then from there to yet another destination. One reason for this is, that the means of transport can be changed during the journey (eg. from ship to road transport).

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.

This flag is used to indicate whether for this L/C a special payment condition for beneficiary is avaiable.

This flag is used to indicate whether for this L/C a special payment condition for beneficiary is avaiable.

This flag is used to indicate whether for this L/C a special payment condition for receiving bank is avaiable.

This flag is used to indicate whether for this L/C a special payment condition for receiving bank is avaiable.

This field contains the days of presentation period.

This field contains the days of presentation period.

This field contains details to the presentation period.

This field contains details to the presentation period.

Flag to activate assignment of proceeds panel.

Flag to activate assignment of proceeds panel.

Flag to activate participation sold logic.

Flag to activate participation sold logic.

Incoming retain the right to refuse amendments.

Incoming retain the right to refuse amendments.

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

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.

Introduced with Swift Release 2023 This field specifies the place of taking in charge (in case of a multimodal transport document), the place of receipt (in case of a road, rail or inland waterway transport document or a courier or expedited delivery service document), the place of dispatch or the place of shipment to be indicated on the transport document.

Introduced with Swift Release 2023 This field specifies the final destination or place of delivery to be indicated on the transport document.

Introduced with Swift Release 2023 This field specifies the port of loading or airport of departure to be indicated on the transport document.

Introduced with Swift Release 2023 This field specifies the port of discharge or airport of destination to be indicated on the transport document.

This flag is used to indicate whether for this L/C a special instructions from transferring bank (:78D: ) is available.