A quality inspection completion event is triggered in SAP S/4HANA at Global Manufacturing AG's Frankfurt facility. S/4HANA sends an HTTP message to EIC's integration endpoint - an HTTPS address on Global Manufacturing AG's private Frankfurt network, exposed by the Kubernetes LoadBalancer Service provisioned as part of the EIC deployment. The LoadBalancer Service distributes the incoming request to one of the three available Worker Pod replicas.
The Worker Pod's Apache Camel runtime receives the message and begins executing the deployed iFlow. The iFlow maps the S/4HANA quality notification structure to the QMS's expected REST payload format, applies routing logic to select the correct QMS endpoint based on the inspection type, and delivers the transformed message to the QMS via an outbound HTTP call - all within Global Manufacturing AG's private Frankfurt data center network. The QMS acknowledges receipt, and the Worker records a successful processing outcome.
The Worker writes a Message Processing Log to the external PostgreSQL database: the message ID, the iFlow name and version, the processing start and end timestamp, the status (Success), and the step-level log. Within seconds, the MPL metadata becomes available to the SAP Business AI Platform control plane via the Cloud Connector, and an operations engineer monitoring the SAP Integration Suite Cockpit. - filtered to the Frankfurt EIC instance - sees the processing entry appear in the Message Processing Monitor. The actual quality inspection data in the message never left Global Manufacturing AG's network.