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.procurement/M MatchPO

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


Contents

M_MatchPO

This table contains the following columns:

Name Nullable Data Type Description


Processed No CHAR (1) The Processed checkbox indicates that a document has been processed.
Updated No TIMESTAMP (7) The Updated field indicates the date that this record was updated.
C_InvoiceLine_ID Yes VARCHAR (32) The Invoice Line uniquely identifies a single line of an Invoice.
Qty No DECIMAL The Quantity indicates the number of a specific product or item for this document.
C_OrderLine_ID No VARCHAR (32) A unique identifier and a reference to a sales order line (product).
M_InOutLine_ID Yes VARCHAR (32) The Goods Shipment Line indicates a unique line in a Shipment document
UpdatedBy No VARCHAR (32) The Updated By field indicates the user who updated this record.
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.
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.

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.
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
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 No CHAR (1) When this field is set as 'Y' a process is being performed on this record.
M_MatchPO_ID No VARCHAR (32) The ID identifies a unique record
M_Product_ID No VARCHAR (32) Identifies an item which is either purchased or sold in this organization.
DateTrx No TIMESTAMP (7) The Transaction Date indicates the date of the transaction.

Columns

Processed



top


Updated



top


Invoice Line


Foreign key column to C_InvoiceLine table, (column: C_InvoiceLine_ID)

top


Quantity



top


Sales Order Line


Foreign key column to C_OrderLine table, (column: C_OrderLine_ID)

top


Goods Shipment Line


Foreign key column to M_InOutLine table, (column: M_InOutLine_ID)

top


Updated By


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

top


Created By


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

top


Creation Date



top


Active



top


Organization


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

top


Client


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

top


Posted


List values: All_Posted Status

The allowed values for this list are:

top


Process Now



top


Match PO


top


Product


Foreign key column to M_Product table, (column: M_Product_ID)

top


Transaction Date



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

Retrieved from "http://wiki.openbravo.com/wiki/ERP/3.0/Developers_Guide/Database_Model/org.openbravo.model.procurement/M_MatchPO"

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