How To Fix /SRMSMC/CHANGE_INFO002 - Change info for contact &1 is locked by user &2

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/CHANGE_INFO -

• Message number: 002

• Message text: Change info for contact &1 is locked by user &2

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/CHANGE_INFO002 - Change info for contact &1 is locked by user &2 ?

  The SAP error message /SRMSMC/CHANGE_INFO002 indicates that a change attempt is being made to a contact (or some related object) that is currently locked by another user. This locking mechanism is a standard feature in SAP to prevent data inconsistencies that could arise from simultaneous modifications by multiple users.
  Cause:
  
  User Lock: The contact information is currently being edited or accessed by another user, which causes the system to lock it for changes.
  Session Timeout: Sometimes, a user may have left a session open, and the system still considers that session active, leading to a lock.
  Technical Issues: Occasionally, technical issues or bugs can lead to locks not being released properly.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for the other user to finish their changes and release the lock. You can try again after some time.
  Identify the Locking User: If you have the necessary permissions, you can check which user is locking the contact. You can do this using transaction code SM12 (for lock entries) to see the locks and identify the user.
  Contact the Locking User: If possible, communicate with the user who is locking the contact to see if they can release the lock.
  Release the Lock: If the locking user is unavailable and you have the necessary authorizations, you can manually delete the lock entry in transaction SM12. However, this should be done with caution, as it may lead to data inconsistencies.
  Check for Background Jobs: Sometimes, background jobs may also hold locks. Check if any background processes are running that might be causing the lock.
  System Restart: In rare cases, a system restart may be required to clear persistent locks, but this should be done as a last resort and typically requires coordination with your SAP Basis team.
  
  Related Information:
  
  Lock Management: Understanding how SAP handles locks can help in troubleshooting. Locks are typically managed at the database level, and SAP uses various types of locks (exclusive, shared) depending on the operation being performed.
  User Authorizations: Ensure that you have the necessary authorizations to view and manage locks in the system.
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to locking mechanisms or bugs in the version of SAP you are using.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with your SAP Basis team or open a support ticket with SAP for further assistance.