This displays all active and requested database locks. Exclusive locks mean that other users cannot access the locked entry, but these locks can severely reduce performance of your R/3 System and database system.
Procedure for Determining Which User Triggered the Lock:
In a database system that is part of an R/3 System, this user is always SAPR3. Using the TASKID, you can determine the corresponding Application PID and the application server through Current system status / Task manager. Then use transaction
SM50 to determine which R/3 work process triggered the lock or lock request. Waits (SAP DB) Total (SAP DB)