Define the business event
Sending production data to SAP is not a single operation. Production confirmations, material consumption, quality results and maintenance notifications carry different business rules. Establish which event will change which SAP object. Map line, plant, production order, material and unit of measure to their source fields. A PLC counter cannot reliably become an ERP transaction until its operational context is defined. Decide who owns corrections when the machine data is technically valid but the business context is wrong.
Validate the interface with the SAP team
OPC Router supports SAP connections using interfaces such as RFC, BAPI and IDoc. Validate the SAP version, deployment model, permitted interface and licence scope for the actual project. Do not transfer an assumption about S/4HANA on-premise to Public Cloud. Work with SAP Basis and application specialists to define the function, technical user, network path and development-to-test-to-production promotion. Record destination transaction limits and any maintenance windows. Confirm required runtime components against the manufacturer's documentation.
Prevent duplicate business postings
If the network drops before a response arrives, SAP may already have completed the transaction. Resending the message can create another business posting. Associate the source event identifier, business key and returned SAP document. Consider querying destination state before retrying or enforcing uniqueness at the receiving application. A technical acknowledgement is not necessarily confirmation that the business transaction has completed; monitor them as separate states. Failed business validations need a correction workflow, not an endless retry loop.
Test with the business owner
Write down eight decisions: business event, interface, field mapping, access, trigger, retry policy, error ownership and acceptance criteria. Include unknown materials, closed orders, unit mismatches and permission denials in the test set. Check the processing order of queued messages after connectivity returns. Agree when the previous manual workflow stops and how it resumes during rollback. Keep a reconciliation report that connects source events with destination documents so both engineering and operations can review the same evidence.
Technical references
Check manufacturer documentation for product capabilities. Project steps and examples were prepared by OPC Turkey.