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