Skip to content
EBS Reference

MTL_DEMAND

Schema: INVtransactionPer inventory org

The legacy demand picture used by ATP and planning — summary demand, open demand, and pre-R12 reservation rows for an item in an org, keyed to the order document that generated them

Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
Notes

In R12 most reservation traffic lives in MTL_RESERVATIONS; treat this as the ATP/planning side. DEMAND_SOURCE_LINE is a VARCHAR2 — joins to numeric order-line ids need an explicit cast.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

12 fields · 1 key

Table fields: position, field name, description, data type, and flags. 12 fields.
#FieldDescriptionTypeFlags
1DEMAND_IDSurrogate key of the demand rowNUMBER
Key
2ORGANIZATION_IDInventory organizationNUMBER
3INVENTORY_ITEM_IDItem idNUMBER
4DEMAND_SOURCE_TYPEWhat kind of document generated the demandNUMBER
5DEMAND_SOURCE_HEADER_IDThe demand document's header idNUMBER
6DEMAND_SOURCE_LINEThe demand document's line reference — a VARCHAR2, so numeric line-id joins need a castVARCHAR2
7UOM_CODEUOM the demand is expressed inVARCHAR2
8LINE_ITEM_QUANTITYDemand quantity in the document UOMNUMBER
9PRIMARY_UOM_QUANTITYDemand quantity in the item's primary UOMNUMBER
10REQUIREMENT_DATEWhen the demand needs the materialDATE
Filter date
11RESERVATION_TYPERow flavor — summary demand, open demand, or a legacy reservationNUMBER
12COMPLETED_QUANTITYHow much of the demand has been satisfiedNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading MTL_DEMANDon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark 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  : MTL_DEMAND — The legacy demand picture used by ATP and planning — summary demand, open demand, and pre-R12 reservation rows for an item in an org, keyed to the order document that generated them
-- Purpose: Column-selected read of MTL_DEMAND — auto-generated from field metadata
-- Grain  : One row per inventory org (ORGANIZATION_ID) + DEMAND_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. 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.DEMAND_ID AS "Surrogate key of the demand row",
  t.ORGANIZATION_ID AS "Inventory organization",
  t.INVENTORY_ITEM_ID AS "Item id",
  t.DEMAND_SOURCE_TYPE AS "What kind of document generated the demand",
  t.DEMAND_SOURCE_HEADER_ID AS "The demand document's header id",
  t.DEMAND_SOURCE_LINE AS "The demand document's line reference — a VARCHAR2, so numeric line-id joins need a cast",
  t.UOM_CODE AS "UOM the demand is expressed in",
  t.LINE_ITEM_QUANTITY AS "Demand quantity in the document UOM",
  t.PRIMARY_UOM_QUANTITY AS "Demand quantity in the item's primary UOM",
  t.REQUIREMENT_DATE AS "When the demand needs the material",
  t.RESERVATION_TYPE AS "Row flavor — summary demand, open demand, or a legacy reservation",
  t.COMPLETED_QUANTITY AS "How much of the demand has been satisfied"
FROM <catalog>.<schema>.MTL_DEMAND t
WHERE
  t.ORGANIZATION_ID = <inventory_org_id>  -- inventory org, NOT the operating unit — see quirks guide #two-orgs
  -- AND t.REQUIREMENT_DATE >= DATE '<DATE_FROM>'
  -- AND t.REQUIREMENT_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DEMAND_ID;

6 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DATE_FROM>, <DATE_TO>, <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

  • MTL_DEMANDMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON MTL_DEMAND.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_DEMAND.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID

Browse more Inventorytables →

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 E-Business Suite are registered trademarks of Oracle and/or its affiliates.