Skip to content
EBS Reference

WIP_REQUIREMENT_OPERATIONS

Schema: WIPtransactionPer inventory org

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

Module: Work in ProcessInventory-org partitioned (ORGANIZATION_ID)
Grain note

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

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.
In field listings, K marks a primary-key field.

Fields

17 fields · 5 key

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1WIP_ENTITY_IDThe job or scheduleNUMBER
Key
2INVENTORY_ITEM_IDThe component item — part of the key; the same component can appear at several operationsNUMBER
Key
3OPERATION_SEQ_NUMThe operation the component is required atNUMBER
Key
4ORGANIZATION_IDInventory organization — part of the keyNUMBER
Key
5REPETITIVE_SCHEDULE_IDRepetitive schedule — NULL for discrete jobs, but part of the unique keyNUMBER
Key
6DEPARTMENT_IDThe using departmentNUMBER
7WIP_SUPPLY_TYPESupply method — push, pull, phantom, bulk, supplier; numeric, undecodedNUMBER
8DATE_REQUIREDWhen the component is required — the analysis dateDATE
Filter date
9REQUIRED_QUANTITYTotal quantity requiredNUMBER
10QUANTITY_ISSUEDQuantity issued to date — open balance is required minus issuedNUMBER
11QUANTITY_PER_ASSEMBLYUsage per assemblyNUMBER
12COMPONENT_YIELD_FACTORYield factor applied to the requirementNUMBER
13QUANTITY_ALLOCATEDQuantity allocated by pickingNUMBER
14QUANTITY_BACKORDEREDQuantity backorderedNUMBER
15SUPPLY_SUBINVENTORYThe subinventory issues pull fromVARCHAR2
16SUPPLY_LOCATOR_IDThe locator issues pull fromNUMBER
17MRP_NET_FLAGWhether planning nets the requirementNUMBER

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.

Query parameters
-- ============================================================
-- 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

  • WIP_REQUIREMENT_OPERATIONSWIP_DISCRETE_JOBSforeign key · N:1
    ON WIP_REQUIREMENT_OPERATIONS.WIP_ENTITY_ID = WIP_DISCRETE_JOBS.WIP_ENTITY_ID AND WIP_REQUIREMENT_OPERATIONS.ORGANIZATION_ID = WIP_DISCRETE_JOBS.ORGANIZATION_ID
  • WIP_REQUIREMENT_OPERATIONSMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON 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

Browse more Work in Processtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.