Understanding MRP Exception Types and Priority
SyteLine generates six primary exception types: Expedite (supply needed earlier), Defer (supply needed later), Cancel (supply no longer needed), Release Planned (convert planned order to firm), Reschedule In (move supply date earlier), and Reschedule Out (move supply date later). mrp_exception_msg WHERE except_code IN ('E','D','C','R') ORDER BY due_date ASC. Prioritize exceptions by impact: Expedite and Reschedule In affect customer delivery dates and should be addressed within 24 hours.
Cancel and Defer exceptions affect inventory carrying costs and can be reviewed weekly.
- Query MRP exceptions: SELECT except_code, item, due_date, qty FROM dbo.mrp_exception_msg ORDER BY due_date
- Prioritize Expedite (E) and Reschedule In (R) exceptions first as they directly impact customer delivery
- Review Cancel (C) exceptions weekly to prevent excess inventory buildup and reduce carrying costs
- Use the MRP Exception Messages form with filters by planner code to distribute workload across planning team
Root Cause Analysis for Recurring Exceptions
Recurring MRP exceptions signal systemic planning parameter issues rather than one-time demand changes. mrp_exception_msg GROUP BY item, except_code HAVING COUNT(*) > 3 ORDER BY frequency DESC. Items appearing more than 3 times typically have incorrect lead times, safety stock levels, or lot sizing rules.
Open the Item Planning Parameters form for flagged items and verify the planning lead time matches actual supplier or production lead time. Check order quantity modifiers including minimum order qty, maximum order qty, and order multiple, overly restrictive lot sizing generates excessive reschedule exceptions.
- Run frequency analysis on mrp_exception_msg to identify items with recurring exceptions (threshold: >3 occurrences)
- Verify planning lead times in Item Planning Parameters match actual supplier delivery performance
- Review lot sizing rules (min qty, max qty, order multiple) that may force suboptimal order quantities
- Check safety stock levels against actual demand variability using standard deviation of past 12 months consumption
Processing Exceptions and Validating MRP Results
After analyzing exceptions, process them through the MRP Action Messages form or use the APS Planning Workbench for visual scheduling. For bulk reschedule operations, use the Process MRP Messages utility to automatically apply recommended date changes to purchase orders and production orders. Before processing, validate MRP results by checking the MRP Pegging inquiry to confirm demand-supply relationships.
mrp_peg WHERE item = 'YOUR_ITEM' to see the full pegging chain. After processing exceptions, regenerate MRP for the affected items to verify the exceptions clear and no new cascading exceptions appear.
- Use Process MRP Messages utility for bulk reschedule operations on purchase and production orders
- Validate pegging chains: SELECT trans_type, due_date, qty, order_num FROM dbo.mrp_peg WHERE item = 'ITEM'
- Regenerate MRP for affected items after processing to verify exceptions clear without creating new ones
- Document exception resolution patterns to build a planning parameter tuning checklist for quarterly review
Try it here, free
Oracle EBS MRP Exception Messages Reference
What each Oracle MRP exception message means, why it appears and what a planner usually does about it.
Frequently asked questions
How many MRP exceptions per planner is considered manageable?
Best practice is under 50 active exceptions per planner per day. Organizations with over 200 exceptions per planner typically have systemic planning parameter issues. Start by fixing the top 20 items by exception frequency, which usually accounts for 60-70% of total exceptions. Quarterly lead time and safety stock reviews prevent exception buildup over time.
Should I use net change or regenerative MRP to clear exceptions?
Use net change MRP for daily processing as it only recalculates items with changes since the last run, completing in 15-30 minutes versus 2-4 hours for full regeneration. Run full regenerative MRP weekly during off-hours to reset the planning baseline. After major parameter changes affecting more than 50 items, a full regeneration is recommended to capture cascading effects.
Why do MRP exceptions reappear after I process them?
Reappearing exceptions indicate the root cause was not addressed. Common reasons include lead time mismatches where the planning lead time differs from actual, demand changes from new sales orders or forecast updates arriving after processing, and supply constraints like vendor capacity limits. Check if new demand was entered after your last MRP run and verify planning parameters match reality.
Overwhelmed by MRP exceptions in SyteLine? Netray's supply chain consultants can tune your planning parameters and build exception management workflows. Contact us for an MRP health assessment.