How To Fix ESH_ADM_MSG300 - There is no periodic indexing scheduled

SAP Error Message - Details

• Message type: E = Error

• Message class: ESH_ADM_MSG - ESH Administration and Monitoring Tool

• Message number: 300

• Message text: There is no periodic indexing scheduled

What causes this issue?

The system is configured as a cloud system. It is not possible to
schedule extraction/indexing of objects periodically with this task
list.

System Response

The extraction and indexing was done once. There is no further periodic
schedule.

How to fix this error?

In cloud systems the job schedules were done in the technical job
repository.
Another alternative is to define an extraction user with the report
ESH_EX_SET_EXTRACTION_USER. Then this task list schedules
extraction/indexing of objects periodically if it is requested by the
model.

Procedure for System Administrators

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ESH_ADM_MSG300 - There is no periodic indexing scheduled ?

  The SAP error message ESH_ADM_MSG300 indicates that there is no periodic indexing scheduled for the Enterprise Search (ES) in your SAP system. This can lead to issues where the search functionality does not return the most up-to-date results, as the index is not being refreshed regularly.
  
  Cause:
  The primary cause of this error is that the periodic indexing job, which is responsible for updating the search index with the latest data, has not been scheduled or has been disabled. This can happen due to various reasons, such as:
  
  Initial Setup: The periodic indexing job was never set up during the initial configuration of the Enterprise Search.
  Job Deletion: The job may have been deleted or failed to run due to system issues.
  Configuration Changes: Changes in the system configuration or updates may have affected the scheduling of the indexing job.
  
  
  Solution:
  To resolve this issue, you need to schedule a periodic indexing job. Here are the steps