How To Fix RSMPC080 - Hierarchy &1 was not found in table 'RSHIEDIR'. Terminated

SAP Error Message - Details

• Message type: E = Error

• Message class: RSMPC - Messages for Process Chains of Generic Processes

• Message number: 080

• Message text: Hierarchy &1 was not found in table 'RSHIEDIR'. Terminated

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 RSMPC080 - Hierarchy &1 was not found in table 'RSHIEDIR'. Terminated ?

  The SAP error message RSMPC080 indicates that a specific hierarchy (denoted as &1) could not be found in the table 'RSHIEDIR'. This error typically occurs in the context of SAP BW (Business Warehouse) when trying to access or use a hierarchy that is not defined or has been deleted.
  Cause:
  
  Hierarchy Not Defined: The hierarchy you are trying to access does not exist in the system.
  Deleted Hierarchy: The hierarchy may have been deleted or not activated properly.
  Incorrect Hierarchy Name: There might be a typo or incorrect reference to the hierarchy name in your query or report.
  Transport Issues: If the hierarchy was recently transported from another system, it may not have been transported correctly.
  
  Solution:
  
  
  Check Hierarchy Existence:
  
  Go to the transaction code RSA1 (Data Warehousing Workbench).
  Navigate to the InfoObject that should contain the hierarchy.
  Check if the hierarchy is listed under the "Hierarchies" tab.
  
  
  
  Recreate or Activate Hierarchy:
  
  If the hierarchy is missing, you may need to recreate it.
  If it exists but is inactive, activate it.
  
  
  
  Verify Hierarchy Name:
  
  Ensure that the name of the hierarchy you are using in your query or report matches exactly with what is defined in the system.
  
  
  
  Transport Check:
  
  If the hierarchy was supposed to be transported, check the transport logs to ensure it was successfully transported.
  If there were issues, you may need to re-transport the hierarchy.
  
  
  
  Check Authorizations:
  
  Ensure that you have the necessary authorizations to access the hierarchy.
  
  
  
  Consult Documentation:
  
  Review any relevant documentation or notes from SAP regarding the specific hierarchy and its usage.
  
  
  
  Related Information:
  
  Table RSHIEDIR: This table contains the directory of hierarchies in SAP BW. You can check this table directly using transaction SE11 or SE16 to see if the hierarchy exists.
  Transaction Codes:
  
  RSA1: Data Warehousing Workbench
  SE11: Data Dictionary
  SE16: Data Browser
  
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  
  If the problem persists after following these steps, consider reaching out to your SAP Basis or BW support team for further assistance.