Gratis demo

Service Group configuration in SOAMANAGER using Integration Scenarios

Ruchita Vanjari, 28 december 2022

In this blog, we will discuss how to configure the service group using local integration scenario in SOAMANAGER along with Data Replication Framework setting in S4HANA for Replication of data

This is useful when you want to replicate master data from S/4 to more than one external system (example SAP Cloud for Customer aka C4C and SMILE ,  CIG), using Data Replication Framework (DRFOUT).

It is recommended to create logical ports based on integration scenarios for service groups, rather than creating logical ports manually in SOAMANAGER.

In this blog we will configure the service group MDG_BS_SUPPLIERREPLICATEREQ to configure the consumer proxies 

BusinessPartnerSUITEBulkReplicateRequest_Out (CO_MDG_BP_RPLCTRQ) BusinessPartnerRelationshipSUITEBulkReplicateRequest_Out (CO_MDG_BP_RELATIONSHIP_OUT)

Configuration in SOAMANAGER

The following steps need to be performed in SOAMANAGER

  1. Prepare and Upload WSDL
  2. Publish WSDL to Service Registry
  3. Create a Domain
  4. Create a Domain System
  5. Create Logon Data
  6. Create Local Integration Scenario
  7. Create Configuration Objects

Prepare and Upload WSDL

You can download WSDL files directly from here.
Note: You need to change the host Name in the URL configured in these WSDL file.

You can also fetch these files individually from system. Execute transaction sproxy in SAP S/4HANA system and download the WSDL files for the below interfaces.



Altering the WSDL files with C4C Endpoints

Add the following elements at the end of each of the WSDL Files before the </wsdl:definitions> tag.

It is important to note that the below XML element contains a sample  Endpoint. You would have to replace this with your CPI details for all of them.

E.g. For BP, replace


with your CPI  tenant endpoint. Additionally, make sure the endpoint contains the 443 port number suffixed after the Host Name.



<wsdl:binding name=”CO_MDG_BP_RPLCTRQ” type=”tns:BusinessPartnerSUITEBulkReplicateRequest_Out”>

<soap:binding transport=”” style=”document”/>

<wsdl:operation name=”BusinessPartnerSUITEBulkReplicateRequest_Out”>

<soap:operation soapAction=”” style=”document”/>

<wsdl:input name=”BusinessPartnerSUITEBulkReplicateRequest”>

<soap:body use=”literal”/>




<wsdl:service name=”BusinessPartnerSUITEBulkReplicateRequestOut”>

<wsdl:port name=”C4C_PORT” binding=”tns:CO_MDG_BP_RPLCTRQ”>

<soap:address location= “https://<cpihost>” /></wsdl:port>





Publication of External WSDL

Navigation: Service Registry-> Publication of external WSDL



Under Service Details tab, provide an internal name



Note: The Port type name and namespace in the external WSDL should match the corresponding names defined in SE80.

Select the service state as Configured


In the Bindings tab, Click Next


Create a new Physical system, with system type as Third Party (This will make sure the RM protocol is set to SAP RM when the logical ports are created later for asynchronous reliable messaging). This is mandatory to send messages via SAP Cloud platform Integration


Review the service details and click on finish to publish the WSDL to local service registry

Perform all the above steps for the other consumer proxies in the service group except for the Physical system. Select the existing system that was already created.


We can verify the published service definitions using the navigation path: Service Registry-> Published Service Definitions

Create a Domain

Navigate to tab “Technical Administration” and open “Domain”.


Click on “Create Domain ”.

Enter a Name and a Domain Description for accessing C4C and select “Old Profile Mode”.




Click “Next” and fill out the Security Settings as follows –
a. Authentication Method: User ID/Password
b. Identifiable Business Context: No IBC Determination
c. Transport Security: Select “Secured Communication”

Click “Next”. In case Proxy Settings are used, fill them in. Otherwise leave them empty & click “Finish”
Confirm the popup with “Yes”  and activate the Domain


Create a Domain System ( Configuring C4C  as “Third party Domain System )

