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.materialmgmt.cost/M Costing Algorithm

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.materialmgmt.cost


Contents

M_Costing_Algorithm

This table contains the following columns:

Name Nullable Data Type Description


M_Costing_Algorithm_ID No VARCHAR (32) Identifies a Costing Algorithm. Core distribution includes Average and Standard costing methods. Additional methods can be added using Extension Modules.
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 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.

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.
Description Yes NVARCHAR (2000) A description is limited to 255 characters.
Classname No VARCHAR (1000) The classname is used when generating a representation of the table in java (the entity or business object). The classname is the simplename of the class (so without the package name). Often the AD_Table.name can be used here. The combination of classname and package needs to be unique.

Columns

M_Costing_Algorithm_ID



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


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


Java Class Name



top


Other Info

Check Constraints

These are the check constraints for this table:

top

Back button.png   Back to org.openbravo.model.materialmgmt.cost

Retrieved from "http://wiki.openbravo.com/wiki/ERP/3.0/Developers_Guide/Database_Model/org.openbravo.model.materialmgmt.cost/M_Costing_Algorithm"

This page has been accessed 298 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.