How To Fix CM_SUB040 - Background program for Enterprise Search (&1) is not scheduled

CM_SUB040 - Overview

• Message type: E = Error

• Message class: CM_SUB - Substance (general)

• Message number: 040

• Message text: Background program for Enterprise Search (&1) is not scheduled

What causes this issue?

The report for Enterprise Search could not be started, because the job
is not scheduled.

System Response

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

How to fix this error?

Schedule the job for the report.

Procedure for System Administrators

Set up the job as follows:
INCLUDE EHS_SAF_27A_JOB_01 OBJECT DOKU ID TX
Choose <LS>Edit -> <LS>Start Date</> and choose the function <LS>After
Event</> in the following dialog box.
In the field <LS>Event</>, enter the key SAP_START_EHS_ES_BUS1077 and
set the indicator <LS>Execute Job Periodically</>.
INCLUDE EHS_SAF_27A_JOB_02 OBJECT DOKU ID TX
For the name of the ABAP program, enter RC1_ES_CPOINTER_EXTRACT.
INCLUDE EHS_SAF_27A_JOB_03 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_SUB040 - Background program for Enterprise Search (&1) is not scheduled ?

  The SAP error message CM_SUB040 indicates that the background program for Enterprise Search is not scheduled. This can occur in systems where Enterprise Search is implemented, and it typically means that the necessary background job to update or maintain the search index is not running.
  
  Cause:
  
  Background Job Not Scheduled: The most common cause is that the background job responsible for updating the Enterprise Search index has not been scheduled or has been deleted.
  Job Failure: The job may have been scheduled but failed to run due to various reasons such as system errors, resource issues, or configuration problems.
  
  Configuration Issues: There may be issues with the configuration of the Enterprise Search or the related components that prevent the job from being scheduled.
  Authorization Issues: The user may not have the necessary authorizations to schedule or execute the background job.
  
  
  Solution:
  
  
  Schedule the Background Job:
  
  Go to transaction SM36 (Define Background Job).
  Create a new job for the Enterprise