BTD - Document Set under Transfer L/C - Data

BTD is the main data table for the Document Set under Transfer L/C contract.
All technical important fields have to be defined here.
Large text blocks should be defined in BTT.

/

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 BTD. The field INR is used to enable links from other tables to this table. It also links the two tables BTD and BTT 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 subcontract which has been created for the set of documents received from 2nd beneficiary.

This field contains the reference number of the subcontract created for the set of documents received from 2nd beneficiary.

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 contains the external name of the selected set of documents presented under the transfer.

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.

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

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.

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 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 type of the parent contract.

This field contains the type of the parent contract.

This field contains the internal unique ID of the parent contract.

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

This field specifies the date on which the exchange documents (such as commercial invoice) of the first beneficiary side (PRP) have been received by the bank using the application (date of the actual receipt stamp, NOT date of customer order - that is ORDDATBE1). This field should be entered when documents are received from the first beneficiary side in transaction BTTDCK.

This field specifies the date on which the exchange documents (such as the commercial invoice) of the first beneficiary side were received by the bank using the application (date of the actual receipt stamp, NOT date of customer order - that is 'Order Date (1st Beneficiary)'). This field should be entered when documents are received from the first beneficiary side in the transaction 'Receiving Documents from 1st Beneficiary'.

This field contains the date of shipment as per transport document presented.

This field contains the date of shipment as per the transport document presented.

This date is set when an Advice of Payment (incoming MT754) has been received ( e.g. in TRN LTTDAV).

This date is set when an Payment Advice (incoming MT754) has been received.

This field specifies the date when the documents under the transfer are due for payment.

This field contains a fixed maturity date for the set of documents presented.

This field contains the type of documents presented under the Transfer L/C.

This field contains a list to select the type of the document presentation.

This date is set when an Advice of Discrepancy (incoming MT750) has been received ( e.g. in TRN LTTDAV).

This date is set when an Advice of Discrepancy (incoming MT750) has been received.

This field holds the version counter to keep track of the version history of an BTD 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 specifies if documents are sent on approval basis, meaning that discrepant documents are received which the applicant may pay or reject.

Check this box if documents are to be handled on approval basis.

This field specifies if the documents are handled free of payment, meaning that the documents are presented to the applicant without him having to pay for them. In German, this is called “Dokumente ohne Zahlung/wertfrei aushändigen”.

This field specifies whether documents are handled free of payment, i.e. whether they are presented to the applicant without the applicant having to pay for them.

This field is set to a non-empty value, if the document set holds more than one tenor.

This field is set to a non-empty value, if the document set holds more than one tenor.

This field specifies the date of the incoming cover letter received from the second beneficiary side (PRB). The documents can be presented by the second beneficiary directly or via a second advising bank (refer to default BTDGRP\REC\DOCPRBROL).

This date should be entered when the receipt of second beneficiary documents is logged in transaction LTTDCK. If necessary, the date can be corrected in BTTDRV.

This field specifies the date the incoming cover letter was received from the second beneficiary side. The documents can be presented by the second beneficiary directly or via a second advising bank.

This date should be entered when the receipt of second beneficiary documents is logged in transaction 'Receiving Documents from 2nd Beneficiary'. If necessary, the date can be corrected in 'Receive Documents'.

Role of the party which presented the documents.

Role of the party which presented the documents.

This field specifies the debit party who is paying the document set (e.g. Issuing bank resp. their customer who is the applicant of the L/C).

This field specifies the party to be debitted, i.e. the party responsible for paying the document set (e.g. the issuing bank or their customer, who is the applicant of the L/C).

This checkbox enables the banks to decide whether they want to use a 'slim' version of TRN LTTDCK (Receiving Documents from 2nd Beneficiary) where only minimal information is entered (→ This function is preferred by larger banks). Smaller banks use TRN LTTDCK to enter document details, discrepancies and instructions. When the checkbox is set to 'not empty' the relevant additional panels are visible.

This checkbox allows banks to decide whether they want to use a 'slim' version of transaction 'Documents received', where only minimal information is entered.

This function is preferred by larger banks. Smaller banks use the 'Documents received' transaction to enter details, discrepanies, instructions and shipping details. If the checkbox is checked, relevant additional panels are visible.

This flag specifies that documents are taken up for payment, acceptance, negotiation. The selection made in this field strongly influences the available processing options in BT. The flag is used in transaction BTTPAY in order to pay sight documents or to book in liability for usance documents.

This flag specifies that documents are taken up for payment, acceptance, negotiation. The selection made in this field strongly influences the processing options available in the BT (business sector Back-to-Back-L/C).

