How To Fix RSM928 - Cannot create hierarchy header in RSOSOHIE for DS & LS & InfoPackage &

SAP Error Message - Details

• Message type: E = Error

• Message class: RSM -

• Message number: 928

• Message text: Cannot create hierarchy header in RSOSOHIE for DS & LS & InfoPackage &

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 RSM928 - Cannot create hierarchy header in RSOSOHIE for DS & LS & InfoPackage & ?

  The SAP error message RSM928, which states "Cannot create hierarchy header in RSOSOHIE for DS & LS & InfoPackage &," typically occurs in the context of SAP BW (Business Warehouse) when there are issues related to the creation of hierarchy headers for a DataSource (DS) or InfoPackage (IP). This error can arise due to various reasons, and here are some common causes, solutions, and related information:
  Causes:
  
  Missing or Incorrect Hierarchy Definition: The hierarchy definition in the InfoObject may be missing or incorrectly defined.
  DataSource Issues: The DataSource may not be properly configured or may not contain the necessary data for hierarchy creation.
  Authorization Issues: The user executing the InfoPackage may not have the necessary authorizations to create or modify hierarchies.
  Technical Issues: There may be technical issues in the BW system, such as inconsistencies in the data model or problems with the underlying database.
  InfoPackage Settings: The settings in the InfoPackage may not be correctly configured to handle hierarchies.
  
  Solutions:
  
  
  Check Hierarchy Definition:
  
  Go to the InfoObject maintenance and ensure that the hierarchy is correctly defined.
  Make sure that the hierarchy type is set correctly and that the hierarchy nodes are properly structured.
  
  
  
  Validate DataSource:
  
  Check the DataSource settings and ensure that it is active and correctly configured.
  Test the DataSource to ensure it is returning the expected data.
  
  
  
  Review Authorizations:
  
  Ensure that the user executing the InfoPackage has the necessary authorizations to create and modify hierarchies.
  Check the authorization objects related to the InfoObject and hierarchy management.
  
  
  
  Check InfoPackage Settings:
  
  Review the settings in the InfoPackage to ensure that it is configured to handle hierarchies.
  Make sure that the "Hierarchy" option is selected if applicable.
  
  
  
  Technical Checks:
  
  Perform a consistency check on the InfoObject and the DataSource.
  Check for any inconsistencies in the data model or issues in the underlying database.
  
  
  
  Recreate Hierarchy:
  
  If the hierarchy is corrupted, consider deleting and recreating it.
  
  
  
  Related Information:
  
  Transaction Codes: You may use transaction codes like RSA1 (Data Warehousing Workbench) to check InfoObjects and DataSources.
  SAP Notes: Check SAP Notes related to this error message for any specific patches or updates that may resolve the issue.
  Logs and Traces: Review the application logs (transaction SLG1) for more detailed error messages that can provide additional context.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP Basis or BW team for further investigation or to reach out to SAP support for assistance.