How To Fix TR736 - &: Import to & has already been initiated

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 736

• Message text: &: Import to & has already been initiated

What causes this issue?

The import of (transport/...) request &V1& into system &V2& cannot be
started because the request has already been imported.

System Response

The function was cancelled.

How to fix this error?

Wait for the results of the current import. You can repeat the faulty
imports, depending on the results of the current one.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message TR736 - &: Import to & has already been initiated ?

  The SAP error message TR736 typically indicates that an import process for a transport request has already been initiated for the specified target system. This can occur in various scenarios, such as when multiple users attempt to import the same transport request simultaneously or if a previous import process is still running or has not been completed.
  Cause:
  
  Concurrent Import Attempts: Another user or process is already importing the same transport request.
  Previous Import Still Running: The import process for the transport request has not yet completed, possibly due to a long-running operation or a lock.
  System Lock: The target system may be locked for transport imports due to maintenance or other administrative tasks.
  
  Solution:
  
  
  Check Import Status: 
  
  Use transaction code STMS to check the status of the transport request in the Transport Management System (TMS). Look for any ongoing imports and their statuses.
  
  
  
  Wait for Completion: 
  
  If another import is in progress, wait for it to complete before attempting to import the transport request again.
  
  
  
  Cancel or Terminate the Import: 
  
  If you determine that the previous import is stuck or has failed, you may need to cancel or terminate it. This can be done through the TMS interface or by using transaction SM37 to check for any background jobs related to the import and cancel them if necessary.
  
  
  
  Check for Locks: 
  
  Use transaction SM12 to check for any locks that might be preventing the import. If you find locks related to the transport request, you may need to release them, but be cautious and ensure that it is safe to do so.
  
  
  
  Consult Logs: 
  
  Review the transport logs for any errors or warnings that might provide more context on why the import is not proceeding.
  
  
  
  Retry the Import: 
  
  Once you have confirmed that no other import is in progress and any locks have been resolved, you can retry the import of the transport request.
  
  
  
  Related Information:
  
  Transport Management System (TMS): This is the SAP tool used for managing transport requests and imports across different systems in a landscape.
  Transaction Codes:
  
  STMS: Transport Management System
  SM37: Job Monitoring
  SM12: Lock Entries
  
  
  SAP Notes: Check for any relevant SAP Notes that might address specific issues related to transport imports and the TR736 error.
  
  If the problem persists after following these steps, it may be beneficial to consult with your SAP Basis team or refer to SAP support for further assistance.