Data Interfaces

Asynchronous RFC with Return of Data
R/3 server A R/3 server B (same or other R/3)
PROGRAM RS01.
...
CALL FUNCTION 'FUNC1'.
DESTINATION 'B'
STARTING NEW TASK 'ABC'
PERFORMING FUNC1_RETURN ON END OF TASK.
EXPORTING ...
TABLES ...
...
FORM FUNC1_RETURN USING TASK.
...
RECEIVE RESULTS FROM FUNCTION FUNC1
IMPORTING ...
TABLES ...
EXCEPTIONS ...
...
SET USER-COMMAND '...'.
ENDFORM.
...
AT USER-COMMAND.
...
© SAP AG
FUNCTION FUNC1.
...
ENDFUNCTION.
In the above example, the called function module can return data or exceptions to the client program,
although the function module has been started asynchronously. By using the PERFORMING addition,
you ensure that the connection to the partner remains open.
When the called function module is processed, the FORM routine specified after the CALL-FUNCTION
parameter PERFORMING is called.
The FORM routine must have a formal parameter (any name is allowed). This parameter is supplied
automatically with the relevant task ID when the routine is called.
By using RECEIVE RESULTS FROM FUNCTION ... in the FORM routine, you can get the
asynchronously processed function module to return data and exceptions. By using the SET USER-
COMMAND statement, you can start the program event directly.