Supply Chain Management Blogs by SAP
Expand your SAP SCM knowledge and stay informed about supply chain management technology and solutions with blog posts by SAP. Follow and stay connected.
Showing results for 
Search instead for 
Did you mean: 
0 Kudos


Most of SAP Logistics Business Network (LBN) customers connecting their SAP S/4HANA systems to SAP LBN have a middleware such as SAP Process Integration, SAP Process Orchestration, SAP Cloud Integration (CPI) system etc. LBN also has many customers trying to connect their SAP S/4HANA system directly to SAP LBN using SOAMANAGER configuration. They follow a blog LBN has published to achieve the same. These connections are one-to-one from SAP S/4HANA to SAP LBN live landscape by creating manual configuration to define logical ports for an outbound webservice. In such a scenario, one of the manual ports needs to be set as default port. When one SAP S/4HANA system is acting as source for one SAP LBN shipper tenant, these manual configurations work fine.

If a customer needs to send data from one SAP S/4HANA system to multiple SAP LBN tenants, then the manual configurations won’t work. One such scenario is when a customer trying to replicate locations from single SAP S/4HANA system to multiple SAP LBN shipper/solution owner tenants. In this scenario we should have two logical ports pointing to same SAP LBN endpoint but authenticating using two different certificates. The logical port should be determined dynamically based on the receiver business system (LBN Id) in runtime. This is possible by configuring service groups in SOAMANAGER using integration scenarios.

The steps mentioned in this blog are using decentralized configuration (local configuration) approach in SOAMANAGER. There’s a central configuration also possible, the necessary steps for which are covered in a different blog - Global SOAMANAGER Configurations: Location Replication from one SAP S/4HANA system to multiple SAP Logistics Business Network tenants using centralized integration scenarios

We relied on this blog to setup these decentralized configurations.


  1. SAP LBN provides LocationReplicationRequest_Out WSDL to match the policies from SAP LBN's integration system. You've already obtained the same. If not, you can raise an incident with the team on component SBN-LBN-INT requesting the same.

  2. Make sure that necessary configurations are made in Data Replication Framework - DRF (tcode: DRFIMG) as per the steps mentioned in SAP LBN documentation.

  3. Ensure that the technical business systems assigned in replication models in DRF are your LBN Ids.

  4. In SOAMANAGER, ensure that you’re not using Central Configurations. This guide deals with local or decentralized configurations only.In case Central Configurations are enabled for your system, you need to follow a different blog and need to follow a different set of steps.

Configuration in SOAMANAGER

The following steps need to be performed in SOAMANAGER by customer

  1. Customer to upload the WSDL in SOAMANAGER

  2. Publish WSDL to Service Registry (twice)

  3. Create a Profile

  4. Create Provider Systems

  5. Create Logon Data

  6. Create Local Integration Scenario

  7. Create Configuration Object

  8. Logical Determination of Receivers using Service Groups

[1] Upload LBN provided WSDL in SOAMANAGER

  1. Reach out to LBN integration team requesting for the LocationReplication WSDL document. You can raise an incident with the team on component SBN-LBN-INT requesting the same.

  2. In SOAMANAGER, upload the WSDL. Navigation Tools -> WSDL Upload

[2] Publish the uploaded WSDL to service registry (twice)

Please note that steps a-f should be done twice. This is already mentioned in step g.

  1. Navigation: Service Registry-> Publication of external WSDL

  2. 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.

  3. Select the service state as Configured

  4. In the Bindings tab, ensure that Access URL is pointing to LBN SOAP endpoint and click Next. If not, reach out to LBN support.

  5. 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.Give System Name as the shipper LBN Id and host name as LBN CPI host ‘l20398-iflmap’

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

  7. Perform all the above steps for the second ‘Physical System’.

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

  9. Additionally, this will create two IBCs (Identifiable Business Context for the physical systems) in the service registry. Navigation: Service Registry-> Published IBCs

[3] Create a profile

  • Navigation: Technical Administration->Profiles (Example: Here the profile is used for maintaining proxy settings). Use the authentication method as X.509 SSL Client Certificate.

