Search Results mrp_full_pegging




MRP_FULL_PEGGING in Oracle EBS 12.1.1/12.2.2: A Detailed Overview

The MRP_FULL_PEGGING table in Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2 is a critical repository for Material Requirements Planning (MRP) pegging data, which establishes hierarchical relationships between supply and demand elements. This table enables end-to-end visibility of demand-supply linkages across the supply chain, supporting traceability, exception management, and decision-making in manufacturing and procurement processes.

Purpose and Functional Role
MRP pegging connects demand sources (sales orders, forecasts, dependent demands) to supply sources (purchase orders, work orders, on-hand inventory) through a parent-child relationship structure. The MRP_FULL_PEGGING table stores these relationships after MRP engine execution, allowing users to:

  • Trace demand fulfillment paths across multiple BOM levels
  • Analyze the impact of supply disruptions on downstream demand
  • Identify excess inventory linked to specific demand
  • Support what-if scenario planning through pegging analysis

Key Table Structure
The table contains these essential columns:

Column Description
PEGGING_ID Primary key identifier for pegging relationships
DEMAND_SOURCE_TYPE Classification of demand (SO, Forecast, etc.)
DEMAND_SOURCE_HEADER_ID Reference to demand document header
SUPPLY_SOURCE_TYPE Classification of supply (PO, WO, etc.)
SUPPLY_SOURCE_HEADER_ID Reference to supply document header
INVENTORY_ITEM_ID Item being pegged
ORGANIZATION_ID Inventory organization context
QUANTITY Pegged amount between supply and demand
LEVEL_NUMBER Hierarchy level in multi-level pegging

Technical Implementation
The table is populated during MRP plan generation through these key processes:

  1. MRP engine explosion creates demand-supply relationships
  2. Pegging relationships are established based on allocation rules
  3. Data is written to MRP_FULL_PEGGING with transaction timestamps
  4. Indexes on demand/supply references enable fast joins with transaction tables

Integration Points
The table integrates with multiple EBS modules:

  • Inventory: Links to MTL_SYSTEM_ITEMS via INVENTORY_ITEM_ID
  • Order Management: References sales orders through DEMAND_SOURCE_HEADER_ID
  • Purchasing: Connects to purchase orders via SUPPLY_SOURCE_HEADER_ID
  • Work in Process: Ties to work orders through supply references

Performance Considerations
For optimal performance in large implementations:

  • Partitioning by ORGANIZATION_ID improves query performance
  • Materialized views can aggregate pegging data for reporting
  • Regular purging of historical pegging data reduces table growth
  • Composite indexes on frequently joined columns enhance join operations

Business Applications
Organizations leverage MRP_FULL_PEGGING data for:

  • Shortage analysis by tracing unmet demand to root causes
  • Order promising by verifying material availability paths
  • Supply chain risk assessment through dependency mapping
  • Inventory optimization by identifying non-critical stock

The table's comprehensive demand-supply mapping provides foundational data for advanced supply chain analytics and responsive decision-making in Oracle EBS environments.