Results for “mtl_reservations”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_RESERVATIONS is the core Inventory (INV) table in Oracle E-Business Suite that stores hard and soft reservations of on-hand inventory against demand. Each row links a specific quantity of an item — identified by organization, subinventory, locator, lot, revision, and optionally serial number — to a demand source (such as a sales order, a work in process job, or a shipping requirement) and, where applicable, to a supply source. In Oracle EBS 12.1.1 and 12.2.2, the table is owned by the INV schema and remains a central object for order management, shipping, warehouse management, and manufacturing flows that must guarantee material availability.

The documented primary key is MTL_RESERVATIONS_PK on RESERVATION_ID, with a unique index MTL_RESERVATIONS_U1 on the same column. Both are surrogate-key candidates rather than composite business keys; the true business identity of a reservation is the combination of demand source, item, organization, and material detail. Based on the foreign key topology provided, the heuristic Data Vault classification is satellite-leaning: MTL_RESERVATIONS carries descriptive state (quantities, dates, flags) about a demand/supply relationship rather than acting as a pure hub or link.

Key Information Stored

The 87 documented columns hold reservation detail, demand/supply identity, material control attributes, and audit fields. The most operationally significant columns are:

• RESERVATION_ID — surrogate primary key (MTL_RESERVATIONS_PK, MTL_RESERVATIONS_U1); referenced by many downstream tables.
• ORGANIZATION_ID — inventory organization owning the reservation; FK to MTL_PARAMETERS.
• INVENTORY_ITEM_ID — reserved item; FK to MTL_SYSTEM_ITEMS_B, MTL_LOT_NUMBERS, and MTL_ITEM_REVISIONS_B.
• DEMAND_SOURCE_TYPE_ID / DEMAND_SOURCE_HEADER_ID / DEMAND_SOURCE_LINE_ID — identify the consuming document (e.g., sales order line).
• SUPPLY_SOURCE_TYPE_ID / SUPPLY_SOURCE_HEADER_ID / SUPPLY_SOURCE_LINE_ID — identify the supplying document or receipt.
• RESERVATION_QUANTITY / PRIMARY_RESERVATION_QUANTITY / DETAILED_QUANTITY — reserved quantity in reservation, primary, and detailed UOMs.
• SUBINVENTORY_CODE / LOCATOR_ID / LOT_NUMBER / REVISION / SERIAL_NUMBER — material control dimensions; FKs to MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS.
• REQUIREMENT_DATE / DEMAND_SHIP_DATE — timing drivers for planning and shipping.
• PICK_SLIP_NUMBER / LPN_ID / CONTAINER_LPN_ID — warehouse execution and license plate linkage.
• AUTO_DETAILED / PARTIAL_QUANTITIES_ALLOWED / SHIP_READY_FLAG / STAGED_FLAG / CROSSDOCK_FLAG — behavioral and workflow flags.
• COST_GROUP_ID — FK to CST_COST_GROUPS for cost-level reservations.
• PROJECT_ID / TASK_ID — project-driven reservations.
• LAST_UPDATE_DATE / CREATED_BY / CREATION_DATE — standard audit columns.

Common Use Cases and Queries

Reservations underpin availability checks, backorder processing, pick release, and shop-floor material issuance. Typical reporting identifies reserved quantity by item and organization, or traces a demand source to its reservations.

• Reserved quantity on hand for an item in an organization: SELECT organization_id, inventory_item_id, SUM(reservation_quantity) FROM mtl_reservations GROUP BY organization_id, inventory_item_id;
• Reservations tied to a specific sales order line: filter on DEMAND_SOURCE_TYPE_ID, DEMAND_SOURCE_HEADER_ID, DEMAND_SOURCE_LINE_ID.
• Unstaged reservations for a pick slip: filter on PICK_SLIP_NUMBER with STAGED_FLAG and SHIP_READY_FLAG.
• Reservations by subinventory/locator for cycle-count or replenishment analysis: join to MTL_SECONDARY_INVENTORIES and MTL_ITEM_LOCATIONS.

Related Objects

MTL_RESERVATIONS sits at the center of a dense FK web. Significant referencing tables (children) join on RESERVATION_ID:

• MTL_MATERIAL_TRANSACTIONS — every issue/transfer transaction that consumes a reservation.
• MTL_MATERIAL_TRANSACTIONS_TEMP — pending transactions awaiting processing.
• MTL_SERIAL_NUMBERS — serialized material tied to reservations.
• WMS_TRANSACTIONS_TEMP, WMS_MATERIAL_TXN_TRACE, WMS_CARTONIZATION_TEMP — Warehouse Management execution.
• ASO_SHIPMENTS — shipping/reservation linkage.
• MRP_GROSS_REQUIREMENTS, MRP_SCHEDULE_DATES, MSC_DEMANDS, MSC_ST_DEMANDS — planning demand and scheduling.
• CSP_REQUIREMENT_LINES — referenced twice, on RESERVATION_ID and LOCAL_RESERVATION_ID.
• GMO_MATERIAL_DISPENSES, GMO_DISPENSING_PLANNING, GMD_MATERIAL_DETAILS_GTMP — process manufacturing dispensing.

Parent lookups include MTL_PARAMETERS, MTL_SYSTEM_ITEMS_B, MTL_LOT_NUMBERS, MTL_ITEM_REVISIONS_B, MTL_SECONDARY_INVENTORIES, MTL_ITEM_LOCATIONS, MTL_TXN_SOURCE_TYPES, and CST_COST_GROUPS.