Revision as of 07:04, 15 May 2016 edit Widefox (talk \| contribs) Autopatrolled, Extended confirmed users, Page movers, IP block exemptions, New page reviewers, Pending changes reviewers, Rollbackers 110,641 edits Added {{primary sources}} tag to article (TW) ← Previous edit		Revision as of 08:38, 16 March 2017 edit undo Boudewijn Waijers (talk \| contribs) 78 edits →RFC interfaces: SAP is pronounced es-aye-pee, not sap, so it requires "an" instead of "a". Next edit →
Line 17: 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 aan 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 aan 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.

Remote Function Call: Difference between revisions