How To Fix ESH_TST_SMK_MSG058 - No authorization for creating object types

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_TST_SMK_MSG - Smoke Test

• Message number: 058

• Message text: No authorization for creating object types

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 ESH_TST_SMK_MSG058 - No authorization for creating object types ?

  The SAP error message ESH_TST_SMK_MSG058 indicates that a user does not have the necessary authorization to create object types in the SAP system. This error typically arises in the context of the SAP Enterprise Search or similar applications where object types need to be defined or modified.
  Cause:
  The primary cause of this error is a lack of appropriate authorizations assigned to the user role. Specifically, the user may not have the necessary permissions to create or modify object types in the system.
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error. This will show you the last authorization check and help identify which specific authorization is missing.
  Alternatively, you can use transaction code SU01 to check the user’s roles and authorizations.
  
  
  
  Review Role Assignments:
  
  Ensure that the user has the correct roles assigned that include the necessary authorizations for creating object types. This may involve checking the roles assigned to the user in transaction PFCG.
  
  
  
  Modify Roles:
  
  If the required authorizations are missing, you may need to modify the existing roles or create a new role that includes the necessary authorizations. This typically involves:
  
  Adding the relevant authorization objects that allow for the creation of object types.
  Common authorization objects that may be relevant include S_TCODE (Transaction Codes) and specific objects related to the application area.
  
  
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary permissions to modify roles or authorizations, you may need to consult with your SAP security team or administrator to request the required access.
  
  
  
  Testing:
  
  After making the necessary changes, have the user log out and log back in to ensure that the new authorizations take effect. Then, attempt to create the object type again to verify that the issue is resolved.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that pertain to the specific functionality you are trying to access. This can often be found in SAP documentation or by consulting with your SAP security team.
  SAP Notes: Check for any relevant SAP Notes that may provide additional context or solutions for this specific error message.
  Documentation: Review the SAP Help Portal or other documentation related to the specific module or functionality you are working with to understand the required authorizations better.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the error message ESH_TST_SMK_MSG058.