---
schema_version: "1"
id: 3b54dfca1e16efe819a65e0a78015f965c70b8d2b9a4c7b0cc4609c5709dd759
title: SAP S4HANA Setup Guide
collection: mulesoft
version: current
locale: en-us
portal_url: https://docs.salesforce.com/mulesoft/current/en-us/retail/latest/sap-s4hana-setup-guide.md
canonical_url: https://docs.mulesoft.com/retail/latest/sap-s4hana-setup-guide
source_site: docs.mulesoft.com
content_type: documentation
content_hash: 444a552e077086889e3e811b1cb010ab9637091624fd01035e0e8d776da8bf90
description: MuleSoft Documentation Site
release: "3.2"
latest: true
---
---
product: Retail
version: 3.2
is-latest-version: true
---

# SAP S4HANA Setup Guide

> For the full documentation index, see: https://docs.mulesoft.com/llms.txt

## Overview

The following describes how to configure and test an S/4HANA Cloud SOAP outbound service (Product
replication: `productmdmbulkreplicaterequest`) and the S/4HANA Cloud SOAP Connector as a Mule
application deployed on Cloudhub.

## Configurations in S/4HANA

To make the necessary configurations in S/4HANA:

1.  Create a **Communication System** in the corresponding Fiori app. This communication system
    represents the external system that will consume the S/4HANA Cloud SOAP service. In this
    example, it’s named `COM_0009_SOAP_OUT`:

    ![SAP S/4HANA Create Communication System](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-01.png)

2.  For the 'Business System' name, use the same name of the System ID.

3.  In the 'Host Name' field, enter the hostname of the Mule application deployed on Cloudhub (if
    you don’t have it yet, you can enter a mock URL and then modify it later):

    ![SAP S/4HANA Communication System with Host Name field](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-02.png)

4.  Create a user that will be used to connect to the Cloud Hub app for sending product information
    in the outbound scenario (this is necessary even though the Mule application does not validate
    the user; we used any user for outbound):

    ![SAP S/4HANA user creation](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-03.png)

5.  Use the **Communication Arrangement** Fiori app to create a new Communication Arrangement:

    ![SAP S/4HANA Create Communication Arrangement](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-04.png)

6.  Create a new **Communication Arrangement**, select the communication scenario "SAP\_COM\_0009",
    and then define a specific name for the arrangement, "SAP\_COM\_0009\_SOAP".

7.  In the **Communication System** field, select the Communication System created in the previous
    step:

    ![SAP S/4HANA Communication Arrangement with Communication System selected](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-05.png)

8.  For outbound communication, select the previously-created user and configure the **Product
    Master - Replicate from SAP S/4HANA Cloud to Client** and include the following settings. Make
    sure to note the Path (`/sap/bc/srt/scs/sap/productmdmbulkreplicaterequest`) because we will use
    this path to configure the Mule application SOAP endpoint:

    - Set the **Service status** to **Active**

    - Replication Model (any name)

    - Replication model = `I (Initial)`

    - The Output Mode = `D (Direct)`+

      ![SAP S/4HANA outbound service with Service Status set to Active](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-06.png)

      ![SAP S/4HANA outbound service Replication Model settings](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-07.png)

      ![SAP S/4HANA outbound service Output Mode settings](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-08.png)

9.  Save it. All configurations at S/4HANA Cloud side are finished and you will be able to download
    the WSDL that contains the metadata to import into the S/4HANA Cloud SOAP Connector into the
    Mule application.

## Configurations in the Mule Application

The following example describes how to create a Mule application using the Outbound Message Listener
operation of MuleSoft’s SAP S/4HANA SOAP Connector:

1.  Create a Mule project and add the appropriate connector from Exchange to the Mule Palette:

    ![Anypoint Studio Mule Palette with SAP S/4HANA SOAP Connector](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-09.png)

2.  Add and configure the **Outbound Message Listener** to the canvas:

    ![Anypoint Studio Outbound Message Listener configuration](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-10.png)

