Skip to main content
Question

Split SOs (Budget-Driven) – Forcing Single Production Order in MRP

  • April 23, 2026
  • 2 replies
  • 18 views

We’re currently preparing for an MRP implementation in Acumatica, and one of the key risks we’re anticipating is how the system will handle split Sales Orders tied to the same item.

Due to capital budget constraints, it’s common in our environment for a single project/item to be split across multiple Sales Orders—sometimes up to 6–8 based on customer capital funding limits (typically around $5,000 per order). From an operational standpoint, these do not represent separate demand signals; they reflect a single underlying requirement that is fragmented for financial reasons.

Our concern is how MRP will interpret this structure:

  • Will each split SO be treated as independent demand, potentially inflating supply signals?
  • What is the best way to maintain a unified supply strategy (single PO or Production Order) while demand is distributed across multiple SOs?
  • Are there recommended configurations, linking mechanisms, or planning practices to prevent duplicate or excessive planned orders in this scenario?

The goal is to avoid a situation where MRP overstates demand or generates redundant supply recommendations due to administrative order splitting rather than true demand variability.

If anyone has experience with similar constraints—particularly in capital equipment or hybrid MTO/ATO environments (Hardware is sub fabricated, assembled/dressed in house) —I’d appreciate any guidance on system setup, data structure, or process controls that have worked effectively.

2 replies

angierowley75
Acumatica Moderator
Forum|alt.badge.img+3
  • Acumatica Moderator
  • April 23, 2026

Can you provide an example of how the sales orders are split?

Are you splitting the same item across multiple sales orders and adjusting quantities?

With MRP you can consolidate like items so when the recommendation is made to purchase/manufacture to satisfy the demand, you can generate 1 PO or 1 Production Order.

 


  • Author
  • Freshman I
  • April 24, 2026

The Sales Orders are being split based on price. In the example referenced, the demand was divided across eight separate SOs—covering two manufactured units along with additional accessories that would be assembled on the manufactured units.

Many of our customers operate under a capital spending cap (typically around $5,000 per order). Since each unit exceeds $8,000 per unit, they work around this constraint by using the same item code across multiple SOs and reducing the unit price on each order to stay within the limit—in this case, two SOs per sink.

From a financial perspective, this achieves compliance with the customers’ budget constraints. However, from a production and planning standpoint, this introduces significant risk because the same item appears across multiple SOs at a discounted price, I am concern MRP may interpret these as independent demand signals, potentially making it appear as though four units are required instead of the actual two.

We are currently in the early phase of our MRP implementation.