# |
Message |
Message Short Text |
Documentation status |
Authorization check |
1 |
000 |
* Comments on this message class **************************************** |
|
|
2 |
020 |
* Do not use ************************************************************ |
|
|
3 |
100 |
* General messages ****************************************************** |
|
|
4 |
101 |
Data for mode-dependent tagging was determined |
The short text describes the object sufficiently |
|
5 |
102 |
Data for mode-dependent tagging has been deleted |
The short text describes the object sufficiently |
|
6 |
103 |
In maintenance planning plant &1, overall condition &2 is not defined |
The short text describes the object sufficiently |
|
7 |
104 |
Date & is in the past |
|
|
8 |
105 |
Enter either functional location or equipment |
Space: object requires documentation |
|
9 |
106 |
Execute the function later |
The short text describes the object sufficiently |
|
10 |
107 |
This entry has already been assigned |
|
|
11 |
108 |
This entry has already been deleted |
|
|
12 |
109 |
The assignment has not been made |
|
|
13 |
110 |
No & are assigned |
Space: object requires documentation |
|
14 |
111 |
This is the wrong direction |
Space: object requires documentation |
|
15 |
112 |
You cannot assign & |
Space: object requires documentation |
|
16 |
113 |
Assignments already exist |
Space: object requires documentation |
|
17 |
114 |
Assignments do not exist |
Space: object requires documentation |
|
18 |
115 |
&1 &2 is before &3 &4 |
Space: object requires documentation |
|
19 |
116 |
The &1 &2 with print format &3 was copied |
Space: object requires documentation |
|
20 |
117 |
The profile in maintenance planning plant &1 was adjusted |
Space: object requires documentation |
|
21 |
118 |
Plant & does not exist |
|
|
22 |
119 |
Maintenance planning plant & does not exist |
|
|
23 |
120 |
Maintenance plant &1 does not support maintenance planner group &2 |
Space: object requires documentation |
|
24 |
121 |
Plant &1 does not support location &2 |
Space: object requires documentation |
|
25 |
122 |
Maintenance plant &1 does not support plant section &2 |
Space: object requires documentation |
|
26 |
123 |
Check whether the data is valid for the new reference object |
Space: object requires documentation |
|
27 |
124 |
The reference object and object list cannot be copied |
Space: object requires documentation |
|
28 |
125 |
Perform Identification |
Space: object requires documentation |
|
29 |
126 |
Number & does not lie within external number range interval |
Space: object requires documentation |
|
30 |
127 |
&2 was created for maintenance planning plant &1 |
The short text describes the object sufficiently |
|
31 |
128 |
Functional location &1 belongs to maintenance planning plant &2 |
Space: object requires documentation |
|
32 |
129 |
Equipment &1 belongs to maintenance planning plant &2 |
Space: object requires documentation |
|
33 |
130 |
&1 &2 is flagged for deletion |
Space: object requires documentation |
|
34 |
131 |
&1 &2 is inactive |
Space: object requires documentation |
|
35 |
132 |
The maintenance planning plants are different |
Space: object requires documentation |
|
36 |
133 |
Long text was changed, you cannot cancel |
Space: object requires documentation |
|
37 |
134 |
Define a valid view |
Space: object requires documentation |
|
38 |
135 |
& already exists |
Space: object requires documentation |
|
39 |
136 |
Deselect work approval indicator |
Space: object requires documentation |
|
40 |
137 |
User & is locked |
Space: object requires documentation |
|
41 |
138 |
Operational list was created with the number & |
The short text describes the object sufficiently |
|
42 |
139 |
Operational list was printed |
The short text describes the object sufficiently |
|
43 |
140 |
&1 was printed |
The short text describes the object sufficiently |
|
44 |
141 |
An item was selected |
The short text describes the object sufficiently |
|
45 |
142 |
& items were selected |
The short text describes the object sufficiently |
|
46 |
143 |
Approval group is already assigned |
The short text describes the object sufficiently |
|
47 |
144 |
You cannot assign any more & |
Space: object requires documentation |
|
48 |
145 |
&1 &2 was closed |
The short text describes the object sufficiently |
|
49 |
146 |
&1 &2 was rejected |
The short text describes the object sufficiently |
|
50 |
147 |
Release for execution has been issued for order & |
The short text describes the object sufficiently |
|
51 |
148 |
No entry available |
|
|
52 |
149 |
Nearly all numbers are assigned for object & in internal number range |
Space: object requires documentation |
|
53 |
150 |
Last number was assigned for object & in internal number range |
Space: object requires documentation |
|
54 |
151 |
For & you need the internal number assignment |
The short text describes the object sufficiently |
|
55 |
152 |
Release for execution has been issued for WCM-relevant operation & |
The short text describes the object sufficiently |
|
56 |
153 |
Date & lies too far in the future |
|
|
57 |
154 |
One entry corresponded to the selection conditions |
Space: object requires documentation |
|
58 |
155 |
Enter a valid object |
Space: object requires documentation |
|
59 |
156 |
You can only assign &1 &2 |
Space: object requires documentation |
|
60 |
157 |
&1 &2 were assigned |
Space: object requires documentation |
|
61 |
158 |
No & satisfy the selection criteria |
Space: object requires documentation |
|
62 |
159 |
Invalid selection |
Space: object requires documentation |
|
63 |
160 |
Invalid cursor position |
|
|
64 |
161 |
Nothing was changed |
Space: object requires documentation |
|
65 |
162 |
You can only assign one & |
Space: object requires documentation |
|
66 |
163 |
You cannot reset date and time (&1 &2) |
Space: object requires documentation |
|
67 |
164 |
Enter an approval group |
The short text describes the object sufficiently |
|
68 |
165 |
Data cannot be copied |
Space: object requires documentation |
|
69 |
166 |
Enter a reference object |
Space: object requires documentation |
|
70 |
167 |
You cannot create the WCM object (&) directly |
Space: object requires documentation |
|
71 |
168 |
You cannot change the WCM object (&) directly |
Space: object requires documentation |
|
72 |
169 |
You cannot use the &1 &2 as a template |
Space: object requires documentation |
|
73 |
170 |
& assignments were deleted |
Space: object requires documentation |
|
74 |
171 |
Not all subordinate approvals are issued |
Space: object requires documentation |
|
75 |
172 |
Work for order & has been completed |
The short text describes the object sufficiently |
|
76 |
173 |
Work for WCM-relevant operation & has been completed |
The short text describes the object sufficiently |
|
77 |
174 |
Work for WCM-relevant operation & has not been completed |
The short text describes the object sufficiently |
|
78 |
175 |
Release for execution for WCM-relevant operation & has not been issued |
The short text describes the object sufficiently |
|
79 |
176 |
Incorrect master data for mode-dependent tagging |
Space: object requires documentation |
|
80 |
177 |
Incomplete master data for mode-dependent tagging |
Space: object requires documentation |
|
81 |
178 |
Maximum number of parameters permitted is 10 |
Space: object requires documentation |
|
82 |
179 |
Feature of authorization or calling up AUTHORITY CHECK is incorrect |
Space: object requires documentation |
|
83 |
180 |
You cannot delete approval & |
Space: object requires documentation |
|
84 |
181 |
You have no authorization for & |
Space: object requires documentation |
|
85 |
182 |
Approval & is missing for switching |
Space: object requires documentation |
|
86 |
183 |
You cannot deactivate the item |
Space: object requires documentation |
|
87 |
184 |
The changes have been saved |
|
|
88 |
185 |
Enter a technical object, which is not of type & |
Space: object requires documentation |
|
89 |
186 |
Enter a reason for rejecting the WCM object |
Space: object requires documentation |
|
90 |
187 |
First end the lockout/tagout |
Space: object requires documentation |
|
91 |
188 |
Maintain the obligatory roles for the assigned partner profile |
Space: object requires documentation |
|
92 |
189 |
Select one valid entry only |
Space: object requires documentation |
|
93 |
190 |
Enter the time |
Space: object requires documentation |
|
94 |
191 |
Enter the unit |
Space: object requires documentation |
|
95 |
192 |
Enter the operational group |
Space: object requires documentation |
|
96 |
193 |
Enter the tagging condition |
Space: object requires documentation |
|
97 |
194 |
Clipboard is empty |
Space: object requires documentation |
|
98 |
195 |
& items have been inserted |
Space: object requires documentation |
|
99 |
196 |
One item has been inserted |
Space: object requires documentation |
|
100 |
197 |
Data has been saved |
Space: object requires documentation |
|
101 |
198 |
Select a maximum of one entry |
Space: object requires documentation |
|
102 |
199 |
Approvals were issued/revoked automatically |
Space: object requires documentation |
|
103 |
200 |
&1 &2 does not exist |
Space: object requires documentation |
|
104 |
201 |
& items were adjusted |
The short text describes the object sufficiently |
|
105 |
202 |
& does not exist |
Space: object requires documentation |
|
106 |
203 |
&1 &2 was assigned |
The short text describes the object sufficiently |
|
107 |
204 |
&1 &2 already exists |
Space: object requires documentation |
|
108 |
205 |
One item was adjusted |
The short text describes the object sufficiently |
|
109 |
206 |
&1 is not a &2 |
Space: object requires documentation |
|
110 |
207 |
&1 was saved with number &2 |
Space: object requires documentation |
|
111 |
208 |
Check the item |
Space: object requires documentation |
|
112 |
209 |
Enter the type of technical object |
Space: object requires documentation |
|
113 |
210 |
Enter the technical object |
Space: object requires documentation |
|
114 |
211 |
Data was saved |
Space: object requires documentation |
|
115 |
212 |
Enter the tag print format |
Space: object requires documentation |
|
116 |
213 |
Select two valid entries |
Space: object requires documentation |
|
117 |
214 |
Select a second valid entry |
Space: object requires documentation |
|
118 |
215 |
In op. group &1, op. condition &2 is not allowed for &3 &4 |
Space: object requires documentation |
|
119 |
216 |
One item was added to the clipboard |
Space: object requires documentation |
|
120 |
217 |
One item was copied to the clipboard |
Space: object requires documentation |
|
121 |
218 |
& items were added to the clipboard |
Space: object requires documentation |
|
122 |
219 |
& items were copied to the clipboard |
Space: object requires documentation |
|
123 |
220 |
The function is not permitted |
Space: object requires documentation |
|
124 |
221 |
Clipboard is deleted |
Space: object requires documentation |
|
125 |
222 |
Select field: Tag required |
Space: object requires documentation |
|
126 |
223 |
Type & is not permitted |
|
|
127 |
224 |
&1 are the same |
Space: object requires documentation |
|
128 |
225 |
No required approvals found |
Space: object requires documentation |
|
129 |
226 |
& parameter is blank |
Space: object requires documentation |
|
130 |
227 |
& approval is assigned to the WCM object |
Space: object requires documentation |
|
131 |
228 |
&4 are not the same |
Space: object requires documentation |
|
132 |
229 |
&4 was changed |
Space: object requires documentation |
|
133 |
230 |
Function is not available |
Space: object requires documentation |
|
134 |
231 |
Select at least one valid entry |
Space: object requires documentation |
|
135 |
232 |
Before issuing the approval, set the status & (&) |
Space: object requires documentation |
|
136 |
233 |
Check completed successfully |
|
|
137 |
234 |
Combination of print format &1 and print category &2 is not permitted |
Space: object requires documentation |
|
138 |
235 |
&1 was not changed |
Space: object requires documentation |
|
139 |
236 |
This entry is not allowed |
The short text describes the object sufficiently |
|
140 |
237 |
WCM has not been released |
Space: object requires documentation |
|
141 |
238 |
You cannot assign any approvals |
Space: object requires documentation |
|
142 |
239 |
WCM object doesn't exist in this maintenance planning plant & |
Space: object requires documentation |
|
143 |
240 |
This is not a transaction for & |
Space: object requires documentation |
|
144 |
241 |
Deletion indicator was saved in the database |
|
|
145 |
242 |
Reorganization run completed successfully |
|
|
146 |
243 |
Errors occurred during reorganization run |
|
|
147 |
244 |
No changes were made to database |
Space: object requires documentation |
|
148 |
245 |
Navigation not permitted |
Space: object requires documentation |
|
149 |
246 |
Maintenance planning plant & not permitted |
Space: object requires documentation |
|
150 |
247 |
External number assignment not permitted |
Space: object requires documentation |
|
151 |
248 |
You can only change WCM object (&) directly |
Space: object requires documentation |
|
152 |
249 |
You can only create WCM object (&) directly |
Space: object requires documentation |
|
153 |
250 |
You cannot select a & |
Space: object requires documentation |
|
154 |
251 |
Data has been changed |
The short text describes the object sufficiently |
|
155 |
252 |
Data was deleted |
Space: object requires documentation |
|
156 |
253 |
You cannot delete type & |
Space: object requires documentation |
|
157 |
254 |
No more applications possible in the standard model |
Space: object requires documentation |
|
158 |
255 |
Type & already exists |
Space: object requires documentation |
|
159 |
256 |
Type & does not exist |
Space: object requires documentation |
|
160 |
257 |
Entry &1 &2 &3 could not be locked. |
The short text describes the object sufficiently |
|
161 |
258 |
No processing for entry &1 &2 &3 |
The short text describes the object sufficiently |
|
162 |
259 |
Error in BAdI implementation |
Space: object requires documentation |
|
163 |
260 |
No further overall conditions exist |
The short text describes the object sufficiently |
|
164 |
261 |
No further operational conditions exist |
The short text describes the object sufficiently |
|
165 |
262 |
No further operational types exist |
The short text describes the object sufficiently |
|
166 |
263 |
Entries that are flagged for deletion cannot be changed |
The short text describes the object sufficiently |
|
167 |
264 |
Data could not be saved |
Space: object requires documentation |
|
168 |
265 |
No protected area exists |
The short text describes the object sufficiently |
|
169 |
266 |
You have planned too few checks |
The short text describes the object sufficiently |
|
170 |
267 |
Enter a reason for your rejection of the lineup |
The short text describes the object sufficiently |
|
171 |
268 |
Select an entry |
The short text describes the object sufficiently |
|
172 |
269 |
Enter a reason for your rejection of the verification list |
The short text describes the object sufficiently |
|
173 |
270 |
Enter the planned number of checks |
The short text describes the object sufficiently |
|
174 |
271 |
& items confirmed |
The short text describes the object sufficiently |
|
175 |
272 |
One item confirmed |
The short text describes the object sufficiently |
|
176 |
273 |
Enter Notes on Subject |
The short text describes the object sufficiently |
|
177 |
274 |
Enter the operational condition |
The short text describes the object sufficiently |
|
178 |
275 |
Enter Operational Type |
The short text describes the object sufficiently |
|
179 |
276 |
Enter Tagging Type |
The short text describes the object sufficiently |
|
180 |
277 |
Operational condition &1 is not permitted |
The short text describes the object sufficiently |
|
181 |
278 |
Operational type &1 is not permitted |
The short text describes the object sufficiently |
|
182 |
279 |
Operational group &1 is not permitted |
The short text describes the object sufficiently |
|
183 |
280 |
Status &1 (&2) was set |
The short text describes the object sufficiently |
|
184 |
281 |
Status &1 (&2) was revoked |
The short text describes the object sufficiently |
|
185 |
282 |
You must assign operational steps to each item |
The short text describes the object sufficiently |
|
186 |
283 |
Operational step &1 is not allowed for tagging |
Space: object requires documentation |
|
187 |
284 |
Operational step &1 is not allowed for untagging |
Space: object requires documentation |
|
188 |
285 |
Operational steps were created automatically |
The short text describes the object sufficiently |
|
189 |
286 |
Operational step &1 is no longer allowed for tagging |
Space: object requires documentation |
|
190 |
287 |
Operational step &1 is no longer allowed for untagging |
Space: object requires documentation |
|
191 |
288 |
Release for execution for WCM-relevant operation &1 is already assigned |
The short text describes the object sufficiently |
|
192 |
289 |
WCM-relevant operation &1 is already assigned to an approval group |
The short text describes the object sufficiently |
|
193 |
290 |
WCM-relevant operation &1 is already assigned to one &2 |
The short text describes the object sufficiently |
|
194 |
291 |
WCM-relevant operation &1 is already assigned to an operational step |
The short text describes the object sufficiently |
|
195 |
292 |
WCM-relevant operation &1 is not assigned to an approval group |
The short text describes the object sufficiently |
|
196 |
293 |
WCM-relevant operation &1 is not assigned to any &2 |
The short text describes the object sufficiently |
|
197 |
294 |
WCM-relevant operation &1 is not assigned to an operational step |
The short text describes the object sufficiently |
|
198 |
295 |
Approval group &1 is already assigned to WCM-relevant operation &2 |
The short text describes the object sufficiently |
|
199 |
296 |
&1 &2 is already assigned to WCM-relevant operation &3 |
The short text describes the object sufficiently |
|
200 |
297 |
Operational step &1 (&2 &3) is already assigned to WCM-relevant oper. &4 |
The short text describes the object sufficiently |
|
201 |
298 |
Status of operational step &1 prevents revoking of the assignment |
The short text describes the object sufficiently |
|
202 |
299 |
Status of &1 &2 prevents revoking of the assignment |
The short text describes the object sufficiently |
|
203 |
300 |
Status of &1 &2 prevents assignment |
The short text describes the object sufficiently |
|
204 |
301 |
Status of operational step &1 prevents assignment |
The short text describes the object sufficiently |
|
205 |
302 |
An approval was assigned automatically |
The short text describes the object sufficiently |
|
206 |
303 |
&1 approvals were assigned automatically |
The short text describes the object sufficiently |
|
207 |
304 |
Tag &1 has been deleted |
The short text describes the object sufficiently |
|
208 |
305 |
Test tag &1 has been deleted |
The short text describes the object sufficiently |
|
209 |
306 |
Tagging steps cannot be processed simultaneously |
The short text describes the object sufficiently |
|
210 |
307 |
Untagging steps cannot be processed simultaneously |
The short text describes the object sufficiently |
|
211 |
308 |
Operational step &1 for tagging was not executed |
The short text describes the object sufficiently |
|
212 |
309 |
Operational step &1 for untagging was not executed |
The short text describes the object sufficiently |
|
213 |
310 |
The sequence of operational steps is not allowed |
The short text describes the object sufficiently |
|
214 |
311 |
The simultaneous processing of operational steps is not allowed |
The short text describes the object sufficiently |
|
215 |
312 |
No operational step found for this selection |
The short text describes the object sufficiently |
|
216 |
313 |
No item found for this selection |
The short text describes the object sufficiently |
|
217 |
314 |
Assignments have been revoked automatically |
The short text describes the object sufficiently |
|
218 |
315 |
The data of the reference object was deleted |
The short text describes the object sufficiently |
|
219 |
316 |
Asynchronous operational steps are not allowed |
The short text describes the object sufficiently |
|
220 |
317 |
Filters for &1 are not allowed |
The short text describes the object sufficiently |
|
221 |
318 |
The order is not WCM relevant |
Space: object requires documentation |
|
222 |
319 |
Assignment is not allowed |
The short text describes the object sufficiently |
|
223 |
320 |
Activity category is not allowed |
The short text describes the object sufficiently |
|
224 |
321 |
Architecture is not allowed |
The short text describes the object sufficiently |
|
225 |
322 |
A status prevents assignment |
The short text describes the object sufficiently |
|
226 |
323 |
&1 &2 activated |
The short text describes the object sufficiently |
|
227 |
324 |
&1 &2 was deactivated |
The short text describes the object sufficiently |
|
228 |
325 |
&1 &2 has been flagged for deletion |
The short text describes the object sufficiently |
|
229 |
326 |
Deletion flag for &1 &2 revoked |
The short text describes the object sufficiently |
|
230 |
327 |
&1 &2 was prepared |
The short text describes the object sufficiently |
|
231 |
328 |
Preparation for &1 &2 revoked |
The short text describes the object sufficiently |
|
232 |
329 |
The maintenance of tab pages is only possible for tab |
The short text describes the object sufficiently |
|
233 |
330 |
No tabs (for example, &1) can be arranged on tab pages |
The short text describes the object sufficiently |
|
234 |
331 |
The function was performed for &1 of &2 entries |
The short text describes the object sufficiently |
|
235 |
332 |
The function was performed for all &1 entries |
The short text describes the object sufficiently |
|
236 |
333 |
The function was not performed for any entries |
The short text describes the object sufficiently |
|
237 |
334 |
The validity was extended by &1 hours |
The short text describes the object sufficiently |
|
238 |
335 |
The validity was extended by one hour |
The short text describes the object sufficiently |
|
239 |
336 |
Check the data for the new use |
Space: object requires documentation |
|
240 |
337 |
The function was performed for one entry |
The short text describes the object sufficiently |
|
241 |
338 |
All &1 entries were changed |
The short text describes the object sufficiently |
|
242 |
339 |
No entries were changed |
The short text describes the object sufficiently |
|
243 |
340 |
One entry was changed |
The short text describes the object sufficiently |
|
244 |
341 |
One of &1 entries was changed |
The short text describes the object sufficiently |
|
245 |
342 |
&1 of &2 entries were changed |
The short text describes the object sufficiently |
|
246 |
343 |
No &1 is assigned |
The short text describes the object sufficiently |
|
247 |
344 |
&1 is locked |
The short text describes the object sufficiently |
|
248 |
345 |
Log entry for tag &1 deleted |
The short text describes the object sufficiently |
|
249 |
346 |
Log entry for test tag &1 deleted |
The short text describes the object sufficiently |
|
250 |
347 |
The WCM object is not yet valid |
The short text describes the object sufficiently |
|
251 |
348 |
The validity period has already expired |
The short text describes the object sufficiently |
|
252 |
349 |
Select an operation |
The short text describes the object sufficiently |
|
253 |
350 |
Date and time (&1 &2) are in the past |
The short text describes the object sufficiently |
|
254 |
351 |
Date and time (&1 &2) are too far in the future |
The short text describes the object sufficiently |
|
255 |
352 |
Approval &1 was issued |
The short text describes the object sufficiently |
|
256 |
353 |
Approval &1 was revoked |
The short text describes the object sufficiently |
|
257 |
354 |
Approval &1 was deleted |
The short text describes the object sufficiently |
|
258 |
355 |
An entry was deleted |
The short text describes the object sufficiently |
|
259 |
356 |
Default value &1 for operational steps was used |
The short text describes the object sufficiently |
|
260 |
357 |
Operational step &1 for tagging was enhanced |
The short text describes the object sufficiently |
|
261 |
358 |
Operational step &1 for untagging was enhanced |
The short text describes the object sufficiently |
|
262 |
359 |
Function &1 is active |
The short text describes the object sufficiently |
|
263 |
360 |
Function &1 is possible |
The short text describes the object sufficiently |
|
264 |
361 |
&1 entries have been deleted |
The short text describes the object sufficiently |
|
265 |
362 |
No entry has been deleted |
The short text describes the object sufficiently |
|
266 |
363 |
Table &1 has been changed |
The short text describes the object sufficiently |
|
267 |
364 |
Table &1 has not been changed |
The short text describes the object sufficiently |
|
268 |
365 |
Work clearance management for the operation is active |
The short text describes the object sufficiently |
|
269 |
366 |
The settings for work permits have been defined |
The short text describes the object sufficiently |
|
270 |
367 |
Graphical WCM planning is active |
The short text describes the object sufficiently |
|
271 |
368 |
Mobile processing is active |
The short text describes the object sufficiently |
|
272 |
369 |
Mode-dependent tagging is active |
The short text describes the object sufficiently |
|
273 |
370 |
Stepwise tagging is active |
The short text describes the object sufficiently |
|
274 |
371 |
Digital signature is active |
The short text describes the object sufficiently |
|
275 |
372 |
Multiple use of operational tags is active |
The short text describes the object sufficiently |
|
276 |
373 |
Valuation is active |
The short text describes the object sufficiently |
|
277 |
374 |
When specifying an extension, you must specify the maximum extension |
The short text describes the object sufficiently |
|
278 |
375 |
When specifying the maximum extension, you must specify the extension |
The short text describes the object sufficiently |
|
279 |
376 |
The maximum extension must be the extension multiplied by n (n>0) |
The short text describes the object sufficiently |
|
280 |
377 |
If you use an icon, the title can have up to 25 characters |
The short text describes the object sufficiently |
|
281 |
378 |
No assignment was copied |
The short text describes the object sufficiently |
|
282 |
379 |
Not all assignments were copied |
The short text describes the object sufficiently |
|
283 |
380 |
Approval status for &1 &2 prevents the revoking of the assignment |
The short text describes the object sufficiently |
|
284 |
381 |
Approval status for &1 &2 prevents the assignment |
The short text describes the object sufficiently |
|
285 |
382 |
&1 &2 cannot be locked |
The short text describes the object sufficiently |
|
286 |
383 |
&1 &2 already assigned |
The short text describes the object sufficiently |
|
287 |
384 |
Enhancement prevents the assignment of &1 &2 |
The short text describes the object sufficiently |
|
288 |
385 |
The maximum number of assignments has already been reached for &1 &2 |
The short text describes the object sufficiently |
|
289 |
386 |
The previous validity has been restored |
The short text describes the object sufficiently |
|
290 |
387 |
A new validity has been determined |
The short text describes the object sufficiently |
|
291 |
388 |
Sequence number &1 is already assigned |
The short text describes the object sufficiently |
|
292 |
389 |
Tabstrips do not support frames |
The short text describes the object sufficiently |
|
293 |
390 |
Subscreen &1 does not support (additional) frames |
The short text describes the object sufficiently |
|
294 |
391 |
Subscreen &1 does not support arrangement in the right half of the screen |
The short text describes the object sufficiently |
|
295 |
392 |
When arranging horizontally, use a frame |
The short text describes the object sufficiently |
|
296 |
393 |
Subscreen &1 does not exist |
The short text describes the object sufficiently |
|
297 |
394 |
You can only select operations for an order |
The short text describes the object sufficiently |
|
298 |
395 |
Operational step &1 for tagging is in process |
The short text describes the object sufficiently |
|
299 |
396 |
Operational step &1 for untagging is in process |
The short text describes the object sufficiently |
|
300 |
397 |
The WCM object must be created manually |
The short text describes the object sufficiently |
|
301 |
398 |
&1 &2 is locked by user &3 |
The short text describes the object sufficiently |
|
302 |
399 |
&1 &2 can no longer be changed due to its status |
The short text describes the object sufficiently |
|
303 |
400 |
The proposal was adopted |
The short text describes the object sufficiently |
|
304 |
401 |
The proposal was revoked |
The short text describes the object sufficiently |
|
305 |
402 |
&1 of &2 entries were selected |
The short text describes the object sufficiently |
|
306 |
403 |
One entry of &2 entries was selected |
The short text describes the object sufficiently |
|
307 |
404 |
No entries were selected |
The short text describes the object sufficiently |
|
308 |
405 |
All &1 entries were selected |
The short text describes the object sufficiently |
|
309 |
406 |
One entry was selected |
The short text describes the object sufficiently |
|
310 |
407 |
&1 was extended (validity) |
The short text describes the object sufficiently |
|
311 |
408 |
&1 &2 created |
The short text describes the object sufficiently |
|
312 |
409 |
&1 &2 created |
The short text describes the object sufficiently |
|
313 |
410 |
One proposal was adopted |
The short text describes the object sufficiently |
|
314 |
411 |
&1 proposals were adopted |
The short text describes the object sufficiently |
|
315 |
412 |
One proposal was determined |
The short text describes the object sufficiently |
|
316 |
413 |
&1 proposals were determined |
The short text describes the object sufficiently |
|
317 |
414 |
One entry was displayed |
The short text describes the object sufficiently |
|
318 |
415 |
&1 entries were displayed |
The short text describes the object sufficiently |
|
319 |
416 |
&1 &2 selected |
The short text describes the object sufficiently |
|
320 |
417 |
&1 &2 selected |
The short text describes the object sufficiently |
|
321 |
418 |
No proposals could be determined |
The short text describes the object sufficiently |
|
322 |
419 |
Further information is available |
The short text describes the object sufficiently |
|
323 |
420 |
Approval &1 does not exist |
The short text describes the object sufficiently |
|
324 |
421 |
Approval &1 is already assigned |
The short text describes the object sufficiently |
|
325 |
422 |
An assignment was deleted |
The short text describes the object sufficiently |
|
326 |
423 |
Work permit was handed out |
The short text describes the object sufficiently |
|
327 |
424 |
Work permit was returned |
The short text describes the object sufficiently |
|
328 |
425 |
PDF document of safety plan could not be created |
The short text describes the object sufficiently |
|
329 |
426 |
PDF document of safety plan could not be appended |
The short text describes the object sufficiently |
|
330 |
427 |
Overriding of internal number range requires dedicated usage type |
The short text describes the object sufficiently |
|
331 |
428 |
Overriding of external number range requires dedicated usage type |
The short text describes the object sufficiently |
|
332 |
429 |
Overriding of view profile requires dedicated usage type |
The short text describes the object sufficiently |
|
333 |
430 |
Specification of usage for automatic generation only applies to templates |
The short text describes the object sufficiently |
|
334 |
431 |
Dedicated usage types must be specified consistently (plant &1) |
The short text describes the object sufficiently |
|
335 |
432 |
View profile &1; maximum width of screen &2 |
The short text describes the object sufficiently |
|
336 |
433 |
Planning plant &1; usage &2; usage type &3 |
The short text describes the object sufficiently |
|
337 |
434 |
Direction &1: Database &2; Add &3; Delete &4 |
The short text describes the object sufficiently |
|
338 |
435 |
View profile &1: screen width reduced; check screen area arrangement |
The short text describes the object sufficiently |
|
339 |
436 |
Not all items were copied |
The short text describes the object sufficiently |
|
340 |
437 |
Subscreen &1 exceeds the maximum permitted screen width (&2 > &3) |
The short text describes the object sufficiently |
|
341 |
438 |
Train &2 is not intended for use in maintenance planning plant &1 |
The short text describes the object sufficiently |
|
342 |
439 |
Revision phase &2 is not intended for use in maint. planning plant &1 |
The short text describes the object sufficiently |
|
343 |
440 |
Enter the maintenance planning plant |
The short text describes the object sufficiently |
|
344 |
441 |
The maintenance planning plant (&1) can no longer be changed |
The short text describes the object sufficiently |
|
345 |
442 |
Enter the usage |
The short text describes the object sufficiently |
|
346 |
443 |
The usage (&1) can no longer be changed |
The short text describes the object sufficiently |
|
347 |
444 |
Current status for &1 &2 does not allow the required change |
The short text describes the object sufficiently |
|
348 |
600 |
* Archiving ************************************************************* |
Space: object requires documentation |
|
349 |
601 |
Archiving object &1 is not available |
Space: object requires documentation |
|
350 |
603 |
Choose at least one activity |
Space: object requires documentation |
|
351 |
604 |
Select at least one status as condition |
Space: object requires documentation |
|
352 |
610 |
* Graphic WCM Planning ************************************************** |
Space: object requires documentation |
|
353 |
611 |
RFC Server: Problems with basic RFC functions |
Space: object requires documentation |
|
354 |
612 |
RFC Server: Error importing data from SAP |
Space: object requires documentation |
|
355 |
613 |
RFC Server: Error interpreting data from SAP |
Space: object requires documentation |
|
356 |
614 |
RFC Server: Error exporting data to SAP |
Space: object requires documentation |
|
357 |
615 |
RFC Server: Termination |
Space: object requires documentation |
|
358 |
616 |
& could not be started |
Space: object requires documentation |
|
359 |
617 |
& is busy |
Space: object requires documentation |
|
360 |
618 |
& canceled |
Space: object requires documentation |
|
361 |
619 |
Unspecified error calling up graphic planning |
Space: object requires documentation |
|
362 |
620 |
* General messages ****************************************************** |
The short text describes the object sufficiently |
|
363 |
621 |
GUI status &1 was defined, activity category: &2 |
The short text describes the object sufficiently |
|
364 |
622 |
Label &1 was set |
The short text describes the object sufficiently |
|
365 |
623 |
GUI status &1 and GUI title &2 were defined, activity category: &3 |
The short text describes the object sufficiently |
|
366 |
624 |
Question: &1; answer: &2 |
The short text describes the object sufficiently |
|
367 |
625 |
The update of the update function modules was successful |
The short text describes the object sufficiently |
|
368 |
626 |
Call screen &1 |
The short text describes the object sufficiently |
|
369 |
627 |
Exit screen sequence: call screen &1 |
The short text describes the object sufficiently |
|
370 |
628 |
All change requests for current SAP LUW were stored |
The short text describes the object sufficiently |
|
371 |
629 |
Exit program &1 |
The short text describes the object sufficiently |
|
372 |
630 |
Call transaction &1, display screen, new internal session |
The short text describes the object sufficiently |
|
373 |
631 |
Exit current call sequence: call transaction &1 |
The short text describes the object sufficiently |
|
374 |
632 |
Data was written to ABAP memory under the ID &1 |
The short text describes the object sufficiently |
|
375 |
633 |
Data with the ID &1 found, and contents transferred |
The short text describes the object sufficiently |
|
376 |
634 |
SET/GET parameter &1 has the value &2 |
The short text describes the object sufficiently |
|
377 |
635 |
Value &2 was set for SET/GET parameter &1 |
The short text describes the object sufficiently |
|
378 |
636 |
Dialog box &1 was displayed |
The short text describes the object sufficiently |
|
379 |
637 |
Return value &1 |
The short text describes the object sufficiently |
|
380 |
638 |
Execute update function module &1 in dialog mode |
The short text describes the object sufficiently |
|
381 |
639 |
Register update function module &1, execution is scheduled |
The short text describes the object sufficiently |
|
382 |
640 |
Register subroutine &1, execution is scheduled |
The short text describes the object sufficiently |
|
383 |
641 |
Call program &1, new internal session |
The short text describes the object sufficiently |
|
384 |
642 |
Call program &1, internal session replaced |
The short text describes the object sufficiently |
|
385 |
643 |
Screen sequence control was listed |
The short text describes the object sufficiently |
|
386 |
644 |
Process current screen &1 in background, execute function code &2 |
The short text describes the object sufficiently |
|
387 |
645 |
Data records unlocked; lock object &1 (&2) |
The short text describes the object sufficiently |
|
388 |
646 |
Lock data records; lock object &1 (&2) |
The short text describes the object sufficiently |
|
389 |
647 |
Call transaction &1, do not display screen, new internal session |
The short text describes the object sufficiently |
|
390 |
648 |
Execute function code &1 |
The short text describes the object sufficiently |
|
391 |
649 |
Function code &1 was executed |
The short text describes the object sufficiently |
|
392 |
650 |
GUI title &1 was defined, activity category: &2 |
The short text describes the object sufficiently |
|
393 |
651 |
& & & & |
|
|
394 |
652 |
Output simple list (one-line or multiline): &1 entries |
The short text describes the object sufficiently |
|
395 |
653 |
Output hierarchical, sequential list: &1 header data, &2 items |
The short text describes the object sufficiently |
|
396 |
654 |
List contains no data |
The short text describes the object sufficiently |
|
397 |
655 |
No exception for function module call &1 |
The short text describes the object sufficiently |
|
398 |
656 |
Function is not available |
|
|
399 |
657 |
Indicator &1 was set |
The short text describes the object sufficiently |
|
400 |
658 |
Indicator &1 was revoked |
The short text describes the object sufficiently |
|
401 |
659 |
Indicator &1 is set |
The short text describes the object sufficiently |
|
402 |
660 |
Indicator &1 is not set |
The short text describes the object sufficiently |
|
403 |
661 |
Result: &1 errors, &2 warnings, and &3 information messages |
The short text describes the object sufficiently |
|
404 |
662 |
Execute data change in dialog mode |
The short text describes the object sufficiently |
|
405 |
663 |
Table &1: create &2, delete &3, and change &4 |
The short text describes the object sufficiently |
|
406 |
664 |
Table &1: &2 created, &3 deleted, and &4 changed |
The short text describes the object sufficiently |
|
407 |
665 |
Table &1 has one entry |
The short text describes the object sufficiently |
|
408 |
666 |
Table &1 has no entries |
The short text describes the object sufficiently |
|
409 |
667 |
Table &1 has &2 entries |
The short text describes the object sufficiently |
|
410 |
668 |
Variable &1 has the value &2 |
The short text describes the object sufficiently |
|
411 |
669 |
Value of variable &1 changed from &2 to &3 |
The short text describes the object sufficiently |
|
412 |
670 |
Variable &1 was initialized |
The short text describes the object sufficiently |
|
413 |
671 |
Value of variable &1 was set to &2 |
The short text describes the object sufficiently |
|
414 |
672 |
Variable &1 is initial |
The short text describes the object sufficiently |
|
415 |
673 |
Label &1 was completed: processing duration &2 |
The short text describes the object sufficiently |
|
416 |
674 |
BAdI &1, method &2: return value &3 |
The short text describes the object sufficiently |
|
417 |
675 |
Function module &1: return value &2 |
The short text describes the object sufficiently |
|
418 |
676 |
& items were deleted |
The short text describes the object sufficiently |
|
419 |
677 |
One item has been inserted |
The short text describes the object sufficiently |
|
420 |
678 |
Table &1: no lines were transferred |
The short text describes the object sufficiently |
|
421 |
679 |
Table &1: one line was transferred |
The short text describes the object sufficiently |
|
422 |
680 |
Table &1: &2 lines were transferred |
The short text describes the object sufficiently |
|
423 |
681 |
View &1: no lines were transferred |
The short text describes the object sufficiently |
|
424 |
682 |
View &1: one line was transferred |
The short text describes the object sufficiently |
|
425 |
683 |
View &1: &2 lines were transferred |
The short text describes the object sufficiently |
|
426 |
684 |
One item was deleted |
The short text describes the object sufficiently |
|
427 |
685 |
No view profile was assigned |
The short text describes the object sufficiently |
|
428 |
686 |
Call subroutine (&2) of program (&1) |
The short text describes the object sufficiently |
|
429 |
687 |
Program (&1), subroutine (&2): Return value &3 |
The short text describes the object sufficiently |
|
430 |
700 |
* Program errors ******************************************************** |
|
|
431 |
701 |
Wrong transfer parameter(s) |
Space: object requires documentation |
|
432 |
702 |
No entry/entries in the table (&) |
Space: object requires documentation |
|
433 |
703 |
Task (&) is not defined |
Space: object requires documentation |
|
434 |
704 |
Object type (&) is not defined |
Space: object requires documentation |
|
435 |
705 |
Entry already exists |
|
|
436 |
706 |
Entry does not exist |
|
|
437 |
707 |
Activity category (&) is not defined |
Space: object requires documentation |
|
438 |
708 |
Print type (&) is not defined |
Space: object requires documentation |
|
439 |
709 |
Value (&) is not defined |
Space: object requires documentation |
|
440 |
710 |
Object number (&) is not defined |
Space: object requires documentation |
|
441 |
711 |
Error (&) occurred executing function module (&) |
Space: object requires documentation |
|
442 |
712 |
Entry (&) not found in table (&) |
Space: object requires documentation |
|
443 |
713 |
Transaction code (&) is not defined |
Space: object requires documentation |
|
444 |
714 |
Direction (&) is not defined |
Space: object requires documentation |
|
445 |
715 |
Message category (&) is not defined |
Space: object requires documentation |
|
446 |
716 |
Assignments are already available |
Space: object requires documentation |
|
447 |
717 |
Table (&) has (&) entry/entries |
Space: object requires documentation |
|
448 |
718 |
Program errors |
|
|
449 |
719 |
Object type (&) is not defined |
Space: object requires documentation |
|
450 |
720 |
Subprogram (&1) or program (&2) is not available |
Space: object requires documentation |
|
451 |
721 |
Error when importing data (&) |
Space: object requires documentation |
|
452 |
722 |
Invalid entry in database table (&) |
Space: object requires documentation |
|
453 |
723 |
Invalid entry in internal table (&) |
Space: object requires documentation |
|
454 |
724 |
Function code (&) is not defined |
Space: object requires documentation |
|
455 |
725 |
Instruction (&1) provides exception (&2) |
Space: object requires documentation |
|
456 |
726 |
Memory ID (&) is not defined |
Space: object requires documentation |
|
457 |
727 |
Category (&) is not defined |
Space: object requires documentation |
|
458 |
728 |
Impermissible Customizing (&) |
Space: object requires documentation |
|
459 |
729 |
Return value (&) is not defined |
Space: object requires documentation |
|
460 |
730 |
Incorrect call (&) |
|
|
461 |
731 |
Function cannot be active |
Space: object requires documentation |
|
462 |
732 |
Transaction (&) is not defined |
Space: object requires documentation |
|
463 |
733 |
Status (&) is not defined |
Space: object requires documentation |
|
464 |
734 |
Subscreen (&1) is not defined |
Space: object requires documentation |
|
465 |
735 |
Screen (&) is not defined |
Space: object requires documentation |
|
466 |
736 |
Item category (&) is not defined |
Space: object requires documentation |
|
467 |
737 |
Approval status (&) is not defined |
Space: object requires documentation |
|
468 |
738 |
List editing (&) is not defined |
Space: object requires documentation |
|
469 |
739 |
Model (&) is not defined |
Space: object requires documentation |
|
470 |
740 |
The generic object services are not available |
Space: object requires documentation |
|
471 |
741 |
Unspecified error when processing the object (&) |
The short text describes the object sufficiently |
|
472 |
742 |
Usage (&1) is not defined |
The short text describes the object sufficiently |
|
473 |
743 |
View profile (&1) is not defined |
The short text describes the object sufficiently |
|
474 |
744 |
&1 (&2) is not defined |
The short text describes the object sufficiently |
|
475 |
745 |
Error (&) in item data to be processed |
The short text describes the object sufficiently |
|
476 |
746 |
Missing lock for &1 &2 |
The short text describes the object sufficiently |
|
477 |
800 |
* System errors ********************************************************* |
|
|
478 |
801 |
Error when inserting in database table (&) |
Space: object requires documentation |
|
479 |
802 |
Error when deleting from database table (&) |
Space: object requires documentation |
|
480 |
803 |
Error during loop using the internal table (&) |
Space: object requires documentation |
|
481 |
804 |
Error when executing function module (&) |
Space: object requires documentation |
|
482 |
805 |
Error when deleting from internal table (&) |
Space: object requires documentation |
|
483 |
806 |
Error when reading the internal table (&) |
Space: object requires documentation |
|
484 |
807 |
Error during change to internal table (&) |
Space: object requires documentation |
|
485 |
808 |
Error during change to database table (&) |
Space: object requires documentation |
|
486 |
809 |
Error when inserting in internal table (&) |
Space: object requires documentation |
|
487 |
810 |
Error when reading line (&) |
Space: object requires documentation |
|
488 |
811 |
Error linking field (&1) to component (&2) |
Space: object requires documentation |
|
489 |
812 |
Update could not be completed successfully |
Space: object requires documentation |
|
490 |
813 |
Error when reading database table (&) |
Space: object requires documentation |
|
491 |
814 |
Could not import data objects |
Space: object requires documentation |
|
492 |
815 |
Error (&2) when executing method (&1) |
Space: object requires documentation |
|
493 |
816 |
Error when assigning memory area (&1) to field symbol (&2) |
Space: object requires documentation |
|
494 |
817 |
Error when converting date (&1) and time (&2) |
Space: object requires documentation |
|
495 |
818 |
Error (&1) during pattern-based replace |
Space: object requires documentation |
|
496 |
899 |
* Customer namespace **************************************************** |
|
|
497 |
900 |
|
|
|