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 & SAP Business Suite

SAP S/4HANA & SAP Business Suite

Available Monitoring Content

The following monitoring content is available for SAP S/4HANA and SAP Business Suite

CategoryTypeDescription
AIF MessagesMessagesMessages send via the Application Interface Framework
IDOCMessagesIDocs sent or received by the SAP S/4HANA system
Web Service MessagesMessagesMessages sent or received via Web Services and Web Service Proxies
Concur ObjectsMessagesMonitors messages sent for the integration with Concur
ABAP Web Service ProviderExceptionsWeb service errors for incoming web service calls
ABAP RuntimeExceptionsABAP runtime errors
ABAP UpdateExceptionsABAP update errors
ABAP Gateway ErrorsExceptionsExceptions in the ABAP Gateway
ABAP Aborted JobExceptionsABAP aborted jobs
ABAP System LogExceptionsABAP system log errors
SAP S/4HANA Cloud Data ReplicationExceptionsCollects exceptions in the Data Replication Framework (DRF)
ABAP Web Service ConsumerExceptionsWeb service errors for outgoing web service calls
SAP S/4HANA Cloud Asset Central Foundation IntegrationExceptionsCollects exceptions happening in SAP Intelligent Asset Management

Setup Steps in SAP ABAP On-Premise System

Prerequisites

  • Technical Prerequisites for the ABAP system
    • SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04)
    • Install ST-PI 7.40 SP14 or higher
    • Implement the latest version of SAP note 2985521-Collective corrections as of ST-PI 7.40 SP14 for Cloud ALM
    • Implement the latest version of SAP note 3054258 -Collective corrections as of ST-PI 7.40 SP15 for Cloud ALM
    • Check that profile parameter icm/HTTPS/client_sni_enabled is set to TRUE (see also note 510007 - Additional considerations for setting up SSL on Application Server ABAP)
  • Required Authorizations
    • To run  transaction /SDF/ALM_SETUP you need the PFCG role SAP_SDF_ALM_SETUP
    • The user you specify as Background User, requires the PFCG role SAP_SDF_ALM_COLLECTORS_JOBS
  • Obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system

Maintain ALM Destination

Integration & Exception Monitoring for SAP S/4HANA and SAP Business Suite uses a PUSH mechanism to push monitoring data to SAP Cloud ALM. 

Call transaction /n/SDF/ALM_SETUP and perform the following steps:

  1. Target ALM Destination
    • To create a new ALM Destination, enter a name (e.g. CALM) and press the 'Enter' key
    • To change an existing ALM destination, select one from the F4 input help and press the 'Enter' key
    • After pressing the 'Enter' key the subsequent fields will be filled.
  2. Maintain HTTP Destination
    • Click 'Update destination'
    • You can copy&paste the content from the JSON file created during the enablement of the SAP Cloud ALM APIs by clicking 'Paste Service Keys'
    • Or you can enter the required fields for connecting Cloud ALM manually:
      1. Token Endpoint: Enter the CALM OAuth URL 
      2. Client ID: Enter Cloud ALM client ID
      3. Client Secret: Enter Cloud ALM client secret
      4. Proxy User (if required)
      5. Proxy Password (if required)
      6. Proxy Host (if required)
      7. Proxy Port (if required)
    • Click 'Ok' to close the pop-up.
    • To delete a destination click on 'Delete destination'
  3. Enter registration target
    • Enter the target ALM root url depending on your region e.g. https://eu10.alm.cloud.sap
    • Enter the background user you created to perform the data collection
    • Click on 'Register' to call Cloud ALM and register the system. If it is successful, a LMS ID is retrieved and is displayed.
    • To unregister a system, click the 'Unregister' button. Caution: This stops all data collection and heartbeat measurements
  4. For Integration & Exception Monitoring please activate the following use-cases:
    • Integration Monitoring
    • Exception Management 
After the successful setup the SAP S/4HANA or SAP Business Suite system will show up as "Registered' service in the Landscape Management application of your SAP Cloud ALM tenant. 

