Search Results mrp_full_pegging




Overview
Explore in AI Chat

Overview

The MRP_FULL_PEGGING table is a core data repository within the Oracle E-Business Suite (EBS) Master Scheduling/MRP module. It stores the complete pegging relationships generated by the MRP planning engine. Pegging is the process of linking a supply (e.g., a planned order, purchase requisition) to the specific demand (e.g., a sales order, forecast) that it is intended to fulfill. This table provides a detailed, navigable chain of these dependencies, enabling full visibility into the source and destination of material requirements throughout the supply plan. Its role is critical for performing "what-if" analysis, resolving material shortages, and understanding the impact of demand changes on the supply network in releases 12.1.1 and 12.2.2.

Key Information Stored

The table's primary structure revolves around establishing and traversing pegging relationships. The PEGGING_ID column serves as the unique primary key for each pegging record. Crucially, the table uses self-referential foreign keys to build the pegging chain: PREV_PEGGING_ID links to the prior step in the sequence, while END_PEGGING_ID can point to a terminal point in the chain, allowing for efficient navigation. The table integrates with the core MRP transaction tables via the TRANSACTION_ID (linking to MRP_RECOMMENDATIONS for supply) and DEMAND_ID (linking to MRP_GROSS_REQUIREMENTS for demand). This design allows each record to represent a single link between a specific supply transaction and its corresponding demand element.

Common Use Cases and Queries

A primary use case is tracing the origin of a supply order. For instance, to find all demands pegged to a specific planned order (transaction_id), one would query the chain starting from the relevant PEGGING_ID. Conversely, to find the planned supplies for a specific sales order demand, the query would trace the chain from the DEMAND_ID. A typical analytical query involves a recursive or hierarchical SELECT using CONNECT BY on PREV_PEGGING_ID to unfold an entire pegging network. This is essential for reporting on order dependencies, assessing the impact of canceling a demand, or validating the planning output. Planners often use this data through the "Pegging" form within the EBS MRP application, which executes such queries against this underlying table.

Related Objects

  • MRP_RECOMMENDATIONS: A key foreign key relationship via TRANSACTION_ID. This table stores the planned supply orders (e.g., Planned Orders, Purchase Requisitions) generated by MRP.
  • MRP_GROSS_REQUIREMENTS: A key foreign key relationship via DEMAND_ID. This table stores the demand elements (e.g., Sales Orders, Forecasts) that drive the plan.
  • MRP_FULL_PEGGING (Self-Referenced): The table has two internal foreign key relationships to itself (PREV_PEGGING_ID, END_PEGGING_ID) to structure the pegging hierarchy and chain.