SAP S/4HANA Setup Guide | MuleSoft Documentation
# SAP S/4HANA Setup Guide
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": 
  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): 
  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): 
  5. Use the **Communication Arrangement** Fiori app to create a new Communication Arrangement: 
  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: 
  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). 
  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: 
  2. Add and configure the **Outbound Message Listener** to the canvas: 
  3. Add the corresponding WSDL path to the WSDL you downloaded from S/4HANA Cloud and create the HTTP listener configuration: _*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:_
  4. Select the Message type that the connector expects to receive from SAP (the connector reads the metadata from the WSDL we configured): 
  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: 
  6. Use a **Logger** component to log the inbound XML payload: _The Mule flow should look like the following:_
  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: _After you save the new material, you should see the following confirmation in S/4HANA Cloud:_ _The following shows the XML message received at the Mule application at the Runtime Manager on Cloudhub:_
  2. See the sent message in the Message Dashboard Fiori Application: 
  3. Select the date: 
  4. Search under **CMD:Product Integration - /CMDPR → Product Replication to Client via Service - PRDREQ_OUT/00001 namespace** : 


## 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.
Create the following new fields in the corresponding objects for the use case:
Salesforce Object | Field Name | Data Type | Length | Unique | ExternalId  
---|---|---|---|---|---  
BusinessPartner | YY1_SME_MPARTYROLEID_bus  
SalesOrder | YY1_SME_MORDERID_SDH  
YY1_SME_UnvProductId_PRD  
The following provides guidance on the custom fields that you must create for both the customer and product sync from SAP S/4HANA to Salesforce Consumer Goods Cloud.
Create the following fields using the app Custom fields:
SAP Field Name | Label | Data Type | Length | SAP Business Context  
---|---|---|---|---  
YY1_SME_ParentID_RTL | Parent ID | Master Data: Business Partner  
YY1_SME_AccouTemp_RTL | Account template | Master Data: Business Partner  
YY1_SME_KAM_Prod_RTL | KAM Products | Master Data: Product General  
YY1_SME_Comp_Prod_RTL | Competitive Product | Checkbox | Master Data: Product General  
YY1_SME_Prod_Temp_RTL | Product template | Master Data: Product General  
YY1_SME_Prod_Code_RTL | Product code | 50 Master Data: Product General  
YY1_SME_Shrt_PCode_RTL | Short Product Code | Master Data: Product General  
YY1_SME_Sell_Code_RTL | Sell in Code | Master Data: Product General  
YY1_SME_Asset_Temp_RTL | Asset Template | Master Data: Product General  
YY1_SME_PackSize_RTL | Pack Size | Master Data: Product General  
YY1_SME_PackSizeUn_RTL | Pack Size Unit | Master Data: Product General  
YY1_SME_ProdForm_RTL Product Form | Master Data: Product General  
YY1_SME_Category_RTL | Category | Master Data: Product General  
YY1_SME_SubCategor_RTL | SubCategory | Master Data: Product General  
YY1_SME_Brand_RTL | Master Data: Product General  
YY1_SME_Flavor_RTL | Master Data: Product General  
YY1_SME_Package_RTL | Master Data: Product General  
YY1_SME_Prod_Desc1_RTL | Description 1 | Master Data: Product General  
YY1_SME_Prod_Desc2_RTL | Description 2 | Master Data: Product General  
YY1_SME_DlvValFrom_RTL | Delivery Valid From | Master Data: Product General  
YY1_SME_FieldValFr_RTL | Field Valid From | Master Data: Product General  
YY1_SME_KAMValFrom_RTL | KAM Valid From | Master Data: Product General  
YY1_SME_NewItmVldF_RTL | New Item Valid From | Master Data: Product General  
YY1_SME_FundValiFr_RTL | Fund Valid From | Master Data: Product General  
YY1_SME_DlvValThru_RTL | Delivery Valid Thru | Master Data: Product General  
YY1_SME_FieldValTh_RTL | Field Valid Thru | Master Data: Product General  
YY1_SME_KAMValThru_RTL | KAM Valid Thru | Master Data: Product General  
YY1_SME_NewItmVldT_RTL | New Item Valid Thru | Master Data: Product General  
YY1_SME_FundValiTh_RTL | Fund Valid Thru | Master Data: Product General  
YY1_SME_ManItemNmb_RTL | Manufacturer Item Number | Master Data: Product General  
YY1_SME_EstimValue_RTL | Estimated Value | Master Data: Product General  
YY1_SME_PowSuppCon_RTL | Power Supply Connected | Checkbox | Master Data: Product General  
YY1_SME_HierarchID_RTL | Hierarchy Identifier | Code List | Master Data: Product General  
As YY1_SME_HierarchID_RTL data type is Code list, the possible values for are:
Code Value | Description  
---|---  
On the section ‘UIs and Reports’ for each field enable the corresponding UI app (Business Partner or Product basic data) and the option OData extension model and publish.
To add the fields into each app, use the option Adapt UI from your profile.
## See Also
  *   * MuleSoft Accelerator for Consumer Goods