Name: SAP Sales and Service Cloud Configuration Part 1: Integrating SAP Sales and Service Cloud with SAP S/4HANA Cloud using SAP Cloud Integration
Uploaded: 2023-6-20
Duration: 635 s
Description: The configuration process for SAP Sales and Service Cloud is also shown using two videos. In this first part, we are showcasing how to do the project scoping and fine tuning.

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><p>The configuration process for SAP Sales and Service Cloud is also shown using two videos. In this first part, we are showcasing how to do the project scoping and fine tuning.</p><p></p></div></div></div></div></div>

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

The configuration of SAP Sales and Service Cloud is split into two videos. In this video, we will start with the project scoping and fine-tuning. The second part covers integration settings like communication system and arrangements, as well as the necessary ID mappings. In order to make the relevant integration settings available, we have to adapt the project scoping in SAP Sales and Service Cloud. Go to the Business Configuration Work Center, View Implementation Projects. Select the row with the implementation project. Choose the Edit Project Scope action, navigate through the guided activity until you reach step 3, Scoping, and navigate down the tree by selecting Communication and Information Exchange, Integration with External Applications and Solutions. Depending on the desired integration scenarios you have to enable different points. In our case we choose Integration of master data, integration into sales, service and marketing processes and the last one we need is integration with SAP ERP. You may now ask why do we have to select SAP ERP? We are integrating with SAP S4HANA Cloud. That's a valid question. The answer is that some parts of the ERP integration are used by S4HANA as well. Most prominent feature is the ID mapping. If you forget to flag this point now, you will not be able to manually assign external ideas for some objects later. After you have checked the three elements, select Next to navigate to the fourth step, Questions. The question screen looks similar like the scoping, with the difference that the tree now only contains the previously enabled items. Navigate again to Communication and Information Exchange, Integration with External Applications and Solutions. Now we can define which integration scenarios we need by answering questions for each element accordingly. Integration with SAP ERP can be ignored on this screen. We only needed to enable it for scoping. The first two relevant questions are in the integration of master data section. We want to replicate business partners and products from S4 to our cloud solution. We search for the group of business partners and make sure that Do you want to replicate business partners from an external application to your cloud solution is checked. Then we search for the products group. Make sure that Do you want to replicate products from an external application to your cloud solution is checked. That's it for the master data scenarios. The next questions are in the sales processes section. As we want to enable the Sales Quote Follow-up Scenario, we have to search for the Sales Quotes group, and make sure that the question for the follow-up creation itself, as well as the determination of prices by an external application is checked. That's it for the process integration. When selecting Next this time, a question pops up, how to deal with questions that we have not reviewed so far. Here we can choose, accept pre-selected answers, finally, we can select finish and leave the scoping by selecting close. In the next step, we have to maintain necessary fine-tuning settings for our integration scenarios. In our case, we need to maintain a new document type for sales quotes that will support the external pricing and external follow-up document creation. Maintain code list mapping to translate some technical codes, so that Sales and Service Clouds and S4 Clouds can talk to and understand each other, and maintain some details for the external pricing. Let's start with the document type. We can enter the fine-tuning by opening the activity list. Search for the Sales Quotes activity, open it and choose Maintain Document Types. Here we add a new document type that will support the external pricing and follow-up document creation. Enter a new technical document typecode, give a reasonable name and mark the external pricing checkbox that has created a new document type that we could already use internally in SAP Sales and Service Cloud. Now we have to define how this document typecode will be sent to S4HANA Cloud when the pricing is requested or the follow-up document creation is triggered. This can be done in another fine-tuning activity, Coatless Mapping. It's usually sufficient to search for code, and you should find it. Inside the activity, we choose Maintain Coatless Mapping. In case you're not familiar with Coatless Mapping, let's gather a quick overview. Coatless Mapping is used when technical codes, like our created sales quote document type code, do not match between sales and service clouds and an external application. They're usually represented to the user as drop-downs or sometimes as value-helps. As long as they're only used internally in sales and service clouds, there is no need to maintain a code list mapping. But if they're used in an integration context, that means a code value is part of a message, to or from an external system. Then the mapping might be necessary in case the codes are different, and in this case, you need to know the technical name of the data type behind the code list. We're looking for the document type. The technical name is Business Transaction Document Processing Typecode. Usually you can search by parts of the name with wildcards. The second table contains the Mapping Rule. Here you can define that all internal and external codes are equal, which is the default for many code lists. In our case, the rule is already set to map individual codes, and we can concentrate on the third table, where the internal codes and their external mappings are listed. This list contains all document types for all business objects. For a better overview, let's filter the description for order with wildcards around it. Now we can see some other document types that already exist and are mapped equally at the moment. Let's add our previously created document type to this list. As external code, we do not maintain ZTA. Instead, we maintain TA as the external code, and this is used for standard orders in our S4 HANA cloud system. That means when we send our sales code to S4, it shall arrive as standard order. This is the reason why we have used the term order request in its name. Furthermore, we also want to map the standard order OR to external TA. In order to change it, we have to remove the entry first, and add it again, as existing mappings are read-only. Whenever we have the same external code multiple times for different internal code, we have to tell the system which entry should be used, when a message is coming in that contains such ambiguous code. That's why we flagged the standard order entry as inbound default. Alright, we have added our new document typecode and maintained the code list mapping so that it is sent to S4 as a sales order. This ensures the correct flow for the follow-up document creation and external pricing calculation. Furthermore, in case we would replicate orders of type TA from S4 to Sales and Service Cloud, they would be stored as standard orders. Please keep in mind that the values shown here are only examples and other systems might need different approaches. Now we can leave the code list mapping. Keep in mind that CoatList mapping is not only for mapping, it is also the maintenance of the CoatList itself. Keep in mind that if you connect SAP Sales and Service Cloud to an existing environment, you might need to delete some pre-configured values that SAP Sales and Service Cloud is shipped with, in case there is no equivalent in the existing system. Do not try to solve all problems with coatless mapping. Ok, that's enough for coatless mapping, let's take care of the pricing settings that we need for the external pricing. Another way of opening fine-tuning activities is from the Business Configuration WorkCenter, View Overview. Here we can search for the activity as well. Let's search for pricing and choose external pricing. First, we will define the external pricing procedure and the step details. This must be done according to the settings in S4. We will have a brief look at where to find some pricing details in S4 right after this. Next, we have to define external condition types, again according to the values used by S4. In this system, some have been defined already. We can already say that this list is incomplete. That's a good chance to show you what happens in case some values are missing. In your project, that should of course not be the case. Let's have a brief look at where you can find some pricing details in SAP S4 HANA Cloud. Open the Manage Your Solution app and choose Configure Your Solution. Search for Pricing, and select the pricing item. In the new table on the right hand side, select the Set pricing procedure step. Here you can see all the fine pricing procedures and nearly at the end of the list, we can find the one that we have maintained in SAP Sales and Service Clouds. By navigating to the procedure's control data, we can even see more details like the condition types that we have maintained as well in SAP Sales and Service Cloud. As mentioned, this was only a brief outlook to pricing configuration in SAP S4 HANA Cloud. Other important steps, like the determination of the pricing procedure and so on, can be found there as well. If you're not familiar with the details of pricing setup, you should consider talking to a functional expert or reaching out to the system owner for further contacts. That concludes the first part of SAP Sales and Service Cloud Configuration. See you in the next video.