Setup Steps in SAP Cloud ALM

Activate Monitoring (Standard)

For managed services using PUSH data collection the standard monitoring content is automatically activated during the setup of the PUSH monitoring in the managed service. No further setup steps are necessary. You can check the successful activation in the Integration & Exception Monitoring application.

  1. Open the Integration & Exception Monitoring application from the launchpad
  2. Open the scope selection via the target icon in the upper right corner
  3. Select your cloud service in the scope
  4. Click the rack-wheel icon in the upper right corner to access the configuration
  5. Expand the Configuration panel
  6. The activation status for your SAP S/4HANA service should already be set 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 and SAP Business Suite

  • 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 Message(IDOC) Detected: Creates an alert for each failed message in the category IDOC Messages
  • Erroneous Messages(IDOC) Detected: Creates an alert if one or more failed messages in the category IDOC Messages were detected since the last data collection
  • Erroneous Message(WS) Detected: Creates an alert for each failed message in the category WS Messages
  • Erroneous Messages(WS) Detected: Creates an alert if one or more failed messages in the category WS 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

Available Filter Fields for SAP S/4HANA and SAP Business Suite

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
  • Direction: INBOUND or OUTBOUND
  • Message Type: IDoc message type, e.g. ORDRSP 
  • Basic Type: IDoc basic type, e.g. ORDERS05 
  • Message Variant: IDoc message variant 
  • Message Function: IDoc message function
  • Status group: Select a status group from the input help
  • Status Text: Filter on the Status Text of the collected IDoc message (see tab 'Header Data' in SAP Cloud ALM)
  • Status: Last status of the IDoc (e.g. 51, 02 ...)
  • Sender Partner Number: The partner number of the IDoc sender
  • Sender Port: The partner port of the IDoc sender
  • Sender Partner Function: The partner function of the IDoc sender
  • Sender Partner Type: The partner type of the IDoc sender, e.g. LS
  • Receiver Partner Number: The partner number of the IDoc recipient
  • Receiver Port: The partner port of the IDoc recipient
  • Receiver Partner Function: The partner function of the IDoc recipient
  • Receiver Partner Type: The partner type of the IDoc recipient
  • Receiver Address: The SAP Directory address (SADR) of the receiver
  • Sender Address: The SAP Directory address (SADR) of the sender
  • Client: Client in the SAP ABAP system
  • Direction: INBOUND or OUTBOUND
  • Status: Status value on tab 'Header Data' in SAP Cloud ALM, e.g. System_Error
  • Status Group: Select a value from the input help
  • Status Text: Status text on tab 'Header Data' in SAP Cloud ALM, e.g. "SRT: Unsupported xstream found"
  • Processing Status Group: Processing status group on tab 'Application Data' in SAP cloud ALM, e.g. 2
  • Message Status: Message state on tab 'Application Data' in SAP Cloud ALM, e.g. 114 - Syst_Error
  • State Group: State group of the web service messages, e.g. 99, 2, ...
  • State Group Text: State group text, e.g. Finished, System Error, Application Error etc.  
  • Adapter Type: Adapter type, e.g. PLAINSOAP
  • Sender Party: Sender party of the web service message
  • Sender Interface Name: Sender interface name of the web service message
  • Sender Interface Namespace: Sender interface namespace of the web service message
  • Sender Interface Operation: Sender interface operation of the web service message
  • Receiver Party: Receiver party of the web service message
  • Receiver Interface Name: Receiver interface name of the web service message
  • Receiver Interface Namespace: Receiver interface namespace of the web service message
  • Receiver Interface Operation: Receiver interface operation of the web service message

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
Restriction

Currently the monitoring of the connection between the on-premise S/4HANA or SAP Business Suite system, with SAP Cloud ALM, is not fully functional. 

For this reason you might see a gray rating for the connectivity status in the Data Quality Check in the Integration & Exception Monitoring UI. You can disregard this gray rating.