Skip to content
Fusion Reference

WIE_WORK_ORDERS_B

Product: WIEtransactionPer inventory org

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

Grain note

COMPLETED/SCRAPPED/REJECTED quantities are maintained counters, not events — event history lives in the two transaction ledgers

Notes

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

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.WorkOrderExtractPVO
    OTBI: 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 →

Fields

17 fields · 2 key

Table fields: position, field name, description, data type, and flags. 17 fields.
#FieldDescriptionTypeFlags
1WORK_ORDER_IDSurrogate key of the work orderNUMBER
Key
2WORK_ORDER_NUMBERUser-facing work order numberVARCHAR2
Key
3ORGANIZATION_IDManufacturing plant owning the work orderNUMBER
4INVENTORY_ITEM_IDThe assembly / primary product itemNUMBER
5WORK_DEFINITION_IDThe work definition usedNUMBER
6WORK_DEFINITION_VERSION_IDThe specific version the order was created fromNUMBER
7WORK_ORDER_STATUS_IDThe user-definable status row — join through it, don't filter literalsNUMBER
8WORK_ORDER_TYPEStandard vs nonstandard workVARCHAR2
ORA_WIE_WO_TYPE
9PLANNED_START_QUANTITYPlanned build quantityNUMBER
10COMPLETED_QUANTITYRunning total completed — a maintained counter, not eventsNUMBER
11SCRAPPED_QUANTITYRunning total scrappedNUMBER
12UOM_CODEUOM the assembly is produced inVARCHAR2
13PLANNED_START_DATEScheduled startTIMESTAMP
14PLANNED_COMPLETION_DATEScheduled finishTIMESTAMP
15ACTUAL_START_DATEActual startTIMESTAMP
16ACTUAL_COMPLETION_DATEActual finishTIMESTAMP
17RELEASED_DATEWhen released to the shop floorTIMESTAMP

Field provenance: hand-curated. 2 key fields.

Boilerplate SQL

Starting point for reading the BICC-landed copy of WIE_WORK_ORDERS_Bon 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  : 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;

6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WORK_ORDER_ID>, <WORK_ORDER_NUMBER>, <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

  • WIE_WORK_ORDERS_BWIE_WO_OPERATIONS_Bheader line · 1:N
    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_ID
  • WIE_WORK_ORDERS_BEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON 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_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
  • WIE_WORK_ORDERS_BWIS_WD_VERSIONSforeign key · N:1
    ON WIE_WORK_ORDERS_B.WORK_DEFINITION_VERSION_ID = WIS_WD_VERSIONS.WORK_DEFINITION_VERSION_ID
  • WIE_WORK_ORDERS_BINV_ORG_PARAMETERSforeign key · N:1
    ON WIE_WORK_ORDERS_B.ORGANIZATION_ID = INV_ORG_PARAMETERS.ORGANIZATION_ID
  • WIE_OPERATION_TRANSACTIONSWIE_WORK_ORDERS_Bforeign key · N:1
    ON WIE_OPERATION_TRANSACTIONS.WORK_ORDER_ID = WIE_WORK_ORDERS_B.WORK_ORDER_ID AND WIE_OPERATION_TRANSACTIONS.ORGANIZATION_ID = WIE_WORK_ORDERS_B.ORGANIZATION_ID
  • WIE_RESOURCE_TRANSACTIONSWIE_WORK_ORDERS_Bforeign key · N:1
    ON 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

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.