How To Fix SOI421 - Running imports have been found - Upgrade cannot be performed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 421

• Message text: Running imports have been found - Upgrade cannot be performed

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 SOI421 - Running imports have been found - Upgrade cannot be performed ?

  The SAP error message SOI421 indicates that there are running imports in the system, which prevents an upgrade from being performed. This situation typically arises when there are ongoing background jobs or processes that are importing data or performing other operations that need to be completed before an upgrade can proceed.
  Cause:
  
  Ongoing Imports: The most common cause is that there are active import processes running in the system. These could be related to transport requests, data imports, or other background jobs that are currently executing.
  Long-Running Jobs: Sometimes, jobs may take longer than expected, leading to conflicts with the upgrade process.
  System Lock: The system may be locked due to other operations that are preventing the upgrade from starting.
  
  Solution:
  
  Check Background Jobs: Use transaction code SM37 to check for any running background jobs. Look for jobs that are related to imports or any other long-running processes.
  Terminate or Wait: If you find any jobs that are blocking the upgrade, you can either wait for them to complete or terminate them if they are not critical. Be cautious when terminating jobs, as this may lead to data inconsistencies.
  Check Transport Directory: Ensure that there are no pending transport requests in the transport directory that could be causing the issue.
  System Monitoring: Use transaction SM66 to monitor all active processes in the system. This can help identify any other processes that might be causing the blockage.
  Restart Upgrade: Once all blocking processes have been resolved, you can restart the upgrade process.
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional guidance or updates related to this error message.
  Upgrade Documentation: Review the official SAP upgrade documentation for any prerequisites or steps that need to be followed before starting the upgrade.
  System Logs: Check system logs (transaction SM21) for any additional error messages or warnings that might provide more context about the issue.
  
  Best Practices:
  
  Plan Downtime: Schedule upgrades during planned downtime to minimize the impact of running jobs.
  Communicate with Users: Inform users about the upgrade schedule and potential impacts on system availability.
  Backup: Always ensure that you have a complete backup of the system before performing any upgrades.
  
  By following these steps, you should be able to resolve the SOI421 error and proceed with the upgrade successfully.