How To Fix ESH_EX063 - Referenced default role with reference key &1 does not exist

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_EX - Extraction

• Message number: 063

• Message text: Referenced default role with reference key &1 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_EX063 - Referenced default role with reference key &1 does not exist ?

  The SAP error message ESH_EX063 indicates that a referenced default role, identified by the reference key provided in the error message, does not exist in the system. This error typically occurs in the context of the SAP Enterprise Search (SAP ESH) or when dealing with roles and authorizations in SAP systems.
  Cause:
  
  Missing Role: The default role that is being referenced in the system is either not created or has been deleted.
  Incorrect Configuration: There may be a misconfiguration in the settings where the system is trying to reference a role that is not correctly defined.
  Transport Issues: If the role was transported from another system, it may not have been included in the transport request, or the transport may have failed.
  Authorization Issues: The user may not have the necessary authorizations to access the role, leading to the perception that it does not exist.
  
  Solution:
  
  
  Check Role Existence:
  
  Go to transaction PFCG (Role Maintenance) and check if the role with the reference key exists.
  If it does not exist, you may need to create it or restore it from a backup if it was deleted.
  
  
  
  Create the Role:
  
  If the role is missing, create a new role in transaction PFCG and ensure it has the necessary authorizations and settings.
  
  
  
  Review Configuration:
  
  Check the configuration settings in the relevant areas (like the ESH configuration) to ensure that the correct role is being referenced.
  Make sure that the role is correctly assigned to the relevant users or user groups.
  
  
  
  Transport Check:
  
  If the role was supposed to be transported, check the transport logs to ensure that the transport was successful and that the role was included.
  
  
  
  Authorization Check:
  
  Ensure that the user encountering the error has the necessary authorizations to access the role. You can use transaction SU53 to analyze authorization issues.
  
  
  
  System Logs:
  
  Check the system logs for any additional error messages or warnings that might provide more context about the issue.
  
  
  
  Related Information:
  
  SAP Notes: Check SAP Notes related to ESH and role management for any known issues or patches that might address this error.
  Documentation: Review the SAP documentation for Enterprise Search and role management to ensure that you are following best practices.
  Support: If the issue persists, consider reaching out to SAP support for further assistance, providing them with the error message and any relevant details about your configuration.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.