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/C Remittance Type

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

C_Remittance_Type

This table contains the following columns:

Name Nullable Data Type Description


C_Remittance_Type_ID No VARCHAR (32) The remittance type defines the properties the remittance has.
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.
IsActive No 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.

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.
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.
Consolidate No CHAR (1) When a remittance type is consolidated it will be created a cancel settlement from the debt/payments in the remittance and another one with the amount being the sum of all debt/payments.
Status_To Yes VARCHAR (60) Is the status that debt payment has taken.
Paymentruleconsolidated Yes VARCHAR (60) Is the payment rule that will be applied for the consolidated debt/payments.
Status_Returned Yes VARCHAR (60) The returned status is the status that will be taken by the debt/payment when it is returned.
IsReceipt Yes CHAR (1) Indicated a sales transaction (Accounts Receivable if Receipt=Y) or a purchase transaction (Accounts Payable if Receipt=N).

Columns

Remittance Type



top


Client


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

top


Organization


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

top


Active



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


Name


top


Consolidate



top


Final Status



List values: C_DP_Management_Status

The allowed values for this list are:

top


Payment Rule Consolidated



List values: All_Payment Rule

The allowed values for this list are:

top


Returned Status



List values: C_DP_Management_Status

The allowed values for this list are:

top


Receipt



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/C_Remittance_Type"

This page has been accessed 908 times. This page was last modified on 1 December 2016, at 02:15. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.