WIE_OPERATION_TRANSACTIONS
Product: WIEtransactionPer inventory orgThe shop-floor product ledger — one row per movement of primary-product quantity through operation dispatch states: completions, moves, scrap, reject, and their reversals
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
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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
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.WOOperationTransactionExtractPVOOTBI: 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 →
Fields
14 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WO_OPERATION_TRANSACTION_ID | Surrogate key of the shop-floor event | NUMBER | Key |
| 2 | TRANSACTION_TYPE_CODE | Event type, derived from the from/to dispatch states | VARCHAR2 | ORA_WIE_OP_TRANSACTION_TYPE |
| 3 | TRANSACTION_DATE | When the event was reported | TIMESTAMP | |
| 4 | TRANSACTION_QUANTITY | Quantity moved by this event | NUMBER | |
| 5 | TRANSACTION_UOM_CODE | UOM of the transacted quantity | VARCHAR2 | |
| 6 | PRIMARY_QUANTITY | Quantity converted to the primary UOM | NUMBER | |
| 7 | ORGANIZATION_ID | Plant | NUMBER | |
| 8 | WORK_ORDER_ID | Work order context | NUMBER | |
| 9 | WO_OPERATION_ID | Operation the product is transacted from | NUMBER | |
| 10 | FROM_DISPATCH_STATE | Source dispatch state (ready, complete, scrap, reject…) | VARCHAR2 | ORA_WIE_DISPATCH_STATE |
| 11 | TO_DISPATCH_STATE | Destination dispatch state | VARCHAR2 | ORA_WIE_DISPATCH_STATE |
| 12 | REASON_CODE | Scrap/reject reason | VARCHAR2 | |
| 13 | INVENTORY_ITEM_ID | Primary product on the work order | NUMBER | |
| 14 | INV_TRANSACTION_ID | The inventory ledger row a completion wrote — the documented link into stock | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIE_OPERATION_TRANSACTIONSon 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.
-- ============================================================
-- 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;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WO_OPERATION_TRANSACTION_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
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_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_IDON WIE_OPERATION_TRANSACTIONS.INV_TRANSACTION_ID = INV_MATERIAL_TXNS.TRANSACTION_ID AND WIE_OPERATION_TRANSACTIONS.ORGANIZATION_ID = INV_MATERIAL_TXNS.ORGANIZATION_IDON 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>'