MTL_RESERVATIONS
Schema: INVtransactionPer inventory orgFirm 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
This is the R12 reservations table. Legacy reservation rows also exist in MTL_DEMAND — don't count both.
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
15 fields · 1 key
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | RESERVATION_ID | Surrogate key of the reservation | NUMBER | Key |
| 2 | ORGANIZATION_ID | Inventory organization | NUMBER | |
| 3 | INVENTORY_ITEM_ID | Item id | NUMBER | |
| 4 | DEMAND_SOURCE_TYPE_ID | What kind of demand holds the reservation (sales order, most commonly) | NUMBER | |
| 5 | DEMAND_SOURCE_HEADER_ID | The demand document's header id — interpretation depends on the source type | NUMBER | |
| 6 | DEMAND_SOURCE_LINE_ID | The demand document's line id | NUMBER | |
| 7 | SUPPLY_SOURCE_TYPE_ID | What supplies the reservation — on-hand or an expected supply document | NUMBER | |
| 8 | SUPPLY_SOURCE_HEADER_ID | The supplying document's header id, when not against on-hand | NUMBER | |
| 9 | RESERVATION_QUANTITY | Reserved quantity in the reservation UOM | NUMBER | |
| 10 | PRIMARY_RESERVATION_QUANTITY | Reserved quantity in the item's primary UOM — the column to aggregate | NUMBER | |
| 11 | RESERVATION_UOM_CODE | The UOM the reservation was placed in | VARCHAR2 | |
| 12 | SUBINVENTORY_CODE | Subinventory the reservation is pinned to, when detailed | VARCHAR2 | |
| 13 | LOCATOR_ID | Locator the reservation is pinned to | NUMBER | |
| 14 | LOT_NUMBER | Lot the reservation is pinned to | VARCHAR2 | |
| 15 | REQUIREMENT_DATE | When the demand needs the material | DATE | Filter date |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading MTL_RESERVATIONSon 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_RESERVATIONS — Firm 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
-- Purpose: Column-selected read of MTL_RESERVATIONS — auto-generated from field metadata
-- Grain : One row per inventory org (ORGANIZATION_ID) + RESERVATION_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.RESERVATION_ID AS "Surrogate key of the reservation",
t.ORGANIZATION_ID AS "Inventory organization",
t.INVENTORY_ITEM_ID AS "Item id",
t.DEMAND_SOURCE_TYPE_ID AS "What kind of demand holds the reservation (sales order, most commonly)",
t.DEMAND_SOURCE_HEADER_ID AS "The demand document's header id — interpretation depends on the source type",
t.DEMAND_SOURCE_LINE_ID AS "The demand document's line id",
t.SUPPLY_SOURCE_TYPE_ID AS "What supplies the reservation — on-hand or an expected supply document",
t.SUPPLY_SOURCE_HEADER_ID AS "The supplying document's header id, when not against on-hand",
t.RESERVATION_QUANTITY AS "Reserved quantity in the reservation UOM",
t.PRIMARY_RESERVATION_QUANTITY AS "Reserved quantity in the item's primary UOM — the column to aggregate",
t.RESERVATION_UOM_CODE AS "The UOM the reservation was placed in",
t.SUBINVENTORY_CODE AS "Subinventory the reservation is pinned to, when detailed",
t.LOCATOR_ID AS "Locator the reservation is pinned to",
t.LOT_NUMBER AS "Lot the reservation is pinned to",
t.REQUIREMENT_DATE AS "When the demand needs the material"
FROM <catalog>.<schema>.MTL_RESERVATIONS t
WHERE
t.ORGANIZATION_ID = <inventory_org_id> -- inventory org, NOT the operating unit — see quirks guide #two-orgs
-- AND t.RESERVATION_ID = <RESERVATION_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.RESERVATION_ID;7 parameters not filled: <catalog>, <schema>, <inventory_org_id>, <RESERVATION_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_RESERVATIONS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_RESERVATIONS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_IDON MTL_RESERVATIONS.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_IDON MTL_RESERVATIONS.DEMAND_SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_ID