SAP MRP Controller Daily Worklist Template
MRP does not finish when the run completes. The controller still has to work the exceptions, convert or firm orders and chase purchasing. This template turns that daily routine into a one page record you can hand to a manager or a colleague on shift change.
Fill in
SAP MRP Controller Daily Worklist Template
Daily MRP Controller Worklist
Company: Acme Precision Ltd Plant: 1010 MRP controller: P01 Planner: A. Planner Date: 2026-10-20 Last MRP run: 2026-10-20 02:30
Exception summary (MD06 or MD07)
| Exception | Meaning | Count | Cleared today |
|---|---|---|---|
| 10 | Reschedule in | 18 | |
| 15 | Reschedule out | 12 | |
| 20 | Cancel process | 5 | |
| 96 | Below safety stock | 3 |
Priorities
1. Expedite PO for bearing housing, shortage on order 1000214 2. Convert planned orders for family 4400 inside the firming horizon 3. Review cancel messages on obsolete revision parts
Action log
| Material | MD04 element | Action | Owner | Due | Status |
|---|---|---|---|---|---|
Blockers and escalations
Supplier confirmation pending on two POs. Engineering to confirm BOM change on assembly A-2200.
Sign off
Exception numbers 10, 15, 20 and 96 are standard SAP MRP exception messages. If your exception groups are customized, adapt the summary table to your own list.
Automate the morning MRP review
Optional: a short call on how a read only assistant could prepare this worklist from your SAP data.
Optional. The tool and every export work without this. No spam.
How to use the worklist
Start the day after the planning run. Open MD07 or MD06 for your MRP controller, count the exception messages by type and enter them in the summary. Then list the top priorities and log each action against a material and MD04 element. Print or export it to PDF at the end of the shift so the next planner sees what is open and who owns it.
- Fill the counts from MD06 before you start acting
- Log one line per material, not per message
- Record the owner so purchasing and production see their items
Which exceptions to work first
Work shortages and late supply before cosmetic messages. A reschedule in (10) on a purchase order for a material that is short today usually matters more than ten reschedule out (15) messages on safe stock. Cancel process (20) messages free money and capacity but need a check that no demand was hidden by a planning time fence. Messages below safety stock (96) point to demand surprises or stale safety stock values.
Using it as a handover and KPI source
Keep the daily sheets in a shared folder. After a month you can see which materials generate repeat exceptions, which suppliers need follow up and how long messages stay open. That feeds MRP parameter reviews, for example lot size, planned delivery time and safety stock. If you track exception counts per controller you can balance workload across planners.
Common mistakes
Clearing messages in bulk without checking the underlying supply hides real problems. Firming planned orders that MRP will otherwise move creates nervous schedules. Not recording the MRP run time means nobody knows if the numbers are from today or yesterday.
- Check the run timestamp before acting
- Do not reschedule firmed orders silently
- Review the top repeat offenders weekly
Frequently Asked Questions
Is this an official SAP form?
No. It is a practical working document. The exception numbers follow SAP MRP exception messages, but the layout is ours so you can adapt it to your plant and your customized exception groups.
Should I use MD04 or MD07 for the daily review?
Use MD07 or MD06 to see which materials have exceptions across your controller, then open MD04 for each material to read the detailed elements and act. MD04 is the single material view and MD06 is the collective list.
How many exception messages is normal?
It depends on master data quality, planning time fences and how often supply changes. A rising count with no change in volume often points to bad lead times or lot sizes. Track your own trend instead of a generic target.
Can I change the exception list in the template?
The summary rows are fixed to common exceptions, but you can edit the exported document or Excel file to add rows for the messages your plant uses. Your configuration decides which exceptions are active.
If your controllers spend an hour a day pulling MD04 data into spreadsheets, we can build an assistant on your SAP data that prepares this worklist automatically, with human approval for any change.
Related Tools
SAP MD04 Exception Messages and MRP Elements Reference
A searchable lookup of MD04 element abbreviations, key exception messages and the MRP transactions you use to act on them.
SAPSAP Lot Sizing Procedures and MRP Parameters Reference
A searchable list of SAP lot size keys, MRP types and the material master MRP fields that control planning results.
SAPSAP Planned Order to Production Order Conversion Checklist
A step by step checklist to verify materials, BOM, routing, capacity and release before converting planned orders to production orders in SAP.
SAPSAP Production Order Types, Categories and Statuses Reference
A searchable lookup of SAP order categories, order type controls, system statuses, shop floor transactions and core order tables.
More SAP tools
See all- SAP Routing Upload Worksheet (Excel)
- SAP BOM Usage, Status and Item Category Reference
- SAP Work Center Capacity Planning Calculator
- SAP QM Database Tables Reference
- SAP QM Transaction Codes Reference
- SAP QM Go-Live and Cutover Checklist
- SAP QM Maturity Assessment
- SAP Movement Types Reference
- SAP Purchasing Document Types Reference