MES sends production results back into ERP through controlled integration points, usually by posting production confirmations, material consumption, labor, scrap, quality status, and inventory movements against ERP production orders. In regulated plants, “real time” usually means event-driven or near real time after an operation, inspection, batch step, or transaction is completed and checked. It should not be assumed to mean every machine signal is written directly into ERP.
What is typically sent
The exact payload depends on the ERP, MES, process model, and validation scope, but common production results include:
- operation start, completion, hold, and status changes;
- good quantity, scrap quantity, rework quantity, and reason codes;
- material issues, backflush consumption, substitutions, and lot or serial usage;
- labor time, machine time, and sometimes setup time;
- inspection results or quality disposition status, where the interface is approved for that use;
- finished goods receipt, work-in-process movement, or inventory location updates;
- genealogy and traceability references, if ERP needs them rather than only MES or QMS.
How the interface usually works
MES typically receives the production order, routing, bill of materials, material master, and work center data from ERP. Operators, equipment, or automated checks then execute the work in MES. When a defined event occurs, MES sends a transaction back to ERP through an approved interface.
Common mechanisms include ERP APIs, web services, message queues, middleware, IDocs, BAPIs, database staging tables, or controlled file drops. The technology matters, but the data contract matters more. Both systems need to agree on order numbers, operation numbers, material identifiers, units of measure, lot and serial rules, status codes, and timing rules.
Real time has limits
Real-time integration is not automatically better. Posting too early can create inventory, costing, or traceability errors if the operation later fails inspection or is reversed. Posting too late can make ERP planning, available-to-promise, and inventory visibility inaccurate. Most plants define specific transaction boundaries, such as operation complete, batch phase complete, inspection accepted, or final goods receipt.
Latency also depends on network reliability, middleware design, ERP transaction load, validation rules, and exception handling. In many regulated environments, a reliable near-real-time interface with reconciliation is safer than a fragile synchronous interface that stops production when ERP is unavailable.
Failure modes that need controls
The common failures are not exotic. They are usually master data mismatches, duplicate postings, missing reversals, unit-of-measure errors, unhandled scrap or rework paths, lot and serial mismatches, or transactions posted to the wrong operation. These failures can affect inventory, costing, genealogy, and production order status.
Good interfaces include message logging, retries, idempotency or duplicate protection, error queues, operator-visible exception status, and reconciliation reports between MES and ERP. In regulated environments, changes to these mappings and rules normally require change control, testing, and validation evidence appropriate to the process risk.
Brownfield reality
In brownfield plants, MES rarely connects to ERP in isolation. The same production event may also affect PLM-controlled definitions, QMS nonconformance workflows, maintenance systems, label systems, warehouse systems, or customer-specific portals. The interface design has to respect which system is authoritative for each record.
Full replacement of ERP, MES, or surrounding systems is often unrealistic in aerospace-grade and similarly regulated environments. Qualification burden, validation cost, downtime risk, integration complexity, traceability obligations, change control, and long equipment lifecycles usually favor phased integration, data cleanup, and controlled coexistence over a clean-slate cutover.
What must be defined before go-live
Before treating the interface as real time, the site should define which events trigger ERP postings, which system owns each field, how exceptions are handled, how reversals work, how partial completions are treated, and how MES and ERP are reconciled. Without those rules, real-time posting can simply move bad data faster.