With SAP Application Interface Framework (AIF) you can easily develop, run and monitor all the application interfaces your business needs. SAP AIF is an integral part of SAP S/4HANA and S/4HANA Cloud Edition for interface development, error and monitoring handling. And it is also available as add-on for the SAP Business Suite.

While SAP AIF has a local monitoring tool integrated, the messages sent through SAP AIF can be monitored also with SAP Focused Run to provide a centralized monitoring for all interface types and all systems in the SAP landscape.


Technical Prerequisites

SAP Application Interface Framework is the standard monitoring and interface hub for SAP S/4HANA and SAP S/4 HANA Cloud applications. AIF is now part of the S/4HANA core component and no longer needs to be installed as an add-on to the system.

To be able to monitor SAP AIF messages, you need:

  • FRUN 2.0 Feature Pack 01

  • S/4HANA running on SAP Basis 7.54 and SAP_ABA 75E or higher 

The formerly used ABAP add-on for SAP AIF in SAP ABAP systems with SAP Basis < 7.50 is not supported by SAP Focused Run.

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 'Technical Systems' tray and click on the pen icon in the upper right corner. This will open the 'Integration and Cloud Monitoring - Systems' 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

The available monitoring categories are:

  • AIF-bgRFC(queue): AIF monitored queued bgRFC interfaces
  • AIF-bgRFC(trans): AIF monitored transactions bgRFC interfaces
  • AIF-IDoc: AIF monitored IDoc interfaces
  • AIF-PI-runtime: AIF monitored PI interfaces
  • AIF-qRFC: AIF monitored qRFC interfaces
  • AIF-tRFC: AIF monitored tRFC interfaces
  • AIF-WS-runtime: AIF monitored web service interfaces

To monitor currently running interfaces and messages in the S/4 system please use transaction /n/AIF/ERR the setup of AIF is done in transaction /n/AIF/IFMON.


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. SAP 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

For AIF Monitoring you can always collect all messages collected by AIF for all categories. However, you can also use the following filter parameters, to restrict the data collection:


  • 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


  • 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

To find useful filters for the categories, it makes sense to collect all messages first. The filter values will be in the collection context of the collected messages in Advanced Interface Monitoring

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 message retrieved from SAP AIF the following metrics are collected:


  • 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 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]


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

Not for all monitoring categories, metrics are defined to create alerts.