Queued RFC is a variant of the Remote Function Call that makes the data transfer between different systems more reliable and more secure; among other things, queued RFC guarantees chronological processing of RFC calls.
For monitoring tRFC and qRFC calls, there is the Transactional RFC and Queued RFC subtree in the Alert Monitor. For information about the structure of the subtree, see Transactional RFC and Queued RFC Monitor . This section describes how to set up the monitoring.
For optimal usage of qRFC, there are different queues for different applications, so that a blocked queue does not affect the other application processes. These queues are differentiated using their names; in this way, you can assign each queue to the associated application.
To provide a better overview, each of these queues that is being monitored using the monitoring architecture should be assigned a separate subtree. Without Customizing, all queue errors are reported in a single subtree. You can create the desired monitoring subtrees in Customizing. You can make the following changes:
Default Customizing settings are delivered for applications and components that use the qRFC monitoring data. This means that the associated subtrees should already be active after delivery. You only need to perform more far-reaching Customizing if the default Customizing does not meet your particular needs.
Your Customizing changes become active the next time the data collection method CCMS_tRFC_Collector runs. By default, this method runs every 15 minutes.
SAP Note 441269