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
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

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.WOOperationMaterialExtractPVO
    OTBI: Manufacturing - Material Usage Real Time

    Work Order Operation Materials data store — keyed on WoOperationMaterialId.

    Oracle data-store documentation →

Fields

16 fields · 1 key

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

5 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <WO_OPERATION_MATERIAL_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

  • 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 Manufacturingtables →

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.