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
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
Fields
12 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DEMAND_ID | Surrogate key of the demand row | NUMBER | Key |
| 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 | Filter date |
| 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_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.
-- ============================================================
-- 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
ON MTL_DEMAND.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_DEMAND.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID