# How to Read MD04 Exception Messages in SAP > Source: https://netray.co/erp-help/sap-md04-exception-messages-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer The exception indicator in MD04 flags procurement elements whose date or quantity no longer matches the current demand situation - it is SAP's built-in change signal, read element by element in the detail screen, not just the header icon. Triage by exception group first, then decide to reschedule, cancel, or accept each one. ## Kind how-to ## System sap ## Erp SAP ERP (ECC 6.0 / S/4HANA) ## Module PP / MRP ## Query how to read MD04 exception messages in SAP ## Alternate Queries - what do MD04 exception icons mean - MD04 reschedule exception SAP - how to clear exception messages in MRP ## Applies To SAP ECC 6.0 and S/4HANA, PP-MRP (classic MRP and MRP Live) ## Steps ### Work through MD04 exceptions systematically **Items:** Run MD04 for the material and plant, and look at the exception indicator column both on the header line and on individual procurement elements below it. Double-click an element showing an exception icon to open its detail screen, where the Exception field names the category (rescheduling, date in the past, excess stock, and so on). Use the exception group filter (Exceptions menu or the traffic-light filter) to narrow MD04 to only elements with active exceptions across a plant or MRP controller instead of scanning every line. For a scheduling exception, compare the proposed date against today and the order's current start date to decide whether rescheduling the order (ME38 for purchase orders, CO02 for production orders) is operationally feasible. For a quantity-related exception, use the Pegged Requirements view to see exactly which sales order or planned order is driving the number before changing anything. If the same exception recurs for a material on every MRP run, investigate the underlying master data - lot size, safety stock, or planning time fence in the MRP1-MRP4 views - rather than manually correcting it each cycle. For volume review across an MRP controller's whole portfolio, use MD06 (collective display) or MD07 to bulk-review and bulk-act on exceptions instead of opening MD04 material by material. ## Sections ### MD04 is a live pegged list, not a static report **Body:** MD04's stock/requirements list reflects the current planning situation - every open requirement pegged against every open procurement element, recalculated (or refreshed) as changes come in. The exception column is SAP's way of telling the planner 'this element no longer lines up with what it was originally planned against.' That is why the same material can show a clean MD04 one day and exceptions the next without anyone touching it directly - a sales order date change, a new higher-priority order, or an MRP run elsewhere in the supply chain can ripple into the pegging. ### Reading an individual exception **Body:** The exception shown at the header level is usually a summary of the most significant exception among the material's elements; the real detail is always at the element level. Open the specific planned order, purchase requisition, or production order line and check the Exception field in its detail screen. Common categories a planner sees regularly are rescheduling (the element's date should move earlier or later to match current demand), items in the past (an open element dated before today), and excess or shortfall against current requirements. **Code:** - MD04 -> Material, Plant -> Execute - Double-click an element with an exception icon -> Exception field in the detail screen - Menu: Exceptions -> filter by exception group / MRP controller ### Deciding what to do with each exception **Body:** Rescheduling proposals are suggestions, not commands - only move a purchase order or production order to the proposed date if it is operationally realistic (vendor lead time, shop capacity). If it is not, the right fix is usually to address the demand side (confirm or move the sales order) rather than force a proposal that cannot be met. For orders inside the planning time fence, MRP will flag exceptions instead of silently moving them - this is intentional protection for firmed, near-term orders, not a defect, and generally means a planner needs to make a manual call rather than let MRP auto-adjust. ### Working the exception list by MRP controller **Body:** MD06 gives a collective, cross-material view for an MRP controller or plant, letting a planner triage exceptions across their whole portfolio in one screen instead of opening MD04 material by material. MD07 offers a similar collective view geared toward reviewing net requirements. For weekly or daily planning cadences, many teams export the MD06 exception list to a spreadsheet for review and sign-off before acting in the system, especially where reschedule proposals affect supplier commitments. ## Pitfalls - Re-running MRP (MD01/MD02) repeatedly without addressing the underlying exception does not clear a genuine scheduling conflict - it just regenerates the same proposal. - Ignoring the planning time fence and expecting MRP to auto-move firmed near-term orders is a misunderstanding of the design, not a bug. - Mixing firmed and unfirmed planned orders without periodic review causes repeated reschedule-out exceptions on the same material every run. - MD04's exception list reflects the plan at the moment you pulled it and goes stale quickly - always refresh before acting on a screenshot or export from earlier in the day. - Acting on the header-level exception icon without opening the specific element detail can lead to fixing the wrong order, since the header often summarizes several different exceptions. ## Ai Angle ERPray grounded on your SAP PP data can summarize an MRP controller's open MD04 exceptions in plain language - which are genuine scheduling conflicts, which are inside the planning time fence and expected, and which trace back to a single upstream master data setting - instead of a planner opening MD06 and drilling into each material by hand. ## Faq ### What is the difference between the header exception and the element exception in MD04? **Answer:** The header icon summarizes the most significant exception among the material's elements as a quick visual cue. The actual, actionable detail is always on the specific procurement element - open it directly rather than acting on the header alone. ### Why does MD04 show an exception for an order inside the planning time fence? **Answer:** MRP will not silently reschedule firmed orders inside the planning time fence, so instead it flags the mismatch as an exception for a planner to review manually. This protects near-term commitments from automatic changes. ### Can I bulk-clear exceptions across many materials at once? **Answer:** MD06 and MD07 give a collective view for an MRP controller so you can review and act on multiple materials in one session, but there is no single button that clears exceptions without a planning decision on each one. ### Does the exception list update automatically as new sales orders come in? **Answer:** MD04 reflects the current pegging whenever you open or refresh it, so a new order or a date change elsewhere can introduce a new exception without an MRP run, depending on your live/net change planning configuration. ## Search terms SAP MD04 exception messages, MRP exception SAP, MD04 reschedule exception, SAP stock requirements list, MD06 collective display, planning time fence SAP, SAP MRP controller exceptions, pegged requirements SAP, MD04 how to read, SAP PP MRP exceptions --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json