qRFC Outbound Queue 

Purpose

qRFC is a layer between the application and tRFC. It only allows a LUW to be transferred to a target system if the participating queues do not contain any predecessor LUWs. Once a qRFC LUW has been executed, the QOUT Scheduler automatically executes the next qRFC LUW from the queue.

 

Features

qRFC with outbound queue enables serialization of the LUWs in the sending system. You can use qRFC with outbound queue with every tRFC-supported target system, as the call sequence is established in the application program. The target system does not therefore require any knowledge about the serialization. This applies to SAP and non-SAP systems when using the RFC Library.

When working with qRFC with outbound queue, you need to be aware of the following:

...

       1.      The queued RFC with outbound queue forces the pages in the sending system to be serialized. The target system is not informed of this serialization. This allows communication with any SAP target system with Release 3.0 and higher.

       2.      A LUW (transaction) can be distributed to multiple queues. However, it can only be transferred once all predecessor LUWs in all participating queues have been processed. After a qRFC transaction has been executed, the system tries to start all waiting qRFC transactions in sequence.

       3.      A queue name and a queue counter are required for each qRFC transaction for queue administration. Each tRFC call that needs to be serialized is assigned to a queue name that is determined by the application. The application programmer specifies the queue name when calling the function module TRFC_SET_QUEUE_NAME. This occurs directly before each RFC call that needs to be serialized.
There is no queue configuration, since this is a logical queue. An SAP system contains just one table for all outbound queues. This table records the names.