One of the most noticeable differences to classic qRFC is the reduced importance of the queues in the processing of the units. The queues have finished their work after the sequence of the units has been determined. This is done when the unit is saved to the database, which is when the COMMIT WORK of the application is performed.
The following sections offer a detailed introduction to the features of the bgRFC type q and bgRFC type t:
API of bgRFC Type t and bgRFC Type q
Transactional Consistency Check
Creating a Destination Object and Unit Objects
Manipulating a Background Unit
Using Queues to Lock and Unlock Units
RFC Client-Side Runtime Control
RFC Server-Side Runtime Control
Examples for Inbound and Outbound Processing
Filling Multiple Units in Parallel
For a general introduction, see the qRFC documentation.