ENQUEUE_TIMEOUT
mediumEnqueue Lock Request Timed Out Waiting for Release
Module: BASIS / Enqueue
What this means
ENQUEUE_TIMEOUT occurs when a lock request via the SAP enqueue server cannot be satisfied within the configured timeout period because another process holds the required lock and does not release it. Unlike ENQUEUE_FOREIGN (immediate rejection), ENQUEUE_TIMEOUT means the system waited for the lock to become available but gave up after the timeout expired. This is common during: long-running batch jobs that hold locks on shared objects; period-end processing where many users and jobs compete for the same financial objects; or deadlock situations where two processes are each waiting for a lock the other holds.
Check SM12 for the lock entries on the affected objects. Identify which user or work process holds the conflicting lock and how long it has been held. If the lock is from a hanging process, check SM50 and terminate it if appropriate. If this is a recurring pattern during batch runs, review whether background jobs can be serialised or whether the locking granularity can be reduced. Check SM21 for enqueue server load or error messages.
Quick Info