Manufacturing Model
From Opentaps Wiki
Jump to navigationJump to search
This document describes how the data model of the ofbiz manufacturing application works.
Terminology
Manufacturing Tasks:
- A production run is a series of tasks which converts raw materials to finished products.
- A production run task is a particular task of the production run.
- A routing is a template of tasks to be performced to produce a product.
- A routing task is one particular task in the routing.
Data Model Usage
Only a few entities are used to do everything in manufacturing. Different type keys (workEffortTypeId, workEffortAssocTypeId, workEffortGoodStdTypeId) are used to perform the different functions. The following entities are used by the manufacturing application:
- WorkEffort (WE): All manufacturing tasks are modeled as WorkEffort with different workEffortTypeId's. The workEffortParentId is used to associate production run tasks to the parent production task. Descriptive information, times, and dates are all stored on WorkEffort.
- WorkEffortAssoc (WEA): Routing tasks are associated to routing via WEA. When a production run is created, production run tasks are associated to routing task via WEA.
- WorkEffortGoodStandard (WEGS): This is used to do three things:
- Record which routing (template) is used to produce a product
- Record which products are needed for a particular production run task
- Record which product is actually produced by a production run
- Record which product is used to define the purchasing of outsourcing for a routing task (in opentaps Warehouse application.)
- WorkEffortInventoryAssign (WEIA) is used to record actual inventory items issued to a production run task.