Cloud Integration acts as the middleware between SAP S/4HANA and SAP Sales and Service Cloud Version 2, responsible for "translating" and forwarding messages between the two systems. This can be achieved by utilizing prepackaged integration flows from the integration package SAP Sales Cloud and SAP Service Cloud Version 2 Integration for Master Data with SAP S/4HANA, which was copied to the workspace earlier in this course.
This lesson focuses on configuring and deploying the relevant integration flow for replicating products from SAP S/4HANA to the cloud CRM. Please note that this lesson only covers the replication of products, not the confirmation back, as this is not necessary for the scenarios demonstrated in this course.
Video: Configure and Deploy the Integration Flow
The following video shows how to set up and deploy the integration flow in the demo environment. The upcoming sections provide a more detailed explanation of the configuration steps.
Configuration in Detail
To configure the integration flow, navigate as follows: Design→Integrations and API→Package "SAP Sales Cloud and SAP Service Cloud Version 2 Integration for Master Data with SAP S/4HANA"→Artifacts Tab→search for the integration flow "Replicate Product from SAP S4HANA"→choose the three dots menu→Configure
Sender Tab
The sender tab collects all necessary information related to the sending system, which, in our case, is SAP S/4HANA, as indicated in the Sender dropdown. The Adapter Type tells you that the incoming message is sent via the SOAP protocol. While these two dropdown fields are fixed and cannot be changed, the following fields are editable:
- Address: The path where the Cloud Integration runtime listens for incoming messages. However, this is not the full path. Because of the Adapter Type SOAP, the final path of the deployed integration flow will begin with cxf. It’s best to obtain the actual full endpoint of the integration flow during runtime from the deployed integration flow in the Manage Integration Content section of the Monitor area.
- Authorization: Although you can select Client Certificate here and upload a certificate, the recommended method is to use User Role (the default is ESBMessaging.send), which is more flexible and still supports different authentication methods, including client certificates. It delegates sender authentication to SAP BTP. This was explained earlier in the course.
In the demonstration, the address was left unchanged, and the Authorization was set to User Role to use the previously created Service Key for authenticating SAP S/4HANA.
Receiver Tab
The sender tab collects all necessary information related to the receiving system, which in this case is SAP Sales and Service Cloud Version 2. The Receiver name CNS stands for Cloud Native Solution. After processing the message, the integration flow uses an HTTP adapter to forward the message to the cloud CRM, which requires the following details:
- Address: In addition to the hostname, the address is predefined and corresponds to the endpoint where SAP Sales and Service Cloud Version 2 listens for messages in this integration scenario.
- CNS-Host: The hostname of your SAP Sales and Service Cloud Version 2 system.
- Authentication: The preferred authentication method, especially for production systems, is Client Certificate.
- Private Key Alias: Specifies which private key pair from the key store to use. If you leave the field blank, the Cloud Integration’s client certificate (sap_cloudintegrationcertificate) is used. However, you can also specify that name explicitly so that anyone reviewing the configuration knows which certificate is to be used and the field has not been overlooked.
More Tab
The More tab includes additional options that may vary between different integration flows.
- Custom Exit: Can be used to implement custom processing logic. It requires an extra integration flow where the custom logic is placed. However, this is beyond the scope of this course.
- Default S4 ID: If this field is set to true, the External ID will be automatically set equal to the Internal ID, unless a specific External ID is predefined in the message by SAP S/4HANA.
After configuring the parameters, you can deploy the integration flow. It will then be available under Monitor→Integrations and APIs→Manage Integration Content, where you can also view the final runtime endpoint as shown in the following screenshot.
