How To Fix /SRMSMC/QLB028 - Import failed because some objects are being edited

SAP Error Message - Details

• Message type: E = Error

• Message class: /SRMSMC/QLB -

• Message number: 028

• Message text: Import failed because some objects are being edited

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/QLB028 - Import failed because some objects are being edited ?

  The SAP error message /SRMSMC/QLB028 Import failed because some objects are being edited typically occurs during the import of transport requests in the SAP system. This error indicates that the import process cannot proceed because some of the objects included in the transport request are currently being edited or locked by another user or process.
  Cause:
  
  Locked Objects: The objects that are part of the transport request are currently being edited or are locked by another user or transaction.
  Active Sessions: There may be active sessions or transactions that are using the objects included in the transport.
  Long-running Transactions: If a transaction is taking a long time to complete, it may hold locks on the objects, preventing the import from proceeding.
  
  Solution:
  
  
  Identify Locked Objects:
  
  Use transaction code SM12 to check for any locks on the objects. You can filter by user or object name to find out who is holding the lock.
  If you find locks that are not needed, you can ask the user to release them or, if necessary, you can delete the locks (be cautious with this approach).
  
  
  
  Check Active Sessions:
  
  Use transaction code SM66 to view all active processes in the system. Look for any processes that might be using the objects in question.
  If you identify a long-running process that is holding locks, you may need to wait for it to complete or coordinate with the user to release the lock.
  
  
  
  Wait and Retry:
  
  Sometimes, simply waiting for the other user or process to finish editing the objects can resolve the issue. After a short period, try the import again.
  
  
  
  Transport Request Management:
  
  If the issue persists, consider checking the transport request for any dependencies or objects that might be causing the lock. You may need to adjust the transport request or split it into smaller requests.
  
  
  
  System Administration:
  
  If you are unable to resolve the issue, it may be necessary to involve your SAP Basis team or system administrator to investigate further and assist with unlocking objects or managing transport requests.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SM12: To view and manage locks.
  SM66: To monitor active processes.
  SE01: To manage transport requests.
  
  
  
  Documentation: Refer to SAP Notes and documentation related to transport management and object locking for more detailed guidance.
  
  
  Best Practices: Implement best practices for transport management, such as scheduling imports during off-peak hours and ensuring that users are aware of transport activities to minimize conflicts.
  
  
  By following these steps, you should be able to resolve the /SRMSMC/QLB028 error and successfully import your transport request.