How To Fix /SAPDMC/LSMW073 - Object '&' is currently being edited by user '&'

SAP Error Message - Details

• Message type: E = Error

• Message class: /SAPDMC/LSMW -

• Message number: 073

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

  The SAP error message /SAPDMC/LSMW073 Object '&' is currently being edited by user '&' typically occurs in the context of the Legacy System Migration Workbench (LSMW) when you attempt to edit or access an object (like a project, subproject, or object) that is currently being edited by another user. This is a locking mechanism in SAP to prevent concurrent modifications that could lead to data inconsistencies.
  Cause:
  
  Concurrent Access: Another user is currently editing the same LSMW object.
  Session Left Open: The user who is editing the object may have left their session open, causing the lock to persist.
  System Error: Occasionally, a system error or crash may leave a lock on an object even if the user is no longer actively editing it.
  
  Solution:
  
  Wait for Release: The simplest solution is to wait until the other user has finished editing the object and released the lock.
  Contact the User: If you know who the user is, you can contact them to see if they can finish their work or release the lock.
  Check Lock Entries: You can check the lock entries in the system using transaction code SM12. This will allow you to see which user is holding the lock on the object.
  
  In SM12, enter the object name and execute to see the lock entries.
  
  
  Delete Lock Entry: If necessary and if you have the appropriate authorizations, you can delete the lock entry from SM12. However, this should be done with caution, as it may lead to data inconsistencies if the other user is still working on the object.
  System Administrator: If you are unable to resolve the issue, contact your SAP system administrator for assistance. They may have additional tools or permissions to help resolve the lock.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage lock entries) and LSMW (to access the Legacy System Migration Workbench).
  User Management: Ensure that users are aware of the importance of properly closing their sessions to avoid unnecessary locks.
  Documentation: Review SAP documentation or notes related to LSMW and locking mechanisms for further insights and best practices.
  
  By following these steps, you should be able to address the error message and continue your work with LSMW in SAP.