How To Fix RSM358 - No hierarchies exist

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 358

• Message text: No hierarchies exist

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 RSM358 - No hierarchies exist ?

  The SAP error message RSM358 ("No hierarchies exist") typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when you are trying to access or display a hierarchy that has not been defined or is not available in the system. This can happen in various scenarios, such as when working with InfoObjects, queries, or reports that rely on hierarchies for data representation.
  Cause:
  
  Missing Hierarchy Definition: The hierarchy you are trying to access has not been created or defined in the system.
  Incorrect InfoObject: The InfoObject you are using may not have any associated hierarchies.
  Data Loading Issues: There may be issues with the data loading process that prevent hierarchies from being populated.
  Authorization Issues: The user may not have the necessary authorizations to view the hierarchies.
  Incorrect Query Design: The query or report may be incorrectly designed, leading to the system not being able to find the required hierarchy.
  
  Solution:
  
  
  Check Hierarchy Definition:
  
  Go to the relevant InfoObject in the SAP BW system and check if the hierarchy is defined. You can do this by navigating to the InfoObject maintenance transaction (e.g., RSD1).
  If the hierarchy is missing, create it by defining the necessary nodes and structure.
  
  
  
  Verify InfoObject Settings:
  
  Ensure that the InfoObject you are working with is set up to support hierarchies. Check the properties of the InfoObject to confirm that it is configured correctly.
  
  
  
  Data Load Verification:
  
  Check the data loading process to ensure that the hierarchy data is being loaded correctly. You can review the data load logs for any errors or warnings that might indicate issues.
  
  
  
  Authorization Check:
  
  Ensure that the user has the necessary authorizations to access the hierarchies. This can be checked in the user roles and authorizations assigned to the user.
  
  
  
  Query Design Review:
  
  Review the query or report design to ensure that it is correctly referencing the hierarchy. Make sure that the hierarchy is included in the query structure.
  
  
  
  Rebuild Hierarchies:
  
  If the hierarchy is defined but still not showing, consider rebuilding the hierarchy or refreshing the data in the InfoProvider.
  
  
  
  Related Information:
  
  Transaction Codes: 
  
  RSD1: InfoObject maintenance
  RSA1: Data Warehousing Workbench
  
  
  Documentation: Refer to SAP Help documentation for detailed steps on creating and managing hierarchies in BW.
  SAP Notes: Check for any relevant SAP Notes that may address specific issues related to hierarchies and the RSM358 error.
  
  By following these steps, you should be able to identify the cause of the RSM358 error and implement the appropriate solution.