How To Fix SHDI022 - You are not authorized to create this root.

SAP Error Message - Details

• Message type: E = Error

• Message class: SHDI - Texts Image archive Transaction variants

• Message number: 022

• Message text: You are not authorized to create this root.

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 SHDI022 - You are not authorized to create this root. ?

  The SAP error message SHDI022, which states "You are not authorized to create this root," typically occurs in the context of SAP's Hierarchy Management or when dealing with certain organizational structures. This error indicates that the user does not have the necessary authorizations to create a specific root node in a hierarchy.
  Cause:
  
  Authorization Issues: The primary cause of this error is a lack of appropriate authorizations assigned to the user. The user may not have the necessary roles or permissions to create or modify hierarchy structures.
  Role Configuration: The roles assigned to the user may not include the necessary transaction codes or object authorizations required for hierarchy management.
  Hierarchy Settings: There may be specific settings or restrictions in the hierarchy configuration that prevent certain users from creating root nodes.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to check for missing authorizations. This will show you which authorization checks failed.
  Review the user's roles and profiles in transaction SU01 or PFCG to ensure they have the necessary permissions.
  
  
  
  Assign Necessary Roles:
  
  If the user lacks the required roles, work with your SAP security team to assign the appropriate roles that include permissions for hierarchy management.
  Ensure that the roles include the necessary authorization objects, such as S_HIER (Hierarchy Management) or any other relevant objects.
  
  
  
  Review Hierarchy Configuration:
  
  Check the configuration settings for the hierarchy to ensure there are no restrictions that would prevent the creation of root nodes.
  Consult with your SAP Basis or configuration team if there are specific settings that need to be adjusted.
  
  
  
  Testing:
  
  After making changes to roles or configurations, have the user log out and log back in to ensure that the new authorizations take effect.
  Attempt to create the root node again to verify that the issue has been resolved.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SU01 (User Maintenance), PFCG (Role Maintenance), and SU53 (Authorization Check).
  Authorization Objects: Understand the specific authorization objects related to hierarchy management, which may include S_HIER, S_TCODE, and others depending on your SAP system configuration.
  Documentation: Refer to SAP documentation or help resources for detailed information on hierarchy management and authorization concepts.
  
  If the issue persists after checking authorizations and configurations, it may be beneficial to consult with SAP support or your internal SAP team for further assistance.