Manufacturing & custom software · Bengaluru · Whitefish, USA
Manufacturing

Following One Work Order Through ERP and MES: Where Each System Takes Over

A step-by-step walk through a single work order — from sales order to dispatch and costing — showing what the ERP does, what the MES does, and exactly which data passes between them at each handover.

By Corposol Team··9 min read
Operator at a CNC tool grinding machine in a production workshop
Photo: Станок Schutte 305 на заводе Авиаагрегат г. Самара by Vlad chernenko, CC BY-SA 3.0 (cropped)

Most explanations of ERP and MES compare the two systems side by side. That's useful for understanding what each is for — our guide to the difference between MES and ERP does exactly that. But factories don't run on comparisons; they run on work orders. This guide follows one work order from the customer's purchase order to dispatch and costing, and shows at each step which system is in charge and exactly what passes from one to the other.

The example is a typical Indian engineering SME: a customer orders 500 machined flanges, made from forged blanks, with turning, drilling, an outside zinc plating process and final inspection. The same pattern applies to most discrete manufacturing.

Step 1: Sales order (ERP)

The customer's purchase order arrives and is entered as a sales order in the ERP: customer, part number, drawing revision, quantity 500, rate and delivery date. The ERP checks the customer's credit position and the drawing revision against the part master. Nothing has happened on the shop floor yet, and the MES knows nothing about the order.

Owned by ERP: customer, commercial terms, delivery promise.

Step 2: Planning and material (ERP)

The ERP's planning function explodes the part's BOM: 500 forged blanks (plus an allowance for setup and rejections), packing material and plating as an outside process. It checks stock: 300 blanks are available; 220 must be purchased. A purchase order goes to the forging supplier with a delivery date that supports the order. The planner decides when the work order should start, based on machine load and material arrival — see our guide to production planning.

Owned by ERP: material requirements, purchase, planned dates.

Step 3: Work order release — the first handover

When material is available and capacity is planned, the work order is released. This is the key handover. The ERP passes to the MES:

  • Work order number, part, drawing revision and quantity.
  • The routing: operations in sequence — turning on CNC lathe group A, drilling on VMC group B, plating at an approved vendor, final inspection — with standard times.
  • The material to be issued, from the BOM.
  • Planned start and finish dates, and priority.
  • Inspection requirements per operation.

From this moment, the MES is responsible for executing the order.

Rule: don't release orders whose material isn't available. A released order that can't start clutters the floor and makes the MES's WIP picture meaningless.

Step 4: Material issue (ERP stock, MES consumption)

Stores issues 510 blanks against the work order, scanning the forging lot. Stock decreases in the ERP; the MES records which material lot is now with the order, which is the start of traceability. See our guide to material issue against the BOM.

Data flow: issue quantity and lot from stores to both stock (ERP) and the order's genealogy (MES).

Step 5: Operations on the floor (MES)

The MES puts the job on the turning section's list. The operator scans the job card, starts the operation, sees the drawing and setup sheet, performs a first-off check, and books output as it progresses: 506 good, 4 rejected for undersize bore, with the reason. Downtime during the job — a tool change, a short breakdown — is booked with reasons. The order moves to drilling, where the same happens.

The ERP doesn't need every tap. It needs to know the order is progressing, and roughly where. The MES knows everything: which machine, operator, times, quantities and checks.

Owned by MES: operation status, actual times, operator, machine, in-process quality.

Step 6: Outside processing (both)

After drilling, 502 good flanges go for plating. The job-work challan is a document with financial and GST implications, so it belongs with the ERP; the order's status — "at plating vendor since Tuesday" — belongs in the MES so that WIP is complete. When the parts return, receipt quantity and the vendor's coating certificate are recorded; 2 parts are rejected for coating defects. Both systems are updated. Our guide to planning around job-work vendors covers this step.

Step 7: Final inspection (MES, with QMS)

Final inspection checks the critical dimensions and coating thickness on a sample, recorded on a tablet with the gauges scanned. The lot passes; 500 good flanges are accepted. Had it failed, an NCR would have put the lot on hold, and neither system would allow it to be packed or dispatched until disposition. See quality management software.

Step 8: Completion — the second handover

The MES reports completion of the work order back to the ERP:

  • Good quantity completed: 500.
  • Rejections by operation and reason: 4 at turning, 2 at plating.
  • Material consumed: 510 blanks issued, 6 scrapped as rejects, 4 returned unused.
  • Actual times per operation.
  • Lot number for the finished goods, linked to the material lot and processes.

The ERP adds 500 flanges to finished-goods stock, closes the work order's material, and makes the goods available for dispatch.

Rule: completion must be reported promptly. A finished order that the ERP doesn't know about can't be dispatched or invoiced, and stock is wrong until it is.

Step 9: Dispatch and invoice (ERP)

Dispatch picks the 500 flanges, generates the delivery challan and tax invoice against the sales order, and records the finished-goods lot on the dispatch. The lot link means that if the customer ever raises a complaint, the full history — material, machines, operators, inspections — is a click away.

Step 10: Costing (ERP, from MES data)

With actual material, times, rejections and outside processing costs, the ERP calculates the work order's actual cost and compares it with the estimate used for the quotation. If drilling took much longer than standard, or rejections at turning were high, the variance appears here — and the next quotation for this part can use the real numbers. Our guide to job costing covers the method.

