How To Fix ESH_IEF_MSG021 - Import of transported repository objects started in background

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_IEF_MSG - Import/Export Framework

• Message number: 021

• Message text: Import of transported repository objects started in background

What causes this issue?

A background job has been scheduled to import all pending software
component updates.

System Response

-

How to fix this error?

-

Procedure for System Administrators

The name of background job is &v1& (see transaction SM37).

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_IEF_MSG021 - Import of transported repository objects started in background ?

  The SAP error message ESH_IEF_MSG021 indicates that the import of transported repository objects has started in the background. This message is typically related to the SAP Enterprise Search (SAP ESH) and can occur during the import of transport requests that contain changes to the repository objects.
  Cause:
  
  Background Processing: The import process for the transport request is initiated in the background, which means that the system is processing the request without immediate user interaction.
  Long-running Process: The import might take a significant amount of time, especially if it involves large or complex objects.
  System Load: High system load or resource constraints can also lead to delays in processing the import.
  
  Solution:
  
  Check Background Jobs: Use transaction code SM37 to check the status of background jobs. Look for jobs related to the transport request and see if they are still running or if they have completed successfully.
  Monitor Import Logs: Review the import logs for any errors or warnings that may have occurred during the import process. This can provide insights into any issues that need to be addressed.
  Wait for Completion: If the import is still running, it may simply require more time to complete. Monitor the job until it finishes.
  Check for Locks: Ensure that there are no locks on the objects being imported. You can use transaction code SM12 to check for and release any locks if necessary.
  Review Transport Request: If the import fails or takes too long, review the transport request for any issues. You may need to adjust the contents of the transport or split it into smaller requests if it is too large.
  System Performance: If the system is under heavy load, consider scheduling the import during off-peak hours to improve performance.
  
  Related Information:
  
  Transaction Codes:
  
  SM37: Monitor background jobs.
  SM12: Check and manage locks.
  SE01: Transport Organizer for managing transport requests.
  
  
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to transport imports or the ESH component.
  Documentation: Refer to the SAP Help Portal for documentation on SAP ESH and transport management.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis team or reach out to SAP support for further assistance.