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

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_Payment_Detail

This table contains the following columns:

Name Nullable Data Type Description


Fin_Payment_Detail_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.
Fin_Payment_ID No VARCHAR (32) Payment event
Amount No DECIMAL
Refund Yes CHAR (1)
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.

Writeoffamt Yes DECIMAL The Write Off Amount indicates the amount to be written off as uncollectible.
C_Glitem_ID Yes VARCHAR (32) General ledger item.
Isprepayment No CHAR (1) When the payment is created against order it is considered to be a prepayment

Columns

Payment Details



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


Fin_Payment_ID

Foreign key column to FIN_Payment table, (column: Fin_Payment_ID)

top


Amount



top


Refund



top


Active



top


Write-off Amount



top


G/L Item


Foreign key column to C_Glitem table, (column: C_Glitem_ID)

top


Isprepayment



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


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

This page has been accessed 1,116 times. This page was last modified on 5 August 2014, at 14:00. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.