How To Fix RH400 - ***** BW Hierarchies for NDIs (SEM-CRM-B2B-...) *****

SAP Error Message - Details

• Message type: E = Error

• Message class: RH - BW: Hierarchies ( basic functions )

• Message number: 400

• Message text: ***** BW Hierarchies for NDIs (SEM-CRM-B2B-...) *****

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 RH400 - ***** BW Hierarchies for NDIs (SEM-CRM-B2B-...) ***** ?

  The SAP error message RH400 related to BW hierarchies for NDIs (Non-Data Items) typically indicates an issue with the configuration or data integrity in the SAP BW (Business Warehouse) system, particularly in the context of SEM-CRM (Strategic Enterprise Management - Customer Relationship Management).
  Cause:
  
  Missing Hierarchies: The error may occur if the required hierarchies for the NDIs are not defined or are missing in the BW system.
  Data Inconsistencies: There may be inconsistencies in the data that prevent the system from processing the hierarchies correctly.
  Configuration Issues: Incorrect configuration settings in the BW system or in the SEM-CRM module can lead to this error.
  Transport Issues: If the hierarchies were recently transported from another system, there may have been issues during the transport process.
  
  Solution:
  
  Check Hierarchies: Verify that all necessary hierarchies for the NDIs are defined in the BW system. You can do this by navigating to the hierarchy maintenance area in BW and ensuring that the required hierarchies exist and are active.
  Data Consistency Check: Run consistency checks on the data to identify any discrepancies. This can often be done using transaction codes like RSA1 (Data Warehousing Workbench) to analyze the InfoObjects and InfoProviders.
  Review Configuration: Review the configuration settings in both the BW and SEM-CRM modules to ensure they are set up correctly. This includes checking the settings for the NDIs and their associated hierarchies.
  Transport Logs: If the hierarchies were recently transported, check the transport logs for any errors or warnings that may indicate issues during the transport process.
  Rebuild Hierarchies: If necessary, you may need to rebuild the hierarchies or re-import them from a source system if they are missing or corrupted.
  Consult Documentation: Refer to SAP documentation or notes related to SEM-CRM and BW hierarchies for any specific guidance or known issues.
  
  Related Information:
  
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. You can search for relevant notes in the SAP Support Portal.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as RSA1 (Data Warehousing Workbench), RSRV (Consistency Check), and others that may help in diagnosing and resolving the issue.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed, and solutions shared.
  
  If the issue persists after trying the above solutions, it may be beneficial to reach out to SAP support for further assistance.