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.manufacturing.transaction/MA WorkRequirement

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.manufacturing.transaction


Contents

MA_WorkRequirement

This table contains the following columns:

Name Nullable Data Type Description


DocumentNo No NVARCHAR (30) 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).
MA_Workrequirement_ID No VARCHAR (32) Indicates a work requirement.
AD_Client_ID No VARCHAR (32) A Client is a company or a legal entity. You cannot share data between Clients.
StartDate No TIMESTAMP (7) A parameter stating when a specified request will begin.
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 Yes 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.
MA_Processplan_ID No VARCHAR (32) Indicates a process plan.
Quantity No DECIMAL Indicates the quantity of product needed to process one time the sequence.
Launchdate No TIMESTAMP (7) Indicates the date that the work requirement came in.
EndDate No TIMESTAMP (7) The End Date indicates the last date in this range.
Closed No CHAR (1) Indicates if the work requirement phase has been completely done.
Explote Yes CHAR (1) Process to explode the phases and/or insert the correspondent products to them.
Processed Yes CHAR (1) The Processed checkbox indicates that a document has been processed.
Explodephases No CHAR (1) Indicates if the work requirement operations will be generated automatically.
Secondaryqty Yes DECIMAL (10,0) 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.
Secondaryunit Yes NVARCHAR (40) The name of the main final product obtained by executing a process plan.
Conversionrate Yes DECIMAL 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

Estimatedtime No DECIMAL Estimated time for the operation
Runtime No DECIMAL Operation run time
C_Doctype_ID Yes VARCHAR (32) The Document Type determines document sequence and processing rules
Createworkrequirement Yes CHAR (1) Create all Work Effort for a specific day

Columns

Document No.


top


Work Requirement



top


Client


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

top


Starting Date


Callout: SL_WorkRequirement_StartDate

This column has a callout associated.

It is implemented by [1] Java Class.

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


Process Plan


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

Callout: SL_WorkRequirement_ProcessPlan

This column has a callout associated.

It is implemented by [2] Java Class.

top


Quantity



top


WR Creation Date



top


Ending Date



top


Closed



top


Insert Products and/or Phases



top


Processed



top


Include Phases when inserting



top


Process Quantity



Callout: SL_WorkRequirement_Conversion

This column has a callout associated.

It is implemented by [3] Java Class.

top


Process Unit



top


Conversion Rate



Callout: SL_WorkRequirement_Conversion

This column has a callout associated.

It is implemented by [4] Java Class.

top


Estimated Time



top


Run time



top


Document Type


Foreign key column to C_DocType table, (column: C_DocType_ID) It has a validation "C_DocType Work Requirement", with the following code

C_DocType.DocBaseType='WRE'

top


Createworkrequirement



top


Other Info

Check Constraints

These are the check constraints for this table:

top

Back button.png   Back to org.openbravo.model.manufacturing.transaction

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

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