BPD - Advance Data

BPD is the main data table for the Advance contract.
All technical important fields have to be defined here.
Large text blocks should be defined in BPT.

/

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 BPD. The field INR is used to enable links from other tables to this table. It also links the two tables BPD and BPT 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 financing.

This field contains the reference number of the subcontract created during the initiating process of a purchase transaction to either purchase or discount a set of documents.

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 contract amount and main party and cannot be modified by the user.

This field holds the displayed descriptive name of the parent contract.

This field holds the descriptive name of the parent contract.

This field holds the reference of the parent contract.

This is the reference number of the parent 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 maturity date of the documents.

This field contains the maturity date for the documents.

This field holds the date until interest has already been calculated.

This field contains maturity date of selected tenor.

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 field holds the version counter to keep track of the version history of a BPD 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 internal unique ID of the parent contract.

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

This field holds the INR of forfaiting contract if the contract is linked to a purchase agreement.

It is set in the transaction creating the BP (usually BPTOPN) if a purchase agreement is selected and used in following transactions for accessing it.

This field contains the INR (internal unique ID) of the forfaiting contract if this contract is linked to a purchase agreement.

It is set in the transaction that generates the advance (generally BPTOPN) if a purchase agreement was selected and used in the following transactions for access.

This field contains the type of the parent contract.

This field contains the type of the parent contract.

This field holds the margin applied to an advance.

This field contains the margin applied to an advance.

This field holds the number of days for which interest are to be calculated.

The field contains the number of days for interest calculation. These are calculated based on the difference between the due date minus the opening Date.

This field holds the type of the financing.

This field holds the type of the financing

This field contains the financed portion in percent of the underlying parent contract.

If no parent contract is selected the value is 100.00 PCT

This field contains the financed portion in percent of the underlaying parent contract.

If no parent contract is selected the value is 100.00 PCT

This field holds the rate definition used for the calculation of the interest of the selected finance contract.

This field holds the rate definition used for the calculation of the interest of the selected finance contract.

If checkbox is filled, costumer wants bank to pay supplier on their behalf.

If checkbox is checked, the costumer wants the bank to pay the supplier on their behalf.

Contract status flag. If not empty, contract is reserved. That means, only a few basic fields have to be filled in. Visible on BPTP in BPTPOP and INFBPD. Invisible in all other transactions.

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 an Advance' (BPTPOP) and 'Info Advance' (INFBPD). Invisible in all other transactions.

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 contains the drawdown method irrespective of the special type of financing.

This field further specifies the type of the underlying financing/ advance.

This field further specifies the type of the underlying financing/ advance.

This is the earliest date on supporting documents (bill of exchange or invoice) for bill under credit / usance terms.

The Start Date of a Bankers Acceptance is calculated as the earliest invoice date of all registered invoices.

This field contains the standard tenor for the party to whom an advance is made. If this field is not completed manually, it will be filled with the maximum tenor permissible for the financing type 'Bankers Acceptance' of the party concerned.

Total amount advanced under a bankers' acceptance

Currency of the converted amount. This currency is usually set from SYSCUR. This field is an optional field and may be empty, if no converted amount of the specific balance is known.

Currency of the converted amount. This currency is usually set from SYSCUR. This field is an optional field and may be empty, if no converted amount of the specific balance is known.

Date of the transport document

This is the 6-digit number on the BA draft.

This is the 6-digit number on the BA draft.

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.

This field specifies whether recourse can be claimed from the advanced party.

This field specifies whether recourse can be claimed from the advanced party.

This field specifies the type of risk involved in the underlying financing/ advance.

This field specifies the type of risk involved in the underlying financing/ advance.

This field hold the current begin date for interest calculation

The date from which the interest is calculated.

This field hold the current end date for interest calculation

Date until which interest are calculated.

If, checked, the current TR is a roll over tr. That means, that the interest rate is adjusted from time to time.

When a loan is marked as a “Roll-Over Financing”, the interest period is independent from the validity of the financing. Interest is then calculated for the interest period recorded at the total interest rate valid for the period in question. Upon expiry of the interest period, the contract is adjusted in the amendment transaction with the details of the following interest period.

Costs for refinanzing in the market

Costs of procuring the funds on the money market.

Costs for keeping liquidity

The liquidity costs refer to the costs of the bank which occur in order to provide the neccessary liquidity.

Our Share of Interest

The share of the overall interest rate booked as income in the bank's books. Is pre-defined and noted by rate type possible special terms and conditions.

Additional days for interest calculation

Additional Grace Days used for interest calculation.

This field is defaulted with the country code of the sender of the L/C and therefore indicates the risk country of the L/C. It is used for statistical reasons and allows the advising bank to evaluate the country risks it may have entered by advising/confirming the L/C.

This field is defaulted with the country code of the advanced party (role FIA) or the final beneficiary if the role BEF is set under the contract. It is used for statistical reasons and allows the bank to evaluate the country risks it may have entered by opening the advance.

Mark, if Assignment of Proceeds had been entered for this contract.

Mark, if Assignment of Proceeds had been entered for this contract.

Marks if there is a Participation Sold defined under this contract.

Marks if there is a Participation Sold defined under this contract.

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.

If a faclility had been selected this field contains the INR pointer to this facility in database table FAC.

If a faclility had been selected this field contains the INR pointer to this facility in database table FAC.

Contains the amount of selected tenor(s).

Contains the amount of selected tenor(s).

Additional penalty interest rate in case advance contract becomes past due

Additional penalty interest rate in case advance contract becomes past due