Data Interfaces

tRFC Syntax
© SAP AG
PROGRAM ASYN01.
.
.
.
CALL FUNCTION 'A'
DESTINATION '1'
IN BACKGROUND TASK
EXPORTING ...
TABLES ...
...
CALL FUNCTION 'B'
DESTINATION '1'
IN BACKGROUND TASK
EXPORTING ...
TABLES ...
COMMIT WORK.
In contrast to synchronous RFC, there is an additional parameter sequence called IN BACKGROUND
TASK
All RFC calls which contain this sequence and the same DESTINATION are stored in the database
using COMMIT WORK. These RFC calls form a Logical Unit of Work (LUW). The function
modules are executed in the target system in the same sequence in which they are submitted in the source
system.
This means that, for each target system, the RFCs submitted in a LUW form a Logical Unit of Work.
The called RFC-enabled function is executed once and only once.
Exactly Once!
This guarantees transaction integrity.
You cannot specify IMPORTING parameters with CALL.
External systems can benefit from the tRFC guarantee that a function module is executed once by using
the RFC API call RfcIndirectCall.