Where MES ends and ERP begins: who owns which data
One rule decides it: things managed by day and by money belong to ERP; things managed by minute and by physical unit belong to MES. Most conflicts sit in work-order numbers, stock definitions and BOM versions.
The division of labour between MES and ERP comes down to one line: what is managed by the day and by money belongs to ERP; what is managed by the minute and by physical units belongs to MES. Planning, finance and purchasing sit in ERP; execution, equipment and operations sit in MES.
The basis: time scale and object granularity
| Dimension | ERP | MES |
|---|---|---|
| Time scale | Days, weeks, months | Minutes, seconds |
| Object granularity | Work orders, batches, material groups | Individual boards, reels, stations |
| Main questions | How much to make, what it costs, when to deliver | Where it is now, what was used, who did it |
| Data source | Human entry and documents | Scans, equipment capture, station terminals |
Both manage work orders, but different sides of them: an ERP work order is a planning unit and a cost-collection object, while an MES work order is an execution unit that is broken down into operations, machines and people.
The three points of most conflict
Work order numbers
Does ERP generate the number and MES reuse it, or does MES create its own? Reuse it, and let MES split sub-orders in production (batch launch, shift spanning) expressed as "ERP order number plus sub-batch". Two independently generated numbers will never reconcile afterwards.
Inventory definitions
ERP inventory is book inventory, moved by receipt and issue documents; MES inventory is physical material at the line, moved by scans. They differ by nature, and the differences come from:
- Issued to the line but not yet loaded (ERP has deducted, MES has not consumed)
- Scrapped after loading but not returned
- Leftover counting at different moments
The fix is to state who owns line-side stock: MES owns it, ERP only sees the "issued" status and keeps no line-side detail. To see the combined total, write MES line-side data back to an ERP line-side warehouse.
BOM versions
The ERP BOM is the engineering and costing BOM; what MES uses is the manufacturing BOM with substitutes, feeders and side. Substitution rules usually live only in MES, because they are an execution-level judgement that changes per work order.
The risk: ERP changes the BOM version and MES does not know, so the line keeps loading against the old one. There has to be a version synchronisation step, and MES must record which BOM version a production run used.
Four standard integration points
- Work order release: ERP → MES, with order number, part number, quantity and due date
- Material master: ERP → MES, with part number, name, unit and batch rules
- Completion reporting: MES → ERP, with good quantity, defect quantity, labour hours and material consumption
- Inventory movement: MES → ERP, with line-side consumption and returns
For anything beyond these four, first ask on what time scale the data changes; the answer points to the owner.
What happens with ERP alone
The usual result: work-order status in ERP has to be entered by hand after the shift, which pushes execution data back by a shift. Reporting is unreliable, WIP quantity is unclear and traceability stops at batch level. ERP cannot solve these by itself because it has no operation-level capture point.
The reverse, MES with no ERP, leaves planning and costing in Excel and turns MES into an island. Both are needed; the interfaces do not have to be many, four are enough.
Frequently asked questions
FAQ
- Can MES replace ERP?
- No. MES has no finance, purchasing, sales or costing, and does not balance capacity at the planning level. The two cover different time scales, so replacement does not apply.
- Who should generate work order numbers?
- ERP generates them and MES reuses them, allowing sub-batch splits. Independent numbering on both sides makes completion reporting impossible to reconcile one to one.
- Whose inventory is material at the line?
- Let MES hold the detail and ERP see only the issued status. If both maintain line-side detail, counting differences persist and responsibility cannot be assigned.
- How many interfaces does the integration need?
- Four in the usual case: work order release, material master, completion reporting and inventory movement. The count is not the issue; field definitions and update points belong in the interface document.