How To Fix ACM117 - Hierarchy data table (metadata header) &1 / &2 deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: ACM - Message-Class for all ACM functions/exceptions

• Message number: 117

• Message text: Hierarchy data table (metadata header) &1 / &2 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 ACM117 - Hierarchy data table (metadata header) &1 / &2 deleted ?

  The SAP error message ACM117 indicates that a hierarchy data table, specifically the metadata header, has been deleted. This error typically arises in the context of SAP's Analytical and Reporting tools, where hierarchies are used to structure data for reporting and analysis.
  
  Cause:
  
  Deletion of Hierarchy: The most common cause of this error is that the hierarchy or its metadata has been deleted from the system. This could happen due to manual deletion, data migration, or system updates.
  Inconsistent Data: If there are inconsistencies in the data or if the hierarchy is not properly defined, it may lead to this error.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the hierarchy, leading to the perception that it has been deleted.
  
  
  Solution:
  
  Check Hierarchy Existence: Verify if the hierarchy still exists in the system. You can do this by navigating to the relevant transaction codes (like RSH1 for InfoObjects) to check if