Skip to content
EBS Reference

WIP_OPERATIONS

Schema: WIPtransactionPer inventory org

Operations on a job or repetitive schedule — the shop-floor step sequence with department, live quantity counters per intraoperation step (queue, run, to-move, reject, scrap), and first/last-unit schedule dates

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

The quantity columns are live position counters, not history — summing them across extracts double-counts; the event history is the move transaction ledger

Notes

REPETITIVE_SCHEDULE_ID participates in the unique key and is NULL for discrete jobs — a job id alone is not a unique parent here.

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.

Header & line

WIP_OPERATIONS lines join back to their header WIP_DISCRETE_JOBS — and the org column — so a line never fans out.

Fields

18 fields · 4 key

Table fields: position, field name, description, data type, and flags. 18 fields.
#FieldDescriptionTypeFlags
1WIP_ENTITY_IDThe job or scheduleNUMBER
Key
2OPERATION_SEQ_NUMOperation sequence within the job's routingNUMBER
Key
3ORGANIZATION_IDInventory organization — part of the keyNUMBER
Key
4REPETITIVE_SCHEDULE_IDRepetitive schedule — NULL for discrete jobs, but part of the unique keyNUMBER
Key
5OPERATION_SEQUENCE_IDThe BOM routing operation this one came fromNUMBER
6STANDARD_OPERATION_IDThe standard operation referenceNUMBER
7DEPARTMENT_IDThe department (work center) running the operationNUMBER
8QUANTITY_IN_QUEUEUnits in the Queue step right now — a live counter, not historyNUMBER
9QUANTITY_RUNNINGUnits in the Run stepNUMBER
10QUANTITY_WAITING_TO_MOVEUnits in the To Move stepNUMBER
11QUANTITY_REJECTEDUnits in the Reject stepNUMBER
12QUANTITY_SCRAPPEDUnits scrapped from the operationNUMBER
13QUANTITY_COMPLETEDUnits completed through the operationNUMBER
14FIRST_UNIT_START_DATEFirst unit's scheduled start — the schedule-side analysis dateDATE
Filter date
15LAST_UNIT_START_DATELast unit's scheduled startDATE
16LAST_UNIT_COMPLETION_DATELast unit's scheduled completionDATE
17DATE_LAST_MOVEDWhen a move last touched the operation — the activity-recency signalDATE
18COUNT_POINT_TYPECount-point/autocharge behavior of the operationNUMBER

Field provenance: hand-curated. 4 key fields.

Boilerplate SQL

Starting point for reading WIP_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_OPERATIONS — Operations on a job or repetitive schedule — the shop-floor step sequence with department, live quantity counters per intraoperation step (queue, run, to-move, reject, scrap), and first/last-unit schedule dates
-- Purpose: Column-selected read of WIP_OPERATIONS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + WIP_ENTITY_ID + OPERATION_SEQ_NUM + REPETITIVE_SCHEDULE_ID
-- Caution: The quantity columns are live position counters, not history — summing them across extracts double-counts; the event history is the move transaction ledger
-- 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.OPERATION_SEQ_NUM AS "Operation sequence within the job's routing",
  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.OPERATION_SEQUENCE_ID AS "The BOM routing operation this one came from",
  t.STANDARD_OPERATION_ID AS "The standard operation reference",
  t.DEPARTMENT_ID AS "The department (work center) running the operation",
  t.QUANTITY_IN_QUEUE AS "Units in the Queue step right now — a live counter, not history",
  t.QUANTITY_RUNNING AS "Units in the Run step",
  t.QUANTITY_WAITING_TO_MOVE AS "Units in the To Move step",
  t.QUANTITY_REJECTED AS "Units in the Reject step",
  t.QUANTITY_SCRAPPED AS "Units scrapped from the operation",
  t.QUANTITY_COMPLETED AS "Units completed through the operation",
  t.FIRST_UNIT_START_DATE AS "First unit's scheduled start — the schedule-side analysis date",
  t.LAST_UNIT_START_DATE AS "Last unit's scheduled start",
  t.LAST_UNIT_COMPLETION_DATE AS "Last unit's scheduled completion",
  t.DATE_LAST_MOVED AS "When a move last touched the operation — the activity-recency signal",
  t.COUNT_POINT_TYPE AS "Count-point/autocharge behavior of the operation"
FROM <catalog>.<schema>.WIP_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.OPERATION_SEQ_NUM = <OPERATION_SEQ_NUM>
  -- AND t.FIRST_UNIT_START_DATE >= DATE '<DATE_FROM>'
  -- AND t.FIRST_UNIT_START_DATE <= 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;

8 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WIP_ENTITY_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_DISCRETE_JOBSWIP_OPERATIONSheader line · 1:N
    ON WIP_DISCRETE_JOBS.WIP_ENTITY_ID = WIP_OPERATIONS.WIP_ENTITY_ID AND WIP_DISCRETE_JOBS.ORGANIZATION_ID = WIP_OPERATIONS.ORGANIZATION_ID
  • WIP_OPERATIONSBOM_DEPARTMENTSforeign key · N:1
    ON WIP_OPERATIONS.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID AND WIP_OPERATIONS.ORGANIZATION_ID = BOM_DEPARTMENTS.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.