qRFC Monitor 

Report: RSTRFCM1

Use

Communication between R/3 and APO is based on the asynchronous transfer technique queued Remote Function Call (qRFC). This technique is used in the integration of SAP APO with an R/3 System, both for the initial data supply and incremental supply (R/3 à APO) and for the publication of planning results (APO à R/3).

The data is first buffered by the system it is sent from, then transferred to the target system. The advantage is that the initializing application does not have to wait for the update to be completed in the target system. However, return parameters cannot be delivered which means that potential error messages cannot be directly returned to the application.

The system differentiates between two types of error when processing qRFC modules:

  1. Communication errors These include:

Due to periodic repetition of the data transfer, communication problems should disappear of their own accord as soon as the network connection is available again.
  1. Application errors These include:

Application problems must be solved by a system administrator.

The qRFC is the central instance for monitoring application errors. It is available in both R/3 and APO. All transfer channels (queues) are displayed for all target systems.

Integration

The technical name for transfer channels relevant to R/3 – APO integration starts with CF.

CF_ADC_LOAD – the name of the transfer channel for the initial supply.

CFSLS0000010003 – the name of the incremental supply for the sales order number 10003

Prerequisites

Generation and activation of at least one integration model.

Ensure that you have maintained the settings for RFC destination (including the settings under TRFC options).

For further information, see Setting the RFC Destination

Features

To start the qRFC Monitor, select the transaction SMQ1 or Tools ® APO Administration ® Integration ® Monitor ® qRFC Monitor.

Transfer errors in the initial supply are recognized automatically and a dialog box appears which you can use to access the qRFC monitor.

This does not happen automatically in push supply (online supply), which means that when data is not transferred between APO and R/3, you must check for entries that are marked red in the qRFC monitor of the sending system. This check can happen automatically by means of the qRFC Alert (see also qRFC Alert).

You can double click on the rows to display all the function calls for the selected transfer channel. The highest function call blocks all other entries if an error occurs.

You can call up the current status text via the error short text. A detailed error log is always saved in the application log of the target system.

Automatic navigation from the qRFC monitor to the application log in question is not available in the current release.

See also: