How To Fix J-805 - Unable to find the saved characteristic hierarchies

SAP Error Message - Details

• Message type: E = Error

• Message class: J- -

• Message number: 805

• Message text: Unable to find the saved characteristic hierarchies

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 J-805 - Unable to find the saved characteristic hierarchies ?

  The SAP error message J-805, "Unable to find the saved characteristic hierarchies," typically occurs in the context of SAP BW (Business Warehouse) or SAP BI (Business Intelligence) when the system is unable to locate the characteristic hierarchies that are required for a query or report. This can happen for several reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing Hierarchies: The characteristic hierarchies may not have been created or saved properly in the system.
  Transport Issues: If the hierarchies were transported from one system to another (e.g., from development to production), there may have been issues during the transport process.
  Data Model Changes: Changes in the data model or the underlying InfoObjects may have led to the hierarchies being invalid or deleted.
  Authorization Issues: The user may not have the necessary authorizations to access the characteristic hierarchies.
  Incorrect Query Design: The query may be incorrectly designed, referencing hierarchies that do not exist or are not active.
  
  Solutions:
  
  Check Hierarchy Existence: Verify that the characteristic hierarchies exist in the system. You can do this by navigating to the relevant InfoObject in the SAP BW modeling tools and checking the hierarchy settings.
  Recreate Hierarchies: If the hierarchies are missing, you may need to recreate them. This can be done in the InfoObject maintenance screen.
  Transport Check: If the hierarchies were supposed to be transported, check the transport logs for any errors and ensure that the transport was successful.
  Authorization Check: Ensure that the user has the necessary authorizations to access the characteristic hierarchies. This can be checked in the user roles and authorizations.
  Query Redesign: Review the query design in BEx Query Designer or similar tools to ensure that it is correctly referencing the existing hierarchies.
  Activate Hierarchies: If the hierarchies exist but are not active, make sure to activate them in the InfoObject settings.
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to error J-805 for any specific patches or updates that may address this issue.
  Documentation: Refer to the SAP BW documentation for more details on managing characteristic hierarchies and troubleshooting common issues.
  Community Forums: Engage with SAP community forums or support channels for additional insights and solutions from other users who may have encountered similar issues.
  
  By following these steps, you should be able to identify the cause of the J-805 error and implement a suitable solution. If the problem persists, consider reaching out to SAP support for further assistance.