Identifying the Involved Systems

Objective

After completing this lesson, you will be able to identify the involved systems and get an overview of the system landscape

Involved Solutions

Before we dive deep into the integration setup, let's clarify some details about the solutions this course covers.

SAP Sales Cloud Version 2 / SAP Service Cloud Version 2

SAP Sales Cloud Version 2 and SAP Service Cloud Version 2 are two variants of SAP's next-generation, cloud-based Customer Relationship Management (CRM) solution.

They are successors to SAP Sales Cloud and SAP Service Cloud, which were previously known collectively as SAP Cloud for Customer.

While they have different names based on the subscribed focus area (Sales or Service), they share the same technology stack and can function as a single system when both areas are utilized.

Screenshot of SAP Sales and Service Cloud Version 2 System

You will find resources that refer to both solutions with the combined name SAP Sales Cloud and SAP Service Cloud Version 2 (for instance, the integration package SAP Sales Cloud and SAP Service Cloud Version 2 Integration for Master Data with SAP S/4HANA). Please note that this combined name refers to Version 2 for both solution areas: Sales and Service. It does not refer to the previous version.

In this course, we will refer to them collectively as SAP Sales and Service Cloud Version 2, or simply cloud CRM, to enhance readability.

Note

This course focuses on Version 2 of SAP’s cloud CRM solution. There is a separate course for the previous version that you can find here.

Most of the time we spend in this system will be in the administrative area, the System Settings. The following screenshot shows the entry via the User Menu and the All Settings tab. The displayed cards are a compilation of the most important settings that we will be navigating. The search bar at the top helps to quickly find the correct settings using keywords.

Screenshot of the most important system settings in SAP Sales and Service Cloud Version 2.

Cloud Integration

Cloud Integration is SAP’s cloud-based integration platform and the core integration capability within SAP Integration Suite that enables seamless, secure connectivity between cloud applications, on-premises systems, and third-party solutions. It provides access to pre-built integration content and offers tools for running and monitoring that, including error handling and versioning functionality, to ensure reliable data exchange across complex enterprise landscapes.

Cloud Integration system screenshot

SAP Integration Suite is a service that runs on the SAP Business Technology Platform (SAP BTP). Along with the Cloud Integration capability, it comprises two main components.

  • The SAP Integration Suite application offers a WebUI for managing integration content, including integration packages and flows.
  • The Cloud Integration / SAP Process Integration Runtime runs as an instance in the Cloud Foundry environment and performs the actual message processing of deployed integration flows.

Note

Please note that the WebUI and the runtime have different hostnames. This distinction is particularly important when setting up integrations from other systems to Cloud Integration. Messages must always be sent to the runtime hostname, which can be easily obtained from a deployed integration flow or a service key. This will be illustrated later.

Cloud Integration has also been renamed in the past. Its former name was SAP Cloud Platform Integration, often abbreviated as CPI, which you will find in many online resources on the internet, such as blogs. In this course, we will abbreviate Cloud Integration as CI.

SAP S/4HANA

SAP S/4HANA is an Enterprise Resource Planning (ERP) system and the successor to SAP ERP/ECC. There are several offerings of SAP S/4HANA:

  • SAP S/4HANA, without any additional suffix, refers to the on-premise suite with SAP GUI access that provides the full flexibility associated with SAP ERP/ECC.
  • SAP S/4HANA Cloud Private Edition is similar to the on-premise suite but is hosted by SAP or certified partners on dedicated infrastructure. Access to SAP GUI remains available.
  • SAP S/4HANA Cloud Public Edition is an entirely cloud-based SaaS (Software-as-a-Service) solution that SAP hosts and can be fully operated from a web browser. SAP GUI is not available, and configuration works differently compared to the on-premise suite and cloud private edition.

This course focuses on SAP S/4HANA with on-premise functionality, including SAP GUI access, which means either the full on-premise or the private cloud offering.

Note

If you are using SAP S/4HANA Cloud Public Edition, the integration with SAP Sales and Service Cloud Version 2 is managed and operated by SAP. In this case, this training does not apply!

S/4HANA and SOAMANAGER screenshots

SAP S/4HANA - Important Transactions

In contrast to the cloud-based solutions, where you can navigate from screen to screen with a user-specific navigation menu, you must remember transaction codes for working with SAP S/4HANA in SAP GUI or create a list of favorites.

The following list serves as a reference, containing some of the most commonly used transactions during the integration setup to SAP Sales and Service Cloud Version 2:

  • SPRO: Access to Customizing
  • DRFIMG and DRFF: Setup of the Data Replication Framework and filters (the latter opens in a browser window)
  • DRFOUT: Send data via Data Replication Framework
  • SOAMANAGER: Web services configuration (browser window opens)
  • SRT_MONI, SRT_UTIL: Monitoring of web service-based communication
  • WE20, WE21, SM59: Configuration of IDoc communication - Partner Profiles, Ports and RFC Destinations
  • WE02, BD87: Monitoring of IDoc-based communication
  • BD64: IDoc Distribution Model
  • BP, MM##, VA##: Display or edit Business Partners (BP), Materials (MM), or Sales Orders (VA); where ## stands for 01 (create), 02 (edit), or 03 (display)
  • STRUST: Manage Certificates
  • SA38 / SE38: Run ABAP programs*, for example, RCOD_CREATE_CONNECTIVITY_SIMPL to launch the connectivity setup report
  • COD_INT_MENU: Area menu for integration with SAP Sales and Service Cloud, containing entries for several useful transactions

* ABAP programs are used to implement business logic, data processing, and user interfaces within the SAP environment. They are also referred to as reports. Not to be confused with analytical reports.

Note

To make the most of it, you should consider creating your own transaction list, adding your own hints and remarks when starting to work with transaction-based systems.

Most transactions or entries from area menus start ABAP programs that can also be executed directly from transaction SA38 or SE38. Hence, these are important transactions that allow you to run or search for ABAP programs flexibly.

System Landscape

The following graphic illustrates the landscape comprising the three main systems for integrating SAP Sales and Service Cloud Version 2 with SAP S/4HANA using Cloud Integration.

System Landscape - Simple Overview

SAP Sales and Service Cloud Version 2 typically functions as the new system that is integrated with the existing landscape. In this scenario, the SAP S/4HANA system acts as the leading system, and Version 2 must adapt to it along with all its settings. After setting up the new system’s configuration according to the leading system, an initial load is usually required to load all relevant data into the new system. Then, normal operation begins with exchanging newly created or changed data. This is sometimes referred to as delta load, although this sounds like a manually triggered synchronization of data, it usually refers to data that is exchanged in real-time after changes.