AD - Arbeitsgebiet Data Dictionary
The following messages are stored in message class AD: Arbeitsgebiet Data Dictionary.
It is part of development package SDIC in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP Dictionary".
It is part of development package SDIC in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP Dictionary".
Message Nr ▲ | Message Text |
---|---|
000 | Temporary table for & not in database |
001 | Action possible only for 'value table' field |
002 | Action possible only for 'domain name' field |
003 | Value & was deleted |
004 | Domain & has no active values |
005 | & (Error activating dependent objects) |
006 | Enter only single language-dependent values |
007 | & (Lower limit of range is blank) |
008 | Values for domain & were deleted |
009 | Enter consistent parameter passing |
010 | & & & & |
011 | Value range for domain & is defined by a value table |
012 | Transfer parameter missing. & is not possible |
013 | &:Data type missing (value maintenance is not possible) |
014 | Upper and lower limits are identical; correct the limits |
015 | & & (Value deviates from data type & or is not allowed) |
016 | & & (Enter a value length shorter than the domain length &) |
017 | Value & already exists |
018 | Values have already been saved |
019 | Value does not exist |
020 | If you enter X, values for & will be deleted |
021 | & & is locked by another transaction |
022 | Enter a valid command |
023 | Data element & has already been saved |
024 | Activate is currently locked by user & |
025 | System error in lock management |
026 | & is not valid; check and correct it |
027 | Domain name missing (enter names) |
028 | Domain & is not active (check name) |
029 | Foreign key maintenance not possible for this field |
030 | & is not active |
031 | Report database error (DDERR & &) to the system administrator |
032 | & was activated |
033 | & was deleted |
034 | & saved |
035 | & was reset |
036 | & & already saved |
037 | To cancel processing, select ESC |
038 | Domain & was not saved |
039 | & & does not exist |
040 | & is reserved for & |
041 | Object & is being processed |
042 | & is non-standard and must be corrected |
043 | Table & already saved |
044 | Data element & is not active |
045 | Table & is not active (check name) |
046 | Data element does not exist |
047 | Enter a data element |
048 | Data element is not active (check name) |
049 | Field attributes were not saved; save them now |
050 | Press ENTER to confirm |
051 | Identical field names in lines & and &; change one of the field names |
052 | &-& (Specify a valid reference table) |
053 | Field & is used as a reference field and cannot be deleted |
054 | Table & has more than & key fields |
055 | &-& (Specify a reference field with format UNIT/PREC) |
056 | &-& (Specify a reference field with format CUKY) |
057 | &-& (Specify a reference field) |
058 | Reference field &-& not in format & |
059 | Format CURR/QUAN requires you to specify a reference field |
060 | & (Specify a data type) |
061 | & (Output length shorter than calculated (&) ) |
062 | & (Specify a data length) |
063 | Output length shorter than data length |
064 | & (Number of spaces adapted to number of decimal places) |
065 | Data length exceeds length defined in the template |
066 | Output length for data type & is set to & |
067 | & (Values do not exist) |
068 | Only the active version of & exists |
069 | Object & is new and being processed by & |
070 | Documentation for & & deleted |
071 | Data element & is not in ABAP Dictionary |
072 | No documentation exists for & & & |
073 | Documentation for & & & has been deleted |
074 | Specify a valid document class |
075 | Documentation & saved |
076 | You cannot change active fields in this mode |
077 | Choose only one object class |
078 | Choose an object class |
079 | Documentation maintenance not possible until values have been saved |
080 | No authorization for object & |
081 | No authorization for object &, active version missing |
082 | & is new and reserved for & |
083 | No authorization for table &, active version missing |
084 | Enter an object name for navigation |
085 | Field & (specify an active data element/domain) |
086 | Values for & were saved |
087 | Only those responsible for DDIC can activate objects |
088 | Interval & to & was deleted |
089 | Table is locked (see restart log) |
090 | & was released |
091 | First 7 characters of name & are identical to the view table name |
092 | First 7 characters of name & are identical to the pool/cluster |
093 | First 7 characters of name & are identical to the MC table |
094 | An underscore is not permitted in position 2 or 3 |
095 | An active version can be unlocked, but this is optional |
096 | Data element & was unlocked |
097 | Domain & was unlocked |
098 | Table & was unlocked |
099 | Table name must be at least 4 characters long |
100 | Table/view & does not exist |
101 | First 7 characters of name & are identical to a table |
102 | Select a shorter name for & |
103 | The name & does not start with a letter |
104 | The name & contains a blank; enter it again without blanks |
105 | The name & contains a non-alphanumeric character |
106 | 'A' version of & was saved, but not locked |
107 | No fields exist for table & |
108 | &-& data element & is missing |
109 | Field & in table & is specified twice. Please check. |
110 | Field & (Data type & is not supported in domain &) |
111 | &-& (Check table & does not exist) |
112 | &-& (Reference field &-& does not exist) |
113 | Table & still exists in R/2 DD; activation not possible |
114 | ATAB pooled table & does not start with T |
115 | Field & (Value & is not permitted) |
116 | & is a reserved word; choose another word |
117 | Field & in table & was entered twice |
118 | Activate table & |
119 | Activate data element & |
120 | Data element & does not exist |
121 | Data element & (domain & does not exist) |
122 | Activate domain & |
123 | Object & does not exist |
124 | & check table & does not exist |
125 | %N |
126 | Length of & is greater than & |
127 | & (Check table and values are not allowed) |
128 | Max. length of & is & |
129 | Enter & |
130 | Table & was activated |
131 | Table pool/cluster & was not activated |
132 | Domain & was activated |
133 | ** Activation of domain & canceled |
134 | Data element & was activated |
135 | **** Activation of data element & canceled |
136 | Activate dependent table & |
137 | ****** Activation of MC table & canceled |
138 | ****** Activation of view table & canceled |
139 | MC table & was activated |
140 | Activation/check log for & does not exist |
141 | & No authorization for & |
142 | Delete table & |
143 | Table & was deleted |
144 | Table & was not deleted |
145 | Table & is value table in domain & |
146 | Table & is check table in &-& |
147 | Table & is reference table in &-& |
148 | Table & still contains pooled/cluster tables (&) |
149 | View table & was activated |
150 | Table & is not active (action not possible) |
151 | Table & was reset |
152 | Table & was saved |
153 | Table & was activated |
154 | Table & was deleted |
155 | Table & is new (action not allowed) |
156 | Correct your entry (edit "Generic Area") |
157 | Only active version of table & exists (action not allowed) |
158 | Attributes of table & already saved |
159 | Activate table & with added fields |
160 | Table & DLIB generation unsuccessful, & |
161 | Texts for & were not activated |
162 | ==> Check table &: |
163 | =====> Check dependent table &: |
164 | <== Table & is consistent |
165 | <==== Dependent table & is consistent |
166 | <=== Warning: Table & is inconsistent ! |
167 | <=== Warning: Dependent table & is inconsistent ! |
168 | ....> Table & can only achieve partially active status |
169 | Fields of table & saved |
170 | Fields of table & are not active |
171 | Fields of table & were reset |
172 | Field name is missing |
173 | Field name & violates SAA standard |
174 | Field name & in table & does not exist |
175 | Fields of table & incorrect, activation is not possible |
176 | No fields exist for table &. Saving not possible |
177 | Only active fields exist for table & |
178 | Field & specified twice. (Saving not possible) |
179 | Transfer parameters are inconsistent. Field maintenance is not possible |
180 | Transfer parameters are missing. Field maintenance is not possible |
181 | Field name missing from table. Saving not poss. | |
182 | Specify a valid table type |
183 | Specify a maximum key length |
184 | Specify a maximum data length |
185 | Specify a delivery class |
186 | Key to table & is too long |
187 | Delete technical settings for table & |
188 | Technical settings for table & have been deleted |
189 | Technical settings for table & could not be deleted |
190 | Cursor position not allowed. Line & is selected |
191 | Cursor position not allowed. Lines & to & are selected |
192 | In generic buffering you cannot select a number of key fields |
193 | Data class & only becomes relevant when type changed from & to TRANSP |
194 | Minimum DB extent cannot be greater than maximum DB extent |
195 | No appropriate field name found |
196 | No other appropriate field name found for & |
197 | No authorization for assigning class 01 |
198 | & is not a database view |
199 | Incorrect call of routine ACTDD09L |
200 | Object & not active |
201 | Object & was reset |
202 | Object & was saved |
203 | Object & was activated |
204 | Object & was deleted |
205 | Object & is new, no active version exists |
206 | & is not a table of type POOL,CLUSTER,TRANSP |
207 | Only active version of object & exists |
208 | Object & does not exist |
209 | No suitable object found |
210 | You may not define more than two key fields |
211 | Structure type 'HEAD' can be used only once |
212 | Structure type 'HEAD' is mandatory |
213 | Choose name VARKEY for second key field |
214 | Model program & does not exist |
215 | You may select only one option |
216 | Select only one function |
217 | Object component missing (List (F4), Maintain (F2) ) |
218 | Object component not active (List (F4), Maintain (F2) ) |
219 | Table & is used in & as an INCLUDE table |
220 | One of the INCLUDE tables is not active or does not exist |
221 | Specify a table |
222 | INCLUDE table & is not active |
223 | Table is not active. (Check name) |
224 | INCLUDE table used twice in the same INCLUDE chain |
225 | INCLUDE cannot be broken down; field name with suffix is too long |
226 | Too many nested INCLUDEs |
227 | Table does not exist |
228 | Table & is not an active table |
229 | & |
230 | Delete object & |
231 | Object & was deleted |
232 | Object & was not deleted |
233 | Activate object & |
234 | Object & was activated |
235 | Activation of object & was canceled |
236 | Tables of type VIEW are not permitted as INCLUDEs |
237 | Only structures can be included in database tables |
238 | Object & (&) was deleted |
239 | Unable to delete object & (&) because it is still in use |
240 | Specify a valid pool/cluster name |
241 | Specify an active pool/cluster |
242 | Entry of pool/cluster name not required |
243 | No table specified |
244 | Table & is not active or does not exist |
245 | No selection made |
246 | Choose one processing option only |
247 | No change was made |
248 | Value which has already been saved is overwritten |
249 | There are no active parameters for table & |
250 | Entry already exists |
251 | Logical directory & does not exist |
252 | Delete domain & |
253 | Domain & deleted |
254 | Domain & not deleted |
255 | Domain & is used in data element & |
256 | KeyFieldDisp. = 0; change keyFieldDisp only if generic buffering selected |
257 | Gen. buffering not allowed. Table & contains only one key field |
258 | Not saved. Generic buffering requires a key field number |
259 | This number of key fields is not permitted with generic buffering |
260 | Saved |
261 | Foreign key &-& (dependency factor TEXT is incorrect) |
262 | Delete data element & |
263 | Data element & deleted |
264 | Data element & not deleted |
265 | Data element & is still being used (see "Where-used list") |
266 | Length of header was increased from & to & |
267 | &-& (text foreign key requires additional language field) |
268 | &-& (text foreign key with fields outside of key) |
269 | Foreign key &-& (dependency factor ID incorrect) |
270 | Foreign key &-& (enter a valid relationship category) |
271 | Check table cannot be deleted |
272 | Foreign key & was saved |
273 | Foreign key &-& does not originate from foreign key table & |
274 | Foreign key &-& (& and & point to different domains) |
275 | Foreign key &-& (dependency factor & is incorrect here) |
276 | Foreign key &-& was already saved |
277 | Foreign key &-& is new, active version does not exist |
278 | No active version of foreign key &-& |
279 | &-& (foreign key exists only in active version) |
280 | For. &-& (check table & is not transitive with respect to value table &) |
281 | Foreign key maintenance is not possible for this field |
282 | Field &-& (check table & deviates from entity table &) |
283 | &-&: Foreign key has not been maintained |
284 | &-&: Foreign key cannot be specified in full |
285 | Check table & does not exist or does not have any key fields |
286 | Check table & is also foreign key table |
287 | Foreign key is incomplete, saving not possible |
288 | Foreign key &-& (foreign key not defined) |
289 | Check table & is not active |
290 | &-& (foreign key definition cannot be specified in full) |
291 | Foreign key &-& (foreign key field & & does not exist) |
292 | Foreign key & was deleted |
293 | Foreign key &-& (foreign key not generated) |
294 | Foreign key &-& (foreign key was deleted) |
295 | Foreign key &-& (foreign key incomplete, foreign key deleted) |
296 | Foreign key &-&; select one field only |
297 | Foreign key &-& (rel. cat. DYNP -> CARD superfluous) |
298 | Foreign key &-& (relationship cat. DYNP for internal tables) |
299 | Foreign key &-& (relationship cat. CLAS/SPEC --> cardinality 'C') |
300 | Primary key change not permitted for value table & |
301 | Foreign key &-& (relationship 'CLAS' --> classified field/value) |
302 | Foreign key &-& (no classified field/value specified with &) |
303 | Foreign key &-& (enter valid cardinality) |
304 | &-& (foreign key field & does not exist) |
305 | Field type &-& must be CHAR or NUMC |
306 | Field &-& is not defined in ABAP Dictionary |
307 | Foreign key & is not known in ABAP Dictionary |
308 | Value table & does not contain any key fields |
309 | Table & (no key field points to domain &) |
310 | & & & & |
311 | Entry incomplete |
312 | &-& (foreign key definition is partial) |
313 | No authorization; foreign key & does not exist |
314 | Foreign key & does not exist |
315 | Value & is not numeric |
316 | Value & is not allowed |
317 | Enter a valid application class |
318 | Enter max. 4-character control block name |
319 | &-& (foreign key definition generated automatically) |
320 | &: Key length greater than maximum key length (&) |
321 | & (specify a primary key) |
322 | & (data length used > max. data length in pool (&) ) |
323 | & (key fields are not at the beginning of the table) |
324 | & (key fields are not listed in sequence) |
325 | Table & is check table in domain & |
326 | Pool definition & (unauthorized change to field definition &) |
327 | Pool definition & (max. key length & exceeded) |
328 | Pool definition & (max. data length & exceeded) |
330 | Move the cursor to a valid position |
331 | Use only 'Insert' key to create a blank line |
332 | Pool & (mandatory field & does not exist) |
333 | Pool &, field & (field name, data type or data length incorrect) |
335 | Field & (data type or data length incorrect) |
336 | Generic key field missing |
337 | Specify no more than one client field in the key |
338 | Use another data type in the pool key |
339 | Enter a key for table & |
340 | Field definitions for table & changed, data exists (F1) |
341 | Key to table & changed, data exists (F1) |
342 | Table & is not defined in ABAP Dictionary |
343 | Structure of table & changed, conversion of DB table (F1) |
344 | Create a database table for table & |
345 | Table & (different key length in client &) |
346 | Table & (different function length in client &) |
347 | Table &: Structure changed; generate the database table again |
348 | Table & (fields added or deleted, data exists) |
349 | Table & is locked by user & |
350 | Table & (table type changed from TRANSP --> POOL (F1)) |
351 | Table & (table type changed from POOL --> TRANSP (F1)) |
352 | Table & (inconsistencies in database, cause & (routine &)) |
353 | Correction system lock is not correct |
354 | Nametab does not exist |
355 | Nametab generated; adjust the C structures |
356 | Specify an application class from TAPPL |
357 | Specify a parameter ID from table TPARA |
358 | First generate nametab using C program |
359 | Table & (generation type 1, nametab was written) |
360 | Table & (error & &) |
361 | Inconsistencies between nametab and field catalog |
362 | Table type change. Convert data |
363 | Create a database table |
364 | Table type change. Convert data |
365 | Fields inserted/deleted. Convert DB table/data |
366 | Field definitions changed; update them now |
367 | Key changed (update the DB table/data) |
368 | Fields added. Convert DB table/data |
369 | Field definitions were changed completely. Data will be lost |
370 | Active nametab is missing. Nametab was re-written |
371 | Table type change. Create database table |
372 | Table type change. Delete database table |
373 | Fields deleted; update the DB table/data |
374 | Create a database table |
375 | Table type changed (delete the table dynpro) |
376 | Table type changed; data may have been invalidated |
377 | Key format changed; update the data |
378 | Fields can only be added with permission from your head of development |
379 | Key fields were changed/renamed; update the DB table/data |
380 | Table key structure changed; update the database table/data |
381 | Table type change. Create database table |
382 | Nametab is incomplete |
383 | Fields deleted; adjust the table dynpro |
384 | Pool/cluster name changed. Convert data |
385 | Table type change. Convert data |
386 | Table type change; check whether data updates are required |
387 | Create a database table |
388 | INCLUDE not allowed for tables of type VIEW |
389 | Fields were added; modify the table dynpro |
390 | Activation of table & forced (E- & ), &, & |
391 | Output length for data type & is set to at least & |
392 | Table & of generation type 1 (nametab was not rewritten) |
393 | Fields were added; update the DB table |
394 | Entry already exists in TACOB |
395 | Entry in TACOB performed, activation takes place in background |
396 | Fields can be added only with permission of head of development |
397 | Already activated |
398 | First eliminate errors in table structure |
399 | No inconsistencies found |
400 | Entries for data type & have been fixed and will be corrected |
401 | Domain & does not contain any values and cannot be saved |
402 | & (format & is not supported) |
403 | Upper limit is lower than lower limit |
404 | & (error during value test) |
405 | Value range is only permitted for formats CHAR, NUMC, DEC, INT* |
406 | & (length & is not within limits (&,&)) |
407 | Ordering party & |
408 | & (calculated output length & is less than specified &) |
409 | & (length> & for & is only allowed in structures) |
410 | Field length & is too big; enter a length between & and & bytes |
411 | & No restart log is available for this object |
412 | Check whether function was performed correctly |
413 | Table was converted |
414 | Table update was canceled due to error |
415 | Background job already exists |
416 | Background job & & was created |
417 | & (length> & for DEC only allowed for non-DB table) |
418 | Key field number was applied; save the data |
419 | Data was saved |
420 | No change to the key field number |
421 | Generic buffering requires a number of key fields to be entered |
422 | Table & cannot be buffered |
423 | Generic buffering is not possible. Table & has no key fields. |
424 | When specifying buffering type, you must select storage type in buffer |
425 | Compressed save in buffer can only be chosen if buffering type <> SPACE |
426 | Buffering/compression not allowed |
427 | Activate technical settings for table & |
428 | Check technical settings for table & |
429 | Technical settings activated for table & |
430 | & used in MC or view. Table type change not permitted |
431 | Table & used in VIEW table or in MC object & |
432 | Field & is used in view, MC or lock object and cannot be deleted |
433 | Relationship &-& is used in MC/view and cannot be deleted |
434 | Key is already defined; field & cannot be in the key |
435 | Client field & is not in first field position, table is cross-client |
436 | Enter active data element and/or domain in field & |
437 | & & & is entered for background conversion |
438 | Objects entered for background editing....:& |
439 | Termination of activation of technical settings for table & |
440 | Technical settings for table & were checked successfully |
441 | SQL table & is already activated |
442 | Data element & is already activated |
443 | Domain & is already activated |
444 | Table & is already activated |
445 | No documentation exists for this message |
446 | Domain & is active, check value table |
447 | Errors occurred when activating table & |
448 | Errors occurred when activating table & |
449 | Errors occurred during activation of dependent objects |
450 | *B* start of mass activation & & |
451 | Enter a valid structure name |
452 | Enter a valid transport request/correction |
453 | Final log: mass activation |
454 | *E* end of mass activation & & (total & msec.) |
455 | ROUND 1: activation with internal checks |
456 | ROUND 2: activation with external checks |
457 | *R* Activation successful, refer to log: & |
458 | & & & was not activated ( & ) |
459 | *R* Error during activation, refer to log: & |
460 | * - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - * |
461 | & & & was activated |
462 | Log for mass activation & & |
463 | & & & was not imported |
464 | & does not contain any objects to be activated |
465 | Object & & & was already activated |
466 | Mass activation ended with return code & |
467 | Mass activation RDDMASG0 &: |
468 | Start activation & & |
469 | System name.......... & |
470 | Activated using....... & & |
471 | & error in routine & |
472 | & error in routine & |
473 | Client field already exists in table & |
474 | & error during activation |
475 | Min/average/max (sec):....&/&/& |
476 | All objects dependent on table & were updated |
477 | Error in objects dependent on table & |
478 | & in round & (number/time):....&/& |
479 | Time statistics: |
480 | Started by........... & |
481 | Function............. & & |
482 | Number of objects to be activated...........: & (& &) |
483 | Activated objects...........& |
484 | Objects not activated:........& |
485 | Activated objects with warnings: & |
486 | Entry 'Create DB table & ' made for mass processing |
487 | Table of activation type 1; use C program to generate nametab |
488 | Entry 'Convert DB table &' made for mass processing |
489 | Object R3TR TABL & for mass processing already entered |
490 | Number of dependent tables:.................: & |
491 | Dependent table & |
492 | Warning with dependent tables |
493 | Entry & for index &-& made for mass processing |
494 | Statistics............& |
495 | Inactive nametab..... & |
496 | Add fields to database table (3rd round) |
497 | Logs...... ......... & & |
498 | Stored in clipboard --> Paste with F7 |
499 | Data from & saved temporarily (F1=Long text documentation) |
500 | Data from & saved temporarily (F1=Long text documentation) |
501 | SET INTERRUPT; press ENTER |
502 | Program replaced by RDDSQLTB |
503 | NEWOWNER is not ready for input (F1=Long text documentation) |
504 | Check on technical settings for table & was not successful |
505 | No. of key fields respected can only be specified for generic buffering |
506 | There was no active nametab |
507 | Table & (error reading fields from the inactive nametab) |
508 | No technical setting available for table & |
509 | Use the "activate" function |
510 | Table is partially active; activate it again |
511 | Table is partially active, DB table has not been modified |
512 | Table is partially active; resolve the inconsistency |
513 | Technical settings for table & not consistent (Goto -> Act./Check Log) |
514 | Activation of technical settings for table & successful |
515 | Function can only be used by the system administrator |
516 | Gen. buffering calls for no. of key fields > 0 |
517 | Calculation of number of data records for size categories not possible |
518 | No. of fields in key deleted. Can only be maintained for gen. buffering |
519 | Object locked or no authorization |
520 | Partially active tables for domain (&) |
521 | Partially active tables for data element (&) |
522 | Partially active domains or data elements for table (&) |
523 | There are no technical settings for internal table & |
524 | Message text does not exist in language & |
525 | Start of XPRA program: & time stamp & & |
526 | Function: & & & & |
527 | End of XPRA program & & & |
528 | XPRA program ends with return code & |
529 | Buffering not allowed.(-> No. of fields in gen. key must be 0) |
530 | & & activated (& &) |
531 | & & not activated (error & &) |
532 | & & (flag for activation in table TACOB) |
533 | Entry 'Delete DB table &' made for mass processing |
534 | & & (activation only before & and after & o'clock) |
535 | & & & for mass processing already entered |
536 | Message & & in language & does not exist |
537 | Enter a valid log type |
538 | File could not be opened or closed |
539 | Enter a valid log mode |
540 | Enter a valid error category |
541 | Internal error (program &, routine &, error code &) |
542 | & & & was activated with appended fields |
543 | Object & & has been flagged for deletion |
544 | Table & (buffering authorization, buffering type inconsistent) |
545 | Define a data class and size category for transparent table & |
546 | Table & (too many generically buffered fields) |
547 | Technical settings for table & modified/generated |
548 | Technical settings for table & activated |
549 | Error in technical settings for table & |
550 | Table & cannot be displayed |
551 | Generic entry not possible for numeric field types |
552 | Table & does not exist |
553 | There is a revised version of table & |
554 | No table authorization for table & |
555 | Table & is not a relational table |
556 | No values selected in the specified area |
557 | Table & not found |
558 | Maximum number of programs that can be generated reached |
559 | Table & is too wide to display (& bytes). |
560 | List for & printed |
561 | Caution: SELECT terminated after 100 runs |
562 | Internal error (& & &) |
563 | No database view exists for view & |
564 | View & cannot be displayed |
565 | Use only double quotation marks |
566 | An error occurred during generating (see long text) |
567 | Inactive nametab, without conversion & |
568 | & & inactive nametab with ADD FIELDS already exists |
569 | No. of tables that are both dependent and direct): & |
570 | &-&: Foreign key is partial (check table field &) |
571 | Partial foreign key incorrectly specified - remove field names |
572 | Error in dependent table & (caused by & &) |
573 | &-&: partial foreign key incorrect (remove at * field) |
574 | Table & was activated as a direct table |
575 | Dependent table & successful (caused by & &) |
576 | Direct table & successful, caused by & & |
577 | &-&: foreign key constant incorrect (remove field names) |
578 | &-& (enter constant part of foreign key correctly) |
579 | Specified DB parameters are invalid |
580 | **** Messages from the data interfaces |
581 | SQL error & in module &, function & occurred |
582 | Internal error & & in module & occurred |
583 | Internal error (F-16) occurred (refer to system log) |
584 | Gen. buffering not allowed, therefore no. of key fields must be 0 |
585 | Number of key fields not changed |
586 | Table & is of type & (technical settings cannot be defined/displayed) |
587 | Current table & has type & (no technical settings can be specified) |
588 | Data that had already been saved was not changed |
589 | Data not saved. Gen. buffering calls for no. of key fields > 0 |
590 | Table &: new version only, 'Add fields' not allowed |
591 | Table & already changed, 'Add fields' not allowed |
592 | Table & (activation canceled due to database lock) |
593 | Table &: Active version partially active |
594 | Table & (no fields to append) |
595 | Table & (append fields to ABAP Dictionary table) |
596 | Table & (fields appended to DB table) |
597 | Table & (modification of DB table canceled (DB lock)) |
598 | Table & (modification of DB table delayed) |
599 | Fields changed. Check database view & |
600 | **** Leave numbers in 600s for pool/cluster transaction |
601 | Do not change field 'DATALN' |
602 | No further key fields are specified in table & |
603 | Do not change field 'TABNAME' |
604 | Field & must be a key field |
605 | Key length greater than maximum key length & |
606 | No further data fields are specified in table & |
607 | Field & may not be a key field |
608 | Field & must be last field and of type 'RAW' |
609 | Table & is greater than the physical data page |
610 | Function length is greater than maximum functional length & |
611 | Table & already contains tables: Field cannot be changed |
612 | Table & already contains tables: Class cannot be changed |
613 | Table & does not contain a mandatory key field |
614 | Key length in table & > maximum key length (&) |
615 | Cluster & (function fields cannot be changed) |
616 | Table & already exists in another class (SAP, MC, nametab) |
617 | No errors found in structure & |
618 | Structure & unlocked |
619 | Pool/cluster fields & saved |
620 | Use only 'Insert' key to generate blank lines |
621 | Field '&' not found |
622 | Select an area |
623 | Clipboard empty |
624 | & fields copied to clipboard |
625 | Message & not found |
626 | Use compression for clusters only |
627 | Cluster fields reinitialized |
628 | Pool fields reinitialized |
629 | The fields cannot be reset (&-&) |
630 | Changing table type? Delete database table first |
631 | Changing table type? Delete data first |
632 | Foreign key &-& (inconsistency between header and structure) |
633 | Function 'Add MC fields' allowed only for MC objects |
634 | Save table first and select function again |
635 | Activate matchcode object & - no adding fields |
636 | Field & contains ' '. This is no longer supported |
637 | Field &1 contains '-'; change this now |
638 | Error in active POOL/CLUSTER |
639 | Table of type ATAB only allowed with data section < & |
640 | Attributes of & have already been saved |
641 | Error saving attributes of & |
642 | No active data element for attribute & |
643 | Entity type & has no attributes |
644 | Attributes of & saved |
645 | No short/long name for entity types & |
646 | Table & (primary key is not compact) |
647 | Enter a valid tablespace |
648 | No source selected |
649 | No. of key fields > &. Conversion to type & not allowed |
650 | *** Messages from T100 maintenance *** |
651 | Enter a valid target language |
652 | Enter a valid source language |
653 | Entry was saved |
654 | Enter a two-character message ID |
655 | Position cursor on message |
656 | Position cursor on line to be deleted |
657 | Text & not found |
658 | Message ID & is new |
659 | Message ID & contains no messages in language & |
660 | No messages in language & exist |
661 | Target message ID & is not locked |
662 | & messages copied |
663 | Target message ID & cannot contain entries |
664 | Enter different languages |
665 | Target language and original language must be different |
666 | & messages were renamed |
667 | Message & already exists |
668 | Choose a processing option |
669 | Choose a message ID |
670 | Message ID & already exists |
671 | Message ID & not yet created |
672 | Error when deleting & |
673 | Message ID & deleted |
674 | Source message ID and target message ID must be different |
675 | Message ID & already being maintained |
676 | Error during locking of message ID & |
677 | Error & occurred when deleting long text |
678 | Message ID & deleted |
679 | Message & could not be locked |
680 | Message & already exists |
681 | Message & is already being edited |
682 | An error occurred when locking message & |
683 | Enter values to be replaced |
684 | F17 replaces; press F6 to continue searching |
685 | The search string has been replaced in & messages |
686 | Message & & was not found |
687 | Do not use formatting characters in numeric fields |
688 | Tab. &: No. of key fields > & (no change possible in type TRANSP) |
689 | Number of objects to be deleted.............: & |
690 | & & & (& version) were deleted; check the references |
691 | Number of deleted objects with references...: & |
692 | & is still used & in & & |
693 | Table & is stored in SQLT & |
694 | No objects for deletion in & |
695 | Field & (use other data type in pool key) |
696 | Generic key field is missing from logical cluster & |
697 | Field & (Data type is not allowed) |
698 | Field & (data element does not exist) |
699 | Field & (data element or domain is not active) |
700 | **** Leave numbers in 700s for correction system **** |
701 | Program is locked for correction & (&). ENTER->Display |
702 | Original in & system. ENTER->Display |
703 | Program not contained in any correction. ENTER->Display |
704 | Program is locked for correction & (&) |
705 | No change to consolidation system &. ENTER->Display |
706 | Table & has no database table |
707 | Technical settings & (system type or name not available) |
708 | Table locked > See restart log (old) < Read long text |
709 | No inactive nametab exists |
710 | List level > 7. F3 to return to 1st level and F6 |
711 | & does not exist |
712 | Piece list & was saved |
713 | No enhancement made |
714 | Piece list was not saved |
715 | Change was not made |
716 | Specify a delivery class other than M |
717 | Table & contains data |
718 | Table & does not contain data |
719 | Table is a pooled/cluster table |
720 | More than 2000 fetches -> SAPDSQL error |
721 | Nametab generation for table & failed (problems with client field) |
722 | File & could not be opened |
723 | Data element & is partial |
724 | Domain & is partial |
725 | Combination of & with inactive mode not allowed |
726 | & & & was activated with warnings (&) |
727 | & & & was activated with warnings without dependent objects (&) |
728 | Minimum length & is assumed for data type & |
729 | Save index first |
730 | Foreign key &-& (enter valid dependency factor) |
731 | Foreign key &-& (do not make any more entries on foreign key screen) |
732 | Foreign key &-& (with internal tables, flag as foreign key screen) |
733 | Foreign key &-& (use cardinality 1 : N or 1 : CN with 'TEXT') |
734 | Foreign key &-& (indicate the foreign key type) |
735 | Foreign key &-& (flag as a semantic foreign key) |
736 | Foreign key &-& (enter valid cardinality) |
737 | Check field &-& missing from foreign key field definition |
738 | & & too long for logging (must be < &) |
739 | Table &: Nametab missing; check consistency of ABAP Dictionary <-> DB |
740 | & does not contain any objects to be deleted |
741 | Number of objects to be activated: & (& &) |
742 | There are no objects to be deleted |
743 | Max. number of temporary programs reached (try again later) |
744 | SQL error occurred during test access to table & |
745 | No inconsistencies found when checking the latest version |
746 | Only active version of technical settings exists (function not allowed) |
747 | Technical settings are new (function not possible) |
748 | Resetting was not possible |
749 | Technical settings reset to active version |
750 | No version exists that can be reset |
751 | You cannot display technical settings for table & |
752 | Error occurred when accessing the table |
753 | Physical pool/cluster does not exist in the database |
754 | Error: & occurred during job scheduling |
755 | Obtain approval for structure changes from head of development |
756 | Entry inserted |
757 | Job & scheduled |
758 | Error occurred in function module DD_DATABASE_UTILITY |
759 | ==> Index activation..................& Round : & |
760 | ==> Read request...............................: & |
761 | ==> Calculating order.........................: & |
762 | ==> Delete........................... & Call: & |
763 | ==> Domain activation................ & Round : & |
764 | ==> Data element activation.......... & Round : & |
765 | ==> Activation of dependent objects.. & Round : & |
766 | ==> Activation of special tables..... & Round : & |
767 | ==> Table activation ................ & Round : & |
768 | ==> Activation of including programs. & Round : & |
769 | ==> Comparison of results............ & Round : & |
770 | ==> Add fields........................& Round : & |
771 | ==> Activate technical settings...... & Round : & |
772 | ==> Total............................ & Round : & |
773 | ==> Activation of aggregates...................: & |
774 | ==> DDL operations.............................: & |
775 | ==> Reactivate active tables...................: & |
776 | ==> Final comparison of results................: & |
777 | ==> Output final log...........................: & |
778 | ==> Total......................................: & |
779 | ============================== Time consumption ===================== |
780 | Mass activation program.......: & & |
781 | Date/time.....................: & & |
782 | Input data....................: & & |
783 | Function......................: & & |
784 | Activation method.............: & |
785 | User..........................: & |
786 | Detailed log..................: & |
787 | Final log.....................: & |
788 | Statistics....................: & |
789 | SAP system....................: & |
790 | Operating system..............: & |
791 | Database management system....: & |
792 | Host..........................: & |
793 | * MASS ACTIVATION PROGRAM, ABAP DICTIONARY GROUP, SAP AG * |
794 | ******************************************************************* |
795 | Adjust database view if required |
796 | Version of >> active << object stored |
797 | Temporary version of active object stored |
798 | Identical version already stored |
799 | Only a version of an active object can be stored |
800 | **** Reserved for index maintenance up to 819 |
801 | Error in parameter passing to dialog module |
802 | Field & does not exist in table & |
803 | Field & occurs more than once in index &-& |
804 | Index &-& deleted |
805 | Place the cursor on a valid position |
806 | Index & to table & was saved |
807 | Index maintenance only possible for transparent tables |
808 | & is not allowed as index name (A-Z or 1-9) |
809 | No indexes found for table & |
810 | No changes were made. Saving unnecessary |
811 | Table still has no fields |
812 | Indexes are incorrect |
813 | Index &-& in being processed by & |
814 | Index &-& is new and is being edited by & |
815 | Index &-& (field & is not in the table) |
816 | Recreate database index for &-& |
817 | Delete database index for &-& |
818 | Index &-& does not contain fields |
819 | Delete database index for &-& and recreate |
820 | *********** MAINT_TRANS************* |
821 | Choose only & |
822 | The function group name must be 4 characters long |
823 | Choose a processing option |
824 | Choose one processing option only |
825 | Function group & still contains function modules |
826 | User name & invalid |
827 | No check values exist for the displayed transaction |
828 | Enter a validation object |
829 | You cannot save in display mode |
830 | You cannot delete in display mode |
831 | & selected |
832 | Deletion of & & was canceled |
833 | & & cannot be saved |
834 | && was not saved |
835 | & & saved |
836 | & already exists as & |
837 | & & cannot be changed |
838 | Processing of & & terminated |
839 | Check is only intended for transaction types T and R |
840 | Specify & |
841 | Choose a confirmation |
842 | Choose & for maintenance |
843 | Choose & |
844 | Conversion/ADD FIELDS for table with long raw field not allowed |
845 | Choose & for deletion |
846 | Table & is too long (>&) |
847 | No change made. Saving unnecessary |
848 | & already deleted |
849 | & was deleted |
850 | Table & (first delete database table) |
851 | Table & (first delete data and database table) |
852 | Length of table & > &. Conversion not possible in type TRANSP |
853 | Approval from head of development required to activate CLUSTER table |
854 | Approval from head of development required to activate & |
855 | &-& (no reference table/field combination &-& exists or data type wrong) |
856 | Table & (first delete data from the pooled table) |
857 | &-& (specify reference table AND reference field) |
858 | Field & (Value & = & not allowed) |
859 | First & places of name & identical to & |
860 | Table & (delete data from the cluster table) |
861 | Exception (database should not contain primary index) |
862 | You may not delete the primary index |
863 | Index could not be created |
864 | Error deleting operation/recreating index |
865 | Primary index is not in the database |
866 | Index is already in the database |
867 | Background processing not currently supported for primary indexes |
868 | Index & not defined in ABAP Dictionary |
869 | Index created |
870 | Index deleted and created again |
871 | Index & exists in database but not in ABAP Dictionary (inconsistency) |
872 | Only the delete function can be used for this object |
873 | Index & was deleted from the database |
874 | Error occurred when deleting index & |
875 | & does not require database parameters |
876 | & does not require database parameters for indexes |
877 | DB parameters are not currently supported for your database |
878 | No authorization for action: & with object: & |
879 | Delete objects (& call) |
880 | Final log of mass deletion program |
881 | &-& is reference field for &-&. Deletion not allowed |
882 | &-& is used in aggregate &. Delete not allowed |
883 | & & h |
884 | Table & and physical table & are not of same type |
885 | Structure change at field level (convert table &) |
886 | Fields were added. Database table is adjusted |
887 | &: Structure change at field level. Recreate database index |
888 | &: Structure change at field level. Database must be adjusted |
889 | &: Structure change at field level (modify the table dynpro) |
890 | Activation could not be unlocked |
891 | & (table type change &->& only after approval) |
892 | Generic buffering of table & (at least 2 key fields required) |
893 | Table & is already transparent (conversion not necessary) |
894 | Function & not intended for RDDGEN0L |
895 | End of distribution: & |
896 | Start of distribution: & |
897 | End of conversion: & |
898 | Start of conversion: & |
899 | Program names starting with { or } are reserved for the DB utility |
900 | **** Leave 900 series messages free for DB utility |
901 | This is a COMMIT; press ENTER |
902 | Enter table name |
903 | Enter R,T,D,S as processing type |
904 | Enter correction name |
905 | Enter R or S as a processing type |
906 | Enter a processing type |
907 | No restart log exists for this table |
908 | Check whether function was performed correctly |
909 | Lock entry deleted |
910 | Incorrect return code |
911 | Entry was saved |
912 | Error occurred when saving |
913 | No requests for mass processing exist |
914 | There are no restart logs |
915 | Temporary table for & has been deleted |
916 | Lock entry for & does not exist |
917 | Function & is not allowed |
918 | Command & not allowed |
919 | Log & was deleted |
920 | Logs older than & were deleted |
921 | Log older than & was not found |
922 | No conversion authorization |
923 | Invalid CONTROL parameter |
924 | Message number &, program & |
925 | Table name is missing |
926 | Table & defined as transparent (see Technical Settings) |
927 | & & already revised |
928 | Conversion of & from POOL to TRANSP successful |
929 | Conversion of & from POOL to TRANSP unsuccessful |
930 | Technical settings for table &: 'transparent' flag reset |
931 | Physical pool/cluster & changed to &; update them |
932 | Transparent flag set. Convert table & |
933 | Conversion from POOL (TRANSP cannot be executed) |
934 | Table & is a cluster table. Buffering not allowed |
935 | In the DB Utility select Restart log -> Restart for this table |
936 | Error reading inactive nametab, table & |
937 | Tables with long fields (> 255) cannot be converted. |
938 | Program for database adjustment could not be generated/executed |
939 | Technical settings (new): Version cannot be stored |
940 | Table & (Statements could not be generated) |
941 | Unexpected action (=&) or unexpected MODEFLAG (=&) |
942 | Table type change &->&. Database table must be created |
943 | Table type change &->&. Database table must be deleted |
944 | Table type change &->&. Database adjustment necessary |
945 | No log exists |
946 | Active table & is lang.-spec. (no translation type defined) |
947 | Active table & is not language-dependent (translation type is defined) |
948 | System type or name cannot be determined |
949 | Table & must be created in the database |
950 | *****************ABAP Development Workbench************************** |
951 | & already exists; choose another name |
952 | & does not exist; check the name |
953 | Action was canceled |
954 | You are not authorized to delete & |
955 | Object name missing. (Enter object name) |
956 | No allowed values defined for domain & |
957 | Set of values for domain & defined using allowed values |
958 | Active version of & does not contain values |
959 | Only an active version of the technical settings exists |
960 | & (entry does not exist yet) |
961 | ==> Index activation................. & Round : & |
962 | Table screen was created |
963 | & was not deleted |
964 | & was not saved (correction entry not possible) |
965 | Value & is not numeric |
966 | Length of value & exceeds domain length (correct) |
967 | Entry deleted |
968 | Entry was not deleted |
969 | All entries were deleted |
970 | Entry already exists; enter another value |
971 | Initial value not allowed in this field |
972 | Choose only one option |
973 | & does not exist (action not possible) |
974 | Field &-& (type & no longer supported from Release & onwards) |
975 | Field &-& (type & is no longer supported) |
976 | Function not supported |
977 | Operation terminated with errors |
978 | Internal error occurred (unknown object) |
979 | Activate domain & (active version) |
980 | Activate table & (Active version) |
981 | Domain & (data type VARC no longer supported from Release 3.0) |
982 | Request terminated with errors (see log) |
983 | A job has already been scheduled for the object |
984 | Not possible select translation type |
985 | Entered for background processing (check job scheduling) |
986 | Table change made makes table language-dependent |
987 | Table & is no longer language-dependent |
988 | Technical settings for & are already being edited |
989 | Defined translation type & is not known |
990 | Active table & is language-dependent (standard translation type set) |
991 | Active table & is not language-dependent (translation type deleted) |
992 | Language-dependent table & (no field with TYPE & in key) |
993 | Language-dependent table & (no text field in data part) |
994 | K11-&: Structure changes in K11 only when approved by development manager |
995 | K11-&: Cluster-->pool in K11 only when approved by development manager |
996 | K11-&: Pool-->cluster in K11 only when approved by development manager |
997 | K11-&: Pool/cluster-->TRANSP in K11 only when approved by manager |
998 | K11-&: TRANSP-->pool/cluster in K11 only when approved by manager |
999 | Activation currently locked (F1) |