Lock inheritance with "CALL FUNCTION func IN BACKGROUND TASK"

[Former Member]

I see that the "SAP Lock concept" documentation states that for locks obtained with _scope = '3', all UPDATE tasks (spawned via "CALL FUNCTION func IN UPDATE TASK" inherit the lock (which is released only once all such update tasks and the calling process have requested a DEQUEUE).

What should happen when instead, I use "CALL FUNCTION func IN BACKGROUND TASK" (for doing the update in a queue)? Are the locks inherited here as well?

Cheers!

[Sandra_Rossi]

Hopefully not, as a background task may be executed late. While update tasks are to be executed quickly (if not, administrators should review the system configuration, like increasing the number of UPD workprocesses).

Solution: In the background task, redo the locks, as if it was a background job.

[Former Member]

Yep. Thats what I'm going to do. Thanks!