How To Fix ESH_SEARCH087 - Authorization check &1, template &2, node &3: Attribute &4 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_SEARCH - ESH Search

• Message number: 087

• Message text: Authorization check &1, template &2, node &3: Attribute &4 does not exist

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_SEARCH087 - Authorization check &1, template &2, node &3: Attribute &4 does not exist ?

  The SAP error message ESH_SEARCH087 typically indicates an authorization issue related to the Enterprise Search (ESH) functionality in SAP. This error occurs when a user attempts to access a search template or node that references an attribute that does not exist or is not authorized for the user.
  Cause:
  
  Non-Existent Attribute: The attribute specified in the error message does not exist in the search model or the underlying data source.
  Authorization Issues: The user does not have the necessary authorizations to access the specified attribute or the search template.
  Configuration Issues: There may be a misconfiguration in the search model or the search template that leads to the reference of an invalid or non-existent attribute.
  
  Solution:
  
  
  Check Attribute Existence:
  
  Verify that the attribute mentioned in the error message exists in the relevant search model. You can do this by checking the configuration of the search model in the SAP system.
  
  
  
  Review Authorizations:
  
  Ensure that the user has the necessary authorizations to access the specified attribute. This may involve checking the user's roles and authorizations in the SAP system.
  You can use transaction codes like SU53 to analyze authorization failures after the error occurs.
  
  
  
  Update Search Model:
  
  If the attribute is indeed missing, you may need to update the search model to include the required attribute. This may involve modifying the search model configuration in the ESH administration.
  
  
  
  Check Search Template Configuration:
  
  Review the configuration of the search template to ensure that it is correctly set up and does not reference any invalid attributes.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to ESH and the specific error message for additional guidance and troubleshooting steps.
  
  
  
  System Logs:
  
  Check system logs (transaction SLG1) for any additional error messages or warnings that may provide more context about the issue.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  EHS_SEARCH_ADMIN for managing search models and templates.
  SU53 for checking authorization issues.
  SLG1 for viewing application logs.
  
  
  
  SAP Notes: 
  
  Search for relevant SAP Notes in the SAP Support Portal that may address known issues or provide patches related to ESH and authorization checks.
  
  
  
  Community Forums: 
  
  Consider checking SAP Community forums or other user groups for similar issues and solutions shared by other users.
  
  
  
  By following these steps, you should be able to identify the root cause of the ESH_SEARCH087 error and implement the necessary solutions to resolve it.