Search Results mrp_reservations




Overview
Explore in AI Chat

Overview

The MRP_RESERVATIONS table is a core data object within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as the central repository for material reservations generated by the MRP planning engine. When MRP runs, it creates planned orders and purchase requisitions to satisfy net requirements. This table stores the detailed, component-level reservations that link these planned supply orders to specific demand sources, such as discrete jobs, repetitive schedules, or sales orders. Its primary role is to maintain the integrity of the material plan by explicitly recording how future supply is allocated to meet future demand, which is critical for accurate material availability analysis and plan execution.

Key Information Stored

The table's structure captures the essential elements of a material reservation. Its primary key uniquely identifies a reservation through a combination of TRANSACTION_ID, COMPILE_DESIGNATOR, and ORGANIZATION_ID. Key columns define the supply and demand relationship: DEMAND_SOURCE_HEADER_ID and DEMAND_SOURCE_LINE specify the consuming entity (e.g., a discrete job), while SUPPLY_SOURCE_HEADER_ID and SUPPLY_SOURCE_LINE identify the supplying entity (e.g., a planned order). The INVENTORY_ITEM_ID, ORGANIZATION_ID, and REVISION pinpoint the reserved material. Quantity and date information is stored in columns like RESERVATION_QUANTITY and NEED_BY_DATE. The COMPILE_DESIGNATOR links the reservation to a specific MRP plan, and the SUBINVENTORY indicates the specific stock location for the material.

Common Use Cases and Queries

A primary use case is analyzing material availability and reservation details for a specific planned order or demand schedule. For instance, planners often need to see all component reservations for a set of planned orders to understand material constraints. A typical query would join MRP_RESERVATIONS to MRP_SYSTEM_ITEMS for part descriptions and filter by SUPPLY_SOURCE_HEADER_ID. Another common scenario is auditing or cleaning reservations after an MRP plan is discontinued, which involves querying for records with a specific, obsolete COMPILE_DESIGNATOR. Reporting on reserved quantities for critical components across all active plans is also frequent, requiring aggregation of RESERVATION_QUANTITY by INVENTORY_ITEM_ID and ORGANIZATION_ID.

SELECT msr.reservation_quantity,
       msr.inventory_item_id,
       msi.segment1 item_code,
       msr.demand_source_header_id,
       msr.supply_source_header_id
  FROM mrp_reservations msr,
       mrp_system_items msi
 WHERE msr.compile_designator = '&plan_name'
   AND msr.organization_id = msi.organization_id
   AND msr.inventory_item_id = msi.inventory_item_id
   AND msr.supply_source_header_id IN ( &list_of_planned_orders );

Related Objects

As indicated by its foreign keys, MRP_RESERVATIONS has integral relationships with several other EBS tables. It references MRP_SYSTEM_ITEMS to validate the item and organization within the context of a specific MRP plan (COMPILE_DESIGNATOR). The link to MRP_SUB_INVENTORIES validates the reserved subinventory location. For reservations tied to sales order demand, it references MTL_SALES_ORDERS via the DISPOSITION_ID. It also references MTL_ITEM_REVISIONS_B for specific item revisions. The table is closely tied to the MRP planning engine's output and is typically populated and maintained by standard MRP processes rather than direct user DML.