The handovers at a glance

HandoverFromToData
ReleaseERPMESOrder, part, revision, quantity, routing, BOM, dates
Material issueStoresERP and MESQuantity, material lot
ProgressMESERP (summary)Current operation, quantity complete
Outside processERP and MESBothChallan, status, receipt, certificate
CompletionMESERPGood and rejected quantity, consumption, times, lot

What goes wrong — and the rules that prevent it

  • Routing changes not reaching the floor. Engineering changes the routing in the ERP after release; the floor keeps working to the old one. Rule: changes to released orders go through a defined change step that updates the MES.
  • Quantities that disagree. The ERP shows 500 ordered, the MES shows 512 started, stores issued 520. Rule: each quantity has one owner, and differences must be explained before closure.
  • Orders never closed. Old orders stay open in one system, distorting WIP and costs. Rule: completion in the MES closes the order in the ERP, and a weekly report lists orders with no activity.
  • Double entry. Someone types MES completions into the ERP by hand. Rule: data passes between systems automatically, or both are modules of the same system.

Partial completions and split orders

Real orders rarely run as neatly as the example. A customer asks for 200 flanges urgently from the 500; the planner splits the work order or allows a partial completion. The MES must then report 200 completed and passed to finished goods while the remaining 300 continue, and the ERP must allow a partial dispatch against the sales order. Each partial completion should carry its own finished-goods lot, linked to the same material lot, so traceability is kept for both shipments. Rules for when splits are allowed — and who approves them — prevent the confusion of orders split on the floor without anyone telling the office.

Rework loops

When parts fail inspection and can be reworked, they leave the normal sequence: they go back to an earlier operation or to a rework station, then return for re-inspection. The MES should record rework as its own operation against the work order, with time and result, so the order's quantities stay consistent and rework cost is visible. The ERP needs only the outcome — how many good parts finally completed and how many were scrapped — but the costing benefits from knowing how much rework time was spent.

Engineering changes mid-order

Sometimes the customer issues a new drawing revision while an order is in progress. The ERP updates the part and the sales order; the MES must show the floor which operations are affected and whether parts already made to the old revision can be used, reworked or must be scrapped. That decision belongs to engineering and quality, often with the customer's agreement, and should be recorded against the work order. Without a defined process, old-revision parts can quietly reach the customer — one of the most damaging errors a supplier can make.

Reports that need both systems

Some of the most useful reports combine ERP and MES data: on-time delivery with the operation that caused each delay; job cost with actual times and rejections per operation; customer complaint history linked to production conditions. When the two systems are separate, these reports need data from both, which is another reason SMEs often prefer a single system with both sets of functions on one database. When they are separate, make sure the shared keys — work order number, part number, lot number — are identical in both, so reports can join them reliably.

One system or two?

Large companies often run a packaged ERP and a separate MES with an interface between them. For SMEs, a single custom system with ERP and MES modules on one database is often simpler: there is no interface to build and maintain, and the "handovers" above are just status changes on the same record. If you already have an ERP you want to keep, the MES can exchange data with it where the ERP offers an API or import facility — something to confirm during scoping. Either way, the logic of who owns what at each step is the same.

A checklist for your own handovers

  • When exactly is a work order released, and who decides?
  • What does the floor receive at release — routing, drawing, material, checks?
  • How is material issue recorded, and does it capture lots?
  • How are progress, rejections and downtime booked, and who sees them?
  • How are outside processes tracked while parts are away?
  • What exactly is reported at completion, and how quickly?
  • Who owns each quantity, and how are differences resolved before closure?

If you can answer each of these clearly, your ERP and MES — whether separate systems or modules of one — will work together. If not, the answers are worth settling before any software is built.

Walking one real work order through your factory with these questions in hand, from purchase order to invoice, is the best way to find the gaps before choosing or building software.

Working with Corposol

Corposol builds custom manufacturing ERP and MES software for Indian SMEs, usually as modules of one system on the same database. Read our use case for a hydraulic equipment manufacturer. All custom code is transferred to you on final payment.

Frequently asked questions

Where does the ERP stop and the MES start?

At work order release. The ERP decides what to make and when, and reserves material; the MES takes the released order and manages its execution operation by operation; completion and consumption flow back to the ERP.

Do we need two separate systems?

Not necessarily. In many SMEs, ERP and MES functions are modules of one custom system on the same database, so there is no integration to maintain. The handovers described here still apply, as steps within one system.

What data flows from MES back to ERP?

Quantities completed and rejected per operation, material consumed by lot, actual times, scrap, and completion of the work order — the data the ERP needs for stock, costing and delivery commitments.

What goes wrong at the handovers?

Orders released without material, routing changes not reaching the floor, completions not reported back, and quantities that disagree between systems. Each is prevented by clear rules about which system owns which data.

  • ERP and MES
  • Work order
  • ERP MES integration
  • Manufacturing software
  • Shop-floor data

Let's discuss your factory's software

Tell us about your process or idea. You'll get a free consultation and a clear, fixed quote — no obligation.

  • Free consultation
  • Prototype before you commit
  • Fixed, itemised quote
  • You own the software

Get a free quote

We reply within one working day. Your details are never shared.