SET
Basic form
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 to programs. 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 , whereas CALL DIALOG does not.
On COMMIT WORK and
ROLLBACK WORK the switch is reset.
Update requests with a delayed start (V2) cannot be processed
locally.
Like in the normal update task, all messages apart from type
'S' result in termination and rollback.
Note
Unlike the normal update task, the local update task does
not run in its own LUW . If a rollback occurs, any changes
made in the dialog part are also reset.
The return code value is set as follows:
-
SY-SUBRC = 0
The local update task was switched on.
SY-SUBRC = 1
The local update task could not be switched on
because a CALL FUNCTION ... IN UPDATE TASK has already been
started. The system continues in the normal update mode.
Example
Switch on local update task:
-
SET UPDATE TASK LOCAL.
Index
© SAP AG 1996