How To Fix RSDD355 - Error while activating hierarchy &1 (&2)

SAP Error Message - Details

• Message type: E = Error

• Message class: RSDD - Message class for data manager

• Message number: 355

• Message text: Error while activating hierarchy &1 (&2)

What causes this issue?

An error occurred for which no specific details can currently be
provided.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Try alternative options to get more information about the error, for
example, by calling the following transactions:
List of short dumps (transaction ST22)
System log (transaction SM21)
Job log (transaction SM37)

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message RSDD355 - Error while activating hierarchy &1 (&2) ?

  The SAP error message RSDD355, which states "Error while activating hierarchy &1 (&2)," typically occurs in the context of SAP BW (Business Warehouse) when there is an issue with activating a hierarchy in the system. This error can arise due to various reasons, and understanding the cause is essential for finding a solution.
  Causes of RSDD355 Error
  
  
  Data Inconsistencies: There may be inconsistencies in the data that the hierarchy is based on, such as missing or incorrect entries in the underlying InfoObject.
  
  
  Hierarchy Structure Issues: The hierarchy structure might be incorrect, such as circular references or missing parent-child relationships.
  
  
  Authorization Issues: The user may not have the necessary authorizations to activate the hierarchy.
  
  
  Technical Issues: There could be technical issues related to the BW system, such as problems with the database or transport issues.
  
  
  Locking Issues: The hierarchy might be locked by another process or user, preventing activation.
  
  
  Incorrect Hierarchy Type: The hierarchy type may not be compatible with the InfoObject or may not be defined correctly.
  
  
  Solutions to RSDD355 Error
  
  
  Check Data Consistency:
  
  Verify the data in the InfoObject that the hierarchy is based on. Ensure that all necessary entries are present and correct.
  
  
  
  Review Hierarchy Structure:
  
  Examine the hierarchy structure for any circular references or missing relationships. Use transaction RSD1 to check the hierarchy.
  
  
  
  Check Authorizations:
  
  Ensure that the user attempting to activate the hierarchy has the necessary authorizations. You can check this in transaction SU53 or by consulting with your security team.
  
  
  
  Technical Checks:
  
  Look for any technical issues in the BW system. Check the system logs (transaction SLG1) for any related error messages.
  
  
  
  Release Locks:
  
  If the hierarchy is locked, identify the user or process that is holding the lock and resolve it. You can use transaction SM12 to check for locks.
  
  
  
  Hierarchy Type Validation:
  
  Ensure that the hierarchy type is correctly defined and compatible with the InfoObject. You can check this in the hierarchy maintenance area.
  
  
  
  Recreate the Hierarchy:
  
  If the issue persists, consider deleting and recreating the hierarchy. This can sometimes resolve underlying issues.
  
  
  
  Consult SAP Notes:
  
  Check the SAP Support Portal for any relevant SAP Notes that may address this specific error. There may be patches or updates that resolve known issues.
  
  
  
  Related Information
  
  
  Transaction Codes:
  
  RSD1: Hierarchy maintenance
  SLG1: Application log
  SM12: Lock entries
  SU53: Authorization check
  
  
  
  SAP Documentation: Refer to the official SAP documentation for more detailed information on hierarchy management in BW.
  
  
  SAP Community: Engage with the SAP Community forums for insights from other users who may have encountered similar issues.
  
  
  By following these steps, you should be able to identify the cause of the RSDD355 error and implement a suitable solution. If the problem persists, consider reaching out to SAP support for further assistance.