View source | Discuss this page | Page history | Printable version   

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


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.

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

Columns

Active



top


Automatic Deposit



top


Automatic Payment



top


Automatic Receipt



top


Automatic Withdrawn



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


Created By


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

top


Creation Date



top


Description



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


Name


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


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


Payin_Allow



top


Payin_Deferred



top


Payin_Execution_Process_ID


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

top


Payin_Execution_Type


List values: Payment Execution Type

The allowed values for this list are:

top


Payin_IsMulticurrency



top


Payment Method



top


Payout_Allow



top


Payout_Deferred



top


Payout_Execution_Process_ID


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

top


Payout_Execution_Type


List values: Payment Execution Type

The allowed values for this list are:

top


Payout_IsMulticurrency



top


Updated



top


Updated By


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

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


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


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 4,308 times. This page was last modified on 14 March 2023, at 04:12. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.