Skip to content
EBS Reference

MTL_RESERVATIONS

Schema: INVtransactionPer inventory org

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

Module: InventoryInventory-org partitioned (ORGANIZATION_ID)
Notes

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.
In field listings, K marks a primary-key field.

Fields

15 fields · 1 key

Table fields: position, field name, description, data type, and flags. 15 fields.
#FieldDescriptionTypeFlags
1RESERVATION_IDSurrogate key of the reservationNUMBER
Key
2ORGANIZATION_IDInventory organizationNUMBER
3INVENTORY_ITEM_IDItem idNUMBER
4DEMAND_SOURCE_TYPE_IDWhat kind of demand holds the reservation (sales order, most commonly)NUMBER
5DEMAND_SOURCE_HEADER_IDThe demand document's header id — interpretation depends on the source typeNUMBER
6DEMAND_SOURCE_LINE_IDThe demand document's line idNUMBER
7SUPPLY_SOURCE_TYPE_IDWhat supplies the reservation — on-hand or an expected supply documentNUMBER
8SUPPLY_SOURCE_HEADER_IDThe supplying document's header id, when not against on-handNUMBER
9RESERVATION_QUANTITYReserved quantity in the reservation UOMNUMBER
10PRIMARY_RESERVATION_QUANTITYReserved quantity in the item's primary UOM — the column to aggregateNUMBER
11RESERVATION_UOM_CODEThe UOM the reservation was placed inVARCHAR2
12SUBINVENTORY_CODESubinventory the reservation is pinned to, when detailedVARCHAR2
13LOCATOR_IDLocator the reservation is pinned toNUMBER
14LOT_NUMBERLot the reservation is pinned toVARCHAR2
15REQUIREMENT_DATEWhen the demand needs the materialDATE
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.

Query parameters
-- ============================================================
-- 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

  • MTL_RESERVATIONSMTL_SYSTEM_ITEMS_Bforeign key · N:1
    ON MTL_RESERVATIONS.INVENTORY_ITEM_ID = MTL_SYSTEM_ITEMS_B.INVENTORY_ITEM_ID AND MTL_RESERVATIONS.ORGANIZATION_ID = MTL_SYSTEM_ITEMS_B.ORGANIZATION_ID
  • MTL_RESERVATIONSMTL_PARAMETERSforeign key · N:1
    ON MTL_RESERVATIONS.ORGANIZATION_ID = MTL_PARAMETERS.ORGANIZATION_ID
  • MTL_RESERVATIONSOE_ORDER_LINES_ALLforeign key · N:1
    ON MTL_RESERVATIONS.DEMAND_SOURCE_LINE_ID = OE_ORDER_LINES_ALL.LINE_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.