Entering content frameFunction documentation RFC Call - Example Program Locate the document in its SAP Library structure


An RFC (remote function call) is a function provided by another system which can call up and trigger a function module (an RFC function). You can find further information under Structure link RFC interface and Structure link RFC in SAP systems.

If you create a new data record in your operative system and want to immediately transfer it to the R/3 system (neartime), you can run a data transfer using an RFC. You can use this example program as a template for an RFC you can write for your operative (source) system.


There is an established system connection between the two systems.

You have defined a variant for external data transfer in the R/3 system. You can find further information under start external data transfer.


This program describes how you can start an external data transfer from a source system (in this example, an R/3 system named KI4) to another R/3 system (in the example, ALR). The data to be transferred is prepared in the source system in the format of the ABAP Dictionary structure used in the system ALR.

Two function modules have to be called up in the order given in the example:

First, function module FDU_EXPORT_GLOBAL_VARIABLES is run. This will export different parameters to the memory of the R/3 system. These parameters can be set online in the source system at the start of the transfer. In the example program you can enter parameters using PARAMETER statements. You should only use the parameters explained in the example program.

After this, function module EIS_DATA_TRANSFER_RKCT<nnn> is called up (where <nnn> the extension of the ABAP Dictionary structure RKCTnnn). You have to generate this module manually when defining the sender structure in Customizing by choosing Environment ® Generate RFC. The function module has to be given the name of the transfer program, the transfer type CPIC, and a table containing the data to be transferred. The example program can take the messages written in the log for further use in an internal table in the function module.

This graphic is explained in the accompanying text

When evaluating log entries, be aware that the messages in an EDT log can change over the course of several releases. Both the content and the name of a message can change. If messages are used in programs you developed, you should check them after changing releases.


  1. To be in a position to display the program coding, choose Tools ® ABAP workbench ® ABAP editor. The screen ABAP Editor: Initial Screen appears.
  2. In the field Program, enter KCFDURFC as the name of the example program.
  3. Under Sub-objects, you have to mark Source code.
  4. Choose Display. You land on the screen ABAP: Editor Display Program KCFDURFC. Now you can look at the coding.






Leaving content frame