MTL_DEMAND
Schema: INVtransactionPer inventory orgThe 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
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
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - 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 (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
12 fields · 1 key
12 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DEMAND_ID | Surrogate key of the demand row | NUMBER | Primary-key field |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 3 | INVENTORY_ITEM_ID | Item id | NUMBER | |
| 4 | DEMAND_SOURCE_TYPE | What kind of document generated the demand | NUMBER | |
| 5 | DEMAND_SOURCE_HEADER_ID | The demand document's header id | NUMBER | |
| 6 | DEMAND_SOURCE_LINE | The demand document's line reference — a VARCHAR2, so numeric line-id joins need a cast | VARCHAR2 | |
| 7 | UOM_CODE | UOM the demand is expressed in | VARCHAR2 | |
| 8 | LINE_ITEM_QUANTITY | Demand quantity in the document UOM | NUMBER | |
| 9 | PRIMARY_UOM_QUANTITY | Demand quantity in the item's primary UOM | NUMBER | |
| 10 | REQUIREMENT_DATE | When the demand needs the material | DATE | The table's primary analysis date — a real DATE column, no conversion needed |
| 11 | RESERVATION_TYPE | Row flavor — summary demand, open demand, or a legacy reservation | NUMBER | |
| 12 | COMPLETED_QUANTITY | How much of the demand has been satisfied | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading MTL_DEMAND on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <DEMAND_ID>, <DATE_FROM>, <DATE_TO>, <watermark>
-- ============================================================
-- 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.DEMAND_ID = <DEMAND_ID>
-- 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;Verified September 2026
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 MTL_DEMAND.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_DEMAND.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
More Inventory tables
- MTL_ITEM_LOCATIONSThe stock locator master — the physical bin/row/rack positions inside a subinventory, with the locator name held as SEGMENTn flexfield columns
- MTL_LOT_NUMBERSThe lot master — definition, genealogy (parent lot), status, grade, and the origination/expiration/retest dates for every lot, keyed by item + organization + lot number
- MTL_MATERIAL_TRANSACTIONSThe material transaction ledger — one row per inventory movement or cost update, classified by transaction type, action, and source type, with quantity, date, and the document reference that caused it; the reconciliation backbone for every stock question
- MTL_ONHAND_QUANTITIES_DETAILThe on-hand balance detail — receipt-level slices of stock per item, org, subinventory, locator, lot, and revision, consumed in FIFO order as material issues
- MTL_PARAMETERSInventory organization parameters — one row per inventory org, holding the short org code, the master org it points to, and the org's costing method and locator/lot/serial control defaults; the org list every ORGANIZATION_ID resolves against
- MTL_RESERVATIONSFirm reservations tying a demand source (a sales order line, most commonly) to a supply source (on-hand or expected supply) for an item in an org, optionally pinned down to subinventory, locator, and lot