S/4 HANA Cloud Edition is SAP's on-demand cloud-based S/4 HANA offering.
For most cloud services, SAP Solution Manager is able to collect and monitor exceptions happening in the cloud service. But to fully monitor a cloud service scenario it is also important to monitor the integration between the cloud service and the on-premise backend system. This integration consists of different point-to-point interfaces of different usually more traditional types.
The following section describes the different integration options for the cloud service. Please choose the integration option you are using and consider also setting up the monitoring for the relevant interface types that are part of the integration scenario for the cloud service.
On this page we describe the monitoring setup this specific cloud service type. For information on how to set up the monitoring for the interface types supporting the integration, please refer to the setup documentation of the respective interface type which you can here.
For SAP S/4 HANA Cloud Edition the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
|Scenario Component||Monitored Content||Interface Channel Type||
|1||Systems: ABAP on-premise system||IDocs||IDoc||7.1 SP12|
|2||Systems: ABAP on-premise system||Web Service errors and performance||Web Service: Web Service ABAP (STAD) or Web Service ABAP (SOAP)||7.1 SP05*|
|3||Systems: ABAP on-premise system||Messages in the ABAP proxy framework||Process Integration: Process Integration (PI – ABAP only)||7.1 SP12|
|4||Systems: ABAP on-premise system||RFC destination to the S/4 HANA CE (Cloud connector)||RFC||7.1 SP05*|
|5||Cloud Services: SAP Cloud Platform Integration||Exceptions in integration flows (iFlow) in SAP CPI||Cloud: Cloud (SAP Cloud Platform Integration)||7.1 SP12*|
|6||Systems: SAP PI on-premise system||PI Messages and Channels||Process Integration||7.1 SP12|
|7||Cloud Services: SAP S/4 HANA Cloud Edition||Exceptions in SAP S/4 HANA Cloud Edition||Cloud: Cloud (S/4 CE)||7.2 SP06|
|8||On-premise: SAP Cloud Connector||Availability and Performance for SAP Cloud Connector||Available monitoring content in System Monitoring||7.2 SP06|
*) Monitoring content was extended with later support packages (see monitoring template page for details)
The following technical prerequisites have to be met in order to monitor this scenario:
For S/4 HANA Cloud Edition the following exceptions are currently covered by public cloud operation with SAP Solution Manager:
The exceptions in S/4 HANA Cloud Edition are collected using Exception Management in SAP Solution Manager. After they are collected in Exception Management they can be reused for monitoring in Interface and Connection Monitoring
|Metric Name||Description||MAI Category||Since SP|
|Single exceptions in S/4 CE||Single exceptions detected in Application Log of S/4 CE||Exceptions||7.2 SP08|
Public cloud service offerings are usually Software-as-a-Service (SaaS) solutions. This means that customers only have access to the service but not to the underlying infrastructure. Hence, the usual way to connect on-premise managed systems to SAP Solution Manager does not apply to cloud services.
However, to be able to monitor exceptions and performance in cloud services they need to be connected to SAP Solution Manager. This connection is created using the customer and cloud service specific root URL and an end-point definition.
The first step is to import the SSL certificate into SAP Solution Manager. This is valid for all cloud services.
Import Cloud SSL certificate into STRUST
Export Certificate from Browser:
Import Certificate into SAP Solution Manager:
Additionally you have to perform certain preparations in the cloud service to enable SAP Solution Manager to connect to the cloud service.
Create Communication Agreement
The user that will be maintained in the RFC endpoint, must be a user declared in the relevant Communication Arrangement defined in SAP Cloud for Customer for enabling the API used by Solution Manager. To arrange a communications agreement and allow SAP Solution Manager access please proceed as following:
Install SAP Cloud Connector
To connect to S/4 HANA Cloud Editions, SAP Solution Manager needs a SAP Cloud Connector, which enables Remote Function Call (RFC) between SAP Solution Manager system and SAP S/4 HANA Cloud Edition.
You can reuse the SAP Cloud Connector already installed in your landscape or if you don't have one yet, install one.
For more information regarding the installation and setup of SAP Cloud Connector please refer to:
Configure a Service Channel for RFC:
The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.
Create Cloud Service
The second step is to create the end-point for the cloud service.
Create the End-Point
Possible error messages during connection check:
After the basic configuration you now have to configure Exception Management, as the exceptions collected via Exception Management and stored in the central exception store are the basis for the Integration Monitoring data collection.
Configuration for Exceptions from SAP S/4 HANA Cloud
To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management
|Application Interface Framework (AIF)||/AIF/LOG||
|Data Replication Framework (DRF)||DRF_OUTBOUND||
|Asset Central Foundation Integration||/SYCLO/||
For /AIF/LOG there are a lot of different sub-objects that also depend of what interfaces you run in S/4 HANA Cloud Edition. To find out which sub-object to use, you have to find the interface you want to monitor in the message monitoring of your S/4 HANA Cloud Edition tenant.
The last step is the configuration of Interface and Connection Monitoring. The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP). Since the data collection is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions.
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.
Monitoring Template: Cloud (S/4 CE)
Navigate to the step 'Define Scope'. You can create a new scenario for the SAP S/4 HANA CE monitoring or use an existing one. Make sure the on premise system for the SAP S/4 HANA CE scenario and the Cloud Service created for SAP S/4 HANA CE is part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
Since the data collection is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions. The filters applied in Interface and Connection Monitoring allow you to filter the exceptions collected by the Exception Management further. However if the filters in Exception Management do not collect an exception, it is not available in the central exception store and you will not be able to find it in Interface and Connection Monitoring!
Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.
Maintain Thresholds and Schedule:
If not active you can also activate the reporting for the channels by checking the box in the column 'Reporting'. This way you can see a history of the number of exceptions that happened and also place the metric on the OCC Dashboard in Focused Insights.