Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: UT - Logical transports
Message number: 117
Message text: Import data of request & has already been cleaned up
You want to clean up the import data for request &V1&. However, this
has already been done.
The function is not executed.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
UT117
- Import data of request & has already been cleaned up ?The SAP error message UT117, which states "Import data of request & has already been cleaned up," typically occurs in the context of data transport or import processes within the SAP system. This error indicates that the data associated with a specific transport request has been deleted or cleaned up, making it unavailable for import.
Cause:
- Data Cleanup: The transport request data may have been cleaned up due to system maintenance or housekeeping activities. This can happen if the transport request is older and the system has been configured to delete old transport data.
- Transport Request Status: The transport request may have been marked as completed or released, and the associated data has been removed from the system.
- System Configuration: The system may have settings that automatically clean up transport requests after a certain period or after they have been imported successfully.
Solution:
- Check Transport Request Status: Verify the status of the transport request in the Transport Management System (TMS). Ensure that the request is still valid and has not been deleted.
- Recreate the Transport Request: If the transport request has been cleaned up, you may need to recreate it. This involves re-transporting the objects or data that were originally included in the request.
- Review System Settings: Check the system settings related to transport request cleanup. If necessary, adjust the settings to prevent premature cleanup of transport requests in the future.
- Consult Logs: Review the transport logs and system logs for any additional information that might indicate why the request was cleaned up.
- Contact Basis Team: If you are unable to resolve the issue, it may be necessary to contact your SAP Basis team or system administrator for further assistance. They can provide insights into system configurations and help recover or recreate the necessary transport request.
Related Information:
By following these steps, you should be able to address the UT117 error and ensure that your transport requests are managed effectively.
Get instant SAP help. Sign up for our Free Essentials Plan.
UT116
Cleanup of import data in client & locked by user &
What causes this issue? You want to clean up the import data for a request. The cleanup of the import data is currently blocked in client &V1&...
UT115
Internal error during cleanup of import data for request &
What causes this issue? You want to clean up the import data for the request &V1&. While doing this an internal error occurred (generation of...
UT118
The request does not contain object & for import
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
UT119
There are no objects for import in the request
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.