Skip to content
Fusion Reference

WIE_WO_OPERATION_MATERIALS

Product: WIEtransactionPer inventory org

Component requirements of each work order operation — one row per material line with per-assembly usage, total requirement, supply method, and running issued/allocated/picked counters

Notes

The total requirement is plainly QUANTITY (no REQUIRED_QUANTITY column), and there is no operation-sequence column — join the operation for it. Issue events live in the inventory transaction ledger; the counters here are balances.

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

16 fields · 1 key

16 fields.

Table fields: position, field name, description, data type, and flags. 16 fields.
#FieldDescriptionTypeFlags
1WO_OPERATION_MATERIAL_IDSurrogate key of the material lineNUMBER
Key
2WO_OPERATION_IDParent operationNUMBER
3WORK_ORDER_IDParent work order (denormalized)NUMBER
4ORGANIZATION_IDPlantNUMBER
5MATERIAL_SEQ_NUMBEROrder of consumption within the operationNUMBER
6INVENTORY_ITEM_IDComponent item requiredNUMBER
7QUANTITY_PER_PRODUCTUsage per unit of assembly, from the work definitionNUMBER
8QUANTITYTotal requirement for the operation — plainly QUANTITY, there is no REQUIRED_QUANTITYNUMBER
9ISSUED_QUANTITYQuantity issued so far — a counter; issue events are inventory transactionsNUMBER
10ALLOCATED_QUANTITYQuantity allocated by component pickingNUMBER
11PICKED_QUANTITYPick-confirmed quantity from move ordersNUMBER
12UOM_CODEUOM of the requirementVARCHAR2
13REQUIRED_DATEWhen the material is needed at the operationTIMESTAMP
14SUPPLY_TYPEPush, operation pull, or assembly pull supplyVARCHAR2
15MATERIAL_TYPEInput material classificationVARCHAR2
ORA_WIS_WD_INPUT_MATERIAL
16BASIS_TYPEFixed vs variable usage basisVARCHAR2
EGP_BOM_BASIS_TYPE

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

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

-- ============================================================
-- Table  : WIE_WO_OPERATION_MATERIALS — Component requirements of each work order operation — one row per material line with per-assembly usage, total requirement, supply method, and running issued/allocated/picked counters
-- Purpose: Column-selected read of WIE_WO_OPERATION_MATERIALS — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + WO_OPERATION_MATERIAL_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_MATERIAL_ID AS "Surrogate key of the material line",
  t.WO_OPERATION_ID AS "Parent operation",
  t.WORK_ORDER_ID AS "Parent work order (denormalized)",
  t.ORGANIZATION_ID AS "Plant",
  t.MATERIAL_SEQ_NUMBER AS "Order of consumption within the operation",
  t.INVENTORY_ITEM_ID AS "Component item required",
  t.QUANTITY_PER_PRODUCT AS "Usage per unit of assembly, from the work definition",
  t.QUANTITY AS "Total requirement for the operation — plainly QUANTITY, there is no REQUIRED_QUANTITY",
  t.ISSUED_QUANTITY AS "Quantity issued so far — a counter; issue events are inventory transactions",
  t.ALLOCATED_QUANTITY AS "Quantity allocated by component picking",
  t.PICKED_QUANTITY AS "Pick-confirmed quantity from move orders",
  t.UOM_CODE AS "UOM of the requirement",
  t.REQUIRED_DATE AS "When the material is needed at the operation",
  t.SUPPLY_TYPE AS "Push, operation pull, or assembly pull supply",
  t.MATERIAL_TYPE AS "Input material classification",  -- decode t.MATERIAL_TYPE via FND_LOOKUP_VALUES (LOOKUP_TYPE = 'ORA_WIS_WD_INPUT_MATERIAL', LANGUAGE-filtered)
  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)
FROM <catalog>.<schema>.WIE_WO_OPERATION_MATERIALS t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the business unit — see quirks guide #item-org-striping
  -- AND t.WO_OPERATION_MATERIAL_ID = <WO_OPERATION_MATERIAL_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.WO_OPERATION_MATERIAL_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_MATERIALSheader line · 1:N
    ON WIE_WO_OPERATIONS_B.WO_OPERATION_ID = WIE_WO_OPERATION_MATERIALS.WO_OPERATION_ID AND WIE_WO_OPERATIONS_B.ORGANIZATION_ID = WIE_WO_OPERATION_MATERIALS.ORGANIZATION_ID
  • WIE_WO_OPERATION_MATERIALSEGP_SYSTEM_ITEMS_Bforeign key · N:1
    ON WIE_WO_OPERATION_MATERIALS.INVENTORY_ITEM_ID = EGP_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND WIE_WO_OPERATION_MATERIALS.ORGANIZATION_ID = EGP_SYSTEM_ITEMS_B.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.