Skip to main content
Solved

MRP creates an additional planned purchase order even though an actual purchase order already exists

  • April 14, 2026
  • 2 replies
  • 55 views

Forum|alt.badge.img

Hi everyone,

We were having issue with the MRP,

We have two separate projects, and each project has one Production order. Both production orders use the same BOM and the same material item. Both Projects are configured with inventory tracking = Track by Project quantity and cost.

Scenario details:

Projects ID

Production Order Nbr

Start Date

BOM ID

Purchase Order

PROJ-VK-45

ORDER41326

5/11/26

BOM1

008815

JB-007

ORDER2

4/27/26

BOM1

 

 

Test steps:

  1. Created both production orders under two different projects.
  2. Since ORDER2 had the earlier start date, I placed ORDER2 on hold for testing purposes.
  3. Ran Regenerate Inventory Planning.
  4. Based on the demand from ORDER41326, the system created the supply suggestion, and we created a Purchase Order 008815
  5. Then I removed ORDER2 from hold
  6. Ran MRP again
  7. Reviewed Inventory Planning Results by Item.

Issue observed:

After the second MRP run, the system shows:

 

My concern is that an actual purchase order already exists for ORDER41326, but the system still generates an additional Planned supply instead of recognizing the existing purchase order as the correct supply.

Attached all relevant screenshots.

Any solution, guidance, clarification, or recommended workaround to prevent MRP from creating an extra planned purchase order when an actual purchase order already exists would be greatly appreciated.

Best answer by PragatiMalviya64

@PrasadNaidu06 

Acumatica MRP/DRP does not maintain a hard link between a purchase order and the demand that triggered it - this is by design, not a bug. Once a PO exists, the planning engine treats it purely as floating supply: a quantity arriving on a date. It does not ask "was this PO already created for that production order or sales order?" It simply nets all supply against all demand for the same item and warehouse, and if there is a gap in timing or quantity, it recommends a new planned order regardless of what already exists. Supply and demand are matched by date and quantity, not by document relationship.
You can vote and provide the use case in the community idea for the hard pegging: MRP/Inventory Planning Display should carry demand type and transaction number over to create supply order | Community

The following community discussions cover this topic as well:

To understand how Acumatica MRP/DRP handles supply, demand, and pegging in detail, the whitepaper is the best starting point: Material Requirements Planning (MRP/DRP) Whitepaper | Community

 

2 replies

Forum|alt.badge.img+2

@PrasadNaidu06 

Acumatica MRP/DRP does not maintain a hard link between a purchase order and the demand that triggered it - this is by design, not a bug. Once a PO exists, the planning engine treats it purely as floating supply: a quantity arriving on a date. It does not ask "was this PO already created for that production order or sales order?" It simply nets all supply against all demand for the same item and warehouse, and if there is a gap in timing or quantity, it recommends a new planned order regardless of what already exists. Supply and demand are matched by date and quantity, not by document relationship.
You can vote and provide the use case in the community idea for the hard pegging: MRP/Inventory Planning Display should carry demand type and transaction number over to create supply order | Community

The following community discussions cover this topic as well:

To understand how Acumatica MRP/DRP handles supply, demand, and pegging in detail, the whitepaper is the best starting point: Material Requirements Planning (MRP/DRP) Whitepaper | Community

 


Forum|alt.badge.img
  • Author
  • Freshman I
  • April 22, 2026

@PragatiMalviya64 Thank you for response and clarification.