Skip to Content
Technical Articles
Author's profile photo Gaurav Karkara

S/4HANA Cloud Output Management – Configuration for Channel EDI

In this blog, we will discuss about the Channel ‘EDI’ which is one of the options available in S/4HANA Output Management. We will assume a Buyer-Supplier scenario where sales document needs to go to a Business Partner system and see what all steps are required to achieve this integration.

Channels in S/4HANA Output Management:

S/4HANA Output Management, which is the only option for Output Management in S/4HANA Cloud, we have below 5 options when it comes to configuring the Output Channels:

Channels ‘IDOC’ & ‘XML’ are deprecated & shouldn’t be used for system integration. These options are there just for legacy reasons.

Channel PRINT:  Cloud enabled using Print Queues / Cloud Print Manager

Users can either print via web browser for foreground printing or can enable Cloud Print Manager for background printing.

Foreground printing is as simple as triggering the printing from S/4HANA Cloud system manually.

Background printing can be achieved by using CPM – Cloud Print Manager.

Please refer to links at the bottom for details.

Channel EMAIL: Output channel EMAIL is used to send output documents to business partners through email. Below blog can be referred if you seek more details regarding channel EMAIL.

Please refer to links at the bottom for details:

Channel EDI: We are most interested in this Channel as purpose of this blog.

EDI is Electronic Data Interchange which may include interchange via IDoc, XML, SOA etc.

S/4HANA Cloud system supports sending output of business documents to external systems (SAP or non-SAP) through EDI. External system may import these EDI business documents as IDOC, XML or any other document format depending on their requirement.

For example, if buyer system is SAP On-Premise system & supplier system is a S/4HANA Cloud system then S/4HANA Cloud system will be sending Order Confirmation, Delivery & Billing documents to OP system. S/4HANA Cloud system will output the business documents as EDI & OP system can import these documents as IDOC. Similarly, if non-SAP systems are used, they can import & convert business documents to their required format.

We will be discussing steps to be done to enable EDI output of a Sales Document I.e. Order Confirmation output. We are only covering Output management related settings here. For detailed overview of all set-up instructions, visit scope item 2EL.

To configure the EDI integration, make sure you have following roles assigned to your user:

  • Configuration Expert – Business Network Integration (SAP_BR_CONF_EXPERT_BUS_NET_INT)
  • Configuration Expert – Business Process Configuration (SAP_BR_BPC_EXPERT)


Output Parameter Determination:

While keeping most the settings for ‘Sales Document’ as they are delivered out of the box, we will need to add a new entry for Determination step ‘Channel’.

For Output type ‘ORDER_CONFRIMATION’ & ‘ORDER_CONFIRMATION_CHANGE’, make an entry for channel as ‘EDI’. Maintaining ‘Recipient’ as optional but its recommended to avoid unnecessary outbound traffic.

Make sure that entries for other determination steps are not restricted based on Channel. If yes, please add another entry for ‘EDI’. In my system, for determination step ‘Form template’, Channel column for Sales document output types is blank means these entries will be considered for all channels. If we had Channel column maintained, we need to be sure that it contains an entry for EDI as well.

Assign Recipients to Users:

Maintain below entries for your user so that you can monitor messages related to Sales Order communication. For Invoice & delivery related monitoring, corresponding namespace & Recipient would need to be added.

Namespace Recipient Name Message Type Overview Technical User
/SDEDI EDI_SD_ORDR_RECIPIENT Application Error or Technical Error Set Flag Set Flag
/SDEDI EDI_SD_CONF_RECIPIENT Application Error or Technical Error Set Flag Set Flag

Communication Arrangement:

  1. Create a communication user by providing user name, Description & Password. (App – Maintain Communication Users)
  2. Define a Communication System (App – Communication Systems)

2.1 Provide System ID & System name as your preferred name for EDI integration supplier.

2.2 Under Technical Data – General: Provide details about your buyer system i.e. external system to which business document will be sent.

Provide all relevant details here for external system.

2.3 Provide users for Inbound & Outbound communication.

Inbound Communication: You should maintain User ID & password that we created in Step 1. This will be used for any inbound communication from external/buyer system. Same user should be maintained as Outbound user in external/buyer system.

Outbound Communication: This is the User ID/Password which will be used to login into external/buyer system. So, these details will be provided by external/buyer system.

