In this blog post we will discuss about Integration between S/4 HANA Cloud to external system via Integration Suite using Output Type as the trigger from S/4 HANA Side. This can be achieved provided there is a standard Outbound service available within any standard SAP Communication scenario. This pattern can also be considered as a good alternative for EDA when there are no standard events available for the business object and in those cases, it can be used instead of going to custom events. The outbound service will use SOAP technology so every time you trigger you will get a SOAP payload.
Advantage – It gives you the full data every time so no need for additional OData calls to S/4 HANA to fetch additional details.
Disadvantage – You do not get delta changes, but you will get the full data every time you trigger. So you can control it from middleware mapping according to your business need.
To demonstrate this use-case today I am using S/4 HANA Public Cloud. I will write a separate blog for S/4 HANA Private Cloud. To configure the triggering using Output Type from S/4 HANA Public cloud we will need to use five standard applications in S/4 HANA.
Maintain Communication UsersCommunication SystemsCommunication ArrangementsOutput Parameter DeterminationAssign Recipients to Users (Optional for monitoring purpose)
Step 1 – Create a basic Integration flow with SOAP Sender adapter and deploy it.
In this blog we are only focusing on the part of integration from S/4 HANA Cloud to Integration Suite. The Output Type triggering will be done using a SOAP Outbound service which will eventually send an XML payload. Based on the technology used(API/SFTP) on target side it can be converted or sent as it is after evaluating the capability of the target system to interpret an XML file.
Copy the deployed URL and SOAP Address part to be used later.
Step 2 – Activating Communication
We will be using standard communication scenario SAP_COM_0223 to demonstrate the use case here. However, there are other communication scenarios too which has outbound SOAP services available. SAP_COM_0223 has three outbound services, here we will trigger the Outbound delivery.
I have used SAP Business Accelerator Hub to identify my required API for my requirement. API – https://api.sap.com/api/sap-s4-CE_CO_EDI_DELIVERY_REQUEST_V2_OUT-v2/overview
We need to create a communication arrangement for this standard communication scenario. How to create communication arrangements and its related communication system and communication user that I have covered in one of my previous blogs – API Consumption – S/4 HANA Cloud,Public Edition a… – SAP Community . Also, there are multiple other blogs available in SAP community on this topic.
The hierarchy is – Communication User -> Communication System -> Communication Arrangement
*Additional step for this scenario you have to add a Outbound User in communication system as in this case our communication direction is S/4 HANA -> External(outgoing)
Also “Inbound only“ checkbox should be unchecked in this case.
Most important you have to add the host of your Integration Suite in the field “Host Name” as your S/4 HANA system is communicating with Integration Suite via this communication system.
Once we have created the arrangement, we need to configure the Integration flow URL components in the two fields highlighted in the below screenshot
In the “Path” provide the portion of your deployed URL which is highlighted in the below screenshot
The “Service URL” part is non editable and it is supposed to populated automatically from your assigned communication system when you configure the Host Name in your communication system as shown above
Step 3 – Configuring Output Parameter
Configure the Output Type in the app “Output Parameter Determination”
Open the app –
Configure the standard output type “DELIVERY_NOTE” for Determination Step = “Output Type” for “EDI” .
Step 4 – Maintain BP in Communication System
Maintain the business partners in communication system. This is an important step as without this your Output does not gets triggered. The BP for which you are intending to create your Sales Order, and corresponding Outbound delivery needs to be maintained in this section.
Go to “Communication System” app, open the communication system that you are using for the particular communication arrangement and add the BPs under this tab.
Test your Interface using an existing Outbound Delivery or creating a new one.
Here I have triggered output manually but automatic triggering to be configured with appropriate conditions from “Output Parameter Determination”
Go to app – “Change Outbound Delivery”/VL02N and open the delivery number for which you want to trigger the output type.
Go to path –
Menu -> Extras -> Delivery Output -> Output Control
Click on “Add Output” and then click on “Send Output”
Once output shows as “Completed” you can check the message in your Iflow if it has reached. You can check your Iflow monitoring for message received –
So once you have the XML payload in your Integration flow, you can do necessary conversion/mapping or send as it is to target using API or SFTP whichever capability your target system supports.
**Additional tips – For monitoring you can create a recipient for this interface from the application – “Assign Recipients to Users” with names space and recipient name as below –
You can monitor SOAP outbound messages from the applications like –
Message Monitoring for Integration Experts
Message Monitoring
In this blog post we will discuss about Integration between S/4 HANA Cloud to external system via Integration Suite using Output Type as the trigger from S/4 HANA Side. This can be achieved provided there is a standard Outbound service available within any standard SAP Communication scenario. This pattern can also be considered as a good alternative for EDA when there are no standard events available for the business object and in those cases, it can be used instead of going to custom events. The outbound service will use SOAP technology so every time you trigger you will get a SOAP payload.Advantage – It gives you the full data every time so no need for additional OData calls to S/4 HANA to fetch additional details.Disadvantage – You do not get delta changes, but you will get the full data every time you trigger. So you can control it from middleware mapping according to your business need.To demonstrate this use-case today I am using S/4 HANA Public Cloud. I will write a separate blog for S/4 HANA Private Cloud. To configure the triggering using Output Type from S/4 HANA Public cloud we will need to use five standard applications in S/4 HANA.Maintain Communication UsersCommunication SystemsCommunication ArrangementsOutput Parameter DeterminationAssign Recipients to Users (Optional for monitoring purpose)Step 1 – Create a basic Integration flow with SOAP Sender adapter and deploy it.In this blog we are only focusing on the part of integration from S/4 HANA Cloud to Integration Suite. The Output Type triggering will be done using a SOAP Outbound service which will eventually send an XML payload. Based on the technology used(API/SFTP) on target side it can be converted or sent as it is after evaluating the capability of the target system to interpret an XML file. Copy the deployed URL and SOAP Address part to be used later.Step 2 – Activating CommunicationWe will be using standard communication scenario SAP_COM_0223 to demonstrate the use case here. However, there are other communication scenarios too which has outbound SOAP services available. SAP_COM_0223 has three outbound services, here we will trigger the Outbound delivery.I have used SAP Business Accelerator Hub to identify my required API for my requirement. API – https://api.sap.com/api/sap-s4-CE_CO_EDI_DELIVERY_REQUEST_V2_OUT-v2/overviewWe need to create a communication arrangement for this standard communication scenario. How to create communication arrangements and its related communication system and communication user that I have covered in one of my previous blogs – API Consumption – S/4 HANA Cloud,Public Edition a… – SAP Community . Also, there are multiple other blogs available in SAP community on this topic.The hierarchy is – Communication User -> Communication System -> Communication Arrangement*Additional step for this scenario you have to add a Outbound User in communication system as in this case our communication direction is S/4 HANA -> External(outgoing)Also “Inbound only” checkbox should be unchecked in this case.Most important you have to add the host of your Integration Suite in the field “Host Name” as your S/4 HANA system is communicating with Integration Suite via this communication system.Once we have created the arrangement, we need to configure the Integration flow URL components in the two fields highlighted in the below screenshotIn the “Path” provide the portion of your deployed URL which is highlighted in the below screenshotThe “Service URL” part is non editable and it is supposed to populated automatically from your assigned communication system when you configure the Host Name in your communication system as shown aboveStep 3 – Configuring Output ParameterConfigure the Output Type in the app “Output Parameter Determination”Open the app –Configure the standard output type “DELIVERY_NOTE” for Determination Step = “Output Type” for “EDI” .Step 4 – Maintain BP in Communication SystemMaintain the business partners in communication system. This is an important step as without this your Output does not gets triggered. The BP for which you are intending to create your Sales Order, and corresponding Outbound delivery needs to be maintained in this section.Go to “Communication System” app, open the communication system that you are using for the particular communication arrangement and add the BPs under this tab.Test your Interface using an existing Outbound Delivery or creating a new one.Here I have triggered output manually but automatic triggering to be configured with appropriate conditions from “Output Parameter Determination”Go to app – “Change Outbound Delivery”/VL02N and open the delivery number for which you want to trigger the output type.Go to path –Menu -> Extras -> Delivery Output -> Output ControlClick on “Add Output” and then click on “Send Output”Once output shows as “Completed” you can check the message in your Iflow if it has reached. You can check your Iflow monitoring for message received –So once you have the XML payload in your Integration flow, you can do necessary conversion/mapping or send as it is to target using API or SFTP whichever capability your target system supports.**Additional tips – For monitoring you can create a recipient for this interface from the application – “Assign Recipients to Users” with names space and recipient name as below -You can monitor SOAP outbound messages from the applications like –Message Monitoring for Integration ExpertsMessage Monitoring Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
