DI - Dictionary-Nachrichten: Bereich Indizes, Enqueues, DB-Funcs
The following messages are stored in message class DI: Dictionary-Nachrichten: Bereich Indizes, Enqueues, DB-Funcs.
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 | ****************** Create Indexes in the Database ******************** |
| 002 | Index &-& is not in ABAP Dictionary |
| 003 | Index &-& is inconsistent in ABAP Dictionary |
| 004 | Index & already exists in the database |
| 005 | Table & for index & is not in the database |
| 006 | Index & could not be created completely in the database |
| 007 | Table & is not active in ABAP Dictionary |
| 008 | Type of table & does not allow any indexes |
| 009 | Index &-& (client field required for unique index) |
| 010 | Index &-& (total of field lengths exceeds allowed value) |
| 011 | Do not create the index &-& on the database |
| 012 | Index &-& could not be saved |
| 013 | Index &-&: Database HDB could not be excluded |
| 014 | Index &-& introduced DB-based, exception list created, & added |
| 015 | Index &-& already existed DB-based, exception list created, & added |
| 016 | Index &-& already existed DB-based with inclusion list, no change for & |
| 017 | Index &-& already existed DB-based, exception list existed, & added |
| 018 | Index &-& will not be created on any DB; no action necessary for & |
| 019 | Index &-& was already defined DB-based and & existed in the except. list |
| 020 | Activation of indexes - see log & |
| 021 | Save Indexes Table & (&) |
| 022 | Table &: Indexes are not selected as DB-specific |
| 023 | Index &-& is defined by exactly one column |
| 400 | ====================== = DB Procedure Proxy ============================= |
| 401 | Activates database procedure proxy & |
| 402 | Database procedure proxy & was activated |
| 403 | Database procedure proxy & was activated with warnings |
| 404 | Database procedure proxy & was not activated |
| 405 | A DB procedure proxy cannot be activated as dependent/active object |
| 750 | ******Messages on lock objects************** |
| 751 | Base table & of the lock object is not active |
| 752 | Base table & of lock object does not have any fields |
| 753 | No foreign key fields found for check field &-& |
| 754 | No foreign key definition found for check field &-& |
| 755 | Field &-& is checked against multiple key fields using join condition |
| 756 | Field &-& may only be checked against key fields |
| 757 | Field &-& may not be checked against field &-& |
| 758 | Name & not allowed for lock parameter |
| 759 | Lock parameter & meaningless, as it does not refer to a lock argument |
| 760 | There is a lock parameter without a name |
| 761 | Internal error (a check was not made) |
| 762 | Lock object is not active |
| 763 | Incorrect name & in the header of the lock object |
| 764 | Incorrect aggregate type & in the header of the lock object |
| 765 | Base table & is assigned to incorrect lock object & |
| 766 | Inconsistent entry for the primary table of the lock object |
| 767 | Lock object has no base tables |
| 768 | Lock mode for table & is assigned to incorrect lock object & |
| 769 | Lock parameter & is assigned to incorrect lock object & |
| 770 | Lock object does not exist |
| 771 | Lock object does not have any lock parameters |
| 772 | Multiple lock parameters have the name & |
| 773 | Basis table & occurs more than once |
| 774 | Lock mode for table & meaningless since no base table exists |
| 775 | Base table & of lock object has table type & |
| 776 | Total length of lock argument for table & longer than & |
| 777 | Name of lock object does not start with a letter |
| 778 | Name of lock object contains only invalid letter & |
| 779 | Name of lock parameter & is invalid since it contains & |
| 780 | Name of lock parameter & invalid since it does not start with a letter |
| 781 | Lock parameter name & contains nonalphanumeric characters (invalid) |
| 782 | Obsolete function group & deleted |
| 783 | Lock parameter name & starts with 'X_' and is thus invalid |
| 784 | Lock parameter name & starts with 'MODE_' and is thus invalid |
| 785 | Parameter field &-& belongs to multiple lock parameters |
| 786 | Parameter field &-& of lock parameter & does not exist |
| 787 | Parameter field &-& of lock parameter & is not in base table |
| 788 | Position of base table & incorrectly maintained |
| 789 | No table can be locked with the lock object |
| 790 | No lock mode was defined for base table & |
| 791 | Secondary table & refers to itself |
| 792 | Secondary table & bound to incorrect foreign key type using join |
| 793 | No valid join conditions found for secondary table & |
| 794 | Predecessor table & for base table & is not a base table |
| 795 | Predecessor table & for base table & does not follow this in hierarchy |
| 796 | Lock field &-& does not have a character-like type |
| 797 | Inconsistent join of basis table & to predecessor table & (check field &) |
| 798 | Parameter field &-& for lock parameter & is not a key field |
| 799 | Parameter field &-& for lock parameter & is a foreign key field |
| 800 | Foreign key field &-& for join of table & is not a key field |
| 801 | Join condition for secondary table & with adjusted foreign key |
| 802 | For. key field &-& for join cond. to sec. table & not in base table |
| 803 | Join condition for secondary table & conflicts with the hierarchy |
| 804 | Lock mode & for table & is not allowed |
| 805 | Check lock object & |
| 806 | Activate lock object & |
| 807 | Lock object & is consistent |
| 808 | Lock object & was checked with warnings |
| 809 | Lock object & is inconsistent |
| 810 | Lock object & could not be checked |
| 811 | Lock object & activated |
| 812 | Lock object & was activated with warnings |
| 813 | Lock object & not activated |
| 814 | Lock object & activated without generating the function modules |
| 815 | Function group & could not be generated |
| 816 | The program code for the &EUE module could not be generated |
| 817 | Lock object & activated without generating the FMs with warnings |
| 818 | Generate function modules for lock object & |
| 819 | Function modules for lock object & could not be generated |
| 820 | Function modules for lock object & were generated |
| 821 | Lock parameter & has the same name as a base table |
| 822 | Lock argument for table & cannot be determined |
| 823 | Maximum number & of tables to be locked exceeded |
| 824 | Maximum number & of lock parameters exceeded |
| 825 | Lock parameter name & has more than & characters and is thus invalid |
| 826 | Parameter field for lock parameter & is not a component of base table |
| 827 | Parameter field for lock parameter & is not elementary type |
| 828 | Type of lock field &-& is not suitable |
| 829 | The program code for the &EUE module could not be generated |
| 830 | Check dependent lock object & |
| 831 | Generate function module for dependent lock object & |
| 832 | Activate dependent lock object & |
| 833 | Dependent lock object & was not activated |
| 834 | Dependent lock object & activated with warning (no FM generated) |
| 835 | Dependent lock object & was activated with warning |
| 836 | Dependent lock object & activated without generating the function modules |
| 837 | Dependent lock object & was activated |
| 838 | &1 and &2 lock objects were activated |
| 840 | Namespaces EY and EZ are reserved for (customer) lock objects |
| 850 | The interfaces were adjusted for &1 lock objects |
| 851 | Application: ABAP Dictionary (Basis), Client: * |
| 852 | Interface of lock object &1 could not be updated |
| 853 | No lock objects need be adjusted |
| 854 | No authorization for executing this program |
| 900 | ******************* General Messages ********************************** |
| 901 | Internal error (Form: &. Parameter: & & &) |