1. SAP Support Portal Home
  2. Application Lifecycle Management
  3. SAP Cloud ALM
  4. SAP Cloud ALM for Operations
  5. SAP Cloud ALM for Operations Expert Portal
  6. Integration & Exception Monitoring

SAP S/4HANA Public Cloud Edition

SAP S/4HANA Public Cloud Edition

Available Monitoring Content

The following monitoring content is available for SAP S/4HANA Public Cloud Edition. 

SAP Concur messages can be monitored for the integration with SAP S/4HANA Public Cloud Edition. The setup for SAP Concur message monitoring is performed as part of the monitoring setup for SAP S/4HANA Public Cloud Edition. Please follow the instructions here.

CategoryTypeDescription
AIF MessagesMessagesMonitors messages sent in the SAP Application Interface Framework
Concur ObjectsMessagesMonitors messages sent for the integration with Concur
Asset Central Foundation IntegrationExceptionsCollects exceptions happening in SAP Intelligent Asset Management
Data ReplicationExceptionsCollects exceptions in the Data Replication Framework (DRF)

Setup Steps in SAP S/4HANA Public Cloud Edition

Integration & Exception Monitoring for SAP S/4HANA Public Cloud Edition uses a PUSH as well as a PULL mechanism to collect the data for the different monitoring categories.

PUSH data collection:

  • AIF Messages
  • Concur Objects

PULL data collection:

  • Asset Central Foundation Integration
  • Data Replication

Enable Monitoring Data PUSH to SAP Cloud ALM

Perform the following steps to enable SAP S/4HANA Public Cloud Edition to send monitoring data to SAP Cloud ALM.

Prerequisites:

  • You need an user with administrator authorizations in SAP S/4HANA Public Cloud Edition
  • You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
    • Endpoint: eu10.alm.cloud.sap
    • OAuth URL: Service Key parameter "url" + /oauth/token, e.g. calm-tenant.authentication.eu10.hana.ondemand.com/oauth/token
    • Client ID: Service key parameter "clientid"
    • Client secret: Service key parameter "clientsecret"
  1. Log on to SAP S/4HANA Public Cloud Edition
  2. Navigate back to the 'Communication Management' view and select 'Communication Arrangements'
  3. Click the New button to create a new Communication Arrangement
  4. Scenario: Select SAP_COM_0527 'Application Monitoring Push Integration'
  5. 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. Enter the Cloud ALM endpoint URL in the 'Host Name' field
    3. Make sure the 'Port' is set to 443
    4. Under 'OAuth 2.0 Settings' enter the Cloud ALM OAuth URL 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: Enter Cloud ALM client ID
      3. Client Secret: Enter Cloud ALM client secret
    6. Save the communication system. The UI will take you back to the communication arrangement
  6. Enter an 'X' in 'Collect Integration Monitoring' if the field is empty. Do not change any of the other fields.
  7. The 'Outbound Communication' fields are automatically propagated from the communication system
  8. Under 'Outbound Services' enter a '/' in the field 'Path'. This will trigger the propagation of the fields below when you save the communication arrangement
  9. Adjust the Job Execution Details to schedule the job to Run Every 01 Minute(s)
  10. Save

Create Communication Arrangement

The Communications Arrangement is necessary to create an HTTP end-point in SAP Cloud ALM to support the PULL data collection.
  1. Navigate to the 'Communication Management' view on the SAP S/4HANA Public Cloud Edition launchpad
  2. Select 'Communication Systems'
  3. Create a new communication system
    1. ID: Enter e.g. CRUN
  4. Enter General data
    1. Enter a value for the host name field
  5. Create User for Inbound Communication
    1. Select the + button
    2. Click the New User button
    3. Enter user name, description and password
    4. Click the Create button
  6. Save
  7. Navigate back to the 'Communication Management' view and select 'Communication Arrangements'
  8. Create a new Communication Arrangement
  9. Scenario: Select SAP_COM_0454 'Application Monitoring Integration'
  10. Common Data: Select the CRUN communication system
  11. Inbound Communication: Enter the user created for the communication system.
  12. Save

Setup Steps in SAP Cloud ALM

Create HTTP End-Point

The end-point only needs to be created to support PULL data collection. PUSH data collection is configured in the managed cloud service and available after registration of the cloud service in Landscape Management. You can create the PULL end-point for the same system in Landscape Management, that was created by the PUSH registration.
  1. Open the Landscape Management application from the launchpad
  2. Select your SAP S/4HANA Public Cloud Edition service
  3. Press the > button at the end of the line
  4. On the tab "Endpoints" press the Add button to create a new end-point
  5. Enter a description
  6. Choose the use-case "Exception Monitoring"
  7. Adjust the Root-URL for the end-point: make sure to add -api to the hostname, e.g. https://myhost-api.s4hana.ondemand.com 
  8. Choose BASIC authentication enter the user and password created in the Communication Agreement

