SAP ABAP Message Class DT (Table activation (incl. 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
⤷
SDTB (Package) ABAP/4 Dictionary: Tables
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD⤷
SDTB (Package) ABAP/4 Dictionary: Tables 
Attributes
| Message class |  |
DT |
| Short Description |  |
Table activation (incl. indexes) |
| Changed On |  |
20141121 |
| Last Changed At |  |
124009 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  000 |
************** General Messages on Tables ********************** | ||
| 2 | 001 |
Routine & (Table & could not be read) | ||
| 3 | 002 |
Table & does not exist | ||
| 4 | 003 |
Routine & (Table & could not be expanded) | ||
| 5 | 004 |
Routine & (Physical & & could not be read) | ||
| 6 | 005 |
Nametab for table & cannot be generated | ||
| 7 | 006 |
Routine & (Error writing table &) | ||
| 8 | 007 |
Table & (Error adjusting the database) | ||
| 9 | 008 |
Dependent tables are used in too many programs | ||
| 10 | 009 |
Table & (Activation could not be unlocked) | ||
| 11 | 010 |
Tab. & is of type INTTAB (Technical settings are not meaningful) | ||
| 12 | 011 |
& is not a DB-VIEW (Technical settings are not meaningful) | Space: object requires documentation | |
| 13 | 012 |
Activate table & | ||
| 14 | 013 |
Table & was not activated | ||
| 15 | 014 |
Activate dependent table & | ||
| 16 | 015 |
Dependent table & was not activated | ||
| 17 | 016 |
Check table & | ||
| 18 | 017 |
Check on table & resulted in errors | ||
| 19 | 018 |
If activation was successful, adjust C structures (where necessary) | ||
| 20 | 019 |
Fields: & Foreign key: & Indexes: & | ||
| 21 | 020 |
>>> STATISTICS & table & <<< | ||
| 22 | 021 |
Table is used in too many programs | ||
| 23 | 022 |
Dependent table & is used in too many programs | ||
| 24 | 023 |
Technical settings for table & deleted if activation is successful | ||
| 25 | 024 |
Table & must be created | ||
| 26 | 025 |
& (Invalid log parameters or parameter combination) | Space: object requires documentation | |
| 27 | 026 |
& (Invalid activation mode &) | Space: object requires documentation | |
| 28 | 027 |
List of tables dependent on & | ||
| 29 | 028 |
Table & | ||
| 30 | 029 |
If necessary, adjust & in the database (table type VIEW) | ||
| 31 | 030 |
Table & must be created in the database | ||
| 32 | 031 |
Table type changed from &->& (Make database changes where required) | ||
| 33 | 032 |
Create table/view & in the database | ||
| 34 | 033 |
Table type changed from &->& (Delete database table/view) | ||
| 35 | 034 |
Table type changed from &->& (Table is created in the DB) | ||
| 36 | 035 |
Table type changed from &->& (Table is deleted from DB) | ||
| 37 | 036 |
Table type changed from &->& (Data must be deleted) | ||
| 38 | 037 |
Table & was activated successfully | ||
| 39 | 038 |
Activation of dependent table & successful | ||
| 40 | 039 |
Table & is consistent | ||
| 41 | 040 |
Table type changed from &->& (DB table is deleted) | ||
| 42 | 041 |
==> Error in dependent objects | ||
| 43 | 042 |
Table &: Update of activation flag failed | ||
| 44 | 043 |
Scheduling of DD jobs & and & : & & | ||
| 45 | 044 |
Job & could not be scheduled | ||
| 46 | 045 |
No & objects in table & | Space: object requires documentation | |
| 47 | 046 |
Parallel start of activation/conversion job not possible | Space: object requires documentation | |
| 48 | 047 |
Job cannot be started between & and & | Space: object requires documentation | |
| 49 | 048 |
Job was terminated (Upgrade still in progress) | Space: object requires documentation | |
| 50 | 049 |
Table & is modified (Deleted or deleted/created new) | ||
| 51 | 050 |
Table & must be converted | ||
| 52 | 051 |
Error number in DD_DECIDE (&) | ||
| 53 | 052 |
No objects (& -> &) transferred (Action is not started) | Space: object requires documentation | |
| 54 | 053 |
Table & is used by table & as an append structure | ||
| 55 | 054 |
Activate table & with append structure | ||
| 56 | 055 |
Activation of table & with append structure successful | ||
| 57 | 056 |
Table & with append structure not activated | ||
| 58 | 057 |
Table & was activated >>> error in dependent tables | ||
| 59 | 058 |
Table & was activated with warnings | ||
| 60 | 059 |
Dependent table & was activated with warnings | ||
| 61 | 060 |
Table & was checked with warnings | ||
| 62 | 061 |
Table & with append structure was activated with warnings | ||
| 63 | 062 |
Correct the faulty objects | Space: object requires documentation | |
| 64 | 063 |
Table & (Activation lock could not be set) | ||
| 65 | 064 |
Structure change at field level (convert table &) | ||
| 66 | 065 |
Structure change at field level (convert matchcode &) | ||
| 67 | 066 |
Table & (Statements could not be generated) | ||
| 68 | 067 |
Check table for DD <-> DB inconsistencies | ||
| 69 | 068 |
Table & (error when adjusting the secondary indexes or views in the DB) | ||
| 70 | 069 |
Table &: Adjust secondary indexes in the database | ||
| 71 | 070 |
Unexpected action (=&) or unanticipated MODEFLAG (=&) ---> | ||
| 72 | 071 |
Structure & is used in/for & as Append/LOB structure | Space: object requires documentation | |
| 73 | 072 |
---> Deletion of & only after successful deletion of dependents | Space: object requires documentation | |
| 74 | 073 |
Table type change &->VIEW (Correct any DD<->DB inconsistencies) | ||
| 75 | 074 |
Table type change &->& (Convert table) | ||
| 76 | 075 |
Table & is inconsistent. Correct it. | Space: object requires documentation | |
| 77 | 076 |
Table has type VIEW. Correct any DD<->DB inconsistencies. | ||
| 78 | 077 |
Table type change &->&. Delete DB table or data. | ||
| 79 | 078 |
Adjust table in DB >>> | ||
| 80 | 079 |
<<< Database operations successful | ||
| 81 | 080 |
&: Structure change at field level (DB is adjusted) | ||
| 82 | 081 |
&: Structure change at field level (Index is created new) | ||
| 83 | 082 |
Activate table & (Active version) | ||
| 84 | 083 |
Activation caused by table & | ||
| 85 | 084 |
Table &: nametab missing (Check consistency of data) | ||
| 86 | 085 |
&: Inconsistency DD <-> DB (check table with analysis tool) | ||
| 87 | 086 |
Table &: nametab missing (Check consistency DD <-> DB) | ||
| 88 | 087 |
Activation of technical settings for table & | ||
| 89 | 088 |
Table & (Check for conversion from pooled -> transparent) | ||
| 90 | 089 |
Table & (Activation for conversion from pooled -> transparent) | ||
| 91 | 090 |
You do not have authorization for database modification of table & | ||
| 92 | 091 |
Initiated in the activation of table & | ||
| 93 | 092 |
Act. parameter & does not correspond to table fields specified | Space: object requires documentation | |
| 94 | 093 |
Activate and transport view(s) | ||
| 95 | 094 |
Table & is a multiplex table or multiplex-dependent. Conversion not poss. | ||
| 96 | 095 |
Table/structure & is used in program & | ||
| 97 | 096 |
You do not have permission to delete table & | ||
| 98 | 097 |
You do not have permission to create table & | ||
| 99 | 098 |
No activation authorization for & &. Entry not possible. | ||
| 100 | 099 |
Object type TABF is no longer supported | ||
| 101 | 100 |
********************* Tables: Headers ************************** | ||
| 102 | 101 |
Table & (Underscore not permitted at 2nd or 3rd position) | ||
| 103 | 102 |
Tab. &: Activation type=1 (Activation not possible online) | ||
| 104 | 103 |
& (Activation of tables of type cluster only with approval) | ||
| 105 | 104 |
Physical pool/cluster & not active | ||
| 106 | 105 |
Append structure & was moved from table & to table & | ||
| 107 | 106 |
Append structure & is used in more than one table: | ||
| 108 | 107 |
Table & | ||
| 109 | 108 |
Table & is of type append, but is not assigned to a table | ||
| 110 | 109 |
It does not make sense to enter a pool/cluster name here | ||
| 111 | 110 |
Enter a valid table type (Type & not known) | Space: object requires documentation | |
| 112 | 111 |
==> Pool/cluster name is deleted if successful activation | ||
| 113 | 112 |
No selection possible (Table & has only one key field) | Space: object requires documentation | |
| 114 | 113 |
Table & is transportable, append structure & local | ||
| 115 | 114 |
Append structure & is transportable, table & local | ||
| 116 | 115 |
Table & (Inactive nametab header could not be read) | ||
| 117 | 116 |
The namespace QCM is reserved for table conversions | ||
| 118 | 117 |
Name '&': Underscore not allowed at end | ||
| 119 | 118 |
Tab. & belongs to central Basis. Append & cannot be activated | ||
| 120 | 119 |
Table & was delivered | Space: object requires documentation | |
| 121 | 120 |
No authorization for requested DB change to table & | Space: object requires documentation | |
| 122 | 121 |
Name & is identical or is in same namespace as & | Space: object requires documentation | |
| 123 | 122 |
Structure & is itself used as a subtype | Space: object requires documentation | |
| 124 | 123 |
Specified table types are not defined | Space: object requires documentation | |
| 125 | 124 |
Table name & contains '/' in incorrect order or number | Space: object requires documentation | |
| 126 | 125 |
There are no structures with table types | Space: object requires documentation | |
| 127 | 126 |
Inactive nametab contains entries. First clean them up. | Space: object requires documentation | |
| 128 | 127 |
Target table & already contains entries. Please check. | Space: object requires documentation | |
| 129 | 128 |
Activation of table & because of data field POSITION | Space: object requires documentation | |
| 130 | 129 |
Activate Table & (language import) | Space: object requires documentation | |
| 131 | 130 |
Only use namespaces CL_ and IF_ for classes and interfaces | Space: object requires documentation | |
| 132 | 131 |
Activate data element & (language import) | Space: object requires documentation | |
| 133 | 132 |
Table contains more than & long string fields | Space: object requires documentation | |
| 134 | 133 |
Structure & is part of a cycle | Space: object requires documentation | |
| 135 | 134 |
Table set to read-only | Space: object requires documentation | |
| 136 | 135 |
Flag: 'Incorrect enhancement category' could not be updated | Space: object requires documentation | |
| 137 | 136 |
Database items for cluster table could not be determined | The short text describes the object sufficiently | |
| 138 | 137 |
Most recent runtime object & could not be read | The short text describes the object sufficiently | |
| 139 | 138 |
Generation of runtime object for structure or table & | The short text describes the object sufficiently | |
| 140 | 139 |
&: Update of ABAP time stamp not executed due to index/buffering change | The short text describes the object sufficiently | |
| 141 | 140 |
Table class has been changed from & to & | Space: object requires documentation | |
| 142 | 141 |
Delivery class was changed from & to & | Space: object requires documentation | |
| 143 | 142 |
& &: Type and length must not be changed | Space: object requires documentation | |
| 144 | 143 |
Key field &: Decimal places must not be changed | Space: object requires documentation | |
| 145 | 144 |
& & was deleted. This is not allowed in the Support Package System | Space: object requires documentation | |
| 146 | 145 |
Key field & was inserted into existing key | Space: object requires documentation | |
| 147 | 146 |
Field &: Position was changed | Space: object requires documentation | |
| 148 | 147 |
Table is still in conversion; activation is not possible | Space: object requires documentation | |
| 149 | 148 |
Table & with multiple occurrence (cycle) adjusted again | The short text describes the object sufficiently | |
| 150 | 149 |
Structure is not flat (component &) (use in DB function) | The short text describes the object sufficiently | |
| 151 | 150 |
Table class & is not known | The short text describes the object sufficiently | |
| 152 | 151 |
Input values are not consistent | The short text describes the object sufficiently | |
| 153 | 152 |
Generating a TADIR entry for & is not possible (return value = &) | The short text describes the object sufficiently | |
| 154 | 153 |
Active runtime object (header) for & could not be written to database | The short text describes the object sufficiently | |
| 155 | 154 |
Inactive runtime object header for & could not be written to database | The short text describes the object sufficiently | |
| 156 | 155 |
&: ABAP time stamp updated due to index or buffering change | The short text describes the object sufficiently | |
| 157 | 156 |
Table & does not exist, converted to CDS View | The short text describes the object sufficiently | |
| 158 | 157 |
Append &: Parent changed from & to & | The short text describes the object sufficiently | |
| 159 | 170 |
********************* Tables: Fields *************************** | The short text describes the object sufficiently | |
| 160 | 171 |
Table &: No candidates for streams and locators were found | Space: object requires documentation | |
| 161 | 172 |
Field &: & is not a basis type for streams and locators | The short text describes the object sufficiently | |
| 162 | 173 |
Field &: Basis type &: Reference only allowed to class & | The short text describes the object sufficiently | |
| 163 | 174 |
Stream classes for reading and writing cannot be combined | Space: object requires documentation | |
| 164 | 175 |
It was derived from read view &. Write class cannot be referenced | Space: object requires documentation | |
| 165 | 176 |
Derived LOB handle structure & must not reference any write class & | Space: object requires documentation | |
| 166 | 177 |
Field & cannot be deleted; usage in LOB handle structure & | The short text describes the object sufficiently | |
| 167 | 178 |
Field &: Type change not possible; usage in LOB handle structure & | The short text describes the object sufficiently | |
| 168 | 179 |
Table &: Fields could not be selected | The short text describes the object sufficiently | |
| 169 | 180 |
Deletion field & not possible: LOB handle struct. * has only this column | Space: object requires documentation | |
| 170 | 181 |
Key field & has unpermitted type & | Space: object requires documentation | |
| 171 | 182 |
&-&: Switching on NOT-NULL flag for SHORT RAWSTRING type not permitted | Space: object requires documentation | |
| 172 | 183 |
Field &: Used reference type & is not active | Space: object requires documentation | |
| 173 | 184 |
Field &-&: Table type & is a generic type | Space: object requires documentation | |
| 174 | 185 |
Field &: User type & is generated proxy type, therefore not usable | Space: object requires documentation | |
| 175 | 186 |
& is a generated proxy type, cannot be used as include | Space: object requires documentation | |
| 176 | 187 |
More than one field was selected as language field: & | Space: object requires documentation | |
| 177 | 188 |
Field &: Only fields with data ty.LANG can be selected as language fields | Space: object requires documentation | |
| 178 | 189 |
Current enhancement category & is incorrect | Space: object requires documentation | |
| 179 | 190 |
The following enhancement categories can be selected: | Space: object requires documentation | |
| 180 | 191 |
Enhancement category & possible, but include or subty. not yet classified | Space: object requires documentation | |
| 181 | 192 |
Enhancement category for table missing | Space: object requires documentation | |
| 182 | 193 |
Enhancement category for include or subtype missing | Space: object requires documentation | |
| 183 | 194 |
Field &: ANY cannot be used for data references | Space: object requires documentation | |
| 184 | 195 |
Several fields of type LANG: Select one of these as text language | Space: object requires documentation | |
| 185 | 196 |
Text language info deleted | Space: object requires documentation | |
| 186 | 197 |
Field &: Float type cannot be used in the key | Space: object requires documentation | |
| 187 | 198 |
Include &: Group name & contains SPACE | Space: object requires documentation | |
| 188 | 199 |
Exactly one field & of type LANG: Selection as text language possible | Space: object requires documentation | |
| 189 | 200 |
Field with name & in & does not exist | Space: object requires documentation | |
| 190 | 201 |
Table & for logging is too long (key<&, data division<& necessary) | ||
| 191 | 202 |
Specify a delivery class from the set (&) | ||
| 192 | 203 |
Field & (No underlining permitted in 2nd or 3rd position) | ||
| 193 | 204 |
Reference field &-& for &-& has incorrect type | Space: object requires documentation | |
| 194 | 205 |
& is a reserved word (Select another field name) | ||
| 195 | 206 |
Table & (Conversion to type transparent not possible) | ||
| 196 | 207 |
Key does not fulfill the requirements for a transparent table | ||
| 197 | 208 |
Table is too long | ||
| 198 | 209 |
Table & is rel. for translation (Marked for standard translation) | ||
| 199 | 210 |
Specified type of translation & is not known | ||
| 200 | 211 |
Field & (Length > & for & only allowed for non-DB tables) | ||
| 201 | 212 |
Field & is too long (Specify a length between & and &) | ||
| 202 | 213 |
&-& (Type VARC no longer supported as of release 3.0) | ||
| 203 | 214 |
Table &: Key length > & (Restricted functionality) | ||
| 204 | 215 |
&-&: Set NOT_NULL only after obtaining approval --> | ||
| 205 | 216 |
--> Activation by user DDIC | ||
| 206 | 217 |
&-&: Too long for activation of 'not null' flag (>&) | ||
| 207 | 218 |
Table has no fields | ||
| 208 | 219 |
Table is value table for clients (So not client-specific) | ||
| 209 | 220 |
Field & lies within customer namespace | ||
| 210 | 221 |
Field & does not lie within customer namespace | ||
| 211 | 222 |
Table has no fields apart from .INCLUDE | ||
| 212 | 223 |
There are too many fields (>&) | ||
| 213 | 224 |
Generic key is too long (>& bytes) | Space: object requires documentation | |
| 214 | 225 |
Table &: key length > & (Buffering not possible) | ||
| 215 | 226 |
Field of type CLNT not a key field. (Table is not client-specific) | ||
| 216 | 227 |
Check table & (Key was extended) | ||
| 217 | 228 |
&-& (Recommended length for field of type &: &) | ||
| 218 | 229 |
Field &-& does not exist | Space: object requires documentation | |
| 219 | 230 |
Field name & is reserved (Do not use structure as include in DB table) | ||
| 220 | 231 |
Field name & is reserved (Structure cannot be used as append in DB table) | ||
| 221 | 232 |
Only one long field allowed per table | ||
| 222 | 233 |
---> Long field must be in last position | ||
| 223 | 234 |
Field & of type & must be in the final position | ||
| 224 | 235 |
Field & does not have a preceding length field of type & | ||
| 225 | 236 |
Table & not translation-relevant (Type of translation is deleted) | ||
| 226 | 237 |
Translation-relevant table & (No field of type & in key) | ||
| 227 | 238 |
Translation-relevant table & (No field of type & in data division) | ||
| 228 | 239 |
Field & (Length < & for & not permitted) | ||
| 229 | 240 |
Number of fields too large | ||
| 230 | 241 |
Field & (Value & = & not allowed) | ||
| 231 | 242 |
Field &: Component type or domain used not active or does not exist | Space: object requires documentation | |
| 232 | 243 |
Field &: Data type is not allowed | Space: object requires documentation | |
| 233 | 244 |
Field &: Data type & is not supported in domain & | Space: object requires documentation | |
| 234 | 245 |
DB length of the key of table & is too large (>&) | Space: object requires documentation | |
| 235 | 246 |
This number of key fields is not permitted with generic buffering | ||
| 236 | 247 |
Field & cannot be used as key field because no default exists for type & | Space: object requires documentation | |
| 237 | 248 |
Data field &: init. flag deleted because no default exists for type & | Space: object requires documentation | |
| 238 | 249 |
Field &: Structured type & is not active or does not exist | Space: object requires documentation | |
| 239 | 250 |
Field name & does not agree with proposed name & for & table | Space: object requires documentation | |
| 240 | 251 |
Field &: Data type & does not exist | Space: object requires documentation | |
| 241 | 252 |
Field &: Data type & is no longer supported | Space: object requires documentation | |
| 242 | 253 |
Field &: Length < minimum length (=&) for data type & | Space: object requires documentation | |
| 243 | 254 |
Field &: Length > maximum length (=&) for data type & | Space: object requires documentation | |
| 244 | 255 |
No type was defined for field & | Space: object requires documentation | |
| 245 | 256 |
Field &: Length is corrected to & (because > maximum length (=&) for &) | ||
| 246 | 257 |
Field &: Length is corrected to & (Set for data type &) | ||
| 247 | 258 |
Field &: Decimal places are deleted. (Not appropriate for data type &) | ||
| 248 | 259 |
Field &: Decimal places are corrected to & (set for &) | ||
| 249 | 260 |
Field &: Decimal places are corrected to & (proposed value for &) | ||
| 250 | 261 |
Field &: Decimal places are adjusted to the length (=&) | ||
| 251 | 262 |
Field & does not begin with a letter (please check) | ||
| 252 | 263 |
Field & contains a non-alphanumeric character | ||
| 253 | 264 |
Generic key field & is missing from logical cluster & | ||
| 254 | 265 |
Field &: . in the first position is not allowed | ||
| 255 | 266 |
Type of key field & is a table type | Space: object requires documentation | |
| 256 | 267 |
Field &: Table type & is not active or does not exist | Space: object requires documentation | |
| 257 | 268 |
Field &: Table type & cannot be used in DB table & | Space: object requires documentation | |
| 258 | 269 |
Field &: Structured type & cannot be used in DB table & | Space: object requires documentation | |
| 259 | 270 |
Field & contains at least one invalid character | ||
| 260 | 271 |
Field &: Component type of a DB table may not be table type | Space: object requires documentation | |
| 261 | 272 |
Field name & is too long. At most & characters are permitted. | Space: object requires documentation | |
| 262 | 273 |
Field name & contains '/' in incorrect order | Space: object requires documentation | |
| 263 | 274 |
Field name & contains incorrect number of '/' | Space: object requires documentation | |
| 264 | 275 |
Field name & may not only consist of a namespace prefix | Space: object requires documentation | |
| 265 | 276 |
Field name &: define a namespace between '/' | Space: object requires documentation | |
| 266 | 277 |
Structure with '-' in field name cannot contain a structured type | Space: object requires documentation | |
| 267 | 278 |
Only use types whose component fields do not contain '-' | Space: object requires documentation | |
| 268 | 279 |
Field &: Reference & to class w/o interface cannot be used in DB table & | Space: object requires documentation | |
| 269 | 280 |
Define at least one field of the phys. cluster other than the key | ||
| 270 | 281 |
Table name & does not lie in valid namespace | Space: object requires documentation | |
| 271 | 282 |
Field name & lies in external or unknown namespace but is valid | Space: object requires documentation | |
| 272 | 283 |
Field name & can be provided in this system. Please do not use. | Space: object requires documentation | |
| 273 | 284 |
Field name & can already exist in a subsequent system | Space: object requires documentation | |
| 274 | 285 |
Prefix for field name & is not valid | Space: object requires documentation | |
| 275 | 286 |
Field name & lies in unknown namespace | Space: object requires documentation | |
| 276 | 287 |
Change field name & and place in your own existing namespace | Space: object requires documentation | |
| 277 | 288 |
Field &: Class or interface & not active/implemented | Space: object requires documentation | |
| 278 | 289 |
Key field & references a class or interface | Space: object requires documentation | |
| 279 | 290 |
& cannot be used as include because it contains nested or table types | Space: object requires documentation | |
| 280 | 291 |
Field &: No foreign key possible when using a reference type | Space: object requires documentation | |
| 281 | 292 |
Field &: Data type change from & to & not possible | Space: object requires documentation | |
| 282 | 293 |
Field & with reference type: Value help with search help not possible | Space: object requires documentation | |
| 283 | 294 |
Field & generic reference type & in DB table & not allowed | Space: object requires documentation | |
| 284 | 295 |
Field name & is reserved for ABAP and thus not allowed | Space: object requires documentation | |
| 285 | 296 |
&-&: Too long for use as key field (>=&) | Space: object requires documentation | |
| 286 | 297 |
Field &: Type & not allowed in DB tables | Space: object requires documentation | |
| 287 | 298 |
Neither foreign key nor search help maintained for this append | Space: object requires documentation | |
| 288 | 299 |
Append has no fields | Space: object requires documentation | |
| 289 | 300 |
********************* Tables: Foreign Keys *********** | Space: object requires documentation | |
| 290 | 301 |
Field & of foreign key &-& not found | ||
| 291 | 302 |
Foreign key &-& specification incomplete | ||
| 292 | 303 |
Message/application area missing for foreign key &-& | ||
| 293 | 304 |
Foreign key &-& (More foreign key fields than check table fields) | ||
| 294 | 305 |
Foreign key &-& (No value table defined) | ||
| 295 | 306 |
Foreign key &-& (Field specified despite generic foreign key) | ||
| 296 | 307 |
Foreign key &-& (Field specified despite constant foreign key) | ||
| 297 | 308 |
Foreign key &-& is extended generically | ||
| 298 | 310 |
Deleted foreign key &-& is still used in: | ||
| 299 | 311 |
Changed foreign key &-& is still used in: | ||
| 300 | 312 |
Foreign key &-& becomes generic because key of check table was extended | ||
| 301 | 313 |
For. &-& (& and & have different data types) | ||
| 302 | 314 |
For. &-& (& and & are of different lengths) | ||
| 303 | 315 |
Text foreign key for table & is already defined: | Space: object requires documentation | |
| 304 | 316 |
&-& is not a text foreign key. Reset to unspecified. | Space: object requires documentation | |
| 305 | 317 |
Check field & cannot be type & | Space: object requires documentation | |
| 306 | 332 |
Active runtime object & could not be read | The short text describes the object sufficiently | |
| 307 | 350 |
********************* Tables: assignment to search help ***** | Space: object requires documentation | |
| 308 | 351 |
Attachment of search help & to field &-& is deleted | Space: object requires documentation | |
| 309 | 352 |
Search field &-& of search help attachment: search help & not active | Space: object requires documentation | |
| 310 | 353 |
&-&: Table & in search help attachment differs from table of search field | Space: object requires documentation | |
| 311 | 354 |
Search field &-& not contained in search help attachment | Space: object requires documentation | |
| 312 | 355 |
Attachment to search help &-&: & and & refer to different domains | Space: object requires documentation | |
| 313 | 356 |
Attachment to search help &-&: & and & have different data types | Space: object requires documentation | |
| 314 | 357 |
Attachment to search help &-&: & and & have different lengths | Space: object requires documentation | |
| 315 | 358 |
&-&: Field & of the assignment does not exist in the search help & | Space: object requires documentation | |
| 316 | 359 |
Field &-& of the search help link to field & does not exist in table & | Space: object requires documentation | |
| 317 | 360 |
Field &-& of search help attachment: constant is not maintained correctly | Space: object requires documentation | |
| 318 | 361 |
&-&: Field &-& of search help attachment: no import/export definition | Space: object requires documentation | |
| 319 | 362 |
Search field &-&: field def. despite generic attachment | Space: object requires documentation | |
| 320 | 363 |
Search field &-&: Field def. despite constant attachment | Space: object requires documentation | |
| 321 | 364 |
Search help attachment & to table & is deleted | Space: object requires documentation | |
| 322 | 365 |
Search help & for table & not active | Space: object requires documentation | |
| 323 | 366 |
Search field &-&: search help par. & used multiply and is import param. | Space: object requires documentation | |
| 324 | 367 |
Search field &-&: field & occurs more than once. Value export not clear | Space: object requires documentation | |
| 325 | 368 |
Search help &: search help par. & used multiply and is import parameter | Space: object requires documentation | |
| 326 | 369 |
Search help &: field & occurs more than once. Value export not clear | Space: object requires documentation | |
| 327 | 370 |
Field &-& of allocation does not exist in search help & of the table | Space: object requires documentation | |
| 328 | 371 |
Field &-& of search help attachment: No import/export specification | Space: object requires documentation | |
| 329 | 372 |
Search help attachment field &-&: Define constant & with apostrophes | Space: object requires documentation | |
| 330 | 373 |
&: Table & in search help attachment differs from table of search field | Space: object requires documentation | |
| 331 | 374 |
Search help attachment for table &: Constant not correctly maintained | Space: object requires documentation | |
| 332 | 375 |
Search help attachment for table &: Constant & defined with apostrophes | Space: object requires documentation | |
| 333 | 400 |
******************** Tables: Includes ************************* | ||
| 334 | 401 |
Customer and SAP Includes not allowed for table type & | ||
| 335 | 402 |
Append structure & appended to table & | ||
| 336 | 403 |
Inconsistent foreign key &-& deleted | ||
| 337 | 404 |
Inconsistent foreign key &-& not inherited | ||
| 338 | 405 |
No customer or SAP include & exists | ||
| 339 | 406 |
Append structure & cannot be appended to table of type & | ||
| 340 | 407 |
Tables of type & may not be included | ||
| 341 | 408 |
Append structure & no longer found | ||
| 342 | 409 |
Define max. three-place suffix for & | Space: object requires documentation | |
| 343 | 410 |
Inconsistent search help attachment &-& deleted | Space: object requires documentation | |
| 344 | 411 |
Inconsistent search help attachment &-& not inherited | Space: object requires documentation | |
| 345 | 412 |
Definition & for include is syntactically incorrect | Space: object requires documentation | |
| 346 | 413 |
Foreign key for field & may not be overwritten by append | Space: object requires documentation | |
| 347 | 414 |
Search help for field & may not be overwritten by append | Space: object requires documentation | |
| 348 | 415 |
& does not contain an append | The short text describes the object sufficiently | |
| 349 | 430 |
*********** Tables: Include structures (complex types) | Space: object requires documentation | |
| 350 | 431 |
Type & for component & is not active | Space: object requires documentation | |
| 351 | 450 |
*** 450 - 460: Messages about Table Fields | Space: object requires documentation | |
| 352 | 451 |
Field &: Decimal places are corrected to & (max. no. of decimal places) | Space: object requires documentation | |
| 353 | 452 |
&-&: Structure change -> MODEFLAG set to special | Space: object requires documentation | |
| 354 | 453 |
Field & of cluster key has type DEC with digits after the decimal point | Space: object requires documentation | |
| 355 | 454 |
Feld &: Preceding & field cannot be a key field | Space: object requires documentation | |
| 356 | 455 |
Field &: String type is not allowed | Space: object requires documentation | |
| 357 | 456 |
Field &: Type DECFLOAT (&) in key of a pool table not allowed | Space: object requires documentation | |
| 358 | 457 |
Field &: Typ & is not allowed in a cluster table | The short text describes the object sufficiently | |
| 359 | 458 |
Field &: Typ & is not allowed in the key of a cluster table | The short text describes the object sufficiently | |
| 360 | 459 |
Feld &: Type Decfloat (&) requires following scale column of type INT2 | The short text describes the object sufficiently | |
| 361 | 460 |
Field &-&: Only output types (enhanced) currency amount allowed | Space: object requires documentation | |
| 362 | 461 |
Field &-&: Output type (enhanced) currency amount requires ref.field | Space: object requires documentation | |
| 363 | 462 |
Key field & has forbidden DECFLOAT type (D16S/D34S) | The short text describes the object sufficiently | |
| 364 | 463 |
Field &: Another field has been added before the subsequent INT2 field | Space: object requires documentation | |
| 365 | 464 |
Check the following fields: & | The short text describes the object sufficiently | |
| 366 | 465 |
&: Boxed components are not yet released | The short text describes the object sufficiently | |
| 367 | 466 |
Field &: Renaming of INT2 field invalidates data | Space: object requires documentation | |
| 368 | 467 |
Introduction of field & will invalidate the data of subsequent INT2 field | Space: object requires documentation | |
| 369 | 468 |
Field & contains characters in lowercase | The short text describes the object sufficiently | |
| 370 | 471 |
Table & should not have any text language indicator. Delete | The short text describes the object sufficiently | |
| 371 | 500 |
******************************** Indexes ****************************** | ||
| 372 | 501 |
DB index & not defined in ABAP Dictionary | Space: object requires documentation | |
| 373 | 502 |
Index &-& must be created in the database | ||
| 374 | 503 |
Index &-& must be converted | ||
| 375 | 504 |
No index &-& found with status & | ||
| 376 | 505 |
Text for index &-& missing in status & | ||
| 377 | 506 |
No fields defined for index &-& | ||
| 378 | 507 |
Index &-& for table & not found | Space: object requires documentation | |
| 379 | 508 |
Index &-& is not correctly defined | ||
| 380 | 509 |
Indexes & and & for table & have identical fields | ||
| 381 | 510 |
Index &-& completely contains the fields of index & | ||
| 382 | 511 |
More than 16 indexes defined for table & | ||
| 383 | 512 |
Index &-& could not be activated | ||
| 384 | 513 |
Indexes to table & could not be activated | ||
| 385 | 514 |
Index &-& has more than 16 fields | ||
| 386 | 515 |
Entry of index &-& for background processing failed | ||
| 387 | 516 |
Index &-& entered for background processing | ||
| 388 | 517 |
Index &-& already entered for background processing | ||
| 389 | 518 |
Index &-& is not in the customer namespace | ||
| 390 | 519 |
Index &-& is in the customer namespace | ||
| 391 | 520 |
Index &-& was successfully activated | Space: object requires documentation | |
| 392 | 521 |
Indexes to table & were successfully activated | ||
| 393 | 522 |
Index &-& is consistent | ||
| 394 | 523 |
Indexes to table & are consistent | ||
| 395 | 524 |
Index &-& is not consistent | ||
| 396 | 525 |
Indexes to table & are not consistent | ||
| 397 | 526 |
Activate index & | ||
| 398 | 527 |
Check index & | ||
| 399 | 528 |
Activate indexes to table & | ||
| 400 | 529 |
Check indexes of table & | ||
| 401 | 530 |
Table & is not transparent | Space: object requires documentation | |
| 402 | 531 |
Indexes to non-transparent tables are deleted | ||
| 403 | 532 |
Index & was not created with SAP tools | ||
| 404 | 533 |
Index &-& (Definitions of the unique flag vary) | ||
| 405 | 534 |
Index &-& (different fields in ABAP Dictionary and database) | Space: object requires documentation | |
| 406 | 535 |
Table & does not exist | Space: object requires documentation | |
| 407 | 536 |
Index &-& was not found | Space: object requires documentation | |
| 408 | 537 |
Number of indexes (&) allowed by DB system exceeded | Space: object requires documentation | |
| 409 | 538 |
Number of indexes too large for following DB systems: | Space: object requires documentation | |
| 410 | 540 |
Index ID must be between 1 and 3 characters in length | ||
| 411 | 541 |
An index name must be maintained for object type index | Space: object requires documentation | |
| 412 | 542 |
Unique index &-& must always be created on the database | Space: object requires documentation | |
| 413 | 543 |
Define at least one DB system for DB-dependent index &-& | Space: object requires documentation | |
| 414 | 544 |
Index &-& must be deleted on DB | Space: object requires documentation | |
| 415 | 545 |
Index &-& lies in namespace for partner developments | Space: object requires documentation | |
| 416 | 546 |
Index &-& does not lie in namespace for partner | Space: object requires documentation | |
| 417 | 547 |
Index &-& is of type Full Text; table must be in Column Store | The short text describes the object sufficiently | |
| 418 | 548 |
Index &-& is of type Full Text. This is supported on: & | The short text describes the object sufficiently | |
| 419 | 549 |
Check exception list for index &-& | The short text describes the object sufficiently | |
| 420 | 550 |
The index & was created in the database | ||
| 421 | 551 |
The index & was deleted in the database | ||
| 422 | 552 |
Index & was converted in the database | ||
| 423 | 553 |
Error creating index & in the database | ||
| 424 | 554 |
Error when deleting index & from the database | ||
| 425 | 555 |
Error converting index & in the database | ||
| 426 | 556 |
Online execution can lead to runtime being exceeded | ||
| 427 | 557 |
Activate (via DB utility) index & | ||
| 428 | 558 |
Index &-& is of type Full Text. This is not implemented for DB & | The short text describes the object sufficiently | |
| 429 | 559 |
Full Text index &-& can only be defined for exactly one column of type & | The short text describes the object sufficiently | |
| 430 | 560 |
Index ID 0 is reserved for the primary index | Space: object requires documentation | |
| 431 | 561 |
Index &-& (Field & has unauthorized data type &) | Space: object requires documentation | |
| 432 | 562 |
DB actions for indexes table &: Index info could not be read | Space: object requires documentation | |
| 433 | 563 |
&-&: Full text index cannot be unique | The short text describes the object sufficiently | |
| 434 | 564 |
Full text index &-&, parameter &: Value & is not allowed | The short text describes the object sufficiently | |
| 435 | 565 |
Full text index &-&: Select similarity value for search words [0...100] | The short text describes the object sufficiently | |
| 436 | 566 |
Index &-&: Vector for autom. language search: Language & is invalid | The short text describes the object sufficiently | |
| 437 | 567 |
Full text index &-&: Values of param. & and & cannot be combined | Space: object requires documentation | |
| 438 | 568 |
Full text index &-&: Language column & is not in table & | The short text describes the object sufficiently | |
| 439 | 569 |
Full text index &-&: Mime Type column & is not in table & | The short text describes the object sufficiently | |
| 440 | 570 |
Full text index &-&: & is not a valid Mime Type | The short text describes the object sufficiently | |
| 441 | 571 |
Full-text index &-&: & and data type RAWSTRING cannot be combined | The short text describes the object sufficiently | |
| 442 | 600 |
*********************** Technical Settings ****************************** | ||
| 443 | 601 |
Maintain the data class and size category for table & | ||
| 444 | 602 |
The technical settings for table & are already locked | Space: object requires documentation | |
| 445 | 603 |
You have no change authorization for technical settings | Space: object requires documentation | |
| 446 | 604 |
You cannot maintain/display the technical settings for table & | Space: object requires documentation | |
| 447 | 605 |
Techn. settings table & already locked or no authorization | Space: object requires documentation | |
| 448 | 606 |
Specifications for number of key fields are deleted | Space: object requires documentation | |
| 449 | 607 |
Key field & has type &: Buffering not possible, Transport restricted | Space: object requires documentation | |
| 450 | 608 |
No action taken (Control parameters were inactive) | Space: object requires documentation | |
| 451 | 609 |
Value in field & (value & not permitted) | Space: object requires documentation | |
| 452 | 610 |
Table & is not an active table | ||
| 453 | 611 |
Activate as transparent table: & | ||
| 454 | 612 |
Check as transparent table: & | ||
| 455 | 613 |
==> Table exists in revised version or is new | ||
| 456 | 614 |
==> Execute the action via the table activation of & | ||
| 457 | 615 |
Technical settings for & not found | ||
| 458 | 616 |
Maintain data class for table & | ||
| 459 | 617 |
Maintain size category for table & | ||
| 460 | 618 |
Generic buffering & (at least 2 key fields necessary) | Space: object requires documentation | |
| 461 | 619 |
Activate technical settings for & | Space: object requires documentation | |
| 462 | 620 |
Technical settings for & were activated successfully | ||
| 463 | 621 |
Technical settings for & were activated with warning | ||
| 464 | 622 |
Technical settings for & were not activated | ||
| 465 | 623 |
Check technical settings for & | Space: object requires documentation | |
| 466 | 624 |
Technical settings for & are consistent | ||
| 467 | 625 |
Technical settings for & were checked with warning | ||
| 468 | 626 |
Technical settings for & are inconsistent | ||
| 469 | 627 |
Inactive nametab header could not be written | ||
| 470 | 628 |
Error in writing the technical settings | ||
| 471 | 629 |
Inconsistency betw. nametab (type transparent) and DD sources (type pool) | ||
| 472 | 630 |
Active nametab could not be written | ||
| 473 | 631 |
Conversion requirements pool/custer -> transparent table | ||
| 474 | 632 |
Error writing the table header pool -> transparent | Space: object requires documentation | |
| 475 | 633 |
Job for conversion was not scheduled | ||
| 476 | 634 |
& (Conversion & -> transparent not possible) | ||
| 477 | 635 |
Nametab for & does not exist (Update therefore not possible) | ||
| 478 | 636 |
Table &: Entry for conversion for follows | ||
| 479 | 637 |
Overall result act. techn. settings (OK/warnings/errors): (&/&/&) | ||
| 480 | 638 |
Overall result of check of techn. settings (OK/warnings/errors): (&/&/&) | ||
| 481 | 639 |
Table & can be converted | ||
| 482 | 640 |
Overall result of conversions (OK/warnings/errors): (&/&/&) | ||
| 483 | 641 |
Log could not be opened | ||
| 484 | 642 |
Action canceled | Space: object requires documentation | |
| 485 | 643 |
Technical settings were no activated successfully | ||
| 486 | 644 |
Transparent flag was set. Convert table | ||
| 487 | 645 |
No authorization for activating technical settings for table & | Space: object requires documentation | |
| 488 | 646 |
Buffering not permitted for &, but a buffering type was defined | Space: object requires documentation | |
| 489 | 647 |
Buffering activated for &: specify buffering type | Space: object requires documentation | |
| 490 | 648 |
Multiple selection not possible for buffering type | ||
| 491 | 649 |
No buffering information available to be copied | ||
| 492 | 650 |
Buffering parameter (BUFALLOW/KIND): &1/&2 -> &3/&4 | ||
| 493 | 651 |
Buffering parameter active version (BUFALLOW/KIND): &1/&2 -> &3/&4 | ||
| 494 | 652 |
MERGE_BUF: Internal error when writing the buffering parameters | ||
| 495 | 653 |
Object & already locked -> activation not performed | ||
| 496 | 654 |
Number of key fields in generic key: &1 -> &2 | ||
| 497 | 655 |
Technical settings are deleted with next table activation | ||
| 498 | 656 |
Technical settings make no sense - > are not generated | ||
| 499 | 657 |
Table & was written in N verson -> no further action required | ||
| 500 | 658 |
&: Values already copied from DDBUF -> no further action | ||
| 501 | 659 |
Latest buffering values do not agree with the active ones. Please check. | ||
| 502 | 660 |
Latest values (&1/&2) were copied. Active values were (&3/&4) | ||
| 503 | 661 |
You do not have display authorization for technical settings | ||
| 504 | 662 |
Define table name or attributes of the technical settings | ||
| 505 | 663 |
Technical settings are defined but not from table & | ||
| 506 | 664 |
Technical settings not meaningful for tables of type & | ||
| 507 | 665 |
Table & does not exist | ||
| 508 | 666 |
Information for table & could not be read | ||
| 509 | 667 |
Action & terminated | ||
| 510 | 668 |
Technical settings for & already locked by another user | ||
| 511 | 669 |
Enqueue system error: Technical settings for & could not be locked | ||
| 512 | 670 |
No authorization to change the technical settings for & | ||
| 513 | 671 |
No authorization to display the technical settings for & | ||
| 514 | 672 |
No access authorization or internal error | ||
| 515 | 673 |
Technical settings for & already exist | ||
| 516 | 674 |
Technical settings for & do not yet exist | ||
| 517 | 675 |
Error reading technical settings for & | ||
| 518 | 676 |
Table & does not exist or could not be read | ||
| 519 | 677 |
Technical settings could not be locked | ||
| 520 | 678 |
Technical settings could not be unlocked | ||
| 521 | 679 |
Technical settings could not be written | ||
| 522 | 680 |
Reset to active version failed | ||
| 523 | 681 |
Technical settings reset to active version | ||
| 524 | 682 |
Version can only be stored from active object | ||
| 525 | 683 |
Version of >> active << object stored | ||
| 526 | 684 |
&: Incorrect version of technical settings | Space: object requires documentation | |
| 527 | 685 |
Temporary version of active object stored | ||
| 528 | 686 |
Identical version was already stored or version could not be stored | ||
| 529 | 687 |
Technical settings for & are new. Active version does not exist. | ||
| 530 | 688 |
Active version is already displayed | ||
| 531 | 689 |
Technical settings for & are new. Revised version does not exist. | ||
| 532 | 690 |
Revised version does not exist | ||
| 533 | 691 |
Log could not be read | ||
| 534 | 692 |
Log & does not exist | Space: object requires documentation | |
| 535 | 693 |
Technical settings could not be written -> activation terminated | ||
| 536 | 694 |
Specify only one buffering type | ||
| 537 | 695 |
Technical settings for & were activated successfully | ||
| 538 | 696 |
Buffering mode is not generic. Delete "number of key fields". | ||
| 539 | 697 |
Buffering mode is not generic. Number of key fiels must be 0. | ||
| 540 | 698 |
Buffering type is generic. Specify "number of key fields" | ||
| 541 | 699 |
Processing terminated or no correction entry possible | ||
| 542 | 700 |
Form &: error when calling & | ||
| 543 | 701 |
Active version is latest and is already displayed | ||
| 544 | 702 |
Domain fixed values for domain & could not be read | ||
| 545 | 703 |
Define table name <> ' ' | ||
| 546 | 704 |
Technical settings for table & successfully deleted | ||
| 547 | 705 |
Technical settings for table & could not be deleted | ||
| 548 | 706 |
Technical settings for & could not be read. Copy not possible | ||
| 549 | 707 |
Not possible to write technical settings for &. Copy not successful | ||
| 550 | 708 |
Table & already has technical settings | ||
| 551 | 709 |
Techn. sett. for table & successfully copied to techn. sett. for & | ||
| 552 | 710 |
Table & has type &. "Copy" action was terminated | ||
| 553 | 711 |
Table/view & does not exist | Space: object requires documentation | |
| 554 | 712 |
First save and then check again | Space: object requires documentation | |
| 555 | 713 |
Base table & of buff. view &: Active nametab header not read | Space: object requires documentation | |
| 556 | 714 |
Base table & of buff. view &: Nametab header was not written | Space: object requires documentation | |
| 557 | 715 |
Base table & is used in at least 10 views which are or can be buffered | Space: object requires documentation | |
| 558 | 716 |
Base table & of buff. view &: Runtime object could not be read | Space: object requires documentation | |
| 559 | 717 |
Base table & of buff. view &: Runtime object was not written | Space: object requires documentation | |
| 560 | 718 |
Base table & of buff. view &: Inactive nametab header not read | Space: object requires documentation | |
| 561 | 719 |
Buffer of table use for view & could not be reset | Space: object requires documentation | |
| 562 | 720 |
No technical settings exist for the given table name & | Space: object requires documentation | |
| 563 | 721 |
View & cannot be buffered | Space: object requires documentation | |
| 564 | 722 |
Technical settings for & do not exist. Delete not possible. | Space: object requires documentation | |
| 565 | 723 |
Documentation about technical settings not found | Space: object requires documentation | |
| 566 | 724 |
Technical settings for table & already being edited by user & | Space: object requires documentation | |
| 567 | 725 |
Version of technical settings of & & cannot be displayed | Space: object requires documentation | |
| 568 | 726 |
& is not a database view (technical settings cannot be defined/displayed) | Space: object requires documentation | |
| 569 | 727 |
Technical settings only available in & version | Space: object requires documentation | |
| 570 | 728 |
View & with basis table &: Active nametab header of view not read | Space: object requires documentation | |
| 571 | 729 |
View & with basis tab. &: Inactive nametab header of view not read | Space: object requires documentation | |
| 572 | 730 |
View & with basis table &: Runtime object of view not read | Space: object requires documentation | |
| 573 | 731 |
View & with basis table &: Nametab header was not written | Space: object requires documentation | |
| 574 | 732 |
View & with basis table &: runtime object was not written | Space: object requires documentation | |
| 575 | 733 |
Techn.setting: will be set for &: 'Write access only with Java' set | The short text describes the object sufficiently | |
| 576 | 734 |
Techn. setting: for &: 'Write access only with Java' set | The short text describes the object sufficiently | |
| 577 | 735 |
Technical settings for view & cannot be read | The short text describes the object sufficiently | |
| 578 | 736 |
Field & contains forbidden type & for 'write access only with Java' | The short text describes the object sufficiently | |
| 579 | 737 |
Logging only possible if all fields are NOT NULL | Space: object requires documentation | |
| 580 | 738 |
Field & does not have NOT NULL property | The short text describes the object sufficiently | |
| 581 | 739 |
Buffering is only possible if all fields are NOT NULL | Space: object requires documentation | |
| 582 | 740 |
Logging of string fields can only be used in limited way | Space: object requires documentation | |
| 583 | 741 |
Activation of active technical settings table & successful | The short text describes the object sufficiently | |
| 584 | 742 |
Memory type was set to & | The short text describes the object sufficiently | |
| 585 | 743 |
Specify row or column store information | The short text describes the object sufficiently | |
| 586 | 744 |
Table will be moved from & store to & store | The short text describes the object sufficiently | |
| 587 | 745 |
Tab &: Row or Column Store Info from DB cannot be determined | The short text describes the object sufficiently | |
| 588 | 746 |
Table contains at least one field of type DECFLOAT 16 DEC/RAW | The short text describes the object sufficiently | |
| 589 | 747 |
This is not possible in row store | The short text describes the object sufficiently | |
| 590 | 748 |
Table & is participating in DataAging; therefore buffering not possible | Space: object requires documentation | |
| 591 | 749 |
Table & is already in store &; no action necessary on DB | The short text describes the object sufficiently | |
| 592 | 800 |
*********************Table Appends************************************ | Space: object requires documentation | |
| 593 | 801 |
Name & is invalid | ||
| 594 | 802 |
Editing of the append to table & was cancelled | Space: object requires documentation | |
| 595 | 803 |
Field & adopted as non-key field in table & | ||
| 596 | 804 |
Internal error | Space: object requires documentation | |
| 597 | 805 |
No help available here | Space: object requires documentation | |
| 598 | 806 |
The name & does not start with either 'Y' or 'Z' | ||
| 599 | 807 |
Field & is in both versions of the table | ||
| 600 | 808 |
Field & is contained in the key of the table | ||
| 601 | 809 |
Field & occurs several times in the table | ||
| 602 | 810 |
Field & was included in the proposal | ||
| 603 | 811 |
Standard append & for table & already exists | Space: object requires documentation | |
| 604 | 812 |
Standard name & not permitted for append to table & | Space: object requires documentation | |
| 605 | 813 |
Standard name & for append to table & is already assigned to a view | Space: object requires documentation | |
| 606 | 814 |
Standard name & for append to table & is already assigned | Space: object requires documentation | |
| 607 | 815 |
Enter a name for the append | ||
| 608 | 816 |
The selected name has already been assigned to a view | ||
| 609 | 817 |
The selected name & has already been assigned | Space: object requires documentation | |
| 610 | 818 |
& was included in the proposal as & | ||
| 611 | 819 |
& as & in both versions of the table | ||
| 612 | 820 |
& occurs as & in the non-key section of the table | ||
| 613 | 821 |
& occurs as & in the key of the table | ||
| 614 | 822 |
& occurs several times as & in the table | ||
| 615 | 823 |
Field & in key section, so not in proposal | ||
| 616 | 824 |
& is contained in the key section as &, therefore, not in the proposal | ||
| 617 | 825 |
Current version already corresponds to proposal | Space: object requires documentation | |
| 618 | 826 |
Position cursor on a name | Space: object requires documentation | |
| 619 | 827 |
Not all of the imported appends for table & could be activated | ||
| 620 | 828 |
Field & is included in the table | ||
| 621 | 829 |
Appended table & is temporarily partially active | ||
| 622 | 830 |
As transparent flag of table & is set, appends are allowed | ||
| 623 | 831 |
Change in structure of field & | ||
| 624 | 832 |
& is included as & in the table | ||
| 625 | 833 |
Append structures can only be created via the menu | Space: object requires documentation | |
| 626 | 834 |
Append structures can only be created for active tables | Space: object requires documentation | |
| 627 | 835 |
Several foreign key definitions were found for field & | ||
| 628 | 836 |
It is not necessary to adjust the technical settings for table & | Space: object requires documentation | |
| 629 | 837 |
Start: create a proposal list for table & | ||
| 630 | 838 |
End: create a proposal list for table & | ||
| 631 | 839 |
Original table does not require adjustment | ||
| 632 | 840 |
Customer version of table & could not be accessed | ||
| 633 | 841 |
Current version of table & could not be read | ||
| 634 | 842 |
Warnings were issued when the proposal list was created | ||
| 635 | 843 |
It is not necessary to create an append for table & | ||
| 636 | 844 |
Create or extend append to table & | ||
| 637 | 845 |
Start: Analyze & as & | ||
| 638 | 846 |
Start: Analyze field & | ||
| 639 | 847 |
End: Analyze & as & | ||
| 640 | 848 |
End: Analyze field & | ||
| 641 | 849 |
Warning issued when analyzing & as & | ||
| 642 | 850 |
Warnings issued when analyzing field & | ||
| 643 | 851 |
Old version of technical settings for table & could not be read | ||
| 644 | 852 |
Expanding current version of table & failed | ||
| 645 | 853 |
Warnings issued during editing of the old field list | ||
| 646 | 854 |
End: Edit table & old field list | ||
| 647 | 855 |
Start: Append new fields to table & | ||
| 648 | 856 |
& placed in first table position as & | ||
| 649 | 857 |
New client field & is placed at the start of the table | ||
| 650 | 858 |
& is added as & to the key of the table | ||
| 651 | 859 |
Field & is added to the key of the table | ||
| 652 | 860 |
& is added to the table as & | ||
| 653 | 861 |
Field & is added to the table | ||
| 654 | 862 |
End: Append new fields to table & | ||
| 655 | 863 |
Original table requires adjustment | ||
| 656 | 864 |
Problems arise with customer long field | ||
| 657 | 865 |
Append & included in proposal without check | ||
| 658 | 866 |
Append cannot be created because table has table type & | Space: object requires documentation | |
| 659 | 867 |
Table & has long field (therefore not possible to create appends) | Space: object requires documentation | |
| 660 | 868 |
Customer has extended the key of table & | ||
| 661 | 869 |
Adjustment of table & can be completed | Space: object requires documentation | |
| 662 | 870 |
New version of technical settings for table & could not be read | ||
| 663 | 871 |
Attribute had to be modified | Space: object requires documentation | |
| 664 | 872 |
Append & could not be activated and will therefore be reset | Space: object requires documentation | |
| 665 | 873 |
Append & was activated with warnings => table & partially active | Space: object requires documentation | |
| 666 | 874 |
Append & was activated => table & partially active | Space: object requires documentation | |
| 667 | 875 |
Attribute could not be copied | Space: object requires documentation | |
| 668 | 876 |
& deleted by SAP as &. May not be copied to the proposal | ||
| 669 | 877 |
Field & deleted by SAP. May not be copied to the proposal | ||
| 670 | 878 |
Objects not saved may only be treated in change mode | Space: object requires documentation | |
| 671 | 879 |
Table & is not active in the ABAP Dictionary | Space: object requires documentation | |
| 672 | 880 |
Entry & is not allowed as include description | Space: object requires documentation | |
| 673 | 881 |
Please enter a valid field name | Space: object requires documentation | |
| 674 | 882 |
& is already being processed by user & | Space: object requires documentation | |
| 675 | 883 |
Entry for & was removed | Space: object requires documentation | |
| 676 | 884 |
All entries for table & were removed | Space: object requires documentation | |
| 677 | 885 |
& was entered as for deletion in 3.0 | Space: object requires documentation | |
| 678 | 886 |
& was entered as for changing in 3.0 | Space: object requires documentation | |
| 679 | 887 |
Table & belongs to central Basis, so appends are not allowed | ||
| 680 | 888 |
Proposal for table & accepted | Space: object requires documentation | |
| 681 | 889 |
Proposal for table & could not be accepted | Space: object requires documentation | |
| 682 | 890 |
Proposal for table & edited and saved in editor | Space: object requires documentation | |
| 683 | 891 |
Error occurred when automatically adjusting table & | Space: object requires documentation | |
| 684 | 892 |
& under version number & read in the version management | Space: object requires documentation | |
| 685 | 900 |
************** General Tables and Fields ********************** | Space: object requires documentation | |
| 686 | 901 |
Changes to table & were not passed on to view & | ||
| 687 | 902 |
&-structure: invalid change: data type of field & changed | Space: object requires documentation | |
| 688 | 903 |
&-structure: invalid change: length of field & was changed | Space: object requires documentation | |
| 689 | 904 |
&-structure: invalid change: decimal places of field & changed | Space: object requires documentation | |
| 690 | 905 |
List of dependent views: | ||
| 691 | 906 |
View &: dependent on table & | ||
| 692 | 907 |
Activate dependent view & | ||
| 693 | 908 |
Activation of dependent view & successful | ||
| 694 | 909 |
Dependent view & was activated with warnings | ||
| 695 | 910 |
Dependent view & was not activated | ||
| 696 | 911 |
Table & was activated >>> error in dependent views | ||
| 697 | 912 |
View &: update of activation flag failed | ||
| 698 | 913 |
&-structure: invalid change: field & should be deleted | Space: object requires documentation | |
| 699 | 914 |
&-structure: invalid change: position field & changed | Space: object requires documentation | |
| 700 | 915 |
&-structure: field & data element changed | Space: object requires documentation | |
| 701 | 916 |
List of dependent search helps: | Space: object requires documentation | |
| 702 | 917 |
Search help &: Dependent on table & | Space: object requires documentation | |
| 703 | 918 |
Activate dependent search help & | Space: object requires documentation | |
| 704 | 919 |
Activatation of dependent search help & successful | Space: object requires documentation | |
| 705 | 920 |
Dependent search help & was activated with warnings | Space: object requires documentation | |
| 706 | 921 |
Dependent search help & was not activated | Space: object requires documentation | |
| 707 | 922 |
Search help &: Update of activation flag failed | Space: object requires documentation | |
| 708 | 923 |
Changes to table & are not passed on to search help & | Space: object requires documentation | |
| 709 | 924 |
Table & was activated >>> Error in dependent search helps | Space: object requires documentation | |
| 710 | 925 |
List of dependent structured types: | Space: object requires documentation | |
| 711 | 926 |
Structured type: & | Space: object requires documentation | |
| 712 | 927 |
List of dependent table types: | Space: object requires documentation | |
| 713 | 928 |
Table type: & | Space: object requires documentation | |
| 714 | 929 |
Activate dependent structured type & | Space: object requires documentation | |
| 715 | 930 |
Dependent structured type & successfully activated | Space: object requires documentation | |
| 716 | 931 |
Dependent structured type & was not activated successfully | Space: object requires documentation | |
| 717 | 932 |
Dependent structured type & was activated with warnings | Space: object requires documentation | |
| 718 | 933 |
Table &: latest nametab header could not be read | Space: object requires documentation | |
| 719 | 934 |
Table &: acitve nametab header could not be written | Space: object requires documentation | |
| 720 | 935 |
Table &: inactive nametab header could not be written | Space: object requires documentation | |
| 721 | 936 |
Table/structure & was activated >>> error in dependent types | Space: object requires documentation | |
| 722 | 937 |
Dependent table type & was activated successfully | Space: object requires documentation | |
| 723 | 938 |
Dependent table type & was not activated successfully | Space: object requires documentation | |
| 724 | 939 |
Dependent table type & was activated with warnings | Space: object requires documentation | |
| 725 | 940 |
Structure &: nametab timestamps updated | Space: object requires documentation | |
| 726 | 941 |
No table name found | Space: object requires documentation | |
| 727 | 942 |
Table &: active nametab could not be read | Space: object requires documentation | |
| 728 | 943 |
Table &: Field ROLLNAME in nametab is already filled | Space: object requires documentation | |
| 729 | 944 |
Table &: latest nametab could not be written | Space: object requires documentation | |
| 730 | 945 |
Table &: DD sources could not be read | Space: object requires documentation | |
| 731 | 946 |
Table &: Data elements were entered in nametab | Space: object requires documentation | |
| 732 | 947 |
ABAP Dictionary Object &: Could not write nametab | Space: object requires documentation | |
| 733 | 948 |
Set data element information in nametab | Space: object requires documentation | |
| 734 | 949 |
Table &: field component type was filled | Space: object requires documentation | |
| 735 | 950 |
Table &: field component type could not be filled | Space: object requires documentation | |
| 736 | 951 |
Renamed data elements cannot be handled | Space: object requires documentation | |
| 737 | 952 |
Set information about fields of depth 0 in nametab header | Space: object requires documentation | |
| 738 | 953 |
Table &: Information about fields of depth 0 already set | Space: object requires documentation | |
| 739 | 954 |
Table &: BUFPARM was already set to & | Space: object requires documentation | |
| 740 | 955 |
Activate dependent lock object & | Space: object requires documentation | |
| 741 | 956 |
Activation of dependent lock object & was successful | Space: object requires documentation | |
| 742 | 957 |
Dependent lock object & was activated with warning | Space: object requires documentation | |
| 743 | 958 |
Dependent lock object & was not activated | Space: object requires documentation | |
| 744 | 959 |
Changes to table & were not passed on to lock object & | Space: object requires documentation | |
| 745 | 960 |
List of dependent lock objects: | Space: object requires documentation | |
| 746 | 961 |
Lock object &: Dependent on table & | Space: object requires documentation | |
| 747 | 962 |
Lock object &: Update of activation flag failed | Space: object requires documentation | |
| 748 | 963 |
Field & in table & is specified twice. Please check | Space: object requires documentation | |
| 749 | 964 |
Group name & in table & is specified twice | Space: object requires documentation | |
| 750 | 965 |
Group name & of include & matches field name | Space: object requires documentation | |
| 751 | 966 |
Include information copied to runtime objects | Space: object requires documentation | |
| 752 | 967 |
Runtime object table & could not be generated | Space: object requires documentation | |
| 753 | 968 |
Inactive nametab table & with includes written successfully | Space: object requires documentation | |
| 754 | 969 |
Active nametab table & with includes successfully written | Space: object requires documentation | |
| 755 | 970 |
& nametabs of & table successfully generated | Space: object requires documentation | |
| 756 | 971 |
Conversion of table & successful | Space: object requires documentation | |
| 757 | 972 |
Conversion of table & canceled | Space: object requires documentation | |
| 758 | 973 |
Field &: Data type & is not supported | Space: object requires documentation | |
| 759 | 974 |
Table &: UUID was regenerated; active nametab header was written | Space: object requires documentation | |
| 760 | 975 |
Table &: Inconsistency between nametab and sources. Check! | The short text describes the object sufficiently | |
| 761 | 976 |
Table & too wide for DB & (width: &, maximum width: &) | The short text describes the object sufficiently | |
| 762 | 977 |
Table &: Check for database & not possible | The short text describes the object sufficiently | |
| 763 | 978 |
Table &: Key too wide for DB & (width: &, maximum width: &) | The short text describes the object sufficiently | |
| 764 | 979 |
Index &-&: Check for database & not possible | The short text describes the object sufficiently | |
| 765 | 980 |
Index & too wide for DB & (width: &, maximum width: &) | The short text describes the object sufficiently | |
| 766 | 981 |
Check & as table, not as View | The short text describes the object sufficiently | |
| 767 | 982 |
Table & has no indices | The short text describes the object sufficiently | |
| 768 | 983 |
Number of Tables Without Text Language Indicator: & | The short text describes the object sufficiently | |
| 769 | 984 |
No pool table found | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141121 | SAP |
| SAP Release Created in |
