Search Results MTL_RESERVATIONS

Overview

The MTL_RESERVATIONS table is a core transactional data structure within the Oracle E-Business Suite Inventory (INV) module. It serves as the central repository for all material reservation records. A reservation is a formal allocation of on-hand inventory to a specific demand, such as a sales order line, work order job, or internal requisition. This mechanism ensures that committed inventory is not available for other transactions, thereby preventing overselling and enabling accurate available-to-promise (ATP) calculations. The table is critical for managing the supply chain fulfillment process, linking supply sources to demand sources within a specific organizational and subinventory context.

Key Information Stored

The table's primary key is RESERVATION_ID, which uniquely identifies each reservation record. Key columns define the relationship between supply and demand, and the specific inventory characteristics being reserved. Major columns include DEMAND_SOURCE_TYPE_ID and DEMAND_SOURCE_HEADER_ID/LINE_ID, which identify the nature and specific instance of the consuming entity (e.g., a sales order). Conversely, SUPPLY_SOURCE_TYPE_ID and SUPPLY_SOURCE_HEADER_ID/LINE_ID identify the providing entity. The table stores detailed inventory attributes for the reserved material: ORGANIZATION_ID, INVENTORY_ITEM_ID, SUBINVENTORY_CODE, LOCATOR_ID, LOT_NUMBER, and REVISION. The REQUIRED_QUANTITY and RESERVATION_QUANTITY columns track the amount needed and the amount actually reserved, which can differ in partial reservation scenarios.

Common Use Cases and Queries

This table is central to inquiries about material availability and commitment status. Common operational and reporting queries include identifying all reservations for a specific sales order to understand fulfillment status, or checking reservations against a particular lot or subinventory for cycle count reconciliation. Troubleshooting often involves querying reservations linked to a stuck transaction in MTL_MATERIAL_TRANSACTIONS_TEMP. A typical diagnostic SQL pattern is:

• SELECT mr.reservation_id, mr.demand_source_line_id, mr.inventory_item_id, mr.required_quantity, mr.reservation_quantity FROM mtl_reservations mr WHERE mr.demand_source_header_id = <order_header_id>;

Reservations are primarily created, updated, and deleted via public APIs such as INV_RESERVATION_PUB, rather than through direct DML, to maintain data integrity.

Related Objects

As indicated by its foreign keys, MTL_RESERVATIONS has strong referential integrity with numerous foundational inventory tables. It references MTL_SYSTEM_ITEMS_B for the item definition, MTL_SECONDARY_INVENTORIES for the subinventory, MTL_ITEM_LOCATIONS for the locator, and MTL_LOT_NUMBERS and MTL_ITEM_REVISIONS_B for lot and revision control. It links to MTL_TXN_SOURCE_TYPES to classify demand and supply sources. Crucially, it is referenced by the CSP_REQUIREMENT_LINES table for Consumption Advice processing in Advanced Planning and by MTL_MATERIAL_TRANSACTIONS_TEMP, where the RESERVATION_ID is populated during transaction processing to consume the reservation. This network of relationships underscores its pivotal role in the inventory transaction flow.