How To Fix /SAPDMC/LSMW071 - Project '&' is currently being edited by user '&'

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPDMC/LSMW -

• Message number: 071

• Message text: Project '&' is currently being edited by user '&'

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 /SAPDMC/LSMW071 - Project '&' is currently being edited by user '&' ?

  The SAP error message /SAPDMC/LSMW071 indicates that a specific project in the Legacy System Migration Workbench (LSMW) is currently being edited by another user. This is a common issue in environments where multiple users may be working on LSMW projects simultaneously.
  Cause:
  The error occurs when:
  
  A user attempts to access or edit an LSMW project that is already open and being edited by another user.
  The project is locked to prevent concurrent modifications, which could lead to data inconsistencies or corruption.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Identify the User: Check who is currently editing the project. You can do this by using transaction code SM12 to view the lock entries. Look for the project name in the list to see which user has it locked.
  
  
  Contact the User: If possible, reach out to the user who is currently editing the project and ask them to finish their work or to log out of the project.
  
  
  Wait for Release: If the user is actively working on the project, you may need to wait until they have completed their changes and released the lock.
  
  
  Force Unlock (if necessary): If the user is no longer available (e.g., they have logged off unexpectedly), you may need to forcefully unlock the project. This can be done by:
  
  Going to transaction SM12, finding the lock entry, and deleting it. Note: This should be done with caution and typically requires appropriate authorizations, as it can lead to data loss or corruption if the user was in the middle of a critical operation.
  
  
  
  Check for Background Jobs: Sometimes, background jobs may also hold locks on LSMW projects. Ensure that no background jobs are running that could be causing the lock.
  
  
  Review User Permissions: Ensure that users have the appropriate permissions to access and edit the LSMW projects. Sometimes, permission issues can lead to unexpected behavior.
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  LSMW: Access the Legacy System Migration Workbench.
  SM12: View and manage lock entries.
  SM21: Check system logs for any related issues.
  
  
  
  Documentation: Refer to SAP Help documentation for LSMW for more details on project management and user access.
  
  
  Best Practices: To avoid such issues in the future, consider implementing a policy for project editing, such as assigning specific projects to users or scheduling times for project updates.
  
  
  By following these steps, you should be able to resolve the error and continue working with your LSMW project.