Remote Function Call
|This article relies too much on references to primary sources. (May 2016) (Learn how and when to remove this template message)|
|This article needs additional citations for verification. (August 2015) (Learn how and when to remove this template message)|
Remote Function Call is the proprietary SAP SE interface. Remote Function Call (RFC) is the standard SAP interface for communication between SAP systems. The RFC calls a function to be executed in a remote system. Remote function calls may be associated with SAP software and ABAP programming and provide a way for an external program (written in languages such as PHP, ASP, Java, or C, C++) to use data returned from the server. Data transactions are not limited to getting data from the server, but can insert data into server records as well. SAP can act as the Client or Server in an RFC call.
A Remote Function Call (RFC) is the call or remote execution of a Remote Function Module in an external system. In the SAP system, these functions are provided by the RFC interface system. The RFC interface system enables function calls between two SAP systems. There are 3 different versions of RFC communication:
- The first version of RFC is synchronous RFC (sRFC).
- Transactional RFC (tRFC, also originally known as asynchronous RFC)
- Queued RFC (qRFC)
The RFC interface system is made up of the following interfaces:
- Calling interface for ABAP programs
- Each ABAP program can call a remote function module using the command CALL FUNCTION...DESTINATION. The parameter DESTINATION informs the SAP system that the called function module runs in a different system to the calling system. RFC communication with the remote system takes place as a part of the CALL FUNCTION command.
- RFC function modules in a SAP system must be proper function modules and must be registered in the SAP system as remote.
- If the calling program and the called program are both ABAP programs, the RFC interface provides both communication partners. The calling program can be any ABAP program, and the called program must be a function module that is registered as remote.
- Interfaces for calling non-ABAP programs
If either the calling program or the called partner is not a SAP program, it must be programmed in such a way that it can play the role of the other partner in RFC communication.
To implement RFC partner programs in non-SAP systems, read: Components of the SAP Communication Technology.
RFC-supported and GUI-supported interfaces can be used by external programs to call function modules in SAP systems, and execute them in these systems. Likewise, ABAP programs can also use these interfaces to use functions supplied by external programs.
Functions are remote-enabled by setting the "Remote-enabled module"-flag in the Attributes tab of the ABAP Workbench: Function Builder (transaction SE37).