tRFC

Via tRFC, data can be transferred safely and reliably between applications. The RFC client calls a specific function module on the RFC server. The called function module is executed exactly once on the server. The resulting data is then stored temporarily in the SAP database under a unique transaction ID (TID), that is, data creation and data transmission are two separate processes. The tRFC is used for example to send business documents from one SAP system to another SAP system, often by using the ALE/IDoc layer.

One or several functional module calls can be grouped into a single tRFC LUW (logical unit of work). Due to its asynchronous nature, the tRFC can handle situations where the called remote system is not available at the time of posting. In such a case a reprocessing is triggered by the tRFC framework.

 

Technical Prerequisites

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

  • The managed system is ABAP based system with basis release ≥ 7.00 (RFC client)

On the managed system, use transaction SM58 to check whether there are tRFC entries present.

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:

  • tRFC: tRFC entries send from the ABAP system (Monitoring transaction SM58)

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

tRFC 

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

  • RFC Destination: The name of the RFC destination the tRFC is sent over (see SM59)
  • Function Module: The name on the called function module (see SM58)
  • User: The user in the RFC destination (see SM58)
 

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 tRFC the following metrics are collected:

tRFC 

  • Number of tRFC entries: Number of entries that fall in the selected status group
    Metric parameters:
    • STATE_GROUP = CRITICAL, INTERIM
  • Age of oldest tRFC entry: Age of the oldest entry that falls in the selected status group
    Metric parameters:
    • STATE_GROUP = CRITICAL, INTERIM
 
 

Further Information

The following status codes are taken into account for error and interim statuses:

Severity tRFC Status Code
Critical ANORETRY, ARETRY, CPICERR, RETRY, SYSFAIL, VBERROR
Interim AFINISH, CONFAIL, DEBUG, EXECUTED, MAILED, READ, RECORDED, SENDED, SYSLOAD, VBRECORD, VXRECORD

The term “Critical” as used above indicates an immediate error state, with no automatic reprocessing, manual action is required. The term “Interim” indicates a temporary error or backlog situation only. Usually automatic reprocessing is in place.