SAP S/4 HANA Cloud Edition

S/4 HANA Cloud Edition is SAP's on-demand cloud-based Software-as-a-Service S/4 HANA offering.

Integration Scenario

Please, select...

Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring 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 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 categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.

After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found 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:

  • Integrating SAP backend with SAP S/4HANA Cloud Edition mediated via SAP CPI: 2, 5, 7
  • Integrating SAP backend with SAP S/4HANA Cloud Edition mediated via SAP PI: 1, 2, 3, 6, 7
  • Integrating SAP backend with SAP S/4HANA Cloud Edition via SAP Cloud Connector: 1, 4, 7, 8 
 

Scenario Component Monitored Content Monitoring Category
Systems: ABAP on-premise system IDocs IDoc
Systems: ABAP on-premise system  Web Service errors and performance  Web Service Messages (ABAP), Web Service (Performance) 
Systems: ABAP on-premise system  Messages in the ABAP proxy framework  ABAP: PI Messages 
Systems: ABAP on-premise system  RFC destination to the S/4 HANA CE (Cloud connector)  Connection Monitoring (SM59), RFC (Performance) 
Cloud Services: SAP Cloud Platform Integration  Integration flows (iFlow) in SAP CPI  SAP Cloud Platform Integration 
Systems: SAP PI on-premise system  PI Messages 

ABAP: PI Messages

Java: PI Communication Channels, PI Messages 

Cloud Services: SAP S/4 HANA Cloud Edition  Exceptions and messages in SAP S/4 HANA Cloud Edition  SAP S/4HANA Cloud Asset Central Integration, SAP S/4HANA Cloud Data Replication, bgRFC(queue), bgRFC(trans), IDoc, PI-runtime, qRFC, tRFC, WS-runtime 
On-premise: SAP Cloud Connector  Availability and Performance for SAP Cloud Connector  Available monitoring content in Advanced System Monitoring 

Technical Prerequisites

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

  • SAP S/4HANA Cloud Data Replication (f.k.a. SAP S/4HANA Cloud) can be monitored with Focused Run 1.0 Feature Pack 01
  • For all other monitoring categories you need FRUN 2.0 Feature Pack 01 

Configure Cloud Service

Please, select...

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 Focused Run does not apply to cloud services.

However, to be able to monitor exceptions and performance in cloud services they need to be connected to Focused Run. This connection is created using the customer and cloud service specific root URL and an end-point definition, which allows Focused Run to receive information from the cloud service.

The first step is to import the SSL certificate into Focused Run. This is valid for all cloud services.

Import Cloud SSL certificate into STRUST

Export Certificate from Browser: 

  1. Open the cloud service URL in your web browser.
  2. Click on the padlock next to the Cloud Service URL (within the address input field).
  3. When using Firefox, click on ‘Show Connection details', ‘More Information', 'View Certificate' and select the ‘Details' tab.
  4. When using Microsoft IExplorer, click on ‘View Certificate' and select the 'Certificate Path' tab.
  5. When using Google Chrome, click on ‘Certificate' and select the 'Certificate Path' tab.
  6. In the displayed certificate hierarchy select the Certification Authority (CA) certificate you plan to trust.
  7. When using Firefox, press ‘Export…'.
  8. When using Microsoft IExplorer or Google Chrome, press ‘View Certificate' and in the displayed pop-up navigate to the ‘Details' tab, to press ‘Copy to File…'.
  9. Select an export format you would like to use and that is supported by STRUST transaction, and export the certificate.

Import Certificate into Focused Run:

  1. Now, log on to Focused Run and go to transaction STRUST.
  2. Switch to Edit.
  3. Double click on entry 'SSL client SSL Client (Anonymous)'.
  4. Import the previously exported CA certificate, by pressing – within section ‘Certificate' – the icon ‘Import Certificate'.
  5. Press ‘Add to Certificate List'.
  6. Finally ‘Save' this modification. 

Additionally you have to perform certain preparations in the cloud service to enable Focused Run to connect to the cloud service.   

 
 
 
 

Preparations in SAP S/4 HANA Cloud Edition

  1. Create a communication arrangement of type 'SAP_COM_0454' (Application Monitoring Integration) in SAP S/4 HANA Cloud Edition.
  2. Note down the user and the password used in the communication arrangement. 

