Skip to content
Fusion Reference

WIE_RESOURCE_TRANSACTIONS

Product: WIEtransactionPer inventory org

The resource charge ledger — labor and equipment usage charged (or reversed) against work order operation resources, with full lineage down to the resource assignment

Identity
Module: ManufacturingInventory-org partitioned (ORGANIZATION_ID)
Notes

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
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.

Fields

13 fields · 1 key

13 fields.

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1WO_RESOURCE_TRANSACTION_IDSurrogate key of the resource chargeNUMBER
Key
2TRANSACTION_TYPE_CODECharge vs reversal event typeVARCHAR2
ORA_WIE_TRANSACTION_TYPE
3TRANSACTION_DATEWhen the usage was chargedTIMESTAMP
4TRANSACTION_QUANTITYUsage charged by this eventNUMBER
5TRANSACTION_UOM_CODEUOM of the usageVARCHAR2
6ORGANIZATION_IDPlantNUMBER
7WORK_ORDER_IDWork order — carried directly on this ledger, unlike the requirement tableNUMBER
8WO_OPERATION_IDOperation chargedNUMBER
9WO_OPERATION_RESOURCE_IDThe resource assignment chargedNUMBER
10RESOURCE_IDThe resource usedNUMBER
11WORK_CENTER_IDWork center contextNUMBER
12INVENTORY_ITEM_IDThe work order's product (denormalized)NUMBER
13CST_INTERFACED_FLAGWhether the charge has been handed to cost managementVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

-- ============================================================
-- 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;

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_RESOURCE_TRANSACTIONSWIE_WORK_ORDERS_Bforeign key · N:1
    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_ID
  • WIE_RESOURCE_TRANSACTIONSWIE_WO_OPERATION_RESOURCESforeign key · N:1
    ON 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_ID
  • WIE_RESOURCE_TRANSACTIONSWIS_RESOURCES_Bforeign key · N:1
    ON WIE_RESOURCE_TRANSACTIONS.RESOURCE_ID = WIS_RESOURCES_B.RESOURCE_ID AND WIE_RESOURCE_TRANSACTIONS.ORGANIZATION_ID = WIS_RESOURCES_B.ORGANIZATION_ID
  • WIE_RESOURCE_TRANSACTIONSFND_LOOKUP_VALUESFND lookup decode · N:1
    ON 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>'

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.