SAP RFC STATEMENTS documentation, setup help and example usage

ARTICLE

RFC Calls
The following additions of the CALL FUNCTION
statement cause a Remote Function Call:

DESTINATION for a synchronous RFC ( sRFC )

If the DESTINATION addition is specified without one of the following two additions, the calling program waits until the remotely called function has finished.

STARTING NEW TASK for an aynschronous RFC ( aRFC ) and its parallel RFC variety ( pRFC

)

With the STARTING NEW TASK addition, the system continues to process the calling program as soon as the remotely called function is started, without waiting for the latter function to finish. The results are received in callback routines.

IN BACKGROUND UNIT|TASK for a Background RFC ( bgRFC ) or a transactional RFC ( tRFC

) and the variety thereof, queued RFC ( qRFC ).

With the IN BACKGROUND addition, the remotely called function is designated for execution and started with a COMMIT WORK statement.

Note
Background RFC ( bgRFC ) is an enhanced successor of
tRFC (and qRFC ). At the moment, all variants can still be used. However, SAP strongly recommends that you use the bgRFC instead of the tRFC .

More Information
For a detailed description of RFC calls, see

CALL FUNCTION - RFC

Additional information is also available in the SAP Library in the following section:

Calling RFC Function Modules in ABAP

Documentation extract taken from SAP system, � Copyright SAP AG. All rights reserved