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.
The following technical prerequisites have to be met in order to use the tRFC monitoring:
On the managed system, use transaction SM58 to check whether there are tRFC entries present.
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.
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:
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 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:
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.
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:
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.
For interfaces of type tRFC the following metrics are collected:
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.