How To Fix /SRMSMC/CMN_BL029 - Response is locked by another user or is not "Pending Decision"

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/CMN_BL -

• Message number: 029

• Message text: Response is locked by another user or is not "Pending Decision"

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 /SRMSMC/CMN_BL029 - Response is locked by another user or is not "Pending Decision" ?

  The SAP error message /SRMSMC/CMN_BL029 indicates that a response in the Supplier Relationship Management (SRM) system is locked by another user or is not in a "Pending Decision" state. This typically occurs when multiple users are trying to access or modify the same response simultaneously, or when the response has already been processed or is in a state that does not allow further actions.
  Causes:
  
  Concurrent Access: Another user is currently editing or has locked the response.
  Response Status: The response is not in a "Pending Decision" state, meaning it may have already been processed, approved, or rejected.
  Session Timeout: The session may have timed out, causing the response to be locked.
  System Configuration: There may be specific configurations or workflows that prevent changes to the response under certain conditions.
  
  Solutions:
  
  Check User Locks: Verify if another user is currently editing the response. You can check the lock entries in the system using transaction code SM12 to see if the response is locked by another user.
  Refresh the Session: If you suspect a session timeout, try refreshing your session or logging out and back in to see if the lock is released.
  Verify Response Status: Check the status of the response to ensure it is indeed in a "Pending Decision" state. If it is in a different state, you may need to wait for the current process to complete or contact the relevant user to release the lock.
  Contact Administrator: If the issue persists, contact your SAP system administrator or support team to investigate further. They may need to unlock the response or provide additional insights into the workflow configuration.
  Wait and Retry: If the response is locked by another user, you may need to wait until that user completes their action and releases the lock.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage locks) and SWI1 (to check workflow instances).
  User Roles and Permissions: Ensure that your user role has the necessary permissions to access and modify the response.
  Documentation: Refer to SAP documentation or help resources for more detailed information on handling locks and response statuses in SRM.
  
  By following these steps, you should be able to resolve the error message and proceed with your tasks in the SAP SRM system.