Name: SAP Sales and Service Cloud Configuration Part 2: Integrating SAP Sales and Service Cloud with SAP S/4HANA Cloud using SAP Cloud Integration
Uploaded: 2023-6-20
Duration: 719 s
Description: The configuration process for SAP Sales and Service Cloud is also shown using two videos. In this second part, we are going to cover integration settings like communication system and arrangements, as well as the necessary ID mappings.

Share feedback

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

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Choose your subscription

Manage your subscription

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div><div><div>The configuration process for SAP Sales and Service Cloud is also shown using two videos. In this second part, we are going to cover integration settings like communication system and arrangements, as well as the necessary ID mappings.</div></div></div></div></div></div>

SAP Sales and Service Cloud 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 Sales and Service Cloud Configuration. In this video, we will concentrate on the connectivity settings, that means creating a communication system, configuring communication arrangements, and finally, we will maintain some ID mappings manually that are necessary for our kind of setup. Let's start with the communication system. Navigate to the Administrator Work Center, view general settings, open communication systems, and create a new one. First of all, we have to enter an identifier for the communication system. This is not yet the ID that will be used to address the system inside of Exchange Messages. It's just the name that will be shown on the UI. You could also enter S4 test here, for instance. However, it's quite common to use the logical system ID, and we will follow this approach. Should we have a look where to get this ID from? No problem. Log in to your S4HANA Cloud Web UI and open the Communication Systems app. Find the entry that fits the hostname of your S4HANA Cloud system. Comparing with the hostname in your browser's address bar, you will usually find a dash API as part of it. Copy the system ID. If you select the entry, you can see further details, like the SAP client, under RFC settings. Back on the new system screen, we set SAP Business Suite to Yes, and enter the hostname of our cloud integration runtime. Make sure you copy the runtime, that means the worker node hostname and not the web UI hostname. It's the same procedure as earlier during the communication system setup within S4HANA Cloud. For the system access type drop-down, we can only choose Internet. The technical contact data should be filled according to whom to contact in case of questions or problems with the system integration. For our demo, we leave it empty. Finally, we have to fill the technically relevant system ID fields. Because our target system is a cloud system, we enter the same system ID for all three ID fields as system instance ID, business system ID and iDoc logical system ID. The preferred application protocol is 5, web service and the SAP client is 100, as we have seen previously. Then we can save the system and activate it. In the next step, we are going to set up the communication arrangements. For the desired scope, we need four communication arrangements. Material Replication, Business Partner Replication that also includes relationships, external pricing and the sales quote follow-up document creation, including quote update notifications. Let's start with the Material Replication. We start again on the General Settings screen. This time we choose communication arrangements and select new. We search the list of available communication scenarios for material replication from SAP Business Suite. On the next screen, we choose our previously created communication system and select SAP On-Premise Integration from the Coatless Mapping drop-down. This ensures that the codeless mappings that we have maintained earlier are applied for all messages that are sent through this communication arrangement. The next screen gives an overview on the inbound and outbound communication related settings. Let's start with outbound settings on the right hand side. We can see that a confirmation service is offered. What is a confirmation service? Confirmation services are typically offered in asynchronous replication scenarios to inform the original Sender system that a certain object has been received and what ID has been assigned inside the receiving system. If the sender system does not need to know what ID has been assigned in the receiving system, these services can be disabled. As SAP Sales and Service Cloud shall only receive materials from S4HANA, and S4HANA does not need to know the assigned ID, we can disable the outbound servers. That's it for the outbound direction. For inbound communication, we change the authentication method to user ID and password. Keep in mind to use client certificate for production environment and everywhere else whenever you can. The user ID in the field below has been generated based on the communication system ID. When selecting the Edit credentials button, you can enter the password for the communication user. Please note that although the password is maintained on communication arrangement level, it is valid for all other communication arrangements that belong to this communication system. The user ID and password from here must also be maintained in SAP Cloud Integration for the security material that will be used for communication towards SAP Sales and Service Cloud. After doing that, we can navigate to the next page and finish the wizard. That concludes the configuration of the first communication arrangement. Let's continue directly with the next one. Select New. On the communication scenario screen, search for business partner replication from SAP Business Suite. On the next screen, we assign the system ID and code list mapping group, as we did before. On the screen with in and outbound communication settings, we have to do some more steps this time. Let's start on the left-hand side with the authentication method. Choose user ID and password. Keep in mind that the password does not need to be maintained again. Then we continue on the right-hand side. This time, we keep the outbound communication enabled and let SAP Sales and Service Cloud confirm received business partners. This way, S4HANA Cloud will be aware of the assigned business partner IDs. For authentication in outbound services, we want to use SAP Sales and Service Cloud's client certificate. So, the setting is already correct. The certificate should have been downloaded during the cloud integration configuration as tenant certificate from the certificate's Work Center view. Alternatively, you could download it here. Then we have to define the final endpoint that the outbound service should address. We can do this on the Advanced Settings screen. The Advanced screen opens with the Inbound Services tab. Here you can see the final endpoint of inbound services again and enable and disable single services. We don't replicate business partner attachments, hence we disable the first servers. Then we continue on the outbound tab where we can enter the path where the integration flow is listening for the confirmation messages on SAP Cloud Integration. After that, we can select Next and see the review of all settings. If everything looks good, we can finish the guided activity. The next communication arrangement is the pricing, select new once more and search for pricing and sales quote follow-up scenario, continue as usual until we reach step 3. This communication arrangement only offers one outbound service that is interestingly showing up on the left-hand side. Anyway, we choose Edit Advanced Settings and enter the path of the pricing integration flow. Finish the guarded activity, and go on with the final one, select new. It is creation of sales quotes follow-up document in SAP Business Suite. Again, continue as usual until we reach step 3. This communication arrangement has again multiple inbound and outbound services. The inbound services can be used to update the status of sales quotes from S4HANA Cloud. Choose user ID and password as authentication method, as we did earlier for inbound services. The outbound services are ready from authentication perspective, we only need to maintain the path. Here we can disable the attachment service first, and then select the Create Sales Quote service and enter the path. That concludes the communication arrangement setup. With the communication arrangements done, we have finished another big configuration topic. The last piece of configuration is the maintenance of ID mappings. Navigate to the Administrator Work Center. View ID Mapping for Integration and choose Edit ID Mapping for Integration. Here we have to select two filters. The first is the Object Type, for that we want to maintain the ID Mapping. In case you miss entries here, you need to go back to scoping, and check if all necessary scoping elements have been selected. Alright, let's go ahead and choose ERP product categories. The second mandatory filter is the System Instance ID, as you can integrate with multiple external systems, where each system could have its own IDs. We need to select for which system we want to maintain the ID mapping. We choose RS4 system and select Go. Now we can see all ERP product categories that are currently available in SAP Sales and Service Cloud with their internal IDs. For this demonstration, we will map only a single product category that belongs to the sample material that we will replicate later. The product category we are looking for is Trading Materials. The easiest way to find it might be filtering the Description column. Then, we enter the respective S4ID of the Product category as External ID, and select Save. After that, choose the next object type, from the Mapping off drop-down, ERP Sales Organizations. Don't forget to remove all column filters, or directly enter a new filter. For this demo, we map to sales organizations. Aspen Bicycles, Inc. gets mapped to the S4 US Sales Org 1710. And Aspen Germany gets mapped to the German S4 Sales Org 1010. Save again, and choose the last object type's ERP plans. Depending on your configuration or the use case, plant data might not be maintained in S4 or needed on the sales and service cloud side. In the demo environment, it is maintained, so we have to maintain the ID mapping for it. Again, we have to maintain two entries in Sales and Service Clouds, one plant in the US and one in Germany. The respective plants have the same IDs in S4HANA as the sales orgs from the previous step 1710 and 1010. Select Save one more time and we are done. That concludes the ID mapping and also the SAP Sales and Service Cloud configuration as a whole. See you in the next video.