Yes, a manufacturing execution system can integrate with SAP. In fact, connecting the two is one of the most common setups in modern production environments. SAP handles the business side of things, while a MES manages what actually happens on the shop floor. Together, they give you a complete picture of your operations, from purchase order to finished product.
If you’re wondering whether this kind of integration is realistic for your situation, the short answer is: it depends on the systems involved and how you approach it. But the good news is that MES–SAP integration is well established, and there are clear methods and standards that make it work. Let’s walk through the most common questions people have about it.
What is a manufacturing execution system, and how does it relate to SAP?
A manufacturing execution system (MES) is software that monitors, controls, and documents production processes on the shop floor in real time. SAP is an ERP system that manages business-level data such as orders, inventory, finance, and planning. The two systems sit at different layers of your operation and are designed to complement each other, not replace one another.
SAP works at the planning level. It knows what needs to be produced, when, and for whom. A MES works at the execution level. It knows what is actually being produced right now, on which machine, by which operator, and with what result. Without a MES, SAP is essentially flying blind when it comes to real-time production data. Without SAP, a MES lacks the business context that gives shop floor data its meaning.
Why would a manufacturer need both a MES and SAP?
Manufacturers need both systems because SAP and a MES solve fundamentally different problems. SAP is built for business process management across the entire organisation. A MES is built for real-time production control and visibility at the machine and operator level. Running both means you can plan effectively and execute reliably, with data flowing between the two.
In practice, manufacturers that rely on SAP alone often struggle with a lack of real-time visibility into what’s happening on the floor. They might know a production order was released, but not whether it’s on track, delayed, or producing defects. A MES fills that gap. It tracks work orders, machine performance, material consumption, and quality data in real time, giving both the shop floor team and management the information they need to act quickly.
How does a manufacturing execution system integrate with SAP?
A MES integrates with SAP by exchanging data through APIs, middleware platforms, or direct database connections. The most common approach is to use an integration layer, such as SAP’s own integration tools or third-party middleware, to map data fields between the two systems and automate the flow of information in both directions.
There are several technical approaches depending on your setup:
- SAP Manufacturing Integration and Intelligence (SAP MII) is SAP’s own middleware layer designed specifically to connect ERP data with shop floor systems.
- REST or SOAP APIs allow modern MES platforms to connect directly to SAP modules through standard web services.
- OPC UA and MQTT are industrial communication standards that some MES platforms use to bridge operational technology (OT) with IT systems, including SAP.
- Third-party integration platforms such as MuleSoft or Azure Integration Services can act as a neutral layer between the MES and SAP.
The right approach depends on your SAP version, the MES you’re using, and how much real-time data exchange you need.
What data is exchanged between a MES and SAP?
The data exchanged between a MES and SAP typically flows in both directions. SAP sends production orders, bills of materials, routing information, and planned schedules to the MES. The MES sends back actual production results, material consumption, machine downtime, quality outcomes, and order completion confirmations.
This bidirectional flow is what makes the integration valuable. SAP can update inventory and financial records automatically based on what the MES reports, while the MES always works from the latest planning data coming from SAP. Common data types that move between the two systems include:
- Work orders and production orders
- Material and component data
- Actual vs. planned production quantities
- Machine availability and downtime events
- Quality inspection results
- Labour and time reporting
What are the biggest challenges of integrating a MES with SAP?
The biggest challenges in MES–SAP integration are data-mapping complexity, system version mismatches, and maintaining synchronisation in real time. SAP is a large, highly customised system in most organisations, which means the integration needs to be tailored carefully to match how your specific SAP instance is configured.
Other common challenges include differences in how the two systems define the same concepts (for example, a “work order” in SAP might not map directly to a “job” in your MES), latency in data synchronisation, and managing change when either system is updated. Organisations that underestimate the complexity of data mapping often run into problems after go-live, when edge cases and exceptions start appearing in production.
Which MES systems are compatible with SAP?
Most modern MES systems are compatible with SAP, either through native connectors, certified integration packages, or open API frameworks. SAP itself offers integration-ready interfaces through SAP MII and SAP Plant Connectivity (SAP PCo), which many MES vendors have built connectors for.
MES platforms built on open standards like OPC UA and REST APIs tend to be more flexible when it comes to SAP integration because they are not locked into a specific connector or SAP version. When evaluating a MES for SAP compatibility, it is worth asking the vendor specifically about their experience with your SAP version (SAP ECC vs. SAP S/4HANA) and whether they have existing customers running that exact combination.
How long does a MES–SAP integration project typically take?
A MES–SAP integration project typically takes between three and twelve months, depending on the scope of the integration, the complexity of your SAP configuration, and how many data points need to be synchronised. Simpler integrations covering basic order management and production confirmations can be completed faster. Full bidirectional integrations with real-time data exchange across multiple production lines take longer.
One factor that significantly affects the timeline is whether you take an incremental approach or try to integrate everything at once. Starting with a single process, such as syncing production orders and completion confirmations, lets you validate the integration before expanding it. This reduces risk and gives your team time to learn how the two systems interact before taking on more complexity.
If you’re looking for a MES that is built with integration in mind, we at Factorise have designed our composable MES specifically to connect with existing IT and OT infrastructure, including SAP, using open standards like OPC UA and MQTT. Our modular approach means you can start with one process and expand step by step, without having to overhaul your entire setup at once. If you want to see how that works in practice, we’re happy to walk you through it.
Frequently Asked Questions
Do we need to upgrade our SAP version before starting a MES integration?
Not necessarily, but your SAP version will significantly influence which integration methods are available to you. SAP ECC and SAP S/4HANA both support MES integration, but they use different interfaces and tools — for example, some newer API-based connectors are only available in S/4HANA. Before committing to a MES platform, confirm with the vendor that they have live integration experience with your exact SAP version, including any custom modules or configurations your organisation uses.
Can we integrate a MES with SAP without involving SAP consultants?
It is possible in some cases, particularly if your SAP instance is relatively standard and the MES vendor provides a pre-built connector. However, most real-world SAP environments are heavily customised, which means someone with SAP configuration knowledge will almost certainly be needed to map data fields correctly and handle exceptions. Involving an SAP consultant early — even in a limited capacity — tends to prevent costly rework after go-live.
What's the best way to get started if we've never done a MES–SAP integration before?
The most practical starting point is to identify one well-defined process to integrate first — syncing production orders from SAP to the MES and sending completion confirmations back is a common and manageable first step. This gives your team hands-on experience with how the two systems interact without overwhelming them with complexity. Once that single integration is stable and validated in a real production environment, you can expand incrementally to cover more data points and processes.
What happens to the integration if we update or upgrade SAP in the future?
SAP upgrades — especially a migration from ECC to S/4HANA — can break existing MES integrations if the underlying APIs or data structures change. This is one of the strongest arguments for using open, standards-based integration approaches rather than tightly coupled custom connectors, as they tend to be more resilient to version changes. It is good practice to include your MES vendor in any SAP upgrade planning early, so they can assess the impact and update connectors before the upgrade goes live rather than scrambling to fix issues afterward.
Is real-time data synchronisation between a MES and SAP always necessary, or is batch synchronisation sometimes enough?
It depends on the process. For production order management and completion confirmations, near-real-time synchronisation is usually important because delays can cause SAP's inventory and scheduling data to fall out of step with what's actually happening on the floor. For less time-sensitive data — such as aggregated shift reports or maintenance logs — batch synchronisation at the end of a shift or day is often perfectly adequate. Designing your integration with this distinction in mind helps reduce system load and simplifies the architecture without sacrificing operational accuracy.
How do we measure whether our MES–SAP integration is actually working correctly after go-live?
The clearest indicators are data consistency checks between the two systems — for example, verifying that material consumption recorded in the MES matches what SAP reflects in inventory, or that production order statuses are in sync. Setting up automated reconciliation reports in the early weeks after go-live is a practical way to catch discrepancies before they compound. Beyond data accuracy, tracking whether your team is still relying on manual workarounds (spreadsheets, phone calls, manual data entry) is a good real-world indicator of whether the integration is delivering the visibility it was designed to provide.
Can a MES–SAP integration support multi-site manufacturing environments?
Yes, and multi-site environments are actually one of the strongest use cases for this kind of integration, since they create the most complexity in keeping production data aligned with business-level planning. The key consideration is whether your MES architecture supports multi-site deployments — some platforms use a centralised model while others deploy site-level instances that feed into a central data layer. Whichever model you use, the SAP integration layer needs to correctly route data to and from the right plant codes and organisational units within SAP to avoid cross-site data errors.
