How To Fix RSANA_UMM_API021 - Error occurred while reading hierarchy objects

SAP Error Message - Details

• Message type: E = Error

• Message class: RSANA_UMM_API - UMM API Messages

• Message number: 021

• Message text: Error occurred while reading hierarchy objects

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 RSANA_UMM_API021 - Error occurred while reading hierarchy objects ?

  The SAP error message RSANA_UMM_API021 typically indicates that there was an issue while reading hierarchy objects in the context of SAP BW (Business Warehouse) or SAP Analytics. This error can occur due to various reasons, including issues with the hierarchy structure, data inconsistencies, or problems with the underlying database.
  Causes:
  
  Missing Hierarchy Objects: The hierarchy object that is being referenced may not exist or may have been deleted.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the hierarchy from being read correctly.
  Authorization Issues: The user may not have the necessary authorizations to access the hierarchy objects.
  Database Issues: There could be issues with the underlying database, such as corruption or connectivity problems.
  Transport Issues: If the hierarchy was transported from one system to another, there may have been issues during the transport process.
  
  Solutions:
  
  Check Hierarchy Objects: Verify that the hierarchy objects exist in the system and are correctly defined. You can do this by navigating to the relevant hierarchy in the SAP BW modeling tools.
  Data Consistency Check: Run consistency checks on the data to ensure that there are no inconsistencies. This can often be done using transaction codes like RSA1 (Data Warehousing Workbench) or RSCUSTV10 (for customizing).
  Authorization Check: Ensure that the user has the necessary authorizations to access the hierarchy objects. You can check this in the user roles and authorizations.
  Database Check: Check the database for any issues. This may involve running database consistency checks or consulting with your database administrator.
  Transport Logs: If the hierarchy was recently transported, check the transport logs for any errors or warnings that may indicate what went wrong during the transport process.
  Recreate Hierarchy: If the hierarchy object is corrupted or missing, you may need to recreate it.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1, RSCUSTV10, and RSD1 (for InfoObjects).
  SAP Notes: Check the SAP Support Portal for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Logs and Traces: Review system logs and traces for more detailed error messages that can provide additional context for the issue.
  
  If the problem persists after trying the above solutions, it may be beneficial to consult with SAP support or your internal SAP BW team for further assistance.