qRFC Design
qRFC communication consists of nothing more than tRFC communication with a preceding inbound queue and outbound queue. tRFC communication is typically constructed as follows:
tRFC Communication
|
report rstrfct0.
... call function ’rfc_function’ destination rfcdest in background task ( as separate unit )
exporting ...
tables ...
... commit work.
|
All data that belongs to a tRFC call (Call Function ... in Background Task) in an LUW is saved to two internal tables with a transaction ID (TID).
At COMMIT WORK time, the contents of these internal tables to the database (ARFCSSTATE and ARFCSDATA). The RFC Manager then requires a DIALOG work process to send this LUW to the partner system.
You can find detailed information about qRFC design in:
● Using qRFC with the RFC Library