TRFC & QRFC

[Former Member]

What is TRFC and QRFC?

Some one said TRFC is Asynchronous and QRFC is Synchronous, but I am not convinced or I am not clear with that.could some explain me pleas.e

[former_member91687]

Hi Mohan,

A tRFC is simply a renaming of what was known as asynchronous RFC. This is achieved by calling an RFC in a background task. When you serialize either for an inbound or outbound queue you would call that a Qrfc.

If you need detailed explanation have a look at this link:

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

Do get back if you need further clarifications.

Regards,

Chandra

[former_member187339]

Hi,

Refer these threads:

Regards

Suraj

[Former Member]

Hi,

+What is TRFC and QRFC?

+

They are variants of remote function calls

Refer, http://help.sap.com/saphelp_nw04/helpdata/en/8b/ceea3b31aac554e10000000a114084/content.htm

"Transactional RFC guarantees the following attributes:

· The call is executed exactly once in the target system.

· Calls that belong to a Logical Unit of Work (LUW) are either completely executed, or not executed at all.

If the target system is not available when the call is made, the call remains in the local wait queue. The calling dialog program can, however, proceed. If the target system does not become active within a certain amount of time, the call is scheduled as a background job.

Although tRFC significantly improves the reliability of the data transfer, it also has disadvantages. This method does not ensure that the sequence of LUWs specified in the application is observed. However, there is a guarantee that all LUWs will be transferred at some point.

Queued RFC (qRFC with Outbound Queue)

To offset this disadvantage, a serialization of tRFC is performed using wait queues. It is called queued RFC (qRFC). With this serialization, an outbound queue for tRFC was created in SAP R/3, which is therefore referred to as qRFC with outbound queue. The main features of qRFC are as follows:

· A LUW is only transferred if it has no predecessor (in reference to the sequence defined in the applications) in the participating queues. After a qRFC transaction is executed, the system attempts to start the next qRFC transaction in the sequence from the queue.

· A queue name and a queue counter are required fore each qRFC transaction for queue administration. Each tRFC call that is to be processed chronologically is assigned a queue name determined by the application."

Hope this helps you,

Anirban.