Data Interfaces

RFC Dialog
R/3 System 1 R/3 System 2
Variant 1: Synchronous
PROGRAM RS01.
...
CALL FUNCTION 'DIALOG'.
DESTINATION ...
...
Screen 100
Variant 2: Separated
PROGRAM RS01.
...
CALL FUNCTION 'DIALOG'.
DESTINATION ...
STARTING NEW TASK 'A'...
Caller
session
© SAP AG
Screen 100
1st session 2nd session
FUNCTION DIALOG.
...
CALL SCREEN '100'.
...
ENDFUNCTION.
Screen 100
RFC dialog (or RFC with screens) allows you to display screens (dialog and list screens) in the client
system and process them in a remote system within a RFC.
In the called function module, you can call a screen using (for example) CALL SCREEN. The screen is
then transported and displayed in the client system. The same applies to CALL TRANSACTION,
SUBMIT AND RETURN, and CALL DIALOG.
There are two call techniques:
1) Synchronous RFC:
Here, the client program executes the call and waits until the called function module has finished. All
dialog steps executed by the called function module are displayed in the original session of the client
program. Only when the function module is finished does the client program continue processing after
CALL FUNCTION.
2) Asynchronous RFC (STARTING NEW TASK ):
Here, the client program continues processing directly after CALL FUNCTION. The function module is
run asynchronously on a remote system. All dialog steps executed by the called function module are
displayed in a new session in the client system. RFC dialog thus behaves like a remote login.
Transaction SC38 allows you to start a R/2 program. The list output of the this program is displayed in
the R/3 SAPGUI.