ESH_ADM_MSG - ESH Administration and Monitoring Tool
The following messages are stored in message class ESH_ADM_MSG: ESH Administration and Monitoring Tool.
It is part of development package S_ESH_ENG_MONITORING_ADMIN in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Monitoring and Admin Component".
It is part of development package S_ESH_ENG_MONITORING_ADMIN in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Monitoring and Admin Component".
Message Nr ▲ | Message Text |
---|---|
001 | RFC destination for TREX changed to &1 |
002 | Start scheduling of indexing |
003 | Cannot schedule search object connector &1 (&2) |
004 | Schedule search object connector &1 (&2) |
005 | Could not write an application log |
006 | Scheduling of indexes has been canceled |
007 | Search object connector &1 has been activated |
008 | Search object connector &1 has been deactivated |
009 | Specify a template type |
010 | Specify a search object connector ID |
011 | Search object connector &1 &2 exists |
012 | Specify a start date |
013 | User and/or domain were changed. Enter a password |
014 | No changes were made |
015 | Crawl settings for crawl &1 were changed successfully |
016 | Enter a path |
017 | Enter a user name |
018 | Enter a password |
019 | Enter a domain |
020 | Path &1 has been entered before |
021 | Enter a directory |
022 | Directory &1 has been entered before |
023 | You cannot delete this entry |
024 | You cannot change this entry |
025 | You cannot cancel crawl &1 |
026 | Crawl &1 has been deleted |
027 | Crawl &1 has been canceled |
028 | Crawl &1 has been restarted |
029 | You cannot suspend crawl &1 |
030 | Crawl &1 has been suspended |
031 | You cannot resume crawl &1 |
032 | Crawl &1 has been resumed |
033 | Update of crawl &1 has been started |
034 | Full update of crawl &1 has been started |
035 | Enter a seed URL |
036 | Crawl &1 has been created |
037 | Crawl &1 has been started |
038 | You cannot activate search object connector &1 with status &2 |
039 | &1&2&3&4 |
040 | Communication error while calling the Java Web service |
041 | Application error while calling the Java Web service |
042 | Start preparation of search object connectors |
043 | Prepare search object connector &1 (&2) |
044 | Search object connector &1: New status: &2 |
045 | No entry found for &1 &2 |
046 | You are not authorized to use the administration cockpit |
047 | Queue with index &1 has been flushed |
048 | You are not authorized to activate or deactivate search connectors |
049 | You are not authorized to prepare search connectors |
050 | You are not authorized to index search connectors |
051 | You are not authorized to reset search connectors |
052 | You cannot use BI user &1 |
053 | You are not authorized to create a user in back-end system &1 |
054 | You are not authorized to create search object connectors |
055 | You are not authorized to access RFC destination &1 |
056 | You are not authorized to create RFC destination &1 |
057 | Could not create RFC destination &1 |
058 | Error occurred while reading RFC destination &1 |
059 | RFC destination &1 created |
060 | Logical system received from back-end system: |
061 | You are not authorized to create crawls |
062 | You are not authorized to change crawls |
063 | You are not authorized to delete crawls |
064 | You are not authorized to cancel crawls |
065 | You are not authorized to update crawls |
066 | You are not authorized to start crawls |
067 | You are not authorized to suspend crawls |
068 | You are not authorized to resume crawls |
069 | DB Connection not set (SAP HANA or TREX) |
070 | You are not authorized to delete search object connectors |
071 | Specify schedule data for delta indexing |
072 | Search object connectors scheduled for indexing |
073 | Search object connector &1 will be reset to status prepared |
074 | Use &1 as system ID |
075 | Specify an application server |
076 | Specify a system number |
077 | Specify a system ID |
078 | Specify a client |
079 | Could not delete RFC destination &1 |
080 | You are not authorized to delete RFC destination &1 |
081 | Connection &1 does not exist |
082 | System &1, client &2: A connection already exists |
083 | MDM connection already exists |
084 | Specify a template ID |
085 | You are not authorized to flush queues |
086 | Starting migration of logical systems to connection GUIDs |
087 | You are not authorized to create search object connector templates |
088 | Specify a connection GUID |
089 | Template ID &1 &2 is not registered |
090 | Connection to &1 is locked by user &2 |
091 | No logical system found for connection GUID &1 |
092 | You are not authorized to update a search object connector from template |
093 | Search object connector &1 has been deleted |
094 | RFC destination &1 has been changed |
095 | You are not authorized to change RFC destination &1 |
096 | Could not change RFC destination &1 |
097 | You cannot deactivate search object connector &1 with status &2 |
098 | Specify schedule data for periodically indexing |
099 | Function: REGISTER_SEARCH_CONNECTORS |
100 | Search object connectors: |
101 | Template type: &1 |
102 | Search object connector ID: &1 |
103 | Connection GUID: &1 |
104 | Nodes: |
105 | Object type: &1 |
106 | Node name: &1 |
107 | Created: &1, changed: &2, deleted: &3 |
108 | Requests: |
109 | Request: &1 |
110 | Function: DELETE_SEARCH_CONNECTOR |
111 | Date is in the past |
112 | Time is in the past |
113 | You are not authorized to delete the indexing schedules |
114 | No object connectors were scheduled or rescheduled for indexing |
115 | No search object connector has been deleted |
116 | No schedule data were deleted |
117 | The system changed the status filter from '&1' to '&2' |
118 | Crawl &1 has not been canceled |
119 | Crawl &1 has not been suspended |
120 | Crawl &1 has not been resumed |
121 | You are not authorized to schedule crawls |
122 | No administration cockpit URL created |
123 | Search object connector &1 does not exist |
124 | You are not authorized to connect a back-end system |
125 | You are not authorized to continue indexing |
126 | No crawl has been deleted |
127 | Crawl &1 has not been deleted |
128 | Scheduling of crawls has been canceled |
129 | TREX version &1 is too old. Required version &2 or higher |
130 | You are not authorized to maintain UI technologies |
131 | You are not authorized to delete crawl schedules |
132 | BOS search connectors can only be created in client &1 |
133 | System is connected to &1 -> TREX destination has no effect |
134 | You are not authorized to administrate real-time indexing |
135 | Enter a software component |
136 | Background process for real-time indexing started |
137 | Background process for real-time indexing stopped |
138 | Background process for real-time indexing could not be started |
139 | Background process for real-time indexing could not be stopped |
140 | Process parameters for real-time indexing changed |
141 | Process parameters for real-time indexing could not be changed |
142 | Select an object type |
143 | No schedule start time for object type "&1" |
144 | Schedule start for object type "&1" is in the past |
145 | Schedule start for object type "&1" needs to be the same as "&2" |
146 | No schedule data have been changed |
147 | Set a recurrence period |
148 | Set a recurrence period for object type "&1" |
149 | No schedule start time for crawl "&1" |
150 | Schedule start for crawl "&1" is in the past |
151 | Lead selection cannot be deleted |
152 | System was copied -> execute program ESH_ADM_INDEX_ALL_SC (see long text) |
153 | System is connected to hub &1 -> Disconnect the system |
154 | Error while opening an RFC connection. Cannot connect to &1 &2 |
155 | Error with connection GUID &1 |
156 | Indexing schedule has been saved |
157 | Crawl schedule has been saved |
158 | Queue with index &1 has not been flushed |
159 | Search connectors exist -> TREX dest / HANA connection cannot be changed |
160 | Index does not contain authorization data |
161 | Index contains authorization data |
162 | Set system change option /BIC/ to modifiable (transaction SE03) |
163 | You are not authorized to maintain categories |
164 | Category "&1" does not exist |
165 | Category "&1" exists |
166 | No crawl was scheduled |
167 | You are not authorized to edit connector names |
168 | Descriptions of connector "&1" are locked by user &2 |
169 | Category assignments of connector "&1" are locked by user &2 |
170 | Connectors cannot be enhanced during update processes |
171 | Exception occurred while trying to set a lock |
172 | You are not authorized to delete a back-end system |
173 | You are not authorized to display performance measurement data |
174 | User &1 has no auth. for authorization obj. &2 in system &3 client &4 |
175 | You are not authorized to process the consistency check |
176 | Do a proper configuration for the TREX server with destination &1 |
177 | No connection of type SAP BO Legacy Search can be created in this system |
178 | RFC destination &1 deleted |
179 | No connection of type SAP BO Search can be created in this system |
180 | Invalid URL: &1 |
181 | Hub test: The replay mode is active |
182 | Cannot connect to destination &1. Reason: |
183 | Language &1 is not installed in system &2 |
184 | Last selection cannot be deleted |
185 | You are not authorized to maintain the system usage |
186 | Indexing of application data was successful |
187 | Indexing of application data was unsuccessful |
188 | Indexing of authorization data was successful |
189 | Indexing of authorization data was unsuccessful |
190 | There might be a problem in the BAdI framework -> see SAP Note 1521903 |
191 | Destination NO TREX is only allowed for Enterprise Search |
192 | Enter a search term |
193 | Search term is not valid |
194 | Search term not found |
195 | Search function is disabled (system is running on SAP HANA) |
196 | The length of the TREX RFC destination must not exceed 27 |
197 | DB connection for HANA changed to &1 |
198 | Virtual models cannot be indexed |
199 | Connector &1 does not exist |
200 | The model authorization check is not active |
201 | Connection for search object connector &1 could not be determined |
202 | Connection for model &1 could not be determined |
203 | No instance of the object model was created |
204 | Search object connector based on model '&1' must be created first |
205 | Model '&1' does not belong to software component '&2' |
206 | There is no application or virtual model to create a search connector |
207 | There is no application or virtual model scheduled for indexing |
208 | Enter a database connection |
209 | System is a central instance |
210 | There is no search object connector |
211 | Enter a TREX destination |
212 | The old and new system ID '&1' as well as the client '&2' are identical |
213 | Enter a model name |
214 | Program 'Adjust after system copy' must be executed in client '000' |
215 | No Enterprise Search connection is maintained |
216 | Specify the HTTP destination data to SAP HANA |
217 | You are not authorized to update authorization data |
218 | Update of authorization data has been started |
219 | The length of the DB connection name must not exceed 28 |
220 | File Loader monitor URL could not be created for connector &1 |
221 | There is no database table in the buffer for the restore |
222 | Database table &1 was restored |
223 | Database table &1 was not restored |
224 | There are no search object connectors for update |
225 | Old and new system ID '&1' are identical in client '&2' |
226 | This is not a client copy because the system IDs are different |
227 | Search object connector is already available for model '&1' |
228 | Search object connectors are older than this adjustment feature |
229 | It is not allowed to create a search object connector for model '&1' |
230 | Software component '&1' does not exist |
231 | Tables for restore deleted |
232 | Search is continued from the top of the table |
233 | There are no more search results |
234 | Database table &1 is empty |
235 | No schedule data for object type &1 |
236 | There is no system that can be used as source system |
237 | Enter a source system ID |
238 | Cockpit and modeler are only active in client '&1' |
239 | The following parameters were used: |
240 | Restore database from INDX |
241 | Delete tables for restore |
242 | Database connection name: &1 |
243 | Source system ID: &1 |
244 | Adjust only this client after client copy |
245 | Adjust all clients after system copy |
246 | Testrun: No database or index update |
247 | Database and index update |
248 | This function is only availabe for systems on SAP HANA |
249 | Error in DB operation (&1) |
250 | Error accessing model data (&1) |
251 | Local connection missing |
252 | Model '&1' is not an application model or virtual model |
253 | File Loader administration URL could not be created for connector &1 |
254 | No error is occurred |
255 | There are &1 search object connectors in client &2 |
256 | HTTP destination &1 to SAP HANA (host:&2, port:&3) |
257 | There might be issues with Enhancement Spot BADI_ESH_IF_OBJECT_DATA |
258 | Search object connectors were deleted |
259 | Current client is a copy of another client |
260 | Current system is a copy of another system |
261 | Model USER_AUTHORITY is not used by a search object connector |
262 | Ranking factor assignments of connector "&1" are locked by user &2 |
263 | Common Runtime is not configured for Enterprise Search |
264 | You are not authorized to clean up this client |
265 | Check the DB connection &1 to SAP HANA |
266 | Enterprise Search was reset to initial state |
267 | An error occured while clean up this client |
268 | Confirm the reset of Enterprise Search into initial state |
269 | Enter a connector name |
270 | User &1 of database connection &2 has no privilege &3 |
271 | Search object connector '&1' has status '&2' |
272 | Password is removed |
273 | Original connector name '&1' was set |
274 | Original plural connector name '&1' was set |
275 | Enterprise Search specific data were not adjusted |
276 | Join index '&1' is missing in client '&2' |
277 | Program '&1' started |
278 | Execute program '&1' in client '&2' |
279 | There is no local search object connector |
280 | DB connection '&1' uses the schema '&2' |
281 | Schema '&1' in client '&2' is different from schema '&3' |
282 | Index user authority |
283 | Index search object connectors |
284 | The erroneous software component '&1' is used by a connector |
285 | The erroneous software component '&1' is not used by a connector |
286 | The erroneous software component '&1' is used in stack of '&2' |
287 | The erroneous software component '&1' is not used in stack of '&2' |
288 | The erroneous software component '&1' is used in table '&2' |
289 | The erroneous software component '&1' is not used in table '&2' |
290 | Check relevance of erroneous software components |
291 | An erroneous software component may be relevant for usage |
292 | Connection &1 points to Trex |
293 | Connection &1: Inconsistent configuration |
294 | The report ESH_ADM_INDEX_ALL_SC is obsolete |
295 | Last lead selection of connector table was set |
296 | Connector adjustment is not possible using a TREX destination (&1) |
297 | Search object connector '&1' will be updated with model '&2' |
298 | Indexing of '&1' is via connector '&2' |
299 | File Processor administration URL could not be created for connector &1 |
300 | There is no periodic indexing scheduled |
301 | Connectors are loading ... |
302 | BWA index '&1' in client '&2' cannot be adjusted |
303 | Local connection is already defined for system '&1' and client '&2' |
304 | HANA user for schema &1 does not have &2 privileges for view &3 in &4 |
305 | Client '&1' uses DB connection '&2' |
306 | Client '&1' cannot be adjusted |
307 | There is no client, which can be adjusted |
308 | Connector '&1' is used from connector '&2' |
309 | Client '&1' is processed |
310 | Client '&1' was adjusted |
311 | Source client: &1 |
312 | The execution of the URL according to the whitelist is not possible |
313 | Error building display |
314 | Entry has been addded |
315 | Select a line first |
316 | Entries have been deleted |
317 | Entry exists already |
318 | Parameter not defined as a constant |
319 | Select a single line |
320 | Connector was changed from '&1' to '&2' |
321 | Connector '&1' was deleted from ESH_ADM_SC_MAIN |
322 | Changes have been saved |
323 | Error reading data |
324 | Error writing data |
325 | Only assignments done on connector level can be deleted |
326 | Connector for model '&1' must not be created |
327 | No software component import was scheduled |
328 | Error during preparing model data |
329 | The following connectors are not in table 'ESH_CU_OM_TO_SC' |
330 | Adjustment of runtime buffer failed in client &1 |
331 | Runtime buffer re-filled with common runtime connectors in client &1 |
332 | Connector &2 missing in runtime buffer of client &1 |
333 | CDS-based ES connectors could not be activated |
334 | Runtime buffer could not to be updated |
335 | Task list '&1' is running |