Skip to content
Fusion Reference

WIE_WO_OPERATION_RESOURCES

Product: WIEtransactionPer inventory org

Labor and equipment requirements for each work order operation — usage rate, required and actual usage, assigned units, and charge behavior

Notes

No WORK_ORDER_ID column — reaching the work order takes the hop through the operation. SCHEDULED_FLAG is a lookup-coded VARCHAR2, not Y/N; ACTUAL_RESOURCE_USAGE is a maintained rollup of the resource ledger.

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.

Header & line

WIE_WO_OPERATION_RESOURCES lines join back to their header WIE_WO_OPERATIONS_B — and the org column — so a line never fans out.

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

14 fields · 1 key

14 fields.

Table fields: position, field name, description, data type, and flags. 14 fields.
#FieldDescriptionTypeFlags
1WO_OPERATION_RESOURCE_IDSurrogate key of the resource assignmentNUMBER
Key
2WO_OPERATION_IDParent operation — there is NO work-order column here; hop through the operationNUMBER
3ORGANIZATION_IDPlantNUMBER
4RESOURCE_SEQ_NUMBERSequence resources work in — equal numbers run parallelNUMBER
5RESOURCE_IDThe labor/equipment resource assignedNUMBER
6WORK_CENTER_IDWork center the resource belongs toNUMBER
7REQUIRED_USAGETotal required usage (rate × basis × order quantity)NUMBER
8USAGE_RATEUsage per unit of assemblyNUMBER
9ACTUAL_RESOURCE_USAGEActual charged usage — a maintained rollup of the resource ledgerNUMBER
10UOM_CODEUOM of the usage (typically hours)VARCHAR2
11BASIS_TYPEFixed vs variable usage basisVARCHAR2
EGP_BOM_BASIS_TYPE
12ASSIGNED_UNITSNumber of resource units assignedNUMBER
13CHARGE_TYPEManual vs automatic charging pointVARCHAR2
ORA_WIS_CHARGE_TYPE
14PRINCIPAL_FLAGExactly one principal resource among parallel resourcesVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

-- ============================================================
-- Table  : WIE_WO_OPERATION_RESOURCES — Labor and equipment requirements for each work order operation — usage rate, required and actual usage, assigned units, and charge behavior
-- Purpose: Column-selected read of WIE_WO_OPERATION_RESOURCES — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + WO_OPERATION_RESOURCE_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_OPERATION_RESOURCE_ID AS "Surrogate key of the resource assignment",
  t.WO_OPERATION_ID AS "Parent operation — there is NO work-order column here; hop through the operation",
  t.ORGANIZATION_ID AS "Plant",
  t.RESOURCE_SEQ_NUMBER AS "Sequence resources work in — equal numbers run parallel",
  t.RESOURCE_ID AS "The labor/equipment resource assigned",
  t.WORK_CENTER_ID AS "Work center the resource belongs to",
  t.REQUIRED_USAGE AS "Total required usage (rate × basis × order quantity)",
  t.USAGE_RATE AS "Usage per unit of assembly",
  t.ACTUAL_RESOURCE_USAGE AS "Actual charged usage — a maintained rollup of the resource ledger",
  t.UOM_CODE AS "UOM of the usage (typically hours)",
  t.BASIS_TYPE AS "Fixed vs variable usage basis",  -- decode t.BASIS_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'EGP_BOM_BASIS_TYPE', LANGUAGE-filtered)
  t.ASSIGNED_UNITS AS "Number of resource units assigned",
  t.CHARGE_TYPE AS "Manual vs automatic charging point",  -- decode t.CHARGE_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_CHARGE_TYPE', LANGUAGE-filtered)
  t.PRINCIPAL_FLAG AS "Exactly one principal resource among parallel resources"
FROM <catalog>.<schema>.WIE_WO_OPERATION_RESOURCES t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.WO_OPERATION_RESOURCE_ID = <WO_OPERATION_RESOURCE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.WO_OPERATION_RESOURCE_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_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_OPERATION_RESOURCESWIS_RESOURCES_Bforeign key · N:1
    ON WIE_WO_OPERATION_RESOURCES.RESOURCE_ID = WIS_RESOURCES_B.RESOURCE_ID AND WIE_WO_OPERATION_RESOURCES.ORGANIZATION_ID = WIS_RESOURCES_B.ORGANIZATION_ID
  • WIE_WO_OPERATION_RESOURCESWIS_WORK_CENTERS_Bforeign key · N:1
    ON WIE_WO_OPERATION_RESOURCES.WORK_CENTER_ID = WIS_WORK_CENTERS_B.WORK_CENTER_ID AND WIE_WO_OPERATION_RESOURCES.ORGANIZATION_ID = WIS_WORK_CENTERS_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

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.