Show TOC

  qRFC Monitor

Use

Communication between the ERP system and the SCM system is based on the asynchronous transfer technique queued Remote Function Call (qRFC) . This technique is used for both the initial data transfer and the transfer of data changes. If your SCM system is SAP Advanced Planning and Optimization (SAP APO), it is also used to publish planning results from SAP APO to the ERP system.

The data is first buffered by the sending system and then transferred to the target system (outbound queue), or it is transferred from the sending system and then buffered by the target system (inbound queue).

The advantage here is that the sending system 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 returned directly to the component.

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

  1. Communication errors. These include:

    • Network problems

    • Non-existent RFC destination, etc.

    • Blocked objects (is dealt with as a communication error)

      As soon as the network connection is available again, a periodic repetition of the data transfer should solve communication problems.

  2. Application errors. These include:

    • Program errors

    • Missing posting of data to the target system

    • Missing master data for transaction data (only SAP APO)

      Application problems cannot be solved by the system itself and must be dealt with by a system administrator.

The qRFC monitor is used to monitor application errors in inbound and outbound queues. It is available in both the ERP system and the SCM system. All transfer channels (queues) are displayed for all target systems.

Integration

The technical name for all transfer channels relevant to the CIF integration starts with CF.

Example Example

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

CFSLS0000010003 – the name of the change transfer for the sales order number 10003

End of the example.

Prerequisites

Generation and activation of at least one integration model.

Note Note

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

For more information, see Defining the RFC Destination .

End of the note.

Features

To start the qRFC monitor for outbound queues, call transaction SMQ1 (report RSTRFCM1) or, on the SAP Easy Access screen, choose Start of the navigation path APO Administration Next navigation step Integration Next navigation step Monitor Next navigation step qRFC Monitor (Outbound Queues) End of the navigation path .

To start the qRFC monitor for inbound queues, call transaction SMQ2 or, on the SAP Easy Access screen, choose Start of the navigation path APO Administration Next navigation step Integration Next navigation step Monitor Next navigation step qRFC Monitor (Inbound Queues) End of the navigation path .

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

In the case of the online transfer, this does not happen automatically, which means that if data is not transferred, you must check for entries that are marked red in the qRFC monitor of the sending system. (If you work with SAP APO, this check can be performed automatically by the qRFC alert.)

You can double-click 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 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 is supported from the qRFC monitor to the affected application log. See also SAP Notes 396838 and 396839.

See Displaying Entries in Application Log .

If you work with bgRFC, you can use the bgRFC monitor (transaction SBGRFCMON in the ERP system and SBGRFCMON1 in the SCM system).