Oracle Fusion/Supply Chain/Manufacturing

WIP_DISCRETE_JOBS

Discrete job header — quantities, dates, and status for a work order.

Key Columns

WIP_ENTITY_IDSTATUS_TYPESTART_QUANTITYQUANTITY_COMPLETED

Parent Table

WIP_ENTITIES

Work order (discrete job) identity — number, type, and the item it produces.

Child Tables

WIP_OPERATIONS

Routing operations on a job — the sequence of steps a discrete job passes through, with quantities at each.

WIP_REQUIREMENT_OPERATIONS

Component (material) requirements for a job — what item is needed at which operation, and how much is issued.

WIP_MOVE_TRANSACTIONS

Move transactions — the record of assemblies moving between operations and intraoperation steps (queue → run → to move).

Common Joins

MTL_MATERIAL_TRANSACTIONSvia TRANSACTION_SOURCE_ID = WIP_ENTITY_ID

Material issued to or completed from this job — what Costing reads to value it.

Used In

ManufacturingInventoryCosting

Work order data model

A work order is identified by WIP_ENTITIES and detailed in WIP_DISCRETE_JOBS (quantities, status). Material issued to or completed from the job is recorded in MTL_MATERIAL_TRANSACTIONS, which is also what Costing reads to value the job.

Discrete job execution: routing, components and moves

A discrete job (WIP_DISCRETE_JOBS) is exploded from a bill (BOM_STRUCTURES_B / BOM_COMPONENTS_B) and routing (BOM_OPERATIONAL_ROUTINGS). Job operations are WIP_OPERATIONS, component needs are WIP_REQUIREMENT_OPERATIONS, and assemblies advance through steps via WIP_MOVE_TRANSACTIONS.