MRP End Assembly Pegging – Oracle EBS SQL Report

Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.

Overview

Detail report for MRP pegging from final assembly to each component, including: planner, end demand pegged qty, demand and plan dates, supply quantity, and supply date.

Report Parameters

Organization Code, Plan, End Assembly, Component, Supplier, Planner, Buyer, Make or Buy, End-Assembly Pegging Only

Oracle EBS Tables Used

oe_sets, mtl_parameters, mrp_full_pegging, mtl_system_items_vl, mtl_units_of_measure_tl, per_people_x, mtl_planners, fnd_lookup_values, mrp_recommendations, mrp_item_purchase_orders, wip_entities, wip_discrete_jobs, mrp_gross_requirements, oe_order_lines_all, oe_order_headers_all, oe_transaction_types_tl

Report Categories

Enginatics

MRP Pegging, PO Headers and Lines, PO Headers and Lines 11i, INV Items

Running This SQL Without Blitz Report

Some Oracle EBS SQL reports in this library require functions from the utility package xxen_util. Install it before running the SQL directly against your Oracle EBS database.

Download & Import Options

Resource Link
Excel Example Output MRP End Assembly Pegging 20-Jan-2019 031236.xlsx
Blitz Report™ XML Import MRP_End_Assembly_Pegging.xml
Full SQL on Enginatics www.enginatics.com/reports/mrp-end-assembly-pegging/

MRP End Assembly Pegging - Case Study & Technical Analysis

Executive Summary

The MRP End Assembly Pegging report provides a critical link between component supply and final product demand. It traces the requirement for a specific component all the way up the Bill of Materials (BOM) to the final “End Assembly” (finished good) that is driving that demand. This visibility is essential for prioritizing component allocation during shortages.

Business Challenge

In a complex manufacturing environment, a single raw material (e.g., a specific screw or chip) might be used in dozens of different finished products. When that raw material is in short supply, planners need to know:

Solution

The MRP End Assembly Pegging report solves this by “pegging” (linking) supply to demand.

Key Features:

Technical Architecture

The report relies on the MRP Pegging logic, which is calculated during the planning run.

Key Tables and Views

Core Logic

  1. Pegging Traversal: The report starts with the component supply (e.g., a Purchase Order or Planned Order).
  2. Upstream Navigation: It recursively traverses the MRP_FULL_PEGGING table to find the parent demand.
  3. End Item Identification: It stops when it reaches an independent demand source (Sales Order or Forecast) at the top of the BOM structure.

Business Impact

© 2026 Enginatics