Service
ERP and MES integration
We bring work orders down from the ERP to the shop floor and post actual output, scrap and material consumption back. Manual production postings and end-of-shift spreadsheet uploads go away.
Our clients
- Siemens
- Anadolu Isuzu
- BSH
- Tofaş
- Toyotetsu
- Martur
- Turkcell
- Vodafone
- Doğadan
- Pakmaya
- Bross
- Abdi İbrahim
- Nobel İlaç
- Plastimak
- Dalgıç Kalıp
- Barbaros Motor
- Magneti Marelli
- Rözmaş
- Sanel
ERP–MES integration connects planning and the shop floor to the same data. Work orders, bills of material and routings flow down from the ERP; produced quantities, scrap, material consumption and actual times flow back. Without it, feedback is usually typed in at the end of a shift and the ERP’s inventory, costs and delivery dates lag reality by a day.
We work with SAP, Microsoft Dynamics and the ERPs common in Türkiye such as Logo, Netsis, Mikro and Canias, always through the ERP’s supported interface: RFC/BAPI, IDoc or OData services for SAP, the vendor APIs for the others. We do not write directly into ERP tables with SQL; that bypasses the ERP’s business rules and breaks with the next upgrade.
The hard part of these projects is master data, not connectivity. If machine codes, material numbers, units and operation numbers differ between the ERP and the floor, no interface produces correct results. We start with mapping tables and log every message as sent, received and processed.
What we deliver
ERP–MES Integration
-
Work-order download
Released work orders flow from the ERP to the MES and operator panel together with BOM and routing data. Changes and cancellations follow the same path.
-
Production feedback
Good quantity, scrap, actual times and material consumption are posted back to the ERP. Whether feedback is real-time, at order completion or at shift end is chosen to fit the ERP’s costing and inventory logic.
-
Master data mapping
Mapping tables are built for machines, work centers, materials, units and downtime codes, each with a named owner. Unmatched records do not vanish; they land in an error queue.
-
Reliable messaging
Every message carries a unique ID, so a resend never creates a duplicate posting. If the ERP is unreachable, messages queue in order and are processed when it returns.
-
Reconciliation reports
Production recorded in the MES is regularly compared with what was posted to the ERP. Any gap points to the specific work order and message.
How a project runs
From discovery to live, step by step
- 01
Process and interface analysis
The ERP production process, work-order lifecycle and available interfaces are reviewed with the ERP consultant and IT. Which data flows in which direction and how often is written down.
- 02
Master data mapping
Machine, work-center, material and unit codes are compared on both sides; mapping tables are built and owners assigned.
- 03
Build in a test environment
The integration is first built against the ERP’s test company or test system. Error, resend and outage scenarios are tested deliberately.
- 04
Go-live and reconciliation
After go-live, reconciliation reports are checked daily in the first period. Manual posting stays available as a fallback until gaps are closed.
Built on Proxus
Integration flows are built on Proxus connectors for ERPs, databases and messaging, including SQL Server, PostgreSQL, REST services and Kafka. Proxus buffers messages through outages, so feedback to the ERP is not lost.
Proxus is the industrial data platform built by the VOLSOFT team.
Frequently asked questions
Common questions
What is MES integration with ERP?
MES–ERP integration means work orders from the ERP reach the shop floor automatically, and actual output, scrap and consumption flow back to the ERP automatically. Inventory, costs and order status then update without waiting for manual entry. ISA-95 is the standard that defines the data exchanged between the two layers.
How does MES integration with SAP work?
MES integration with SAP typically uses RFC/BAPI calls, IDoc messages or OData services. Production orders from SAP PP flow down to the MES, and confirmations and goods movements are posted back. The method is chosen to fit the SAP release and the customer’s SAP team standards.
Can you integrate with Microsoft Dynamics 365?
Yes. Dynamics 365 integration uses its supported web services and data entities for production orders, route cards and consumption journals. The exact entities depend on the Dynamics edition and the customer’s configuration, which we review with their partner.
Why not write directly to ERP database tables?
Because direct writes bypass the ERP’s business logic, such as inventory postings, costing and validations, and they often break after an upgrade. Supported interfaces are slower to build but keep the ERP consistent and supportable by its vendor.
How do you avoid duplicate postings?
Every message carries a unique ID and the ERP side never processes the same ID twice. When the network or the ERP is down, messages queue in order and are processed once, without loss or duplication.
Related pages
Often looked at together
- Solution OEE Software OEE software fed by PLC and CNC data, with downtime reasons, work orders and ERP sync. Explore →
- Solution Industrial IoT Platform Proxus: PLC connectivity, edge, UNS, historian and ERP integration in one on-premises platform. Explore →
- Industry Automotive Data collection on press, welding and assembly lines, IATF 16949 traceability and OEE. Explore →
- Industry Appliances and electronics Takt and downtime tracking, end-of-line test records and serial traceability on assembly lines. Explore →
Next step
Let’s turn your goal into a clear engineering scope.
Tell us about your plant, your machines and your goal. An integration engineer will set up a discovery call with you.