Navigate to tab “Technical Administration” and open “Domain Systems”


Click on “Create” dropdown and select “Create Domain System”


Provide a name for the Domain System.
NOTE: The name of the Domain system here should “exactly” match the value configured in Generic Configuration on C4C.
In the “Domain Name” dropdown, select the value created in previous step.


Click Next. Provide credentials of a system user that can access Service metadata(Please provide S4HANA Technical user credentials). Ensure that the “Use WSIL user” checkbox is selected.


Click Finish. At this step you will get a popup to activate the Provide system. DO NOT activate it yet.

Click on the Provider System that was just created and navigate to “WSDL Upload” tab


Click on “Upload” button and select the WSDL file from your system.


Click “Next”. Do not modify the WSDL.


Click Next. Ensure that the Service Definition Name is selected


Click “Next” and then click “Confirm”.


Repeat the above step for all the WSDL Files that you want to upload.

Finally, click on “Activate”

Create Logon Data

Navigate to tab “Service Administration” and open “Logon Data Management”.


Click on “Create”. Provide a meaningful Logon Data Name & Description.


Provide Logon Data for CPI by entering User Name & Password in case of using Basic Authentication.

From the service keys of CPI instance, clientId is the username and client secret is the password.


Click “Finish” and confirm the popup with “Yes” to activate the Logon Data immediately.

Create Logan Data Assignment 

Click on Assignment Tab – go to create


Select the Client in this case – 0M232MJ

Next select the Logon data created previously and click on finish


Create Local Integration Scenario

The local integration scenario will only contain the outbound messages from SAP S/4 HANA to SAP C4C. In principal it would also be possible to configure the corresponding inbound services as well. However, the current SAP S/4 HANA – C4C – integration requires a different alternative access URL. Therefore, the configuration for the inbound services must be done (manually) outside the Local Integration Scenario Configuration.

Navigate to tab “Service Administration” and open “Local Integration Scenario Configuration”


Create new integration scenario by clicking “Create”.

Provide a meaningful Name & Description.


Click “Next”. Since no inbound services shall be configured here (explanation see above), click “Next”.


Add the following Service Groups

The result should look like this.


Select the Logon Data for each Service Group from the dropdown. Choose the Logon Data created earlier for all the service groups.


Click “Finish”. Confirm the popup with “Yes” if you want the integration scenario to be activated immediately.

Activate the pending tasks. Navigate to them by clicking the link.


Click “Process List” to activate the logical ports


If everything has been done properly, the logical ports should be activated successfully. Confirm the popup with “OK”.


If everything has been configured as desired, navigate to tab “Service Administration” and open “Web Service Configuration.

You can also verify the web service configuration on the respective consumer system (ABAP client) as mentioned in the previous blog under Verify the Configuration section The only difference being, the type of logical port being created should be Central instead of Local.


As search criteria, enter one of the Consumer Proxy
and click “Search”


You can also verify the web service configuration on the respective consumer system (ABAP client) as mentioned in the previous blog under Verify the Configuration section The only difference being, the type of logical port being created should be Central instead of Local.


Similarly, you can verify Logical Port creation for other Service Groups.

At this point you Business Partners created in this system will be replicated to your C4C  tenant.

Configuration in S4HANA

The following steps need to be performed in S4HANA

  1. Creating a logical System – BD54
  2. Creating a Business Partner
  1. Define Technical Settings for Business Systems and Define Replication Models
  2. Activate Function Modules

Creating a logical System – BD54

This describes the procedure to create a logical system that represents the SAP Cloud for Customer system. Logical systems are defined as cross-client systems.


Access the following transaction:

Transaction Code BD54
  1. Choose New Entries.
  2. Create a logical system that identifies the on-demand system, as given in the table below: following:
  3. Choose Save
  4. Choose Ok to confirm the pop-up or create a meaning TR and then choose ok.
Field Entry
Logical System <logical system name of Cloud for Customer tenant> This can be found in SAP Cloud for Customer under My Communication Data of a Communication Arrangement.
Name <Description> for example: SAP Cloud for Customer.

