Fusion Reference
WIE_WO_OPERATIONS_B
Product: WIEtransactionPer inventory orgWork order operations — one row per execution step with its sequence, work center, count-point behavior, and the quantity balances sitting at each dispatch state
Identity
Grain note
READY/COMPLETED/SCRAPPED quantities are state balances maintained from the operation ledger — position, not history
Notes
ACTUAL_START_DATE and ACTUAL_COMPLETION_DATE are documented as currently unused — derive actuals from the operation transaction ledger. Outside-processing steps carry the OSP item, supplier, and PO pipeline quantities.
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
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
WIE_WO_OPERATIONS_B lines join back to their header WIE_WORK_ORDERS_B — and the org column — so a line never fans out.
WIE_WO_OPERATIONS_B is the header for its lines in WIE_WO_OPERATION_MATERIALS and WIE_WO_OPERATION_RESOURCES.
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.WOOperationExtractPVOOTBI: Manufacturing - Work Order Performance Real Time
Work Order Operations data store — keyed on WoOperationId.
Oracle data-store documentation (opens in new tab)
Fields
14 fields · 1 key
14 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WO_OPERATION_ID | Surrogate key of the operation | NUMBER | Key |
| 2 | WORK_ORDER_ID | Parent work order | NUMBER | |
| 3 | ORGANIZATION_ID | Plant (denormalized) | NUMBER | |
| 4 | OPERATION_SEQ_NUMBER | User-visible operation sequence (10, 20…) | NUMBER | |
| 5 | STANDARD_OPERATION_ID | The standard operation this step was created from | NUMBER | |
| 6 | WORK_CENTER_ID | Work center performing the step | NUMBER | |
| 7 | OPERATION_TYPE | In-house vs supplier operation | VARCHAR2 | ORA_WIS_OPERATION_TYPE |
| 8 | COUNT_POINT_OPERATION_FLAG | Completion must be explicitly reported here | VARCHAR2 | |
| 9 | AUTO_TRANSACT_FLAG | Materials and resources auto-charge on completion | VARCHAR2 | |
| 10 | READY_QUANTITY | Quantity currently in the Ready (queue) state — a balance | NUMBER | |
| 11 | COMPLETED_QUANTITY | Quantity completed at this operation — a counter | NUMBER | |
| 12 | SCRAPPED_QUANTITY | Quantity scrapped here | NUMBER | |
| 13 | PLANNED_START_DATE | Scheduled step start | TIMESTAMP | |
| 14 | PLANNED_COMPLETION_DATE | Scheduled step finish | TIMESTAMP |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIE_WO_OPERATIONS_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.
Query parameters
5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WO_OPERATION_ID>, <watermark>
-- ============================================================
-- Table : WIE_WO_OPERATIONS_B — Work order operations — one row per execution step with its sequence, work center, count-point behavior, and the quantity balances sitting at each dispatch state
-- Purpose: Column-selected read of WIE_WO_OPERATIONS_B — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + WO_OPERATION_ID
-- Caution: READY/COMPLETED/SCRAPPED quantities are state balances maintained from the operation ledger — position, not history
-- 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.WO_OPERATION_ID AS "Surrogate key of the operation",
t.WORK_ORDER_ID AS "Parent work order",
t.ORGANIZATION_ID AS "Plant (denormalized)",
t.OPERATION_SEQ_NUMBER AS "User-visible operation sequence (10, 20…)",
t.STANDARD_OPERATION_ID AS "The standard operation this step was created from",
t.WORK_CENTER_ID AS "Work center performing the step",
t.OPERATION_TYPE AS "In-house vs supplier operation", -- decode t.OPERATION_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_OPERATION_TYPE', LANGUAGE-filtered)
t.COUNT_POINT_OPERATION_FLAG AS "Completion must be explicitly reported here",
t.AUTO_TRANSACT_FLAG AS "Materials and resources auto-charge on completion",
t.READY_QUANTITY AS "Quantity currently in the Ready (queue) state — a balance",
t.COMPLETED_QUANTITY AS "Quantity completed at this operation — a counter",
t.SCRAPPED_QUANTITY AS "Quantity scrapped here",
t.PLANNED_START_DATE AS "Scheduled step start",
t.PLANNED_COMPLETION_DATE AS "Scheduled step finish"
FROM <catalog>.<schema>.WIE_WO_OPERATIONS_B t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
-- AND t.WO_OPERATION_ID = <WO_OPERATION_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.WO_OPERATION_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.
Loading relationship diagram…
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_WO_OPERATIONS_B.WO_OPERATION_ID = WIE_WO_OPERATION_MATERIALS.WO_OPERATION_ID AND WIE_WO_OPERATIONS_B.ORGANIZATION_ID = WIE_WO_OPERATION_MATERIALS.ORGANIZATION_IDON WIE_WO_OPERATIONS_B.WO_OPERATION_ID = WIE_WO_OPERATION_RESOURCES.WO_OPERATION_ID AND WIE_WO_OPERATIONS_B.ORGANIZATION_ID = WIE_WO_OPERATION_RESOURCES.ORGANIZATION_IDON WIE_WO_OPERATIONS_B.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_ID AND WIE_WO_OPERATIONS_B.ORGANIZATION_ID = WIS_WORK_CENTERS_B.ORGANIZATION_IDON WIE_OPERATION_TRANSACTIONS.WO_OPERATION_ID = WIE_WO_OPERATIONS_B.WO_OPERATION_ID AND WIE_OPERATION_TRANSACTIONS.ORGANIZATION_ID = WIE_WO_OPERATIONS_B.ORGANIZATION_ID
More Manufacturing tables
- 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
- 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