topic Re: rfc in Application Development and Automation Discussions

rfc

Former Member — Tue, 29 May 2007 09:35:44 GMT

How many types of RFCs are there?

Re: rfc

srinivas_akiri — Tue, 29 May 2007 09:37:42 GMT

Hi,

we can call all RFC in three modes

Synchroneous RFC

Asynchroneous RFC

Transactional RFC

Queue RFC

Thanks

Srini

Re: rfc

Former Member — Tue, 29 May 2007 09:38:05 GMT

there r 4 types of rfcs

1)synchronous

2)asynchronous

3)transactional

4)queued rfc.

rgds,

bharat.

Re: rfc

Former Member — Tue, 29 May 2007 09:38:24 GMT

There will be some 8 types ( 2,3,G,H,I,L,T and X)

go to SM59 and see

RFC (Remote Function Call) is similar to the general SAP fun module: except that in the attributes you click the radio button: RFC enabled;

and you will be passing an Import parameter DESTINATION to it.

Other code and usage will be similar to any fun module;

Have a look at any fun module in SE37 to understand better about the different components of Fun modules;

Refer this link:

http://help.sap.com/saphelp_nw04/helpdata/en/22/042518488911d189490000e829fbbd/frameset.htm

Reward points if useful

Regards

Anji

Message was edited by:

Anji Reddy Vangala

Re: rfc

Former Member — Tue, 29 May 2007 09:40:58 GMT

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

Re: rfc

Former Member — Tue, 29 May 2007 09:43:32 GMT

Hi,

These are the types of RFC :

Asynchronous RFC (aRFC)

Synchronous RFC (sRFC)

Transactional RFC (tRFC)

Queued RFC (qRFC)

Parallel RFC (pRFC)

RFC:

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.

Asynchronous RFC :

This is used when you need to increase the performance of ABAP program by having system call more than one function module in parallel than forcing the program to wait for results .

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:

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 Info,

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

Regards,

Padmam.