How To Fix HRPAO_SEARCH060 - No entry in table ESH_CRT_SCHEDULE for system &1 and model &2

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAO_SEARCH - Messages for SEARCH within masterdata application

• Message number: 060

• Message text: No entry in table ESH_CRT_SCHEDULE for system &1 and model &2

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 HRPAO_SEARCH060 - No entry in table ESH_CRT_SCHEDULE for system &1 and model &2 ?

  The SAP error message HRPAO_SEARCH060 indicates that there is no entry in the table ESH_CRT_SCHEDULE for the specified system and model. This error typically occurs in the context of SAP's Enterprise Search or when dealing with the SAP HCM (Human Capital Management) module, particularly when trying to access or search for data that relies on a scheduled job or configuration that hasn't been set up correctly.
  Cause:
  
  
  Missing Configuration: The error usually arises when the necessary configuration for the search model or system is not present in the ESH_CRT_SCHEDULE table. This could be due to:
  
  The search model not being activated.
  The scheduled job for the search model not being created or executed.
  Incorrect system or model identifiers being used in the search.
  
  
  
  Data Synchronization Issues: If the data synchronization jobs have not run successfully, the entries may not be populated in the relevant tables.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access the data or the scheduled jobs.
  
  
  Solution:
  
  
  Check Configuration:
  
  Verify that the search model is correctly configured and activated in the system.
  Ensure that the relevant entries exist in the ESH_CRT_SCHEDULE table for the specified system and model. You can check this using transaction SE11 (Data Dictionary) or SE16 (Data Browser).
  
  
  
  Create or Schedule Jobs:
  
  If there are no entries, you may need to create a new scheduled job for the search model. This can typically be done through the transaction code EHS_SEARCH or similar, depending on your SAP version.
  Ensure that the job is scheduled to run at appropriate intervals to keep the data up to date.
  
  
  
  Run Data Synchronization:
  
  If applicable, run the data synchronization jobs manually to populate the necessary tables. This can often be done through transaction codes related to the specific search or data model.
  
  
  
  Check Authorizations:
  
  Ensure that the user has the necessary authorizations to access the search functionality and the underlying data.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to the specific version of your SAP system for any additional troubleshooting steps or known issues.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as SE11, SE16, EHS_SEARCH, and others that may be used for configuration and troubleshooting.
  SAP Notes: Check SAP Notes for any known issues or patches related to the error message. You can search for the error message or related keywords in the SAP Support Portal.
  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 cause of the error and implement a solution to resolve it.