How To Fix 5C658 - Account '&1' is locked through user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 5C - HR: Messages for Switzerland

• Message number: 658

• Message text: Account '&1' is locked through user &2

What causes this issue?

You tried to lock account &V1&.
User &V2& has already locked the account..

System Response

There is no write access to the account. Bookings are not written into
the database.

How to fix this error?

Ensure that account &V1& is unlocked.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5C658 - Account '&1' is locked through user &2 ?

  The SAP error message 5C658 indicates that a specific account (denoted by &1) is locked by a user (denoted by &2). This typically occurs in the context of financial transactions or account management within the SAP system.
  Cause:
  The error occurs when:
  
  An account is locked for editing or posting due to a user action, often to prevent concurrent modifications or to enforce data integrity.
  The account may be locked due to a previous transaction that was not completed or was interrupted.
  A user may have locked the account intentionally for maintenance or review purposes.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Identify the Locking User: Check which user has locked the account. The error message provides the user ID (&2).
  
  
  Contact the Locking User: If possible, reach out to the user who has locked the account to understand why it is locked and if they can unlock it.
  
  
  Unlock the Account:
  
  If you have the necessary permissions, you can unlock the account yourself. This can typically be done through transaction codes like SM12 (for locking entries) or SM21 (for system logs) to identify and manage locks.
  In SM12, you can search for the user ID and see the locked entries. You can then delete the lock entry if it is safe to do so.
  
  
  
  Check for Background Jobs: Sometimes, background jobs may lock accounts. Check if there are any running jobs that might be causing the lock.
  
  
  Review System Logs: Use transaction SM21 to review system logs for any related errors or warnings that might provide additional context.
  
  
  Consult with Basis Team: If you are unable to resolve the issue, consult with your SAP Basis team or system administrator for assistance. They may have additional tools or access to resolve the lock.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12, SM21, and SU01 (for user management).
  User Permissions: Ensure that you have the necessary permissions to unlock accounts or manage user locks.
  Documentation: Refer to SAP documentation or support notes for more detailed troubleshooting steps related to account locking issues.
  
  By following these steps, you should be able to identify the cause of the lock and take appropriate action to resolve the error message 5C658.