Search Results mr_pegg_tbl




Overview
Explore in AI Chat

Overview

The MR_PEGG_TBL is a core data table within the Oracle E-Business Suite (EBS) Process Manufacturing Process Planning (GMP) module. Its primary function is to store pegging information, which is a critical component of material requirements planning (MRP) and supply chain execution. Pegging establishes a dynamic link, or traceability, between specific supply (e.g., production batches, purchase orders) and specific demand (e.g., sales orders, work orders). This table specifically supports the pegging of demands to shortage warnings generated by the MRP engine. By maintaining these relationships, the table enables planners to perform impact analysis, understand the source of material shortages, and execute targeted rescheduling or replenishment actions to resolve constraints.

Key Information Stored

The table's structure is defined by its composite primary key, which uniquely identifies each pegging record. The key columns are MRP_ID, ACTION_NO, and LINE_NO. The MRP_ID typically references a specific MRP plan or simulation run. The ACTION_NO and LINE_NO columns link to a corresponding record in the MR_ACTN_TBL (Action table), which details the recommended or taken planning action, such as rescheduling a purchase order. While the provided metadata does not list all columns, the table's foreign key relationships and purpose indicate it likely stores identifiers for the pegged demand (e.g., demand order type and ID) and the associated supply or shortage entity. This creates a many-to-many mapping that the MRP engine uses to model material flow and constraint propagation.

Common Use Cases and Queries

The primary use case is troubleshooting and resolving material shortages identified in an MRP plan. A planner can query this table to answer critical questions: "Which sales orders are affected by this component shortage?" or "What is the source of supply for this specific work order demand?" Common reporting and query patterns involve joining MR_PEGG_TBL to the action table (MR_ACTN_TBL) and relevant transaction or order tables. A sample analytical SQL pattern might trace the pegging chain for a given shortage:

  • SELECT peg.*, actn.action_type FROM gmp.mr_pegg_tbl peg JOIN gmp.mr_actn_tbl actn ON peg.mrp_id = actn.mrp_id AND peg.action_no = actn.action_no WHERE peg.demand_id = :p_order_id;

This data is essential for generating pegging reports, performing "where-used" and "where-from" analyses, and supporting the graphical pegging functionality within Oracle Process Manufacturing.

Related Objects

The MR_PEGG_TBL has a direct and integral relationship with the MR_ACTN_TBL (Action table), as defined by its foreign key constraint. This links each pegging record to a specific MRP-recommended action. It is a child object within the GMP MRP schema. While not listed in the provided metadata, it is logically related to core inventory and planning tables such as MTL_DEMAND, MTL_SUPPLY, and MRP_RECOMMENDATIONS, which hold the detailed records for the actual demand and supply transactions being pegged. The table is primarily maintained by the MRP planning engine processes and is accessed by standard GMP pegging inquiries and reports.