Name: SAP Cloud Integration Configuration Part 2: Integrating SAP Sales and Service Cloud with SAP S/4HANA Cloud using SAP Cloud Integration
Uploaded: 2023-6-20
Duration: 641 s
Description: The configuration process for SAP Cloud Integration is split into two videos. In this second part,we configure and deploy all relevant integration flows.

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><p>The configuration process for SAP Cloud Integration is split into two videos. In this second part,we configure and deploy all relevant integration flows.</p></div></div></div></div>

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

Welcome to the second part of the SAP Cloud Integration Configuration. In this video, we'll configure and deploy all relevant integration flows. Before we start, let's come back to the scenario overview to get a better impression on what integration flows we need. For the Master Data part, we need 3 integration flows for messages from SAP S400 cloud to SAP Sales and Service cloud Material, Business Partner and Business Partner Relationship replication and 1 integration flow from Sales and Service cloud to S400 cloud for the Business Partner confirmation. For the transactional data, we have two integration flows that will be called from Sales Cloud. The Request Pricing and the Sales Quote follow up, in one intro with the other direction for the Sales Quote update. So all in all, seven integration flows. You will notice that we need to provide the same values most of the time. The values mainly depend on the direction of the integration flow. That's why we go object by object, and even more important, direction by direction. Back in our Cloud Integration tenant, we open a package and navigate to the Artifacts tab. Now we can see all integration flows of the package, and we need to find the ones that we want to configure. We start with the Material Integration Flow, Replicate Material from SAP Business Suite. To find it, you can use the filter. Once we have located it, we select the Actions button of its row and choose Configure. We start on the Sender tab. We can see that the sender is S4, and the adapter type is SOAP. Underneath, we can find the address. That's the path where S4HANA needs to send the material replication messages to. As mentioned earlier, the full path will contain a prefix. Here we could adapt the path in case this would be necessary. For instance, because we have another integration flow, that already listens on that endpoint. The first setting that we really have to change here is the authorization. Useral means that we need a user that needs to be created in the BTP Business Technology Platform cockpit first, and then needs a password or a certificate to user mapping assigned. Especially the certificate to user mapping is the best practice approach. In this demonstration, we will simply upload the client certificate from our S4 system here, and hence work around additional settings on BTP. Choose Client Certificate and upload the client certificate that we have downloaded earlier from S4. That's it for the Sender tab. Let's come to the Receiver tab. Here we would expect to see the settings for SAP Sales and Service Clouds, but we can only see some settings related to something with post exit. The reason is that the integration flow has actually multiple receivers. The post exit receiver can be used to enhance the integration flow with custom logic without using the ability to upgrade. We can simply choose our desired receiver, C4C, from the Receiver tab drop down. And then we see the expected configuration parameters, C4C host and the authentication details. That's actually all we need to maintain. Put in the host name of your SCP Sales and Service Cloud tenant. And for authentication, choose Basic and put the credential name in. Make sure that it's the credential name for sales and service clouds. After that, we can select Deploy with Save. Now pay attention to the bottom of the screen. A small message will be displayed that the integration flow has been successfully deployed. From that point in time, we could send data through it. The material integration flow was the first one that we have configured. Now let's continue with the two business partner integration flows that point into the same direction. We start again at the Out of Facts tab of our Integration Package and filter for Replicate Business. From the result list, we mark two integration flows, Replicate Business Partner from SAP Business Suite, and Replicate Business Partner Relationship from SAP Business Suite. This time we select the actions button at the top of the list and choose configure. That's the so-called mass configure feature. Unfortunately, it does not configure all integration flows at once automatically. It rather helps us in navigating between the selected integration flows and keeping a better overview. The parameters that we have to apply are the same as for the material flow. On the sender tab of the first integration flow, we change the authorization to Client Certificate, and upload the certificate from S4. On the Receiver tab, this time C4C is selected from the beginning, and we can directly paste the hostname of our Sales and Service Client tenant, and maintain the authentication details. Then we repeat these steps for the other integration flow, authorization, and the C4C details. Finally, we can select save all, and deploy all. That's it. Now we have the Business Partner Confirmation integration flow left, and now we have to pay attention, because this is the first integration flow that points in the other direction. Back in Cloud Integration we search for the integration flow, Confirm Business Partner Replication to SAP Business Suite. Do you see the description underneath the Integration flow title? It says Business Partner Replication from SAP Business Suite, because the confirmation integration flow belongs to the scenario of replicating a business partner from SAP Business Suite. This time we use the Configure button within the list entry. This time we have the C4C parameters on the sender tab because C4C is initiating the connection. That means after changing the authorization to client certificate, we have to upload the certificate of SAP sales and service cloud. Then we can come to the receiver tab, which is this time our S4 system. In the protocol hostname port field, we have to fill in the S4 web service endpoint. Pay attention that this endpoint contains Dash API in the hostname. You can look up the exact endpoints in the communication arrangement in S4. As the name of the field suggests, we also have to mention the protocol, and if necessary the port. The protocol is HTTPS, where the default port is 443. That means you could omit it. This time, we have to mention the client, which is 100 in our case, and then we come to the credentials for S4. Choose Basic and enter the credential name that contains the user and password for our S4 HANA system. After that, we can deploy the integration flow. Now we have completed the integration flow setup for our master data scenarios, and we have three left for the transactional scenarios. Let's begin with the two integration flows that point towards S4. That means the same direction as we have just configured. Filtering for document gives a good result list and we can mark Create Sales Quote Follow-Up Document in SAP Business Suite and request sales document data from SAP Business Suite, which is the pricing service, as you can see in its description. Then we go with the mass configuration by reactions, configure again, and repeat the known steps. Upload the Sales Client Certificate on the sender tab, and the Receiver tab. Paste the S4 protocol host port combination, fill the client, and change the basic authentication with the respective S4 credential name. Then we do the same for the second integration flow. Finally, select Deploy All, to deploy the two integration flows. We are nearly finished. Let's have a look at this slide for the last time. The last integration flow is for the update of the Sales Quote and Sales Cloud. From a receiver perspective, this is a special one. Let's see why. We are looking for the integration flow. Notify Opportunity or Sales Quote of follow-up document from SAP Business Suite. This time, do not jump into the configuration, instead select the integration flow to open it. This is how an integration flow looks like. On the left hand side, we can see S4 that sends an iDoc into our integration flow. On the right hand side, we can see two boxes with the headline C4C, and each having an arrow pointing to it. That's the receiver systems and channels. And it tells us that this integration flow can send data to two different endpoints depending on the implemented logic, which checks the document type. Are we receiving an update for an opportunity or a sales quote? And this is also reflected in the configuration. We will see it in a moment. Let's quickly configure the sender by uploading the certificate. Please pay attention that now S4 is the sender again. So, we have to upload the S4 certificate accordingly. Now switch to the Receiver tab, and have a look at the Receiver dropdown. This time, we do not only have a single C4C receiver. Instead, we have a C4C opportunity, and a C4C quote receiver. Although we are not planning to use opportunities in our scenario, we will configure both receivers for demonstration purpose, because some of the parameters are shared between them anyway, you will see. In the address field, we can see that the final endpoints are really different. However, we are targeting the same system, and hence we only need to enter the hostname of our Sales Cloud tenant once. Let's change the credentials, and then come to the quote receiver. And there we can see that the path is a different one, and the hostname has been taken over from the opportunity receiver. It's actually the same parameter. For the credentials, that does not work, and we have to enter the credential name here again. Now we can deploy the integration flow. That was the last integration flow that we need for our scenario, and hence that concludes the SAP Cloud's integration configuration.