ABAPCALL_FUNCTION_UPDATE_TASK - CALL FUNCTION UPDATE TASK

Addresses (Business Address Services)   ABAP Short Reference  
This documentation is copyright by SAP AG.

CALL FUNCTION

Variant 3

CALL FUNCTION func IN UPDATE TASK.

Additions

1. ... EXPORTING  p1 = f1     ... pn = fn

2. ... TABLES     p1 = itab1  ... pn = itabn

Effect

Flags the function module func for execution in the update task. It is not executed at once, but the data passed with EXPORTING or TABLES is placed in a database table and a subsequent COMMIT WORK then causes the function module to be executed by the update task. Update function modules must be flagged as such in the Function Builder
The return value is not set.

Addition 1

... EXPORTING p1 = f1 ... pn = fn

Effect

Values of fields and field strings specified under EXPORTING are passed from the calling program to the function module. In the function module, the formal parameters are defined as import parameters. In the interface definition, default values must be assigned to all import parameters of the update function module.

Addition 2

... TABLES p1 = itab1 ... pn = itabn

Effect

TABLES passes references to internal tables. All table parameters of the function module must have values.

Note

With update function modules, both import parameters and exceptions are ignored when the call is made.

1. During updating processes of function modules, you may not make any calls using the language statements SUBMIT, CALL DIALOG, CALL SCREEN, CALL TRANSACTION, COMMIT WORK or ROLLBACK WORK . All other language elements that trigger a database Commit (for example, a screen change using the MESSAGE statement) also lead to a runtime error during updating.
   
   
   

Administration transaction

Related

COMMIT WORK, SET UPDATE TASK LOCAL

General Material Data   General Material Data  
This documentation is copyright by SAP AG.

Length: 3075 Date: 20230327 Time: 230513     sap01-206 ( 50 ms )