How To Fix /PF1/MSG_EH164 - &1 &2 have not been unlocked

SAP Error Message - Details

• Message type: E = Error

• Message class: /PF1/MSG_EH -

• Message number: 164

• Message text: &1 &2 have not been unlocked

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message /PF1/MSG_EH164 - &1 &2 have not been unlocked ?

  The SAP error message /PF1/MSG_EH164 &1 &2 have not been unlocked typically indicates that a certain object or entity (like a document, transaction, or data record) is currently locked and cannot be accessed or modified. This locking mechanism is a part of SAP's data integrity and concurrency control, ensuring that multiple users do not make conflicting changes to the same data simultaneously.
  Cause:
  
  Locked by Another User: The object may be locked by another user who is currently editing or processing it.
  System Lock: The system may have placed a lock on the object due to a previous transaction that did not complete successfully.
  Background Jobs: Sometimes, background jobs or processes may hold locks on certain objects.
  Transaction Errors: If a transaction was interrupted or failed, it might leave the object in a locked state.
  
  Solution:
  
  
  Identify the Lock:
  
  Use transaction code SM12 to check for locks. You can filter by user or object type to find out who is holding the lock.
  If you find that another user is holding the lock, you may need to wait for them to complete their transaction.
  
  
  
  Unlock the Object:
  
  If you have the necessary authorizations, you can manually delete the lock from transaction SM12. Be cautious when doing this, as it may disrupt another user's work.
  
  
  
  Check Background Jobs:
  
  Use transaction SM37 to check if there are any background jobs that might be holding locks on the object. If you find any, you may need to wait for them to complete or terminate them if appropriate.
  
  
  
  Review Transaction Logs:
  
  Check transaction logs or system logs for any errors that might indicate why the object is locked.
  
  
  
  Contact Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP Basis team or support for assistance.
  
  
  
  Related Information:
  
  Lock Management: Understanding how SAP handles locks can help in troubleshooting. Locks can be exclusive (only one user can access) or shared (multiple users can access).
  User Authorizations: Ensure that you have the necessary authorizations to view and manage locks.
  Transaction Codes: Familiarize yourself with relevant transaction codes like SM12 (lock entries), SM37 (job monitoring), and SM21 (system log) for effective troubleshooting.
  
  By following these steps, you should be able to identify the cause of the lock and take appropriate action to resolve the error message.