Data Interfaces

tRFC: Tables and Scheduling
ABAP/4 progam
CALL FUNCTION ...
IN BACKGROUND TASK
EXPORTING ...
TABLES ...
CALL FUNCTION ...
IN BACKGROUND TASK
EXPORTING ...
TABLES ...
COMMIT WORK.
Transaction
SM58
© SAP AG
ARFCSSTATE
Transactional RFC Log file
ARFCSDATA
DB
Caller FM Target system Date Time Status
PAUL xyz R3B 06.07.95 14.00 --
By using CALL FUNCTION ... IN BACKGROUND TASK, you store the called data in internal
tables.
COMMIT WORK stores the context data of the function calls in the database (general data such as the
name of the function module in table ARFCSSTATE; concrete data passed with CALL in table
ARFCSDATA). Then, the send job is scheduled.
The send job reads the database tables ARFCSSTATE and ARFCSDATA and tries to set up a
connection to the partner system. If an error occurs, the send job is re-scheduled.
You can analyze the log file with Transaction SM58. This allows you to display and edit function calls
that have not yet been executed.
If you want to send an LUW later, you can specify this event by calling the function module
START_OF_BACKGROUNDTASK before COMMIT WORK.