Monitoring the Data Replication Process

Objective

After completing this lesson, you will be able to monitor end-to-end master-data replication across SAP S/4HANA Cloud, SAP Cloud Integration (CPI), and SAP Commerce Cloud—using monitoring tools and logs to detect, correlate (message/correlation IDs and timestamps), diagnose, and resolve replication issues.

How to Monitor Data Replication in SAP S/4HANA Cloud

Data Monitoring is mandatory in an integrated environment, to ensure the expected system behavior and that all data has been successfully transferred. Typically, each system has its own monitoring capabilities. To monitor the complete data replication, you must check expected system behavior and data transfer across the business process concerned, end-to-end. For example, for the process to fulfill asynchronous order management involving SAP S/4HANA Cloud and SAP Commerce Cloud, it must be monitored in both these systems. However, here, you must also monitor within Cloud Integration which acts as the middleware between SAP S/4HANA Cloud and SAP Commerce Cloud.

Let's assume that SAP S/4HANA Cloud is the source system in an integrated environment for a business process. Then, you start to monitor the data replication there. The following demonstration shows you how to monitor the data replication within the S/4HANA Cloud system.

How to Monitor Data Replication in Cloud Integration

You need to check expected system behavior and monitor data replication in Cloud Integration, as it's part of the integrated environment for a business process. Assuming SAP S/4HANA Cloud is the source system in an integrated environment connecting to SAP Commerce Cloud, then you monitor data replication in Cloud Integration after monitoring data replication in SAP S/4HANA Cloud, and before SAP Commerce Cloud.

Monitor Data Replication in SAP Commerce Cloud

Master data replication from SAP S/4HANA Cloud through the SAP Cloud Integration to SAP Commerce Cloud can be monitored in the SAP Commerce Cloud Backoffice Integration UI Tool cockpit. In this UI Tool cockpit, you can see all the Inbound and Outbound Integration API calls between SAP S/4HANA Cloud and SAP Cloud Integration.

We'll use the example of the replication of Product Master Data to see how this works. First let's check the Product Integration API Inbound calls in the SAP Commerce Cloud Backoffice.

  1. Log on to the SAP Commerce Cloud Backoffice as an administrator.
  2. In the Backoffice Administration Cockpit, choose the Cockpit dropdown menu from the top left corner, and choose Integration UI Tool.SAP Commerce Cloud Backoffice Administration Cockpit screenshot with the menu open to Integration UI Tool and a Products list showing one item PSR 1090.
  3. In the Integration UI Tool cockpit, choose the Advanced Search button (telescope icon) to bring up the Advanced Search area.
  4. In the Integration Key field, enter PSR. In the Type field, enter InboundProduct2 or any name you give to the integration object. In this case, it's InboundProduct2. In the Status field, choose Success from the dropdown.SAP Integration UI Tool Inbound screen showing filters: Integration Key PSR, Type InboundProduct2, Status Success, and the Search button.
  5. Choose the Search button. You’ll see the Product Integration API inbound calls from the SAP Cloud Integration platform.
  6. Choose an entry from the search result list. You’ll see Inbound Request Details in the editor area at the bottom.Screenshot of the SAP Integration UI Tool Inbound view showing a list of inbound requests with one row selected and the InboundRequest details panel open, highlighting a payload link.

    Hint

    In the Inbound Request Details, you’ll see detailed information about the Integration API call. For example: the HTTP method; the exact time; authenticated user of the API call; integration key extracted from the payload; and the whole request payload, if success payload retention is enabled. You can double-click the Request Payload field to open a payload file popup. All the Integration API request payloads are stored in SAP Commerce Cloud as a media item. The media file can be downloaded from the popup to understand the actual request payload sent from the client applications. For example, sent from SAP Cloud Integration.SAP Integration UI modal showing a payload’s details with prominent Upload and Download buttons.

    However, error payload retention is more important for troubleshooting as you can double-click the Errors field to see the exact Error Code and Error Message.

    In SAP Commerce Cloud, the Integration API inbound and outbound monitoring needs to be enabled in the manifest.json, or properties file, in your SAP Commerce Cloud project repository. You can also enable the monitoring features in the Cloud Portal by configuring the API service properties.

    Screenshot of a GitHub manifest.json file (main/core-customize) showing JSON settings with monitoring-related keys highlighted.

    Now that the high-level data flow looks good, we can confirm the successful data replication from SAP S/4HANA Cloud to SAP Commerce Cloud.