Skip to Content

Electronic data interchange (EDI) is a concept of interchanging business-related documents electronically. As EDI has a history of more than 30 years many de facto standards have established e.g. X12, EDIFACT and ODETTE based on specific industry needs. Due to the fact that miscellaneous companies rely on communication through EDI SAP is glad to offer two different ways for customers to benefit from APIs in SAP S/4HANA Cloud. In dedicated projects customer can implement them to address their specific EDI requirements.

EDI Integration based on SAP S/4HANA Cloud buyer-side integration with SAP Ariba solutions

Right now, SAP S/4HANA Cloud is integrated to the Ariba Network on the buyer side, with procurement functions. The respective integration scenarios can be found on the SAP Best Practices Explorer. The Integration setup and the currently supported X12 and EDIFACT standards including the architecture is visualized in this picture:



EDI integration based on SAP S/4HANA Cloud SOAP APIs

With SAP S/4HANA Cloud, more modern, extensible and structurally simplified SOAP APIs are being provided and maintained by SAP on the SAP API Business Hub. Furthermore, SAP provides a new crowd-based machine learning tool called integration content advisor (ICA) running on the SAP Cloud Platform Integration which now supports creating and maintaining B2B integration content much faster and more efficiently then ever before. For more details on the ICA visit this blog:

The following illustration explains the described the EDI integration based on SAP S/4HANA Cloud SOAP APIs:


Check out the newly released scope items for customers using EDI with SAP S/4HANA Cloud, 2EJ for procurement , and 2EL for sales APIs .

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Mark Nolff

    Are the any plans to offer REST/JSON based equivalents of the SOAP API’s? I only ask because it seems that many organizations are moving away from SOAP to REST for API architectures. If a more structured API with a tighter contract is required in these use cases I could understand why SOAP might be a better fit.

    1. Marcel Wolf Post author

      Hi Mark,

      as in RESTful APIs like OData the client has to initiate the data push from the SAP S/4HANA Cloud system e.g. by subscribing to changes. Furthermore, SOAP is more common when it comes to data exchange in stateful & heavy weight environments like A2A(Application to Application) and B2B(Business to Business). Based on this facts we focus on asynchronous messaging via SOAP APIs in EDI scenarios.



  2. Hermann Ebert

    Hi Marcel,

    Thanks for the update. Do you know if it is planned to provide the EDI interface in the S/4 OnPremise Edition as well?

    In the 2nd picture it is mentioned that the

    Customer owns and manages their own mappings built in SAP Cloud Platform integration (or other platform)

    Could I interpret the “or other platform” in a way that customers are able to use their own EDI systems?

    Thanks in advance & kind regards,

    1. Marcel Wolf Post author

      Hello Hermann,

      please see my answers below:

      1. yes it is planned to delivery the APIs for SAP S/4HANA on-premise as well with later releases.
      2. as the EDI Integration Strategy for SAP S/4HANA Cloud is to use public released APIs you can use any system to create the mappings if this tool is capable to deal with SOAP APIs.

      Kind regards,



Leave a Reply