SAP Cloud Platform Integration (CPI) Part 22 – Understanding SOAMANAGER configuration for Outbound SOAP Webservices to CPI

1 year ago 33

This is the 22^nd post in my blog series on “SAP CPI – Cloud Platform Integration for beginners”. In this post we will see the steps involved in configuring SOAP webservices in SOAMANAGER transaction for outbound connections to CPI.

Overview of this blog series:

1. SAP CPI Introduction
2. SAP BTP tools and features overview (BTP, Global Account, Sub-Account, Entitlements, Connectivity, Security)
3. SAP CPI Web IDE overview
4. Registering a trial account and enrolling to SAP CPI service
5. Deep dive into Cloud Integration features with real world scenario example
6. Use cases of palette functions
7. Adapter configurations
8. Using Cloud connector for connecting to backend SAP systems
9. Overview on API Management & Open Connectors
10. Integration using Open Connectors with real world example

In short, below is the content we will elaborate in this tutorial:

1. SOAMANAGER setup for Outbound SOAP API
– WSDL generation with CI endpoint
– Upload it in Provider System
– Create Local Integration Scenario Configuration
– Set Port to default in Webservice Configuration
– Logical determination of receiver using Service Group
– Testing the SOAP Service

Before we proceed with our tutorial, we would like to give you an opportunity to join our ZAPYard’s learning community where we have more than 32 groups and more than 1000 real SAP Consultants interacting with each other daily. Only SAP topics and not BS. Else, they will be banned from the community without warning. 👇👇👇👇

If you want to be part of ZAPYard’s Discussion Community, please feel free to check the below Link. We Ask, Answer, Help and Learn Together. There are more than 32 groups from different topics like RAP, BPT, Fiori, iRPA, CAI, CPI, PI/PO, ABAP on HANA, SAPUI5, SAP Build, SAP Adobe Forms, ChatBots, SAC etc. Join any group of your interest and interact with our Community.

Join ZAPYard’s WhatsApp Community

SOAMANAGER setup for Outbound SOAP API

For Outbound SOAP Webservices, depending upon the API documentation, we need to do the configuration in SOAMANAGER. In this example, I am going to use the standard outbound delivery request SOAP API.

SOAP Webservice – CO_EDI_DELIVERY_REQUEST_OUT

API Documentation URL – https://help.sap.com/docs/SAP_S4HANA_ON-PREMISE/2f36056ae9a044bba55bcbad204b7bc5/6d877c77526c43b9bc673e923a5e9a34.html

In this URL, we can see the steps to be done in SOAMANAGER.

Let’s get started.

WSDL generation with CI endpoint

Before we start with the configuration, we need to set up the sample IFlow in CI and get the SOAP URL of it. We need to configure this in the WSDL.

Create an IFlow -> Choose SOAP as sender adapter with SOAP RM as message protocol -> Save and Deploy.

Now get the WSDL from S4.

In SPROXY,

Export the WSDL.

In the WSDL, add the wsdl:service node, where we will be mentioning the CPI IFlow URL which we copied earlier.

Upload it in Provider System

SOAMANAGER -> Technical Administration -> Provider System -> WSDL assignments -> click on Upload.

Provider system will be created by BASIS team.

Profile name is assigned to this provider system. This profile will be created in Technical Administration
-> Profiles

Under the WSDL Access tab, we would be providing one User for accessing the WSDL.

Under WSDL assignments tab, the WSDL is uploaded.

Create Local Integration Scenario Configuration

Next is to create a reference to the provider system. So, Go to Service Administration -> Local Integration Scenario Configuration.

Click on Create. Provide a valid name and description.

Click on Next.

You will be asked to select the service definition name. As this interface is through service group, we can neglect this section and click on NEXT.

To know if its service definition or service group. Typically, outbound soap service will be of service group. To confirm it, get the SAP official document of that soap api.

Service group – EDI_DELIVERYREQUEST_OUT_GRP This service group name is provided in the SAP documentation.

Click on Add.

Once done, click on OK. The entries will be showing. To assign a reference to it, click on Assign IBC Reference.

Click on Search which will list all the provider systems. In that select the provider system and click Assign to IBC reference and the same will be assigned.

This IBC reference will be displayed in SRT_MONI as Sender IBC Type / Sender IBC Reference and receiver IBC Type / Receiver IBC Reference.

Back to Integration Scenario configuration. Click on Next.

In the logon data assignment, select the value in the dropdown which corresponds to the login details of CI tenant.

This login details should be created under, Service Administration -> Logon Data Management.

Click on FINISH once done. A new integrated scenario will be created.

Set Port to default in Webservice Configuration

Go to Service Administration -> Webservice Configuration and set the logical port to True or in the local integration scenario, you will be prompted with “There are pending tasks. Click here to open”. Open it and click on Process list. It will process the pending task where the port will be activated against the soap service and once it confirms, click on Rebuild list to see the new pending tasks.

The prompt won’t show after the pending tasks are processed.

Once processed, go to webservice configuration option, and enter the webservice name and click on search.

Click on Set Log Port default. It will assign TRUE against the service.

And do the ping test to check if the WSDL is reachable.

Logical determination of receiver using Service Group

To maintain routing rules for the service group, where you want to transfer the message only if certain conditions are met. We need to configure this option – Service Administration -> Logical Determination of Router using Service Group.

Click on Create.

Enter the service group and choose the provider system.

Get those parameter values from functional and enter it in the below screen. Once done, click on CREATE NEW ROUTING. It will add the routing against the service group. Otherwise, without adding those parameters, it will show as Routing Not Maintained.

You can add multiple routings, if needed.