WIP_ENTITIES
Schema: WIPmasterPer inventory orgThe WIP identity registry — every discrete job, repetitive assembly, and flow schedule claims its id and unique name here before type-specific detail lands in child tables; the anchor outside references point at
Shared across entity types — counting rows here is not counting jobs; filter ENTITY_TYPE. Purchasing's outside-processing distributions point at this table through their WIP_ENTITY_ID column.
What the badges mean
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
7 fields · 1 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WIP_ENTITY_ID | The universal WIP key — globally unique; jobs, schedules, and outside references all carry it | NUMBER | Primary-key field |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 3 | WIP_ENTITY_NAME | The job or schedule name users see — unique per organization | VARCHAR2 | |
| 4 | ENTITY_TYPE | Discrete job, repetitive assembly, or flow schedule — numeric, decode from your instance's manufacturing lookups | NUMBER | |
| 5 | DESCRIPTION | Entity description | VARCHAR2 | |
| 6 | PRIMARY_ITEM_ID | The assembly item being built | NUMBER | |
| 7 | GEN_OBJECT_ID | Genealogy object id for serialized tracking | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading WIP_ENTITIES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WIP_ENTITY_ID>, <watermark>
-- ============================================================
-- Table : WIP_ENTITIES — The WIP identity registry — every discrete job, repetitive assembly, and flow schedule claims its id and unique name here before type-specific detail lands in child tables; the anchor outside references point at
-- Purpose: Column-selected read of WIP_ENTITIES — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + WIP_ENTITY_ID
-- 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 universal WIP key — globally unique; jobs, schedules, and outside references all carry it",
t.ORGANIZATION_ID AS "Inventory organization",
t.WIP_ENTITY_NAME AS "The job or schedule name users see — unique per organization",
t.ENTITY_TYPE AS "Discrete job, repetitive assembly, or flow schedule — numeric, decode from your instance's manufacturing lookups",
t.DESCRIPTION AS "Entity description",
t.PRIMARY_ITEM_ID AS "The assembly item being built",
t.GEN_OBJECT_ID AS "Genealogy object id for serialized tracking"
FROM <catalog>.<schema>.WIP_ENTITIES 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.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.WIP_ENTITY_ID;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Loading relationship diagram…
Join details
ON WIP_DISCRETE_JOBS.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_ID AND WIP_DISCRETE_JOBS.ORGANIZATION_ID = WIP_ENTITIES.ORGANIZATION_IDON WIP_ENTITIES.PRIMARY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIP_ENTITIES.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_IDON PO_DISTRIBUTIONS_ALL.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_ID
More Work in Process tables
- WIP_MOVE_TRANSACTIONSThe shop-floor move ledger — one row per move event with from/to operation and intraoperation step, quantity, and date; the throughput, cycle-time, and WIP-aging fact behind the operation counters
- WIP_OPERATIONSOperations 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
- WIP_REQUIREMENT_OPERATIONSMaterial requirements per job and operation — the job's exploded BOM with required vs issued quantities, supply type, and the supply subinventory issues pull from
- WIP_TRANSACTIONSThe WIP resource ledger — one row per resource charge (labor, machine, outside processing) with operation, resource, rates, and the purchasing/receiving references that drive outside-processing charges
- WIP_ACCOUNTING_CLASSESThe WIP accounting class master per organization — class code, type, and the elemental valuation and variance accounts jobs charge through
- WIP_DISCRETE_JOBSDiscrete job detail — status, start/completed/scrapped quantities, scheduled vs actual dates, accounting class, and the BOM/routing the job was built from; the workhorse of job-level manufacturing analytics