WIE_RESOURCE_TRANSACTIONS
Product: WIEtransactionPer inventory orgThe resource charge ledger — labor and equipment usage charged (or reversed) against work order operation resources, with full lineage down to the resource assignment
Unlike the requirement table, this ledger carries WORK_ORDER_ID directly plus the operation and assignment ids. CST_INTERFACED_FLAG marks the costing handoff; labor and equipment instances ride separate id columns.
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.WOResourceTransactionExtractPVOOTBI: Manufacturing - Resource Usage Real Time
Resource charge transactions data store — keyed on WoResourceTransactionId.
Oracle data-store documentation →
Fields
13 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WO_RESOURCE_TRANSACTION_ID | Surrogate key of the resource charge | NUMBER | Key |
| 2 | TRANSACTION_TYPE_CODE | Charge vs reversal event type | VARCHAR2 | ORA_WIE_TRANSACTION_TYPE |
| 3 | TRANSACTION_DATE | When the usage was charged | TIMESTAMP | |
| 4 | TRANSACTION_QUANTITY | Usage charged by this event | NUMBER | |
| 5 | TRANSACTION_UOM_CODE | UOM of the usage | VARCHAR2 | |
| 6 | ORGANIZATION_ID | Plant | NUMBER | |
| 7 | WORK_ORDER_ID | Work order — carried directly on this ledger, unlike the requirement table | NUMBER | |
| 8 | WO_OPERATION_ID | Operation charged | NUMBER | |
| 9 | WO_OPERATION_RESOURCE_ID | The resource assignment charged | NUMBER | |
| 10 | RESOURCE_ID | The resource used | NUMBER | |
| 11 | WORK_CENTER_ID | Work center context | NUMBER | |
| 12 | INVENTORY_ITEM_ID | The work order's product (denormalized) | NUMBER | |
| 13 | CST_INTERFACED_FLAG | Whether the charge has been handed to cost management | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading the BICC-landed copy of WIE_RESOURCE_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_RESOURCE_TRANSACTIONS — The resource charge ledger — labor and equipment usage charged (or reversed) against work order operation resources, with full lineage down to the resource assignment
-- Purpose: Column-selected read of WIE_RESOURCE_TRANSACTIONS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + WO_RESOURCE_TRANSACTION_ID
-- 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_RESOURCE_TRANSACTION_ID AS "Surrogate key of the resource charge",
t.TRANSACTION_TYPE_CODE AS "Charge vs reversal event type", -- decode t.TRANSACTION_TYPE_CODE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIE_TRANSACTION_TYPE', LANGUAGE-filtered)
t.TRANSACTION_DATE AS "When the usage was charged",
t.TRANSACTION_QUANTITY AS "Usage charged by this event",
t.TRANSACTION_UOM_CODE AS "UOM of the usage",
t.ORGANIZATION_ID AS "Plant",
t.WORK_ORDER_ID AS "Work order — carried directly on this ledger, unlike the requirement table",
t.WO_OPERATION_ID AS "Operation charged",
t.WO_OPERATION_RESOURCE_ID AS "The resource assignment charged",
t.RESOURCE_ID AS "The resource used",
t.WORK_CENTER_ID AS "Work center context",
t.INVENTORY_ITEM_ID AS "The work order's product (denormalized)",
t.CST_INTERFACED_FLAG AS "Whether the charge has been handed to cost management"
FROM <catalog>.<schema>.WIE_RESOURCE_TRANSACTIONS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the business unit — see quirks guide #item-org-striping
-- AND t.WO_RESOURCE_TRANSACTION_ID = <WO_RESOURCE_TRANSACTION_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- the column incremental BICC extracts key on
ORDER BY t.WO_RESOURCE_TRANSACTION_ID;5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WO_RESOURCE_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_RESOURCE_TRANSACTIONS.WORK_ORDER_ID = WIE_WORK_ORDERS_B.WORK_ORDER_ID AND WIE_RESOURCE_TRANSACTIONS.ORGANIZATION_ID = WIE_WORK_ORDERS_B.ORGANIZATION_IDON WIE_RESOURCE_TRANSACTIONS.WO_OPERATION_RESOURCE_ID = WIE_WO_OPERATION_RESOURCES.WO_OPERATION_RESOURCE_ID AND WIE_RESOURCE_TRANSACTIONS.ORGANIZATION_ID = WIE_WO_OPERATION_RESOURCES.ORGANIZATION_IDON WIE_RESOURCE_TRANSACTIONS.RESOURCE_ID = WIS_RESOURCES_B.RESOURCE_ID AND WIE_RESOURCE_TRANSACTIONS.ORGANIZATION_ID = WIS_RESOURCES_B.ORGANIZATION_IDON WIE_RESOURCE_TRANSACTIONS.TRANSACTION_TYPE_CODE = FND_LOOKUP_VALUES.LOOKUP_CODE AND FND_LOOKUP_VALUES.LOOKUP_TYPE = 'ORA_WIE_TRANSACTION_TYPE' AND FND_LOOKUP_VALUES.LANGUAGE = '<language>'