User Authentication method ‘User Name and Password’ for these settings.

2.4 Under Business Partner, Maintain Supplier Business Partner ID pertaining to this communication system. For example, If a communication system is relevant for a set of Business partners, maintain those BPs here in communication system.

  1. Maintain Communication Arrangement (App – Communication Arrangements)


Create a communication arrangement for scenario SAP_COM_0223 (Sales with Buyers Integration), Communication system as created in Step 2. Maintain path for following outbound services:

Your set-up for EDI communication is complete. Now whenever a Sales Document is created/saved, channel EDI will also be added in output log & it can be monitoring using App – Message dashboard under ‘Message Monitoring’.

In conclusion, Above are the activities that you need to execute in S/4HANA Cloud system to successfully work with EDI Channel. SOAP services will change based on type of document (Delivery, Invoice).

Below links can be referred to in case you need more details regarding topic we discussed here:

Cloud Print Manager

Customize Email

Integration of SAP S/4HANA Sales with Procurement (‏2EL‏)

Output Management(1LQ)

Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Adrien Monges
      Adrien Monges

      Hello Gaurav,

      Thank you for this interesting article. I tried to follow it but i'm blocked at the namespace creation.

      No way to create the SDEDI namespace in customizing, always same message : "You have only display authorization for namespace /SDEDI" when i'm on transaction /o/aif/cust.

      I verified that I have change  authorization on object /AIF/CUST on all namespaces, it is ok...

      Sorry if i'm not on the good conversation, but I do not find any other discussion on the subject.

      Thank you,


      Author's profile photo Gaurav Karkara
      Gaurav Karkara
      Blog Post Author

      Hi Adrien,


      What i understand is that you are facing issue while maintaining entries for your user in app 'Assign Recipients to Users'. The message you are facing is definitely authorization related. Can you check guide 2EL (link in blog) to see what roles are required and if you have those roles?




      Author's profile photo Adrien Monges
      Adrien Monges

      Hi Gaurav,


      Thank you for your answer. I now manage to advance in the blog.

      But I have a fundamental question : Is it possible to link an S4H 1809 On-premise system to an external non-SAP system via EDI channel ?

      If yes, is there any SAP-note linked to this way of communicating ?


      Thank you !



      Author's profile photo Gaurav Karkara
      Gaurav Karkara
      Blog Post Author

      Hi Adrien,

      If you are talking about above steps, they are pertaining to S/4HANA Cloud only.

      For connecting OP system to non-SAP systems, you can use IDOCs, traditional way.


      Gaurav K

      Author's profile photo Adrien Monges
      Adrien Monges

      Hello Gaurav,


      Thank you Again for your answer.

      Is there some SAP notes that deals with this "restriction" ?

      A SAP note that mentions something like "EDI channel is only available on S/4HANA cloud" ?


      Thank you,



      Author's profile photo Jay Malla
      Jay Malla

      Hi Gaurav,

      Nice blog!



      Author's profile photo Jay Malla
      Jay Malla

      Hi Gaurav,

      So for S/4 HANA cloud, is the better approach to use SOAP inbound and outbound async messages instead of IDocs?  All of the videos from SAP seem to indicate going the SOAP route.  However the IDoc route is so robust and has been time tested over so many years and there are so many excellent IDoc tcode programs.

      I used the integration advisor to propose mapping from ANSI X12 order to SAP Soap order - but did not get any proposed mapping but when I do ANSI X12 order to SAP Orders IDoc, I get a lot of proposed mapping.

      Any thoughts on this?  For the S/4 HANA Cloud, should we just focus on SOAP and not use IDocs at all?



      Author's profile photo Dilip Mehra
      Dilip Mehra

      Hi Gaurav,


      Thanks for the blog .


      I am trying to send Purchase order data from S4 and used E2J document .Everything is done as per the document and your blog and I can see message in the message dashboard as well but there it is failing. Any idea on this ?

      Author's profile photo Vinit Gangwal
      Vinit Gangwal

      Hi Gaurav Karkara - Thanks so much for sharing this blog. I have one small query - how do I know which communication arrangement or communication systems are involved for lets say order confirmation outbound EDI (scenario - SAP_COM_0223) ?

      Thank you in advance 🙂