Skip to content
EBS Reference

WIP_ENTITIES

Schema: WIPmasterPer inventory org

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

Module: Work in ProcessInventory-org partitioned (ORGANIZATION_ID)
Notes

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
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

7 fields · 1 key

Table fields: position, field name, description, data type, and flags. 7 fields.
#FieldDescriptionTypeFlags
1WIP_ENTITY_IDThe universal WIP key — globally unique; jobs, schedules, and outside references all carry itNUMBER
Key
2ORGANIZATION_IDInventory organizationNUMBER
3WIP_ENTITY_NAMEThe job or schedule name users see — unique per organizationVARCHAR2
4ENTITY_TYPEDiscrete job, repetitive assembly, or flow schedule — numeric, decode from your instance's manufacturing lookupsNUMBER
5DESCRIPTIONEntity descriptionVARCHAR2
6PRIMARY_ITEM_IDThe assembly item being builtNUMBER
7GEN_OBJECT_IDGenealogy object id for serialized trackingNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading WIP_ENTITIESon 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_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;

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WIP_ENTITY_ID>, <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_ENTITIESforeign key · 1:1
    ON WIP_DISCRETE_JOBS.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_ID AND WIP_DISCRETE_JOBS.ORGANIZATION_ID = WIP_ENTITIES.ORGANIZATION_ID
  • WIP_ENTITIESMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON WIP_ENTITIES.PRIMARY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIP_ENTITIES.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • PO_DISTRIBUTIONS_ALLWIP_ENTITIESforeign key · N:1
    ON PO_DISTRIBUTIONS_ALL.WIP_ENTITY_ID = WIP_ENTITIES.WIP_ENTITY_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.