The source
What comes in
- Dated planning run and exception messages
- Open POs, commitments and current inventory
- Demand references and action tolerances
MRP exception management agent MRP raised the exception.
MRP raised the exception.
Now someone has to act.
LaunchAI gathers current PO facts and demand references, then prepares the buyer’s next action with the evidence attached.
The job in one minute
What the agent takes off your desk.
MRP exception messages flag conditions in a planning run that need attention, such as a mismatch between required dates and existing supply. The message is a recommendation to investigate, not evidence that a supplier has accepted a new commitment. LaunchAI can connect it to current purchasing records, identify the missing fact and prepare the permitted next action for the buyer.
The finish
What comes out
A prioritized, evidence-linked queue of supply actions and unresolved assumptions.
Your rules
Who owns the decision
The buyer and the responsible team keep commercial, qualification and financial authority. The agent does the permitted work and brings exceptions to their owner.
See it run
Watch the agent work through it.
In this conceptual walkthrough, an AI agent picks up planner02's request to cover the bought-out parts for job J-24117 (HPU-30 rev D, qty 4, material need-by 11/18/2026) and the overnight MRP notice. In Epicor Kinetic-style screens it confirms the job's three Buy lines, filters the PO suggestions S-9031 to S-9033 (due 11/16, two days before need-by) and checks supply: existing stock and open POs are pegged to other jobs, so all three are truly short 4 EA. Supplier V-1180 is approved, but the pump's 389.00 price expired 10/31, so under PUR-02 the agent asks the supplier for a current price and delivery. Quote BW-Q-3391 prices the pump at 412.00 (+5.91%), over the PUR-07 3.00% limit, so buyer01 approves it. The agent enters PO lines for the pump and reservoir from their sources, raises a planner exception because the motor's confirmed 11/25 misses 11/18, saves PO 5127 (2,506.00) for buyer01's approval, verifies it by reopening, and reports the open motor shortage to buyer01 and planner02.
Conceptual walkthrough with sample data. Screens are generic stand-ins modeled on the named system, not its own interface; workflow and screens vary by ERP.
At the buyer’s desk
The work is spread across several windows.
The planning run says cancel. The supplier shipped after the run finished. The buyer sees a message from yesterday and a commitment from today. The action needs current facts, not another unfiltered exception list.
A reschedule message can be outdated by the time a buyer opens it. Supplier commitments, inventory transactions and engineering changes may have moved since the planning run. The practical task is to reconcile the message with current evidence and identify who can authorize the action.
How the agent does it
Same screens. Your rules. A checked result.
LaunchAI follows the purchasing task through your existing applications. Each step has a source to read, a rule to apply or an outcome to check.
-
Identify the planning run
Retain the run timestamp and the requirement that produced the message.
-
Refresh the order facts
Compare the suggested action with the latest PO, supplier promise and current supply balance.
-
Connect the demand
Show the production or customer requirement affected and distinguish a firm need from a planning suggestion.
-
Prepare the buyer action
Draft the reschedule, cancellation or clarification request within the permitted workflow and route commercial decisions for review.
The detail that changes the job
What gets caught before the next step.
A planning run suggests canceling a PO that the supplier has already shipped after the run completed.
Move the divider to see how the starting information becomes a checked outcome. The complete fields are in the table below.
| Field | Starting information | Checked outcome |
|---|---|---|
| Message | Cancel suggested | Planning timestamp retained |
| Current supply | PO still open | Shipment evidence found |
| Action | Cancellation drafted blindly | Buyer reviews in-transit supply |
Worked example, not a customer result. Values and documents illustrate what to test.
Exact rules. Context. A person where needed.
The exception has somewhere to go.
The agent needs to recognize the point where the next action depends on missing information or another person’s authority.
- Current order data differs from the planning run baseline.
- A proposed cancellation carries supplier charges or affects another demand.
Define the allowed fields and actions in your software. A draft, an external commitment and an approved payment are different steps.
Show the working
Measure the work that actually gets done.
Agree on the baseline and the finish before the pilot. Count review and exception work as well as completed transactions.
Measure 01
Exceptions reviewed against current data
Measure 02
Planning messages with named owners
Measure 03
Stale actions avoided
The practical questions
What buyers ask.
Can an agent change MRP parameters?
Parameter changes alter planning behavior and need their own authority. Start with exception preparation and buyer follow-through.
How is this different from running MRP?
The planning engine calculates requirements. Exception management investigates its messages and coordinates the resulting purchasing work.
Are MRP action messages the same in every ERP?
No. Message names, codes and recommended actions depend on the planning system and configuration. Use your ERP documentation and current planning run as the authority. Confirm the affected item, supply document, dates and demand before acting on a message.
Your applications. Your purchasing rules.
See the work happen on your screens.
We’ll scope the input, the saved output and the exception that needs your team.