How To Fix TR360 - Request &1 is still being exported

SAP Error Message - Details

• Message type: E = Error

• Message class: TR - Change and Transport System

• Message number: 360

• Message text: Request &1 is still being exported

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 TR360 - Request &1 is still being exported ?

  The SAP error message TR360 indicates that a transport request (TR) is still being exported. This typically occurs when a transport request is in the process of being moved from one system to another, and the system is unable to complete the operation because the request is still in the export phase.
  Causes:
  
  Long Export Time: The transport request may be taking longer than expected to export due to large data volume or system performance issues.
  System Lock: The transport directory may be locked or there may be a lock on the transport request itself.
  Transport Directory Issues: Problems with the transport directory or file system can prevent the completion of the export.
  Background Job Issues: The background job responsible for the transport may have failed or is still running.
  Network Issues: If the transport is being sent to another system, network issues could delay the process.
  
  Solutions:
  
  Check Transport Logs: Review the transport logs for any errors or warnings that might indicate what is causing the delay.
  Monitor Background Jobs: Use transaction code SM37 to check the status of the background jobs related to the transport request. If the job is still running, you may need to wait for it to complete.
  Check Locks: Use transaction code SM12 to check for any locks on the transport request or related objects. If you find locks that are no longer needed, you can delete them.
  Check Transport Directory: Ensure that the transport directory is accessible and that there are no issues with the file system. You can check the transport directory settings in transaction SE03.
  Restart the Transport: If the transport request appears to be stuck, you may need to cancel the current export and restart the transport process. This can be done using transaction SE09 or SE10.
  System Performance: If the system is under heavy load, consider optimizing performance or scheduling the transport during off-peak hours.
  
  Related Information:
  
  Transaction Codes:
  
  SE09 / SE10: Transport Organizer
  SM37: Job Monitoring
  SM12: Lock Entries
  SE03: Transport Organizer Tools
  
  
  SAP Notes: Check SAP Notes related to transport issues for any specific patches or updates that may address known problems.
  Documentation: Refer to SAP Help documentation for detailed information on transport management and troubleshooting.
  
  If the issue persists after trying the above solutions, it may be necessary to consult with your SAP Basis team or SAP support for further assistance.