Remote Function Call: Difference between revisions

Revision as of 13:21, 5 August 2015

Revision as of 04:27, 6 August 2015

Line 1:

{{about|the SAP technology|generic term|remote procedure call}}

{{unreferenced|date=August 2014}}

'''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. <ref>[https://help.sap.com/saphelp_nw70/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/frameset.htm RFC documentation by SAP]</ref>. Remote function calls may be associated with [[SAP AG|SAP]] software and [[ABAP]] programming and provide a way for an external program (written in languages such as [[PHP]], [[Active Server Pages|ASP]], [[Java (Sun)|Java]], or [[C programming language|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.

==Technical overview==

A Remote Function Call (RFC) is the call or remote execution of a Remote Function Module in an external system.

In the [[SAP AG|SAP]] system, these functions are provided by the RFC interface system. The RFC interface system enables function calls between two SAP systems.

There are 4 different versions of RFC communication:<br />

# ''The first version of RFC is synchronous RFC (sRFC).''<br />

# ''Transactional RFC (tRFC, also originally known as asynchronous RFC)''

# ''Queued RFC (qRFC)''

Line 20:

*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.

Line 36:

* [[SAP SE]]

* [[Oracle Call Interface]]

==References==

{{Reflist}}

==External links==