Configuring SAP S/4HANA

The integration setup of SAP S/4HANA consists of some automated and some manual configuration steps. The automated steps are carried out by the so-called connectivity report that is designed like a guided activity and asks for the desired integration scope. In addition to that, some manual steps are required, and the automatically generated settings should also be reviewed, of course. Moreover, the configuration consists of a technical part and a functional part.

The following list gives an overview of the most important steps. Depending on the usage of the SAP S/4HANA system (training, productive, and so on), some steps might be carried out already, or may not be necessary.

These steps will be discussed in more detail in the following sections. Some of the steps belong to the Basis configuration of the system, which is treated as given and therefore is only covered briefly.

Executing the connectivity report and configuring the data replication framework are two major milestones for setting up the integration with SAP Sales and Service Cloud. However, there are some additional tasks that need to be carried out as prerequisites. They might be optional or already carried out, depending on your system configuration and usage.

Activate Business Configuration Sets (BC Sets)

Note

In case you are not familiar with BC Sets: They are collections of configuration settings and customizing objects that can be exported and imported as a single unit. They are used to transport and store configuration settings for various business scenarios, allowing for easy distribution and maintenance of configuration settings in different systems.

The BC Sets C4C_INTEGRATION_CC and C4C_INTEGRATION_CS contain predefined client-specific (CS) and cross-client (CC) configuration settings. Activating the client-specific BC Set C4C_INTEGRATION_CS adds output settings for transactional documents, pre-defines a replication model for sending business partners via web services, and other settings (see the following screenshots). You should review the contained settings in detail (using for instance, transaction SCPR3 or SE80) and consider activating them depending on your needs. If you are following this course in a demo system, you should activate C4C_INTEGRATION_CS using transaction SCPR20.

Activate the Inbound IDoc Service Endpoint

If your integration scenarios require SAP S/4HANA to receive IDocs and you are not already using them, you probably need to activate the IDoc service endpoint using transaction SALE. You must carry out the following two steps under Basic Settings:

• Activate event receiver linkage for IDoc inbound
• Inbound SOAP for IDoc Register Service (transaction SRTIDOC)

  With the following parameters:

  Parameter	Value
  URI SOAP Application	urn:sap-com:soap:runtime:application:idoc
  Name of Web Service Definition	GENERIC
  Call Address (ICF Path)	/sap/bc/srt/idoc

Carry Out SSL Configuration (Certificate Management / STRUST)

Make sure SAP S/4HANA has the appropriate certificates maintained in transaction STRUST to allow connections from and to Cloud Integration.

The system supports multiple key stores, called PSE (PSE, Personal Security Environments) for different usages. They can be basically divided into two roles:

• When SAP S/4HANA initiates an outbound connection, hence it acts as client:

  The certificate list must include the root CA certificate for verifying the target's (Cloud Integration) server certificate. Moreover, if certificate-based authentication should be used, the PSE must contain a valid certificate as "Own certificate" issued by a CA that is trusted by the target (Cloud Integration).

• When SAP S/4HANA offers a service and receives an inbound connection, hence it acts as a server:

  The PSE must contain a valid server certificate matching the system's identity (domain) as "Own certificate".

For outbound connections, you can select which PSE is to be used in the configuration screens of the respective RFC destination (transaction SM59) or in the port definition of the consumer proxy (transaction SOAMANAGER). The following screenshot shows the configuration of an RFC destination in transaction SM59.

In the demo system, where the screenshot was taken, there are two relevant client PSEs: While the "DFAULT" PSE contains a valid client certificate, the "ANONYM" PSE doesn't contain an "Own certificate" (as seen in the earlier screenshot for STRUST). Both PSEs contain the necessary certificates in their certificate lists to trust Cloud Integration. If the shown RFC connection should use Basic authentication, either the "ANONYM" PSE must be chosen or the checkbox "Do not use certificate for logon" needs to be activated. Otherwise, if a PSE with a valid client certificate is chosen, the system would try to use it for authentication and

The connectivity report can be executed in several ways:

• Transaction RCOD_CONNECTIVITY (easiest way)
• Transaction SA38 → Program name RCOD_CREATE_CONNECTIVITY_SIMPL
• SAP Reference IMG → SAP Customizing Implementation Guide → Integration with Other SAP Components → Integration with SAP Sales and Service Cloud → Communication Setup → Automatically Generate Integration Settings for Data Exchange

The following video demonstrates how to execute the connectivity report and how to review some basic settings that the report applies.

The report asks for the following input parameters:

• Middleware to be used
• Desired integration scope / integration scenarios to be enabled
• Logical system, representing SAP Sales and Service Cloud (can be created during the report execution)
• Communication details for connecting to the middleware, such as hostname and credentials for Cloud Integration

Based on the specified parameters, the following settings are automatically created (find the transactions to review the settings in brackets):

• ALE / IDoc settings:
  • Partner Profiles (WE20)
  • Ports (WE21)
  • RFC Destinations (SM59)
  • Distribution Model (SALE / BD64)
• Periodically executed jobs for IDoc processing (SM37)
• Web service settings, such as consumer proxies for outbound connections (SOAMANAGER → Web Service Configuration)

The results of the connectivity report are displayed in the last step. If you would like to see them again, you can use transaction SLG1 and search for the program name RCOD_CREATE_CONNECTIVITY_SIMPL or the user who has executed the job. Depending on the selected scope, the result could look like this:

You can use the Data Replication Framework (DRF) to replicate master data such as business partners and products between source systems and target systems. Data is replicated to business systems that are assigned to outbound implementations of replication models.

The configuration of the replication models includes the receiver systems, assignment of outbound implementations, definition of additional parameters per outbound implementation, and the assigned languages.

The following video demonstrates the basic setup of the Data Replication Framework:

The Data Replication Framework can be configured using transaction DRFIMG. In the video, the following settings are being defined:

• Business System for the following Business Object Types, enabled for replication via services:
  • 194 - Product
  • 986 - Business Partner including Relationships
• Replication Model with the Outbound Implementations:
  • 194_3 - Outbound Implementation for Product via Services
  • 986_3 - Outbound Implementation for BP/REL via Services

These basic settings allow you to send products (materials) and business partners including relationships to SAP Sales and Service Cloud via web services (consumer proxies). The replication can be initiated via transaction DRFOUT and is part of a later unit.

Filter Settings of the Data Replication Framework

The Data Replication Framework allows you to filter segments of messages or define filter criteria to include or exclude instances of business objects completely. You can configure the filter criteria using transaction DRFF. Similar to the SOAMANAGER, the transaction DRFF starts a browser window where you can configure filters based on the defined replication models and activated business objects. The following screenshot shows the user interface for Business Partners:

Functional settings are only briefly mentioned here for the sake of completeness, as the current unit focuses on master data configuration settings. Transactional scenarios are discussed in a later unit.

By activating the BC Set C4C_INTEGRATION_CS, some basic functional settings are automatically defined, for instance:

• Output Types:
  • COD4: Order/Quote Replication
  • COD5: Contract Replication
• Processing Routines for Output Distribution via ALE

A good starting point for reviewing and adapting or configuring those settings manually is transaction NACE: