Skip to content
Fusion Reference

WIE_OPERATION_TRANSACTIONS

Product: WIEtransactionPer inventory org

The shop-floor product ledger — one row per movement of primary-product quantity through operation dispatch states: completions, moves, scrap, reject, and their reversals

Identity
Module: ManufacturingInventory-org partitioned (ORGANIZATION_ID)
Grain note

The transaction type is really a from-state → to-state pair, and reversals write new rows moving quantity back — net the rows, don't count events

Notes

Covers product movement only — resource charges are the separate WIE_RESOURCE_TRANSACTIONS ledger, and material issues flow to the inventory transaction ledger. INV_TRANSACTION_ID is the documented link to the inventory ledger when a completion hits stock.

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.

Structural facts — how the table is partitioned, not a trap by itself

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 with INVENTORY_ITEM_ID on 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_ID on the GL journal tables), or a named business-unit column (PRC_BU_ID / REQ_BU_ID in 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 LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows.

Join & extract hazards — verify before you rely on this

Date-effective
This is an _F table — one row per entity per effectivity window, with EFFECTIVE_START_DATE and EFFECTIVE_END_DATE part 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.
In field listings, the Key chip marks a key field — a member of the documented primary key or of a documented unique index.

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.WOOperationTransactionExtractPVO
    OTBI: Manufacturing - Actual Production Real Time

    Operation (quantity move) transactions data store — keyed on WoOperationTransactionId; the completion-transaction subject area is its real-time surface.

    Oracle data-store documentation (opens in new tab)

Fields

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1WO_OPERATION_TRANSACTION_IDSurrogate key of the shop-floor eventNUMBER
Key
2TRANSACTION_TYPE_CODEEvent type, derived from the from/to dispatch statesVARCHAR2
ORA_WIE_OP_TRANSACTION_TYPE
3TRANSACTION_DATEWhen the event was reportedTIMESTAMP
4TRANSACTION_QUANTITYQuantity moved by this eventNUMBER
5TRANSACTION_UOM_CODEUOM of the transacted quantityVARCHAR2
6PRIMARY_QUANTITYQuantity converted to the primary UOMNUMBER
7ORGANIZATION_IDPlantNUMBER
8WORK_ORDER_IDWork order contextNUMBER
9WO_OPERATION_IDOperation the product is transacted fromNUMBER
10FROM_DISPATCH_STATESource dispatch state (ready, complete, scrap, reject…)VARCHAR2
ORA_WIE_DISPATCH_STATE
11TO_DISPATCH_STATEDestination dispatch stateVARCHAR2
ORA_WIE_DISPATCH_STATE
12REASON_CODEScrap/reject reasonVARCHAR2
13INVENTORY_ITEM_IDPrimary product on the work orderNUMBER
14INV_TRANSACTION_IDThe inventory ledger row a completion wrote — the documented link into stockNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of WIE_OPERATION_TRANSACTIONS 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_TRANSACTION_ID>, <watermark>

-- ============================================================
-- Table  : WIE_OPERATION_TRANSACTIONS — The shop-floor product ledger — one row per movement of primary-product quantity through operation dispatch states: completions, moves, scrap, reject, and their reversals
-- Purpose: Column-selected read of WIE_OPERATION_TRANSACTIONS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + WO_OPERATION_TRANSACTION_ID
-- Caution: The transaction type is really a from-state → to-state pair, and reversals write new rows moving quantity back — net the rows, don't count events
-- 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_TRANSACTION_ID AS "Surrogate key of the shop-floor event",
  t.TRANSACTION_TYPE_CODE AS "Event type, derived from the from/to dispatch states",  -- decode t.TRANSACTION_TYPE_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIE_OP_TRANSACTION_TYPE', LANGUAGE-filtered)
  t.TRANSACTION_DATE AS "When the event was reported",
  t.TRANSACTION_QUANTITY AS "Quantity moved by this event",
  t.TRANSACTION_UOM_CODE AS "UOM of the transacted quantity",
  t.PRIMARY_QUANTITY AS "Quantity converted to the primary UOM",
  t.ORGANIZATION_ID AS "Plant",
  t.WORK_ORDER_ID AS "Work order context",
  t.WO_OPERATION_ID AS "Operation the product is transacted from",
  t.FROM_DISPATCH_STATE AS "Source dispatch state (ready, complete, scrap, reject…)",  -- decode t.FROM_DISPATCH_STATE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIE_DISPATCH_STATE', LANGUAGE-filtered)
  t.TO_DISPATCH_STATE AS "Destination dispatch state",  -- decode t.TO_DISPATCH_STATE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIE_DISPATCH_STATE', LANGUAGE-filtered)
  t.REASON_CODE AS "Scrap/reject reason",
  t.INVENTORY_ITEM_ID AS "Primary product on the work order",
  t.INV_TRANSACTION_ID AS "The inventory ledger row a completion wrote — the documented link into stock"
FROM <catalog>.<schema>.WIE_OPERATION_TRANSACTIONS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.WO_OPERATION_TRANSACTION_ID = <WO_OPERATION_TRANSACTION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.WO_OPERATION_TRANSACTION_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

  • 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_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
  • WIE_OPERATION_TRANSACTIONSINV_MATERIAL_TXNSforeign key · N:1
    ON WIE_OPERATION_TRANSACTIONS.INV_TRANSACTION_ID = INV_MATERIAL_TXNS.TRANSACTION_ID AND WIE_OPERATION_TRANSACTIONS.ORGANIZATION_ID = INV_MATERIAL_TXNS.ORGANIZATION_ID
  • WIE_OPERATION_TRANSACTIONSFND_LOOKUP_VALUESFND lookup decode · N:1
    ON WIE_OPERATION_TRANSACTIONS.TRANSACTION_TYPE_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'ORA_WIE_OP_TRANSACTION_TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'

Browse more Manufacturing tables

More Manufacturing tables

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.