Integration
MRP exception message
An MRP exception message is a system-generated alert telling a planner that an order needs attention — expedite it, reschedule it, cancel it, or place it. Volume is the defining problem: a single planning run can produce more messages than any planner can act on.
Also known as: MRP action message, exception report
The volume problem
MRP is reliable at identifying discrepancies between plan and supply. It produces one message per discrepancy, which for a mid-size manufacturer can mean hundreds or thousands per run.
Planners triage: work the top of the list by value or urgency, and accept that the tail goes unworked. The tail is not less risky, only less visible — and next week's run regenerates it, which trains everyone to treat the report as background noise.
Exception messages describe the plan, not the supplier
An important limitation: MRP exception messages are computed from what the ERP holds. If the ERP holds a stale date because a supplier's revised commitment never got entered, MRP will generate confident guidance from wrong data — or fail to generate a warning that was warranted.
This is why keeping supplier commitments current in the ERP is a prerequisite for exception messages being worth reading at all.
How Evolinq handles it
Evolinq improves exception quality upstream by keeping confirmed supplier dates current in the ERP, so the planning run computes against commitments rather than stale requests.
Frequently asked questions
What is an MRP exception message?
An MRP exception message is an alert produced by a material requirements planning run telling a planner that an order needs action — expedite, reschedule, cancel, or place. They are generated per discrepancy, which is why a single run can produce far more than a planner can work.
Why do MRP exception messages get ignored?
Because of volume and repetition. Planners can only work the top of a list of hundreds, the same messages regenerate each run, and messages computed from stale supplier dates produce guidance that turns out to be wrong — which erodes trust in the whole report.