SAP S/4HANA Cloud

How you can contact us:

Technical Assistance

Request product support from SAP
Non-Technical Assistance

Request non-product support or provide feedback on SAP Support Portal site

SAP S/4HANA Cloud

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 applications are supported for SAP S/4HANA Cloud:

Note: If you are looking for documentation on how to monitor SAP S/4HANA on-premises systems (operated by SAP or your organization), please navigate to: Monitoring of Integration Scenarios | Monitoring capabilities for on-premise systems.

Choose Your SAP Focused Run Release

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

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

SAP Focused Run Release	Monitoring Setup Documentation
SAP Focused Run 3.0 FP03	Stay on this page
SAP Focused Run 3.0 FP02 and lower	SAP S/4HANA Cloud - up to SAP Focused Run 3.0 FP02

Prerequisites

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

SAP Focused Run 3.0 FP03
SAP Cloud ALM subscription
To enable this monitoring please ensure that you configured the SAP Focused Run reverse proxy in SAP Cloud ALM
You have enabled the landscape sync during the reverse proxy setup
You need to obtain the SAP Cloud ALM Service Key

PUSH vs. PULL Data Collection

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)

If you already monitor use-cases using PUSH data collection you can add the newly available use-cases in the Communication Arrangement in the managed cloud service.

If you already monitor your cloud service using PULL data collection, we recommend that you switch to PUSH data collection.

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 for the first time 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:

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

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

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.

You need a user with administrator authorizations in SAP S/4HANA Cloud tenant

Log on to SAP S/4HANA Cloud tenant
Navigate back to the 'Communication Management' view and select 'Communication Arrangements'
Click the New button to create a new Communication Arrangement
Scenario: Select SAP_COM_0527 'Application Monitoring Push Integration'
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. Under 'Host Name' enter SAP Cloud ALM service key parameter "Api" without /api, e.g. eu10.alm.cloud.sap
3. Make sure the 'Port' is set to 443
4. Under 'OAuth 2.0 Settings' enter the SAP Cloud ALM service key parameter "uaa":"url" extended by /oauth/token 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: SAP Cloud ALM service key parameter "uaa":"clientid"
  3. Client Secret: SAP Cloud ALM service key parameter "uaa":"clientsecret"
6. Save the communication system. The UI will take you back to the communication arrangement
Under "Additional properties" enter an 'X' for 'Enable Integration Monitoring', 'Enable Exception Monitoring', 'Enable Job & Automation Monitoring', and 'Enable Performance Monitoring'
The 'Outbound Communication' fields are automatically propagated from the communication system
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/sap/frun/
Press the "Enter" key. This will trigger the propagation of the fields below when you save the communication arrangement
Adjust the Job Execution Details to schedule the job to Run Every 01 Minute(s)
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.

Setup Steps in SAP Focused Run

The cloud service entry for the SAP S/4HANA Cloud service which was created by the landscape sync from SAP Cloud ALM will be updated. For this cloud service, the data collection for the activated use-cases will be automatically activated. No further steps have to be taken.

Troubleshooting

To investigate errors during the setup of the monitoring PUSH please refer to the Troubleshooting for SAP ABAP-based Cloud Services page.