WIE_WORK_ORDERS_B
Product: WIEtransactionPer inventory orgThe 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
COMPLETED/SCRAPPED/REJECTED quantities are maintained counters, not events — event history lives in the two transaction ledgers
Statuses are user-definable rows: WORK_ORDER_STATUS_ID points at a status record mapped to a system status (unreleased/released/on hold/completed/closed/canceled) — join through it rather than filtering literals; no status ladder ships. Translated names live on WIE_WORK_ORDERS_TL (not yet cataloged).
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
WIE_WORK_ORDERS_B is the header for its lines in WIE_WO_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.WieBiccExtractAM.WorkOrderExtractPVOOTBI: Manufacturing - Work Order Performance Real Time
Work Orders data store — keyed on WorkOrderId. The subject-area name is Work Order Performance in Oracle's book — no plain Work Orders subject area exists.
Oracle data-store documentation (opens in new tab)
Fields
17 fields · 2 key
17 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WORK_ORDER_ID | Surrogate key of the work order | NUMBER | Key |
| 2 | WORK_ORDER_NUMBER | User-facing work order number | VARCHAR2 | Key |
| 3 | ORGANIZATION_ID | Manufacturing plant owning the work order | NUMBER | |
| 4 | INVENTORY_ITEM_ID | The assembly / primary product item | NUMBER | |
| 5 | WORK_DEFINITION_ID | The work definition used | NUMBER | |
| 6 | WORK_DEFINITION_VERSION_ID | The specific version the order was created from | NUMBER | |
| 7 | WORK_ORDER_STATUS_ID | The user-definable status row — join through it, don't filter literals | NUMBER | |
| 8 | WORK_ORDER_TYPE | Standard vs nonstandard work | VARCHAR2 | ORA_WIE_WO_TYPE |
| 9 | PLANNED_START_QUANTITY | Planned build quantity | NUMBER | |
| 10 | COMPLETED_QUANTITY | Running total completed — a maintained counter, not events | NUMBER | |
| 11 | SCRAPPED_QUANTITY | Running total scrapped | NUMBER | |
| 12 | UOM_CODE | UOM the assembly is produced in | VARCHAR2 | |
| 13 | PLANNED_START_DATE | Scheduled start | TIMESTAMP | |
| 14 | PLANNED_COMPLETION_DATE | Scheduled finish | TIMESTAMP | |
| 15 | ACTUAL_START_DATE | Actual start | TIMESTAMP | |
| 16 | ACTUAL_COMPLETION_DATE | Actual finish | TIMESTAMP | |
| 17 | RELEASED_DATE | When released to the shop floor | TIMESTAMP |
Field provenance: hand-curated. 2 key fields.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIE_WORK_ORDERS_B 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.
6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WORK_ORDER_ID>, <WORK_ORDER_NUMBER>, <watermark>
-- ============================================================
-- Table : WIE_WORK_ORDERS_B — The 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
-- Purpose: Column-selected read of WIE_WORK_ORDERS_B — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + WORK_ORDER_ID + WORK_ORDER_NUMBER
-- Caution: COMPLETED/SCRAPPED/REJECTED quantities are maintained counters, not events — event history lives in the two transaction ledgers
-- 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_ORDER_ID AS "Surrogate key of the work order",
t.WORK_ORDER_NUMBER AS "User-facing work order number",
t.ORGANIZATION_ID AS "Manufacturing plant owning the work order",
t.INVENTORY_ITEM_ID AS "The assembly / primary product item",
t.WORK_DEFINITION_ID AS "The work definition used",
t.WORK_DEFINITION_VERSION_ID AS "The specific version the order was created from",
t.WORK_ORDER_STATUS_ID AS "The user-definable status row — join through it, don't filter literals",
t.WORK_ORDER_TYPE AS "Standard vs nonstandard work", -- decode t.WORK_ORDER_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIE_WO_TYPE', LANGUAGE-filtered)
t.PLANNED_START_QUANTITY AS "Planned build quantity",
t.COMPLETED_QUANTITY AS "Running total completed — a maintained counter, not events",
t.SCRAPPED_QUANTITY AS "Running total scrapped",
t.UOM_CODE AS "UOM the assembly is produced in",
t.PLANNED_START_DATE AS "Scheduled start",
t.PLANNED_COMPLETION_DATE AS "Scheduled finish",
t.ACTUAL_START_DATE AS "Actual start",
t.ACTUAL_COMPLETION_DATE AS "Actual finish",
t.RELEASED_DATE AS "When released to the shop floor"
FROM <catalog>.<schema>.WIE_WORK_ORDERS_B t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
-- AND t.WORK_ORDER_ID = <WORK_ORDER_ID>
-- AND t.WORK_ORDER_NUMBER = '<WORK_ORDER_NUMBER>'
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.WORK_ORDER_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 WIE_WORK_ORDERS_B.WORK_ORDER_ID = WIE_WO_OPERATIONS_B.WORK_ORDER_ID AND WIE_WORK_ORDERS_B.ORGANIZATION_ID = WIE_WO_OPERATIONS_B.ORGANIZATION_IDON WIE_WORK_ORDERS_B.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIE_WORK_ORDERS_B.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.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_IDON WIE_WORK_ORDERS_B.WORK_DEFINITION_VERSION_ID = WIS_WD_VERSIONS.WORK_DEFINITION_VERSION_IDON WIE_WORK_ORDERS_B.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_IDON WIE_OPERATION_TRANSACTIONS.WORK_ORDER_ID = WIE_WORK_ORDERS_B.WORK_ORDER_ID AND WIE_OPERATION_TRANSACTIONS.ORGANIZATION_ID = WIE_WORK_ORDERS_B.ORGANIZATION_IDON WIE_RESOURCE_TRANSACTIONS.WORK_ORDER_ID = WIE_WORK_ORDERS_B.WORK_ORDER_ID AND WIE_RESOURCE_TRANSACTIONS.ORGANIZATION_ID = WIE_WORK_ORDERS_B.ORGANIZATION_ID
More Manufacturing tables
- WIS_RESOURCES_BThe production resource master — each row an equipment or labor resource that performs operations at work centers, unique per plant by resource code
- WIS_WD_OPERATIONS_BWork definition operations — the ordered, date-effective steps of a work definition, each pointing at the work center where it runs and optionally at a reusable standard operation
- WIS_WD_VERSIONSWork definition versions — dated snapshots of the version-controlled header attributes, with the approval status gating which version execution uses
- WIS_WORK_CENTERS_BThe work center master — a physical station inside a work area where a type of operation happens; deliberately thin, with names in the translation companion and capacity on the resource assignments
- WIS_WORK_DEFINITIONSThe 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
- 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