How To Fix RSCV343 - Check hierarchies for InfoObject &1

RSCV343 - Overview

• Message type: E = Error

• Message class: RSCV - Analysis of BW objects (InfoCubes...)

• Message number: 343

• Message text: Check hierarchies for InfoObject &1

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 RSCV343 - Check hierarchies for InfoObject &1 ?

  The SAP error message RSCV343 "Check hierarchies for InfoObject &1" typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with the hierarchy associated with a specific InfoObject. This error can arise during various operations, such as data loading, reporting, or when trying to display hierarchies.
  
  Cause:
  
  Missing Hierarchy: The specified InfoObject does not have a hierarchy defined, or the hierarchy is not activated.
  Inconsistent Hierarchy: The hierarchy may be inconsistent or corrupted, which can happen due to data inconsistencies or issues during data loading.
  Authorization Issues: The user may not have the necessary authorizations to access the hierarchy for the specified InfoObject.
  Hierarchy Structure Changes: Changes made to the hierarchy structure (like adding or deleting nodes) that have not been properly reflected in the InfoObject.
  
  
  Solution:
  
  
  Check Hierarchy Definition:
  
  Go to the hierarchy maintenance transaction (e.g., RSH1 for Hierarchy Maintenance).
  Verify that the hierarchy for the specified InfoObject (&1) exists and is active.
  If