Monitoring qRFC and tRFC Calls

Transactional RFC and queued RFC are variants of the Remote Function Call that make the data transfer between different systems more reliable and more secure. You can monitor these calls using the Alert Monitor. To do this, in the Communications monitor of the SAP CCMS Monitor Templates monitor set, there is a Transactional RFC and Queued RFC subtree. These functions automatically become active at the start of the system; you can, however, maintain and extend the functions.

Monitored Objects in the Transaction RFC and Queued RFC Subtree

• The number of outbound transactional RFC calls that could not be processed due to errors is reported. These errors include data transfer errors (the target server is not reached), execution errors in the target server, or resource errors (there are not enough servers in the RFC server group). Alerts are generated if the number of calls with errors exceeds the threshold value.
• The number of inbound calls from transactional and queued RFCs that are waiting for processing is reported. An alert is generated if the number of waiting calls exceeds the threshold value.
• Error messages for inbound and outbound qRFC queues are reported. An error message means that the affected queue cannot be processed and that all other calls for the queue must wait until the error is corrected. The following applies here:

  By default, a red alert is generated for every queue error. Only one alert is generated for an error, irrespective of how often the error is reported in the monitoring architecture. This means that you do not need to react to multiple notifications of the same problem. If you delete or complete an alert, a new alert can be generated if a queue error occurs.

  The errors are grouped by client; all clients are monitored for queue errors.

• Transfer and execution errors for inbound and outbound RFC schedulers are reported. The monitoring tree for inbound schedulers also reports about queues that are not registered for processing. Calls to these inbound queues are not executed until the queues are registered.

You can make the following settings in Customizing (see Setting Up Monitoring of tRFC and qRFC Calls):

• You can create separate subtrees for the messages of individual queues that you specify by name.
• You can perform extended monitoring for every subtree by specifying exit function modules.
• For every subtree, you can change the color of the alert from red to a lower level, or set no alert to be generated.

By default, the tRFC/qRFC monitor is delivered by SAP without Customizing. This means that all queue errors are monitored in a single subtree. No exit function modules are executed to extend the monitoring functions or to change the alert values.

Some SAP applications provide Customizing for this monitor or make recommendations for Customizing. For recommendations about Customizing qRFC monitoring, see the installation guidelines for the applications.

To monitor tRFC and qRFC calls, use the Transactional RFC and Queued RFC monitor.

More information:

SAP Note 441269