Skip to content
Fusion Reference

WIE_WO_OPERATIONS_B

Product: WIEtransactionPer inventory org

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

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
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_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.WOOperationExtractPVO
    OTBI: Manufacturing - Work Order Performance Real Time

    Work Order Operations data store — keyed on WoOperationId.

    Oracle data-store documentation →

Fields

14 fields · 1 key

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1WO_OPERATION_IDSurrogate key of the operationNUMBER
Key
2WORK_ORDER_IDParent work orderNUMBER
3ORGANIZATION_IDPlant (denormalized)NUMBER
4OPERATION_SEQ_NUMBERUser-visible operation sequence (10, 20…)NUMBER
5STANDARD_OPERATION_IDThe standard operation this step was created fromNUMBER
6WORK_CENTER_IDWork center performing the stepNUMBER
7OPERATION_TYPEIn-house vs supplier operationVARCHAR2
ORA_WIS_OPERATION_TYPE
8COUNT_POINT_OPERATION_FLAGCompletion must be explicitly reported hereVARCHAR2
9AUTO_TRANSACT_FLAGMaterials and resources auto-charge on completionVARCHAR2
10READY_QUANTITYQuantity currently in the Ready (queue) state — a balanceNUMBER
11COMPLETED_QUANTITYQuantity completed at this operation — a counterNUMBER
12SCRAPPED_QUANTITYQuantity scrapped hereNUMBER
13PLANNED_START_DATEScheduled step startTIMESTAMP
14PLANNED_COMPLETION_DATEScheduled step finishTIMESTAMP

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

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

  • 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_WO_OPERATIONS_BWIE_WO_OPERATION_MATERIALSheader line · 1:N
    ON 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_ID
  • WIE_WO_OPERATIONS_BWIE_WO_OPERATION_RESOURCESheader line · 1:N
    ON 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_ID
  • WIE_WO_OPERATIONS_BWIS_WORK_CENTERS_Bforeign key · N:1
    ON 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_ID
  • WIE_OPERATION_TRANSACTIONSWIE_WO_OPERATIONS_Bforeign key · N:1
    ON 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

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.