WIP_REQUIREMENT_OPERATIONS
Schema: WIPtransactionPer inventory orgMaterial requirements per job and operation — the job's exploded BOM with required vs issued quantities, supply type, and the supply subinventory issues pull from
Grain is component × operation × job — joining to the job multiplies rows, and open issue quantity is REQUIRED_QUANTITY − QUANTITY_ISSUED (arithmetic, no stored column)
The same component can legitimately appear at several operations — the item is part of the unique key together with the operation.
What the badges mean
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
17 fields · 5 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WIP_ENTITY_ID | The job or schedule | NUMBER | Key |
| 2 | INVENTORY_ITEM_ID | The component item — part of the key; the same component can appear at several operations | NUMBER | Key |
| 3 | OPERATION_SEQ_NUM | The operation the component is required at | NUMBER | Key |
| 4 | ORGANIZATION_ID | Inventory organization — part of the key | NUMBER | Key |
| 5 | REPETITIVE_SCHEDULE_ID | Repetitive schedule — NULL for discrete jobs, but part of the unique key | NUMBER | Key |
| 6 | DEPARTMENT_ID | The using department | NUMBER | |
| 7 | WIP_SUPPLY_TYPE | Supply method — push, pull, phantom, bulk, supplier; numeric, undecoded | NUMBER | |
| 8 | DATE_REQUIRED | When the component is required — the analysis date | DATE | Filter date |
| 9 | REQUIRED_QUANTITY | Total quantity required | NUMBER | |
| 10 | QUANTITY_ISSUED | Quantity issued to date — open balance is required minus issued | NUMBER | |
| 11 | QUANTITY_PER_ASSEMBLY | Usage per assembly | NUMBER | |
| 12 | COMPONENT_YIELD_FACTOR | Yield factor applied to the requirement | NUMBER | |
| 13 | QUANTITY_ALLOCATED | Quantity allocated by picking | NUMBER | |
| 14 | QUANTITY_BACKORDERED | Quantity backordered | NUMBER | |
| 15 | SUPPLY_SUBINVENTORY | The subinventory issues pull from | VARCHAR2 | |
| 16 | SUPPLY_LOCATOR_ID | The locator issues pull from | NUMBER | |
| 17 | MRP_NET_FLAG | Whether planning nets the requirement | NUMBER |
Field provenance: hand-curated. 5 key fields.
Boilerplate SQL
Starting point for reading WIP_REQUIREMENT_OPERATIONSon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
-- ============================================================
-- Table : WIP_REQUIREMENT_OPERATIONS — Material requirements per job and operation — the job's exploded BOM with required vs issued quantities, supply type, and the supply subinventory issues pull from
-- Purpose: Column-selected read of WIP_REQUIREMENT_OPERATIONS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + WIP_ENTITY_ID + INVENTORY_ITEM_ID + OPERATION_SEQ_NUM + REPETITIVE_SCHEDULE_ID
-- Caution: Grain is component × operation × job — joining to the job multiplies rows, and open issue quantity is REQUIRED_QUANTITY − QUANTITY_ISSUED (arithmetic, no stored column)
-- Notes : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
t.WIP_ENTITY_ID AS "The job or schedule",
t.INVENTORY_ITEM_ID AS "The component item — part of the key; the same component can appear at several operations",
t.OPERATION_SEQ_NUM AS "The operation the component is required at",
t.ORGANIZATION_ID AS "Inventory organization — part of the key",
t.REPETITIVE_SCHEDULE_ID AS "Repetitive schedule — NULL for discrete jobs, but part of the unique key",
t.DEPARTMENT_ID AS "The using department",
t.WIP_SUPPLY_TYPE AS "Supply method — push, pull, phantom, bulk, supplier; numeric, undecoded",
t.DATE_REQUIRED AS "When the component is required — the analysis date",
t.REQUIRED_QUANTITY AS "Total quantity required",
t.QUANTITY_ISSUED AS "Quantity issued to date — open balance is required minus issued",
t.QUANTITY_PER_ASSEMBLY AS "Usage per assembly",
t.COMPONENT_YIELD_FACTOR AS "Yield factor applied to the requirement",
t.QUANTITY_ALLOCATED AS "Quantity allocated by picking",
t.QUANTITY_BACKORDERED AS "Quantity backordered",
t.SUPPLY_SUBINVENTORY AS "The subinventory issues pull from",
t.SUPPLY_LOCATOR_ID AS "The locator issues pull from",
t.MRP_NET_FLAG AS "Whether planning nets the requirement"
FROM <catalog>.<schema>.WIP_REQUIREMENT_OPERATIONS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.WIP_ENTITY_ID = <WIP_ENTITY_ID>
-- AND t.INVENTORY_ITEM_ID = <INVENTORY_ITEM_ID>
-- AND t.OPERATION_SEQ_NUM = <OPERATION_SEQ_NUM>
-- AND t.DATE_REQUIRED >= DATE '<DATE_FROM>'
-- AND t.DATE_REQUIRED <= DATE '<DATE_TO>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.WIP_ENTITY_ID;9 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WIP_ENTITY_ID>, <INVENTORY_ITEM_ID>, <OPERATION_SEQ_NUM>, <DATE_FROM>, <DATE_TO>, <watermark>
Relationships
1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
ON WIP_REQUIREMENT_OPERATIONS.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID AND WIP_REQUIREMENT_OPERATIONS.ORGANIZATION_ID = WIP_DISCRETE_JOBS.ORGANIZATION_IDON WIP_REQUIREMENT_OPERATIONS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIP_REQUIREMENT_OPERATIONS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID