This page explains how to connect SAP S/4HANA Cloud to SAP Focused Run. For the setup of the supported monitoring applications, please click on the monitoring application below.

Currently the following monitoring application are supported for SAP S/4HANA Cloud:

Choose Your SAP Focused Run Release

This page describes the monitoring setup for SAP S/4HANA Cloud with SAP Focused Run 3.0 FP 02 or newer.

Please select the documentation appropriate for your SAP Focused Run release from the table below. 

SAP Focused Run ReleaseMonitoring Setup Documentation
SAP Focused Run 3.0 FP02Stay on this page
SAP Focused Run 3.0 FP01 and lowerSAP S/4HANA Cloud - up to SAP Focused Run 3.0 FP01


The following technical prerequisites have to be met in order to monitor this scenario:

PUSH vs. PULL Data Collection

With SAP Focused Run 3.0 FP02 we enabled PUSH data collection for monitoring data for exceptions in Integration & Exception Monitoring and Real User Monitoring. Further use-cases will follow in the future.

With PUSH data collection the managed cloud service now actively pushes monitoring data to SAP Focused Run via SAP Cloud ALM which is used as a reverse proxy

PUSH data collection has the following advantages over PULL data collection:

  • PUSH data collection uses OAuth 2.0 to connect from the managed cloud service to SAP Cloud ALM (PULL uses BASIC authentication)
  • Data is only transferred if new monitoring data exists (no unnecessary connections)

Activation of PUSH data collection for cloud services already monitored using PULL data collection

If you already monitor SAP S/4HANA Cloud using the PULL data collection, please note the following:

  • With the activation of PUSH data collection a new cloud service will be created in LMDB by the registration process
  • It will not update or overwrite the existing cloud service created manually during the PULL data collection setup
  • Historical monitoring data collected with the "old" PULL based mechanism will remain attached to the "old" cloud service for reporting

To deactivate the PULL data collection for the existing monitoring setup:

  1. Deactivate the monitoring data collection in Integration & Exception Monitoring and Real User Monitoring
  2. Delete the endpoints in the cloud service in LMDB
  3. Do not delete the cloud service from LMDB yet, to avoid losing historical monitoring data

Please read: Exception for SAP Focused Run 3.0 FP02

With SAP Focused Run 3.0 FP02 the data collection was changed to PUSH data collection for Real User Monitoring and exceptions in Integration & Cloud Monitoring.

Unfortunately, the data collection for AIF messages in Integration & Cloud Monitoring hasn't switched to PUSH data collection yet. This will only happen with SAP Focused Run 3.0 FP03

As mentioned above during the registration of a service for the PUSH data collection a new service entry is created in the SAP Focused Run Landscape Management Database. However, for this automatically created cloud service, you cannot create the endpoint necessary for the PULL data collection for AIF messages.

This has the following consequences. 

  • Until the unification of the data collection exceptions and AIF messages would be collected by two different cloud services (logically it is the same SAP S/4HANA cloud tenant, but technically there are two separate cloud services in the monitoring application)

To avoid having to deal with two cloud services in Integration & Cloud Monitoring you can proceed as following:

  • If you already set up Integration & Cloud Monitoring and Real User Monitoring for the SAP S/4 HANA Cloud service, wait with the switch to PUSH data collection until SAP Focused Run 3.0 FP03
  • If this is a new setup:
    • You can activate the PUSH data collection only for performance data, so only Real User Monitoring data is collected using the PUSH data collection. 
    • For Integration & Cloud Monitoring messages and exceptions you can setup the PULL monitoring for as described here and switch to the PUSH monitoring for AIM entirely with SAP Focused Run 3.0 FP03

Setup Steps in SAP S/4HANA Cloud

To enable the PUSH monitoring data collection in SAP S/4HANA Cloud you need to create a communication system and the correct communication arrangement in you SAP S/4HANA Cloud tenant.

Enable Monitoring Data PUSH of Real User Monitoring and Exceptions

The following steps enable SAP S/4HANA Cloud to send monitoring data to SAP Cloud ALM, which then forwards the data to SAP Focused Run. This is the reason why you will need the SAP Cloud ALM service key and maintain some fields with SAP Cloud ALM information. 


  • You need an user with administrator authorizations in SAP S/4HANA Cloud tenant
  • You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
    • Endpoint: The host part of the service key parameter "Api", e.g.
    • OAuth URL: Service key parameter "url" + /oauth/token, e.g.
    • Client ID: Service key parameter "clientid"
    • Client secret: Service key parameter "clientsecret"
  1. Log on to SAP S/4HANA Cloud tenant
  2. Navigate back to the 'Communication Management' view and select 'Communication Arrangements'
  3. Click the New button to create a new Communication Arrangement
  4. Scenario: Select SAP_COM_0527 'Application Monitoring Push Integration'
  5. Click the New button next to 'Communication System' to create a new communication system
    1. Enter a System ID and description and click the Create button
    2. Enter the Cloud ALM endpoint in the 'Host Name' field
    3. Make sure the 'Port' is set to 443
    4. Under 'OAuth 2.0 Settings' enter the Cloud ALM OAuth URL in the field 'Token Endpoint'
    5. Under 'Users for Outbound Communication' click the + button to create a new user
      1. Authentication Method: Choose OAuth 2.0
      2. OAuth 2.0 Client ID: Enter Cloud ALM client ID
      3. Client Secret: Enter Cloud ALM client secret
    6. Save the communication system. The UI will take you back to the communication arrangement
  6. Under "Additional properties" enter an 'X' for "Collect Exceptions". If you want to use Real User Monitoring also for "Collect Performance Data". 
  7. The 'Outbound Communication' fields are automatically propagated from the communication system
  8. The "Path" field under 'Outbound Services' is where you have to maintain the path to SAP Focused Run, enter:
    1. The suffix from the Reverse Proxy URL from the endpoint in SAP Cloud ALM, e.g. /api/frunrevproxy/v1/my_customer_network/
    2. Add sap/frun/ (including the / in the end) to the suffix
    3. The total string should be: /api/frunrevproxy/v1/my_customer_network/sap/frun/
  9. Press the "Enter" key. This will trigger the propagation of the fields below when you save the communication arrangement
  10. Adjust the Job Execution Details to schedule the job to Run Every 01 Minute(s)
  11. Save

After the successful setup in your SAP S/4HANA Cloud tenant, the managed cloud service will automatically be created in the Cloud Service Management of SAP Focused Run.

Prepare PULL Monitoring for AIF Messages

You only need to perform the following steps, if you want to collect AIF messages in Integration & Cloud Monitoring.

Add a user for "Inbound Communication" to the communication system created in the previous step.

  1. Log as administrator onto the SAP Fiori Launchpad of your SAP S/4HANA Cloud tenant
  2. Select 'Communication Systems' under Communication Management
  3. Open the communication system created in the previous step
  4. Choose '+' user under 'User for Inbound Communication' to add a user for inbound communication
  5. Choose 'New User'
  6. Enter the following entries in the 'Create Communication User' screen
    • User Name: Enter a user name
    • Description: Enter a short description
    • Password: Enter a password. Remember this password for later
  7. Choose 'Create'
  8. Choose 'User Name and Password' as authentication method
  9. Select OK and save the communications system.
Now create a communication arrangement for the PULL monitoring connection.
  1. Return to the Fiori Launchpad and choose 'Communication Arrangements' under 'Communication Management'
  2. Create a new scenario of type 'SAP_COM_0454' (Application Monitoring Integration)
  3. On the next screen select the communication system you created before and verify that the user name is provided automatically
  4. Save the communications arrangement
  5. Note down the API-URL shown under 'Common Data'. You will need this later.

Setup Steps in SAP Focused Run

Please note that an entry for the SAP S/4HANA Cloud service will be created by the PUSH monitoring registration. For this cloud service the Real User Monitoring and the Exception Monitoring will be automatically activated. No further steps have to be taken. 

If you also want to monitor AIF messages in SAP S/4HANA Cloud you have to create an additional cloud service by performing the following steps.

Input Values for SAP S/4HANA Cloud

  • Tenant: Tenant name of your tenant
  • Root URL: Your SAP S/4HANA Cloud API-URL ( e.g. )
  • Description: (optional)

Input Values for SAP S/4HANA Cloud

  • User: The user created for the "Inbound Communication" in SAP S/4HANA Cloud
  • Password: Password of the user