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

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMI/PPEENG -

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

  The SAP error message /PLMI/PPEENG160 Lock of &1 &2 reset to shared mode typically occurs in the context of the SAP Production Planning and Detailed Scheduling (PP/DS) module. This message indicates that a lock on a specific object (like a production order, planning object, etc.) has been reset from exclusive mode to shared mode. This can happen due to various reasons, including concurrent access by multiple users or processes.
  Causes:
  
  Concurrent Access: Multiple users or processes are trying to access the same object simultaneously, leading to a conflict in lock modes.
  Long-Running Transactions: If a transaction takes too long to complete, it may cause other transactions to wait, leading to a reset of the lock mode.
  System Configuration: Certain configurations in the SAP system may lead to this behavior, especially if the locking mechanism is not properly set up.
  Database Issues: Problems with the underlying database can also lead to unexpected behavior in lock management.
  
  Solutions:
  
  Check for Concurrent Users: Identify if multiple users are trying to access the same object. If so, coordinate to avoid conflicts.
  Optimize Long Transactions: Review and optimize any long-running transactions that may be holding locks for extended periods.
  Review Lock Configuration: Check the configuration settings related to locking in the SAP system. Ensure that they are set up correctly to handle the expected load.
  Use Transaction SM12: You can use transaction SM12 to view and manage locks in the system. This can help identify which users or processes are holding locks on the object in question.
  System Performance: Monitor system performance and database health. If there are performance issues, consider optimizing the database or increasing system resources.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide patches or updates that could resolve the issue.
  
  Related Information:
  
  Transaction Codes: 
  
  SM12: To view and manage locks.
  SM21: To check system logs for any related errors or warnings.
  ST22: To analyze dumps that may provide more context on the issue.
  
  
  SAP Documentation: Refer to the official SAP documentation for detailed information on locking mechanisms and best practices.
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they have found.
  
  If the problem persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.