Share
Report
12We are a make to order mfg company. We Issue a Sales Order with multiple line and track delivery of each line to a different location.
From a production standpoint, it is more efficient for us to produce each unit consecutively before we start the next "job"/Sales Order.
We have tried every config we can think of to ensure that planned production orders don't intermix after planning optimization runs, to no avail. The closest we "thought" we were, was to use priority-based planning, but this would never produce the desired results.
An example is, we could have two SO's. Each having 5 lines.
SO #1 has five SO lines for item #A1, each line at a qty of 1. Requested Ship date = 9/30/25
SO #2 has five SO lines for item #B2, each line at a qty of 1. Requested Ship date = 10/2/25
We produce 1 item per day.
After planning optimization runs, our planned production orders look like this:
OrderDate (start date) - Item
9/23 - #A1
9/24 - #A1
9/25 - #B2
9/26 - #B2
9/27 - #A1
9/28 - #B2
9/29 - #B2
9/30 - #A1
10/1 - #B2
10/2 - #A1
when we would like it to look like this so we can complete the sales order and be more efficient in production, as well as have all bill of material items in house when we start the job:
OrderDate (start date) / Item
9/23 - #A1
9/24 - #A1
9/25 - #A1
9/26 - #A1
9/27 - #A1
9/28 - #B2
9/29 - #B2
9/30 - #B2
10/1 - #B2
10/2 - #B2
We have looked into priority-based planning, sequencing, and priority. None give the required results of grouping the Sales Order lines together in planning optimization.
The preferred behavior would be for Planning Optimization to consider:
Order by Requested Ship date and group by Sales Order number.
Even if we manage requested ship dates, Planning Optimization still seems to mix up the Sales Order lines.
Categories:
I have the same question (0)
All responses (
Answers (
