Digital transformation for major food industry players often hinges on the seamless replacement of legacy ERPs with modern solutions like SAP S/4HANA Cloud Public Edition. A key challenge in this transition is maintaining robust connectivity with established EDI (Electronic Data Interchange) platforms, such as EDITEL’s eXite® network, while adhering to the Clean Core principles of the cloud.

Architecture: The connectivity framework

The SAP Public Cloud environment operates on a standardized API-first architecture. For high-volume business document exchange—such as orders, shipping notifications, and invoices—the SOAP (Simple Object Access Protocol) web service remains the industry standard for reliability and transactional integrity.

In a recent implementation for a prominent Hungarian food producer, the integration was built on a secure, two-way SOAP communication channel. The configuration required a synchronized exchange of technical handshake parameters:

• SOAP Endpoint URLs: Specific paths defined within the SAP Communication Arrangements.
• TLS/SSL Certificates: Ensuring encrypted data transmission and mutual authentication.
• Technical Credentials: Secure access management for API-level interaction between the ERP and the EDI gateway (Cleo Harmony).

The challenge of message routing: The SBDH envelope

A specific technical hurdle in such cloud migrations is the discrepancy between the native XML output of the ERP and the routing requirements of EDI service providers. The eXite® platform requires a Standard Business Document Header (SBDH)—a specialized metadata envelope—to trigger automated workflows like conversion, validation, and archiving.

Since SAP Public Cloud does not natively generate this specific SBDH wrapper, a custom mediation logic was implemented to handle the “enveloping” and “de-enveloping” of messages.

1. Outbound Flow: From ERP to EDI Gateway

When the company’s SAP system issues an invoice (INVOIC) or despatch advice (DESADV):

• Native XML Export: SAP generates a standardized, clean XML file.
• SBDH Enveloping: Upon reaching the integration layer, the native XML is wrapped into an SBDH envelope. This header contains the routing logic (sender/receiver IDs, document types) necessary for the EDI platform to identify the message.
• Workflow Execution: The eXite® system receives the enveloped message and can immediately proceed with conversion in SubmIT and delivery to the final partner.

2. Inbound Flow: From EDI Gateway to ERP

For incoming documents, such as supplier Purchase Order (ORDERS):

• SBDH: The EDI system delivers the XML messages still wrapped in their technical SBDH wrappers.
• De-Enveloping: To ensure the ERP can process the data, the integration layer strips away the SBDH envelope, leaving only the native XML content.
• ERP Processing: The clean XML is pushed to the SAP SOAP endpoint, where it is automatically validated and posted.

Conclusion

This integration strategy allows the organization to leverage the agility of the SAP Public Cloud without sacrificing the complex routing and compliance features of the EDITEL eXite® network. By implementing a dynamic SBDH handling mechanism, the company ensures that its technical architecture remains clean while its business communication remains globally compatible.