Hi

[Former Member]

Wats meant by this sRFC,tRFC and qRFC?

Rgds

Ruchitha.

[Former Member · Accepted solution]

Hi

With <b>synchronous RFC</b>, processing stops in the calling program until the called remote function is processed and its output is returned. Then in the calling program, the processing continues after the call.

In an <b>asynchronous</b> Remote Function Call, the called remote function is started and then continues processing on its own immediately in the calling program. Remote function processing is separate from the calling program. The function output can be received later in the program.

Asynchronous RFC is intended for parallel processing of processes.

Whereas with synchronous and asynchronous RFC each call makes up a single logical unit of work (LUW) in the remote system, you can use <b>transactional</b> RFC to bundle several remote functions into one LUW (with an automatic rollback mechanism in case of error).

With tRFC, generated LUWs are processed independently of each other. This means, the order in which they are processed is not always the order in which they are generated.

To ensure that tRFC-LUWs are processed in the same order as they were generated, you can use qRFC as an extension of tRFC.

qRFC is available as of Release 4.6A and can be used in R/3-R/3 connections as well as R/3-external connections.

Get back if you have more doubts.

Thanks

[santhosh_kumarv]

>>sRFC

synchronous RFC (sRFC), which required both participating systems to be active to form synchronous communication

>>tRFC

transactional Remote Function Call(tRFC) is responsible for actually sending communications

>>qRFC

tRFC is preceded by inbound and outbound queues, which have led to the name queued Remote Function Call(qRFC)

Regards

San

there is a Way.