Configuring All Systems for Business Partner Confirmation Messages

The following video demonstrates how to set up all systems for the business partner confirmation message, and the subsequent sections describe the steps.

By completing these configuration steps, you have successfully enabled the confirmation message for Business Partners. All business partner messages sent from SAP S/4HANA to SAP Sales and Service Cloud Version 2 after that will be confirmed with a message back to SAP S/4HANA.

In SAP Sales and Service Cloud Version 2, enable confirmation through the Communication Configuration under Asynchronous Outbound Configuration.

1. Navigate to Settings→All Settings→Integration card→Communication Configuration
2. Search for the configured version of the Communication Configuration Integrate Master Data with SAP S/4HANA
3. Make sure the service Confirm Business Partner Replication to SAP S/4HANA is listed under Asynchronous Outbound Configuration. If it isn’t there, add it using the button with the magnifier and the plus icon as shown in the following screenshot.

The following screenshot displays the Communication Configuration with the two services for receiving business partner and sending the confirmation highlighted.

Pay attention to the naming convention. The services and their corresponding integration flows are always named from the cloud CRM’s perspective:

• Replicate Business Partner from SAP S/4HANA
• Confirm Business Partner Replication to SAP S/4HANA

Since business partners can also be replicated from the cloud CRM to SAP S/4HANA, you must be careful not to select the wrong services. If the service name was Replicate Business PartnertoSAP S/4HANA or Confirm Business Partner ReplicationfromSAP S/4HANA, you would be configuring the services for the opposite direction.

Finally, you should remove all outbound services that you don’t use to prevent errors caused by outbound messages that cannot be delivered to the target system. Please note that we do not configure the service for relationship confirmation.

In Cloud Integration, the integration flow Confirm Business Partner Replication to SAP S4HANA must be configured and deployed.

1. Navigate to Design→Integration and APIs
2. Select the package SAP Sales Cloud and SAP Service Cloud Version 2 Integration for Master Data with SAP S/4HANA and navigate to the Artifacts tab
3. Configure the integration flow Confirm Business Partner Replication to SAP S4HANA

Configure the integration flow with the following parameters:

• Sender tab: Ensure that the Authorization is set to User Role.
• Receiver tab:
  • Proxy Type: On-Premise
  • This instructs Cloud Integration to send data through the Cloud Connector
  • Address: The hostname and port must be configured according to the Cloud Connector system mapping.
  • The protocol specified here must always be plain HTTP. The actual protocol used for the communication within the customer network (for example, if HTTPS is used) is managed by the Cloud Connector based on the system mapping configuration.
  • Authentication: The demo uses Basic authentication for communication with SAP S/4HANA and references the user credential S4-COMM-USER, which was created earlier in the course’s preparatory unit.
  • Remember to use certificate-based authentication whenever possible, especially in production environments.

The following screenshot displays the finished configuration of the receiver tab.

In SAP S/4HANA, an additional web service must be activated to receive the business partner confirmation message. This can be done in the SOA manager.

1. Run transaction SOAMANAGER.
2. Navigate to Simplified Web Service Configuration.
3. Search for the service definition: BUSINESSPARTNERSUITEBULKREPLI1.
4. Enable the preferred authentication method for the service.
5. Since the demo uses Basic authentication, the cell in the User Name/Password (Basic) column was enabled.
6. Save the change.

The following screenshot displays the relevant setting in the Simplified Service Configuration in the SOA manager.

After activating the preferred authentication method and saving the change, the glasses icon becomes enabled. You can use it to view details of the web service definition, such as the External Name or the Access URL.

• The External Name helps to confirm you’ve chosen the correct web service. There was also a service with a very similar name, but its name ends with a "C" instead of "1". The "C" might suggest it relates to confirmation, but it actually stands for the "C" in "Replicate".
• The Access URL shown here usually won’t exactly match the URL in the integration flow because the system name and port mapping of the Cloud Connector need to be considered. However, the path should remain the same.