How To Fix ESH_TST_SMK_MSG060 - No authorization for changing object types

ESH_TST_SMK_MSG060 - Overview

• Message type: E = Error

• Message class: ESH_TST_SMK_MSG - Smoke Test

• Message number: 060

• Message text: No authorization for changing 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_MSG060 - No authorization for changing object types ?

  The SAP error message ESH_TST_SMK_MSG060 indicates that a user does not have the necessary authorization to change object types in the SAP system. This error typically arises in the context of the SAP Enterprise Search (ESH) or when working with the Semantic Search and Knowledge Management (SMK) functionalities.
  
  Cause:
  The error is caused by insufficient authorization for the user role that is attempting to perform the action. Specifically, the user lacks the necessary permissions to modify or change object types in the system.
  
  Solution:
  To resolve this issue, you can follow these steps:
  
  
  Check User Roles and Authorizations:
  
  Use transaction code SU01 to check the user profile and the roles assigned to the user.
  Review the authorizations assigned to the user’s roles, particularly focusing on the authorization objects related to ESH and SMK.
  
  
  
  Adjust Authorizations:
  
  If the user lacks the necessary authorizations, you may need to adjust the roles or create a new role that includes the required permissions.
  The