SAP ABAP Message Class DI (Dictionary messages: Indexes)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷
SDIC (Package) ABAP Dictionary
⤷
⤷
Attributes
| Message class | DI | |
| Short Description | Dictionary messages: Indexes | |
| Changed On | 20140121 | |
| Last Changed At | 105017 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | ****************** Create Indexes in the Database ******************** | |||
| 2 | Index &-& is not in ABAP Dictionary | Space: object requires documentation | ||
| 3 | Index &-& is inconsistent in ABAP Dictionary | Space: object requires documentation | ||
| 4 | Index & already exists in the database | |||
| 5 | Table & for index & is not in the database | |||
| 6 | Index & could not be created completely in the database | Space: object requires documentation | ||
| 7 | Table & is not active in ABAP Dictionary | Space: object requires documentation | ||
| 8 | Type of table & does not allow any indexes | |||
| 9 | Index &-& (client field required for unique index) | Space: object requires documentation | ||
| 10 | Index &-& (total of field lengths exceeds allowed value) | |||
| 11 | Index &-& should not be created on the DB | Space: object requires documentation | ||
| 12 | Index &-& could not be saved | The short text describes the object sufficiently | ||
| 13 | Index &-&: Database HDB could not be excluded | The short text describes the object sufficiently | ||
| 14 | Index &-& introduced DB-based, exception list created, & added | The short text describes the object sufficiently | ||
| 15 | Index &-& already existed DB-based, exception list created, & added | The short text describes the object sufficiently | ||
| 16 | Index &-& already existed DB-based with inclusion list, no change for & | The short text describes the object sufficiently | ||
| 17 | Index &-& already existed DB-based, exception list existed, & added | The short text describes the object sufficiently | ||
| 18 | Index &-& will not be created on any DB; no action necessary for & | The short text describes the object sufficiently | ||
| 19 | Index &-& was already defined DB-based and & existed in the except. list | The short text describes the object sufficiently | ||
| 20 | Activation of indexes - see log & | The short text describes the object sufficiently | ||
| 21 | Save Indexes Table & (&) | The short text describes the object sufficiently | ||
| 22 | Table &: Indexes are not selected as DB-specific | The short text describes the object sufficiently | ||
| 23 | ====================== = DB Procedure Proxy ============================= | The short text describes the object sufficiently | ||
| 24 | Activates database procedure proxy & | The short text describes the object sufficiently | ||
| 25 | Database procedure proxy & was activated | The short text describes the object sufficiently | ||
| 26 | Database procedure proxy & was activated with warnings | The short text describes the object sufficiently | ||
| 27 | Database procedure proxy & was not activated | The short text describes the object sufficiently | ||
| 28 | A DB procedure proxy cannot be activated as dependent/active object | The short text describes the object sufficiently | ||
| 29 | ******Messages on lock objects************** | |||
| 30 | Base table & of the lock object is not active | |||
| 31 | Base table & of lock object does not have any fields | |||
| 32 | No foreign key fields found for check field &-& | |||
| 33 | No foreign key definition found for check field &-& | |||
| 34 | Field &-& is checked against several key fields via join condition | |||
| 35 | Field &-& may only be checked against key fields | |||
| 36 | Field &-& may not be checked against field &-& | |||
| 37 | Name & not allowed for lock parameter | |||
| 38 | Lock parameter & meaningless, as it does not refer to a lock argument | |||
| 39 | There is a lock parameter without a name | |||
| 40 | Internal error (a check was not made) | |||
| 41 | Lock object is not active | |||
| 42 | Incorrect name & in the header of the lock object | |||
| 43 | Incorrect aggragate type & in the header of the lock object | |||
| 44 | Base table & is assigned to incorrect lock object & | |||
| 45 | Inconsistent entry for the primary table of the lock object | |||
| 46 | Lock object has no base tables | |||
| 47 | Lock mode for table & is assigned to incorrect lock object & | |||
| 48 | Lock parameter & is assigned to incorrect lock object & | |||
| 49 | Lock object does not exist | |||
| 50 | Lock object does not have any lock parameters | |||
| 51 | There are several lock parameters called & | |||
| 52 | Base table & occurs several times | |||
| 53 | Lock mode for table & meaningless since no base table exists | |||
| 54 | Base table & of lock object has table type & | |||
| 55 | Total length of lock argument for table & longer than & | Space: object requires documentation | ||
| 56 | Name of lock object does not start with a letter | |||
| 57 | Name of lock object contains only invalid letter & | |||
| 58 | Name of lock parameter & is invalid since it contains & | |||
| 59 | Name of lock parameter & invalid since it does not start with a letter | |||
| 60 | Lock parameter name & contains nonalphanumeric characters (invalid) | |||
| 61 | Obsolete function group & deleted | Space: object requires documentation | ||
| 62 | Lock parameter name & starts with 'X_' and is thus invalid | |||
| 63 | Lock parameter name & starts with 'MODE_' and is thus invalid | |||
| 64 | Parameter field &-& belongs to several lock parameters | |||
| 65 | Parameter field &-& of lock parameter & does not exist | |||
| 66 | Parameter field &-& of lock parameter & is not in base table | |||
| 67 | Position of base table & incorrectly maintained | |||
| 68 | No table can be locked with the lock object | |||
| 69 | No lock mode was defined for base table & | |||
| 70 | Secondary table & refers to itself | |||
| 71 | Secondary table & linked via join to incorrect foreign key type | |||
| 72 | No valid join conditions found for secondary table & | |||
| 73 | Predecessor table & for base table & is not a base table | |||
| 74 | Predecessor table & for base table & does not follow this in hierarchy | |||
| 75 | Lock field &-& is not of character type | |||
| 76 | Join of base table & to predecesspr table & via check field & inconsist. | |||
| 77 | Parameter field &-& for lock parameter & is not a key field | |||
| 78 | Parameter field &-& for lock parameter & is a foreign key field | |||
| 79 | Foreign key field &-& for join of table & is not a key field | |||
| 80 | Join condition for secondary table & with adjusted foreign key | |||
| 81 | For. key field &-& for join cond. to sec. table & not in base table | |||
| 82 | Join condition for secondary table & conflicts with the hierarchy | |||
| 83 | Lock mode & for table & is not allowed | |||
| 84 | Check lock object & | |||
| 85 | Activate lock object & | |||
| 86 | Lock object & is consistent | |||
| 87 | Lock object & was checked with warnings | |||
| 88 | Lock object & is inconsistent | |||
| 89 | Lock object & could not be checked | |||
| 90 | Lock object & activated | |||
| 91 | Lock object & was activated with warnings | |||
| 92 | Lock object & not activated | |||
| 93 | Lock object & activated without generating the function modules | |||
| 94 | Function group & could not be generated | Space: object requires documentation | ||
| 95 | The program code for the &EUE module could not be generated | |||
| 96 | Lock object & activated without generating the FMs with warnings | |||
| 97 | Generate function modules for lock object & | |||
| 98 | Function modules for lock object & could not be generated | |||
| 99 | Function modules for lock object & were generated | |||
| 100 | Lock parameter & has the same name as a base table | |||
| 101 | Lock argument for table & can not be determined | |||
| 102 | Maximum number & of tables to be locked exceeded | |||
| 103 | Maximum number & of lock parameters exceeded | |||
| 104 | Lock parameter name & has more than & characters and is thus invalid | Space: object requires documentation | ||
| 105 | Parameter field for lock parameter & is not a component of base table | Space: object requires documentation | ||
| 106 | Parameter field for lock parameter & is not elementary type | Space: object requires documentation | ||
| 107 | Type of lock field &-& is not suitable | Space: object requires documentation | ||
| 108 | The program code for the &EUE module could not be generated | Space: object requires documentation | ||
| 109 | Check dependent lock object & | Space: object requires documentation | ||
| 110 | Generate function module for dependent lock object & | Space: object requires documentation | ||
| 111 | Activate dependent lock object & | Space: object requires documentation | ||
| 112 | Dependent lock object & was not activated | Space: object requires documentation | ||
| 113 | Dep. lock object & activated with warning without gener. function module | Space: object requires documentation | ||
| 114 | Dependent lock object & was activated with warning | Space: object requires documentation | ||
| 115 | Dependent lock object & activated without generating the function modules | Space: object requires documentation | ||
| 116 | Dependent lock object & was activated | Space: object requires documentation | ||
| 117 | &1 and &2 lock objects were activated | Space: object requires documentation | ||
| 118 | Namespaces EY and EZ are reserved for (customer) lock objects | Space: object requires documentation | ||
| 119 | The interfaces were adjusted for &1 lock objects | |||
| 120 | Application: ABAP Dictionary (Basis), Client: * | Space: object requires documentation | ||
| 121 | Interface of lock object &1 could not be updated | |||
| 122 | No lock objects need be adjusted | |||
| 123 | No authorization for executing this program | |||
| 124 | ******************* General Messages ********************************** | |||
| 125 | Internal error (Form: &. Parameter: & & &) |
History
| Last changed on/by | 20140121 | SAP | |
| SAP Release Created in |