How To Fix ACMDT_OBJSTATUS368 - Obsolete generated hierarchy view entry exists

SAP Error Message - Details

• Message type: E = Error

• Message class: ACMDT_OBJSTATUS - ACM: Messages for the Object-Status of Designtime-Objects

• Message number: 368

• Message text: Obsolete generated hierarchy view entry exists

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 ACMDT_OBJSTATUS368 - Obsolete generated hierarchy view entry exists ?

  The SAP error message ACMDT_OBJSTATUS368 indicates that there is an obsolete generated hierarchy view entry in the system. This typically occurs in the context of Asset Accounting (FI-AA) when there are inconsistencies or issues with the hierarchy of asset master data.
  Cause:
  
  Obsolete Entries: The error is triggered when the system detects that there are entries in the hierarchy that are no longer valid or have been marked as obsolete.
  Data Inconsistencies: This can happen due to changes in the asset master data, such as deletions or modifications that have not been properly reflected in the hierarchy.
  System Updates: Sometimes, after system updates or migrations, the hierarchy may not be correctly regenerated, leading to obsolete entries.
  
  Solution:
  
  Check Hierarchy Entries: Review the asset hierarchy entries to identify any obsolete or invalid entries. You can do this using transaction codes like AO90 (for displaying asset hierarchy) or AO91 (for maintaining asset hierarchy).
  Reorganize Hierarchy: Use the transaction AO92 to reorganize the asset hierarchy. This can help in removing obsolete entries and ensuring that the hierarchy is up to date.
  Delete Obsolete Entries: If you identify specific obsolete entries, you may need to delete them manually. Ensure that you have the necessary authorizations to perform this action.
  Run Consistency Checks: Use the transaction AABO to run consistency checks on the asset accounting data. This can help identify and rectify any inconsistencies in the asset data.
  Consult Documentation: Refer to SAP documentation or notes related to asset accounting and hierarchy management for additional guidance and best practices.
  
  Related Information:
  
  Transaction Codes:
  
  AO90: Display Asset Hierarchy
  AO91: Maintain Asset Hierarchy
  AO92: Reorganize Asset Hierarchy
  AABO: Consistency Check for Asset Accounting
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Support: If the issue persists after attempting the above solutions, consider reaching out to SAP support for further assistance.
  
  By following these steps, you should be able to resolve the error message ACMDT_OBJSTATUS368 and ensure that your asset hierarchy is functioning correctly.