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
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.
You can make the following settings in Customizing (see Setting Up Monitoring of tRFC and qRFC Calls):
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.
SAP Note 441269