Is "COMMIT WORK AND WAIT" a local update task?

[EricYu0912]

Hi experts,

If an update task was called and then COMMIT WORK AND WAIT.

Is the update task running in current process or in another update process?

Regards,
Eric

[EricYu0912]

Hi experts,

If an update task was called and then COMMIT WORK AND WAIT.

Is the update task running in current process or in another update process?

Regards,
Eric

[RaymondGiuseppi]

It depends, did you call SET UPDATE TASK LOCAL before (no crystal ball available)

• NO - updates will perform in the update work process , but current process will wait til high-priority update function modules (synchronous updating)
• YES - updates will perform in the current work process

[EricYu0912]

I think there is just COMMIT WORK AND WAIT. But in call stack, you can see a LOCAL_UPDATE_TASK, looks like it's a form in COMMIT WORK AND WAIT (if you switch on system debug).

[RaymondGiuseppi]

There is also a parameter abap/force_local_update_task = [0,1].

(You mean the form local_update_task of SAPMSSY4)

[Sandra_Rossi]

phoenixming0912 You should verify. Add a breakpoint at SET UPDATE TASK LOCAL early in the execution.

Local update task may also be activated via "call transaction using" with option updmode = 'L'.

[Sandra_Rossi]

The ABAP documentation made by SAP gives all the details.

[Sandra_Rossi]

"update task was called" is not very clear, I guess you mean "CALL FUNCTION ... IN UPDATE TASK ... was done".