Creating a Business Partner


This chapter describes the procedure to create a Business system that represents the SAP S/4HANA system.

We can perform this task in following way.


  1. Access the following transaction:
Transaction Code IDMIMG
  1. Navigate to BAdI, Determination of Local System Name from Define Technical Settings.
  2. Execute the BAdI, Determination of Local System Name to create a Local Business System.


Note : Check IMG Activity Documentation for more detail how to perform this task.

Define Technical Settings for Business Systems and Define Replication Model


In this Customizing activity, you complete the following tasks:

A business system can represent a central hub or a local system.

You must complete this activity if you want to replicate data using a replication model within the data replication framework (DRF), or if you want to customize business systems for key mapping or value mapping.


You have maintained the System Landscape Directory.

You have defined a logical system in transaction BD54.

You have defined the required RFC destinations in transaction SM59.

  1. Open transaction DRFIMG.
  2. Navigate to Define Custom Settings for Data Replication àDefine Technical Settings àDefine Technical Systems for Business Systems.45
  3. Choose New Entries to add Business System for SAP Cloud for Customer. Add Business System name as logical system and Logical System name using input help. Choose Save,

Note :-  Make sure that Business System is same as My System maintained in Communication Arrangement in SAP Cloud for Customer.

  1. Select the Business System and double click on Define Bus. Systems, BOs in the Dialog structure.46
  2. Choose New Entries and add BO Type 986 (Business Partner including relationships) using input help and check field Filt. In case this entry exists, skip the step.


  1. Select the entry BO type and double click on Define Bus. Systems, BOs, Communication Channel in the left dialog structure.


  1. Choose New Entries to add the Communication Channel as 1 Replication via Services. In case the entry exists, skip this step.



  1. Choose Save.
  2. Navigate back.

Replication Model


In this Customizing activity, you define replication models and specify the outbound implementations that are used for each replication model. You also verify that the data replication framework can use the replication models you have created by running a report.


  1. Select the IMG activity Define Replication Models.


  1. Choose New Entries and define Replication Model Name and Description and Log days as 50.
  1. Choose Enter.
  2. Select the entry created and double click on Assign Outbound Implementation.


  1. Choose New Entries.
  2. Select Outbound Implementation as Outbound Impl. for BP/REL via Services (986_3) using the input help and choose Enter.
  3. Enter Sequence as 1.


  1. Select the row added and double click on Assign Target Systems for Repl. Model/Outb.Impl in dialog structure.



  1. Choose New Entries and add the Business system created above using the input help.
  2. Select the Business system row and double click on the node Assign Outbound Parameter in the dialog structure.


  1. Choose New Entries to add the Outbound parameter PACK_SIZE_BULK using the input help, Check field Mandatory and enter outbound parameter value as 20.



Outbound Parameter value for PACK_SIZE_BULK can be set as per most efficient package size, which will differ from system to system.

  1. Choose Save,
  2. Click Define Replication Model.
  3. Click Activate to activate the replication model.


Activate Function Modules


  1. Open transaction SPRO.
  2. In IMG menu structure, navigate to Cross-Application ComponentsàSAP Business Partner àData Distribution à Activate Function Modules.


3. Activate the function module MDG_BS_BP_OUTBOUND_DRF by checking the field Call as shown below.


4. Choose Save.

Test the configuration

  1. Trigger a Business partner message using DRFOUT and check SRT_UTIL (Web Services utilities) message monitor using forward navigation from DRFOUT logs.


2. In the payload the RecipientBusinessSystemID in MessageHeader is populated from the Business system name defined in DRFIMG, which is same as the provider system name in SOAMANAGER.


3. For demonstration purpose, the message was made to fail intentionally, so that we can verify the logical port used by DRFOUT, in Web Service utilities-> Error Log.



4. Here we can see the logical port ( 000D3A46D7471EEDA1A43A6A6C908374 ) being used, which is same as created in SOAMANAGER for the service group.


Ruchita Vanjari

Read all my blogs

Receive our weekly blog by email?
Subscribe here: