How To Fix GD072 - Cleanup ended with status: &1

SAP Error Message - Details

• Message type: E = Error

• Message class: GD - EDT: External data transfer

• Message number: 072

• Message text: Cleanup ended with status: &1

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 GD072 - Cleanup ended with status: &1 ?

  The SAP error message GD072, which states "Cleanup ended with status: &1," typically relates to issues encountered during the cleanup process of the SAP system, particularly in the context of data archiving or deletion processes. The status code (&1) provides additional information about the specific nature of the error.
  Causes:
  
  Insufficient Authorizations: The user executing the cleanup may not have the necessary authorizations to perform the operation.
  Database Issues: There may be underlying database issues, such as locks, corruption, or connectivity problems.
  Configuration Errors: Incorrect configuration settings in the archiving or cleanup process can lead to failures.
  Resource Limitations: Insufficient system resources (e.g., memory, disk space) can cause the cleanup process to fail.
  Data Integrity Issues: Problems with the data being processed, such as inconsistencies or violations of referential integrity, can lead to errors.
  
  Solutions:
  
  Check Authorizations: Ensure that the user has the necessary authorizations to perform the cleanup operation.
  Review Logs: Check the application logs (transaction SLG1) and the system logs (transaction SM21) for more detailed error messages that can provide insights into the cause of the failure.
  Database Health Check: Perform a health check on the database to ensure there are no locks or corruption issues. You may need to consult your database administrator.
  Configuration Review: Verify the configuration settings for the cleanup process to ensure they are correct and aligned with best practices.
  Resource Monitoring: Monitor system resources during the cleanup process to identify any bottlenecks or limitations.
  Retry the Process: After addressing any identified issues, retry the cleanup process to see if the problem persists.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SARA (Archive Administration) and SARI (Archive Information System) for managing archiving processes.
  SAP Notes: Check SAP Notes for any known issues or patches related to the GD072 error. You can search for specific notes in the SAP Support Portal.
  Documentation: Review SAP documentation on data archiving and cleanup processes for best practices and troubleshooting steps.
  
  If the issue persists after trying the above solutions, it may be beneficial to engage SAP support for further assistance.