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 PaymentMethod

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_PaymentMethod

This table contains the following columns:

Name Nullable Data Type Description


Fin_Paymentmethod_ID No VARCHAR (32)
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
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.
Created No TIMESTAMP (7) The Created field indicates the date that this record was created.
Createdby No VARCHAR (32) The Created By field indicates the user who created this record.
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.
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.

Name No VARCHAR (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.
Description Yes VARCHAR (255) A description is limited to 255 characters.
Uponreceiptuse Yes VARCHAR (60) Account used upon receipt
Upondeposituse Yes VARCHAR (60) Account used upon deposit
Inuponclearinguse Yes VARCHAR (60) Account used upon clearing
Uponpaymentuse Yes VARCHAR (60) Account used upon payment
Uponwithdrawaluse Yes VARCHAR (60) Account used upon withdrawal
Outuponclearinguse Yes VARCHAR (60) Account to be used upon clearing
Payin_Allow No CHAR (1) Sets that Payment Ins are allowed.
Payout_Allow No CHAR (1) Sets that Payment Ins are allowed.
Payin_Execution_Type No VARCHAR (60) Type of Payment Execution for Payment In flow.
Payout_Execution_Type No VARCHAR (60) Type of Payment Execution for Payment Out flow.
Payin_Execution_Process_ID Yes VARCHAR (32) Execution process to be used in the Payment In flow
Payout_Execution_Process_ID Yes VARCHAR (32) Execution process to be used in the Payment Out flow
Payin_Deferred No CHAR (1) Sets that the Execution Process is deferred in the Payment In flow.
Payout_Deferred No CHAR (1) Sets that the Executiion Process is deferred in the Payment In flow.
Automatic_Receipt No CHAR (1) Automatically create the receipt when the invoice is completed.
Automatic_Payment No CHAR (1) Automatically create the payment when the invoice is completed.
Automatic_Deposit No CHAR (1) Automatically deposit the payment when it is processed.
Automatic_Withdrawn No CHAR (1) Automatically withdrawn the payment when it is processed.
Payin_IsMulticurrency No CHAR (1) Allow Receipt of Payments in Multiple Currencies
Payout_IsMulticurrency No CHAR (1) Allow withdrawl of Payments in Multiple Currencies

Columns

Payment Method



top


Client


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

AD_Client.AD_Client_ID in (@#User_Client@)

top


Organization


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

(@AD_Client_ID@='0' AND AD_Org.AD_Org_ID='0') OR (@AD_Client_ID@!='0' AND ((AD_Org.AD_Client_ID IN (@#User_Client@) AND AD_Org.AD_Org_ID IN (@#User_Org@)) OR AD_Org.AD_Org_ID='0' AND AD_Org.IsSummary='N'))

top


Creation Date



top


Created By


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

top


Updated



top


Updated By


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

top


Active



top


Name


top


Description



top


Upon Receipt Use



It has a validation "Payment IN Accounts", with the following code

AD_Ref_List.Value IN ('INT', 'DEP', 'CLE')

List values: New Financial Flows Accounts

The allowed values for this list are:

top


Upon Deposit Use



It has a validation "Payment IN Accounts", with the following code

AD_Ref_List.Value IN ('INT', 'DEP', 'CLE')

List values: New Financial Flows Accounts

The allowed values for this list are:

top


IN Upon Clearing Use



It has a validation "Payment IN Accounts", with the following code

AD_Ref_List.Value IN ('INT', 'DEP', 'CLE')

List values: New Financial Flows Accounts

The allowed values for this list are:

top


Upon Payment Use



It has a validation "Payment OUT Accounts", with the following code

AD_Ref_List.Value IN ('WIT', 'INT', 'CLE')

List values: New Financial Flows Accounts

The allowed values for this list are:

top


Upon Withdrawal Use



It has a validation "Payment OUT Accounts", with the following code

AD_Ref_List.Value IN ('WIT', 'INT', 'CLE')

List values: New Financial Flows Accounts

The allowed values for this list are:

top


OUT Upon Clearing Use



It has a validation "Payment OUT Accounts", with the following code

AD_Ref_List.Value IN ('WIT', 'INT', 'CLE')

List values: New Financial Flows Accounts

The allowed values for this list are:

top


Payin_Allow



top


Payout_Allow



top


Payin_Execution_Type


List values: Payment Execution Type

The allowed values for this list are:

top


Payout_Execution_Type


List values: Payment Execution Type

The allowed values for this list are:

top


Payin_Execution_Process_ID


Foreign key column to FIN_Pay_Exec_Process table, (column: FIN_Pay_Exec_Process_ID)

top


Payout_Execution_Process_ID


Foreign key column to FIN_Pay_Exec_Process table, (column: FIN_Pay_Exec_Process_ID)

top


Payin_Deferred



top


Payout_Deferred



top


Automatic Receipt



top


Automatic Payment



top


Automatic Deposit



top


Automatic Withdrawn



top


Payin_IsMulticurrency



top


Payout_IsMulticurrency



top


Other Info

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_PaymentMethod"

This page has been accessed 1,084 times. This page was last modified on 1 February 2016, at 14:31. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.