How To Fix /SAPDMC/LSMW072 - Subproject '&' is currently being edited by user '&'

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPDMC/LSMW -

• Message number: 072

• Message text: Subproject '&' 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/LSMW072 - Subproject '&' is currently being edited by user '&' ?

  The SAP error message /SAPDMC/LSMW072 indicates that a subproject 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 the same LSMW project or subproject simultaneously.
  Cause:
  
  Concurrent Access: The primary cause of this error is that another user has locked the subproject for editing. LSMW does not allow multiple users to edit the same subproject at the same time to prevent data inconsistencies.
  Session Timeout: Sometimes, a user may have left a session open, which can lead to the subproject being locked unintentionally.
  System Issues: Occasionally, system glitches or errors can cause a lock to persist even after the user has finished editing.
  
  Solution:
  
  Wait for Release: The simplest solution is to wait until the other user has finished editing the subproject. Once they save their changes and exit, the lock will be released.
  Contact the User: If you know who the user is, you can contact them to see if they can exit the subproject or save their work.
  Check User Sessions: If you have administrative access, you can check the active user sessions in the system. You can use transaction SM04 to see which users are logged in and what they are doing. If necessary, you can ask the user to log out or terminate their session.
  Use Transaction SM12: If you have the necessary permissions, you can check for and delete any lock entries related to the subproject using transaction SM12. However, be cautious with this approach, as it may lead to data loss if the other user is still working on the project.
  Review System Logs: If the issue persists, review system logs for any errors or issues that might be causing the lock to remain active.
  
  Related Information:
  
  Lock Management: Understanding how SAP handles locks can help in troubleshooting similar issues in the future. Locks are typically managed at the database level, and SAP uses various types of locks (e.g., exclusive, shared) to control access to data.
  User Roles and Permissions: Ensure that users have the appropriate roles and permissions to access and edit LSMW projects and subprojects.
  Documentation: Refer to SAP documentation for LSMW for best practices on managing projects and subprojects, especially in multi-user environments.
  
  If the problem continues to occur frequently, it may be worth reviewing the workflow and access policies for LSMW projects to minimize conflicts between users.