Get Example source ABAP code based on a different SAP table
• CHANGING CALL FUNCTION STARTING NEW TASK • EXPORTING CALL FUNCTION STARTING NEW TASK • TABLES CALL FUNCTION STARTING NEW TASK • EXCEPTIONS CALL FUNCTION STARTING NEW TASK • MESSAGE CALL FUNCTION STARTING NEW TASK • OTHERS CALL FUNCTION STARTING NEW TASK • communication_failure CALL FUNCTION STARTING NEW TASK • system_failure CALL FUNCTION STARTING NEW TASK • resource_failure CALL FUNCTION STARTING NEW TASK
CALL FUNCTION STARTING NEW TASK, parameter_list Short Reference
What does it do? Parameter passing for aRFC. These additions are used to assign actual parameters to the formal parameters of the asynchronously called function module, and to assign return codes to exceptions that are not class-based. The additions have the same meaning as in the synchronous RFC with the exception that values with IMPORTING cannot be accepted and that values are passed but not accepted for actual parameters specified by CHANGING or TABLES. BEGIN_SECTION VERSION 5 OUT The additional predefined non-class-based exception resource_failure can also be handled for pRFC. END_SECTION VERSION 5 OUT If this exception is raised, the addition MESSAGE is not allowed. The additions IMPORTING, CHANGING, and TABLES of the statement RECEIVE must be used in callback routines to receive values from an asynchronously called function module.
ABAP_EXAMPLE_ABEXA Parameter Passing in sRFC and aRFC ABAP_EXAMPLE_END
