12-26-2007 8:14 AM
Hi,
I found a description at this link.
http://help.sap.com/saphelp_nw04/helpdata/en/41/7af4c5a79e11d1950f0000e82de14a/content.htm
'At the end of an SAP LUW, you should release all locks. This either happens automatically during the database update, or explicitly, when you call the corresponding dequeue function module. Locks that are not linked to a database update are released at the end of the SAP transaction'
I don't understand this, because I tested using commit work and wait. The lock entry still there after the statement 'commit' executed. the lock entry disappeared when the whole task completed.
don't know what does happens automatically during the database update. Isn't the 'commit' the case they mentioned?
12-26-2007 9:06 AM
Hai,
Commit statement does not release lock even if use it with wait.
You need to use DEQUEUE_ALL function module to release locks.
12-26-2007 9:06 AM
Hai,
Commit statement does not release lock even if use it with wait.
You need to use DEQUEUE_ALL function module to release locks.
12-26-2007 12:09 PM
The automatically bit refers to when updates are done in the update task.
matt
12-28-2007 4:12 AM
So does that means even I using a SYNCHRONIZE commit. There still not a database update happen?
From help.sap.com:
For 'commit work' "It triggers a database commit that also terminates the current database LUW and closes all database cursors. "
Database commit <> database update ?