Skip to content
Fusion Reference

WIS_WORK_DEFINITIONS

Product: WISmasterPer inventory org

The work definition header — one row per item + definition-name combination in a plant, binding the produced item, the item structure supplying material requirements, and the work method; the Fusion successor to the routing

Identity
Module: ManufacturingInventory-org partitioned (ORGANIZATION_ID)
Notes

Breaks the _B/_TL convention — the header is the plain name, version-controlled attributes live in WIS_WD_VERSIONS, and the display name is a separate names dimension (not yet cataloged). PRODUCTION_PRIORITY 1 marks the item's primary definition; COSTING_PRIORITY picks which one cost rollup uses. BILL_SEQUENCE_ID points at the item structure.

What the badges mean
Product: EGP
Product: the Oracle product family that owns the object — the short code Oracle's Tables and Views documentation lists as the object owner. Fusion is SaaS, so this isn't a database schema; there's no SQL path to the tables at all (see the quirks guide).
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.

Structural facts — how the table is partitioned, not a trap by itself

BU-striped (ORG_ID)
Rows are scoped to a business unit. The column is still named ORG_ID, but in Fusion it means business unit, not the EBS operating unit — treat any migrated “operating unit” filter as suspect (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization via ORGANIZATION_ID — always pair it with INVENTORY_ITEM_ID on item-level joins (see the quirks guide).
Set / ledger / named-BU striped
Some tables stripe by a named column instead of ORG_ID: reference data set (SET_ID — see the quirks guide), ledger (LEDGER_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in procurement). The table page’s partition line names the column, and the generated SQL anchors on it — never treat these tables as unpartitioned.
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part of the key. Join without a window filter and every fact multiplies by history (see the quirks guide).
View
This is a documented convenience view, not a physical table. Extract through the BICC data store that fronts its base objects instead of assuming the view lands as-is.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

Header & line

WIS_WORK_DEFINITIONS is the header for its lines in WIS_WD_OPERATIONS_B.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.ScmExtractAM.WisBiccExtractAM.WorkDefinitionExtractPVO

    Work Definitions data store — keyed on WorkDefinitionId. No work-definition OTBI subject area exists in the 26B book; definition attributes surface as dimensions. Versions ride the separate WDVersionExtractPVO store, mapped on its own row.

    Oracle data-store documentation (opens in new tab)

Fields

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1WORK_DEFINITION_IDSurrogate key of the work definition headerNUMBER
Key
2ORGANIZATION_IDManufacturing plant (inventory org) owning the definitionNUMBER
3INVENTORY_ITEM_IDThe produced assembly itemNUMBER
4WORK_DEFINITION_NAME_IDThe reusable definition-name dimension row (Main, Alternate…)NUMBER
5WORK_DEFINITION_HEADER_NAMEUnique header name; the process name in process manufacturingVARCHAR2
6WORK_DEFINITION_TYPEKind of work definitionVARCHAR2
ORA_WIS_WORK_DEFINITION_TYPE
7WORK_METHOD_IDDiscrete vs process work methodNUMBER
8STATUS_CODEHeader statusVARCHAR2
ORA_WIS_WD_STATUS
9INACTIVE_DATEWhen the definition stopped being usable — NULL while activeDATE
10PRODUCTION_PRIORITYRank among the item's definitions — 1 is the primaryNUMBER
11COSTING_PRIORITYWhich definition standard cost rollup usesNUMBER
12BILL_SEQUENCE_IDThe item structure supplying material requirementsNUMBER
13QUANTITYOutput quantity the definition is stated for; the batch quantity in process manufacturingNUMBER
14UOM_CODEUOM of that quantityVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of WIS_WORK_DEFINITIONS on Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WORK_DEFINITION_ID>, <watermark>

-- ============================================================
-- Table  : WIS_WORK_DEFINITIONS — The work definition header — one row per item + definition-name combination in a plant, binding the produced item, the item structure supplying material requirements, and the work method; the Fusion successor to the routing
-- Purpose: Column-selected read of WIS_WORK_DEFINITIONS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + WORK_DEFINITION_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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.WORK_DEFINITION_ID AS "Surrogate key of the work definition header",
  t.ORGANIZATION_ID AS "Manufacturing plant (inventory org) owning the definition",
  t.INVENTORY_ITEM_ID AS "The produced assembly item",
  t.WORK_DEFINITION_NAME_ID AS "The reusable definition-name dimension row (Main, Alternate…)",
  t.WORK_DEFINITION_HEADER_NAME AS "Unique header name; the process name in process manufacturing",
  t.WORK_DEFINITION_TYPE AS "Kind of work definition",  -- decode t.WORK_DEFINITION_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_WORK_DEFINITION_TYPE', LANGUAGE-filtered)
  t.WORK_METHOD_ID AS "Discrete vs process work method",
  t.STATUS_CODE AS "Header status",  -- decode t.STATUS_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_WD_STATUS', LANGUAGE-filtered)
  t.INACTIVE_DATE AS "When the definition stopped being usable — NULL while active",
  t.PRODUCTION_PRIORITY AS "Rank among the item's definitions — 1 is the primary",
  t.COSTING_PRIORITY AS "Which definition standard cost rollup uses",
  t.BILL_SEQUENCE_ID AS "The item structure supplying material requirements",
  t.QUANTITY AS "Output quantity the definition is stated for; the batch quantity in process manufacturing",
  t.UOM_CODE AS "UOM of that quantity"
FROM <catalog>.<schema>.WIS_WORK_DEFINITIONS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.WORK_DEFINITION_ID = <WORK_DEFINITION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.WORK_DEFINITION_ID;

Verified September 2026 · docs release 26C

Column names differ in BICC extracts — see PVO header drift.

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.

Join details

  • WIS_WORK_DEFINITIONSWIS_WD_OPERATIONS_Bheader line · 1:N
    ON WIS_WORK_DEFINITIONS.WORK_DEFINITION_ID = WIS_WD_OPERATIONS_B.WORK_DEFINITION_ID
  • WIS_WD_VERSIONSWIS_WORK_DEFINITIONSforeign key · N:1
    ON WIS_WD_VERSIONS.WORK_DEFINITION_ID = WIS_WORK_DEFINITIONS.WORK_DEFINITION_ID
  • WIS_WORK_DEFINITIONSEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON WIS_WORK_DEFINITIONS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIS_WORK_DEFINITIONS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • WIS_WORK_DEFINITIONSEGP_STRUCTURES_Bforeign key · N:1
    ON WIS_WORK_DEFINITIONS.BILL_SEQUENCE_ID = EGP_STRUCTURES_B.BILL_SEQUENCE_ID
  • WIS_WORK_DEFINITIONSINV_ORG_PARAMETERSforeign key · N:1
    ON WIS_WORK_DEFINITIONS.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • WIE_WORK_ORDERS_BWIS_WORK_DEFINITIONSforeign key · N:1
    ON WIE_WORK_ORDERS_B.WORK_DEFINITION_ID = WIS_WORK_DEFINITIONS.WORK_DEFINITION_ID AND WIE_WORK_ORDERS_B.ORGANIZATION_ID = WIS_WORK_DEFINITIONS.ORGANIZATION_ID

Browse more Manufacturing tables

More Manufacturing tables

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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.