SAP production integration: eight decisions before connecting
Design the interface, business transaction, access rights and retry behaviour together for an SAP ECC or S/4HANA project.
Read the guideSolutions
SAP ERP integration
Turn production events into SAP business records.
Automation, SAP Basis and production planning teams
Transfer production confirmations, material consumption and quality results in the context of the same order. Reduce manual entry while associating the SAP response document with its source event.
SourcePLC / OPC UA
OPC RouterConnect · Transform · TransferDestinationSAP ECC / S/4HANA
Typical data points
- Production order number and operation
- Good and scrap quantity
- Run time and work centre
- Material consumption
- Quality result
How the flow works
- Connect
The OPC UA Client reads the machine or PLC event, which is associated with its order context.
- Transform
Fields are mapped to the format the SAP interface expects; units, plant and work-centre codes are validated.
- Transfer
The SAP plug-in calls the chosen RFC, BAPI or IDoc interface; the response document is stored against the source event.
Decisions before connecting
- 01SAP version and deployment model
- 02RFC/BAPI/IDoc or approved API
- 03Plant, material and order mapping
- 04Duplicate and business-error handling
Pilot acceptance criterion
Reconcile source events with SAP records for one production order; verify that reconnecting does not post the same transaction twice.
Connectors used in this scenario
Connector availability, version compatibility and licence scope are verified for each project.
Implementation guide
Frequently asked questions
Which interface should be used: BAPI or IDoc?
The choice depends on the SAP version, on whether the transaction needs a synchronous result and on the interface your SAP team approves. A BAPI usually returns the result of the call immediately; an IDoc is asynchronous and tracked through status records. The decision is made in the project together with your SAP team. See the BAPI/RFC and IDoc glossary entries.
Can the same production confirmation be posted twice if the connection drops?
This risk is managed by design: a unique key for the event and duplicate-processing control are put in place and verified in acceptance by cutting and restoring the connection. See the idempotency entry for the concept.
Your next step
Let’s talk about the systems you need to connect.
Share your source, destination and intended outcome. We’ll help define the project scope.