[4] Create provider systems

Please note that steps a-e should be done twice. This is already mentioned in step f.

  1. Navigation: Technical Administration->Provider Systems. Note: The Provider system names will be used as business system names in DRFIMG. These will be the LBN Id of each LBN systems.

  2. Under the service registry, select local service registry (SR_LOCAL) and then select the Third-Party system created earlier as the SLD Identifier. Note: If you do not see the use service registry check box, make sure the note 2600392 is implemented.

  3. Maintain user credentials to access WSDL from service registry and check the Tolerant Search

  4. Under applications, assign the business application (IBC) created earlier

  5. Click Finish and activate the provider system

  6. Do steps a) – e) for the second LBN Id as well.

  7. Two IBC references will be created. Navigation: Service Administration->Identifiable Business Context Reference

[5] Create Logon Data

  • Create Log on Data and activate it. Using navigation: Service Administration->Logon Data Management. Note: This will be used to log on to the provider system (will be used in the logical port created later)Choose X.509 SSL Client created for the first LBN tenant and activate it

  • Repeat the step for second tenant

[6] Create a local integration scenario

  1. Navigation: Service Administration->Local Integration Scenario Configuration

  2. Since we are going to use Service Group, we skip the service definitions tab

  3. In the service group tab, add the Service Group Object ‘/SCMB/LOC_REPLICATE_REQ’

  4. And assign the IBC references created earlier

  5. Make sure that Communication Protocol is WS Protocol

  6. In the next step, assign the Logon Datas created previously

  7. Finish and activate the integration scenario

[7] Create Configuration Objects (Logical Ports)

  1. Once the Integration Scenario is activated the system will display a link to configure and activate the consumer proxies using Pending Tasks. Alternatively, use navigation path, Service Administration->Pending Tasks

  2. Ensure the task list is executed successfully and as a result logical ports will be created using the service registry. Make sure logical ports are created for both the LBN Ids.

  3. Verify the configuration. Navigation: Service Administration-> Web Service Configuration. Configuration Search -> Object Name -> /SCMB/CO_CPX_LOC_BULK_REPL_REQ

  4. In the messaging tab, verify the RM protocol is set to SAP RM (required for CPI based connection

[8] Logical Determination of Receivers using Service Groups

  1. Navigation. Service Administration -> Logical Determination of Receiver using Service Groups -> Create.

  2. Select /SCMB/LOC_REPLICATE_REQ as the Service Group

  3. Select IBC Reference as the first LBN Id

  4. In the next step (Routing Details), provide the same LBN Id as the value for routing parameter.

  5. Click on Finish.

  6. Repeat steps a) - e) for second LBN Id.

  7. Routing conditions should look like this

Configurations in IMG

On S/4HANA On-Premise system, transaction code DRFOUT is used to replicate business partner and business partner relationship messages to external systems.

  1. The BC switch BSSOAV_WS_ACTIVE should be active in IMG. This is required for DRFOUT to use the service group configuration.

Testing the configuration

  1. Trigger a location message using DRFOUT for a single location using manual replication filter criteria

  2. Ensure that the DRFOUT was successful

  3. Go to SRT_MONI transaction and check the receiver IBN Name. If all the configurations are maintained correctly, you should see two different receiver IBC names

Alternate Approaches (Central Configuration)

The local configuration is not the best recommended practice anymore. Please see documentation and the following SAP notes:

  • 2985701   Using local and central configuration with external systems

  • 2933829   Central Configuration in SOAMANAGER

  • 2902829   Local configuration in SOAMANAGER

  • 2907252   Pending Tasks in local configuration

  • 2204011   Central configuration for Web services and other functions

Best practice is to use central configuration where you create a Third-Party or external domain system and upload the WSDL. This is documented in 2985701 and 2933829.


This blog talks about the decentralized or local configurations in SOAMANAGER to achieve local replication from one SAP S/4HANA system to multiple SAP LBN tenants. The central configurations are mentioned in a separate blog. Feel free to go through the alternate approach as well and configure what's best suited for your system. Interested to know the feedback from the community on these approaches as well.
1 Comment