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

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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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 a separate store whose full key isn't page-verified — see the plan doc.

    Oracle data-store documentation →

Fields

14 fields · 1 key

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_DEFINITIONSon 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
-- ============================================================
-- 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;

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WORK_DEFINITION_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

  • 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 Manufacturingtables →

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.