ERPClimb logoERPClimb

SAP enqueue lock

Object is locked by another user

A document/master record cannot be changed because an SAP enqueue lock is held by another user/session/process.

Likely root causes

  1. Another user is legitimately editing the same business object.
  2. A session/job terminated and left a lock until cleanup/recovery.
  3. Long-running update/background processing still owns the lock.

What to inspect

  1. Lock owner shown in the application message.
  2. SM12 — lock entry, owner, table/key and age.
  3. SM04/AL08 or SM37 for the owning session/job.
  4. SM13 if update processing may still be active.

Resolution path

  1. Contact the lock owner or wait for valid processing to finish.
  2. Delete a lock manually only after proving the owning session/update is gone and business consistency is safe.
  3. Investigate repeated stale locks as an application/session issue.
  4. Retry the transaction after the lock is safely released.

ERPClimb is an independent platform and is not affiliated with SAP SE.