Please, select...

After gathering all necessary information and creating the necessary connection point or users in the cloud service, you can now create the cloud service in Focused Run.

  1. Call transaction FRUN
  2. Select 'Advanced Integration Monitoring' → Cloud Service Management
  3. Click the 'Add' button
  4. Select the Cloud Service Type.
  5. The other input fields in the section 'Definition' depend on the cloud service type, see the details below
  6. In the section 'Identification' you have to enter the following:
    • Customer Network: the isolated network for which this cloud service should be visible
    • Extended Service ID: the extended SID uniquely identifies the cloud service in LMDB and can be between 3 and 8 characters long
 

Input Values for S/4 HANA Cloud Edition

  • Tenant: Tenant name of your tenant
  • Root URL: Your S/4 HANA Cloud Edition URL ( e.g. https://myhost.s4hana.ondemand.com )
  • Description: (optional)

Please, select...

The second step is to create the end-point for the cloud service. The end-point is used to actually connect to the cloud service with user and password. Most cloud services use HTTP end-points.

  1. Click on the extended service ID of the cloud service 
  2. Click the 'Add' button on the 'HTTP ENDPOINTS' tab.
  3. Enter the following information:
    • Section 'Global':
      • Description: A meaningful description
    • Section 'Authentication':
      • The information needed here depends on the cloud service type, please refer to the details below
    • Section 'Proxy':
      • If necessary add proxy information to connect to the cloud service
 

Input Values for SAP S/4 HANA Cloud Edition

  • Endpoint Type: HTTP
  • Authentication Type: BASICAUTH
  • User: The user created for the communication arrangement
  • Password: Password of the user 
 

Advanced Integration Monitoring Setup

Please, select...

To be able to monitor interfaces of an on-premise system you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system. 

  1. Open the Advanced Integration Monitoring Application by clicking on the 'Integration & Cloud Monitoring' tile in transaction FRUN
  2. Click on the pinwheel in the upper right corner of the 'Integration & Cloud Monitoring' application
  3. In the configuration panel expand the 'Cloud Services' tray and click on the pen icon in the upper right corner. This will open the 'Configuration for Cloud Services' view.
  4. If your system is not on the list yet, click the 'Add' button to add it. If it is on the list, click on the system ID of the system. 

In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.

Select the monitoring categories in scope.

Available Monitoring Categories

For SAP S/4 HANA Cloud Edition, different monitoring categories are available:

  • SAP S/4HANA Cloud Asset Central Integration: Collects exceptions happening in SAP Intelligent Asset Management
  • SAP S/4HANA Cloud Data Replication (f.k.a. SAP S/4 HANA Cloud): Collects exceptions in the Data Replication Framework (DRF)
  • bgRFC(queue): Collects connections from AIF (Application Interface Framework) of type queued bgRFC
  • bgRFC(trans): Collects connections from AIF (Application Interface Framework) of type transactional bgRFC
  • IDoc: Collects messages from AIF (Application Interface Framework) of type IDoc
  • PI-runtime: Collects messages from AIF (Application Interface Framework) of type PI 
  • qRFC: Collects connections from AIF (Application Interface Framework) of type qRFC
  • tRFC: Collects connections from AIF (Application Interface Framework) of type tRFC
  • WS-runtime: Collects messages from AIF (Application Interface Framework) of type web service 
 

Please, select...

After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own. You can create more than one filter for a monitoring category.

Available Filter Options

The categories 'SAP S/4HANA Cloud Asset Central Integration' and 'SAP S/4HANA Cloud Data Replication' are based on ABAP Application Log and hence some parameters are mandatory.

SAP S/4HANA Cloud Asset Central Integration

  • Object (mandatory): The object of the log record (/SYCLO/)
  • Subobject (mandatory): The sub-object of the log record (/SYCLO/INB_TRANS)
  • External ID: External ID of the Application Log entry
  • Message ID: Message Class
  • Message Number: Message Number
  • Text: Message Text
  • Program: Program triggering the log entry
  • Transaction: Transaction code triggering the log entry
  • User: The user who triggered the log entry

SAP S/4HANA Cloud Data Replication

  • Object (mandatory): The object of the log record (DRF_OUTBOUND)
  • Subobject (mandatory): The sub-object of the log record (Choose from the input help, e.g. CHANGES)
  • External ID: External ID of the Application Log entry
  • Message ID: Message Class
  • Message Number: Message Number
  • Text: Message Text
  • Program: Program triggering the log entry
  • Transaction: Transaction code triggering the log entry
  • User: The user who triggered the log entry

For the other categories you can either select all messages or you can restrict them by the following parameters:

bgRFC(queue)

  • Direction: Choose I (Inbound) or O (Outbound)
  • Queue Name: Name of qRFC Queue
  • RFC Destination: RFC destination name

bgRFC(trans)

  • Direction: Choose I (Inbound) or O (Outbound)
  • RFC Destination: RFC destination name
  • Transaction Code: The name of the SAP transaction code with which the unit was created
  • Program: Tcode/program with which the unit was created
  • User: The name of the user under which the unit is recorded

IDoc

  • Direction: 1 (Outbound) or 2 (Inbound)
  • Sender port: Partner port (relevant for inbound IDocs)
  • Receiver port: Partner port (relevant for outbound IDocs)
  • Message Type: IDoc Message type, e.g. ORDERS

PI-runtime

  • Sender namespace: The namespace of the source of the message
  • Sender interface: The interface of the source of the message
  • Sender party: The communication party of the source of the message
  • Sender component: The component of the source of the message
  • Receiver namespace: The namespace of the target of the message
  • Receiver interface: The interface of the target of the message
  • Receiver party: The communication party of the target of the message
  • Receiver component: The component of the target of the message

qRFC

  • Direction: Choose I (Inbound) or O (Outbound)
  • Queue Name: Name of qRFC Queue
  • RFC Destination: RFC destination name

tRFC

  • RFC Destination: The name of the RFC destination the tRFC is sent over
  • Function Module: The name on the called function module
  • User: The user in the RFC destination

WS-runtime

  • Adapter Type: The adapter used for the WS. Please use the input help to select an adapter.
  • Sender Party: Sender Communication party
  • Sender Interface Name: Sender Interface
  • Receiver Party: Receiver Communication party
  • Receiver Interface Name: Receiver Interface 
 

Please, select...

The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually. If you didn't use specific filters in the setup before, but rather opted to collect all data, you have to create filters for the alerts.

  1. Click on the 'New Alert' button in the upper right corner of the alerts table. A new panel will appear below the table for you to enter the alert information
  2. Select the monitoring category
  3. Select the metric name. The available metrics depend on the monitoring category.
  4. Enter a name for the alert
  5. Enter a name for the filter

In the next sub-step, you have to maintain the filter. The filter values are the same as described above. For some metrics, you have to maintain metric parameters. Find details below in the overview of the available metrics.

In the last sub-step you have to activate the alert:

  1. Check the checkbox next to 'Active'
  2. You can adjust the calculation frequency and the severity
  3. Available threshold types depend on the metric selected. If the threshold type allows it you can adjust the threshold value which triggers the alert.
  4. Select the notification variant and the outbound connector variant from the drop-down list.

For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.

Available Metrics

For SAP S/4 HANA Cloud Edition not for all monitoring categories metrics were created. Only the following metrics are available:

SAP S/4HANA Cloud Asset Central Integration

  • SAP S/4HANA Cloud Asset Central Integration exceptions: Indicates that new exceptions were collected during the last data collection interval

SAP S/4HANA Cloud Data Replication

  • SAP S/4HANA Cloud Data Replication exceptions: Indicates that new exceptions were collected during the last data collection interval

IDoc

  • IDocs in status "Error" for longer than N minutes: Indicates new IDocs in the status group ERROR were collected during the collection interval
    Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider IDocs older than [minutes]

PI-runtime

  • PI Messages in status "Error" for longer than N minutes: Indicates new PI messages in the status Error were found during the collection interval
    Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider PI Messages older than [minutes]

WS-runtime

  • Number of erroneous Web Service messages: The metric specifies the number of erroneous Web Service messages within the collection interval.