Skip to main content

Transitioning from SAP MRP: Handling past-due planning suggestions & validating workflow

  • February 3, 2026
  • 3 replies
  • 23 views

Hello Manufacturing and Distribution Experts,

I am currently working with a customer who is transitioning from SAP to Acumatica. We've encountered a significant difference in how the two systems handle MRP planning suggestions when the required action date (start date) is in the past due to lead times. In SAP's MRP logic, the system typically performs automatic "forward scheduling" when a backward-scheduled start date falls in the past. It automatically moves the suggested order date to the earliest possible current date and issues an exception message. Acumatica, as we understand it, requires a more manual process using exceptions and date updates.

I am thinking about  proposing the following workflow to our client, and I'd like the team's validation:

Our Proposed Workflow for Past-Due Demands:

  1. MRP runs and generates planned order suggestions with dates in the past.
  2. The planner uses the Inventory Planning Display screen (AM402000) or Exceptions screen (AM403000) to identify these items.
  3. The planner converts the past-due planned order into an actual firmed order (Purchase Order, Production Order, etc.). The firmed order retains the past date initially.
  4. The planner then navigates to the Inventory Planning Exceptions (AM403000) screen. The newly firmed order is now flagged with an Expedite or Delete exception message.
  5. The planner manually opens the actual PO/Production Order document and updates the Promised Date to a realistic, achievable future date that accounts for the current lead time.

My questions for the Everyone are:

  1. Is there any standard configuration in Acumatica (perhaps using the Grace Period, Time Fences, or other settings in the Inventory Planning Preferences form) that can mimic SAP's automatic forward-replanning behavior?
  2. Does the multi-step process we outlined above make sense as the correct, best-practice approach in Acumatica, or are we overcomplicating the workflow?
  3. Would creating a Business Event or a customization to automatically push the firmed order's promised date to the current date plus lead time be a viable and safe automation strategy to achieve a similar outcome to SAP?
  4. For those who have managed this transition, what key advice would you give the client's planning team to ease the pain of this manual process compared to SAP's automation?

We are using Acumatica version 25R1.

Thank you in advance for any insights!

3 replies

dgodsill97
Varsity I
Forum|alt.badge.img+5
  • Varsity I
  • February 4, 2026

The only alternative to a firm planned order is a master schedule order which can only be converted into a production order.  Some MRP systems will generate an exception message for any planned order that violates the lead time, e.g. the start date or ending date is in the past.  Planned order dates in the past are in response to past due demand so clearing up the demand should be a action taken,


jdobish
Pro III
Forum|alt.badge.img+2
  • Pro III
  • February 4, 2026

I have utilized an import scenario from the exceptions page to then update the date on the past due purchase orders, but it can become cumbersome similar to what you are describing. 

When it comes to production orders, you can set it to forward schedule, but when it comes to purchase orders, it will always go into the past if you are late.

(turn on sarcasm meter - Joke incoming!)

*The easiest answer is to never have any backlog, nor any expedite needs, nor any past due parts. This allows MRP to run perfectly! 🤣


dgodsill97
Varsity I
Forum|alt.badge.img+5
  • Varsity I
  • February 4, 2026

A client, in past life, implemented MRP after many years on their current ERP  There were over 50,000 exception messages.

Having been in the MRP space forever it seems (APICS certified many years ago), we stressed the 3 things necessary for success: accurate inventory, accurate bills of material, accurate dates for existing supply and demand.  I also would mention, a reasonable statement of demand and/or master schedule.

Vendors are always going to be late.  Production is always going to be disrupted because of shortage of labor or material or machine break downs, customer service is unwilling to update the delivery dates until the customer calls.  

My newest client will send out excel spreadsheets to their suppliers requesting updated delivery information. This is a automated process that uses a field on the vendor to indicate the frequency for generating the report which then gets imported to update the PO’s when the vendor returns the file.