Show TOC

Process documentationbgRFC Programming Locate this document in the navigation structure


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

Calling a Function Module

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

New Data Types

Exception Handling

Examples for Inbound and Outbound Processing

Locking a bgRFC Type t Unit

Locking a Queue

Filling Multiple Units in Parallel

Note Note

For a general introduction, see the qRFC documentation.

End of the note.