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/3.0/Developers Guide/Database Model/org.openbravo.model.financialmgmt.payment/FIN BankStatement

This article is protected against manual editing because it is automatically generated from Openbravo meta-data. Learn more about writing and translating such documents.
Back button.png   Back to ERP/3.0/Developers Guide/Database Model/org.openbravo.model.financialmgmt.payment


Contents

FIN_BankStatement

This table contains the following columns:

Name Nullable Data Type Description


FIN_Financial_Account_ID No VARCHAR (32) Financial account used to deposit / withdrawal money such as bank accounts or petty cash
Isactive Yes CHAR (1) 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.

AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
Createdby No VARCHAR (32) The Created By field indicates the user who created this record.
Created No TIMESTAMP (7) The Created field indicates the date that this record was created.
DocumentNo No NVARCHAR (30) 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).
C_Doctype_ID No VARCHAR (32) The Document Type determines document sequence and processing rules
EM_APRM_Process_BS Yes VARCHAR (60)
EM_APRM_Process_BS_Force Yes VARCHAR (60)
FIN_Bankstatement_ID No VARCHAR (32) Bank statements loaded for the given financial account
FIN_Reconciliation_ID Yes VARCHAR (32) Reconciliation events related to the financial account
Filename Yes NVARCHAR (255)
Importdate No TIMESTAMP (7) Import date of the bank file
Name No NVARCHAR (60) 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.
Notes Yes NVARCHAR (255)
AD_Org_ID No VARCHAR (32) An organization is a unit of your client or legal entity - examples are store, department. You can share data between organizations.
Posted No VARCHAR (60) 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.
Processing Yes CHAR (1) When this field is set as 'Y' a process is being performed on this record.
Processed No CHAR (1) The Processed checkbox indicates that a document has been processed.
Statementdate No TIMESTAMP (7) The Statement Date field defines the date of the statement being processed.
Updated No TIMESTAMP (7) The Updated field indicates the date that this record was updated.
Updatedby No VARCHAR (32) The Updated By field indicates the user who updated this record.

Columns

Account


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

top


Active



top


Client


Foreign key column to AD_Client table, (column: AD_Client_ID) It has a validation "AD_Client Trx Security validation", with the following code

AD_Client.AD_Client_ID<>'0'

top


Created By


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

top


Creation Date



top


Document No.


Callout: SL_AdvPayment_Document

This column has a callout associated. Document number generation. It is implemented by [1] Java Class.

top


Document Type


Foreign key column to C_DocType table, (column: C_DocType_ID) It has a validation "C_DocType - Bank Statement File", 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 column has a callout associated. Document number generation. It is implemented by [2] Java Class.

top


EM_APRM_Process Bank Statement


List values: FIN_BankStatement Process Actions

The allowed values for this list are:

top


EM_APRM_Process Bank Statement Force


List values: FIN_BankStatement Process Actions

The allowed values for this list are:

top


FIN_Bankstatement_ID



top


FIN_Reconciliation_ID


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

top


File Name



top


Importdate



top


Name


top


Notes



top


Organization


Foreign key column to AD_Org table, (column: AD_Org_ID) It has a validation "AD_Org Trx Security validation", with the following code

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

top


Posted


List values: All_Posted Status

The allowed values for this list are:

top


Process Now



top


Processed



top


Transaction Date



top


Updated



top


Updated By


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

top


Other Info

Indices

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

top

Check Constraints

These are the check constraints for this table:

top

Back button.png   Back to org.openbravo.model.financialmgmt.payment

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

This page has been accessed 3,085 times. This page was last modified on 7 September 2020, at 01:58. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.