3.  Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the
    HTTP listener configuration:

    ![Anypoint Studio SAP S/4HANA SOAP Connector WSDL configuration](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-11.png)

    ![Anypoint Studio HTTP Listener configuration](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-12.png)

    _Note: we are using no authentication on the Mule Application, so we used the Insecure option
    for the Trust Store Configuration. In the Keystore configuration, we used a test Keystore, which
    is mandatory for HTTPS communication:_

    ![Anypoint Studio TLS configuration with insecure trust store](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-13.png)

4.  Select the Message type that the connector expects to receive from SAP (the connector reads the
    metadata from the WSDL we configured):

    \+ image::retail-sap-s4hana-setup-guide-14.png\["Anypoint Studio SAP S/4HANA SOAP message type
    selection",width=799\]

5.  On the Responses tab, use the status Code "202" and the Reason-Phrase "Accepted" because we want
    to send the same status that S/4HANA Cloud will send if the service invocation results OK. No
    payload will be returned as a response - just the `Status` code and `Reason-phrase`:

    ![Anypoint Studio response configuration with HTTP status 202 Accepted](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-15.png)

6.  Use a **Logger** component to log the inbound XML payload:

    ![Anypoint Studio Logger component configuration](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-16.png)

    _The Mule flow should look like the following:_

    ![Anypoint Studio flow for receiving SAP S/4HANA product replication messages](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-17.png)

7.  Deploy the application to Cloudhub. You’re now ready to test the scenario.

## Testing the Scenario

To test the scenario:

1.  Create the following. You only need to create a material in the corresponding Fiori app of
    S/4HANA Cloud:

    ![SAP S/4HANA material creation](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-18.png)

    ![SAP S/4HANA material data entry](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-19.png)

    ![SAP S/4HANA material configuration](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-20.png)

    ![SAP S/4HANA material save](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-21.png)

    _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_

    ![SAP S/4HANA confirmation that the material was saved](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-22.png)

    _The following shows the XML message received at the Mule application at the Runtime Manager on
    Cloudhub:_

    ![Anypoint Runtime Manager log with the received product replication message](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-23.png)

2.  See the sent message in the Message Dashboard Fiori Application:

    ![SAP S/4HANA Message Dashboard with sent product replication message](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-24.png)

3.  Select the date:

    ![SAP S/4HANA Message Dashboard date selection](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-25.png)

4.  Search under **CMD:Product Integration - /CMDPR → Product Replication to Client via Service -
    PRDREQ\_OUT/00001 namespace**:

    ![SAP S/4HANA Message Dashboard search for product replication messages](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-26.png)

    ![SAP S/4HANA product replication message details](/mulesoft/current/en-us/retail/latest/_images/retail-sap-s4hana-setup-guide-27.png)

## S/4HANA customization guide

The following provides guidance on the custom fields that you must create for both the customer and
order sync use cases to function in an end-to-end manner.

### Custom fields

Create the following new fields in the corresponding objects for the use case:

<table><colgroup><col> <col> <col> <col> <col> <col></colgroup><thead><tr><th>Salesforce Object</th><th>Field Name</th><th>Data Type</th><th>Length</th><th>Unique</th><th>ExternalId</th></tr></thead><tbody><tr><td><p>BusinessPartner</p></td><td><p>YY1_SME_MPARTYROLEID_bus</p></td><td><p>Text</p></td><td><p>36</p></td><td><p>Y</p></td><td><p>Y</p></td></tr><tr><td><p>SalesOrder</p></td><td><p>YY1_SME_MORDERID_SDH</p></td><td><p>Text</p></td><td><p>36</p></td><td><p>Y</p></td><td><p>Y</p></td></tr><tr><td><p>Product</p></td><td><p>YY1_SME_UnvProductId_PRD</p></td><td><p>Text</p></td><td><p>36</p></td><td><p>Y</p></td><td><p>Y</p></td></tr></tbody></table>

## See Also

- [Prerequisites](https://docs.mulesoft.com/retail/latest/prerequisites)

- [MuleSoft Accelerator for Retail](https://docs.mulesoft.com/retail/latest/)
