- Feature
- Auto-scale and priority scheduling for message processor queues
- Availability
- Generally available in Supply Chain Management 10.0.49 (enhancement)
- Industry focus
- Packaging manufacturers
Packaging plants run fast. Lines producing cartons, films, bottles or labels generate a constant flow of production events: starts, completions, scrap, material consumption and quality results. When those events come from a manufacturing execution system (MES) or line automation, they reach Dynamics 365 as messages that must be processed quickly to keep inventory, costing and planning up to date.
The industry challenge
Dynamics 365 uses a message processor to handle inbound messages from integrations such as third-party MES. When the processor runs on a single batch server, it can become a bottleneck at high volumes. Messages queue up, inventory and order status lag behind reality, and planners and warehouse teams make decisions on stale information.
Not all messages are equally urgent, either. A production order completion that releases stock for shipping matters more right now than a routine counter update. Without prioritization, important messages wait behind less important ones. Plants respond with throttling at the MES side or with custom processing jobs, which adds complexity.
What Microsoft delivered in Supply Chain Management 10.0.49
Supply Chain Management 10.0.49 allows the message processor to auto-scale beyond a single batch server. It also adds priority settings, assignment to batch groups and a maximum concurrency setting.
Organizations can process more messages in parallel, decide which queues are handled first and control how much capacity the processor uses.
Where the value shows up
| Business area | Impact |
|---|---|
| Data timeliness | Production events reach Dynamics 365 faster during peaks |
| Prioritization | Critical messages, such as completions, can be handled ahead of routine ones |
| System stability | Concurrency limits stop message processing from overwhelming other batch work |
| Integration design | Less need for custom throttling or processing jobs |
| Planning and shipping | Inventory and order status closer to real time |
A worked scenario
(An illustrative example.) A flexible packaging manufacturer runs a dozen high-speed lines connected to an MES that sends production reports to Dynamics 365. At shift changes, a burst of completion and consumption messages arrives at once, and the queue backs up for an hour, delaying the release of finished rolls for shipping.
The IT team configures the message processor to scale across additional batch servers, puts it in a dedicated batch group, gives production completion messages a higher priority and sets a maximum concurrency so other batch jobs are not starved. At the next shift change, completions are processed first, and shipping can release finished goods without waiting for the whole queue to clear.
Adoption considerations
- Measure current backlogs. Understand when and how much the queue backs up today.
- Plan batch capacity. Scaling out needs batch servers and capacity in your environment; review with your infrastructure team.
- Define priorities. Agree with operations which message types matter most.
- Set sensible concurrency. Too high can affect other batch work; too low leaves gains on the table.
- Monitor and tune. Track queue times after the change and adjust.
The bottom line
For high-speed packaging manufacturers, the value of MES integration depends on how quickly production events reach the ERP. Auto-scaling, prioritization and concurrency control for the message processor help keep data current at peak times without custom workarounds. The configuration needs care, but the payoff is better operational visibility. An experienced Dynamics 365 manufacturing adviser can help you design the set-up.
Source: Microsoft: What's new or changed in Dynamics 365 Supply Chain Management 10.0.49