Keeping a manufacturing execution system (MES) while replacing the ERP means deciding which production records remain authoritative, which transactions must cross the boundary, and when the receiving system can treat them as accepted. The central question is not simply whether the systems connect. It is whether a production event still produces the right operational, inventory and accounting records after the ERP changes.
ERP consultant Francesco Perrotta identifies difficult integration with existing applications as a factor behind ERP migration decisions. He also recalls an implementation involving a difficult MES integration. That makes the retained MES part of the migration scope, even when its shop-floor workflows are not being replaced.
The useful distinction is between business planning and accounting, production execution, and the transactions that reconcile them. Allocate those responsibilities explicitly rather than assuming the labels “ERP” and “MES” settle the design.
Assign authority to records, not product categories
Start by separating permission to plan work, evidence of what happened on the shop floor, and authority to post its inventory or financial consequences. For a retained-MES design, you might assign production-order release and accounting records to ERP, while MES controls execution and captures actual production events. Treat that as an allocation to confirm against your applications, not a universal functional boundary.
The manufacturing-selection webinar connects industry fit with production, finance, inventory and warehouse functionality, then stresses the need for integration capability. These belong in the same evaluation: determine what the replacement ERP should do before deciding what the retained MES must exchange with it.
For each important record, specify:
- Authority: which system may create or change it, and who approves the change.
- Identity: how the order, operation, material, lot and reporting event are recognized across systems.
- Meaning: whether a quantity represents planned usage, actual consumption, good output or scrap.
- Acceptance: what confirms that the receiving system has applied the transaction.
- Correction: how an accepted record is amended without losing its relationship to the original event.
Do not assign ownership only at the level of “the production order.” An order's authorization, execution history and accounting status need separate decisions. Likewise, deciding what should be common across plants does not settle who owns a material-consumption record within a plant.
Follow a production order across the boundary
Consider an illustrative order to manufacture a batch of components. In this design, ERP authorizes the order and maintains inventory and cost records; MES directs execution and records what operators actually produce and consume.
A concrete reference is the Dynamics/MES implementation presented in Inductive Automation's production-order integration session. There, release triggers an order message, MES retrieves the bill of materials and routing, and subsequent reports return consumption, time, finished output and an order-ended notification. Those mechanisms belong to that implementation; they are not default behavior for every ERP/MES connection.
Release and execution start
In the presented implementation, changing the Dynamics order to released triggers a lightweight Service Bus message containing the production-order number and high-level details. MES then requests the bill of materials and routing. Execution may start immediately or wait for a user event.
For the illustrative order, preserve the distinction between “authorized for production” and “physically started.” During migration, keep a durable relationship between the existing MES order identity and the replacement ERP's identity. Also specify which version of the materials and routing the released order authorizes. A recognizable order number is not enough if the systems associate it with different instructions.
Material consumption
The demonstrated integration reports consumption as quantity, lot code and time so ERP can handle inventory. For the illustrative order, decide whether MES supplies actual material usage or whether ERP derives usage from reported output.
The presenters describe the latter alternative as backflushing ideal quantities when finished goods are reported, instead of reporting actual consumption. That distinction matters: an output-based calculation should not be treated as evidence of the material actually used. If actual consumption reporting is selected, prevent a separate output-based deduction from charging the same usage again.
Production reporting and scrap
In the demonstrated process, production time and finished output are separate reporting steps. ERP may use time for costing or recordkeeping, while finished output can be reported at the end of each batch.
For the illustrative order, keep good output and scrap distinguishable. Decide where the scrap event originates, how it relates to the order or operation, and which receiving transaction accounts for its consequence. Make the meaning of each quantity explicit: does “produced” include rejected pieces, or only accepted output? Do not make the receiver infer that answer from a total.
Apply the same discipline to corrections. If an operator changes a scrap classification or consumption quantity, identify the original event and specify how its ERP consequence is corrected. A change to the MES record should have an explicit accounting counterpart wherever one is required.
Completion
The presentation separates finished-goods reporting from a final production-order-ended notification. Preserve that distinction in the illustrative design: finishing physical work, recording output and closing an order for accounting should have explicit acceptance conditions.
Before accepting completion, decide what must already be accepted, including consumption, output and relevant adjustments. Otherwise, “complete” becomes an ambiguous label rather than a reliable statement about the order.
Make disagreement visible and recoverable
Suppose the illustrative order has physically consumed material, but its consumption report has not been accepted by ERP. MES can show the operational event while ERP still lacks the corresponding inventory transaction. If an output report is also delayed, ERP may lack finished stock that the shop floor has already produced. These are different views of progress, not necessarily contradictory observations.
The design should therefore distinguish recorded in MES, sent and accepted in ERP. Keep the event time separate from the receiving system's acceptance or posting time. This lets production and finance identify what happened and what remains unapplied without treating a transport acknowledgment as proof of a business posting.
Define recovery around the transaction's meaning:
- Rejected report: retain the event, expose the rejection reason and assign responsibility for correcting the cause.
- Uncertain delivery: check whether the business transaction was accepted before resending it. Require a stable reporting-event identity so repeated delivery can be recognized.
- Out-of-sequence report: specify whether the receiver must hold, reject or safely apply it. Include completion arriving before related consumption in the acceptance scenarios.
- Accepted but incorrect report: define the supported adjustment or reversal path, preserving the connection to the original event.
Require these outcomes from the integration design and verify them against the selected products. Do not assume that using a queue supplies duplicate protection, business-level ordering or accounting corrections.
Reconciliation should compare accepted quantities and outstanding events, not merely whether both systems display a closed status. Where totals differ, the responsible team should be able to trace the difference to individual reports rather than overwrite a total to make the screens agree.
Preserve transaction continuity through the migration
For orders already active in MES, define which ERP receives their remaining reports and how their identities carry forward. Keep reporting events traceable across the change so a pending consumption report cannot be mistaken for a new event, and an accepted report cannot be posted again merely because the destination has changed.
Resolve ownership before choosing the implementation mechanism. Once responsibility is clear, the configuration and customization decision can address how to deliver it. A custom interface should implement an agreed boundary, not conceal an unresolved ownership question.
This transaction evidence also belongs beneath ERP go-live approval: sponsors need confidence that production reports reach the correct records and that unresolved exceptions have owners. Organizational readiness and transaction continuity support the same decision, but they answer different questions.
The migration boundary is clear when you can explain who authorizes work, who records execution, who posts its consequences and how disagreements are resolved. If those responsibilities remain unclear, Digiventi's ERP specialists can help you work through the planning, inventory and integration requirements alongside the retained MES.