A remote function call (RFC) is the call of a remote-enabled function module (RFM) in a partner system. The caller is the RFC client and the called partner is the RFC server. Information about the server is stored on the client side in table RFCDES. RFC destinations are maintained in transaction SM59. The remote destination can be another application server in the same or a different R/3 System, an R/2 System, or a non-SAP system.


Technical Prerequisites

The following technical prerequisites have to be met in order to use the RFC monitoring:

  • The managed system is ABAP based system with basis release ≥ 7.0
  • The managed system as at least ST-PI  2008_1 SP06 or higher

Performance measurements are based on Real-User Monitoring (RUM) which is also a part of Focused Run. When RFC performance monitoring is set up, RUM is automatically configured in the background.

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:

  • RFC (Performance): Response time of the RFC destination based in Real-User Monitoring data
  • Connection Monitoring (SM59): Availability of RFC destination defined in SM59 in the ABAP system

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

RFC (Performance) 

For RFC Performance Monitoring, you can collect all RFC destinations in the managed system. You can also use the following filter parameters, to restrict the data collection:

  • Function Module: The name on the called function module that you want to monitor, as seen in RUM.

Connection Monitoring (SM59) 

For Connection Monitoring (SM59) you have to provide at least the connection type and the connection name:

  • Connection Name: Name of the RFC destination as in SM59
  • Connection Type: Type of the RFC destination as in SM59

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 interfaces of type RFC the following metrics are collected:

RFC (Performance)

  • RFC Response Time: The average response time of the RFC requests measured in RUM

Connection Monitoring (SM59)

  • Not available (via ping) RFC Destinations: Indicates that RFC destinations have not been available via RFC ping during the last collection interval
    Metric parameters:
    • LAST_N_MEASUREMENTS = Only consider the RFC if it wasn't available for the last N measurements
  • Not available (via logon) RFC Destinations: Indicates that RFC destinations have not been available via logon check during the last collection interval
    Metric parameters:
    • LAST_N_MEASUREMENTS = Only consider the RFC if it wasn't available for the last N measurements
  • RFC Latency: Latency of the RFC destination