Name: SAP S/4HANA Cloud Configuration: Integrating SAP Sales and Service Cloud with SAP S/4HANA Cloud using SAP Cloud Integration
Uploaded: 2023-6-20
Duration: 633 s

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div>During this second video of the Integrating SAP Sales and Service Cloud with SAP S/4HANA Cloud using SAP Cloud Integration series, we will start with the configuration of SAP S/4HANA Cloud system, covering only a few steps, because we treat the rest of the configuration as given:<br><ul><li><p>Double checking a prerequisite in the Configure Your Solution area</p></li><li><p>Must create the Communication User and the Communication System</p></li><li><p>Finish by setting up Communication Arrangements</p></li></ul><br></div></div></div></div></div>

SAP  S/4HANA Cloud Configuration: Integrating SAP Sales and Service Cloud with SAP S/4HANA Cloud using SAP Cloud Integration

In this video we will start with the configuration of SAP S/4HANA Cloud. We have only a few steps, because we treat the rest of the configuration as given: First of all, we need to double check a prerequisite in the Configure Your Solution area. Then we must create the communication user and the communication system. And after that, we can setup communication arrangements. Let’s log on to the system. In order to check the required solution scope, search for the app Manage Your Solution and navigate to View Solution Scope. Make sure that the scope item Opportunity to Order with SAP Cloud for Customer is in scope. You should easily find it when you search for Opportunity. If it is not in scope, you have to request it before you can continue. In the next step we will create the communication user.  Search for the app Maintain Communication Users and open it.  Select new. Enter a meaningful username and a description. For example "CODINTEG" and "SAP Sales Cloud User". The username will be used by SAP Cloud Integration for authentication later on. The description is only for internal purpose. Enter a good password and finish this step by selecting Create in the lower right corner. Now we have to create the communication system. Search for the app Communication Systems and open it. Select New and enter the system ID of the SAP Sales and Service Cloud system. It’s common to enter the same as system name, but you can also enter a speaking name here. Let’s quickly see, where we can find the system ID in SAP Sales and Service Cloud. We navigate to the Administrator work center, view General Settings and then select Communication Arrangements. Unfortunately, we can find system ID only inside of an existing communication arrangement. If you have already configured some communication arrangements, you can simply open one of them. Otherwise, we need to carry out the first two steps of the creation process by selecting New and then we can choose any displayed communication scenario from the list. For instance: Analytics Data Upload. On the next page you can then see the system ID of your SAP Sales and Service Cloud right under My Communication Data. Let’s come back to our S/4 configuration. Select Create to close the small dialog and get to the details screen. On this screen, enter the system ID again into the fields Logical System and Business System. Then we need to fill the Hostname field. The hostname that we maintain here does not refer to our SAP Sales and Service Cloud system. Instead, it must refer to SAP Cloud Integration, because this is the communication partner that will forward the message to SAP Sales and Service Cloud. The hostname reflects the technical network layer where we want to send requests to. To be more precise: The runtime or worker node hostname of SAP Cloud Integration. The system ID or logical system name can be compared to the name of a person in a salutation. If you talk to that person with the wrong name, the person will probably not answer and ignore your request. That will be the same with our systems. Keep in mind that we must choose the integration flow hostname here. If you are not sure which one that is, you can simply look it up by logging on to the WebUI of SAP Cloud Integration and navigating to Manage Integration Content. Choose an integration flow with an externally reachable endpoint. We can find the relevant hostname on the righthand side. Alright, back to the configuration: Scroll down to the section Users for Inbound Communication. Here we add a User for Inbound Communication with username and password authentication. The user that we assign here is the integration user that we have created previously. After that we maintain the User for Outbound Communication. Here we choose SSL Client Certificate as Authentication Method and choose the Client Default certificate from the list. Download the certificate and save it with a meaningful name, like "S/4 Certificate". After that confirm the dialog by selecting Create and finish the communication system creation by selecting Save in the lower right corner. The last step in S/4 HANA Cloud configuration is the setup of communication arrangements. We need to setup two communication arrangements: Cloud for Customer and Product Integration. Let’s start with Product Integration. Search for the app Communication Arrangements and open it. Select New and search for the scenario Product Integration.  Confirm the dialog by selecting Create. First of all, on the details screen, assign the communication system, that we have created earlier, which represents our SAP Sales and Service Cloud system logically. Notice, that some other details, like the usernames for inbound and also outbound communication have been filled automatically. Scroll down until you reach the Outbound Services section. In order to get a better overview on the outbound services, let’s collapse all the details first. We have three outbound services. The only one that we need for our scenario is the: Product Master - Replicate from SAP S/4HANA Cloud to Client. That means, we can deactivate the first one  and the last one. Now we can have a closer look at the outbound service that’s relevant for us. This one needs to stay active, of course. The Application Protocol is SOAP and not IDoc. That’s a hint, that we have picked the right service. And the port is 443 which is the default port for https traffic. That’s also fine. The first setting, that we have to adapt for this service is the Path. This is the endpoint where product replication messages will be sent to and it must point to the respective integration flow on SAP Cloud Integration. So far, we haven’t configured or deployed any integration flows, but the default path of the integration flow, that we will use later on, is different from the one suggested here. We adapt the path here to match the integration flow default. Let’s have a quick look where we can find this path in SAP Cloud Integration. Open SAP Cloud Integration WebUI and navigate to the Actifacts tab of your package in the Design area. Search for the desired integration flow. In our case: Replicate Material from SAP Business Suite. From the menu, select Configure and make sure the configure dialog is showing the Sender page. The Address field contains the path of the integration flow. We only need to keep in mind, that for the deployed integration flow, the path will start with the prefix "cxf". If the integration flow was already deployed, we could even lookup the final endpoint with the full path including this prefix. In this case you could navigate to the Monitoring area, Manage Integration Content and locate the integration flow. In case you have multiple integration flows with the same name from different packages, make sure you are looking at the right one from the right package. And here we can finally see the endpoint including the full path with the "cxf" prefix. Alright. Let’s get back to our communication arrangement. We have adapted the path. Now we need a closer look at the Additional Properties. First of all, we have to define a name for the Replication Model that we will use later when sending out products. For the Replication Mode we choose "C": Change Replication, so that products are sent out, whenever they are changed. The System Filter can be left Empty for the moment. And we set the Output Mode to "D": Direct Output, because we want changes to be replicated instantly. After we have maintained those additional properties, we are finished with the Product Integration communication arrangement and can select Save in the lower right corner. Now we have to carry out similar steps for the Cloud for Customer Logistics communication arrangement. We are still in the Communication Arrangements app. Select New  and choose the Logistics - Cloud for Customer Integration scenario from the list. Select Create. On the details screen, assign again the communication system.  Have a look at the Inbound Services section. This time we will use some inbound services. However, we don’t need to adapt any settings of them. Let’s have a look at the Outbound Services. First of all, let’s get an overview again. As you can see from the inbound and outbound services, this communication arrangement contains many services for different objects, to actually fulfill the whole demo scenario of this video series. An exception is only the product or material replication Because the latest integration flow, that we use, expects a message based on the SOAP protocol, while the material service of this communication arrangement is still using IDoc. That’s why we have configured the separate Product Integration communication arrangement and we deactivate the material service at this place. The next service is one, that we will use: It is the Notify Sales Quote or Opportunity of Follow Up Documents to C4C. This is still nowadays based on IDocs. And the path that is pre-delivered here, matches the default path of the integration flow. So, we can leave it as it is.  And for the business partner services the pre-delivered values match as well. So, we can quickly go over them and finally save the communication arrangement. This concludes the configuration of SAP S/4HANA Cloud.