ESH_TASK_MANAGER_MSG - ESH Task Manager

The following messages are stored in message class ESH_TASK_MANAGER_MSG: ESH Task Manager.
 It is part of development package S_ESH_ENG_TASK_MANAGER in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Technical conifgurations(tasks) for Task Manager".
Message Nr ▲
Message Text
001Save a variant for this step
002Summary
003Task list is not supported for ABAP Cloud Platform
004Task list '&1' is not supported in S/4HANA cloud environment
020Software component '&1' is selected
021All models of software component '&1' are selected
022Model '&1' is going to be created and indexed
023Table/view ESH_CU_OM_TO_SC contains no model to create a connector
024Table/view ESH_CU_OM_TO_SC is used to create connectors
025Model '&1' for connector '&2' is not in table/view ESH_CU_OM_TO_SC
030'&1' has been activated
031Activation of '&1' unsuccessful
032Activation of '&1' unsuccessful: Node does not exist
033Activation of '&1' unsuccessful: Enqueue error
034Activation of '&1' unsuccessful: No authorization
050RFC destination or DB connection to SAP HANA was not set
051RFC destination or DB connection to SAP HANA is set: &1
052RFC destination or DB connection to SAP HANA was set: &1
053RFC destination or DB connection to SAP HANA does not exist
054File Loader needs a SAP HANA connection
055Create HTTP destination for File Loader
056HTTP destination for File Loader is not used
057The entries are NOT inserted in table '&1' client '&2'
058The entries are inserted from table '&1' in client '&2' successfully
059Technical error occurred
060HTTP destination was not set for File Loader
061HTTP destination '&1' was set for File Loader
062Action "set parameter for federated search" was NOT successfully executed
063Action "set parameter for federated search" was successfully executed
064Task executed in the correct client
065Task list must be executed in client '000'
066At least one client has to be selected
067Client is already configured for Enterprise Search
068Task was skipped due to an issue in the task '&1'
069Client can be configured for Enterprise Search
070Task was skipped due to settings in the task '&1'
071Task is mandatory due to settings in the task '&1'
072Task settings were taken back due to settings in the task '&1'
073Function not supported in S/4HANA cloud environment
074The update of the search connectors is not necessary
087Maximum wait time exceeded. Process connector '&1' manually in cockpit
088Interval &1 minutes, maximum wait time &2 hours, maximum loop &3 times
089No connector has the status prepared
090Connector '&1' has status prepared and is ready for further processing
091Connector '&1' has status preparing. Wait for it.
092No instance of class cl_esh_ief_framework is available
093Connector '&1' is going to be indexed
094No connector indexed
102User '&1' was unregistered as extraction user
103User '&1' is set as extraction user
104User '&1' is not set as extraction user
105User '&1' does exist
106User '&1' does not exist
108Log for Role assignment:
111No connector found
112Connector '&1' is searchable
113Connector '&1' can not be checked
114Connector '&1' is not searchable
115The local connector '&1', package '&2' is excluded from check
120Consistency check of connector '&1' step '&2' returns success
121Consistency check of connector '&1' step '&2' returns warning
122Consistency check of connector '&1' step '&2' returns error
123Consistency check of connector '&1' step '&2' returns undefined
124Connector &1 step &2 needs to run follow-up action to repair connector
140Connector status is consolidated
200Enter at least a client
201Client '&1' is the development client of SW Component '&2' (no imports)
Privacy Policy