How To Fix /CPD/SS_MESSAGES036 - MRS update failed; plan &1 and version &2 locked by &3

SAP Error Message - Details

• Message type: E = Error

• Message class: /CPD/SS_MESSAGES -

• Message number: 036

• Message text: MRS update failed; plan &1 and version &2 locked by &3

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 /CPD/SS_MESSAGES036 - MRS update failed; plan &1 and version &2 locked by &3 ?

  The SAP error message /CPD/SS_MESSAGES036 indicates that a Material Requirements Planning (MRP) update has failed because the specified plan and version are locked by another user or process. This typically occurs in environments where multiple users or processes are trying to access or modify the same planning data simultaneously.
  Cause:
  
  Locking Mechanism: SAP uses a locking mechanism to prevent data inconsistencies. If one user or process is currently editing or processing the plan and version, other users will be unable to make changes until the lock is released.
  Long-running Processes: If a process is taking a long time to complete (e.g., a background job), it may hold the lock for an extended period.
  User Sessions: Sometimes, a user may have multiple sessions open, and one of them is holding the lock.
  System Errors: Occasionally, system errors or crashes can leave locks in place that need to be cleared.
  
  Solution:
  
  Identify the Lock: Use transaction code SM12 to view the lock entries. You can filter by the user or the object type to find out who is holding the lock.
  Release the Lock: If you have the necessary authorizations, you can manually delete the lock entry in SM12. However, be cautious when doing this, as it may lead to data inconsistencies if the other user is still processing.
  Wait for Completion: If the lock is held by a legitimate process (like a background job), it may be best to wait until that process completes.
  Check for Long-running Jobs: Use transaction SM37 to check for any long-running jobs that may be holding the lock. If necessary, you can cancel these jobs if they are no longer needed.
  Communicate with Users: If you identify that a specific user is holding the lock, communicate with them to understand if they can release it or if they are still working on the data.
  
  Related Information:
  
  Transaction Codes:
  
  SM12: Display and manage lock entries.
  SM37: Monitor background jobs.
  SM21: Check system logs for any related errors or warnings.
  
  
  User Authorizations: Ensure that you have the necessary authorizations to view and manage locks.
  System Performance: Regularly monitor system performance and job execution times to prevent long-running processes from causing locks.
  Documentation: Refer to SAP documentation for more details on locking mechanisms and best practices for managing locks in the system.
  
  By following these steps, you should be able to resolve the error and prevent it from occurring in the future.