CRM_ES - ES: Message Class for Enterprise Service
The following messages are stored in message class CRM_ES: ES: Message Class for Enterprise Service.
It is part of development package CRM_ES_MGR in software component CA-WUI-ES. This development package consists of objects that can be grouped under "Enterprise Search Manager CRM".
It is part of development package CRM_ES_MGR in software component CA-WUI-ES. This development package consists of objects that can be grouped under "Enterprise Search Manager CRM".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | BOL objects for template type &1 are not supported; entry &2 is discarded |
002 | You can maintain only one key attribute |
003 | Select a template set before you create a template |
004 | Enter the parent/source key before you specify the target |
005 | Field &1 is not defined as a key field in template &2 |
006 | Table &1 is not a text table; it is not related to any text table |
007 | Domain &1 has neither fixed values, nor a value table |
008 | Domain &1 for the attribute &2 has a value table defined |
009 | Technical template found for domain &1 associated to the attribute &2 |
010 | Domain &1 for the attribute &2 has fixed values defined |
011 | Technical template already exists with key &1, description '&2' |
012 | Correct key mapping entry for &1 |
013 | Implicit keys are not possible when explicit keys are already defined |
014 | Template &1 successfully saved |
015 | Enter a BOL object before you create a business template |
016 | SAP templates may not be transferred in customer system |
025 | You cannot copy and rename complete template sets at the moment |
026 | Template described '&2' (ID '&1') already exists in template set '&3' |
027 | BOL type mismatch; BOL type of relation is &1 and foreign template is &2 |
028 | Template with ID '&1' already exists in template set '&2' |
029 | '&1' was already entered as target template ID and must not be used again |
100 | &1 |
101 | Select template type from the dropdown list box |
102 | Template set '&1' does not exist |
103 | First select a template by double-clicking and editing it |
104 | Save your template set before you proceed |
105 | Error '&1' occurred while trying to delete &2 |
106 | Error occurred while saving &1 |
107 | Template set successfully saved |
108 | Error occurred while trying to add a node to the tree: &1 |
109 | Select a node by double-clicking it in the tree |
110 | Model transfer started for template with ID &1 |
111 | Error occurred while copying &1 |
112 | Error during the transfer of model &1 |
113 | Specify the template ID before you delete this element |
114 | &1 has not been deleted |
115 | A template with ID '&1' already exists; enter another ID |
116 | Error occurred in the tree: &1 |
117 | Select a template to perform the check |
118 | Tree is consistent; no errors occurred |
119 | Save your changes before copying |
120 | Element '&1' successfully copied to '&2' |
121 | Lock granted for template '&1' and user &2 |
122 | Target model is not compatible; copy not completed |
124 | Toggle edit mode for previous template &1 before you continue |
125 | You need to save and leave change mode before you continue |
126 | First select a template set by loading it to the tree |
127 | Transport triggered; see application log for details |
128 | No template set was created |
129 | Copying a technical template is not supported |
130 | Component set '&1' does not exist; choose an existing component set |
131 | This template is currently locked by another user |
132 | Template set '&1' was successfully deleted |
133 | Template set '&1' could not be deleted since it contains templates |
134 | If you select a relation name, make sure to also enter a relation ID |
135 | You have to leave edit mode before refreshing the tree |
136 | &1 errors occurred while trying to transfer TOs; see log file |
137 | &1 TOs successfully transferred |
138 | Error occurred while trying to transfer TOs; see log file |
139 | Search for template set did not yield a result |
140 | Element successfully deleted |
141 | Element was not created |
142 | Table '&1' already used as &2, described '&3', and must not be used again |
143 | Load a template set before you continue |
144 | Inconsistencies exist; check entries |
145 | Copying not allowed in change mode |
146 | Switch does not have a correct reaction or vice versa; press cancel |
147 | '&1' is not a valid switch; use F4 to find one or press cancel |
148 | '&1' is not a valid reaction; choose 'Hide' or 'Display' or press cancel |
149 | No permission to copy template '&1' to template set '&2' |
150 | Template set |
151 | Template ID |
152 | Template set '&1' already exists and therefore cannot be used |
153 | Dirty state; initialize the tree again |
154 | Search for template did not yield a result |
155 | Template set must be in edit mode to delete it |
156 | Template ID is empty; specify source template for copy process |
157 | Template &1 does not exist |
200 | Enter the template ID |
201 | Enter the relation ID for template &1 and relation &2 |
202 | Enter field IDs for template &1 and object ID &2 |
203 | Enter object ID for template &1, relation &2, and BOL object &3 |
204 | Template with ID &1 already exists; enter a unique template ID |
205 | Relation ID is not unique for template &1 and relation &2 |
206 | Field IDs are not unique for template &1 and object ID &2 |
207 | Object ID is not unique for template &1, relation &2, and BOL obj. &3 |
208 | Mark &1 as selected; children are marked as selected |
209 | Enter template ID and template set ID |
210 | Input data is not consistent for copying template |
211 | Enter template set and component set |
212 | Deletion of &1 failed |
213 | Enter template set |
214 | Save failed for &1 |
215 | Template set data is inconsistent |
216 | Conversion of XML data failed |
217 | New template ID is already in use |
218 | Nodes for template data are not maintained |
219 | Could not load template set (target) |
220 | Select child of &1 or deselect &1 |
221 | Model relation keys for &1 |
222 | Maintain key fields for &1; key fields have to be marked as selected |
223 | Details for technical object &1 are not specified |
224 | Key fields are not specified for TO &1 |
225 | No language field is specified for TO &1 |
226 | Field &2 does not exist for TO &1 |
227 | Maintain key mapping for TO &1 of node &2 |
228 | Maintain source/target key for key mapping for TO &1 of node &2 |
229 | Enter template ID to get backward relations |
230 | Enter template ID to get forward relations |
231 | Mark field &3 of node &2 as selected for TO mapping of &1 |
232 | Due to references, template &1 cannot be deleted |
233 | Following templates reference template &1: |
240 | Saving of foreign attributes failed for template &1 |
241 | Deletion of foreign attributes failed for template &1 |
242 | Saving of relation paths failed for template &1 |
243 | Deletion of relation path failed for template &1 |
250 | &1 is already in use (&2) |
251 | Select &1 or deselect &2 |
252 | Mark &1 in attributes of source BO for &2 as key and as selected |
253 | Mark &1 in attributes of target BO for &2 as key and as selected |
254 | Keys for root are not specified for template &1 |
255 | Save failed; no template ID provided |
256 | Save failed for &1; data is inconsistent |
257 | Field table is empty for &1 |
258 | Empty data for template &1 |
259 | Template &1 not found |
260 | Technical object for BOL object &1, field &2, has a different data type |
261 | Saving of relations failed for template &1 |
262 | Deletion of relations failed for template &1 |
263 | Saving of relations failed for template &1 relation &2 |
264 | Deletion of relations failed for template &1 relation &2 |
265 | Mark &1 in attributes of source BO for &2 as selected |
266 | Key field &1 of TO &2 is not marked as requested or language or response |
267 | No request field is specified for TO &1 |
268 | No response field is specified for TO &1 |
269 | Related TO &1 of attribute &3 of object &2 does not exist |
270 | Check related template &1 of relation &2 |
271 | Deletion of &1 failed; there are templates related to the template set |
272 | Determined relation of template &1 is not correct |
273 | Currency-reference table for structure &1 has to be checked |
274 | Check response fields; field CURRENCY is missing for reference &1 of &2 |
275 | Check request fields;field for CURRENCY is missing for reference &1 of &2 |
276 | Saving of extractor data failed |
277 | Node &1, field &2: Field linked to TO cannot be text-search-relevant |
278 | Key field &1 of TO &2 cannot be relevant for the text search |
279 | Object &1 of template &2 should have more fields marked as key fields |
280 | Only one field of node &1 should be marked to contain language code |
281 | Field &1 of node &2 should not be marked as language code and text |
282 | One field of node &1 should be marked to contain text |
283 | Field &1 of node &2 is not allowed to contain language code |
284 | If language code field is defined, at least one text field must be set |
285 | Field &1 of node &2 which contains language code should be marked as key |
286 | Foreign template &1 of relation &2 is not unique |
287 | Only one target key of relation &1 can be empty |
288 | Target key of relation &1 has to be specified for foreign relation model |
289 | Node name &1 has to be in upper case |
290 | A refresh is needed to reflect foreign key template changes in the tree |
291 | Default Switch ID from BOL is empty |
292 | Default Reaction switch from BOL is empty |
293 | This operation is not allowed for selected template &1 |
294 | Both, default Switch ID from BOL and its Reaction are empty |
295 | Field &1 of node &2 is marked as key; key fields should not be renamed |
296 | Fields linked to technical objects should not be renamed; field &1 of &2 |
297 | Template &1 is only editable in NW ES Modeler. Save canceled! |
300 | *** 300-399 messages reserved for the ES Manager *** |
301 | Start model transfer of template: &1 (ID: &2, template set: &3) |
302 | End model transfer of template: &1 (ID: &2, template set: &3) |
303 | Error occurred during transfer of template &1 to Enterprise Search |
304 | Model transfer to Enterprise Search successful |
305 | Model transfer to Enterprise Search failed; see appl. log for details |
306 | No installed components found |
307 | Check for failed Customizing entries |
308 | No template has been configured for model transfer (table CRMD_ES_COMP) |
309 | Failed to add ES customizing into transport request for component &1 |
310 | ES Customizing was successfully added to transport request |
311 | No template found for BOR object type &1 |
312 | Model transfer of template &1 successful |
313 | Model transfer to Enterprise Search failed |
314 | Invalid change pointer operation &1 |
315 | Exception &1 was raised |
316 | Template with ID &1 will be attached to component &2 |
317 | Modeling client has not been configured yet (table CRMD_ES_CLIENT) |
318 | Only one modeling client is allowed (table CRMD_ES_CLIENT) |
319 | Failed to set administration data to database |
320 | Internal error in Enterprise Search invocation |
322 | Start client copy of ES model |
323 | End client copy of ES model |
324 | Source client &1, target client &2 |
325 | Selection option: simulation '&1' |
326 | Template id &1 (template set: &2) selected |
327 | Templ. id &1 (templ. set: &2) not transferred to ES, therefore ignored |
328 | Number of templates copied: &1 |
329 | Selection option: clean up target client '&1' |
330 | Start appending ES customizing into transport request |
331 | End appending of ES customizing |
332 | Customizing request: &1 |
333 | Operation was successful |
334 | Operation failed |
335 | Selection option: all templates |
336 | Selection option: template &1 |
337 | Selection option: template set &1 |
338 | Selection option: only transferred templates '&1' |
339 | Adding template &1 to transport request |
340 | Operation failed; see application log for details |
341 | Operation succeeded; see application log for details |
342 | Template &1 omitted as it has not been transferred to ES |
343 | No action performed; see application log for details |
344 | All templates omitted as they have not been transferred to ES |
345 | Template &1 selected |
346 | &1 template sets selected |
347 | Adding deletion of template &1 to transport request |
348 | No action performed |
350 | Activation of structure &1 failed |
351 | TADIR entry for &1 could not be written |
352 | Deletion of structure &1 failed |
353 | Creation of structure &1 failed |
354 | Start generating structures and appending them into transport request |
355 | Stop generating structures and appending them into transport request |
356 | Adding generated stuctures of template &1 to transport request |
357 | Generated stuctures were successfully added to transport request |
358 | Check for addition of generated structures to transport request failed |
359 | According to selection options, no structures are generated/transported |
360 | Check design layer and config. of the views using the generated structure |
361 | Structure generation for template &1 aborted by user |
362 | Start initial extraction of template &1 |
363 | End initial extraction of template &1 |
364 | Error occurred during extraction of template &1 to Enterprise Search |
365 | Start delta extraction of template &1 |
366 | End delta extraction of template &1 |
367 | Extraction to Enterprise Search successful |
368 | Check reference fields and tables for structure &2 of template &1 |
370 | Following change pointers were selected: |
371 | No template found for BOL root name &1 |
372 | No template found for BOR object type &1 |
373 | Change pointer &1 (template ID: &2) passed to ES |
374 | Failed to pass change pointer &1 (template ID: &2) to ES |
376 | Transfer of template requests to Enterprise Search successful |
377 | Transfer of template response to Enterprise Search successful |
378 | Transfer of template requests to Enterprise Search failed |
379 | Transfer of template response to Enterprise Search failed |
380 | Client copy failed; target client may not be the modeling client |
381 | Current version of template &1 has not been transferred to ES |
383 | Start request transfer of template: &1 (ID: &2, template set: &3) |
384 | End request transfer of template: &1 (ID: &2, template set: &3) |
385 | Start response transfer of template: &1 (ID: &2, template set: &3) |
386 | End response transfer of template: &1 (ID: &2, template set: &3) |
387 | Request of template with ID &1 will be attached to component &2 |
388 | Response of template with ID &1 will be attached to component &2 |
390 | &1 |
391 | No authorization for Enterprise Search Modeling UI |
392 | No authorization for creating customizing transports |
393 | No authorization for transferring templates to Enterprise Search |
394 | No authorization for client copy of ES customizing |
395 | Transfer to Enterprise Search failed; see application log for details |
397 | DB table &1 not supported |
398 | Unable to read fields of table &1 |
399 | Template may not be transferred. Maintain it in Enterpise Search Modeler. |
400 | BOL root entity key is empty in request structure of query &1 |
401 | No connectors for Enterprise Search exist in the system |
402 | Connector &1 for Enterprise Search does not exist in the system |
403 | Connector &1 for Enterprise Search is not searchable |
410 | Structure &1 for template &2 does not exist or is inactive |
411 | Field &1 is missing in structure &2 for template &3 |
412 | Field &1 no longer exists in template &3 in the model for &2 |
413 | Error when retrieving structure information for &1 of template &2 |
430 | Select BOL object node &1 or deselect attribute &2 |
431 | Select BOL object node &1 or deselect relation &2 |
432 | Select relation &1 or deselect BOL object node &2 |
480 | Field &2 of object &3 does not exist in BOL/Genil, but in template &1 |
481 | Saving of activation data for foreign attributes functionality failed |
482 | Error while copying to template &1 (at step &2) |
483 | Switch for template header &1 is not ok; check Switch_ID and reaction |
484 | Switch for node &1 field &2 is not ok; check Switch_ID and reaction |
485 | Switch for foreign template &1 node &2 field &3 is not ok |
486 | Foreign template is not maintained for relation &1 |
487 | Switch ID &1 does not exist |
488 | Switch ID &1 is not active |
489 | Switch reaction &1 is not valid |
490 | Switch ID &1 is not valid; check assignment to business function |
491 | Switch for node &1 is not ok; check Switch_ID and reaction |
492 | Switches on root nodes are not allowed; use switch on template level |
500 | Maintain a component set |
501 | Error occurred when loading the model for component set &1 |
600 | Cannot retrieve model data from remote system |
601 | Specify RFC destination |
602 | Check OK; no critical changes in models have been detected |
700 | *** 700-799 messages also reserved for the ES Manager *** |
701 | Cannot increase modeling level, due to missing authorization |
702 | Modeling level decreased; you must save model of template &3 again |
703 | No authorization for application customizing maintenance |
704 | Functionality deactivated; you must save model of template &1 again |
705 | Entry deleted; you must save model of template &1 again |
706 | No authorization for technical customizing maintenance |
707 | Failed to insert into table &1 |
708 | Connector for template &1 still exists in ES; delete it |
709 | Template &1 still exists in ES; delete it |
710 | Changing data provider type for template &1 with GUID &2 |
711 | Changing root node for &1 node &2 |
712 | Changing relation for relation_id &1 to backend_name_l &2 |
713 | Start changing provider type of template &1 |
714 | End changing provider type of template &1 |
730 | Start: Processing changed connectors |
731 | End: Processing changed connectors |
732 | Connectors passed through: &1 &2 &3 &4 |
733 | Relevant connectors: &1 &2 &3 &4 |
734 | Request/response structures generated for connector &1 |
735 | Request/response structures deleted for connector &1 |
740 | Business Object Layer: Enterprise Search via template &1 not supported. |
800 | Empty custom filter is not possible for &1; reset the filter |
830 | Software Component is missing for template &1 for structure generation |
850 | Cannot load template data for &1 from SAP NetWeaver database |
851 | Node &1 cannot be determined; use input help |