What is the difference between trfc and qrfc

Using aRFC is always a good idea when real-time communication is established with a remote system, where processing in the calling program should not be interrupted until the results of the called function module have been obtained the term asynchronous is used in this sense here.

If a call is sent, and the receiving system is down, the call remains in the local queue until a later time. The calling dialog program can proceed without waiting to see whether or not the remote call was successful.

If the receiving system does not become active within a certain amount of time, the call is scheduled to run in batch. Within a LUW, all calls are. Implementation of tRFC is recommended if you want to maintain the transactional sequence of the calls.

Due to the amount of activated tRFC processes, this procedure can reduce performance significantly in both the send and the target systems. In addition, the sequence of LUWs defined in the application cannot be kept.

It is therefore impossible to guarantee that the transactions will be executed in the sequence dictated by the application. The only thing that can be guaranteed is that all LUWs are transferred sooner or later. Former Member. November 5, 1 minute read. Alert Moderator. Alerting is not available for unauthorized users. Assigned Tags. Similar Blog Posts. Related Questions. 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. To offset this disadvantage, a serialization of tRFC is performed using wait queues. With this serialization, an outbound queue for tRFC was created, which is therefore referred to as qRFC with outbound queue. The main features of qRFC are as follows:. Serialization of the incoming RFC calls from other systems is also possible.

Transactional RFC guarantees the following attributes: — The call is executed exactly once in the target system. 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 time period, the repeated call is scheduled as a background job.

However, it does guarantee that all LUWs will be transferred at some point. The special features of qRFC are, above all: — 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. Each tRFC call that is to be processed chronologically is assigned a queue name determined by the application.

Regards, LEH.