How To Fix COM_DML_CUST172 - Archiving object & could not be deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: COM_DML_CUST - MDF Messages

• Message number: 172

• Message text: Archiving object & could not be deleted

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 COM_DML_CUST172 - Archiving object & could not be deleted ?

  The SAP error message COM_DML_CUST172 typically indicates that there is an issue with the archiving process for a specific object, and it states that the archiving object could not be deleted. This error can occur in various scenarios, particularly when dealing with data archiving in SAP systems.
  Cause
  The error can be caused by several factors, including:
  
  Data Dependencies: The archiving object may have dependencies or references in other tables or objects that prevent it from being deleted.
  Authorization Issues: The user executing the archiving process may not have the necessary authorizations to delete the archiving object.
  Incomplete Archiving Process: The archiving process may not have been completed successfully, leaving the object in a state that cannot be deleted.
  Configuration Issues: There may be configuration settings in the archiving object that are not set correctly, leading to issues during deletion.
  Database Constraints: There may be database constraints or locks that prevent the deletion of the archiving object.
  
  Solution
  To resolve the error, you can take the following steps:
  
  Check Dependencies: Investigate if there are any dependencies or references to the archiving object in other tables. You may need to delete or archive those dependencies first.
  Review Authorizations: Ensure that the user has the necessary authorizations to perform the deletion. You may need to consult with your SAP security team.
  Verify Archiving Status: Check the status of the archiving process. If it was incomplete, you may need to rerun the archiving process or check for any errors that occurred during the archiving.
  Configuration Review: Review the configuration settings for the archiving object in transaction SARA. Ensure that all settings are correct and that the object is properly configured for archiving and deletion.
  Database Checks: Check for any database locks or constraints that may be preventing the deletion. You can use database tools or transaction codes like SM12 to check for locks.
  Consult SAP Notes: Look for relevant SAP Notes that may address this specific error. SAP Notes often provide solutions or workarounds for known issues.
  
  Related Information
  
  
  Transaction Codes: 
  
  SARA: For managing archiving objects.
  SARI: For managing the archiving process.
  SM12: To check for locks on database tables.
  SE11: To view the data dictionary and check table dependencies.
  
  
  
  SAP Documentation: Refer to the official SAP documentation for archiving processes and best practices.
  
  
  SAP Community: Engage with the SAP Community forums to see if other users have encountered similar issues and what solutions they found effective.
  
  
  If the issue persists after trying the above solutions, it may be necessary to involve your SAP Basis team or SAP support for further investigation.