Message Number list used by SAP ABAP Class CL_ESH_OM_OTYP (Object Types)
SAP ABAP Class CL_ESH_OM_OTYP (Object Types) is using
# Object Type Object Name Object Description Note
     
1 Message Number  ESH_OM_OBJ_MODEL_REP - 006 Object type &1 does not exist
2 Message Number  ESH_OM_OBJ_MODEL_REP - 006 Object type &1 does not exist
3 Message Number  ESH_OM_OBJ_MODEL_REP - 006 Object type &1 does not exist
4 Message Number  ESH_OM_OBJ_MODEL_REP - 008 There must be exactly one root node
5 Message Number  ESH_OM_OBJ_MODEL_REP - 009 Key of object type description is not fully specified
6 Message Number  ESH_OM_OBJ_MODEL_REP - 012 Object type is initial
7 Message Number  ESH_OM_OBJ_MODEL_REP - 013 Data provider &1 does not exist
8 Message Number  ESH_OM_OBJ_MODEL_REP - 014 Key of data provider filter &1/&2 is not fully specified
9 Message Number  ESH_OM_OBJ_MODEL_REP - 017 Key of node was not fully specified
10 Message Number  ESH_OM_OBJ_MODEL_REP - 017 Key of node was not fully specified
11 Message Number  ESH_OM_OBJ_MODEL_REP - 017 Key of node was not fully specified
12 Message Number  ESH_OM_OBJ_MODEL_REP - 017 Key of node was not fully specified
13 Message Number  ESH_OM_OBJ_MODEL_REP - 018 No relation specified
14 Message Number  ESH_OM_OBJ_MODEL_REP - 019 Data provider &1, filter &2 does not exist
15 Message Number  ESH_OM_OBJ_MODEL_REP - 020 Key of node description is not fully specified
16 Message Number  ESH_OM_OBJ_MODEL_REP - 025 Object type description in language &1 already exists
17 Message Number  ESH_OM_OBJ_MODEL_REP - 033 Object type &1 has to start with &2 in customer systems
18 Message Number  ESH_OM_OBJ_MODEL_REP - 039 Object type &1, node &2, back-end navigation &3/&4:
19 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
20 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
21 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
22 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
23 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
24 Message Number  ESH_OM_OBJ_MODEL_REP - 053 Key of request field is not fully specified
25 Message Number  ESH_OM_OBJ_MODEL_REP - 055 Relation ID &1 does not exist
26 Message Number  ESH_OM_OBJ_MODEL_REP - 055 Relation ID &1 does not exist
27 Message Number  ESH_OM_OBJ_MODEL_REP - 055 Relation ID &1 does not exist
28 Message Number  ESH_OM_OBJ_MODEL_REP - 055 Relation ID &1 does not exist
29 Message Number  ESH_OM_OBJ_MODEL_REP - 057 Value "&1" contains spaces
30 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
31 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
32 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
33 Message Number  ESH_OM_OBJ_MODEL_REP - 074 Data type is initial
34 Message Number  ESH_OM_OBJ_MODEL_REP - 075 Key of authorization check is not fully specified
35 Message Number  ESH_OM_OBJ_MODEL_REP - 076 Data type &1 does not exist
36 Message Number  ESH_OM_OBJ_MODEL_REP - 077 Text data type &1 does not exist
37 Message Number  ESH_OM_OBJ_MODEL_REP - 077 Text data type &1 does not exist
38 Message Number  ESH_OM_OBJ_MODEL_REP - 077 Text data type &1 does not exist
39 Message Number  ESH_OM_OBJ_MODEL_REP - 078 Object type &1, node &2, response field &3:
40 Message Number  ESH_OM_OBJ_MODEL_REP - 078 Object type &1, node &2, response field &3:
41 Message Number  ESH_OM_OBJ_MODEL_REP - 078 Object type &1, node &2, response field &3:
42 Message Number  ESH_OM_OBJ_MODEL_REP - 079 Key of response field is not fully specified
43 Message Number  ESH_OM_OBJ_MODEL_REP - 080 Key of referenced node field is not fully specified
44 Message Number  ESH_OM_OBJ_MODEL_REP - 080 Key of referenced node field is not fully specified
45 Message Number  ESH_OM_OBJ_MODEL_REP - 081 Object type &1, node &2, node field &3 does not exist
46 Message Number  ESH_OM_OBJ_MODEL_REP - 081 Object type &1, node &2, node field &3 does not exist
47 Message Number  ESH_OM_OBJ_MODEL_REP - 081 Object type &1, node &2, node field &3 does not exist
48 Message Number  ESH_OM_OBJ_MODEL_REP - 083 Object type &1, node &2, request &3:
49 Message Number  ESH_OM_OBJ_MODEL_REP - 083 Object type &1, node &2, request &3:
50 Message Number  ESH_OM_OBJ_MODEL_REP - 083 Object type &1, node &2, request &3:
51 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
52 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
53 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
54 Message Number  ESH_OM_OBJ_MODEL_REP - 085 Object type &1 is in customer namespace (&2)
55 Message Number  ESH_OM_OBJ_MODEL_REP - 086 Key of node field is not fully specified
56 Message Number  ESH_OM_OBJ_MODEL_REP - 087 Key of request is not fully specified
57 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
58 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
59 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
60 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
61 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
62 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
63 Message Number  ESH_OM_OBJ_MODEL_REP - 088 Object type &1, node &2 does not exist
64 Message Number  ESH_OM_OBJ_MODEL_REP - 089 Object type &1, node &2, request &3 does not exist
65 Message Number  ESH_OM_OBJ_MODEL_REP - 090 Relation ID is initial
66 Message Number  ESH_OM_OBJ_MODEL_REP - 090 Relation ID is initial
67 Message Number  ESH_OM_OBJ_MODEL_REP - 090 Relation ID is initial
68 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
69 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
70 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
71 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
72 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
73 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
74 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
75 Message Number  ESH_OM_OBJ_MODEL_REP - 094 Source node key is not fully specified
76 Message Number  ESH_OM_OBJ_MODEL_REP - 095 Source node &1/&2 does not exist
77 Message Number  ESH_OM_OBJ_MODEL_REP - 096 Target node &1/&2 does not exist
78 Message Number  ESH_OM_OBJ_MODEL_REP - 097 Source node field is initial
79 Message Number  ESH_OM_OBJ_MODEL_REP - 098 Source node field &1 does not exist
80 Message Number  ESH_OM_OBJ_MODEL_REP - 099 Target node field is initial
81 Message Number  ESH_OM_OBJ_MODEL_REP - 100 Target node field &1 does not exist
82 Message Number  ESH_OM_OBJ_MODEL_REP - 101 Key of related request &1/&2/&3 is not fully specified
83 Message Number  ESH_OM_OBJ_MODEL_REP - 102 Related request &1/&2/&3 does not exist
84 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
85 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
86 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
87 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
88 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
89 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
90 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
91 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
92 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
93 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
94 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
95 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
96 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
97 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
98 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
99 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
100 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
101 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
102 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
103 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
104 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
105 Message Number  ESH_OM_OBJ_MODEL_REP - 115 Rel. requests for object type &1, node &2:
106 Message Number  ESH_OM_OBJ_MODEL_REP - 122 Request does not exist
107 Message Number  ESH_OM_OBJ_MODEL_REP - 125 Node does not exist
108 Message Number  ESH_OM_OBJ_MODEL_REP - 125 Node does not exist
109 Message Number  ESH_OM_OBJ_MODEL_REP - 126 Object type &1, node &2, UI type &3, target navigation &4:
110 Message Number  ESH_OM_OBJ_MODEL_REP - 127 Key of back-end navigation is not fully specified
111 Message Number  ESH_OM_OBJ_MODEL_REP - 128 Key of request description is not fully specified
112 Message Number  ESH_OM_OBJ_MODEL_REP - 131 Key of back-end navigation description is not fully specified
113 Message Number  ESH_OM_OBJ_MODEL_REP - 131 Key of back-end navigation description is not fully specified
114 Message Number  ESH_OM_OBJ_MODEL_REP - 132 Back-end navigation does not exist
115 Message Number  ESH_OM_OBJ_MODEL_REP - 132 Back-end navigation does not exist
116 Message Number  ESH_OM_OBJ_MODEL_REP - 133 Navigation path &1:
117 Message Number  ESH_OM_OBJ_MODEL_REP - 134 Start node key is not fully specified
118 Message Number  ESH_OM_OBJ_MODEL_REP - 135 Start node &1/&2 does not exist
119 Message Number  ESH_OM_OBJ_MODEL_REP - 136 End node key is not fully specified
120 Message Number  ESH_OM_OBJ_MODEL_REP - 137 End node &1/&2 does not exist
121 Message Number  ESH_OM_OBJ_MODEL_REP - 138 Navigation path &1, step &2:
122 Message Number  ESH_OM_OBJ_MODEL_REP - 139 Key of navigation path step is not fully specified
123 Message Number  ESH_OM_OBJ_MODEL_REP - 140 Navigation path &1 does not exist
124 Message Number  ESH_OM_OBJ_MODEL_REP - 140 Navigation path &1 does not exist
125 Message Number  ESH_OM_OBJ_MODEL_REP - 140 Navigation path &1 does not exist
126 Message Number  ESH_OM_OBJ_MODEL_REP - 141 From-node key is not fully specified
127 Message Number  ESH_OM_OBJ_MODEL_REP - 142 From-node &1/&2 does not exist
128 Message Number  ESH_OM_OBJ_MODEL_REP - 143 To-node key is not fully specified
129 Message Number  ESH_OM_OBJ_MODEL_REP - 144 To-node &1/&2 does not exist
130 Message Number  ESH_OM_OBJ_MODEL_REP - 145 Field ass. of object type &1, node &2, UI type &3, operation &4:
131 Message Number  ESH_OM_OBJ_MODEL_REP - 146 Response field &1 does not exist
132 Message Number  ESH_OM_OBJ_MODEL_REP - 147 Response field is initial
133 Message Number  ESH_OM_OBJ_MODEL_REP - 151 Object type &1, language &2:
134 Message Number  ESH_OM_OBJ_MODEL_REP - 152 Object type &1, node &2, language &3:
135 Message Number  ESH_OM_OBJ_MODEL_REP - 153 Object type &1, node &2, request &3, language &4:
136 Message Number  ESH_OM_OBJ_MODEL_REP - 193 Node name &1 contains forbidden characters
137 Message Number  ESH_OM_OBJ_MODEL_REP - 194 Object type &1 contains forbidden characters
138 Message Number  ESH_OM_OBJ_MODEL_REP - 195 Request &1 contains forbidden characters
139 Message Number  ESH_OM_OBJ_MODEL_REP - 202 Request &1 is reserved
140 Message Number  ESH_OM_OBJ_MODEL_REP - 213 Node is referenced as physical node in object type &1, node &2
141 Message Number  ESH_OM_OBJ_MODEL_REP - 214 Cannot delete node
142 Message Number  ESH_OM_OBJ_MODEL_REP - 215 Node is referenced in NQF navigation path &1
143 Message Number  ESH_OM_OBJ_MODEL_REP - 216 Node is referenced in NQF navigation path &1, step &2
144 Message Number  ESH_OM_OBJ_MODEL_REP - 217 Node is referenced in NRF navigation path &1
145 Message Number  ESH_OM_OBJ_MODEL_REP - 218 Node is referenced in NRF navigation path &1, step &2
146 Message Number  ESH_OM_OBJ_MODEL_REP - 219 Node has child node &1
147 Message Number  ESH_OM_OBJ_MODEL_REP - 220 Cannot delete node field
148 Message Number  ESH_OM_OBJ_MODEL_REP - 221 Field is referenced in object type &1, node &2, resp. field &3
149 Message Number  ESH_OM_OBJ_MODEL_REP - 222 Field is referenced in object type &1, node &2, request &3, field &4
150 Message Number  ESH_OM_OBJ_MODEL_REP - 226 Cannot delete request &1
151 Message Number  ESH_OM_OBJ_MODEL_REP - 227 Request is related to object type &1, node &2
152 Message Number  ESH_OM_OBJ_MODEL_REP - 228 Field is referenced in relation ID &1
153 Message Number  ESH_OM_OBJ_MODEL_REP - 229 Field is referenced in composition &1/&2 to &3/&4
154 Message Number  ESH_OM_OBJ_MODEL_REP - 230 Cannot delete relation
155 Message Number  ESH_OM_OBJ_MODEL_REP - 231 Composition &1/&2 to &3/&4
156 Message Number  ESH_OM_OBJ_MODEL_REP - 231 Composition &1/&2 to &3/&4
157 Message Number  ESH_OM_OBJ_MODEL_REP - 232 Relation is used in NQF navigation path &1, step &2
158 Message Number  ESH_OM_OBJ_MODEL_REP - 233 Relation is used in NRF navigation path &1, step &2
159 Message Number  ESH_OM_OBJ_MODEL_REP - 234 Cannot delete request field
160 Message Number  ESH_OM_OBJ_MODEL_REP - 235 Field is referenced in object type &1, node &2, rel. request &3
161 Message Number  ESH_OM_OBJ_MODEL_REP - 258 Node is referenced in NFNW navigation path &1
162 Message Number  ESH_OM_OBJ_MODEL_REP - 259 Node is referenced in NFNW navigation path &1, step &2
163 Message Number  ESH_OM_OBJ_MODEL_REP - 260 Node is referenced in NSNW navigation path &1
164 Message Number  ESH_OM_OBJ_MODEL_REP - 262 One node must be flagged as the root node
165 Message Number  ESH_OM_OBJ_MODEL_REP - 265 There must be at least one key field in node &1
166 Message Number  ESH_OM_OBJ_MODEL_REP - 271 You cannot delete the default request if there are other requests
167 Message Number  ESH_OM_OBJ_MODEL_REP - 272 You cannot delete the root node if there are other nodes
168 Message Number  ESH_OM_OBJ_MODEL_REP - 284 Types of field &1 and &2 are incompatible
169 Message Number  ESH_OM_OBJ_MODEL_REP - 286 Response field &1 contains forbidden characters
170 Message Number  ESH_OM_OBJ_MODEL_REP - 287 Relation ID &1 contains characters that are not allowed
171 Message Number  ESH_OM_OBJ_MODEL_REP - 289 No authorization for action &1 on object &2
172 Message Number  ESH_OM_OBJ_MODEL_REP - 289 No authorization for action &1 on object &2
173 Message Number  ESH_OM_OBJ_MODEL_REP - 289 No authorization for action &1 on object &2
174 Message Number  ESH_OM_OBJ_MODEL_REP - 308 Nodes &1 and &2 have the same description in language &3
175 Message Number  ESH_OM_OBJ_MODEL_REP - 309 Object types &1 and &2 have the same description in language &3
176 Message Number  ESH_OM_OBJ_MODEL_REP - 310 Requests &1 and &2 have the same description in language &3
177 Message Number  ESH_OM_OBJ_MODEL_REP - 318 Association ID &1:
178 Message Number  ESH_OM_OBJ_MODEL_REP - 318 Association ID &1:
179 Message Number  ESH_OM_OBJ_MODEL_REP - 320 Description already exists in language &3
180 Message Number  ESH_OM_OBJ_MODEL_REP - 322 Description already exists in language &4
181 Message Number  ESH_OM_OBJ_MODEL_REP - 324 Description already exists in language &1
182 Message Number  ESH_OM_OBJ_MODEL_REP - 338 There is no UI area &1
183 Message Number  ESH_OM_OBJ_MODEL_REP - 345 Object type &1, language &2, keyword &3:
184 Message Number  ESH_OM_OBJ_MODEL_REP - 345 Object type &1, language &2, keyword &3:
185 Message Number  ESH_OM_OBJ_MODEL_REP - 346 Key of keyword assignment is not fully specified
186 Message Number  ESH_OM_OBJ_MODEL_REP - 348 Object type &1, node &2, response field &3, ui area &4:
187 Message Number  ESH_OM_OBJ_MODEL_REP - 349 Object type &1, node &2, response field &3 does not exist
188 Message Number  ESH_OM_OBJ_MODEL_REP - 352 Object type &1, node &2, role type &3, role &4:
189 Message Number  ESH_OM_OBJ_MODEL_REP - 353 Key of role assignment is not fully specified
190 Message Number  ESH_OM_OBJ_MODEL_REP - 355 Role type &1, role &2 does not exist
191 Message Number  ESH_OM_OBJ_MODEL_REP - 356 Icon &1 does not exist
192 Message Number  ESH_OM_OBJ_MODEL_REP - 359 Category &1 does not exist
193 Message Number  ESH_OM_OBJ_MODEL_REP - 369 Type &1 does not exist
194 Message Number  ESH_OM_OBJ_MODEL_REP - 370 Type of object type is initial
195 Message Number  ESH_OM_OBJ_MODEL_REP - 371 Object type &1, category &2:
196 Message Number  ESH_OM_OBJ_MODEL_REP - 372 Key of category assignment is not fully specified
197 Message Number  ESH_OM_OBJ_MODEL_REP - 375 There is no modification status &1
198 Message Number  ESH_OM_OBJ_MODEL_REP - 375 There is no modification status &1
199 Message Number  ESH_OM_OBJ_MODEL_REP - 375 There is no modification status &1
200 Message Number  ESH_OM_OBJ_MODEL_REP - 375 There is no modification status &1
201 Message Number  ESH_OM_OBJ_MODEL_REP - 381 Text-search-relevant fields cannot be used in relations
202 Message Number  ESH_OM_OBJ_MODEL_REP - 385 You cannot delete the node field
203 Message Number  ESH_OM_OBJ_MODEL_REP - 386 You cannot delete the request
204 Message Number  ESH_OM_OBJ_MODEL_REP - 387 There is no modification status &1
205 Message Number  ESH_OM_OBJ_MODEL_REP - 388 Target UI type &1 is not valid
206 Message Number  ESH_OM_OBJ_MODEL_REP - 389 Relation does not fit to from-node and to-node of navigation path step
207 Message Number  ESH_OM_OBJ_MODEL_REP - 393 Cardinality &1 of source node is not valid
208 Message Number  ESH_OM_OBJ_MODEL_REP - 394 Cardinality of source node is initial
209 Message Number  ESH_OM_OBJ_MODEL_REP - 395 Cardinality of target node is initial
210 Message Number  ESH_OM_OBJ_MODEL_REP - 396 Cardinality &1 of target node is not valid
211 Message Number  ESH_OM_OBJ_MODEL_REP - 398 Field &1 contains forbidden characters
212 Message Number  ESH_OM_OBJ_MODEL_REP - 401 Request field &1 contains forbidden characters
213 Message Number  ESH_OM_OBJ_MODEL_REP - 447 Types of field &1 and &2 are incompatible
214 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
215 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
216 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
217 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
218 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
219 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
220 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
221 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
222 Message Number  ESH_OM_OBJ_MODEL_REP - 455 Field &1 is a flag (Only 'X' or SPACE are allowed as input)
223 Message Number  ESH_OM_OBJ_MODEL_REP - 461 UI operation &1 is not valid
224 Message Number  ESH_OM_OBJ_MODEL_REP - 465 Key of UI area assignment is not fully specified
225 Message Number  ESH_OM_OBJ_MODEL_REP - 466 Object type &1, node &2, UI type &3, navigation/language &4:
226 Message Number  ESH_OM_OBJ_MODEL_REP - 467 Object type is not allowed to be deleted
227 Message Number  ESH_OM_OBJ_MODEL_REP - 477 Keyword incorporates several words
228 Message Number  ESH_OM_OBJ_MODEL_REP - 482 Link type is not valid
229 Message Number  ESH_OM_OBJ_MODEL_REP - 483 More than one navigation ID is flagged to be the object link
230 Message Number  ESH_OM_OBJ_MODEL_REP - 487 Authorization check &1 does not exist
231 Message Number  ESH_OM_OBJ_MODEL_REP - 489 Authorization check is initial
232 Message Number  ESH_OM_OBJ_MODEL_REP - 491 Assignment of authorization check &3 to object type &1, node &2:
233 Message Number  ESH_OM_OBJ_MODEL_REP - 491 Assignment of authorization check &3 to object type &1, node &2:
234 Message Number  ESH_OM_OBJ_MODEL_REP - 513 Sign is initial
235 Message Number  ESH_OM_OBJ_MODEL_REP - 514 Sign &1 does not exist
236 Message Number  ESH_OM_OBJ_MODEL_REP - 515 Option is initial
237 Message Number  ESH_OM_OBJ_MODEL_REP - 516 Option &1 does not exist
238 Message Number  ESH_OM_OBJ_MODEL_REP - 518 Relation to authorization check &3
239 Message Number  ESH_OM_OBJ_MODEL_REP - 519 Key of authorization check assignment was not fully specified
240 Message Number  ESH_OM_OBJ_MODEL_REP - 519 Key of authorization check assignment was not fully specified
241 Message Number  ESH_OM_OBJ_MODEL_REP - 520 Assignment of authorization check does not exist
242 Message Number  ESH_OM_OBJ_MODEL_REP - 520 Assignment of authorization check does not exist
243 Message Number  ESH_OM_OBJ_MODEL_REP - 521 Relation is used in assignment of authorization check to node
244 Message Number  ESH_OM_OBJ_MODEL_REP - 523 Logical conjunction to object type &1, node &2: type &3, counter &4
245 Message Number  ESH_OM_OBJ_MODEL_REP - 524 Key of part of logical conjunction is not fully specified
246 Message Number  ESH_OM_OBJ_MODEL_REP - 525 Operator &1 does not exist
247 Message Number  ESH_OM_OBJ_MODEL_REP - 526 Field &1 is numerical and has length &2 but also contains characters
248 Message Number  ESH_OM_OBJ_MODEL_REP - 527 Cannot delete assignment of authorization check to node
249 Message Number  ESH_OM_OBJ_MODEL_REP - 528 Assignment is used in logical conjunction
250 Message Number  ESH_OM_OBJ_MODEL_REP - 541 Navigation path &1 is already used
251 Message Number  ESH_OM_OBJ_MODEL_REP - 541 Navigation path &1 is already used
252 Message Number  ESH_OM_OBJ_MODEL_REP - 546 Relation to authorization check &3
253 Message Number  ESH_OM_OBJ_MODEL_REP - 547 In auth. check &1, auth. field &2 is not assigned to a node field
254 Message Number  ESH_OM_OBJ_MODEL_REP - 554 Key of fixed value definition for a relation field is not fully specified
255 Message Number  ESH_OM_OBJ_MODEL_REP - 555 Fixed value definitions of composition &1/&2 to &3/&4
256 Message Number  ESH_OM_OBJ_MODEL_REP - 556 Fixed value definitions of association ID &1:
257 Message Number  ESH_OM_OBJ_MODEL_REP - 557 Value is incompatible with type of node field
258 Message Number  ESH_OM_OBJ_MODEL_REP - 558 There is already a fixed value definition for source field &3
259 Message Number  ESH_OM_OBJ_MODEL_REP - 559 There is already a fixed value definition for target field &3
260 Message Number  ESH_OM_OBJ_MODEL_REP - 560 Object type &1, node &2, field &3 is already assigned to another field
261 Message Number  ESH_OM_OBJ_MODEL_REP - 561 Relation is used in CPB navigation path &1, step &2
262 Message Number  ESH_OM_OBJ_MODEL_REP - 562 Node is referenced in CPB navigation path &1
263 Message Number  ESH_OM_OBJ_MODEL_REP - 563 Node is referenced in CPB navigation path &1, step &2
264 Message Number  ESH_OM_OBJ_MODEL_REP - 585 We recommend a maximum of 19 characters for model names
265 Message Number  ESH_OM_OBJ_MODEL_REP - 592 Keyword contains forbidden characters
266 Message Number  ESH_OM_OBJ_MODEL_REP - 593 Object type has connectors in system &1: Deletion not possible
267 Message Number  ESH_OM_OBJ_MODEL_REP - 609 Model cannot be renamed because connectors exist
268 Message Number  ESH_OM_OBJ_MODEL_REP - 616 Auth. field specified for ABAP authorization object-based check
269 Message Number  ESH_OM_OBJ_MODEL_REP - 630 Relation is used in object type &1, node &2, response field &3
270 Message Number  ESH_OM_OBJ_MODEL_REP - 631 Relation is used in object type &1, node &2, request &3, field &4
271 Message Number  ESH_OM_OBJ_MODEL_REP - 632 Relation is used in path-based authorization check &1
272 Message Number  ESH_OM_OBJ_MODEL_REP - 633 Relation is used in NFNW navigation path &1, step &2
273 Message Number  ESH_OM_OBJ_MODEL_REP - 634 Relation is used in ABAP authorization check &1, auth. field &2
274 Message Number  ESH_OM_OBJ_MODEL_REP - 635 Node is used in object type &1, node &2, request &3, field &4
275 Message Number  ESH_OM_OBJ_MODEL_REP - 636 Node is used in object type &1, node &2, response field &3
276 Message Number  ESH_OM_OBJ_MODEL_REP - 637 Node is used in ABAP authorization check &1, auth. field &2
277 Message Number  ESH_OM_OBJ_MODEL_REP - 638 Node is used in path-based authorization check &1
278 Message Number  ESH_OM_OBJ_MODEL_REP - 656 Association type &1 does not exist
279 Message Number  ESH_OM_OBJ_MODEL_REP - 657 Referenced node (object type &1, node &2) does not exist
280 Message Number  ESH_OM_OBJ_MODEL_REP - 672 Node field is used in authorization check &1 that has value &2
281 Message Number  ESH_OM_OBJ_MODEL_REP - 724 Field semantics &1 does not exist
282 Message Number  ESH_OM_OBJ_MODEL_REP - 738 Objects starting with Y or Z cannot be created in SAP software component
283 Message Number  ESH_OM_OBJ_MODEL_REP - 772 Node &2 cannot be a root node because there are switches assigned to it
284 Message Number  ESH_OM_OBJ_MODEL_REP - 830 Field is referenced in object type &1, node &2, ODP &3, field &4
285 Message Number  ESH_OM_OBJ_MODEL_REP - 847 Ranking weight &1 does not exist
286 Message Number  ESH_OM_OBJ_MODEL_REP - 853 Node is used in object type &1, node &2, ODP &3, field &4
287 Message Number  ESH_OM_OBJ_MODEL_REP - 854 Node is referenced in NAF navigation path &1
288 Message Number  ESH_OM_OBJ_MODEL_REP - 855 Node is referenced in NAF navigation path &1, step &2
289 Message Number  ESH_OM_OBJ_MODEL_REP - 856 Relation is used in NAF navigation path &1, step &2
290 Message Number  ESH_OM_OBJ_MODEL_REP - 857 Relation is used in object type &1, node &2, ODP &3, field &4
291 Message Number  ESH_OM_OBJ_MODEL_REP - 861 Scheduling information cannot be set for real-time indexing
292 Message Number  ESH_OM_OBJ_MODEL_RP2 - 053 Flag "Based on BW Data Sources" cannot be changed
293 Message Number  ESH_OM_OBJ_MODEL_RP2 - 164 ODP is used in ODP field &4 of object type &1, node &2, ODP &3
294 Message Number  ESH_OM_OBJ_MODEL_RP2 - 176 Package &1 does not exist
295 Message Number  ESH_OM_OBJ_MODEL_RP2 - 204 Join operator &1 does not exist
296 Message Number  ESH_OM_OBJ_MODEL_RP2 - 223 Mapping role &1 does not exist
297 Message Number  ESH_OM_OBJ_MODEL_RP2 - 224 A composition must not have an association type
298 Message Number  ESH_OM_OBJ_MODEL_RP2 - 225 The composition links different object types
299 Message Number  ESH_OM_OBJ_MODEL_RP2 - 231 The relation is not a cross-system rel. but has cross-system references
300 Message Number  ESH_OM_OBJ_MODEL_RP2 - 235 Software comp. &1 is not a cross-system SWC or central cross-system SWC
301 Message Number  ESH_OM_OBJ_MODEL_RP2 - 238 Authorization type &1 does not exist
302 Message Number  ESH_OM_OBJ_MODEL_RP2 - 254 Model &1 is assigned to package $$TMP
303 Message Number  ESH_OM_OBJ_MODEL_RP2 - 255 Model &1 must not start with Y or Z
304 Message Number  ESH_OM_OBJ_MODEL_RP2 - 256 The request must be flagged for at least one usage
305 Message Number  ESH_OM_OBJ_MODEL_RP2 - 257 The request cannot be the default ODP request as it is not OPD-relevant
306 Message Number  ESH_OM_OBJ_MODEL_RP2 - 281 &1 is a reserved node field name
307 Message Number  ESH_OM_OBJ_MODEL_RP2 - 282 &1 is a reserved node field GUID
308 Message Number  ESH_OM_OBJ_MODEL_RP2 - 296 Request auto-tagging type &1 does not exist
309 Message Number  ESH_OM_OBJ_MODEL_RP2 - 339 Root node cannot be changed as object type is inherited from lower SWC
310 Message Number  ESH_OM_OBJ_MODEL_RP2 - 348 Connectors must be deleted, recreated and indexed in target systems
311 Message Number  ESH_OM_OBJ_MODEL_RP2 - 349 Renaming object tpye &1 may have impact on customer systems!
312 Message Number  ESH_OM_OBJ_MODEL_RP2 - 352 Auto completion cannot be set
313 Message Number  ESH_OM_OBJ_MODEL_RP2 - 386 Cannot delete response field
314 Message Number  ESH_OM_OBJ_MODEL_RP2 - 387 Response field is used in related perspective field mapping &1/&2/&3/&4
315 Message Number  ESH_OM_OBJ_MODEL_RP2 - 406 Mapping number for related request &1/&2/&3 is initial
316 Message Number  ESH_OM_OBJ_MODEL_RP2 - 407 The subquery flag only be set for UI technology &1
317 Message Number  ESH_OM_OBJ_MODEL_RP2 - 430 Response field is used in related request field mapping &1/&2/&3/&4
318 Message Number  ESH_OM_OBJ_MODEL_RP2 - 432 Request field is used in related request field mapping &1/&2/&3/&4
319 Message Number  ESH_OM_OBJ_MODEL_RP2 - 443 Request field is used in fixed values def. of related request &1/&2/&3/&4
320 Message Number  ESH_OM_OBJ_MODEL_RP2 - 470 Node name contains slashes that do not indicate a namespace
321 Message Number  ESH_OM_OBJ_MODEL_RP2 - 476 Flag "Contains Text" is ignored in connectors created on a HANA Data Base
322 Message Number  ESH_OM_OBJ_MODEL_RP2 - 494 Only business templates or virtual templates may have predecessors
323 Message Number  ESH_OM_OBJ_MODEL_RP2 - 495 Navigation id &1 must start with &2
324 Message Number  ESH_OM_OBJ_MODEL_RP2 - 496 Navigation id &1 must not start with &2
325 Message Number  ESH_OM_OBJ_MODEL_RP2 - 496 Navigation id &1 must not start with &2
326 Message Number  ESH_OM_OBJ_MODEL_RP2 - 501 Response field is used in backend navigation field ass. &1/&2/&3/&4
327 Message Number  ESH_OM_OBJ_MODEL_RP2 - 513 You cannot enter &1 because &1 is a reserved keyword
328 Message Number  ESH_OM_OBJ_MODEL_RP2 - 514 Key field &3 of node &2 of object type &1 cannot used in field mapping
329 Message Number  ESH_OM_OBJ_MODEL_RP2 - 515 Key field &4 cannot have semantics "Language Code"
330 Message Number  ESH_OM_OBJ_MODEL_RP2 - 516 Key field &4 cannot have semantics "Language Code"
331 Message Number  ESH_OM_OBJ_MODEL_RP2 - 517 Field &3 cannot be flagged to "Contain text"
332 Message Number  ESH_OM_OBJ_MODEL_RP2 - 518 Field &4 cannot be flagged to "Contain text"
333 Message Number  ESH_OM_OBJ_MODEL_RP2 - 531 Could not resolve GUID &1 (&2) - maybe SNOTE report missing
334 Message Number  ESH_OM_OBJ_MODEL_RP2 - 531 Could not resolve GUID &1 (&2) - maybe SNOTE report missing
335 Message Number  ESH_OM_OBJ_MODEL_RP2 - 531 Could not resolve GUID &1 (&2) - maybe SNOTE report missing
336 Message Number  ESH_OM_OBJ_MODEL_RP2 - 531 Could not resolve GUID &1 (&2) - maybe SNOTE report missing