Receiving Results from an Asynchronous RFC 

Once the called function is completed, the next dialog step in the calling program (such as AT USER-COMMAND ) guides the system into the FORM routine that checks for results. This FORM routine consists of a special syntax and must be called with a using parameter that refers to the name of the task:

• If a function module returns no result, the addition PERFORMING RETURN_FORM ON END OF TASK can be omitted.
• If an asynchronous call calls several consecutive function modules with the same destination, you must assign a different task name to each.
• A calling program which starts an asynchronous RFC with PERFORMING cannot switch roll areas or change to an internal mode. This is because the asynchronous function module call reply cannot be passed on to the relevant program. You can perform a roll area switch with SUBMIT or CALL TRANSACTION .
• If the calling program which has executed the asynchronous call is terminated, despite the fact that it is expecting replies, these replies from the asynchronous call cannot be delivered.
• You can use the WAIT statement with PERFORMING form ON END OF TASK to wait for the reply to a previously started asynchronous call. In this case, WAIT must be in the same program context.
• The program processing continues after WAIT if either the condition of a logical expression was satisfied by the subroutine that performs the task in question, or a specified time period has been exceeded. For more information on the WAIT statement, see the online help in the ABAP editor.

The key word RECEIVE occurs only with the function module call CALL FUNCTION func STARTING NEW TASK taskname . If the function module returns no results, this part need not be defined.

The effect of the SET USER-COMMAND ‘OKCD’ statement is exactly as if the user had entered the function in the command field and pressed ENTER. This means that the current positioning of the list and the cursor is taken into account.