How To Fix MC604 - Own lock is no longer set for object requested

SAP Error Message - Details

• Message type: E = Error

• Message class: MC - Aggregate: views, matchcodes, lock objects

• Message number: 604

• Message text: Own lock is no longer set for object requested

What causes this issue?

An exclusive lock requested by calling an ENQUEUE function module cannot
be allowed because your own lock for the object in question no longer
exists or is no longer complete. This error can occur, for example, when
an optimistic lock is to be converted to an exclusive lock, but the
optimistic lock no longer exists meanwhile. The reason for this is that
the object in question has already been locked exclusively by another
mode.
Technical Information: The C_ENQUEUE routine returned the following
values:
COLLISION_OBJECT = &V2&
COLLISION_UNAME = &V1&

System Response

The ENQUEUE function module triggers an appropriate exception. If this
exception was not caught by the application program immediately, this
automatically causes termination of the current SAP transaction.

How to fix this error?

The application program should catch this exception after the ENQUEUE
function module has been called and react to it accordingly.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message MC604 - Own lock is no longer set for object requested ?

  The SAP error message MC604 ("Own lock is no longer set for object requested") typically occurs in the context of inventory management or material management processes. This error indicates that the system is trying to access a lock on a particular object (like a material document or inventory record) that it no longer holds. This can happen for various reasons, such as timeouts, session terminations, or other processes releasing the lock.
  Causes:
  
  Session Timeout: The user session may have timed out, causing the lock to be released.
  Process Interruption: If the process that set the lock was interrupted or terminated unexpectedly, the lock would be released.
  Concurrent Access: Another user or process may have accessed the same object, causing the original lock to be released.
  Database Issues: Problems with the database or network connectivity can also lead to locks being released unexpectedly.
  
  Solutions:
  
  Retry the Operation: Often, simply retrying the operation can resolve the issue if it was a temporary glitch.
  Check for Concurrent Processes: Ensure that no other processes are trying to access the same object simultaneously. You may need to coordinate with other users or processes.
  Session Management: Make sure that your session is active and not timing out. If you are working in a long-running transaction, consider keeping the session alive.
  Review System Logs: Check the system logs for any related errors or warnings that might provide more context about why the lock was released.
  Database Health Check: If the issue persists, perform a health check on the database to ensure there are no underlying issues affecting performance or connectivity.
  Contact SAP Support: If the problem continues and you cannot identify the cause, consider reaching out to SAP support for further assistance.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that may help in diagnosing the issue, such as SM12 (to view locks) and SM21 (to view system logs).
  SAP Notes: Check for any SAP Notes related to this error message, as they may provide specific patches or updates that address known issues.
  User Authorization: Ensure that the user has the necessary authorizations to access the object in question, as lack of permissions can sometimes lead to unexpected behavior.
  
  By following these steps, you should be able to diagnose and resolve the MC604 error in SAP.