This page describes the monitoring setup for SAP S/4HANA Cloud with SAP Focused Run 3.0 FP 01 or newer.
As of SAP Focused Run 3.0 FP 01 it is possible to use the PUSH monitoring architecture in SAP S/4HANA Cloud to push collected messages and exceptions for Advanced Integration Monitoring from the SAP S/4HANA Cloud tenant using the SAP Focused Run reverse proxy architecture.
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 FP 1.0||Stay on this page|
|SAP Focused Run 3.0 and lower||SAP S/4HANA Cloud - up to SAP Focused Run 3.0|
For SAP S/4HANA Cloud the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
|Scenario Component||Monitored Content||Monitoring Category|
|1||Systems: ABAP on-premise system||IDocs||IDoc|
|2||Systems: ABAP on-premise system||Web Service errors and performance||Web Service Messages (ABAP), Web Service (Performance)|
|3||Systems: ABAP on-premise system||Messages in the ABAP proxy framework||ABAP: PI Messages|
|4||Systems: ABAP on-premise system||RFC destination to the S/4HANA Cloud (Cloud connector)||Connection Monitoring (SM59), RFC (Performance)|
|5||Cloud Services: SAP Integration Suite - Cloud Integration||Integration flows (IFlow) in SAP Integration Suite - Cloud Integration||SAP Integration Suite|
|6||Systems: SAP PI on-premise system||PI Messages|
ABAP: PI Messages
Java: PI Communication Channels, PI Messages
|7||Cloud Services: SAP S/4HANA Cloud||Exceptions and messages in SAP S/4HANA Cloud|
SAP S/4HANA Cloud Asset Central Foundation Integration, SAP S/4HANA Cloud Data Replication, Extensibility Transport Management, bgRFC(queue), bgRFC(trans), IDoc, PI-runtime, qRFC, tRFC, WS-runtime, XML, Synchronous Log
|8||On-premise: SAP Cloud Connector||Availability and Performance for SAP Cloud Connector||Available monitoring content in Advanced System Monitoring|
The following technical prerequisites have to be met in order to monitor this scenario:
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.
After the successful setup in you SAP S/4HANA Cloud tenant, the managed cloud service will automatically be created in the Landscape Management Database of SAP Focused Run.
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.
For SAP S/4HANA Cloud services with PUSH monitoring configuration, the monitoring is activated by default during the PUSH monitoring activation in the managed system. You can activate or deactivate the categories after the initial setup.
Available Monitoring Categories
For SAP S/4HANA Cloud, different monitoring categories are available:
For SAP S/4HANA Cloud services using PUSH monitoring, standard filters are created during the initial PUSH monitoring setup. You can create additional filters or change the existing filter as required.
Available Filter Options
For categories collecting messages from AIF no data collection filters are allowed. In general all data is collected. You can create a filter later on, when creating an alert.
The other categories you can restrict by the following parameters:
The category 'SAP S/4HANA Cloud Asset Central Foundation Integration' is based on ABAP Application Log
The category 'SAP S/4HANA Cloud Data Replication' is based on ABAP Application Log
The category 'Extensibility Transport Management' is based on ABAP Application Log
For the other categories you can either select all messages or you can restrict them by the following parameters:
For SAP S/4HANA Cloud the following metrics are available: