MRP Exceptions – Oracle EBS SQL Report
Oracle E-Business Suite SQL report from the Enginatics Library powered by Blitz Report™.
Overview
Detail report for MRP Exception messages, including item, make or buy, default buyer, planner and exception message to use.
Report Parameters
Organization Code, Plan, Exception, Planner Code, Buyer, Item
Oracle EBS Tables Used
mrp_exception_details_v, mtl_system_items_vl, per_people_x, mtl_planners
Report Categories
Related Reports
MRP Pegging, INV Items, WIP Required Components, INV Item Upload, MRP Horizontal Plan, MRP End Assembly Pegging
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 Exceptions 03-Aug-2018 212438.xlsx |
| Blitz Report™ XML Import | MRP_Exceptions.xml |
| Full SQL on Enginatics | www.enginatics.com/reports/mrp-exceptions/ |
MRP Exceptions - Case Study & Technical Analysis
Executive Summary
The MRP Exceptions report is the primary “to-do list” for material planners. It filters the massive amount of data generated by an MRP run into actionable alerts. Instead of reviewing every item, planners focus only on items where the plan is “broken” or requires intervention, such as late orders, potential shortages, or excess inventory.
Business Challenge
An MRP run might generate thousands of planned orders and recommendations. Planners cannot review them all. They need to know:
- Urgency: “Which orders are already late and need immediate expediting?”
- Efficiency: “Which orders can be cancelled because the demand went away?”
- Data Integrity: “Which items have missing lead times or invalid planning parameters?”
Solution
The MRP Exceptions report highlights these specific issues using standard exception messages.
Key Features:
- Action-Oriented: Groups items by exception type (e.g., “Orders to be cancelled,” “Orders with compression days”).
- Prioritization: Allows filtering by Planner Code, so each planner sees only their own items.
- Details: Provides the specific context (e.g., “Order 123 is late by 5 days”).
Technical Architecture
The report queries the exception messages generated during the planning process.
Key Tables and Views
MRP_EXCEPTION_DETAILS_V: The primary view containing the exception messages linked to specific items and plans.MTL_SYSTEM_ITEMS_VL: Provides item descriptions and planning attributes.MTL_PLANNERS: Used to filter exceptions by the responsible planner.
Core Logic
- Exception Generation: During the MRP run, the engine identifies conditions that violate planning rules (e.g., supply date > need date).
- Categorization: These conditions are flagged with specific Exception Types (e.g., Type 10 = “Orders to be cancelled”).
- Reporting: The report retrieves these records, joined with item and planner details for context.
Business Impact
- Productivity: Drastically reduces the time planners spend analyzing data, allowing them to focus on fixing problems.
- Responsiveness: Ensures that critical shortages (potential stockouts) are identified and addressed immediately.
- Cost Reduction: Helps identify excess inventory (orders to cancel) and avoid unnecessary expediting costs.
Useful Links
- Blitz Report™ – World’s Fastest Oracle EBS Reporting Tool
- Oracle Discoverer Replacement – Import Worksheets into Blitz Report™
- Oracle EBS Reporting Toolkits by Blitz Report™
- Blitz Report™ FAQ & Community Q&A
- Supply Chain Hub by Blitz Report™
- Blitz Report™ Customer Case Studies
- Oracle EBS Reporting Blog
- Oracle EBS Reporting Resource Centre
© 2026 Enginatics