WIS_WORK_DEFINITIONS
Product: WISmasterPer inventory orgThe 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
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.
- 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 withINVENTORY_ITEM_IDon 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_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin 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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WORK_DEFINITION_ID | Surrogate key of the work definition header | NUMBER | Key |
| 2 | ORGANIZATION_ID | Manufacturing plant (inventory org) owning the definition | NUMBER | |
| 3 | INVENTORY_ITEM_ID | The produced assembly item | NUMBER | |
| 4 | WORK_DEFINITION_NAME_ID | The reusable definition-name dimension row (Main, Alternate…) | NUMBER | |
| 5 | WORK_DEFINITION_HEADER_NAME | Unique header name; the process name in process manufacturing | VARCHAR2 | |
| 6 | WORK_DEFINITION_TYPE | Kind of work definition | VARCHAR2 | ORA_WIS_WORK_DEFINITION_TYPE |
| 7 | WORK_METHOD_ID | Discrete vs process work method | NUMBER | |
| 8 | STATUS_CODE | Header status | VARCHAR2 | ORA_WIS_WD_STATUS |
| 9 | INACTIVE_DATE | When the definition stopped being usable — NULL while active | DATE | |
| 10 | PRODUCTION_PRIORITY | Rank among the item's definitions — 1 is the primary | NUMBER | |
| 11 | COSTING_PRIORITY | Which definition standard cost rollup uses | NUMBER | |
| 12 | BILL_SEQUENCE_ID | The item structure supplying material requirements | NUMBER | |
| 13 | QUANTITY | Output quantity the definition is stated for; the batch quantity in process manufacturing | NUMBER | |
| 14 | UOM_CODE | UOM of that quantity | VARCHAR2 |
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.
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
ON WIS_WORK_DEFINITIONS.WORK_DEFINITION_ID = WIS_WD_OPERATIONS_B.WORK_DEFINITION_IDON WIS_WD_VERSIONS.WORK_DEFINITION_ID = WIS_WORK_DEFINITIONS.WORK_DEFINITION_IDON WIS_WORK_DEFINITIONS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIS_WORK_DEFINITIONS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.ORGANIZATION_IDON WIS_WORK_DEFINITIONS.BILL_SEQUENCE_ID = EGP_STRUCTURES_B.BILL_SEQUENCE_IDON WIS_WORK_DEFINITIONS.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON 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
More Manufacturing tables
- WIE_OPERATION_TRANSACTIONSThe shop-floor product ledger — one row per movement of primary-product quantity through operation dispatch states: completions, moves, scrap, reject, and their reversals
- WIE_RESOURCE_TRANSACTIONSThe resource charge ledger — labor and equipment usage charged (or reversed) against work order operation resources, with full lineage down to the resource assignment
- WIE_WO_OPERATION_MATERIALSComponent requirements of each work order operation — one row per material line with per-assembly usage, total requirement, supply method, and running issued/allocated/picked counters
- WIE_WO_OPERATION_RESOURCESLabor and equipment requirements for each work order operation — usage rate, required and actual usage, assigned units, and charge behavior
- WIE_WO_OPERATIONS_BWork order operations — one row per execution step with its sequence, work center, count-point behavior, and the quantity balances sitting at each dispatch state
- WIE_WORK_ORDERS_BThe work order header — the primary product being built, the work definition version it was created from, the build quantity, status, and planned/actual execution dates