Activate Monitoring (Standard)

In SAP Cloud ALM you can easily activate the standard monitoring content without any additional setup effort. 

  1. Open the Integration & Exception Monitoring application from the launchpad
  2. The scope selection will appear automatically
  3. Change the drop-down for Display Service to "All"
  4. Make sure to select your cloud service in the scope
  5. Click the Configuration button in the upper right corner to access the configuration
  6. Expand the Configuration panel
  7. Change the toggle button next to the cloud service from OFF to ON

Adjust Monitoring and Alerting (Expert)

You can change which parts of the standard content are activated for each cloud service, activate and deactivate alerts or create own alerts with specific filters. 

  1. In the configuration panel, click on the name of the cloud service
  2. The "Configuration of Services" screen opens
  3. In the "Configuration for Services" screen, click the > button at the end of the line for the cloud service you want to change

Adjust Monitoring Categories

  1. Use the toggle button in the column Active to turn a monitoring category ON or OFF

Adjust Alerting

  1. Use the toggle button in the column Active to turn a standard alert ON or OFF
  2. Press the > button at the end of the line to access the detail setup for an existing alert or use the + button to create a new alert
  3. Adjust the display name if desired
  4. Expand the Filter Configuration tray
  5. Enter a filter name
  6. Select the filter category
  7. Maintain the available filter fields (see details below)

Available Alerts for SAP S/4HANA Public Cloud Edition

  • Erroneous Message(AIF) Detected: Creates an alert for each failed message in the category AIF Messages
  • Erroneous Messages(AIF) Detected: Creates an alert if one or more failed messages in the category AIF Messages were detected since the last data collection
  • Erroneous Concur Object Detected: Creates an alert for each failed message in the category Concur Objects
  • Erroneous Concur Objects Detected: Creates an alert if one or more failed messages in the category Concur Objects were detected since the last data collection
  • Erroneous Asset Central Foundation Integration: Creates an alert for each exception in the category Asset Central Foundation Integration
  • Erroneous Data Replication: Creates an alert for each exception in the category Data Replication

Available Filter Fields for SAP S/4HANA Public Cloud Edition

The filter fields depend on the monitoring category the alert is created for and additional on the filter category, if there is more than one available.

For AIF message alerts different filter categories are available. 

  1. Select the filter category from the drop-down 'Categories'
  2. Maintain the filter parameters

The following AIF-related filter parameters are always available:

  • Direction: Choose INBOUND or OUTBOUND
  • Namespace: AIF interface namespace
  • Interface Name: AIF interface name
  • Version: AIF interface version
  • Status: The last status of the message, e.g. TECHNICAL ERROR
  • Status Group: The status group of the message, please select a value from the input help

Additional filter parameters are available depending on the selected alert category:

AIF Messages - bgRFC(queue)

  • Queue Name: Name of qRFC Queue
  • RFC Destination: RFC destination name

AIF Messages - bgRFC(trans)

  • 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

AIF Messages - IDOC

  • Sender port: Partner port (relevant for inbound IDocs)
  • Receiver port: Partner port (relevant for outbound IDocs)
  • Message Type: IDoc Message type, e.g. ORDERS

AIF Messages - XI-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

AIF Messages - qRFC

  • Queue Name: Name of qRFC Queue
  • RFC Destination: RFC destination name

AIF Messages - 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

AIF Messages - 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

AIF Messages - XML

  • No additional filters

AIF Messages - Sync Log

  • No additional filters

For Concur Objects the available filters depend on the message direction.

INBOUND Message

  • Direction: INBOUND
  • Source System: SAP Logical System ID
  • Source System Type: SAP System Type, e.g. SAP S/4HANA Cloud, essential edition (ES)
  • Status Group: Message status group, select a value from the input help
  • Status: Last message status, e.g. Successful
  • Object Type: Object Type, e.g. Expense Report
  • Connection Name: Connection Name

OUTBOUND Message

  • Direction: OUTBOUND
  • Target System: SAP Logical System ID
  • Status Group: Message status group, select a value from the input help
  • Status: Last message status, e.g. Failed
  • Object Type: Object Type, e.g. Exchange Rate
  • Connection Name: Connection Name

The category 'Asset Central Foundation Integration' is based on ABAP Application Log

  • Object: The object of the log record (always /SYCLO/)
  • Subobject: The sub-object of the log record (always /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

The category 'Data Replication' is based on ABAP Application Log

  • Object: The object of the log record (always DRF_OUTBOUND)
  • Subobject: The sub-object of the log record (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