View source | Discuss this page | Page history | Printable version   
Toolbox
Main Page
Upload file
What links here
Recent changes
Help

PDF Books
Add page
Show collection (0 pages)
Collections help

Search

ERP/2.50/Developers Guide/Database Model/org.openbravo.model.financialmgmt.payment/FIN BankStatement

Contents

FIN_BankStatement

Bank statements loaded for the given financial account

This table contains the following columns:

Name Nullable Data Type Description
FIN_Bankstatement_ID NVARCHAR2(32)Bank statements related to a financial account
AD_Client_ID NVARCHAR2(32)Client for this installation.
AD_Org_ID NVARCHAR2(32)Organizational entity within client
Created NDATEThe date that this record is completed.
Createdby NVARCHAR2(32)User who created this records
Updated NDATEx not implemented
Updatedby NVARCHAR2(32)User who updated this records
Isactive YCHAR(1)A flag indicating whether this record is available for use or de-activated.
FIN_Financial_Account_ID NVARCHAR2(32)Financial account used to deposit / withdrawal money such as bank accounts or petty cash
DocumentNo NNVARCHAR2(30)An often automatically generated identifier for all documents.
Name NNVARCHAR2(60)A non-unique identifier for a record/document often used as a search tool.
Notes YNVARCHAR2(255)null
C_Doctype_ID NVARCHAR2(32)A value defining what sequence and process setup are used to handle this document.
Filename YNVARCHAR2(255)null
Importdate NDATEImport date of the bank file
Statementdate NDATEThe date the transaction is carried out and registered in the cash journal.
FIN_Reconciliation_ID YVARCHAR2(32)Reconciliation events related to the financial account
Processing YCHAR(1)A request to process the respective document or task.
Processed NCHAR(1)A confirmation that the associated documents or requests are processed.
Posted NVARCHAR2(60)An accounting status button that indicates if the transaction has already been posted to the general ledger or not.

Other Info

Check constraints

These are the check constraints for this table:

top

Indexes

These are the indexes for this table (for each index there is a list of all the columns included within it):

Unique

top

Columns

FIN_Bankstatement_ID

Bank statements loaded for the given financial account

top

Client

Foreign key column to AD_Client table, (column: AD_Client_ID)


Validation Rule AD_Client Trx Security validation: null. With the following code:

 
AD_Client.AD_Client_ID<>'0'

top

Organization

Foreign key column to AD_Org table, (column: AD_Org_ID)


Validation Rule AD_Org Trx Security validation: null. With the following code:

 
AD_Org.AD_Org_ID<> '0' AND AD_Org.IsReady='Y'

top

Creation Date

The Created field indicates the date that this record was created.

top

Created By

Foreign key column to AD_User table, (column: AD_User_ID)

top

Updated

The Updated field indicates the date that this record was updated.

top

Updated By

Foreign key column to AD_User table, (column: AD_User_ID)

top

Active

There are two methods of making records unavailable in the system: One is to delete the record, the other is to de-activate the record. A de-activated record is not available for selection, but available for reporting. There are two reasons for de-activating and not deleting records:
(1) The system requires the record for auditing purposes.
(2) The record is referenced by other records. E.g., you cannot delete a Business Partner, if there are existing invoices for it. By de-activating the Business Partner you prevent it from being used in future transactions.

top

Account

Foreign key column to FIN_Financial_Account table, (column: Fin_Financial_Account_ID)

top

Document No.

The document number is usually automatically generated by the system and determined by the document type of the document. If the document is not saved, the preliminary number is displayed in "<>". If the document type of your document has no automatic document sequence defined, the field will be empty when creating a new document. This is for documents which usually have an external number (like vendor invoice). If you leave the field empty, the system will generate a document number for you. The document sequence used for this fallback number is defined in the "Document Sequence" window with the name "DocumentNo_<TableName>", where TableName is the actual name of the table inside the database (e.g. C_Order).

Callout: SL_AdvPayment_Document

This element is linked to a callout.

Document number generation.

It is implemented by org.openbravo.erpCommon.ad_callouts.SL_AdvPayment_Document Java class.

top

Name

A more descriptive identifier (that does need to be unique) of a record/document that is used as a default search option along with the search key (that is unique and mostly shorter). It is up to 60 characters in length.

top

Notes

top

Document Type

Foreign key column to C_Doctype table, (column: C_DocType_ID)


Validation Rule C_DocType - Bank Statement File: C_DocType - Bank Statement File Validation. With the following code:

 
C_DocType.DocBaseType IN ('BSF') AND AD_ISORGINCLUDED(@AD_Org_ID@,C_DocType.AD_Org_ID, @#AD_Client_ID@) <> '-1' AND C_DocType.AD_Client_ID=@#AD_Client_ID@

Callout: SL_AdvPayment_Document

This element is linked to a callout.

Document number generation.

It is implemented by org.openbravo.erpCommon.ad_callouts.SL_AdvPayment_Document Java class.

top

File Name

top

Importdate

Import date of the bank file

top

Transaction Date

The Statement Date field defines the date of the statement being processed.

top

FIN_Reconciliation_ID

Foreign key column to FIN_Reconciliation table, (column: FIN_Reconciliation_ID)

top

Process Now

When this field is set as 'Y' a process is being performed on this record.

top

Processed

The Processed checkbox indicates that a document has been processed.

top

Posted

An accounting status button that indicates if the transaction has already been posted to the general ledger or not. When doing the accounting manually this button can be used to post or unpost the transaction from the general ledger by hand.

top

Retrieved from "http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Database_Model/org.openbravo.model.financialmgmt.payment/FIN_BankStatement"

This page has been accessed 1,516 times. This page was last modified on 2 July 2011, at 20:57. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.