# MRP Exception Message Triage Template

> Source: https://netray.co/tools/mrp-exception-message-triage-template
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A one page record for working an MRP action message: what it says, what it affects, why it happened and what the planner decided.

## Category

supply-chain

## Audience

- Production planner
- MRP controller
- Buyer

## Tool

**Kind:** template

**Output:** document

**Fields:**

#### Company

**Key:** company

**Type:** text

**Default:** Acme Precision Ltd

#### Planner

**Key:** planner

**Type:** text

**Default:** R. Mehta

#### Plant

**Key:** plant

**Type:** text

**Default:** Plant 01

#### MRP run date

**Key:** run_date

**Type:** date

**Default:** 2026-10-19

#### Part number

**Key:** part

**Type:** text

**Default:** BRK-1001

#### Exception message

**Key:** message

**Type:** select

**Options:**

- Reschedule in
- Reschedule out
- Cancel
- Release new order
- Expedite
- Past due order
- Below safety stock

**Default:** Reschedule in

#### Order reference

**Key:** order_ref

**Type:** text

**Default:** PO 4500012345 line 10

#### Current due date

**Key:** current_due

**Type:** date

**Default:** 2026-11-09

#### Required date

**Key:** need_date

**Type:** date

**Default:** 2026-10-30

#### Quantity affected

**Key:** qty

**Type:** text

**Default:** 400 EA

#### Impact if ignored

**Key:** impact

**Type:** textarea

**Default:** Shortage on work order WO-77120 on 30 Oct. Line stops for two shifts.

#### Root cause

**Key:** root_cause

**Type:** select

**Options:**

- Demand increase
- Supplier slip
- Forecast change
- Master data error
- Lead time wrong
- Inventory inaccuracy
- Engineering change
- Other

**Default:** Demand increase

#### Decision

**Key:** decision

**Type:** select

**Options:**

- Accept and action
- Expedite with supplier
- Reschedule out
- Cancel order
- Override and ignore
- Escalate

**Default:** Expedite with supplier

#### Action owner and date

**Key:** action_by

**Type:** text

**Default:** Buyer J. Singh by 2026-10-21

**Blocks:**

#### MRP exception message triage

**Body:** Company: {{company}}
Planner: {{planner}}
Plant: {{plant}}
MRP run date: {{run_date}}

#### Message

**Table:**

**Columns:**

- Field
- Value

**Rows:**

**0:** Part number

**1:** {{part}}

**0:** Message

**1:** {{message}}

**0:** Order reference

**1:** {{order_ref}}

**0:** Current due date

**1:** {{current_due}}

**0:** Required date

**1:** {{need_date}}

**0:** Quantity affected

**1:** {{qty}}

#### Impact if ignored

**Body:** {{impact}}

#### Root cause and decision

**Body:** Root cause: {{root_cause}}
Decision: {{decision}}
Action owner and date: {{action_by}}

#### Follow up

**Table:**

**Columns:**

- Check
- Done
- Date

**Rows:**

**0:** Supplier confirmed new date

**0:** Order updated in ERP

**0:** Root cause corrected at source

**0:** Message cleared on next MRP run

**Signatures:**

- Planner
- Buyer or production lead
- Supply chain manager

**Notes:** Fill in one copy per significant exception. For routine messages, use the log in your ERP and reserve this template for those that need an owner and a record.

## Content

**Intro:** MRP creates hundreds of action messages every run, and most planners cannot act on all of them. Triage means deciding which ones matter, why they appeared and who does what. This template gives that decision a record.

**Sections:**

#### How to use the template

**Body:** Fill the fields from the MRP exception screen: part, message type, order reference, current due date, required date and quantity. Describe the impact if nothing is done, using affected work orders or customer orders. Then record the root cause and decision. The generated document can be printed or exported to Word to attach to an escalation, or kept as an audit trail for planner decisions.

#### The common message types

**Body:** Reschedule in means supply arrives later than needed and should be pulled earlier. Reschedule out means supply is earlier than needed and could be pushed. Cancel means the order is no longer required. Release means a planned order has reached its release date. Past due means the order is already late. Messages inside the planning time fence usually need a manual decision because MRP will not change them itself.

**Bullets:**

- Reschedule in: usually urgent, check supplier capacity.
- Reschedule out: low urgency, saves inventory cost.
- Cancel: check supplier commitments and cancellation terms.
- Release: confirm material and capacity first.

#### Prioritising

**Body:** Sort by the date of the real need, then by the value or criticality of the part. A reschedule in on a constraint item with a shop order due this week outranks ten reschedule outs. Note the root cause every time: if the same cause appears repeatedly, such as a wrong lead time, fixing the master data removes whole classes of messages.

#### Common mistakes

**Body:** Planners often clear messages without recording why, so the same exception returns next run. Another mistake is following a reschedule message blindly when the root cause is inaccurate inventory. And messages for items in the frozen zone are ignored because MRP did not change the order, even though the shortage is real.

**Cta:** Netray can build a read-only exception dashboard on your ERP data that ranks action messages by real shortage impact so planners start with those that matter.

**Faq:**

#### What is an MRP exception message?

**Answer:** It is an action message produced by the MRP run indicating that an existing order or planned order should be rescheduled, cancelled or created because supply and demand do not match in time or quantity.

#### Which MRP exceptions should be worked first?

**Answer:** Those with the nearest real need date and the highest impact: reschedule in, past due orders and shortages on constraint items or customer orders. Cancel and reschedule out messages can wait.

#### Why do the same exception messages return every run?

**Answer:** Because the cause was not fixed. Typical reasons are wrong lead times, inaccurate inventory, unrealistic supplier dates or orders that were reviewed but not updated in the ERP.

#### Can I ignore reschedule out messages?

**Answer:** You can for a while, but they hide inventory. Persistent reschedule outs on large orders tie up cash. Review them at a regular cadence, weekly for A items, and push the orders out when suppliers allow.

## Search terms

mrp exception message triage, mrp action message template, reschedule in reschedule out cancel, mrp exception handling procedure, planner action message log, mrp exception report template, mrp messages reschedule out

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json