Configure OPC UA server on the machine or PLC; deploy an OPC UA to MQTT bridge (e.g., using Eclipse Milo or a purpose-built IoT gateway) that publishes tag values (cycle count, yield, timestamps) to an MQTT broker.
In SAP Integration Suite (Cloud Integration), create an integration flow (iFlow) with an MQTT sender adapter pointing to the broker, topic, and QoS level; configure the adapter's client credentials for broker authentication.
Add a message mapping step to transform the MQTT JSON payload into the SAP production order confirmation OData request format (matching API_PROD_ORDER_CONFIRMATION_2_SRV field names).
Add an OData receiver adapter configured with the S/4HANA tenant URL and service path /sap/opu/odata/sap/API_PROD_ORDER_CONFIRMATION_2_SRV/A_ProdOrderConfirmation; set authentication via the BTP destination service.
Configure error handling in the iFlow: use a dead-letter queue or SAP Integration Suite's retry (JMS adapter) for transient S/4HANA API errors; log the ManufacturingOrder number and confirmation count for audit.
Test end-to-end with a simulated MQTT message; verify the production order confirmation document appears in SAP transaction CO14 (Display Production Order Confirmation).
Known gotchas
OPC UA node IDs are vendor-specific; the bridge must be configured with the exact node ID namespace URI and identifier for each data tag — using generic node browsing at runtime adds latency and is unreliable for production use.
SAP Integration Suite's MQTT adapter does not support MQTT v5 features (user properties, topic aliases); if the OPC UA bridge publishes MQTT v5 packets, configure it to downgrade to MQTT v3.1.1 for compatibility.
Production confirmations posted via API are final by default and cannot be easily reversed; include a validation step in the iFlow to check that the confirmed yield does not exceed the planned order quantity before posting to S/4HANA.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp