How To Fix PPEENG160 - Lock of &1 &2 reset to "shared" mode

SAP Error Message - Details

• Message type: E = Error

• Message class: PPEENG - iPPE Engine Messages

• Message number: 160

• Message text: Lock of &1 &2 reset to "shared" mode

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 PPEENG160 - Lock of &1 &2 reset to "shared" mode ?

  The SAP error message PPEENG160 indicates that a lock on a particular object (like a production order, work center, or similar) has been reset to "shared" mode. This typically occurs in the context of the Production Planning and Execution (PPE) module when multiple users or processes are trying to access the same object simultaneously.
  Cause:
  
  
  Concurrent Access: The most common cause of this error is that multiple users or processes are trying to access or modify the same object at the same time. When one user locks the object in exclusive mode, and another user tries to access it, the system may reset the lock to shared mode to allow read access.
  
  
  Lock Timeout: If a process holds a lock for too long, the system may reset the lock to allow other processes to access the object.
  
  
  System Configuration: Certain configurations in the SAP system regarding lock management may lead to this behavior.
  
  
  Solution:
  
  
  Check Lock Entries: Use transaction code SM12 to check for existing lock entries. Identify if there are any long-held locks that may be causing the issue.
  
  
  Coordinate User Access: Ensure that users are not trying to access the same object simultaneously in a way that conflicts. This may involve coordinating activities or scheduling tasks to avoid overlap.
  
  
  Review and Optimize Processes: If a particular process is holding locks for an extended period, review the process to see if it can be optimized to release locks more quickly.
  
  
  Increase Lock Timeout: If appropriate, consider increasing the lock timeout settings in the system configuration, but this should be done with caution as it may lead to other issues.
  
  
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance.
  
  
  System Monitoring: Implement monitoring to track lock contention and identify patterns that lead to this error.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SM12: Display and manage lock entries.
  SM21: Check system logs for any related errors or warnings.
  ST22: Analyze dumps that may provide insight into the issue.
  
  
  
  SAP Documentation: Review SAP Help documentation for Production Planning and Execution for more details on lock management and best practices.
  
  
  Performance Tuning: Consider performance tuning of the application to reduce the time locks are held.
  
  
  If the issue persists after trying the above solutions, it may be beneficial to engage with SAP support for further assistance.