tRFC and qRFC

Use

SAP Application Interface Framework supports role-based monitoring of tRFC and qRFC interfaces. In Monitoring and Error Handling, business users can monitor messages and handle errors related to tRFC and qRFC interfaces.

Integration

SAP Application Interface Framework enables you to monitor tRFCs and qRFC transactions that have a “pending” (in error) status. It works on top of standard t/qRFC monitoring, functionalities, and persistence. Existing t/qRFC interfaces and function modules are not modified for monitoring in SAP Application Interface Framework.

In order to monitor tRFC and qRFC interfaces with SAP Application Interface Framework, you have to define SAP Application Interface Framework interfaces. For each t/qRFC function module, you have to create an SAP Application Interface Framework interface with the corresponding SAP structure to display all the required parameter values.

For both tRFC and qRFC, central monitoring (for example, in SAP ECC) and also local monitoring (for example, in SAP APO) are supported. You can configure from which system(s) the data is read and in which system the monitoring is done.

Prerequisites

Before you can make t/qRFC integration settings, you have used the SM59 transaction code to define RFC destinations that link the external systems with SAP Application Interface Framework.

Features

The following are the major components of the tRFC/qRFC integration into SAP Application Interface Framework and each component is described in detail in the following sections or linked topics:

  • A Function Module Generator report (transaction code /AIF/RFC_FUNC_GEN for single generation and transaction code /AIF/RFC_MASS_GEN for mass generation)

    Fore more information, see tRFC and qRFC Function Module Generator.

  • A read function

  • A Data Transfer report

  • Customizing

  • Engines

    See tRFC and qRFC for lists of the appropriate engines.

Read Function

The read function reads the following data that is required in SAP Application Interface Framework:

  • Logical units of work (LUW)

  • Parameters of the called function modules

  • Additional application logs written by the functions

As the read function gets the list of the already known LUWs (the transaction IDs with timestamp), it determines which LUWs are new, changed, or deleted; the parameters and additional data is only read for new or changed data.

The read function writes the values of the parameters into the specific SAP structures that are generated by the Function Module Generator (see tRFC and qRFC Function Module Generation).

Data Transfer

The read function is called by the Data Transfer report, which saves the data in the persistency of SAP Application Interface Framework and converts it into the required data format for Monitoring and Error Handling.

The Data Transfer report is used to support several technologies including tRFC, qRFC, CIF postprocessing, and batch input (see Data Transfer).

Customizing

  • In Customizing for SAP Application Interface Framework under Start of the navigation pathSystem Configuration  Next navigation step Configure Data TransferEnd of the navigation path, you make settings to enable the Data Transfer report to transfer t/qRFC data into the persistence of SAP Application Interface Framework.

  • You have to assign engines to interfaces in Customizing for SAP Application Interface Framework under Start of the navigation pathInterface Development Next navigation step Additional Interface Properties Next navigation step Specify Interface EnginesEnd of the navigation path.

  • Use Customizing for SAP Application Interface Framework to make detailed settings for the generated interface.

Engines

See tRFC and qRFC for the appropriate engine settings.

The required functions for the application engine for the t/qRFC integration are:

  • Restart

  • Cancel

  • Debug

    The Debug pushbutton works dynamically as follows:

    • tRFC

      Only outbound queues are supported

    • qRFC

      Both inbound and outbound queues are supported

More Information

For more information about transferring t/qRFC related data to the persistence of SAP Application Interface Framework, see Data Transfer.