This flag is used in the BTTPAY transaction to pay sight documents or to book the liability for usance documents.

This field contains the currency of the total amount of the MT750 message to be remitted to the sender of the message. As this field is required in other transactions lateron (outgoing MT752 in BTTPAY), the field is stored here.

This field contains the currency of the total amount of the MT750 message to be remitted to the sender of the message. As this field is required in subsequent transactions (outgoing MT752), the field is stored here.

This field contains the total amount of the MT750 message to be remitted to the sender of the message. As this field is required in other transaction lateron (outgoing MT752 in BTTPAY), the field is stored here.

This field contains the total amount of the MT750 message to be remitted to the sender of the message. As this field is required in subsequent transactions (outgoing MT752), the field is stored here.

This field is necessary in case an Advice of Payment (MT754) is received under the L/C where TAG 34A has been specified. According to SWIFT regulations, TAG 34A can contain a value date, being the date when the document set should be paid or has been paid. The information received is stored in this field.

This field is necessary if an Advice of Payment (MT754) is received under the L/C where TAG 34A has been specified. According to SWIFT regulations, TAG 34A can contain a value date, i.e. the date when the document set should be paid or has been paid. The information received is stored in this field.

This field specifies if documents have been advised via incoming Payment Advice (e.g. MT754) or Advice of Discrepancy (e.g. MT750).

This field specifies if documents have been advised via incoming Payment Advice (e.g. MT754) or Advice of Discrepancy (e.g. MT750).

The current document set status is stored in this field. This field is set via default in the panel module.

The current status of the document set is stored in this field.

This field specifies the date on which documents of the second beneficiary side (PRB) have been received by the bank using the application (date of the actual receipt stamp, NOT date of customer order - that is ORDDATBE2). This field should be entered when documents are received from the second beneficiary side in transaction LTTDCK.

This field specifies the date on which documents of the second beneficiary side were received by the bank using the application (date of the actual receipt stamp, NOT date of customer order - that is 'Order Date (2nd Beneficiary)'). This field should be entered when documents are received from the second beneficiary side in transaction 'Receiving Documents from 2nd Beneficiary'.

This field specifies the presenting party on the 1st beneficiary side. In most cases, the exchange documents will be presented by the first beneficiary directly, but in some cases another bank might be involved (PRP).

This field specifies the presenting party on the 1st beneficiary side. In most cases, the exchange documents are presented by the first beneficiary directly, in other cases, however, another bank may be involved.

This field specifies the date of the incoming cover letter received from the first beneficiary side (PRP). The documents can be presented by the first beneficiary directly or via a second advising bank (refer to default BTDGRP\REC\DOCPRBROLBE1).

This date should be entered when the exchange documents (e.g. commercial invoice) of the first beneficiary are received and logged via transaction BTTDCK. If necessary, the date can be corrected in BTTDRV.

This field specifies the date the incoming cover letter was received from the first beneficiary side. The documents can be presented by the first beneficiary directly or via a second advising bank.

This date should be entered when the exchange documents (e.g. commercial invoice) of the first beneficiary are received and logged via transaction 'Receive Documents from 1st beneficiary'. If necessary, the date can be corrected in 'Receive Documents'.

This field specifies the date on which the bank using the application presents the documents to the L/C issuing bank. The presentation date should be set in transaction BTTSND or BTTPAY.

This field specifies the date on which the bank using the application presents the documents to the L/C issuing bank. The presentation date should be set in transaction 'Sending Documents' or 'Send and Settle Documents'.

When this flag is set, Documents to BE1 are returned.

When this flag is set, documents to first beneficiary are returned.

When this flag is set, Documents to BE2 are returned.

When this flag is set, documents to second beneficiary are returned.

Checkbox to trigger the outbooking of liability in case that documents are to be sent on approval basis. When set to a nonspace value the liability of the main contract is already booked out (or will be booked out in the transaktion setting this flag)

Triggers the booking of a liability if documents are to be sent on approval basis.

This field can be used to send the documents (e.g. Document Presentation 1st/ 2nd mail) to another address than the payer of documents (DOCPYRROL).

This field can be used to send the documents (e.g. document presentation 1st/ 2nd mail) to an address other than that of the payer of documents.

This flag is used to indicate that documents shall be sent to another address. The address is selected in DOCROL.

If LEDGRP\REC\APLBNKDIRSND was set under the LE, this field is defaulted accordingly.

This checkbox can be used to indicate that documents are to be sent to another address. The address is selected in 'Receiver of Documents'.

If 'Send Directly to Applicant's Bank' was set under the LE, this field is defaulted accordingly.

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.

Contains the reference number for customer negotiation.

Contains the reference number for customer negotiation.