How To Fix RSM358 - No hierarchies exist

RSM358 - Overview

• 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