logo

Are you need IT Support Engineer? Free Consultant

SAP Logistics Management: Direct Integration with SAP S/4HANA Cloud Private Edition – Part 2

  • By Sanjay
  • 18/11/2026
  • 16 Views



Recap of Part 1

Authors : @abhijitbolakhe  & @Saurabh_Goyal

This is Part 2 of a two-part series on integrating SAP Logistics Management directly with SAP S/4HANA Cloud Private Edition, with no middleware in between.

In Part 1, we covered the direct integration architecture and prerequisites, prepared the S/4HANA system (warehouse, OData services, PFCG role, technical user and AIF content) and exposed the four inbound web services in SOA Manager.

This blog completes the setup. It configures the outbound web services in S/4HANA, sets up the Cloud Connector, finishes the configuration in SAP Logistics Management and ends with a checklist to validate the integration end to end. As a reminder, this is how the messages flow between the systems:
Step 1 & 2 are covered in Part 1 Blog

Picture1.Png

Step 3: Configure the outbound web services in S/4HANA

In this step S/4HANA learns where to send its warehouse messages. You download six consumer WSDL files, add the SAP Logistics Management endpoint to each, and then build the logical ports in SOA Manager.

3.1 Download the WSDL files

In SE80, open package LE_IDW_SOA_SERVICES and go to Enterprise Services > Service Consumers. For each consumer, open the WSDL tab and use Save to file.

 

Service consumer

Binding name to add

WarehouseShippingOrderRequest_Out

CO_LEIDW_WAREHOUSE_SHIP_ORDER

WarehouseShippingAdviceCancelConfirmation_Out

CO_LEIDW_WAREHOUSE_SHIPPING_AD

WarehouseIntermediateUpdateConfirmation_Out

CO_LEIDW_WHSE_INTERM_UPD_CONF

SplitOutboundDeliveryConfirmation_Out

CO_LEIDW_SPLIT_OUTBOUND_DELIVE

WarehouseStockTransferShipmentAdviceRequest_Out

CO_LEIDW_WAREHOUSE_STOCK_TRANS

WarehouseStockTransferReceiptAdviceCancelConfirmation_Out

CO_LEIDW_WAREHOUSE_STOCK_TRAN1

3.2 Add the binding and endpoint to each WSDL

For each downloaded WSDL file, add the binding and service definition code before the closing </wsdl:definitions> tag. Replace the <<Endpoint>> placeholder with the actual endpoint URL in the following format: https://{tenant}.{region}.lgm.cloud.sap/api/soapadapter-sap-internal/v1/soap/v1

Here, {tenant} is the subdomain of the SAP BTP subaccount in which SAP Logistics Management is subscribed, and {region} is the region of your instance

Refer this link for all service consumers with Binding & Service Definitions
(OutBound Webservices)

Abhijitbolakhe_0-1794973772907.Png

3.3 Create the logon data

In SOAMANAGER, go to Service Administration > Logon Data Management > Maintenance and choose Create.

Abhijitbolakhe_1-1794974096955.Png

3.4 System Type as Central System

  1. Domain system: Under Technical Administration > Domain Systems, choose Create. Enter an ID and name and upload the six modified WSDL files.
    Under Provider System, check that the WSIL user is your S/4HANA technical user.

    Abhijitbolakhe_2-1794974211466.Png

    2. Domain: Under Technical Administration > Domains, choose Create.

    Abhijitbolakhe_0-1794974341669.Png

    3. Logon data assignment: Under Service Administration > Logon Data Management > Assignments, choose Create. Enter the provider IBC reference of the domain system and select the logon data

    Abhijitbolakhe_1-1794974364811.Png

    Abhijitbolakhe_2-1794974378208.Png

    4. Integration scenario: Under Service Administration > Integration Scenario Configuration, choose Create. Under Service Group Connections, create a connection with the S/4HANA system as Actor 1 and the domain system as Actor 2. Choose connection type Service Group Based, One Way and enter LE_IDW_SOA_3PL_INTEGRATION. Check the consumer proxy and provider interface under Define Matching Interfaces, assign the logon data, then Activate and Release. Refresh until the status shows success.

    Abhijitbolakhe_3-1794974399865.Png

    5. Logical determination: Using the provider IBC reference from the domain system and the warehouse number of the SAP Logistics Management warehouse.

    Abhijitbolakhe_4-1794974443348.Png

    Step 4: Configure the Cloud Connector

    The Cloud Connector is the reverse-invoke proxy that lets SAP Logistics Management on SAP BTP reach your S/4HANA system without opening inbound firewall ports. You connect it to the SAP Logistics Management subaccount and then expose S/4HANA as a virtual system.

    Abhijitbolakhe_5-1794974468952.Png

    Step 5: Configure SAP Logistics Management

    Four tasks complete the integration on the SAP Logistics Management side: create the BTP destination, import the organizational model, create the system connection and replicate the code lists. Do them in this order, because each depends on the one before.

    5.1 Create the BTP destination

    In the SAP BTP cockpit, open the SAP Logistics Management subaccount and go to Connectivity > Destinations. Choose Create Destination.

    Abhijitbolakhe_6-1794974468958.Png

    5.2 Import the organizational model

    SAP Logistics Management needs to know the slice of your S/4HANA enterprise structure that relates to its warehouses. You maintain it in a spreadsheet and upload it.

    Abhijitbolakhe_7-1794974468961.Png

    5.3 Create the system connection

    In the SAP Logistics Management Fiori launchpad, open Manage System Connections and choose Create for Connection Type: 3001
    You can find the service paths or the calculated access URLs in the inbound web service configuration

    Abhijitbolakhe_8-1794974468965.Png

     

    Abhijitbolakhe_9-1794974468969.Png

    5.4 Replicate the code lists

    Units of measure and other customizing data must exist in SAP Logistics Management before you set up business processes.

    1. Open Manage Replication Configuration and create an entity configuration for business object type SAP S/4HANA Customizing Data.
    2. Open Schedule Data Replication and create a schedule for the same business object type.
    3. Run the job.

     Abhijitbolakhe_10-1794974468970.Png

     Abhijitbolakhe_11-1794974468973.Png

    Validate the setup

    Work through these checks in order. Each one confirms a link in the chain, so the first failure tells you where to look.

    • The Cloud Connector subaccount shows Connected, in the connector and in the BTP cockpit.
    • Check Connection on the BTP destination succeeds.
    • All four inbound service bindings exist in SOA Manager and you have their access URLs.
    • The logical ports for the six outbound consumers are active, with no pending tasks left in SOA Manager.
    • The receiver determination for LE_IDW_SOA_3PL_INTEGRATION routes to the right warehouse number.
    • The system connection with type 3001 is created in SAP Logistics Management.

    Conclusion

    Direct integration gives you a lean landscape: S/4HANA, a Cloud Connector and SAP Logistics Management, with no middleware tenant to run. Most of the effort sits in SOA Manager, where four inbound bindings and six outbound consumers have to be configured carefully, and the rest is standard BTP connectivity.

    If you have set this up in your own landscape, I would be glad to hear your experience .

    References





Source link

Leave a Reply

Your email address will not be published. Required fields are marked *

Chat with us on WhatsApp!