RFC

[Former Member]

what is RFC and what is it's use in ABAP?

[Former Member]

Hi,

They are nothing but the function module. They are called as remote function module as they can be called from other systems

Check below link for further details

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm

Have a look at this link.

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCFESDE2/BCFESDE2.pdf

http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c7567...

Please go through the following link. You will get good info on RFC & its types.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/f078394a-4469-2910-c4bf-853c7567...

Regards

[Former Member]

RFC means Remote Function Call.

Remote Function Call:

RFC is an SAP interface protocol. Based on CPI-C, it considerably simplifies the programming of communication processes between systems.

RFCs enable you to call and execute predefined functions in a remote system - or even in the same system.

RFCs manage the communication process, parameter transfer and error handling.

http://help.sap.com/saphelp_47x200/helpdata/en/22/042860488911d189490000e829fbbd/frameset.htm.

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.

Synchronous RFC:

The first version of RFC is synchronous RFC (sRFC). This type of RFC executes the function call based on synchronous communication, which means that the systems involved must both be available at the time the call is made.

Transactional RFC (tRFC) and Queued RFC (qRFC). tRFC is used mainly to transfer ALE Intermediate Documents (IDocs).

Transactional RFC:

If an error occurs during a synchronous remote function call, the system cannot tell at what point the error occurred (most crucially, whether the function module was actually processed in R/3 before the operation failed). Restarting a failed call is therefore a dangerous thing to do, since you risk duplicating a completed function call.

To alleviate this problem, you can use transactional RFC, which guarantees that each function call you issue will only be executed once, even if you submit it repeatedly to the R/3 System. The system implements this safeguard by assigning a unique transaction ID (TID) to each transaction that you submit. When you attempt to process the transaction, the system checks whether that TID has already been processed. If it has, the transaction is ignored.

Queued RFC:

When you use transactional RFC, you cannot guarantee the order in which the function calls will be processed in the system (it is quite possible that one call might overtake another). For cases where you need to specify a particular processing order, you can use queued RFC, which is an extension of transactional RFC. In qRFC, you place each function call in a logical queue. A function call cannot be executed until all of its predecessors in the queue have been processed. Queued RFC calls are processed asynchronously

For more information on RFC, please go through the link.

http://help.sap.com/saphelp_nw04/helpdata/en/6f/1bd5b6a85b11d6b28500508b5d5211/content.htm

RFC Use in ABAP :

You can use the CALL FUNCTION statement to call remote functions, just as you would call local function modules. However, you must include an additional DESTINATION clause to define where the function should run:

CALL FUNCTION (RFC Name) DESTINATION Dest

EXPORTING

F1 = a1

F2 = a2

IMPORTING

F3 = a3

CHANGING

F4 = a4

TABLES

t1 = ITAB

EXCEPTIONS

…

Just Refer these links to know about RFC.

http://help.sap.com/saphelp_nw04s/helpdata/en/22/0424ba488911d189490000e829fbbd/frameset.htm

http://help.sap.com/saphelp_nw04s/helpdata/en/22/0424ba488911d189490000e829fbbd/frameset.htm

[Former Member]

RFC (Remote Function Call) is an extension of CALL FUNCTION in a distributed environment. Existing function modules can be executed from within a remote system (R/2 or R/3) via an RFC Call. Adding a Destination clause to the CALL FUNCTION statement does this.

The destination parameter displays an entry in the RFCDES table (which is defined with t.code SM59). This entry contains all necessary parameters to conect to and log in the destination system. The RFC API on OS/2, Windows, Windows NT and all R/3 based UNIX platforms makes it possible to use the RFC functionality between an SAP System and a non SAP System.;

When you make an RFC call the RFC interface takes care of:

- Converting all plarameter data to the representation needed in the remote system. This includes character string conversions, and any hardware-dependent conversions needed.

- There is no support for Dictionary structures.

- Calling the communication routines needed to talk to the remote system.

- Handling communications errors, and notifying the caller, if desired.

Processing for calling remote programs is built into the CALL FUNCTION statement. Processing for being called is generated automatically for every function module registered as remote.

A distinction is made between an RFC Client and RFC Server. RFC Client is the instance that calls up the remote function call to execute the function that is provided by the RFC Server.

Rewards if useful.

[Former Member]

hi vinothini,

RFC is nothing but calling a function module which is present in remote server.

if suppose u r working in a server , FM is pesent in different seerver, if u want to retrive the values from that server, u have to use RFC at that time.

regards

karthik