WIE_WO_OPERATION_MATERIALS
Product: WIEtransactionPer inventory orgComponent 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
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.
- 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 withINVENTORY_ITEM_IDon 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_IDon the GL journal tables), or a named business-unit column (PRC_BU_ID/REQ_BU_IDin 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
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows. - Date-effective
- This is an
_Ftable — one row per entity per effectivity window, withEFFECTIVE_START_DATEandEFFECTIVE_END_DATEpart 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.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
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.
- FscmTopModelAM.ScmExtractAM.WieBiccExtractAM.WOOperationMaterialExtractPVOOTBI: Manufacturing - Material Usage Real Time
Work Order Operation Materials data store — keyed on WoOperationMaterialId.
Oracle data-store documentation (opens in new tab)
Fields
16 fields · 1 key
16 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | WO_OPERATION_MATERIAL_ID | Surrogate key of the material line | NUMBER | Key |
| 2 | WO_OPERATION_ID | Parent operation | NUMBER | |
| 3 | WORK_ORDER_ID | Parent work order (denormalized) | NUMBER | |
| 4 | ORGANIZATION_ID | Plant | NUMBER | |
| 5 | MATERIAL_SEQ_NUMBER | Order of consumption within the operation | NUMBER | |
| 6 | INVENTORY_ITEM_ID | Component item required | NUMBER | |
| 7 | QUANTITY_PER_PRODUCT | Usage per unit of assembly, from the work definition | NUMBER | |
| 8 | QUANTITY | Total requirement for the operation — plainly QUANTITY, there is no REQUIRED_QUANTITY | NUMBER | |
| 9 | ISSUED_QUANTITY | Quantity issued so far — a counter; issue events are inventory transactions | NUMBER | |
| 10 | ALLOCATED_QUANTITY | Quantity allocated by component picking | NUMBER | |
| 11 | PICKED_QUANTITY | Pick-confirmed quantity from move orders | NUMBER | |
| 12 | UOM_CODE | UOM of the requirement | VARCHAR2 | |
| 13 | REQUIRED_DATE | When the material is needed at the operation | TIMESTAMP | |
| 14 | SUPPLY_TYPE | Push, operation pull, or assembly pull supply | VARCHAR2 | |
| 15 | MATERIAL_TYPE | Input material classification | VARCHAR2 | ORA_WIS_WD_INPUT_MATERIAL |
| 16 | BASIS_TYPE | Fixed vs variable usage basis | VARCHAR2 | 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.
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
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_IDON 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
More Manufacturing tables
- WIE_WO_OPERATION_RESOURCESLabor and equipment requirements for each work order operation — usage rate, required and actual usage, assigned units, and charge behavior
- WIE_WO_OPERATIONS_BWork order operations — one row per execution step with its sequence, work center, count-point behavior, and the quantity balances sitting at each dispatch state
- WIE_WORK_ORDERS_BThe work order header — the primary product being built, the work definition version it was created from, the build quantity, status, and planned/actual execution dates
- WIS_RESOURCES_BThe production resource master — each row an equipment or labor resource that performs operations at work centers, unique per plant by resource code
- WIS_WD_OPERATIONS_BWork definition operations — the ordered, date-effective steps of a work definition, each pointing at the work center where it runs and optionally at a reusable standard operation
- WIS_WD_VERSIONSWork definition versions — dated snapshots of the version-controlled header attributes, with the approval status gating which version execution uses