ESH_OM_OBJ_MODEL_REP - Object Model Repository

The following messages are stored in message class ESH_OM_OBJ_MODEL_REP: Object Model Repository.
 It is part of development package S_ESH_ENG_OBJ_MOD_REP in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Model Repository".
Message Nr ▲
Message Text
001Entry &1 &2 not found in buffer
002Error while changing update flag from &1 to &2
003Incorrect update_flag &1 in &2
004Incorrect call of cl_esh_om_otyp -> save_data_gerneric_int
005Object type &1 already exists
006Object type &1 does not exist
007Could not create new ID from &1
008There must be exactly one root node
009Key of object type description is not fully specified
010Object factory called with incorrect mode
011Object factory called with incorrect area
012Object type is initial
013Data provider &1 does not exist
014Key of data provider filter &1/&2 is not fully specified
015Node name is initial
016Node &1: Node field is initial
017Key of node was not fully specified
018No relation specified
019Data provider &1, filter &2 does not exist
020Key of node description is not fully specified
021Node &1 already exists
022Node field &1 already exists
023Alias &1 of response field already exists
024Request &2 already exists
025Object type description in language &1 already exists
026Description in language &2 already exists
027Parameter missing: &1
028Object model could not be instantiated
029Incorrect parameter value: &1 &2
030Class &1: Incorrect call of SAVE_ALL_METHODS
031Collision in customer area (release &1, group &2)
032Data provider &1:
033Object type &1 has to start with &2 in customer systems
034&1 &2 &3 &4
035ABAP authorization object-based check &1 already exists
036Data provider &1, filter &2:
037Request &1/&2/&3 is already assigned as a related request
038Back-end navigation &1/&2 already exists
039Object type &1, node &2, back-end navigation &3/&4:
040Back-end navigation &1/&2/&3:
041Response field &1, target parameter &2: Field assignment already exists
042Node &1/&2 is already listed
043Relation &1 already listed
044Relation &1/&2 to &3/&4:
045Navigation path (type &1) &2:
046From node &1/&2 to &3/&4:
047Step &1 already exists
048Data type &1 already exists
049Data type &1:
050Field text in language &1 already exists
051Data provider &1 already exists
052Field &1 already exists
053Key of request field is not fully specified
054Filter &1 already exists
055Relation ID &1 does not exist
056Value definition &1/&2/&3 already exists
057Value "&1" contains spaces
058System with connection GUID &1 already exists
059Software component &1 already exists
060System group &1 already exists for software component &2
061Authorization object key &1 (ABAP auth. object &2 ) already exists
062Field &1 already exists in authorization object key &2 (auth. object &3)
063Description in language &1 already exists
064Field assignment already exists
065Authorization field &1, node field &2/&3/&4
066Description in language &2 already exists
067Description in language &2 already exists
068Description in language &2 already exists
069Authorization field &1, counter &2
070Entry already exists
071Control field &1/&2/&3 already exists
072Authorization action &1, counter &2 already exists
073Object type &1, node &2, field &3:
074Data type is initial
075Key of authorization check is not fully specified
076Data type &1 does not exist
077Text data type &1 does not exist
078Object type &1, node &2, response field &3:
079Key of response field is not fully specified
080Key of referenced node field is not fully specified
081Object type &1, node &2, node field &3 does not exist
082Relation &1 already exists
083Object type &1, node &2, request &3:
084Object type &1, node &2, request &3, field &4:
085Object type &1 is in customer namespace (&2)
086Key of node field is not fully specified
087Key of request is not fully specified
088Object type &1, node &2 does not exist
089Object type &1, node &2, request &3 does not exist
090Relation ID is initial
091Object type &1, node &2, authorization check &3:
092Node &1, authorization_check &2:
093Relation ID &1:
094Source node key is not fully specified
095Source node &1/&2 does not exist
096Target node &1/&2 does not exist
097Source node field is initial
098Source node field &1 does not exist
099Target node field is initial
100Target node field &1 does not exist
101Key of related request &1/&2/&3 is not fully specified
102Related request &1/&2/&3 does not exist
103Object type &1, node &2:
104Object type &1, node &2, related request: object type &3, request &4
105Object type &1:
106Object type &1, node &2, request &3:
107Alias &1 of request field already exists
108Object type &1, node &2, auth. check &3:
109Field &4 of rel. request &1/&2/&3 already assigned
110Field assignment already exists
111Authorization object key &1 (ABAP auth. object &2):
112Authorization object-based authorization check &1:
113Related request does not exist
114Key of related request is not fully specified
115Rel. requests for object type &1, node &2:
116Related request field &1/&2/&3/&4 does not exist
117Key of related request field &1/&2/&3/&4 is not fully specified
118Key of node field &1/&2/&3 is not fully specified
119Nodes of request &1/&2/&3:
120Key of node is not fully specified
121Key of request is not fully specified
122Request does not exist
123Requests of request &1/&2/&3:
124Back-end navigation for object type &1, node &2:
125Node does not exist
126Object type &1, node &2, UI type &3, target navigation &4:
127Key of back-end navigation is not fully specified
128Key of request description is not fully specified
129Key of authorization check description is not fully specified
130Authorization check does not exist
131Key of back-end navigation description is not fully specified
132Back-end navigation does not exist
133Navigation path &1:
134Start node key is not fully specified
135Start node &1/&2 does not exist
136End node key is not fully specified
137End node &1/&2 does not exist
138Navigation path &1, step &2:
139Key of navigation path step is not fully specified
140Navigation path &1 does not exist
141From-node key is not fully specified
142From-node &1/&2 does not exist
143To-node key is not fully specified
144To-node &1/&2 does not exist
145Field ass. of object type &1, node &2, UI type &3, operation &4:
146Response field &1 does not exist
147Response field is initial
148Data provider is initial
149Key of data provider description is not fully specified
150Data provider &1, language &2:
151Object type &1, language &2:
152Object type &1, node &2, language &3:
153Object type &1, node &2, request &3, language &4:
154Object type &1, node &2, authorization check &3, language &4:
155Data provider &1, field &2:
156Key of data provider field is not fully specified
157Key of data provider filter is not fully specified
158Data provider &1, filter &2, language &3:
159Key of data provider filter description is not fully specified
160Definition of data provider &1, fitler &2:
161Key of target data provider &1, field &2 is not fully specified
162Target data provider &1, field &2 does not exist
163Key of reference data provider &1, field &2 is not fully specified
164Reference data provider &1, field &2 does not exist
165Data type &1, language &2:
166Key of data type description is not fully specified
167Data type field text &1, language &2:
168Key of data type field text is not fully specified
169Connection GUID is initial
170System ID &1:
171Software component is initial
172Software component &1 does not exist
173System group &1 does not exist
174Key of system group is not fully specified
175System group &1 of software component &2 does not exist
176Connection GUID &1, language &2:
177Key of system description is not fully specified
178System with connection GUID &1 does not exist
179Software component &1, language &2:
180Key of software component description is not fully specified
181Product &1, system group &2:
182Product &1, system group &2, language &3:
183Key of system group description is not fully specified
184Authorization object is initial
185Authorization object &1:
186Authorization object key &1, language &2:
187Key of authorization object description is not fully specified
188Authorization object &1 key does not exist
189Authorization object key &1, field &2:
190Key of authorization object field is not fully specified
191Object type &1, node &2, auth.check &3, assigning authorization objects:
192Could not generate request ID for subquery navigation
193Node name &1 contains forbidden characters
194Object type &1 contains forbidden characters
195Request &1 contains forbidden characters
196System group &1 is reserved for SAP
197System group &1 contains forbidden characters
198Software component must start with &1, &2 or &3 in customer systems
199Software component &1 contains forbidden chararcters
200Generating related request for object type &1, node &2:
201Could not determine navigation path
202Request &1 is reserved
203Authorization check &1, auth. obj. field assignments:
204Authorization object key &1, field &2 does not exist
205Authorization object field is initial
206Key of object type &1, node &2, field &3 is not fully specified
207Auth. check &1, auth. obj. field values:
208Authorization check &1, control field assignments:
209Authorization check &1, control field values:
210No authorization object assignment to authorization check exists
211Object type &1, node &2, field &3 not defined as a control field
212Key for assignment of object type &1, node &2, field &3 is incorrect
213Node is referenced as physical node in object type &1, node &2
214Cannot delete node
215Node is referenced in NQF navigation path &1
216Node is referenced in NQF navigation path &1, step &2
217Node is referenced in NRF navigation path &1
218Node is referenced in NRF navigation path &1, step &2
219Node has child node &1
220Cannot delete node field
221Field is referenced in object type &1, node &2, resp. field &3
222Field is referenced in object type &1, node &2, request &3, field &4
223Field is referenced in authorization check &1
224Field is referenced in authorization check &1 control field
225Field is referenced authorizaiton check &1 control cond.
226Cannot delete request &1
227Request is related to object type &1, node &2
228Field is referenced in relation ID &1
229Field is referenced in composition &1/&2 to &3/&4
230Cannot delete relation
231Composition &1/&2 to &3/&4
232Relation is used in NQF navigation path &1, step &2
233Relation is used in NRF navigation path &1, step &2
234Cannot delete request field
235Field is referenced in object type &1, node &2, rel. request &3
236Cannot delete data provider
237Data provider is referenced in object type &1, node &2
238Cannot delete data provider filter
239Filer is referenced in object type &1, node &2
240Cannot delete data provider field
241Field is referenced in filter condition data prov. &1, filter &2
242Cannot delete authorization object
243Object is referenced by authorization check &1
244Cannot delete authorization object field
245Field is referenced in authorization check &1
246Cannot delete data type
247Data type is referenced in object type &1, node &2, node field &3
248Data type is text data type in object type &1, node &2, node field &3
249Data type is text data type in object type &1, node &2, resp. field &3
250Data type is used in object type &1, node &2, request &3, field &4
251Data type is referenced in data provider &1, field &2
252Software component &1 is assigned to system &2 with connectors
253Software component &1:
254Cannot delete software component
255There are system groups for the product
256The software component is assigned to system ID &1
257More than one key field is flagged as a language field
258Node is referenced in NFNW navigation path &1
259Node is referenced in NFNW navigation path &1, step &2
260Node is referenced in NSNW navigation path &1
261Node is referenced in NSNW navigation path &1, step &2
262One node must be flagged as the root node
263There must be exactly one default request
264One request must be flagged as the default request
265There must be at least one key field in node &1
266Category &1 is already assigned
267Key field &1 for data provider &2 does not occur in the node
268Node &1 has no parent node
269Node has more than one parent node
270Composition of different business objects
271You cannot delete the default request if there are other requests
272You cannot delete the root node if there are other nodes
273System ID &1 is assigned to product &2, system group &3
274Cannot reassign system ID &1 because it contains content
275First remove the old assignment
276Cannot remove assignment because the system contains content
277Product &1, system group &2 is locked by user &3
278Product &1, system group &2: System failure during lock
279Incorrect call of method &1
280System ID &1 has been locked by user &2
281System ID &1: System failure during lock
282Software component &1 has been locked by user &2
283Software component &1: System failure during lock
284Types of field &1 and &2 are incompatible
285Value is incompatible with type of data provider &1, field &2
286Response field &1 contains forbidden characters
287Relation ID &1 contains characters that are not allowed
288Key of control field is not fully specified
289No authorization for action &1 on object &2
290There is a field with the same name as the alias &1
291There is an alias with the same name as field &1
292User &1 has no authorization to change object types
293User &1 has no authorization to create object types
294User &1 has no authorization to delete object types
295User &1 has no authorization to display object types
296User &1 has no authorization to change system groups
297User &1 has no authorization to create system groups
298User &1 has no authorization to delete system groups
299User &1 has no authorization to display system groups
300User &1 has no authorization to transport system groups
301User &1 has no authorization to change software components
302User &1 has no authorization to create software components
303User &1 has no authorization to delete software components
304User &1 has no authorization to display software components
305User &1 has no authorization to transport software components
306User &1 has no authorization to assign systems to system group
307Node fields &1 and &2 have the same description in language &3
308Nodes &1 and &2 have the same description in language &3
309Object types &1 and &2 have the same description in language &3
310Requests &1 and &2 have the same description in language &3
311Response fields &1 and &2 have the same description in language &3
312System ID &1, client &2 has been locked by user &3
313System ID &1, client &2: System failure during lock
314A value has already been specified for authorization field &1
315A node has already been assigned for authorization field &1
316Foreign key assignment with field &1 or &2 already exists
317Relation ID &1 must not be a GUID
318Association ID &1:
319Description already exists in language &2
320Description already exists in language &3
321Description already exists in language &3
322Description already exists in language &4
323Description already exists in language &4
324Description already exists in language &1
325Data provider &1 is already used in object type &2, node &3
326Enter object type name
327Field is used in data provider &1, filter &2
328Data provider &1, field &2 is not flagged for selection
329Response fields &1 and &2 refer to the same node field
330System ID &1 (assigned to product &2, system group &3):
331Choose a transport request to save changes
332UI area is initial
333UI area &1:
334SAP Content: Software component &1
335Modified Content: Product &1, system group &2
336UI area is referenced in object type &1, node &2, resp. field &3
337Key of UI area description is not fully specified
338There is no UI area &1
339UI area &1 has to start with &2 in customer systems
340UI area is in customer &1 namespace (&2)
341UI areas are locked by user &1
342UI areas: System failure during lock
343Description in language &2 already exists
344UI area &1 already exists
345Object type &1, language &2, keyword &3:
346Key of keyword assignment is not fully specified
347Assignment to UI area &1 already exists
348Object type &1, node &2, response field &3, ui area &4:
349Object type &1, node &2, response field &3 does not exist
350Keyword &1 for language &2 is already assigned
351Model type &1 does not exist
352Object type &1, node &2, role type &3, role &4:
353Key of role assignment is not fully specified
354Role type &1, role &1 is already assigned to the node
355Role type &1, role &2 does not exist
356Icon &1 does not exist
357Category is initial
358Key of category description is not fully specified
359Category &1 does not exist
360Category &1:
361Cannot delete category
362Object type &1 in software component &2 is assigned to the category
363Category &1 already exists
364Description already exists in language &1
365Parent category &1 does not exist
366Category is in customer &1 namespace (&2)
367Category &1 has to start with &2 in customer systems
368Category &1 contains forbidden chararcters
369Type &1 does not exist
370Type of object type is initial
371Object type &1, category &2:
372Key of category assignment is not fully specified
373Category is parent of category &1
374Category cannot be its' own parent
375There is no modification status &1
376Categories and common attributes have been locked by user &2
377Categories and common attributes: System failure during lock
378Area &1:
379End node of navigation path differs from to-node of previous step
380Request fields &1 and &2 refer to the same node field
381Text-search-relevant fields cannot be used in relations
382The field is text-search-relevant and used in the following relations:
383Request has been activated
384Request has been deactivated
385You cannot delete the node field
386You cannot delete the request
387There is no modification status &1
388Target UI type &1 is not valid
389Relation does not fit to from-node and to-node of navigation path step
390Start-node of navigation path differs from from-node of first step
391Response field &1 of URL in target operation does not exist
392URL contains no reference to a response field
393Cardinality &1 of source node is not valid
394Cardinality of source node is initial
395Cardinality of target node is initial
396Cardinality &1 of target node is not valid
397System group &1: There is also a product named &1
398Field &1 contains forbidden characters
399Data type &1 contains forbidden characters
400Navigation path ID &1 must be a GUID
401Request field &1 contains forbidden characters
402Data element texts: Data element ID &1, language &2:
403Data element ID &1 is not provided
404Data element field texts: ID &1, language &2:
405Language &1 does not exist
406Language is initial
407Object type texts:
408Fields: Node type ID &1, field &2
409Node type ID &1 is not provided
410Node type texts: Node type ID &1, language &2:
411Data element ID &1:
412Field texts: Node type ID &1, field ID &2, language &3
413Field ID &1 is not provided
414Response fields: Response node type ID &1, response field ID &2
415Node type ID &1 (response node) is not provided
416Requests: Node type ID &1, request ID &1
417Request texts: Node type ID &1, request ID &2, language &3
418Node type ID &1, request ID &2 is not provided
419To-node of step &1 and from-node of step &2 are different
420Request field texts: Node type &1, request &2, field &3, language &4
421Node type ID &1, request ID &2, field ID &3 is not provided
422Relation fields: Relation ID &1 is not provided
423Naviagation paths: Navigation path ID &1 is not a GUID
424Navigation path steps: Navigation path ID &1, step &2
425Navigation path ID &1 is not provided
426Relation ID &1 is not provided
427Relation ID &1 does not fit to start node or target node of previous step
428Back-end navigations: Node type ID &1, TUI &2, TNID &3
429Back-end navigation texts: Node type ID &1, TUI &2,TNID &3
430Language &1 does not exist
431Back-end navigation to language &1 is not provided
432Back-end navigation params: Node type ID &1, TUI &2, TNID &3
433Target parameter &1: Back-end navigation is not provided
434Provider ID &1, object type ID &2 does not exist
435Wrong call of CL_ESH_OM_IMPMOD=>IMPORT_OBJECT_TYPE
436Object type ID not specified
437Navigation path is not used
438Category texts: Category ID &1, language &2
439Category ID &1 is not provided
440System group &1 cannot be reassigned to another product
441There is already an object type ID &1 (imported with provider ID &2)
442Could not create new ID for data type from &1
443Could not create new ID for data provider from &1
444Could not create new ID for relation from &1
445UI area contains forbidden characters
446System group &1 is assigned to system ID &2
447Types of field &1 and &2 are incompatible
448Migration of logical sytems failed
449Lock error when migrating logical systems
450Role assignment: Node ID &1, role type &2, role &3
451UI areas: Response node type ID &1, response field &2, UI area &3
452Node type &1, response field &2 is not provided
453Migrated model (&1)
454System with connection GUID &1 has no connection data
455Field &1 is a flag (Only 'X' or SPACE are allowed as input)
456ABAP data type &1 does not exist
457ABAP data type is initial
458No connection data provided for system with connection GUID &1
459&1 is not case-sensitive but contains lowercase characters
460Object type:
461UI operation &1 is not valid
462Could not populate area "Modified" from area "SAP"
463Lock error when populating area "Modified" from area "SAP" unsuccessful
464ABAP-Dictionary: Screen data type &1 does not exist
465Key of UI area assignment is not fully specified
466Object type &1, node &2, UI type &3, navigation/language &4:
467Object type is not allowed to be deleted
468There are connectors for system ID &1
469The system cannot be deleted
470Data provider &1 contains forbidden characters
471Data provider field &1 contains forbidden characters
472The model type cannot be changed
473System group &1 contains model
474There are models in the model
475The software component is assigned to system ID &1
476Data source &1 does not exist or is inactive
477Keyword incorporates several words
478"DATATYPE" &1 requires declaration of length (field "LENG")
479"INTTYPE" &1 requires declaration of number of decimals
480Response fields &1 and &2 have the same description in language &3
481Request fields &1 and &2 have the same description in language &3
482Link type is not valid
483More than one navigation ID is flagged to be the object link
484Software component &1 belongs to SAP and cannot be deleted
485Authorization check &1, language &2:
486Key of authorization check description is not fully specified
487Authorization check &1 does not exist
488Authorization check &1:
489Authorization check is initial
490Authorization check &1 contains forbidden characters
491Assignment of authorization check &3 to object type &1, node &2:
492There is already an assignment to authorization check &1
493Authorization check is referenced in object type &1, node &2
494Cannot delete authorization check
495Authorization strategy &1 does not exist
496Authorization strategy is initial
497Path-based authorization check &1 already exists
498Authorization strategy must be &1 or &2
499Object type &1, node &2, check field &3 does not exist
500Referenced authorization check &1 does not exist
501Start node of referenced authorization check does not fit nav. path
502Node of check field does not fit nav. path
503Referenced authorization check has wrong authorization strategy
504No check field is specified
505Check field specified and authorization check referenced
506&1 technical models generated
507&1 technical models generated and linked to node &2
508Technology &1 does not exist
509Authorization check &1, check value definition &2:
510Key of check value definition is not fully specified
511Authorization checks &1 and &2 have the same description in language &3
512Value is incompatible with type of check field
513Sign is initial
514Sign &1 does not exist
515Option is initial
516Option &1 does not exist
517RFC failure: &1
518Relation to authorization check &3
519Key of authorization check assignment was not fully specified
520Assignment of authorization check does not exist
521Relation is used in assignment of authorization check to node
522There is already a relation to navigation path &1
523Logical conjunction to object type &1, node &2: type &3, counter &4
524Key of part of logical conjunction is not fully specified
525Operator &1 does not exist
526Field &1 is numerical and has length &2 but also contains characters
527Cannot delete assignment of authorization check to node
528Assignment is used in logical conjunction
529There is already a part of a logical conjunction with type &1, counter &2
530Destination &1 is not suitable for selection of data in client &2
531Logical conjunction to object type &1, node &2: syntax error
532&1 is not an operator, bracket, or authorization check
533Logical conjunction must not start with &1
534&1 or authorization check followed by &2
535&1 is not preceeded by &2 or authorization check
536&1 is not preceeded by &2 or authorization check
537&1 is preceeded by &1 or authorization check
538Authorization check is preceeded by &1 or another authorization check
539Parenthesis unbalanced
540No navigation path specified for user-based authorization check
541Navigation path &1 is already used
542Authorization check &1, authorization field &2:
543The path of the selected check does not fit the current node
544Choose a customizing request
545Not all authorization checks are listed in logical conjunction
546Relation to authorization check &3
547In auth. check &1, auth. field &2 is not assigned to a node field
548Authorization check &1: assignment of auth. field &2 to node field
549Cannot delete assignment of authorization field to node field
550Assignment is referenced in assignment of auth. check to node
551Authorization check is referenced in authorization check &1
552Check field is initial
553User model is not available
554Key of fixed value definition for a relation field is not fully specified
555Fixed value definitions of composition &1/&2 to &3/&4
556Fixed value definitions of association ID &1:
557Value is incompatible with type of node field
558There is already a fixed value definition for source field &3
559There is already a fixed value definition for target field &3
560Object type &1, node &2, field &3 is already assigned to another field
561Relation is used in CPB navigation path &1, step &2
562Node is referenced in CPB navigation path &1
563Node is referenced in CPB navigation path &1, step &2
564There must be no more than one field of type "Date to"
565There must be no more than one field of type "Date from"
566Invalid relation used in NRF navigation path
567Software component is used by SWCV &1
568Software component cannot be deleted
569Software component &1 is used by itself
570Component &1 of SWCV differs from component &2 of predecessor
571Assignment of system &1 to SWCV &2
572Connection GUID is initial
573Assignment of system with connection GUID &1 to SWCV &2
574System contains content belonging to SWCV &1
575Request fields: Node type ID &1, request ID &2, field &3
576System (with connection GUID &1) is already assigned to SWC &2
577Software component usage: SWC &1 using SWC &2
578Used software component is initial
579SWC &1 contains modified content of SWC &2
580Software component usage cannot be deleted
581Software component hierarchy under SWC &1 contains a loop
582Software component usage SWC1 &1 using SWC &2 already exists
583There can be no more than one SWC for system component &1
584There can be no more than one SWC for system component &1, version &2
585We recommend a maximum of 19 characters for model names
586Category &1 is assigned to software component &2 and cannot be deleted
587Foreign key relation has been generated
588Default request has been generated
589Not all included software components are available
590SWCs delivered by SAP must not start with &1, &2 or &3
591Authorization checks &1 and &2 reference each other
592Keyword contains forbidden characters (&1)
593Object type has connectors in system &1: Deletion not possible
594The assignment of the system to the SWC &1 cannot be removed
595Relation ID &1 is a composition but the ID is not a GUID
596Authorization check &1 is already assigned to node &2
597Technical/Authorization object has request &1 at node &2
598Technical/Authorization object has response field &1 at node &2
599In technical/authorization object, subnode &1 is flagged 'subquery'
600Not all authorization fields are mapped to node fields or constants
601Relation &1 has no field mapping and no fixed values
602Check field and referenced authorization check is specified
603Logical conjunction to object type &1, node &2:
604Part of logical conjunction inherited from underlying SWC was changed
605Target attribute &1 is not a field of the target node &2
606Source attribute &1 is not a field of the source node &2
607Default request cannot be changed because it is inherited
608Relation field values: Relation ID &1 is not provided
609Model cannot be renamed because connectors exist
610The path of auth. field &1 does not fit to node the check is assigned
611The path of auth. check &1 does not fit to node &2 of object type &3
612Response field must not refer to node field with variable length
613Node &1 is not a child of the parent node but the subquery flag is set
614Relation does not fit the path of the auth. field
615Relation does not fit the path of the check
616Auth. field specified for ABAP authorization object-based check
617Relation from node to first node of path of check not defined
618Useless relation to start of the path of check specified
619Useless relation to start of the path of auth. field specified
620Relation from node to first node of path of auth. field not defined
621No navigation path specified leading to the node field referenced
622Navigation path specified although request field references own node
623No navigation path specified leading to the node field referenced
624Navigation path specified although response field references own node
625Navigation path does not fit to node of request and referenced node field
626Navigation path does not fit to response field and referenced node field
627Navigation path has no steps
628Software component &1 is not included
629The following checks are missing
630Relation is used in object type &1, node &2, response field &3
631Relation is used in object type &1, node &2, request &3, field &4
632Relation is used in path-based authorization check &1
633Relation is used in NFNW navigation path &1, step &2
634Relation is used in ABAP authorization check &1, auth. field &2
635Node is used in object type &1, node &2, request &3, field &4
636Node is used in object type &1, node &2, response field &3
637Node is used in ABAP authorization check &1, auth. field &2
638Node is used in path-based authorization check &1
639Software component &1 is managed by the Enterprise Search appliance
640User &1 has no authorization for administrative actions
641Back-end software component has not been imported before
642Error while creating the software component mapping
643Node fields are not numbered unambiguously
644Response fields are not numbered unambiguously
645Field name &1 not possible due to indexing restrictions
646System is Enterprise Search hub
647Cannot automatically resolve the following naming conflicts
648&1 "&2" in SWC &3 has same name as in SWC &4. Rename manually
649Could not rename &1 "&2" in SWC &3 - errors occurred during renaming
650Model &1 is only displayed as software component &2 is not editable
651Duplicate object type &1
652Exception when renaming entity &1
653Could not resolve duplicate entries in software component &1
654Could not create directory &1
655Could not change to directory &1
656Association type &1 does not exist
657Referenced node (object type &1, node &2) does not exist
658Virtual model must only have a root node
659Virtual model has more than one relation
660Virtual model has no relation to referenced model
661Type of association from virtual to referenced model must be &1
662Relation does not fit to virtual model and referenced model
663Root node of virtual models must only have key fields
664Conversion exit &1 is not allowed
665Relation between virtual model and referenced model must be 1:1
666No referenced model spefied for virtual model
667Virtual model &1:
668Path is used in authorization but references relation of virtual model
669Regenerating related request for object type &1, node &2:
670Request belongs to foreign software component, regeneration not possible
671&4 cannot be used in fields that contain human-readable text
672Node field is used in authorization check &1 that has value &2
673Could not change to directory &1
674You did not choose a folder, so I am going to use the SAP work dir: &1
675Select a KM system and an existing index
676Severe errors occurred. Export has not been finished correctly
677Error occurred when writing file &1
678Depending on your configuration, problems might have occurred. See output
679SWC stacks of SWC &1 and SWC &2 have to be identical
680You do not have sufficient authorization to perform this action
681Compositon &1 does not point to the imported object type
682Category &1:
683Optimized model for system &1 cannot be changed
684Optimized model has connectors, model cannot be deleted
685Wrong stack type
686Instance of class &1 is obsolete
687Optimized model for connection &1 must be a GUID
688GUID for optimized model is already used as a model GUID
689GUID for model is already used as an optimized model GUID
690System with connection GUID &1:
691Object type &1, node &2 is already listed in node optimization data
692Optimization data for object type &1, node &2
693Key of node compressed node was not fully specified
694Compressed node (object type &1, node &2) does not exist
695Field semantics of node field must be "SAP User ID"
696Remove child categories of non-editable software components first
697Delete all nodes before switching to "Virtual Model"
698ABAP authorization object-based check &1 has no data
699ABAP authorization object-based check &1 has ambiguous data
700ABAP authorization object-based check &1 has wrong data
701Path-based authorization check &1 has no data
702Path-based authorization check &1 has ambiguous data
703Path-based authorization check &1 has wrong data
704Path-based authorization check &1 has wrong data
705Referencing authorization check &1 has another authorization strategy
706Object type ID &1 (imported with provider ID &2)
707Authorization check assignments: Node type ID &1, auth. check &2
708Start relations for paths in assiged authorization checks
709Auth. check assignments - logical conjunction: Node type ID &1
710Exception when instantiating model repository
711Software component for back-end name &1, version ID &2 already exists
712Node field is not referenced in a request field
713Request field references node field flagged for interactive navigation
714SWC &1 references content of SWC &2
715Relation &1 refers to unknown object type(s)
716Switch assignment for &1/&2/&3/&4 already exists
717Key of switch assignment was not fully specified
718Switch assignment for tab name &1, language &2, switch ID &3:
719Key for table entry is initial
720Tab name &1 is not allowed for switch assignment
721Switch ID &1 does not exist
722Switch action is initial
723Switch action &1 does not exist
724Field semantics &1 does not exist
725Category texts: Category ID &1, language &2:
726Authorization check texts: Authorization check ID &1, language &2:
727Model &1, node &2, response field &3 does not exist
728Object type &1, node &2, request &3, request field &4 does not exist
729Entry with key GUID &1 does not exist for tab name &2
730Could not delete &1 "&2" in model &3 - errors occurred during deletion
731Cannot resolve conflicts. Action not supported
732Nodes flagged as "subquery" must have the root node as a parent
733Virtual model must have a root node
734No connector has been created: Select a back-end connection
735SAVE is not possible when switch settings are specified
736RFC failure &1 when trying to connect to &2
737Classification pattern (object type &1) is inconsistent (error &2)
738Objects starting with Y or Z cannot be created in SAP software component
739Model &1 successfully imported
740Software component &1 successfully imported
741Category is already assigned to a globally-defined object type
742Software component &1 already exists globally
743Software component for back-end name &1, version ID &2 exists globally
744UI area is referenced globally
745Back-end navigation has no description
746There is more than one response attribute with UI area "Title"
747Node has no response attribute with UI area "Title"
748There is more than one response attribute with UI area "Detail image"
749There are more than nine response attributes with UI area "Summary"
750There is more than one response attribute with UI area "Thumbnail"
751Assignments created when connecting back ends cannot be deleted
752Back-end system &1, client &2 has been connected to ES hub &3, client &4
753You cannot edit software components
754You are not allowed to delete software components
755Selected SWC &1 is different to SWC &2 specified via interface
756Software component &1 and component &2 must have the same model type
757The changes have been saved
758Model type of software component &1 cannot be changed
759Model type of software component &1 cannot be changed
760Back-end name of object type &1, node &2, response field &3:
761Back-end name of object type &1, node &2, request &3, field &4:
762Existing connector &1 will be assigned to software component &3
763Software component &1 has already been assigned to transport request &2
764Category &1 cannot be assigned to model &3 of SWC &2
765Category &1 cannot be assigned to model &3 of SWC &2
766Category &1 must have a superordinate software component
767Superordinate SC for category &1 has no system software component
768Assignment of system software component cannot be removed
769Assignment to system software component is not possible
770Assignment to system software component is not possible
771Switch cannot be assigned to root node of model &1
772Node &2 cannot be a root node because there are switches assigned to it
773UI area is used in connector of model (node &2, resp. field &3)
774Objects &1 and &2 are overlapping copies of the same original object
775Objects share the following copied subcomponents
776&1 &2 occurs as copy in the software components &3 and &4
777Copies of each other cannot be used as connectors in parallel
778Categories: Category ID &1:
779Superordinate software component &1 does not exist
780Superordinate software component with GUID &1 does not exist
781Property model has not yet been created
782Several property models; assign correct one manually
783Property data type model has not yet been created
784Several property data type models; assign correct one manually
785Technical model &1 generated (classification valuation)
786Model &1 generated (classification property)
787Technical model &1 generated (classification data type)
788Technical model for domain &1 not generated (multiple key fields)
789Node type ID &1:
790It is not possible to specify fields and a DDIC-reference
791Not all messages displayed...
792Conflict cannot be resolved automatically, manual action required
793Resolution of pending text references is already running
794Resolution of pending text references has been scheduled in background
795Object factory called with incorrect model category
796Connectors of the superordinate software component &1 already exist
797Connector for model &1 of SWC &2 was created in SWC &3
798Software component &1 starting with &2 cannot be created or changed
799Software component &1 starting with &2 cannot be created
800Node successfully imported
801Data Source &1 successfully imported
802The request field cannot have the same name as response field &4
803Related requests: Node type ID &1, related request &2/&3/&4
804The response field cannot have the same name as field &4 of request &3
805Software component cannot be edited here
806Authorization checks of attribute node will be disregarded
807Connector of object type &1 for system &2 is assigned to the category
808Object type &2, node &3, field &4 is switched off
809Object type &2, node &3 is switched off
810Association &2 is switched off
811Composition from node &3 to node &4 in object type &2 is switched off
812Object type &1, node &2, ODP ID &3, ODP semantics &4:
813Key of operational data provider is not fully specified
814ODP with ID &1 already exists
815Object type &1, node &2, ODP &3, language &4:
816ODP does not exist
817Object type &1, node &2, ODP &3, field &4:
818Key of operational data provider field is not fully specified
819Object type &1, node &2, ODP ID &3, ODP semantics &4 does not exist
820ODP field type &1 does not exist
821Aggregation mode &1 does not exist
822ODP fields &1 and &2 have the same description in language &3
823ODP ID &1 contains forbidden characters
824ODP field &1 contains forbidden characters
825ODP ID &1, ODP semantics &4 already exists in object type &2, node &3
826Description already exists in language &4
827Original data provider field &1 already exists
828There are no attributes available
829Default ODP attributes have been generated
830Field is referenced in object type &1, node &2, ODP &3, field &4
831Object type &1, node &2, ODP &3, field &4 does not exist
832ODPs: Node type ID &1, ODP ID &2, ODP semantics &3
833ODP texts: Node type ID &1, ODP ID &2, ODP semantics &3, language &4
834Node type ID &1, ODP ID &2, ODP semantics &3 is not provided
835ODP field texts: Node type &1, ODP &2, field &3, language &4
836Node type ID &1, ODP ID &2, ODP semantics &3, field ID &4 is not provided
837ODP fields: Node type ID &1, ODP ID &2, ODP semantics &3, field &4
838Navigation path &1 contains step &2 for navigation path &3
839Navigation path ID &1:
840Navigation path does not fit node of ODP and referenced node field
841There must be no more than one operational data provider
842Navigation path from object type &1, node &2 to object type &3 node &4
843Object type &1, node &2, node attribute group &3:
844Key of attribute group is not fully specified
845Object type &1, node &2, node attribute group &3 does not exist
846Navigation path ID is initial
847Ranking weight &1 does not exist
848Key of field assignment to attribute group is not fully specified
849Assignment of object type &1, node &2, field &4 to attribute group &3
850Key of attribute group description is not fully specified
851Object type &1, node &2, node attribute group &3, language &4:
852Node attribute group does not exist
853Node is used in object type &1, node &2, ODP &3, field &4
854Node is referenced in NAF navigation path &1
855Node is referenced in NAF navigation path &1, step &2
856Relation is used in NAF navigation path &1, step &2
857Relation is used in object type &1, node &2, ODP &3, field &4
858Object type &1, node &2, node attribute group &3 using group &4
859Key of usage is not fully specified
860Object type &1, node &2, attribute group &3 does not exist
861Scheduling information cannot be set for real-time indexing
862Cannot delete attribute group
863Attribute group is used in attribute group &3
864Attribute group &1 contains forbidden characters
865Field &1 cannot be assigned to attribute group &3
866Attribute group &1 cannot be used by attribute group &3
867Attribute group is used by more than one other attribute group
868Hierarchy of node attribute groups contains a loop
869Attribute group &1 is used by attribute group &2
870Object type &1, node &2, node attribute group &3 already exists
871Field &4 is already assigned to node attribute group &1/&2/&3
872Node attribute group &1 is already used by node attribute group &1/&2/&3
873Object type &1, node &2, response attribute group &3 does not exist
874Object type &1, node &2, response attribute group &3:
875Object type &1, node &2, response attribute group &3, language &4:
876Response attribute group does not exist
877Assignment of object type &1, node &2, field &4 to attribute group &3
878Object type &1, node &2, response attribute group &3 using group &4
879Object type &1, node &2, response attribute group &3 already exists
880Field &4 is already assigned to response attribute group &1/&2/&3
881Resp. attribute group &1 is already used by resp attribute group &1/&2/&3
882Object type &1, node &2, response attribute group &3, ui area &4:
883UI area is referenced in object type &1, node &2, resp. attr. grp &3
884UI area is used in connector of model &1 (node &2, resp.attr.grp. &3)
885Object type &1, node &2, request &3, attribute group &4 does not exist
886Object type &1, node &2, request &3, attribute group &4:
887Key of attribute group description for language &1 is not fully specified
888Key of assignment of field &1 to attribute group is not fully specified
889Key of usage of attribute group &1 is not fully specified
890Hierarchy of response attribute groups contains a loop
891Hierarchy of attribute groups contains a loop
892UI area &4 is already assigned response attribute group &1/&2/&3
893Object type &1, node &2, request &3, attribute group &4 already exists
894Request field &1 is already assigned to the attribute group
895Attribute group &1 is already used by attribute group &2
896Description already exists in language &4
897Description already exists in language &4
898Description already exists in language &1
899Data provider &1, attribute group &2 using group &3
900
Privacy Policy