The following programming example shows qRFC communication with an inbound queue (optional parameters are shown with '*'):
qRFC with Inbound Queue
REPORT rstrfct5. ... CALL FUNCTION 'TRFC_SET_QIN_PROPERTIES' EXPORTING QOUT_NAME = ' ' * QIN_NAME = * CALL_EVENT = ' ' * NO_EXECUTE = ' ' * EXCEPTIONS * INVALID_QUEUE_NAME = 1 * OTHERS = 2 . CALL FUNCTION 'rfc_function' DESTINATION rfcdest IN BACKGROUND TASK ( AS SEPARATE UNIT ) EXPORTING ... TABLES ... COMMIT WORK.
To execute a qRFC with an inbound queue, proceed as follows:
Specify the name of the outbound queue and, optionally, the inbound queue.
If you do not give a name for the inbound queue, the name of the oubound queue is used automatically.
Execute a tRFC call (CALL FUNCTION... IN BACKGROUND TASK).
Information about the queue is stored in the database table TRFCQIN. Other data is stored in the tables TRFCQSTATE and TRFCQDATA.
The QIN Scheduler activates a registered inbound queue as soon as this queue is filled.
The sending application cannot define the serialization of the qRFC LUWs in the inbound queue of the target system. The input field for the queue counter is ignored. The target system always creates a queue counter that is dependent on the time of the LUW entry itself.
For detailed information on programming the inbound queue, see: