-
Request for existing cases, user IDs, Portal navigation support and more
Request for existing cases, user IDs, Portal navigation support and more
This page gives you some hints when you get an error or run into a problem during the SAP Cloud ALM monitoring setup of ABAP on-premise systems.
The troubleshooting on the page can be used for the products:
When clicking on "Register" a synchronous call to SAP Cloud ALM is executed. If no LMS-Id is retrieved and displayed the registration was not successful.
There might be several reasons:
When executing /SDF/ALM_SETUP at least one HTTP destination is created. You can display them in SM59 (type G) with the prefix ZSDF_<your destination name>.
When you need proxy access with authentication a second destination ZSDE_ <your destination name> is created.
Don't manipulate the Path Prefix in SM59!
A connection check in transaction SM59 with HTTP status code 400 is normal. Everything else e.g. 401 (wrong credentials), 403 (forbidden), and 500 (error) is not normal.
You click on the "Activate Usecases" button and select a use case. However, when you save your changes the selection is not saved.
During the initial setup, you can specify in each client which data should be collected. However, SAP Cloud ALM is the leading instance. If the use case is deactivated after the initial activation in SAP Cloud ALM or in /SDF/ALM_SETUP, it can only be reactivated in the use case in SAP Cloud ALM.
The deactivation of the data collection from the ABAP system is always possible.
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?"
Data collection is triggered periodically by the scheduled job "CALM Scheduler <Setup name in /SDF/ALM_SETUP>" (Report /SDF/CALM_SCHEDULER) as tasks via asynchronous RFCs.
Additionally, the job "CALM Heartbeat <Setup name in /SDF/ALM_SETUP>" (Report /SDF/CALM_HEARTBEAT) is scheduled.
Data collection for Business Process Monitoring is triggered periodically by the jobs: