MES / OEESAP S/4HANARuns on-prem

SAP Digital Manufacturing and SAP S/4HANA: OEE and shop floor execution

SAP Digital Manufacturing is SAP's cloud MES and is integrated natively with S/4HANA, so production orders flow down to the shop floor and confirmations flow back. Machine data arrives over OPC-UA, and a documented injection moulding project used Euromap 77 to show real-time and historical OEE. It works with on-prem S/4HANA, but the MES itself is a cloud service.

How SAP Digital Manufacturing connects to SAP S/4HANA

First-party S/4HANA integration

Digital Manufacturing is an SAP product and ships with a standard integration to S/4HANA. Released production orders, routings and BOM data are replicated to the MES, and operation confirmations, goods movements and scrap are posted back to the ERP. Exact connectivity (Cloud Connector, communication arrangements) depends on your S/4HANA release and deployment, so confirm against SAP's current integration guide.

OPC-UA machine connectivity

Machines are read through OPC-UA. In the documented injection moulding project, machines exposed data via the Euromap 77 companion specification, which gives a standard set of signals (state, cycle counts, alarms) that feed real-time and historical OEE views. Older machines without OPC-UA usually need a gateway or a PLC-side mapping.

What data moves

FromToDataWhen
S/4HANADigital ManufacturingReleased production orders, routings, BOMs, materialsOrder release or scheduled replication
Machine (OPC-UA)Digital ManufacturingMachine state, cycle counts, alarms, good and reject countsContinuous subscription or polling
Digital ManufacturingS/4HANAOperation confirmations, yield, scrap, component consumptionOperator completes or reports an operation
Digital ManufacturingDashboardsAvailability, performance and quality OEE by machine and shiftCalculated continuously from machine signals

Setting it up

  1. 1Confirm the deployment modelDigital Manufacturing is cloud-delivered. Decide how it will reach on-prem S/4HANA and plant networks, and have security review the outbound path before any design work.
  2. 2Define plants and work centersAlign plant, work center and resource definitions between S/4HANA and the MES so orders land on the right resources.
  3. 3Set up the ERP integrationConfigure the communication between the MES and S/4HANA, then test order download and a single confirmation round trip.
  4. 4Connect machinesInstall the edge or gateway component, point it at the OPC-UA server on each machine and map the signals (running, stopped, cycle, reject).
  5. 5Define OEE rulesAgree on planned downtime, ideal cycle time and what counts as a reject, since OEE is only as meaningful as these definitions.
  6. 6Pilot on one lineRun one line for several weeks, compare MES counts with ERP confirmations, and fix mapping gaps before rolling out.

What usually breaks

  • !Ideal cycle time in the MES differs from the routing standard in S/4HANA, so OEE performance looks wrong without anyone noticing.
  • !Machines that expose OPC-UA but not Euromap 77 need custom signal mapping, which is easy to underestimate.
  • !Confirmation posting failures (locked order, missing batch, closed period) leave the MES and ERP out of step until someone reconciles them.
  • !Network segmentation between the plant and the cloud service blocks data silently if firewall rules are incomplete.
  • !Unit of measure and scrap reason codes differ between systems, producing rejected confirmations.

A private AI layer across both systems

Confirmation exception triage

A private assistant reads failed confirmations from the MES and the S/4HANA error messages, groups them by cause and drafts the fix for a planner to approve.

Plain-language OEE questions

Ask why line 3 lost OEE last week and get an answer that combines machine downtime reasons with the production orders running at the time, with the queries shown.

MES versus ERP reconciliation

Compare good counts in the MES to confirmed yield in S/4HANA each shift and list mismatches by order, so variances are caught before month end.

Try it here, free

Injection Moulding Quality Control Checklist

Open full tool

A printable first piece, in-process and final inspection checklist for injection molded parts with sampling and record-keeping guidance.

When something else fits better

  • If you only need machine monitoring and OEE without execution, a lighter machine-data platform may be enough.
  • If S/4HANA is on-prem and the plant cannot use a cloud MES, consider an on-prem MES from a partner that integrates through standard SAP interfaces.

Frequently asked questions

Does SAP Digital Manufacturing work with on-prem S/4HANA?

SAP positions it as integrated with S/4HANA, but the MES is a cloud service, so on-prem systems need a secure connection to it. Check SAP's current integration documentation for your S/4HANA release and the supported connectivity options before committing.

How does machine data reach the MES?

Through OPC-UA. In the documented injection moulding project the machines used the Euromap 77 standard. Machines without OPC-UA typically need a gateway or PLC-side mapping to expose usable signals.

Can an AI assistant sit on top of this?

Yes, as a separate read-only layer that queries MES and ERP data and runs on your own infrastructure. It explains variances and drafts corrections, while any write-back to S/4HANA stays behind human approval.

Pairing documented at www.adesso.de/en/adesso-branch-solutions/manufacturing-industry/referenzen/durab . SAP Digital Manufacturing is a product of SAP; Netray is independent and not affiliated with either vendor.

Keep exploring

Free tools

ERP fixes and how-tos

Runs with your ERP

Guides

AI on your ERP

Comparisons

Software