Setup for SAP S/4HANA Cloud Private Edition
This page explains how to connect SAP S/4HANA Cloud Private Edition to SAP Cloud ALM.
Currently, the following monitoring applications are supported for SAP S/4HANA Cloud Private Edition systems:
This page explains how to connect SAP S/4HANA Cloud Private Edition to SAP Cloud ALM.
Currently, the following monitoring applications are supported for SAP S/4HANA Cloud Private Edition systems:
The following video demonstrates the setup steps to set up Integration & Exception Monitoring for SAP S/4HANA Cloud Private Edition.
A textual step-by-step description for all setup steps is provided in the sections below the videos.
Monitoring for SAP S/4HANA Cloud Private Edition uses a PUSH mechanism to push monitoring data to SAP Cloud ALM.
Please note that it is not possible to use the Cloud Connector from SAP to establish the connection between your SAP ABAP on-premise system and SAP Cloud ALM.
The Cloud Connector acts as a reverse invoke proxy between the on-premise network and SAP BTP. This means after connecting the subaccount to the Cloud Connector the tunnel between SAP BTP and the on-premise landscape is triggered by the BTP destination service in the connected subaccount. The Cloud Connector is not designed to act in the opposite direction.
The connectivity from On-premise to Cloud is only possible for ABAP cloud systems, HANA Cloud databases, and specific SAP BTP services like K8s clusters. It cannot used for SAP BTP services like SAP Cloud ALM.
For more information see Cloud Connector FAQ > Features > "Can I use the Cloud Connector from on-premise to cloud for any protocol?"
It is possible to use other proxy solutions between your ABAP on-premise system and SAP Cloud ALM. If you do this please make sure to add the relevant URLs to the allow list for the proxy as described under Prerequisites > Network Prerequisites.
The data collection for the selected use-cases will be activated automatically. In general it is recommended to use the standard collection interval. Only for specific requirements, you are able to change the “Collection interval” for the different use cases. Please be aware that Business Process Monitoring is using a separate scheduler, therefore, this specific value cannot be changed.
After setting up the monitoring PUSH to SAP Cloud ALM in the managed service, the data collection will be activated automatically with default monitoring configurations.
You can adjust the monitoring setup within the monitoring application. Find more information on the configuration on the "Setup & Configuration" pages for the application.
After you connected your SAP ABAP system to SAP Cloud ALM, the ABAP system will keep sending data to the monitoring applications. To which ABAP system in LMS the monitoring data is assigned, will be determined by the LMS Id. If you perform a system refresh of your ABAP system, by overwriting it with a copy from another ABAP system, this assignment will be broken.
To avoid that the metrics will be assigned to the source of the copy rather than the actual ABAP system, you need to save and restore the tables containing monitoring setup information for SAP Cloud ALM.
SAP Cloud ALM configuration is integrated in post-copy automation (PCA) Introduction | SAP Help Portal.
Requirements are ST-PI 7.40 SP 27 (and correction note) and note 3501074 (System Copy: ST-PI CALM configuration)
If PCA is not used then two reports will support your system copy and system refresh:
/SDF/CALM_SYS_COPY
After a system has been copied to create a new system based on an already configured system the report /SDF/CALM_SYS_COPY can be used to delete the SAP Cloud ALM configuration. Connection to SAP Cloud ALM must be executed with /SDF/ALM_SETUP.
/SDF/CALM_SYS_REFRESH
As a preparation of a system refresh you can execute this report. It will create a Transport of Copies(ToC) with table content of SAP ALM configuration. You need to export this request and save it. After the system refresh you can import this transport request again.
To troubleshoot any issues with the setup or the data collection for SAP S/4HANA Cloud Private Edition, please follow the Troubleshooting for ABAP Systems page
Should this information not suffice to address your problem please open an incident.