The RFC interface is required to execute a remote function call. The RFC interface performs the following services:
- Calling and controlling the communication routines needed to communicate with the remote system
- Logging on to and log off from the remote system and authorization checks for the function groups used.
- Converting actual parameters to the format required in the remote system and vice-versa. This includes any platform-dependent conversions (for different code pages or byte sequences for example). The conversion supports all ABAP data types.
- Handling any communication errors and forwarding them to the caller if requested.
If the AS ABAP are not the same, two ABAP programs communicate using the RFC interface, whereas for communication between an AS ABAP and an external system, an ABAP program connects with a program in another programming language (C, C++, Visual Basic, Java or .NET).
For communication with programs in other programming languages, RFC libraries are available for all operating systems supported by SAP, including MS Windows, Unix and Linux:
- Java Connector (JCo) for Java
- .NET Connector for .NET (C#, VB.NET)
- RFC Software Development Kit (SDK) for C and C++
Each RFC that runs across the RFC interface on AS ABAP runs in its own user session. The logon data is usually stored in the RFC destination.
For more details about the RFC interface, see the
SAP NetWeaver documentation in SAP Help Portal.