How To Fix SOI420 - Transport &1 is currently imported

SAP Error Message - Details

• Message type: E = Error

• Message class: SOI - Safe Online Import/Upgrade Messages

• Message number: 420

• Message text: Transport &1 is currently imported

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 SOI420 - Transport &1 is currently imported ?

  The SAP error message SOI420 indicates that a transport request (denoted by &1) is currently being imported into the system. This situation can arise during the transport management process when a transport request is in the process of being imported, and another operation is attempted that conflicts with this ongoing import.
  Cause:
  
  Concurrent Import: The most common cause of this error is that a transport request is already being processed in the system. SAP does not allow multiple imports of transport requests to occur simultaneously to maintain data integrity.
  Locking Mechanism: SAP uses a locking mechanism to prevent conflicts during the import process. If a transport request is locked for import, any attempt to import another request will trigger this error.
  
  Solution:
  
  Wait for Completion: The simplest solution is to wait until the current transport request has completed its import process. You can monitor the import status in the Transport Management System (STMS) or check the import logs.
  Check Import Queue: Use transaction code STMS to check the import queue and see which transport request is currently being processed. You can also check the logs for any issues that may have occurred during the import.
  Cancel or Retry: If the import is taking too long or seems to be stuck, you may need to cancel the import process. However, this should be done with caution, as it may lead to inconsistencies. After canceling, you can retry the import.
  System Lock: If you suspect that the system is locked due to a failed import, you may need to release the lock. This can be done by checking the transport logs and ensuring that no processes are still holding the lock.
  
  Related Information:
  
  
  Transaction Codes: 
  
  STMS: Transport Management System, where you can manage transport requests.
  SE01: Transport Organizer, where you can view and manage transport requests.
  SE09/SE10: Workbench requests and Customizing requests, respectively.
  
  
  
  Logs: Always check the transport logs for detailed information about the import process and any errors that may have occurred.
  
  
  SAP Notes: It may be helpful to search for relevant SAP Notes in the SAP Support Portal for any known issues or additional troubleshooting steps related to transport errors.
  
  
  System Administration: If you are not the system administrator, you may need to contact your SAP Basis team for assistance in resolving transport-related issues.
  
  
  By following these steps, you should be able to resolve the SOI420 error and successfully manage your transport requests in SAP.