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/2.50/Developers Guide/Database Model/org.openbravo.model.manufacturing.transaction/MA WorkRequirement

Contents

MA_WorkRequirement

In this table it's defined the header of the requirement. here it's indicated for example the process plan.

This table contains the following columns:

Name Nullable Data Type Description
MA_Workrequirement_ID NVARCHAR2(32)An order authorizing the production of a specific product and product quantity.
AD_Client_ID NVARCHAR2(32)Client for this installation.
AD_Org_ID NVARCHAR2(32)Organizational entity within client
IsActive NCHAR(1)A flag indicating whether this record is available for use or de-activated.
Created NDATEThe date that this record is completed.
Createdby NVARCHAR2(32)User who created this records
Updated NDATEx not implemented
Updatedby NVARCHAR2(32)User who updated this records
Name YNVARCHAR2(60)A non-unique identifier for a record/document often used as a search tool.
MA_Processplan_ID NVARCHAR2(32)A guide stating how a certain item must move through the transformation process.
Quantity NNUMBERnull
Launchdate NDATEnull
StartDate NDATEA parameter stating when a specified request will begin.
EndDate NDATEA parameter stating when a specified request will end.
Closed NCHAR(1)null
Explote YCHAR(1)null
Processed YCHAR(1)The document has been processed
DocumentNo NNVARCHAR2(30)An often automatically generated identifier for all documents.
Explodephases NCHAR(1)null
Secondaryqty YNUMBER(10, 0)The number of Process Units required to be produced.
Secondaryunit YNVARCHAR2(40)The name of the main final product obtained by executing a process plan.
Conversionrate YNUMBERDefines the conversion between Quantity and Process Quantity

Other Info

Check constraints

These are the check constraints for this table:

top

Indexes

These are the indexes for this table (for each index there is a list of all the columns included within it):

Unique

top

Columns

Work Requirement

Indicates a work requirement.

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

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.

top

Creation Date

The Created field indicates the date that this record was created.

top

Created By

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

top

Updated

The Updated field indicates the date that this record was updated.

top

Updated By

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

top

Name

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.

top

Process Plan

Foreign key column to MA_Processplan table, (column: MA_Processplan_ID)

Callout: SL_WorkRequirement_ProcessPlan

This element is linked to a callout.

It is implemented by org.openbravo.erpCommon.ad_callouts.SL_WorkRequirement_ProcessPlan Java class.

top

Quantity

Indicates the number of times the process plan needs to be executed.

top

WR Creation Date

Indicates the date that the work requirement came in.

top

Starting Date

A parameter stating when a specified request will begin.

Callout: SL_WorkRequirement_StartDate

This element is linked to a callout.

It is implemented by org.openbravo.erpCommon.ad_callouts.SL_WorkRequirement_StartDate Java class.

top

Ending Date

The End Date indicates the last date in this range.

top

Closed

Indicates if the work requirement is completely done or if we don't want to continue with it.

top

Process Work Requirement

By running this process the operations (activities) and products will be inserted automatically according to the selected process plan. Quantities will be multiplied according to the number of final products (Process Units) required. If the process plan selected does not have the "explodePhases" checked off, products from previously existing phases will be inserted only.

top

Processed

The Processed checkbox indicates that a document has been processed.

top

Document No.

The document number is usually automatically generated by the system and determined by the document type of the document. If the document is not saved, the preliminary number is displayed in "<>". If the document type of your document has no automatic document sequence defined, the field will be empty when creating a new document. This is for documents which usually have an external number (like vendor invoice). If you leave the field empty, the system will generate a document number for you. The document sequence used for this fallback number is defined in the "Document Sequence" window with the name "DocumentNo_<TableName>", where TableName is the actual name of the table inside the database (e.g. C_Order).

top

Include Phases when inserting

Indicates if the work requirement phases will be generated automatically.

top

Process Quantity

The number of Process Units required to be produced. Usually when it comes to production, our requirements are specified by a number of final products (Process Units). To avoid the need for calculating the number of process plan runs, the system allows for entering this number and then automatically calculating the required process plan runs.

Callout: SL_WorkRequirement_Conversion

This element is linked to a callout.

It is implemented by org.openbravo.erpCommon.ad_callouts.SL_WorkRequirement_Conversion Java class.

top

Process Unit

The name of the main final product obtained by executing a process plan.

top

Conversion Rate

Defines how many final products each run of a process plan produces. See the following formula to understand the relation between the three elements:

Process Quantity = Quantity x Conversion Rate

Callout: SL_WorkRequirement_Conversion

This element is linked to a callout.

It is implemented by org.openbravo.erpCommon.ad_callouts.SL_WorkRequirement_Conversion Java class.

top

Related tables

Tables that link this table:

top

Retrieved from "http://wiki.openbravo.com/wiki/ERP/2.50/Developers_Guide/Database_Model/org.openbravo.model.manufacturing.transaction/MA_WorkRequirement"

This page has been accessed 915 times. This page was last modified on 2 July 2011, at 21:04. Content is available under Creative Commons Attribution-ShareAlike 2.5 Spain License.