FBD - Finance Base Document

FBD is the data table for the Finance Base Document data.

/

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 FBD. The field INR is used to maintain links from other tables into this table.

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.

Each FBD entry is related to one party called Buyer. This is the INR of the related party Buyer.

Each FBD entry is related to one party called Supplier. This is the INR of the related party Supplier.

Unique internal ID of finance program. Note, this is currently not in use.

Defines, which type of document this entry represents.

This field holds the external key to identify a Finance Base Document. This field is depending on the TYP the invoice number, the debit-/credit-Note number etc.

Currency of the document amount. Example: If the document selected is invoice, the currency of the invoice amount.

This amount reflects the positive amount of a invoice or a debit note. In case of credit notes the positive amount reflects the amount to be deducted. Thus typically no negative amounts are allowed in the field. For POA the amount is zero as it reflects the payment on account only, not a payment of the supplier.

Currency of freight amount (equal CUR)

The amount of freight rececived from EDI or entered by the user in the invoice lines dialog. The amount is reduced from the total amount of invoice lines for credit notes to get the documnet amount and added otherwise.

Currency of Amount Paid (same as CUR es soon as there is a amount repaid)

Total amount paid by the buyer set by the repayment transaction. Availaable and maintained for easier access to the total amount repaid in later transactions. It may be amended in several repayments. The amounts for each repayments are stored in the FBL-links for the repayments.

This is the date of the represented document.

Due date of the document. This is usually the maximum time the amount may be financed.

Creation date when the pool entry has been created.

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

Date of last change in transaction. Needed for SOT.

R Registered ; First entered on the system C Approved ; Buyer has Approved it. They will repay it O Offered; Sent to Supplier to see if they wish it to be funded F Financed; Funded D Closed ; Funding Repaid P Partially Paid ; Some of the whole has been repaid V Dispute resolved ; Was in Dispute , now not I In Dispute ; There is an issue with this document A Payment on Account; Special value; Buyer has Overpaid U Unconfirmed; Will not be funded.

INR of the object within the table, defined in OBJTYP. If there is no existing object this field might be empty.

Usually this field contains the INR of the connected IA contract.

Type of object the document refers to. Usually this is the table the object is associated to. The field should be used together with OBJINR.

Usually this field contains 'IAD'.

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.

Date Dispute entered

This is the date which is set, when the document is marked to Status “In Dispute”. A document is set to “In Dispute”, if the buyer does not agree to pay a particular document.

Description of reason of dispute.

When the buyer does not agree to pay any document, it is necessary to update a reason for the disagreement while setting the status to “In Dispute”.

Denotes if the documents are grouped or not

Optional number of purchase order

Description of documents received from the incoming funding requests.

This field holds buyer's payment reference number received from the incoming funding request.

Unique internal ID of the offer contract before they are aggregated or grouped.

Unique internal ID of the associated incoming funding request file.

Displays the sold amount

Displays the sold currency

Specifies the request time of the incoming funding request file.

This field specifies the request sequence number in the incoming funding request file.

This field specifies the funding request number in the incoming funding request file.

This field specifies the document number sequence from the incoming funding request file.

This field holds the version counter to keep track of the version history of a FBD 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 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.