Entering content frameFunction documentation Transactional RFC and Queued RFC Monitor Locate the document in its SAP Library structure

Use

Structure linkTransactional RFC and Structure linkqueued RFC are variants of the Remote Function Call that make the data transfer between different SAP R/3 systems more reliable and more secure.

Transactional RFC guarantees the following attributes:

If the target system is not available when the call is made, the call remains in the local wait queue. The calling dialog program can, however, proceed. If the target system does not become active within a certain amount of time, the call is scheduled as a background job.

Although tRFC significantly improves the reliability of the data transfer, it also has disadvantages. This method does not ensure that the sequence of LUWs specified in the application is observed. However, there is a guarantee that all LUWs will be transferred at some point.

Queued RFC (qRFC with Outbound Queue)

To offset this disadvantage, a serialization of tRFC is performed using wait queues. It is called queued RFC (qRFC). With this serialization, an outbound queue for tRFC was created in SAP R/3, which is therefore referred to as qRFC with outbound queue. The main features of qRFC are as follows:

qRFC with Inbound Queue

Serialization of the incoming RFC calls from other systems is also possible. This ensures that incoming calls are always executed in the order of their arrival. This serialization of incoming calls also limits the maximum load on the target server caused by RFC.

Monitoring with the Alert Monitor

Using the Transactional RFC and Queued RFC subtree, you can quickly detect errors and blocked queues (in the context of transactional RFC and queued RFCs). The corresponding special monitors with which you can quickly eliminate the cause of the error are set as analysis methods. The subtree is in the Communications monitor of the SAP CCMS Monitor Templates monitor set.

Prerequisites

You have performed the setting up of the monitoring of qRFC calls.

Features

This graphic is explained in the accompanying text

The following table provides information about the monitoring tree elements (MTEs) of this monitor:

MTE

Description

ARFCSSTATE: Outbound tRFC Calls

Monitoring object with information about the LUWs and tRFC calls that are waiting to be executed on their target system or on an external component.

Calls w/ Communication Errors CPICERR

Number of tRFC calls that were not executed due to problems creating the connection or the communication with the target system or an external component; depending on the settings (transaction SM59), the attempt may be repeated a number of times

Calls w/ Execution Errors SYSFAIL

Number of tRFC calls that could not be executed due to a problem with the execution in the target system or an external component

Calls w/o Server Resources SYSLOAD

Number of tRFC and qRFC calls with outbound queue with status SYSLOAD; these are calls that could not be executed due to a lack of resources in the target system

ARFCSSTATE: Inbound tRFC/qRFC Calls

Monitoring object with information about tRFC and qRFC calls that are waiting to be executed in this system; after they have been executed, they are deleted from table ARFCRSTATE

Total Calls

Number of tRFC and qRFC calls that are waiting to be executed in this system and are therefore stored in table ARFCRSTATE

Outbound Queues

Subtrees that contain the log messages of the outbound qRFC calls to external systems; these messages are sorted by the different queue groups: there is a monitoring object for each group with the name <Group Name> Outbound Queues

Inbound Queues

Subtrees that contain the log messages of the inbound qRFC calls from external systems; these messages are sorted by the different queue groups: there is a monitoring object for each group with the name <Group Name> Inbound Queues

Blocked queues: Client <Number>

Log messages for the queues of an application, sorted by the different clients; the log messages contain the error messages that are returned during the qRFC call

Queues not processed: Age Alerts

Log messages for the queues of an application; the queues have not been processed for longer than the time defined in the associated threshold value (by default, seven days)

QIN Schedulers: Errors

Monitoring object that contains information about the status of the QIN scheduler; the QIN scheduler controls the processing of incoming tRFC and qRFC calls within a client (see SAP Note 396007)

QOUT Schedulers: Errors

Monitoring object that contains information about the status of the QOUT scheduler; the QOUT scheduler limits the maximum number of parallel tRFC and qRFC connections to an RFC destination (see SAP Note 400330)

QIN Scheduler Error: All Clients

Log messages with error messages for the QIN schedulers of all clients; an alert here indicates that the system could not process an incoming RFC call due to a communication or execution error

QIN Unregistered Queues: All Clients:

Log messages with error messages for the QIN schedulers of all clients; an alert here indicates that the scheduler found an RFC call with a non-registered queue

QOUT Scheduler Error:
All Clients

Log messages from communication and system errors for the QOUT schedulers of all clients

Activities

To start the monitor, follow the procedure below:

  1. Start the Alert Monitor using transaction RZ20 or choose CCMS ® Control/Monitoring ® Alert Monitor.
  2. On the CCMS Monitor Sets screen, expand the SAP CCMS Monitor Templates set.
  3. Start the Communications monitor from the list by double clicking it.
  4. Expand the Transaction RFC and Queued RFC subtree.

Procedure if an Alert Is Triggered

MTE

Procedure

ARFCSSTATE: Outbound tRFC Calls

The transaction Transactional RFC (SM58) is assigned as analysis method to all MTEs of this monitoring object. This tool displays a list of all transactional RFCs that could not be successfully completed or that had to be scheduled as background jobs.

Calls w/Communication Errors - CPICERR

Errors often occur in this attribute when an instance is shut down for maintenance. Once the instance is available again, the calls are automatically processed.

If this is not the case, you should check the RFC connection using the Display and Maintain RFC Destinations transaction (SM59).

Calls w/ Execution Errors - SYSFAIL

Errors in the execution of RFC calls are often caused by errors in the programs. These errors must therefore usually be individually processed.

Calls w/o Server Resources - SYSLOAD

RFC calls with the status SYSLOAD are automatically scheduled in a job. For more information about SYSLOAD status, see SAP Note 319860.

ARFCSSTATE: Inbound tRFC/qRFC Calls

For information about possible statuses and problems for table ARFCRSTATE, see SAP Notes 378903 and 366869.

Outbound Queues
Inbound Queues

Start the assigned analysis method. For the MTEs of this monitoring object, this is transaction SMQ1 or SMQ2 (qRFC Monitor).

QIN Schedulers: Errors
QOUT Schedulers: Errors

Start the assigned analysis method. For the MTEs of this monitoring object, this is transaction SMQR or SMQS (QIN/QOUT Scheduler).

See also:

Monitoring qRFC and tRFC Calls

Leaving content frame