DO - DD: Dom�nen-, Datenelement-, Massenaktivierung
The following messages are stored in message class DO: DD: Dom�nen-, Datenelement-, Massenaktivierung.
It is part of development package SDAD in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP Dictionary: Cross-Object, Mass Processing".
It is part of development package SDAD in software component BC-DWB-DIC-AC. This development package consists of objects that can be grouped under "ABAP Dictionary: Cross-Object, Mass Processing".
Message Nr ▲ | Message Text |
---|---|
000 | *Content: 001 TTYP/100 DOMA/300 DTEL/500 Massact./700 Massdel./800 TTYP |
001 | *** Table types ********************************************************* |
002 | *** 002 - 030: Messages for ranges table types |
003 | Row type & of ranges table type has no component & |
004 | Type of comp. & in row type is not allowed for ranges table type |
005 | Type of component & in row type does not match reference type |
006 | Order of components in row type & not allowed for ranges table types |
007 | Structure of row type & is not allowed for ranges table types |
008 | Key category for ranges table type corrected to non-unique |
009 | Access mode for ranges table type corrected to standard table |
010 | Key for ranges table type corrected to standard key |
011 | Associated type for components LOW and HIGH not specified |
012 | Associated type & for components LOW and HIGH does not exist |
013 | Associated type &: Reference types not allowed as associated types |
014 | The row type must be a structure for ranges table types |
031 | Runtime object of row type & does not exist as active |
100 | *** Domains ************************************************************* |
101 | *** 100 - 149: General messages relating to domain activation |
102 | Activate domain & |
103 | Domain & activated |
104 | Domain & not activated |
105 | Check domain & |
106 | Domain & is correct |
107 | Domain & is inconsistent |
108 | Termination of check / activation of domain & |
109 | Domains......: &/&/&/& (number/confirmations/warnings/errors) |
110 | Start of adjustment of & dependents |
111 | End of adjustment of dependents |
112 | Outstanding actions: & & & & |
113 | Actions to be performed for dependent objects: & & & & |
114 | Adjustments for dependent objects: |
115 | Adjustment as dependent object: & & & & |
116 | Domain & could not be expanded |
119 | Domain & could not be read |
120 | Changes can cause dependent tables to be updated |
121 | No conversion necessary in dependent tables |
122 | Dependent objects were not activated |
123 | Change causes adjustment of the dependent tables and structures |
124 | Change causes adjustment of dependencies and possible updates |
125 | & dependent structure(s): |
126 | & dependent table(s): |
127 | & dependencies: & table(s), & structure(s) |
128 | Take note |
129 | Long text of message |
130 | Domain &1: Dep. table &2 not adjusted (online) |
131 | Domain &1: Dependent table &2 not adjusted (mass activator) |
135 | Activation caused by domain & |
170 | *** 171 - 179: Messages about checks of the domain name (namespace) |
171 | Namespace in name & does not begin at 1st position |
172 | Name & only consists of the namespace |
173 | Number of '/' in name & is incorrect |
174 | Namespace in name & is empty |
175 | Attributes of domain & reset (protected domain) |
180 | *** 181 - 189: Messages relating to flag checks |
181 | For flag & the value & is not allowed |
182 | Flag & is corrected to & (value & not allowed) |
183 | Fixed values are deleted as flag VALEXI is not set |
184 | Flag VALEXI is reset as no fixed values exist |
185 | Lowercase letters are reset (not meaningful for &) |
186 | Lowercase letters are switched on (are defined for &) |
190 | *** 191 - 219: Messages regarding checks of fixed values |
191 | Fixed value definition is not allowed for data type & |
192 | There is no check on the mask for data type & |
193 | Upper fixed value limits are deleted (language-dependent) |
194 | Length of fixed value &1 > maximum number of characters (&2) |
195 | Fixed value/limit & for data type & must be a whole positive number |
196 | Fixed values/limits do not correspond to data type attributes |
197 | Fixed value / lower limit & reoccurs |
198 | Fixed value upper limit & reappears |
199 | Fixed values/limits reappear |
200 | Fixed value/limit & for data type & is less than the minimum value & |
201 | Fixed value range [&,&] defines a single fixed value |
202 | Lower fixed value limit & > upper fixed value limit & |
203 | Fixed value range(s) define(s) a single value |
204 | Fixed value range(s) is (are) not correct ranges |
205 | Fixed value & is within value range [&,&] |
206 | Fixed value range [&,&] and [&,&] overlap |
207 | Fixed value range [&,&] is not identical in ASCII and EBCDIC |
208 | Fixed value ranges and/or single values not disjoint |
209 | Fixed value range/s not identical in ASCII and EBCDIC |
210 | Fixed Value Append: At least one fixed value must be maintained |
211 | Fixed value/limit & for data type & is greater than the maximum value & |
220 | *** 221 - 239: Messages relating to value table checks |
221 | Domain & is not key domain of value table & |
222 | Table & is also a value table for other domains |
223 | Value table & does not exist |
224 | Check table & is not a table (&) |
225 | Value table & is not active |
226 | Value table & changed; check the foreign key |
227 | Value table & changed; foreign keys are preserved |
228 | & Foreign key: & & & |
229 | A value table is not allowed for data type & |
240 | *** 240 - 249: messages or conversion routines |
241 | Conversion routine & does not exist |
242 | Conversion routine & is corrected (is defined for &) |
243 | A conversion routine is not allowed for data type & |
250 | *** 251 - 279: Messages rel. to data type checks, resvd. with table act. |
251 | Data type & does not exist |
252 | Data type & is no longer supported |
253 | Number of positions < minimum number (&) for data type & |
254 | Number of positions > maximum number (&) for data type & |
255 | Maximum length (&) for & in transparent tables exceeded |
256 | Number of positions corrected to & (as > maximum length (&) for &) |
257 | Number of positions is corrected to & (defined for &) |
258 | Decimal places removed (invalid for &) |
259 | Decimal places are corrected to & (defined for &) |
260 | Decimal places are corrected to & (default value for &) |
261 | Decimal places modified to & places |
262 | Output length for data type & must be at least & |
263 | Output length (&) is less than the calculated output length (&) |
264 | Output length is corrected to & (defined for &) |
265 | Output length is corrected to & (according to number of positions &) |
266 | Output length (&) is greater than the calculated output length (&) |
267 | Sign flag is reset (not meaningful for &) |
268 | Number of places is reset (& has variable length) |
269 | Output length (&) is greater than maximum output length (&) on dynpros |
270 | Attributes of data type & are corrected (have fixed assignments) |
271 | Decimal places, signs are reset (not meaningful for &) |
272 | Output length will be reset (& has variable output length) |
273 | Output style will be reset (value itself or for type & not appropriate) |
274 | Decimal places are not allowed for & |
275 | No length restriction |
276 | Output length will be corrected to & (maximum output length for UNIT) |
277 | Number of decimal places & is not correct for data type & |
278 | Number of decimal places & is too large for data type & |
279 | Number of decimal places & cannot be larger than length & |
280 | Number of places for data type & is fixed and must be equal to & |
281 | Number of decimal places for data type & is fixed; must be equal to & |
282 | Could not load list of coordinate systems; SQL code & & |
283 | Coordinate system &1 is not defined |
300 | *** Data elements ******************************************************* |
301 | Activate data element & |
302 | Check data element & |
303 | Data element & was not activated |
304 | Data element & is inconsistent |
305 | Heading in language &: length & > maximum length & |
306 | Heading in languages &: length > maximum length & |
307 | Short key word in language &: length & > maximum length & |
308 | Short key word in languages &: length > maximum length & |
309 | Medium key word in language &: length & > maximum length & |
310 | Medium key word in languages &: length > maximum length & |
311 | Long key word in language &: length & > maximum length & |
312 | Long key word in languages &: length > maximum length & |
313 | Parameter ID & is not contained in table TPARA |
314 | No domain specified |
315 | No active domain & available |
316 | Data element & could not be read |
317 | &: Data element & could not be written |
318 | &: Data elements could not be written |
319 | &: Data element & could not be read |
320 | Dependent ...: &/&/&/& (number/successes/warnings/errors) |
321 | Data elements: &/&/&/& (number/successes/warnings/errors) |
322 | Time stamp of table & was updated |
323 | Time stamp of table & could not be updated |
324 | ===== Start of dependency handling ===== |
325 | Activation must be in the background |
326 | The data element is used in too many tables and programs |
327 | & dependent tables found (maximum permitted &) |
328 | & not suitable for field definition |
329 | & is partial (missing domain specification permitted) |
330 | Value is corrected to & |
331 | Runtime object of table & was updated |
332 | Runtime object of table & could not be updated |
333 | Activation of data element & successful |
334 | Check of data element & successful |
335 | Activation caused by data element & |
336 | Check texts of data element & |
337 | Data element & was activated |
338 | Domain append & cannot be used for definition |
339 | Data element defined recursively |
340 | Data type attributes changed. Check dependent views. |
341 | Changes can cause dependent tables to be updated |
342 | No conversion necessary in dependent tables |
343 | Change causes adjustment of dependencies |
344 | Change causes adjustment of dependencies and possible updates |
345 | Heading in language &: length & > maximum length & |
346 | Short key word in language &: length & > maximum length & |
347 | Medium key word in language &: length & > maximum length & |
348 | Long key word in language &: length & > maximum length & |
349 | Attributes of the data element were corrected |
350 | *** Messages regarding data elements for where-used list/deletion |
351 | Data element & is still being used in table/structure & |
352 | Data element & is still being used in aggregate & |
353 | Heading: Length & > maximum length allowed & |
354 | Short Keyword: Length & > maximum allowed length & |
355 | Medium keyword: Length & > maximum allowed length & |
356 | Long keyword: Length & > maximum allowed length & |
357 | Bidirectional option basic direction for data type & cannot be set |
358 | Bidirectional option BIDI filter for data type & cannot be set |
360 | *** Messages about data element as dependent object |
361 | Activate dependent data element & |
362 | Dependent data element & was not activated |
363 | Activation of dependent data element & successful |
370 | *** 370 - 398: Messages for data type attribute checks |
371 | No domain or data type was defined |
372 | Referenced class or interface & not active/implemented |
373 | Referenced data type & is not active |
374 | User type & is a generated proxy type |
375 | Error from ABAP language version layer: &1 &2 &3 &4 |
379 | Could not determine ABAP language version for object &2 (&1) |
399 | *** 399 - 418: Messages for nametab generation for the data element |
400 | Runtime object for data element & could not be generated |
401 | Runtime object for data element & could not be written |
402 | Active runtime object already exists for another object type |
403 | Time stamp of data element & could not be updated |
404 | Time stamp of data element & was updated |
405 | Runtime object of data element & was updated |
406 | Runtime object for data element & could not be updated |
407 | Inactive runtime object for data element & could not be written |
408 | Active runtime object written for data element & |
409 | Header of runtime object for & could not be read |
410 | Runtime object for & could not be read |
411 | Header of runtime object for & could not be written |
412 | Runtime object of & could not be written |
419 | *** 419 - 430: Messages about search help checks for data elements |
420 | Search help binding is incomplete (name or parameter missing) |
421 | Search help &1 is not active or does not have parameters |
422 | Search help &1 does not have parameter &2 |
423 | Search help parameter &1-&2 is not an EXPORT parameter |
424 | Type of search help parameter &1-&2 is incompatible with the data element |
425 | Search help assignment not allowed for reference types |
426 | Search help assignment not allowed for data type & |
431 | Type & for component & is not active |
435 | *** 436 - 445: Messages about checks of other data element attributes |
436 | Change documents reset (not meaningful for reference types) |
437 | Parameter ID not allowed for reference types |
438 | Parameter ID not allowed for data type & |
439 | Change documents reset (meaningless for data type &) |
440 | & is the name of a built-in data type in the dictionary |
450 | *** 450 - 460: Messages about Table Attributes e.g. for Table Fields |
451 | Decimal places are corrected to & (max. number of decimal places) |
480 | *** Mass Activation Program ********************************************* |
481 | & & &: Home object, will be ignored |
482 | Table GENTAB could not be persisted |
483 | Objects of basic quantity written to DB: & |
484 | Table & could not be imported |
485 | Level &: & objects read from the database |
486 | & dependencies read from the database |
487 | Error in persistence management of internal control tables |
488 | Determining dependencies & -> & |
489 | Determining dependencies & refTo & |
490 | Determining dependencies & refTo & (&) |
491 | Determining dependencies & -> & (&) |
492 | >>> Determination of Dependencies Between Types: Repeat & |
493 | View & is treated as a dependent view |
494 | Error when generating a UUID for mass activation |
495 | >>> Determine dependencies by association: Retry & |
496 | >>> Determine dependencies by association (too many iterations): & |
497 | UUID..........................: &1 |
499 | &1 &2: Could not generate runtime object |
500 | Newest version of & & already activated; active version not activated |
501 | & & &: deletion information could not be imported |
502 | & & & (& version) was not deleted (check references) |
503 | Number of objects not deleted...............: & |
504 | & & & (A version) was deleted; error in dependent table & |
505 | & & & (N and A version) was deleted; error in dependent table & |
506 | Object & & & was already deleted |
507 | Object & & & was already deleted and recreated |
508 | ==> Reactivation of dependent views............: & |
509 | Error when reactivating the dependent views |
510 | *** Reactivation of dependent views |
511 | Reference log for & & & could not be created |
512 | Caused by mass activation >>> (see log &) |
513 | Check mode may only have values from the set {'O','T','U'} |
514 | No object to be deleted and activated exists |
515 | & &: Could not update activation flag |
516 | & & & could not be activated |
517 | & & was activated (error in the dependencies) |
518 | & & & was activated with warnings |
519 | $ $ could not be activated |
520 | & & was activated with warnings |
521 | Request & for index &-& was marked for mass processing |
522 | Request & for index &-& could not be marked for mass processing |
523 | Temporary SQLT log & could not be deleted (&) |
524 | Activate active version of view & |
525 | Activate dependent view & |
526 | View was activated with warnings |
527 | & &: Header of runtime object does not exist |
528 | & &: Indicator for existence of buffered views reset |
529 | & &: Active runtime object does not exist |
530 | & &: Could not write runtime object header |
531 | & &: Could not write runtime object |
532 | & &: Time stamp was updated |
533 | *** Activate objects at level & |
534 | Object & & & was already activated |
535 | Error when selecting the successful activations in the transport request |
536 | & & could not be activated |
537 | & & was activated with warnings |
538 | DD sources table & could not be read |
539 | Runtime object for & could not be generated |
540 | Active runtime object for & could not be written |
541 | Inactive runtime object for & could not be written |
542 | Runtime object for & updated |
543 | Time stamp of runtime object for & updated |
544 | Mass activation already running (user &). Parallel run not allowed. |
545 | & & &: Object information could not be imported |
546 | (&) |
547 | Activate active version of search help & |
548 | Activate dependent search help & |
549 | & & was activated (warning for the dependent tables) |
550 | **** Graphic algorithms **** |
551 | Level &: & objects assigned, & fewer dependencies |
552 | > Cycle at level & |
553 | Request & for lock object & marked for mass processing |
554 | Request & for lock object & not marked for mass processing |
555 | & partitions with & objects |
556 | & partitions |
557 | No. of selected dependencies: & |
558 | Number of relevant dependencies: & |
559 | Dependencies are ignored in order to allocate object & & & |
560 | The following objects participate in cycles: |
561 | Number of objects to be analyzed: & |
562 | Error in DD_GRAPH_ANALYSE: Cycle could not be resolved |
563 | Level &: Preliminary allocation of & objects from cycles |
564 | Level &: & dependencies removed for cycle resolution |
565 | Cycle analysis: & remaining, & relevant transitive dependencies |
566 | Cycle analysis: & objects in & cycles at & levels |
567 | Object: & Cycle: & Level: & |
568 | Level &: Cycle resolution for cycle & on level & |
569 | Preliminary allocation of object & & & on level & |
570 | & -> & (&) |
571 | The following dependencies can be removed for this reason: |
572 | Error trace: Cycle objects/Dependencies/Remaining objects |
573 | Error calling DD_GRAPH_ANALYSIS corrected: OBJLIST contains duplicates |
574 | &1 type loads invalidated in &2 seconds |
578 | The following errors or warnings have occurred: |
579 | DD sources table type & could not be read |
580 | DD sources data element & could not be read |
581 | Request & for table & is marked for mass processing. |
582 | Request & for table & could not be marked for mass processing |
583 | Request & (DROP/CREATE) for view & marked for mass processing |
584 | Request & for view & could not be marked for mass processing |
585 | & &: DROP/CREATE is ignored because of parallel request for activation |
586 | & & (& version) was not deleted (check references) |
587 | & & (& version) was deleted (check references) |
588 | & & & (& version) was not deleted (check references) |
589 | & & & (& version) was deleted (check references) |
590 | Table & is used in & as an INCLUDE table |
591 | & is still used as & in & & |
592 | & is still used in & & |
593 | Table & is stored in table pool/cluster |
594 | Transport request: Delete/recreate the view |
595 | View & was deleted and created again |
596 | Transport request: Activate with deletion/creation |
597 | Table type &: Row type & does not exist. Nametab cannot be created. |
598 | Table type &: Inactive runtime object could not be written |
599 | Unicode nametabs are not created |
600 | Statistics on activated and deleted objects |
601 | Number of objects to be activated............: & |
602 | Number of objects to be deleted..............: & |
603 | Activated objects...............: & |
604 | Objects activated with warning...............: & |
605 | Objects not activated........................: & |
606 | Activated objects with errors in dependencies: & |
607 | Deleted objects.................: & |
608 | Objects not deleted..........................: & |
609 | Tables/views with DROP/CREATE................: & |
610 | No. of them marked for DROP/CREATE: & |
611 | Not marked for DROP/CREATE: & |
612 | Inactive runtime object for table & was written |
613 | Activate active version of lock object & |
614 | Activate dependent lock object & |
615 | Active runtime object & & was written |
616 | Active runtime object & & could not be written (&) |
617 | & nametab & was deleted |
618 | & nametab & was not deleted |
619 | The nametab could not be deleted for the following objects: |
620 | Number of nametabs to be deleted.............: & |
621 | Nametabs not deleted.........................: & |
622 | Deleted nametabs.............................: & |
623 | Delete & & & |
624 | Objects at level & |
625 | Activate & & & |
626 | & & & & |
627 | Table & are not the same before and after level activation |
628 | Table & are not the same before and after level activation |
629 | Cannot delete and recreate table DDFTX |
630 | ****** Reserved: asynchronous parallel processing 630-649 + 675-699 |
631 | * Parallel execution with maximum of &1 concurrent tasks * |
632 | * Server resources ****************************************************** |
633 | Total of & objects in & tasks |
634 | * Synchronous execution, no parallel processing * |
635 | Not enough work processes (& in total, & can be used) |
636 | Not enough objects (&) for parallel execution. Minimum: & |
637 | & !! No task received for & seconds already. Running tasks: |
638 | Task & started & on server & |
639 | Too low costs (&) for parallel processing. Minimum: & |
640 | & -> task & start error [&]: & |
641 | RC=&: && |
642 | & => task & started [&] & |
643 | & <= task & completed [&] & |
644 | & <- task & receiving error [&] & |
645 | & <> task & started synchronously [&] & |
646 | & .. Start attempt for task & after & seconds |
647 | & .. Start attempt for task & after return from another task |
648 | Error in task management: & tasks open |
649 | Program error in &: Illegal mode & in Start_Task in RUTBTPA0 |
650 | ***** Continuation Graph_analysis 650-660 (+ 550-571) ****** |
651 | Graph_Analysis: & objects in & partitions and on & topological levels |
652 | Graph_Analysis: & objects in & partitions |
653 | Graph_Analysis: & objects on & topological levels |
654 | & Switch Framework objects added to be activated, & to be deleted |
655 | & & could not be deleted |
656 | & & deleted (error in dependent ones) |
657 | & & deleted with warnings |
658 | & objects added as switch-dependent |
659 | BI namespaces could not be determined: Table & missing |
660 | *Reservation of Mass Activator*(660-675)********************************* |
661 | Object type & is unknown -> object will be removed from processing |
662 | Switchable object & & will not be activated (switched off) |
663 | Switchable index & & will not be activated (switched off) |
664 | Switchable object & & was not activated (switched off) |
665 | Switchable object & & with error was not activated (switched off) |
666 | Switchable object & & was switched off; dependent objects activated |
667 | Switchable index &-& was switched off |
668 | BI namespaces could not be determined: Function & does not exist |
669 | Objects from namespaces in Table RNSPACE will not be activated |
670 | BI object & & will be activated |
671 | Error while copying DDIC objects from switches |
672 | Invalidation type load buffer for: & & |
673 | Dependent view table & will be activated as a view |
674 | Table &: Request for user-defined conversion is not entered. |
675 | Creation of DB views & not possible; active DDL source & will be flagged |
676 | ******* Parallel processing 675-700, Continuation + (630-649) |
677 | Total of & objects with & costs in & tasks |
678 | Parallel execution: & sec., Phase out time: & sec., Load: & percent |
679 | No objects found for parallel processing |
680 | Synchronous processing: & sec., & objects, & costs |
681 | Dependent views for & & will be adapted |
682 | Dependent views for & could not be (completely) adapted |
683 | & & will be created on the database |
684 | & & could not be created on the database |
685 | & & could not be deleted from the database |
686 | Views will be created on the database |
687 | & & was deleted from the database |
688 | Views will be deleted from the database |
689 | Views will be created on the database |
690 | &-Version & will not be activated (DDL source & exists) |
691 | &-Version & will not be activated (DDL source exists) |
692 | Creation of DB view & is not possible; DDL source & will be reset |
693 | DDL source & was reset to inactive |
694 | DDL source & could not be reset to inactive |
695 | DDL source & marked as inactive |
696 | Deleting & & on database |
697 | Creating & & on database |
698 | Active DDL source & flagged |
699 | Could not flag active DDL source & |
700 | *** Mass deletion ******************************************************* |
701 | *** Mass deleter for ABAP Dictionary objects |
702 | REQUEST & |
703 | START & & |
704 | Domain & marked for deletion |
705 | Data element & marked for deletion |
706 | &1 &2: TADIR entry ignored due to DELFLAG |
707 | Table & marked for deletion |
708 | View & marked for deletion |
709 | Lock object & marked for deletion |
712 | Domain & is still referenced |
713 | Data element & is still referenced |
715 | Table & is still referenced |
716 | View & is still referenced |
717 | Lock object & is still referenced |
720 | & tables were deleted |
721 | & data elements were deleted |
722 | & domains were deleted |
724 | & views were deleted |
725 | & lock objects were deleted |
728 | Table & deleted |
729 | Data element & deleted |
730 | Domain & deleted |
732 | View & deleted |
733 | Lock object & deleted |
736 | Number of objects to be deleted: & |
737 | No transport request was specified |
738 | Number of referenced objects: & |
739 | Index & & for deletion marked |
740 | & indexes were deleted |
741 | Index & & deleted |
742 | Table & (technical settings cannot be deleted separately) |
744 | Delete nametab entries without DD sources |
745 | Nametab of & was deleted |
746 | Delete append structure & |
747 | Append structure & was deleted |
748 | Append structure & was not deleted |
749 | Activation caused by deletion of & |
750 | Delete customizing include & |
751 | Customizing include & was deleted |
752 | Customizing include & was not deleted |
753 | Search help & marked for deletion |
754 | & search helps were deleted |
755 | Deletion of search help & successful |
756 | Search help & is still being referenced |
757 | Table type & marked for deletion |
758 | & table types were deleted |
759 | Deletion of table type & successful |
760 | Table type & still being referenced |
761 | Structure & is referenced as component type in &-& |
762 | Structure & is referenced as row type in table type & |
763 | Data element & is referenced as row type in table type & |
764 | Reactivation of dependent objects in deleted append & |
765 | Table type & still being referenced |
766 | N version index &-& will not be deleted |
767 | Index &-& already has no source; deletion on DB will not be executed |
768 | & & will not be deleted |
769 | & & will be deleted as active version |
770 | *** Create DB-specific objects |
771 | *** Database system: & |
772 | *** Execution of & |
773 | *** No reports exist for this DB system in the DBD�FF |
774 | *** & create |
775 | DB procedure proxy & flagged for deletion |
776 | Structured object & flagged for deletion |
777 | DDL source & flagged for deletion |
778 | & & will not be deleted (either TADIR or N version exists) |
779 | & & will not be deleted (TADIR entry still exists) |
780 | & enhancement indexes deleted |
781 | Deletion of enhancement index & & successful |
782 | Enhancement index & & flagged for deletion |
783 | &1 &2 activated despite naming conflict |
784 | Activation of &1 &2 repeated due to naming conflict |
785 | Activation repeated for objects with errors |
786 | Activation repeated for objects with naming conflicts |
787 | Naming conflict: &1 is deleted as &2 and activated as &3 |
793 | Create index & on field & for table & |
794 | Could not create index & on field & for table & |
795 | Delete index & |
796 | Could not delete index & |
797 | View & was not deleted; table with same name exists |
798 | &-&: The active version of the index will be deleted |
800 | *** Table types ********************************************************* |
801 | *** 800 - 820: General messages on table type activation |
802 | Activation of table type & |
803 | Table type & was activated |
804 | Table type & was not activated |
805 | Check table type & |
806 | Table type & is correct |
807 | Table type & is inconsistent |
808 | Terminate check / activate table type & |
809 | Table types .......: &/&/&/& (number/successes/warnings/errors) |
810 | Table type & could not be read |
811 | Activate dependent table type & |
812 | Activate table type & (active version) |
813 | Table type & was activated with warnings |
814 | Activation caused by table type & |
815 | &: error while executing statements on the database |
816 | Runtime object & could not be read |
817 | *** 818 - 828 Messages about nametab/runtime object |
818 | The row type of table type & does not contain a component with the name & |
819 | Data type not allowed in table type & |
820 | Runtime object for table type & cannot be generated |
821 | Runtime object for table type & cannot be written |
822 | Time stamp for table type & was updated |
823 | Runtime object for table type & was updated |
824 | Runtime object for table type & cannot be updated |
825 | Time stamp for table type & could not be updated |
826 | & & contains fixed length information. Nametab creation is not necessary. |
827 | Inactive runtime object for table type & was written |
828 | Nametab for & used unchanged |
829 | *** 830 - 829 Messages on access mode, key category, generic ... |
830 | Access mode is reset to standard table |
831 | Key category is not valid |
832 | Key category for standard table corrected to non-unique |
833 | Key category corrected to not specified |
834 | Key category for hashed table corrected to unique |
835 | Key category for index table corrected to not specified |
836 | Key category for any table corrected to not specified |
837 | Table type & is a generic type |
838 | Key is reset to not specified |
839 | Generic table type not allowed (& uses) |
840 | Attributes of the table type are corrected |
841 | Initial number of lines & > maximum number of lines allowed (&) |
842 | Alias name must not be displayed |
843 | Generic table type is not allowed (usages exist) |
844 | *** 845 - 850 messages on row type |
845 | Row type & is not active or does not exist |
846 | No row type or data type was specified |
847 | Row type & is a generic table type |
848 | Row type not allowed as key (table type is row type) |
849 | Row type & is a view |
850 | No row type or data type was specified |
851 | *** 852 - 860 messages about key definitions |
852 | Key/Index contains a table (component & of row type) |
853 | Default key is empty (data type & is not character-like) |
854 | Default key is empty (no characterlike fields in row type) |
855 | Explicit key definition is not allowed (row type unstructured) |
856 | Key not set for explicit key definition |
857 | Standard key is empty (table type is row type) |
858 | &: Explicit key specification not allowed (row type unstructured) |
859 | &: Row type as key not allowed (table type is row type) |
860 | *** Messages for table type as dependent object |
861 | Activate dependent table type & |
862 | Dependent table type & was not activated |
863 | Dependent table type & activated |
864 | Table Type &: Select at least one component for the key |
869 | *** Delete table types |
870 | Delete table type & |
871 | Table type & is deleted |
872 | Table type & is not deleted |
873 | Table type & is still being used in structure & |
874 | Table type & is still being used in table type & |
880 | *** Messages about recursive definition |
881 | Table type is defined recursively |
882 | Secondary Index &: |
885 | *** Messages for explicit specification of key components |
887 | Key/Index component & already exists (key / index component &) |
888 | Key/Index component & is a table |
889 | Key/Index component & contains a table |
890 | Key/secondary index &: Component & does not occur in row type |
891 | Key components are not defined |
892 | Key/Index &: Component &: A name is too long (maximum & characters) |
893 | Key/Index &: Comp.&: Namespace in name & does not begin with 1st position |
894 | Key/index &: component &: name & only consists of namespace |
895 | Key/Index &: Comp. &: Number of '/' in name & is not correct |
896 | Key/Index &: Component & contains blanks |
897 | Key/Index &: Component & contains invalid characters |
898 | Key/Index &: Component &: Namespace in name & is empty |
899 | Key/Index component &: A name is missing |
900 | *********************Mass Activation Program***************************** |
901 | Total import of data element text |
902 | Table & could not be deleted |
903 | Table & could not be created |
904 | Table & deleted and created again |
905 | DROP/CREATE runtime object with Screen Painter texts |
906 | Total import of table texts |
907 | DROP/CREATE runtime object with Screen Painter texts already executed |
908 | Delete text runtime object info for table & |
909 | Could not create temporary copy of DDFTX |
910 | Could not activate temporary copy of DDFTX |
911 | Table DDFTX was copied to & |
912 | Copy & of DDFTX was activated |
913 | Table DDFTX deleted from the database |
914 | Could not delete table DDFTX from the database |
915 | Table & was renamed as DDFTX in the database |
916 | Could not rename table & as DDFTX in the database |
917 | Copy & of DDFTX: DD sources and runtime object deleted |
918 | Copy &: Could not delete DD sources and runtime object |
919 | Could not delete index & in table & |
920 | Index & in table & deleted |
921 | Indexes in table & were created with the name of table & |
922 | Could not create indexes in table & with name of & |
923 | Transfer order does not exist |
924 | Used type & is not allowed |
925 | Object & & does not exist |
926 | Deleting entries in text runtime object in language & |
927 | Screen Painter texts in language & could not be deleted |
928 | Screen Painter texts in language & deleted |
929 | The following operations were performed on the runtime object: |
930 | Database proc. proxy & deleted |
931 | & DB proc. proxies were deleted |
932 | DB proc. proxy & is still referenced |
933 | & structured objects were deleted |
934 | Structured object & is still referenced |
935 | & DDL sources were deleted |
936 | DDL source & is still referenced |
937 | Structured object & deleted |
938 | DDL source & deleted |
939 | Dependency rule &1 was deleted |
940 | Dependency rule & deleted |
941 | & & &: Object not activated in BW generation namespace |
942 | New runtime object created for dependent object & & |
950 | ***** Secondary Indexes ************************************************* |
951 | Secondary Index &: Access mode & is not a valid value |
952 | Secondary Index &: Indicator for Unique & is not valid |
953 | Secondary Index &: Type of index & has no valid value |
990 | *** RADCUCNT: Unicode Conversion |
991 | Type conversion for & & not possible |