Search Results mrp_item_purchase_orders




Overview
Explore in AI Chat

Overview

The MRP_ITEM_PURCHASE_ORDERS table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It serves as a detailed transaction table that stores and manages records for all purchase orders and purchase requisitions that are relevant to the Material Requirements Planning (MRP) and Master Scheduling engines. Its primary role is to provide the sourcing and supply-side data necessary for the MRP engine to generate accurate recommendations for planned orders, reschedules, and cancellations. The table is populated during the MRP planning run, which processes supply and demand data, and it acts as a critical link between procurement transactions and the MRP-generated recommendations.

Key Information Stored

The table's structure is designed to capture the essential attributes of procurement documents for planning purposes. Its primary key is the TRANSACTION_ID, which uniquely identifies each purchase order or requisition line record within the MRP context. Key columns include INVENTORY_ITEM_ID and ORGANIZATION_ID, which identify the planned item and its inventory organization, linking to the MRP_SYSTEM_ITEMS table. The COMPILE_DESIGNATOR column specifies the MRP plan name for which the data was compiled. Other significant data points typically stored, inferred from its function, include purchase order/requisition numbers, line IDs, shipment details, promised or expected receipt dates, order quantities, and supplier information. This consolidated view allows the MRP engine to assess current and planned supply against demand.

Common Use Cases and Queries

The primary use case is supporting the MRP planning process and subsequent analysis of supply recommendations. Common queries involve extracting open supply for a specific item or plan to analyze procurement schedules. For instance, a planner might run a query to list all pending purchase orders for critical components within a given planning horizon. Another typical scenario is tracing the source of an MRP recommendation back to the specific purchase order that triggered it, using the link to the MRP_RECOMMENDATIONS table. A sample SQL pattern to find purchase orders for a specific item in a plan would be:

  • SELECT transaction_id, po_number, promised_date, quantity FROM mrp.mrp_item_purchase_orders WHERE inventory_item_id = 1000 AND organization_id = 101 AND compile_designator = 'MAIN-PLAN' AND promised_date BETWEEN SYSDATE AND SYSDATE+30;

This data is fundamental for custom reports on procurement commitments, supplier delivery performance within the planning context, and reconciliation of MRP output with actual Purchasing transactions.

Related Objects

The MRP_ITEM_PURCHASE_ORDERS table has defined relationships with several other key MRP tables. As per the provided metadata, it has a foreign key relationship with MRP_SYSTEM_ITEMS on the columns INVENTORY_ITEM_ID, ORGANIZATION_ID, and COMPILE_DESIGNATOR, ensuring referential integrity to the items being planned. Most importantly, it is referenced by the MRP_RECOMMENDATIONS table via the DISPOSITION_ID foreign key. This is a critical relationship, as it directly ties each MRP output recommendation (e.g., "Reschedule In" or "Cancel") to the specific purchase order or requisition record that is its subject. The table is also conceptually linked to the underlying transaction tables in the Purchasing module (e.g., PO_HEADERS_ALL, PO_LINES_ALL), from which its data is sourced during the MRP snapshot process.