Message Number list used by SAP ABAP Class CL_ESH_OM_OTYP_EXT_I (Object Types)
SAP ABAP Class CL_ESH_OM_OTYP_EXT_I (Object Types) is using
# Object Type Object Name Object Description Note
     
1 Message Number  ESH_OM_OBJ_MODEL_REP - 005 Object type &1 already exists
2 Message Number  ESH_OM_OBJ_MODEL_REP - 005 Object type &1 already exists
3 Message Number  ESH_OM_OBJ_MODEL_REP - 006 Object type &1 does not exist
4 Message Number  ESH_OM_OBJ_MODEL_REP - 021 Node &1 already exists
5 Message Number  ESH_OM_OBJ_MODEL_REP - 022 Node field &1 already exists
6 Message Number  ESH_OM_OBJ_MODEL_REP - 023 Alias &1 of response field already exists
7 Message Number  ESH_OM_OBJ_MODEL_REP - 024 Request &2 already exists
8 Message Number  ESH_OM_OBJ_MODEL_REP - 037 Request &1/&2/&3 is already assigned as a related request
9 Message Number  ESH_OM_OBJ_MODEL_REP - 038 Back-end navigation &1/&2 already exists
10 Message Number  ESH_OM_OBJ_MODEL_REP - 039 Object type &1, node &2, back-end navigation &3/&4:
11 Message Number  ESH_OM_OBJ_MODEL_REP - 040 Back-end navigation &1/&2/&3:
12 Message Number  ESH_OM_OBJ_MODEL_REP - 041 Response field &1, target parameter &2: Field assignment already exists
13 Message Number  ESH_OM_OBJ_MODEL_REP - 042 Node &1/&2 is already listed
14 Message Number  ESH_OM_OBJ_MODEL_REP - 043 Relation &1 already listed
15 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
16 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
17 Message Number  ESH_OM_OBJ_MODEL_REP - 044 Relation &1/&2 to &3/&4:
18 Message Number  ESH_OM_OBJ_MODEL_REP - 045 Navigation path (type &1) &2:
19 Message Number  ESH_OM_OBJ_MODEL_REP - 046 From node &1/&2 to &3/&4:
20 Message Number  ESH_OM_OBJ_MODEL_REP - 047 Step &1 already exists
21 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
22 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
23 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
24 Message Number  ESH_OM_OBJ_MODEL_REP - 073 Object type &1, node &2, field &3:
25 Message Number  ESH_OM_OBJ_MODEL_REP - 078 Object type &1, node &2, response field &3:
26 Message Number  ESH_OM_OBJ_MODEL_REP - 078 Object type &1, node &2, response field &3:
27 Message Number  ESH_OM_OBJ_MODEL_REP - 078 Object type &1, node &2, response field &3:
28 Message Number  ESH_OM_OBJ_MODEL_REP - 082 Relation &1 already exists
29 Message Number  ESH_OM_OBJ_MODEL_REP - 083 Object type &1, node &2, request &3:
30 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
31 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
32 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
33 Message Number  ESH_OM_OBJ_MODEL_REP - 084 Object type &1, node &2, request &3, field &4:
34 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
35 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
36 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
37 Message Number  ESH_OM_OBJ_MODEL_REP - 093 Relation ID &1:
38 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
39 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
40 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
41 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
42 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
43 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
44 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
45 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
46 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
47 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
48 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
49 Message Number  ESH_OM_OBJ_MODEL_REP - 103 Object type &1, node &2:
50 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
51 Message Number  ESH_OM_OBJ_MODEL_REP - 105 Object type &1:
52 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
53 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
54 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
55 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
56 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
57 Message Number  ESH_OM_OBJ_MODEL_REP - 106 Object type &1, node &2, request &3:
58 Message Number  ESH_OM_OBJ_MODEL_REP - 107 Alias &1 of request field already exists
59 Message Number  ESH_OM_OBJ_MODEL_REP - 115 Rel. requests for object type &1, node &2:
60 Message Number  ESH_OM_OBJ_MODEL_REP - 126 Object type &1, node &2, UI type &3, target navigation &4:
61 Message Number  ESH_OM_OBJ_MODEL_REP - 133 Navigation path &1:
62 Message Number  ESH_OM_OBJ_MODEL_REP - 192 Could not generate request ID for subquery navigation
63 Message Number  ESH_OM_OBJ_MODEL_REP - 192 Could not generate request ID for subquery navigation
64 Message Number  ESH_OM_OBJ_MODEL_REP - 200 Generating related request for object type &1, node &2:
65 Message Number  ESH_OM_OBJ_MODEL_REP - 201 Could not determine navigation path
66 Message Number  ESH_OM_OBJ_MODEL_REP - 223 Field is referenced in authorization check &1
67 Message Number  ESH_OM_OBJ_MODEL_REP - 257 More than one key field is flagged as a language field
68 Message Number  ESH_OM_OBJ_MODEL_REP - 257 More than one key field is flagged as a language field
69 Message Number  ESH_OM_OBJ_MODEL_REP - 263 There must be exactly one default request
70 Message Number  ESH_OM_OBJ_MODEL_REP - 264 One request must be flagged as the default request
71 Message Number  ESH_OM_OBJ_MODEL_REP - 264 One request must be flagged as the default request
72 Message Number  ESH_OM_OBJ_MODEL_REP - 265 There must be at least one key field in node &1
73 Message Number  ESH_OM_OBJ_MODEL_REP - 265 There must be at least one key field in node &1
74 Message Number  ESH_OM_OBJ_MODEL_REP - 266 Category &1 is already assigned
75 Message Number  ESH_OM_OBJ_MODEL_REP - 268 Node &1 has no parent node
76 Message Number  ESH_OM_OBJ_MODEL_REP - 269 Node has more than one parent node
77 Message Number  ESH_OM_OBJ_MODEL_REP - 270 Composition of different business objects
78 Message Number  ESH_OM_OBJ_MODEL_REP - 290 There is a field with the same name as the alias &1
79 Message Number  ESH_OM_OBJ_MODEL_REP - 291 There is an alias with the same name as field &1
80 Message Number  ESH_OM_OBJ_MODEL_REP - 307 Node fields &1 and &2 have the same description in language &3
81 Message Number  ESH_OM_OBJ_MODEL_REP - 329 Response fields &1 and &2 refer to the same node field
82 Message Number  ESH_OM_OBJ_MODEL_REP - 329 Response fields &1 and &2 refer to the same node field
83 Message Number  ESH_OM_OBJ_MODEL_REP - 347 Assignment to UI area &1 already exists
84 Message Number  ESH_OM_OBJ_MODEL_REP - 349 Object type &1, node &2, response field &3 does not exist
85 Message Number  ESH_OM_OBJ_MODEL_REP - 349 Object type &1, node &2, response field &3 does not exist
86 Message Number  ESH_OM_OBJ_MODEL_REP - 354 Role type &1, role &1 is already assigned to the node
87 Message Number  ESH_OM_OBJ_MODEL_REP - 371 Object type &1, category &2:
88 Message Number  ESH_OM_OBJ_MODEL_REP - 379 End node of navigation path differs from to-node of previous step
89 Message Number  ESH_OM_OBJ_MODEL_REP - 380 Request fields &1 and &2 refer to the same node field
90 Message Number  ESH_OM_OBJ_MODEL_REP - 380 Request fields &1 and &2 refer to the same node field
91 Message Number  ESH_OM_OBJ_MODEL_REP - 382 The field is text-search-relevant and used in the following relations:
92 Message Number  ESH_OM_OBJ_MODEL_REP - 383 Request has been activated
93 Message Number  ESH_OM_OBJ_MODEL_REP - 384 Request has been deactivated
94 Message Number  ESH_OM_OBJ_MODEL_REP - 390 Start-node of navigation path differs from from-node of first step
95 Message Number  ESH_OM_OBJ_MODEL_REP - 391 Response field &1 of URL in target operation does not exist
96 Message Number  ESH_OM_OBJ_MODEL_REP - 392 URL contains no reference to a response field
97 Message Number  ESH_OM_OBJ_MODEL_REP - 419 To-node of step &1 and from-node of step &2 are different
98 Message Number  ESH_OM_OBJ_MODEL_REP - 480 Response fields &1 and &2 have the same description in language &3
99 Message Number  ESH_OM_OBJ_MODEL_REP - 481 Request fields &1 and &2 have the same description in language &3
100 Message Number  ESH_OM_OBJ_MODEL_REP - 483 More than one navigation ID is flagged to be the object link
101 Message Number  ESH_OM_OBJ_MODEL_REP - 483 More than one navigation ID is flagged to be the object link
102 Message Number  ESH_OM_OBJ_MODEL_REP - 488 Authorization check &1:
103 Message Number  ESH_OM_OBJ_MODEL_REP - 488 Authorization check &1:
104 Message Number  ESH_OM_OBJ_MODEL_REP - 491 Assignment of authorization check &3 to object type &1, node &2:
105 Message Number  ESH_OM_OBJ_MODEL_REP - 491 Assignment of authorization check &3 to object type &1, node &2:
106 Message Number  ESH_OM_OBJ_MODEL_REP - 492 There is already an assignment to authorization check &1
107 Message Number  ESH_OM_OBJ_MODEL_REP - 522 There is already a relation to navigation path &1
108 Message Number  ESH_OM_OBJ_MODEL_REP - 529 There is already a part of a logical conjunction with type &1, counter &2
109 Message Number  ESH_OM_OBJ_MODEL_REP - 531 Logical conjunction to object type &1, node &2: syntax error
110 Message Number  ESH_OM_OBJ_MODEL_REP - 532 &1 is not an operator, bracket, or authorization check
111 Message Number  ESH_OM_OBJ_MODEL_REP - 533 Logical conjunction must not start with &1
112 Message Number  ESH_OM_OBJ_MODEL_REP - 534 &1 or authorization check followed by &2
113 Message Number  ESH_OM_OBJ_MODEL_REP - 535 &1 is not preceeded by &2 or authorization check
114 Message Number  ESH_OM_OBJ_MODEL_REP - 536 &1 is not preceeded by &2 or authorization check
115 Message Number  ESH_OM_OBJ_MODEL_REP - 537 &1 is preceeded by &1 or authorization check
116 Message Number  ESH_OM_OBJ_MODEL_REP - 538 Authorization check is preceeded by &1 or another authorization check
117 Message Number  ESH_OM_OBJ_MODEL_REP - 539 Parenthesis unbalanced
118 Message Number  ESH_OM_OBJ_MODEL_REP - 545 Not all authorization checks are listed in logical conjunction
119 Message Number  ESH_OM_OBJ_MODEL_REP - 545 Not all authorization checks are listed in logical conjunction
120 Message Number  ESH_OM_OBJ_MODEL_REP - 546 Relation to authorization check &3
121 Message Number  ESH_OM_OBJ_MODEL_REP - 564 There must be no more than one field of type "Date to"
122 Message Number  ESH_OM_OBJ_MODEL_REP - 564 There must be no more than one field of type "Date to"
123 Message Number  ESH_OM_OBJ_MODEL_REP - 565 There must be no more than one field of type "Date from"
124 Message Number  ESH_OM_OBJ_MODEL_REP - 566 Invalid relation used in NRF navigation path
125 Message Number  ESH_OM_OBJ_MODEL_REP - 597 Technical/Authorization object has request &1 at node &2
126 Message Number  ESH_OM_OBJ_MODEL_REP - 598 Technical/Authorization object has response field &1 at node &2
127 Message Number  ESH_OM_OBJ_MODEL_REP - 599 In technical/authorization object, subnode &1 is flagged 'subquery'
128 Message Number  ESH_OM_OBJ_MODEL_REP - 601 Relation &1 has no field mapping and no fixed values
129 Message Number  ESH_OM_OBJ_MODEL_REP - 603 Logical conjunction to object type &1, node &2:
130 Message Number  ESH_OM_OBJ_MODEL_REP - 604 Part of logical conjunction inherited from underlying SWC was changed
131 Message Number  ESH_OM_OBJ_MODEL_REP - 605 Target attribute &1 is not a field of the target node &2
132 Message Number  ESH_OM_OBJ_MODEL_REP - 606 Source attribute &1 is not a field of the source node &2
133 Message Number  ESH_OM_OBJ_MODEL_REP - 607 Default request cannot be changed because it is inherited
134 Message Number  ESH_OM_OBJ_MODEL_REP - 614 Relation does not fit the path of the auth. field
135 Message Number  ESH_OM_OBJ_MODEL_REP - 615 Relation does not fit the path of the check
136 Message Number  ESH_OM_OBJ_MODEL_REP - 617 Relation from node to first node of path of check not defined
137 Message Number  ESH_OM_OBJ_MODEL_REP - 618 Useless relation to start of the path of check specified
138 Message Number  ESH_OM_OBJ_MODEL_REP - 619 Useless relation to start of the path of auth. field specified
139 Message Number  ESH_OM_OBJ_MODEL_REP - 620 Relation from node to first node of path of auth. field not defined
140 Message Number  ESH_OM_OBJ_MODEL_REP - 621 No navigation path specified leading to the node field referenced
141 Message Number  ESH_OM_OBJ_MODEL_REP - 623 No navigation path specified leading to the node field referenced
142 Message Number  ESH_OM_OBJ_MODEL_REP - 625 Navigation path does not fit to node of request and referenced node field
143 Message Number  ESH_OM_OBJ_MODEL_REP - 626 Navigation path does not fit to response field and referenced node field
144 Message Number  ESH_OM_OBJ_MODEL_REP - 627 Navigation path has no steps
145 Message Number  ESH_OM_OBJ_MODEL_REP - 629 The following checks are missing
146 Message Number  ESH_OM_OBJ_MODEL_REP - 629 The following checks are missing
147 Message Number  ESH_OM_OBJ_MODEL_REP - 645 Field name &1 not possible due to indexing restrictions
148 Message Number  ESH_OM_OBJ_MODEL_REP - 658 Virtual model must only have a root node
149 Message Number  ESH_OM_OBJ_MODEL_REP - 659 Virtual model has more than one relation
150 Message Number  ESH_OM_OBJ_MODEL_REP - 660 Virtual model has no relation to referenced model
151 Message Number  ESH_OM_OBJ_MODEL_REP - 661 Type of association from virtual to referenced model must be &1
152 Message Number  ESH_OM_OBJ_MODEL_REP - 662 Relation does not fit to virtual model and referenced model
153 Message Number  ESH_OM_OBJ_MODEL_REP - 663 Root node of virtual models must only have key fields
154 Message Number  ESH_OM_OBJ_MODEL_REP - 665 Relation between virtual model and referenced model must be 1:1
155 Message Number  ESH_OM_OBJ_MODEL_REP - 666 No referenced model spefied for virtual model
156 Message Number  ESH_OM_OBJ_MODEL_REP - 667 Virtual model &1:
157 Message Number  ESH_OM_OBJ_MODEL_REP - 668 Path is used in authorization but references relation of virtual model
158 Message Number  ESH_OM_OBJ_MODEL_REP - 669 Regenerating related request for object type &1, node &2:
159 Message Number  ESH_OM_OBJ_MODEL_REP - 669 Regenerating related request for object type &1, node &2:
160 Message Number  ESH_OM_OBJ_MODEL_REP - 670 Request belongs to foreign software component, regeneration not possible
161 Message Number  ESH_OM_OBJ_MODEL_REP - 670 Request belongs to foreign software component, regeneration not possible
162 Message Number  ESH_OM_OBJ_MODEL_REP - 672 Node field is used in authorization check &1 that has value &2
163 Message Number  ESH_OM_OBJ_MODEL_REP - 712 Node field is not referenced in a request field
164 Message Number  ESH_OM_OBJ_MODEL_REP - 713 Request field references node field flagged for interactive navigation
165 Message Number  ESH_OM_OBJ_MODEL_REP - 713 Request field references node field flagged for interactive navigation
166 Message Number  ESH_OM_OBJ_MODEL_REP - 733 Virtual model must have a root node
167 Message Number  ESH_OM_OBJ_MODEL_REP - 745 Back-end navigation has no description
168 Message Number  ESH_OM_OBJ_MODEL_REP - 748 There is more than one response attribute with UI area "Detail image"
169 Message Number  ESH_OM_OBJ_MODEL_REP - 749 There are more than nine response attributes with UI area "Summary"
170 Message Number  ESH_OM_OBJ_MODEL_REP - 750 There is more than one response attribute with UI area "Thumbnail"
171 Message Number  ESH_OM_OBJ_MODEL_REP - 760 Back-end name of object type &1, node &2, response field &3:
172 Message Number  ESH_OM_OBJ_MODEL_REP - 761 Back-end name of object type &1, node &2, request &3, field &4:
173 Message Number  ESH_OM_OBJ_MODEL_REP - 764 Category &1 cannot be assigned to model &3 of SWC &2
174 Message Number  ESH_OM_OBJ_MODEL_REP - 765 Category &1 cannot be assigned to model &3 of SWC &2
175 Message Number  ESH_OM_OBJ_MODEL_REP - 802 The request field cannot have the same name as response field &4
176 Message Number  ESH_OM_OBJ_MODEL_REP - 804 The response field cannot have the same name as field &4 of request &3
177 Message Number  ESH_OM_OBJ_MODEL_REP - 808 Object type &2, node &3, field &4 is switched off
178 Message Number  ESH_OM_OBJ_MODEL_REP - 809 Object type &2, node &3 is switched off
179 Message Number  ESH_OM_OBJ_MODEL_REP - 810 Association &2 is switched off
180 Message Number  ESH_OM_OBJ_MODEL_REP - 811 Composition from node &3 to node &4 in object type &2 is switched off
181 Message Number  ESH_OM_OBJ_MODEL_REP - 812 Object type &1, node &2, ODP ID &3, ODP semantics &4:
182 Message Number  ESH_OM_OBJ_MODEL_REP - 858 Object type &1, node &2, node attribute group &3 using group &4
183 Message Number  ESH_OM_OBJ_MODEL_RP2 - 031 Only one field can have semantics "Searchable file"
184 Message Number  ESH_OM_OBJ_MODEL_RP2 - 037 Node &1 has fields with the same description
185 Message Number  ESH_OM_OBJ_MODEL_RP2 - 038 Node &1 has response fields with the same description
186 Message Number  ESH_OM_OBJ_MODEL_RP2 - 039 Request &1 has fields with the same description
187 Message Number  ESH_OM_OBJ_MODEL_RP2 - 041 Field with semantic "Searchable File" must be of type RSTR (RAWSTRING)
188 Message Number  ESH_OM_OBJ_MODEL_RP2 - 044 Node &1 has no field with semantic "MIME Type"
189 Message Number  ESH_OM_OBJ_MODEL_RP2 - 045 Node &1 has an unpaired field with semantic "MIME Type"
190 Message Number  ESH_OM_OBJ_MODEL_RP2 - 046 Node &1 has no field with semantic "MIME Type"
191 Message Number  ESH_OM_OBJ_MODEL_RP2 - 054 Node &1 should not have response fields with UI area assignments
192 Message Number  ESH_OM_OBJ_MODEL_RP2 - 083 Request &1 has fields with assignments to common attributes
193 Message Number  ESH_OM_OBJ_MODEL_RP2 - 083 Request &1 has fields with assignments to common attributes
194 Message Number  ESH_OM_OBJ_MODEL_RP2 - 092 Request &3 of object type &1, node &2 is not a rational related request
195 Message Number  ESH_OM_OBJ_MODEL_RP2 - 093 Node &1 does not contain the necessary response fields for navigation
196 Message Number  ESH_OM_OBJ_MODEL_RP2 - 170 Error when creating hash code for effective authorization checks
197 Message Number  ESH_OM_OBJ_MODEL_RP2 - 181 Node field cannot contain text as it is used in authorization checks
198 Message Number  ESH_OM_OBJ_MODEL_RP2 - 196 More than one field of request &1 is assigned to common attribute &2
199 Message Number  ESH_OM_OBJ_MODEL_RP2 - 199 Request is used in object type &1, node &2, ODP &3, field &4
200 Message Number  ESH_OM_OBJ_MODEL_RP2 - 205 A relation already exists between node field &1 and &2
201 Message Number  ESH_OM_OBJ_MODEL_RP2 - 206 The relation has no field assignment with join operator '=' (equal)
202 Message Number  ESH_OM_OBJ_MODEL_RP2 - 231 The relation is not a cross-system rel. but has cross-system references
203 Message Number  ESH_OM_OBJ_MODEL_RP2 - 232 Field &1 of fixed value defintion is no field of source or target node
204 Message Number  ESH_OM_OBJ_MODEL_RP2 - 239 Logical conjunctions to object type &1, node &2: syntax error
205 Message Number  ESH_OM_OBJ_MODEL_RP2 - 251 Not all authorization checks are listed in logical conjunction (type &1)
206 Message Number  ESH_OM_OBJ_MODEL_RP2 - 258 There must be exactly one default ODP request
207 Message Number  ESH_OM_OBJ_MODEL_RP2 - 259 You cannot change the default ODP request because it is inherited
208 Message Number  ESH_OM_OBJ_MODEL_RP2 - 260 There are requests relevant for ODP but none of these is set as default
209 Message Number  ESH_OM_OBJ_MODEL_RP2 - 261 Field with semantic "Content URL" must be of type STRG (STRING)
210 Message Number  ESH_OM_OBJ_MODEL_RP2 - 297 Node &2 cannot be enhanced with key attributes in software component &4
211 Message Number  ESH_OM_OBJ_MODEL_RP2 - 312 More than one request is flagged as default request
212 Message Number  ESH_OM_OBJ_MODEL_RP2 - 318 OPD field &1 and OPD field &2 refer to the same node field
213 Message Number  ESH_OM_OBJ_MODEL_RP2 - 320 Reverse/source cardinality does not fit to foreign key definitions
214 Message Number  ESH_OM_OBJ_MODEL_RP2 - 321 Cardinality/target cardinality does not fit to foreign key definitions
215 Message Number  ESH_OM_OBJ_MODEL_RP2 - 322 Cardinality does not fit to foreign key definitions for search
216 Message Number  ESH_OM_OBJ_MODEL_RP2 - 323 Cardinality does not fit to foreign key definitions for search
217 Message Number  ESH_OM_OBJ_MODEL_RP2 - 324 Cardinality does not fit to foreign key definitions
218 Message Number  ESH_OM_OBJ_MODEL_RP2 - 325 Cardinality does not fit to foreign key definitions for search
219 Message Number  ESH_OM_OBJ_MODEL_RP2 - 338 There are more than two response attributes with UI area "Longtext"
220 Message Number  ESH_OM_OBJ_MODEL_RP2 - 340 Request fields have been removed
221 Message Number  ESH_OM_OBJ_MODEL_RP2 - 346 Node &2 references another node but object type &1 is not virtual
222 Message Number  ESH_OM_OBJ_MODEL_RP2 - 347 ODP ID &1, semantic &2, has been renamed to ODP ID &3, semantic &4
223 Message Number  ESH_OM_OBJ_MODEL_RP2 - 352 Auto completion cannot be set
224 Message Number  ESH_OM_OBJ_MODEL_RP2 - 370 Layout template cannot be created because node &2 has no response fields
225 Message Number  ESH_OM_OBJ_MODEL_RP2 - 424 Related request field mapping &1/&2/&3/&4;
226 Message Number  ESH_OM_OBJ_MODEL_RP2 - 442 Related request field &1/&2/&3/&4 is already given fixed values
227 Message Number  ESH_OM_OBJ_MODEL_RP2 - 471 No field of the default request is flagged for freestyle search
228 Message Number  ESH_OM_OBJ_MODEL_RP2 - 472 The root node must not have a parent node
229 Message Number  ESH_OM_OBJ_MODEL_RP2 - 480 Node &2 has no response fields but is flagged for subquery
230 Message Number  ESH_OM_OBJ_MODEL_RP2 - 509 Field &3 of node &2 of object type &1 must be flagged to contain text
231 Message Number  ESH_OM_OBJ_MODEL_RP2 - 526 Default request does not reference key field &3 (object type &1, node &2)
232 Message Number  ESH_OM_OBJ_MODEL_RP2 - 527 Field &3 of node &2 is not referenced in a response field node &2
233 Message Number  ESH_OM_OBJ_MODEL_RP2 - 528 Default request does not reference all key fields of node &2