Function Groups, Update Tasks and IN UPDATE TASK

Explanation

CALL FUNCTION 'X' IN UPDATE TASK registers the FM for asynchronous execution when COMMIT WORK runs. This isolates database writes from dialog work and enables SM13 recovery. Only FMs marked 'Update Module' can be called this way, and their imports are serialised — no reference types, only value transport.

Code example

CALL FUNCTION 'Z_SAVE_HEADER' IN UPDATE TASK  EXPORTING is_header = ls_header.COMMIT WORK.

Real project scenario

Moving DB writes to update tasks fixed lost updates when dialog users hit STOP mid-transaction.

Common mistakes

Reading committed data from within the same LUW; passing reference parameters; forgetting COMMIT WORK.

Best practices

Keep V1 minimal and idempotent; use V2 for non-critical updates; monitor SM13 for stuck records.

Interview angle

Difference between V1, V2 and V3 update tasks.