SAP CALL FUNCTION STARTING PARA ABAP Statements

Get Example source ABAP code based on a different SAP table
  



CALL FUNCTION - STARTING NEW TASK parameter_list

Short Reference
• 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


ABAP Syntax ... [EXPORTING p1 = a1 p2 = a2 ...]

[TABLES t1 = itab1 t2 = itab2 ...]
[CHANGING p1 = a1 p2 = a2 ...]
[EXCEPTIONS [exc1 = n1 exc2 = n2 ...]
[system_failure = ns [MESSAGE smess]]
[communication_failure = nc [MESSAGE cmess]]
[resource_failure = nr [MESSAGE rmess]]
[OTHERS = n_others]].

What does it do? These additions are used to assign actual parameters to the formal parameters of the function module, and assign return values 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 imported and that actual parameters specified by CHANGING can be used to pass values but not to accept values. The additional predefined non-class-based exception resource_failure can also be handled for pRFC.

Return to menu