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 Rule

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_Rule

This table contains the following columns:

Name Nullable Data Type Description


M_Costing_Rule_ID No VARCHAR (32) Identifies a costing rule for cost calculation. The costing rule defines the algorithm to be used, the date is valid from and if warehouses are used as a cost dimension.
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.

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.
Datefrom Yes TIMESTAMP (7) The Date From indicates the starting date of a range.
ORG_Dimension No CHAR (1) If checked the costs have to be calculated by the legal entity of the transaction.
Warehouse_Dimension No CHAR (1) If checked the cost is calculated by the warehouse of the transaction
M_Product_ID Yes VARCHAR (32) Identifies an item which is either purchased or sold in this organization.
Dateto Yes TIMESTAMP (7) The Date To indicates the end date of a range (inclusive)
M_Product_Category_ID Yes VARCHAR (32) Identifies the category which this product belongs to. Product categories are used for pricing.
IsValidated No CHAR (1) Flag to determine that the record has been validated.
Process_Rule Yes CHAR (1) Validate and initialize the Costing Rule. It automatically creates and process the Close and Opening Physical inventories to overwrite an existing Costing Rule. If the instance is using the legacy engine costs it is mandatory to run the Cost Migration Process in advance with System Administrator role.
Backdatedtrxsfixed Yes CHAR (1) If checked Fix Backdated Transactions has been executed for the Costing Rule.
Backdatedtrxsfixedprocess Yes CHAR (1) Process that recalculates costs of backdated transactions until the given date.

Run process from Costing Rules window.

Fixbackdatedfrom Yes TIMESTAMP (7) Starting date in the costing rule to fix backdated transactions

Columns

Costing Rule



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) It has a validation "AD_Org Legal Entity", with the following code

exists (select 1 from ad_orgtype where ad_orgtype.ad_orgtype_id = ad_org.ad_orgtype_id and islegalentity='Y') AND IsReady='Y'

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


Costing Algorithm

Foreign key column to M_Costing_Algorithm table, (column: M_Costing_Algorithm_ID)

top


Starting Date


top


Organization Dimension



top


Warehouse Dimension



top


Product


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

top


Ending Date



top


Product Category


Foreign key column to M_Product_Category table, (column: M_Product_Category_ID)

top


Validated



top


Process_Rule



top


Backdated Transactions Fixed


Callout: SL_CostingRule_FixBackdated

This column has a callout associated. Callout to reset Fix Backdated From in Costing Rule window when the costing rule is nor marked as FIx Backdated It is implemented by [1] Java Class.

top


Fix Backdated Transactions



top


Fixbackdatedfrom



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

This page has been accessed 439 times. This page was last modified on 2 February 2015, at 14:07. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.