How To Fix /LTB/MC039 - Import failed: Project is still being deleted in separate session

SAP Error Message - Details

• Message type: E = Error

• Message class: /LTB/MC -

• Message number: 039

• Message text: Import failed: Project is still being deleted in separate session

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 /LTB/MC039 - Import failed: Project is still being deleted in separate session ?

  The SAP error message /LTB/MC039 Import failed: Project is still being deleted in separate session typically occurs in the context of SAP Project Management or SAP Logistics when there is an attempt to import a project that is currently being deleted in another session. This can happen in scenarios where multiple users or processes are trying to access or modify the same project simultaneously.
  Cause:
  
  Concurrent Sessions: The project is being deleted in another session, which locks the project for any other operations, including imports.
  Database Locking: SAP uses locking mechanisms to prevent data inconsistencies. If a project is marked for deletion, it cannot be accessed until the deletion process is completed.
  Long-running Deletion Process: The deletion process might be taking longer than expected, causing other operations to fail.
  
  Solution:
  
  Wait and Retry: The simplest solution is to wait for a few moments and then retry the import operation. The deletion process may complete, releasing the lock on the project.
  Check Active Sessions: Use transaction codes like SM12 (to check for locks) and SM21 (to check system logs) to identify if there are any active sessions that are deleting the project.
  Identify the Deleting Session: If you have access, you can identify the user or session that is performing the deletion and coordinate with them to understand the status.
  Cancel the Deletion: If the deletion is taking too long and is not necessary, you may consider canceling it if you have the appropriate permissions. This can be done through transaction codes like SE38 or SE80 to run a custom program or report that can cancel the deletion.
  System Administrator Assistance: If the issue persists, it may be necessary to involve a system administrator or SAP Basis team to investigate further, especially if there are underlying issues with the database or locking mechanisms.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SM12 (to view and manage locks), SM21 (to view system logs), and SE38 (to execute reports).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review SAP documentation related to project management and import processes to understand the expected behavior and best practices.
  
  By following these steps, you should be able to resolve the error and successfully import the project once the deletion process is complete.