SET UPDATE TASK LOCAL.

Effect
Switches on the local update task. This means that when you specify CALL FUNCTION ... IN UPDATE TASK, the update data is not stored in the database, but in ABAP/4 Memory. The update works as before. The only difference is that it is not performed in a separate process, but in the same process as the calling program, i.e. when a COMMIT WORK occurs, processing does not continue until all the update requests have been performed. In the standard setting, the normal update task is always active.

The switch status is not passed on from program to program. This means that CALL TRANSACTION and SUBMIT use the standard setting. In contrast to this, a module called with CALL DIALOG inherits the switch setting. This is because CALL TRANSACTION and SUBMIT run in their own LUW, while CALL DIALOG does not.