Contact Us
×
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

  1. SAP Support Portal Home
  2. Application Lifecycle Management
  3. SAP Focused Run
  4. SAP Focused Run Expert Portal
  5. Integration & Exception Monitoring For Cloud Services

SAP S/4HANA Cloud - up to SAP Focused Run 3.0 FP02

SAP S/4HANA Cloud - up to SAP Focused Run 3.0 FP02

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

For SAP Focused Run up to SAP Focused Run 3.0 FP 02 we use a PULL data collection mechanism to collect metrics from 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.

Technical Prerequisites

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

  • SAP S/4HANA Cloud Data Replication (formerly known as SAP S/4HANA Cloud) can be monitored with Focused Run 1.0 FP01
  • For all other monitoring categories you need FRUN 2.0 FP01
  • To use Real User Monitoring you need at least FRUN 2.0 FP02

Configure Cloud Service

Preparations in SAP S/4HANA Cloud 

The user that will be maintained in the HTTP endpoint, must be a user declared in the relevant Communication Arrangement defined in SAP S/4HANA Cloud for enabling the API used by SAP Focused Run. To arrange a communications agreement and allow SAP Focused Run access please proceed as following:

  1. Log as administrator onto the SAP Fiori Launchpad of your SAP S/4HANA Cloud tenant
  2. Select 'Communication Systems' under Communication Management
  3. Create a new communication system
    • System ID: SAP Focused Run SID
    • System Name: SAP Focused Run system name (e.g. FRUN)
    • Host Name: Enter any value into the mandatory field Host Name. Please note that since the actual value is not used in this communication scenario, it can be chosen freely.
  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.
  10. Return to the Fiori Launchpad and choose 'Communication Arrangements' under 'Communication Management'
  11. Create a new scenario of type 'SAP_COM_0454' (Application Monitoring Integration)
  12. On the next screen select the communication system you created before and verify that the user name is provided automatically
  13. Save the communications arrangement

Input Values for SAP S/4HANA Cloud

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

Input Values for SAP S/4HANA Cloud

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

Advanced Integration Monitoring Setup

Available Monitoring Categories

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

  • SAP S/4HANA Cloud Asset Central Foundation Integration: Collects exceptions happening in SAP Intelligent Asset Management
  • SAP S/4HANA Cloud Data Replication (f.k.a. SAP S/4HANA 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 
  • SYNC-LOG: Collects messages from AIF (Application Interface Framework) of type SYNC-LOG
  • XML: Collects messages from AIF (Application Interface Framework) of type XML
 
 

Available Filter Options

  • 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
  • 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
  • Direction: Choose I (Inbound) or O (Outbound)
  • Queue Name: Name of qRFC Queue
  • RFC Destination: RFC destination name
  • 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
  • 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
  • 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
  • Direction: Choose I (Inbound) or O (Outbound)
  • Queue Name: Name of qRFC Queue
  • RFC Destination: RFC destination name
  • 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
  • No filters are available for this category on data collection level. To filter the collected data and generate alerts please use the filters in the 'Alerting' step.
  • 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
  • Sender Interface Namespace: Sender Interface Namespace
  • Receiver Party: Receiver Communication party
  • Receiver Interface Name: Receiver Interface 
  • Receiver Interface Namespace: Receiver Interface Namespace
  • No filters are available for this category on data collection level. To filter the collected data and generate alerts please use the filters in the 'Alerting' step.

Available Metrics

For SAP S/4HANA Cloud the following metrics are available.

  • 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 exceptions: Indicates that new exceptions were collected during the last data collection interval

The following metrics a based on the AIF in the SAP S/4HANA Cloud. For these metrics you can filter by the following parameters additionally to the ones that are already available in the data collection for the respective message type:

  • bgRFC(queue) messages in status Error for longer than N minutes: Indicates new bgRFC (queue) messages in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider bgRFC (queue) messages older than [minutes]
  • bgRFC(trans) messages in status Error for longer than N minutes: Indicates new bgRFC (trans) messages in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider bgRFC (trans) messages older than [minutes]
  • IDocs in status Error for longer than N minutes: Indicates new IDocs in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider IDocs older than [minutes]
  • PI Messages in status Error for longer than N minutes: Indicates new PI messages in the status Error were found during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider PI Messages older than [minutes]
  • qRFC messages in status Error for longer than N minutes: Indicates new qRFC messages in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider qRFC messages older than [minutes]
  • tRFC messages in status Error for longer than N minutes: Indicates new tRFC messages in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider tRFC messages older than [minutes]
  • Sync Log messages in status error for longer than N minutes: Indicates new Sync Log messages in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction: Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider Sync Log messages older than [minutes]
  • Number of erroneous WS messages: The metric specifies the number of erroneous Web Service messages within the collection interval.
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction (if applicable): Message direction
  • XML messages in status error for longer than N minutes: Indicates new XML messages in the status group ERROR were collected during the collection interval
  • Data filter fields:
    • Namespace: AIF interface namespace
    • Interface Name: AIF interface name
    • Interface Version: AIF interface version
    • Status: The last status of the message
    • Status Group: Please select a value from the input help
    • Status Text: Text in the status or parts thereof
    • Direction: Message direction
  • Metric parameters:
    • STATUS_GROUP (not changeable) = ERROR
    • OLDER_THAN_MINUTES = Only consider XML messages older than [minutes]

Real User Monitoring Setup

Activate Real User Monitoring

To enable Real User Monitoring for SAP S/4HANA Cloud, please proceed as following:

  1. Open the "Real User Monitoring" application
  2. Open the scope selection
  3. Select your SAP S/4HANA Cloud service
  4. Open the configuration panel
  5. Expand the "Systems" tray
  6. Switch the data collection for your SAP S/4HANA Cloud service from OFF to ON