Get Example source ABAP code based on a different SAP table
ABAP_RFC , Remote Function Call in ABAP Release 3.0 ITOC
ABAP_MODIFICATION_NN Transactional RFC
CALL FUNCTION... DESTINATION ... can now also be called using the addition IN BACKGROUND TASK. The calls are collected and executed as a logical unit of work (LUW) on the target host (destination) at the next COMMIT WORK. The current program does not wait for the function modules to finish processing.
ABAP_MODIFICATION_NN Asynchronous RFC
Regular remote function calls (calls using CALL FUNCTION .... DESTINATION ...) only enable an ABAP program to communicate with ABAP programs running in the background. This means that a program called in this way cannot interact with the user. The calling program can be a dialog program and display a screen to the user, however this screen is always inactive. The following call starts an ABAP function module in a new session for parallel processing: CALL FUNCTION ... STARTING NEW TASK ... The addition DESTINATION IN GROUP ... allows automatic load balancing within a group of application servers. The addition DESTINATION dest enables parallel processing in a remote system. Unlike in a regular function module call, the caller carries on processing immediately as soon as the function module (either local or remote) has been started (asynchronous call). The called function module can now, for example, use CALL SCREEN ... to display a dynpro and interact with the user. The statement WAIT UNTIL condition $[UP TO n SECONDS$] makes it possible to wait for the confirmation of an asynchronously called function module (this also requires the addition PERFORMING form ON END OF TASK. WAIT must be executed in the same ABAP_ISESS .
ABAP_MODIFICATION_NN Authorization Checks when Accessing Function Pools Using RFC
If the profile parameter auth/rfc_authority_check is set, the system checks authorization against authorization object S_RFC for the function pool before calling the function.
