SAP ABAP Message Class MC (Aggregate: views, matchcodes, lock objects)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD
⤷
SDVI (Package) ABAP/4 Dictionary: Views, Lock Objects
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-DWB-DIC-AC (Application Component) Activation Program, Conversion Program, DB Utility, MC, SPDD⤷
SDVI (Package) ABAP/4 Dictionary: Views, Lock Objects 
Attributes
| Message class |  |
MC |
| Short Description |  |
Aggregate: views, matchcodes, lock objects |
| Changed On |  |
20141121 |
| Last Changed At |  |
124015 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
DB error: (& &) | Space: object requires documentation | |
| 2 | 002 |
Matchcode field &-& no longer exists | ||
| 3 | 003 |
Log & does not exist | Space: object requires documentation | |
| 4 | 004 |
Enter a valid application class | Space: object requires documentation | |
| 5 | 005 |
Background job & successfully scheduled | Space: object requires documentation | |
| 6 | 006 |
Save the object and select the function again | Space: object requires documentation | |
| 7 | 007 |
Internal view & for MC object & not found | Space: object requires documentation | |
| 8 | 009 |
Table & does not exist. Please also check table type | Space: object requires documentation | |
| 9 | 010 |
& violates SAA standard | Space: object requires documentation | |
| 10 | 011 |
Enter a primary table | Space: object requires documentation | |
| 11 | 012 |
Matchcode object & is not active. Start by activating | Space: object requires documentation | |
| 12 | 013 |
Matchcode ID &-& is not active | Space: object requires documentation | |
| 13 | 014 |
No appropriate object found | Space: object requires documentation | |
| 14 | 015 |
Transfer parameters missing | Space: object requires documentation | |
| 15 | 016 |
Choose a 4-character matchcode object name | Space: object requires documentation | |
| 16 | 017 |
Correct matchcode ID | Space: object requires documentation | |
| 17 | 018 |
No cyclic foreign keys possible | Space: object requires documentation | |
| 18 | 019 |
Name clashes with that of another Dictionary object | Space: object requires documentation | |
| 19 | 020 |
Matchcode object & is locked by user & | Space: object requires documentation | |
| 20 | 021 |
No authorization for matchcode object & | Space: object requires documentation | |
| 21 | 022 |
Matchcode ID &-& locked by user & | Space: object requires documentation | |
| 22 | 023 |
No authorization for matchcode ID &-& | ||
| 23 | 024 |
Foreign key field &-& not from table & (see long text) | Space: object requires documentation | |
| 24 | 025 |
Start by withdrawing the modification to matchcode object & | ||
| 25 | 026 |
Matchcode ID &-& does not exist. Display not possible | Space: object requires documentation | |
| 26 | 027 |
Join with partial foreign key | Space: object requires documentation | |
| 27 | 028 |
Join using a constant in the foreign key | Space: object requires documentation | |
| 28 | 029 |
Relationship from & to & no longer exists | Space: object requires documentation | |
| 29 | 030 |
Matchcode object & is being processed by & | Space: object requires documentation | |
| 30 | 031 |
Matchcode object & is new and being processed by & | ||
| 31 | 032 |
Matchcode ID &-& is being processed by & | ||
| 32 | 033 |
Matchcode ID &-& is new and being processed by & | ||
| 33 | 034 |
Pooled table not created until MC ID is activated | ||
| 34 | 035 |
Pool not created until MC object is activated | Space: object requires documentation | |
| 35 | 036 |
Enter an update type | Space: object requires documentation | |
| 36 | 037 |
Enter a function module | Space: object requires documentation | |
| 37 | 038 |
Function module & does not exist yet | Space: object requires documentation | |
| 38 | 039 |
Index & to table & does not yet exist | Space: object requires documentation | |
| 39 | 040 |
Matchcode object & saved | Space: object requires documentation | |
| 40 | 041 |
Foreign key dependencies saved | ||
| 41 | 042 |
Fields were saved | ||
| 42 | 043 |
Matchcode ID &-& saved | Space: object requires documentation | |
| 43 | 044 |
Define one-position matchcode ID | ||
| 44 | 045 |
Matchcode object & has already been saved | Space: object requires documentation | |
| 45 | 046 |
Matchcode ID &-& has already been saved | Space: object requires documentation | |
| 46 | 047 |
First delete the fields of table & from the ID | Space: object requires documentation | |
| 47 | 048 |
This cursor position not allowed when adding fields | Space: object requires documentation | |
| 48 | 049 |
Position the cursor correctly | Space: object requires documentation | |
| 49 | 050 |
Position cursor on a table name | Space: object requires documentation | |
| 50 | 051 |
MC object & reset | Space: object requires documentation | |
| 51 | 052 |
Matchcode ID &-& reset | Space: object requires documentation | |
| 52 | 053 |
First delete the selection fields of table & from the ID | Space: object requires documentation | |
| 53 | 054 |
The value of the U/L flag does not fit the domain of the data element | Space: object requires documentation | |
| 54 | 055 |
Matchcode object & deleted | ||
| 55 | 056 |
Matchcode ID &-& deleted | Space: object requires documentation | |
| 56 | 057 |
Matchcode object & not deleted (log) | Space: object requires documentation | |
| 57 | 058 |
Matchcode ID &-& not deleted (log) | Space: object requires documentation | |
| 58 | 059 |
First delete the old database view | ||
| 59 | 060 |
Field name & not unique | Space: object requires documentation | |
| 60 | 061 |
Field &-& not found | ||
| 61 | 062 |
Field &-& (data type & not allowed in matchcodes) | Space: object requires documentation | |
| 62 | 063 |
Data element for field &-& has changed | ||
| 63 | 064 |
The domain of field &-& has changed | ||
| 64 | 065 |
Table & cannot be accessed from primary table | Space: object requires documentation | |
| 65 | 066 |
Table &: (Switching not allowed) | Space: object requires documentation | |
| 66 | 067 |
Foreign key & after & is not a key extension | Space: object requires documentation | |
| 67 | 068 |
Table & is not transparent | Space: object requires documentation | |
| 68 | 069 |
Deletion flag not allowed with update type I (Matchcode ID &) | Space: object requires documentation | |
| 69 | 070 |
Field & is part of a foreign key | Space: object requires documentation | |
| 70 | 071 |
Field &-& required as a key field | Space: object requires documentation | |
| 71 | 072 |
Required key fields transferred automatically | ||
| 72 | 073 |
Primary table cannot be deleted | Space: object requires documentation | |
| 73 | 074 |
Index to table & was not activated for matchcode ID &-& | ||
| 74 | 075 |
Database index & for table & must be converted | ||
| 75 | 076 |
DB index & for table & has not yet been created in the database | ||
| 76 | 077 |
Build matchcode &-& | ||
| 77 | 078 |
No index has been generated for matchcode ID &-& | ||
| 78 | 079 |
DB operation executed for index & | ||
| 79 | 080 |
Field &-& not defined in MC object & | Space: object requires documentation | |
| 80 | 081 |
Enter length and offset correctly | Space: object requires documentation | |
| 81 | 082 |
Data element & does not have expected length & | Space: object requires documentation | |
| 82 | 083 |
Please correct output field intersection | ||
| 83 | 084 |
Note maximum line length for output field | Space: object requires documentation | |
| 84 | 085 |
Key fields may not be component fields | Space: object requires documentation | |
| 85 | 086 |
The matchcode object does not contain table & | Space: object requires documentation | |
| 86 | 087 |
Output position not allowed. Please correct | Space: object requires documentation | |
| 87 | 088 |
Data element & is not active | Space: object requires documentation | |
| 88 | 089 |
Enter a suitable data element for component fields | Space: object requires documentation | |
| 89 | 090 |
Matchcode object & was activated | Space: object requires documentation | |
| 90 | 091 |
Matchcode object & was not activated | Space: object requires documentation | |
| 91 | 092 |
Matchcode ID &-& was activated | Space: object requires documentation | |
| 92 | 093 |
Matchcode ID $-$ not activated | ||
| 93 | 094 |
Matchcode object & activated with warning message | Space: object requires documentation | |
| 94 | 095 |
Data element & is not of expected type & | Space: object requires documentation | |
| 95 | 096 |
Data element & was created and activated | ||
| 96 | 097 |
Matchcode ID &-& activated with warnings | Space: object requires documentation | |
| 97 | 098 |
Error when reading matchcode object & | ||
| 98 | 099 |
Error when accessing Table & (GETDD23V) | ||
| 99 | 100 |
Report template for gen. function modules for matchcode maint. missing | Space: object requires documentation | |
| 100 | 101 |
Report template for gen. function modules for matchcode maint. changed | Space: object requires documentation | |
| 101 | 102 |
Root table & contains no records | ||
| 102 | 103 |
Field & of table & missing from FIELD_MAP | Space: object requires documentation | |
| 103 | 104 |
No Matchcode ID for MC object & selected for maintenance | Space: object requires documentation | |
| 104 | 105 |
Function modules for maintaining MC object & generated | ||
| 105 | 106 |
Matchcode object & - error generating maintenance function modules | ||
| 106 | 107 |
& records for client & matchcode ID &-& deleted | ||
| 107 | 108 |
& records for client & matchcode ID &-& generated | ||
| 108 | 109 |
Internal error reading the root table (look at syslog) | ||
| 109 | 110 |
Incorrect cursor position | Space: object requires documentation | |
| 110 | 111 |
Choose one or more matchcode IDs | Space: object requires documentation | |
| 111 | 112 |
Incorrect input parameter | Space: object requires documentation | |
| 112 | 113 |
MC object & is already being maintained by another job | ||
| 113 | 114 |
Table T002T has not been correctly maintained (-> long text) | ||
| 114 | 115 |
This definition of matchcode object & is not supported | Space: object requires documentation | |
| 115 | 116 |
& records deleted for matchcode ID &-& | ||
| 116 | 117 |
& records generated for matchcode ID &-& | ||
| 117 | 118 |
No background job started for matchcode object & (TBATG used) | ||
| 118 | 119 |
The repetition period for the background job & is & days | ||
| 119 | 120 |
Unload matchcode ID &-& | ||
| 120 | 121 |
Matchcode ID &-& deleted | ||
| 121 | 122 |
Background job & planned for time & date & | Space: object requires documentation | |
| 122 | 123 |
Error & when starting background job & | Space: object requires documentation | |
| 123 | 124 |
Start of background job is in the past | Space: object requires documentation | |
| 124 | 125 |
Database view & not maintained for matchcode ID &-& | ||
| 125 | 126 |
Job repetition period only allowed with background processing | Space: object requires documentation | |
| 126 | 127 |
Matchcode ID &-& recreated with & records | ||
| 127 | 128 |
Background jobs were scheduled for the MC object request | Space: object requires documentation | |
| 128 | 129 |
Database view & was maintained for matchcode ID &-& | ||
| 129 | 130 |
DB index & was deleted from table & | ||
| 130 | 131 |
DB index & was created in table & | ||
| 131 | 132 |
DB index & in table & was converted | ||
| 132 | 133 |
DB index & already exists in table & | ||
| 133 | 134 |
Table & was created in the database | ||
| 134 | 135 |
Table & could not be created in the database | ||
| 135 | 136 |
Error generating version - matchcode object & function & | ||
| 136 | 137 |
Background job & uses version & | ||
| 137 | 138 |
Structure of matchcode object & only permits transparent IDs | ||
| 138 | 139 |
No matchcode records are generated for &-& | ||
| 139 | 140 |
An error occurred when unloading the matchcode ID &-& | ||
| 140 | 141 |
An error occurred when activating the matchcode ID &-& | ||
| 141 | 142 |
Matchcode ID &-& successfully converted | ||
| 142 | 143 |
Error constructing the matchcode records for matchcode ID &-& | ||
| 143 | 144 |
Matchcode ID &-& does not actively exist or cannot be maintained | ||
| 144 | 145 |
Error selecting matchcode IDs | ||
| 145 | 146 |
Physically implemented IDs may be created for matchcode object & | Space: object requires documentation | |
| 146 | 147 |
No physically impemented IDs possible for matchcode object & | ||
| 147 | 148 |
No active matchcode objects exist | Space: object requires documentation | |
| 148 | 149 |
Uppercase/lowercase not significant for matchcode ID &-& | ||
| 149 | 150 |
Matchcode object & does not exist | Space: object requires documentation | |
| 150 | 151 |
MC object & not activated | Space: object requires documentation | |
| 151 | 152 |
Incorrect parameter & ('&' not allowed) | ||
| 152 | 153 |
FK fields for & & missing | ||
| 153 | 154 |
Field descriptions for table & missing | ||
| 154 | 155 |
Text table & does not have a language key field | ||
| 155 | 156 |
Not all MC IDs for MC object & are active | ||
| 156 | 157 |
No matchcode ID exists for matchcode object & | ||
| 157 | 158 |
Matchcode object & (error in & & &) | ||
| 158 | 159 |
Matchcode IDs of matchcode object & are transparent (-> long text) | ||
| 159 | 160 |
Error in definition of MC object or MC ID | ||
| 160 | 161 |
Error when generating function group or module | ||
| 161 | 162 |
& is missing for function REC. Continue with CRE | ||
| 162 | 163 |
There are no active matchcode objects for search pattern & | Space: object requires documentation | |
| 163 | 164 |
Restart ambiguous for matchcode object & - see ID &,& | ||
| 164 | 165 |
& records were deleted in several clients for matchcode ID &-& | ||
| 165 | 166 |
Matchcode ID &-& locked - try again later | ||
| 166 | 167 |
Request for matchcode object & not executed successfully | Space: object requires documentation | |
| 167 | 168 |
Matchcode object & could not be unlocked after maintenance | ||
| 168 | 169 |
Matchcode ID &-& could not be released | ||
| 169 | 170 |
Began building records of matchcode object & at time & | ||
| 170 | 171 |
Began deleting records of matchcode object & at time & | ||
| 171 | 172 |
Began deleting flagged records of matchcode object & at time & | ||
| 172 | 173 |
Began restarting matchcode object & at time & | ||
| 173 | 174 |
Maintenance of physical IDs of matchcode object & completed at & | ||
| 174 | 175 |
View & was deleted in the database | ||
| 175 | 176 |
Action for matchcode object & performed successfully | Space: object requires documentation | |
| 176 | 177 |
Not all requests were performed successfully (-> long text) | Space: object requires documentation | |
| 177 | 178 |
Maintenance of matchcode object & on & | ||
| 178 | 179 |
Background job started for data maintenance of matchcode object & | ||
| 179 | 180 |
Background job for data maintenance of MC object & ended with errors | ||
| 180 | 181 |
Generate maintenance function modules for & at & | ||
| 181 | 182 |
Requests for search pattern & performed successfully | Space: object requires documentation | |
| 182 | 183 |
Restarting is not possible with matchcode object & | ||
| 183 | 184 |
Maintenance was cancelled for matchcode object & | ||
| 184 | 185 |
Unexpected error when deleting matchcode ID & & & | ||
| 185 | 186 |
Write error with TBATG function & object type & object name & ID & | ||
| 186 | 187 |
Error writing to inactive nametab & & & & | ||
| 187 | 188 |
Error with TBATG entry object type & function & object name & | ||
| 188 | 189 |
Maintenance of matchcode object & locked (try again) | ||
| 189 | 190 |
Unexpected error when locking matchcode object & | ||
| 190 | 191 |
Unexpected error when unlocking (matchcode object &) | ||
| 191 | 192 |
Matchcode object & does not have any transparent matchcode IDs | ||
| 192 | 193 |
Matchcode object & was not maintained | ||
| 193 | 194 |
Matchcode maintenance for search pattern & at & | ||
| 194 | 195 |
Request not performed successfully for all matchcode IDs | Space: object requires documentation | |
| 195 | 196 |
Matchcode ID field M_&&-& must be updated | ||
| 196 | 197 |
Check of data elements for search pattern & successful | Space: object requires documentation | |
| 197 | 198 |
Error checking the data elements of the matchcode IDs for search pattern | Space: object requires documentation | |
| 198 | 199 |
Uppercase/lowercase significant for all physical matchcode IDs | Space: object requires documentation | |
| 199 | 200 |
MC ID & & activated | ||
| 200 | 201 |
Activation of matchcode ID &-& canceled | ||
| 201 | 202 |
Matchcode object & not active | Space: object requires documentation | |
| 202 | 203 |
Matchcode ID &-& not found | ||
| 203 | 204 |
Table & already exists. Choose another name | ||
| 204 | 205 |
Matchcode table has & bytes (maximum & bytes). | ||
| 205 | 206 |
Matchcode table & could not be activated | ||
| 206 | 207 |
Matchcode table & created and activated | ||
| 207 | 208 |
Field &-& not found | Space: object requires documentation | |
| 208 | 209 |
ID field not contained in matchcode object | ||
| 209 | 210 |
There are no fields for matchcode ID &-& | ||
| 210 | 211 |
Key length of the root table for matchcode object & is too long | Space: object requires documentation | |
| 211 | 212 |
Data element & could not be created | ||
| 212 | 213 |
Activate Matchcode ID & | ||
| 213 | 214 |
Error when reading the tables of MC object & | ||
| 214 | 215 |
There are still no IDs for MC object & | Space: object requires documentation | |
| 215 | 216 |
Internal error | ||
| 216 | 217 |
Index & to table & is used for matchcode ID &-& | ||
| 217 | 218 |
Index & to table & is still in the database | ||
| 218 | 219 |
Index & in table & was deleted | ||
| 219 | 220 |
Status parameter & invalid | ||
| 220 | 221 |
Control parameter & invalid | ||
| 221 | 222 |
Matchcode ID &-& must be converted | ||
| 222 | 223 |
Error reading field desc. for MCO & MC ID & index & tab. & | ||
| 223 | 224 |
No deletion flag allowed for update type 'I' | ||
| 224 | 225 |
Table & is not transparent | ||
| 225 | 226 |
Generated matchcode pooled table & was deleted | ||
| 226 | 227 |
Generated matchcode view & was deleted in ABAP Dictionary | ||
| 227 | 228 |
Start by deleting the view on the database | ||
| 228 | 229 |
Component fields are not allowed with transparent matchcodes | Space: object requires documentation | |
| 229 | 230 |
Key field &1-&2 missing | ||
| 230 | 231 |
Foreign key from & to & does not exist | ||
| 231 | 232 |
Key field & lies outside the key area | ||
| 232 | 233 |
Field &-& does not belong to a matchcode object or ID table | ||
| 233 | 234 |
Selection condition incorrect | ||
| 234 | 235 |
Matchcode object & contains no ID of update type 'P' | Space: object requires documentation | |
| 235 | 236 |
No suitable index exists yet for matchcode ID &-& (-> long text) | Space: object requires documentation | |
| 236 | 237 |
Too many synchronous matchcode IDs for table & | ||
| 237 | 238 |
Matchcode ID &-& not physically created | ||
| 238 | 239 |
Pool & for matchcode object & deleted on database | ||
| 239 | 240 |
Pool & could not be deleted on database | ||
| 240 | 241 |
Pool & could not be created on database | ||
| 241 | 242 |
Pool & created for matchcode object & on database | ||
| 242 | 243 |
Background proc. currently not possible (Please read long text) | Space: object requires documentation | |
| 243 | 244 |
No & action for classification matchcode ID &-& | ||
| 244 | 245 |
Requests not performed successfully | Space: object requires documentation | |
| 245 | 246 |
Background job DB-MCOB& scheduled for matchcode object & | ||
| 246 | 247 |
Background jobs successfully scheduled for search pattern & | ||
| 247 | 248 |
You did not select a matchcode ID | ||
| 248 | 249 |
Fields without data elements not allowed in MC objects | Space: object requires documentation | |
| 249 | 250 |
MC ID &-& consistent | ||
| 250 | 251 |
MC ID &-& inconsistent | ||
| 251 | 252 |
Consistency check for Matchcode ID & | ||
| 252 | 253 |
Error when updating function module MC_UPDATE_& | ||
| 253 | 254 |
Consistency check for matchcode object & | ||
| 254 | 255 |
Matchcode object & is consistent | ||
| 255 | 256 |
Matchcode object & is not consistent | ||
| 256 | 257 |
No matchcode objects exist with physically implemented IDs | ||
| 257 | 258 |
Matchcode objects for search pattern & not maintained | ||
| 258 | 259 |
Matchcode objects for search pattern & successfully maintained | ||
| 259 | 260 |
Matchcode object & was activated | ||
| 260 | 261 |
Matchcode object & could not be activated | ||
| 261 | 262 |
Matchcode object & not found | ||
| 262 | 263 |
Matchcode ID &-& does not fit new matchcode object | ||
| 263 | 264 |
Matchcode object & has no fields | ||
| 264 | 265 |
You changed the tables in matchcode ID &-& (see long text) | ||
| 265 | 266 |
Could not create pool & in ABAP Dictionary | Space: object requires documentation | |
| 266 | 267 |
Pool & created and activated in ABAP Dictionary | Space: object requires documentation | |
| 267 | 268 |
Matchcode pool could not be generated | ||
| 268 | 269 |
Matchcode table & still contains data (see long text) | ||
| 269 | 270 |
Activate matchcode object & | ||
| 270 | 271 |
Field &-&: (Table & does not belong to matchcode object) | ||
| 271 | 272 |
Change matchcode ID &-& and reactivate | ||
| 272 | 273 |
Update type & not allowed | ||
| 273 | 274 |
Unexpected error while calling function & | Space: object requires documentation | |
| 274 | 277 |
Sample pool & not found | ||
| 275 | 278 |
Runtime object could not be generated | ||
| 276 | 279 |
Error when reading matchcode object (inconsistency) | ||
| 277 | 280 |
Name of matchcode object not allowed | ||
| 278 | 281 |
Pool & does not yet exist in the database | ||
| 279 | 282 |
Table & does not exist or has incorrect table type | ||
| 280 | 283 |
Table & does not have a foreign key for the primary table | ||
| 281 | 284 |
Field &-&: (foreign key dependency to table & missing) | ||
| 282 | 285 |
Field in matchcode object not allowed | ||
| 283 | 286 |
Invalid relationship structure in matchcode object | ||
| 284 | 287 |
Function module & updated | ||
| 285 | 288 |
Function module & could not be updated | ||
| 286 | 289 |
Table & still used in matchcode ID &-& | ||
| 287 | 290 |
Base field &-& still being used in matchcode ID &-& | ||
| 288 | 291 |
Pool & still exists in the database | ||
| 289 | 292 |
IDs still exist for matchcode object & | Space: object requires documentation | |
| 290 | 293 |
Runtime object was created | ||
| 291 | 294 |
Pool & for matchcode object & was deleted | ||
| 292 | 295 |
Inconsistency between N and A versions of matchcode object field & | ||
| 293 | 296 |
Inconsistency between N and A versions (headers, tables) of MC obj. & | ||
| 294 | 297 |
Error deleting runtime object & | ||
| 295 | 298 |
Runtime object was created for matchcode ID &-& | ||
| 296 | 299 |
All matchcode pools on the DB also exist in the ABAP Dictionary | Space: object requires documentation | |
| 297 | 300 |
*** 301 - 309 reserved for matchcode selection routines MC_... | ||
| 298 | 301 |
MC ID & does not exist for MC object & | Space: object requires documentation | |
| 299 | 302 |
Incorrect search criteria. Please correct | Space: object requires documentation | |
| 300 | 303 |
There are more than $ records. Please be more specific | Space: object requires documentation | |
| 301 | 304 |
No appropriate matchcode data found | Space: object requires documentation | |
| 302 | 305 |
Function module & for matchcode ID &-& missing | Space: object requires documentation | |
| 303 | 306 |
Matchcode pool & exists on the DB but not in the ABAP Dictionary | ||
| 304 | 307 |
Database view & could not be deleted | ||
| 305 | 308 |
Internal error occurred when maintaining matchcode object & | ||
| 306 | 309 |
Exactly one record was found | ||
| 307 | 310 |
Start selection program generation for & matchcode objects | ||
| 308 | 311 |
Selection program generation completed with & errors | ||
| 309 | 312 |
Selection program & generated for matchcode object & | ||
| 310 | 313 |
Generation of program & aborted with error & | ||
| 311 | 314 |
TADIR and TLOCK conversion for matchcodes successfully completed | ||
| 312 | 315 |
& TADIR entries 'R3TR PROG MC_...' deleted | ||
| 313 | 316 |
TADIR entry & deleted | ||
| 314 | 318 |
Maintenance function module for matchcode object & cannot be deleted | ||
| 315 | 319 |
System matchcode ID may not be deactivated | ||
| 316 | 320 |
Matchcode ID &-& activated successfully | Space: object requires documentation | |
| 317 | 321 |
Table & deleted on the database | ||
| 318 | 322 |
Table & does not exist on the database | ||
| 319 | 323 |
View & created on the database | ||
| 320 | 324 |
View & already exists on the database | ||
| 321 | 325 |
Matchcode object & converted successfully | ||
| 322 | 326 |
Matchcode object & not converted successfully | ||
| 323 | 327 |
Deactivation of MC IDs for matchcode object & not required | ||
| 324 | 328 |
Matchcode ID &-& could not be activated | ||
| 325 | 329 |
Matchcode ID &-& was not deactivated | Space: object requires documentation | |
| 326 | 330 |
Deactivate matchcode ID &-& | ||
| 327 | 331 |
Matchcode ID &-& successfully converted | ||
| 328 | 332 |
Matchcode ID &-& was converted with warnings | ||
| 329 | 333 |
Matchcode ID &-& could not be converted | ||
| 330 | 334 |
Warning when building the matchcode records for ID &-& | ||
| 331 | 335 |
Error occurred when generating the explain plan for the search help | ||
| 332 | 336 |
An error occurred when entering the search conditions (see long text) | ||
| 333 | 337 |
Explain plan cannot be displayed at the moment | ||
| 334 | 338 |
Generated SQL instruction is longer than intended in program | ||
| 335 | 339 |
Table or view does not contain any fields | ||
| 336 | 340 |
Table or view has no entry in the nametab (SAP control table) | ||
| 337 | 341 |
Internal error when generating the explain plan | ||
| 338 | 342 |
Error when generating an auxiliary program | ||
| 339 | 343 |
Not necessary to build matchcode records | Space: object requires documentation | |
| 340 | 344 |
Not possible to start sapmaco in the background for matchcode object & | Space: object requires documentation | |
| 341 | 345 |
Error occurred when running sapmaco in the background for & -> long text | Space: object requires documentation | |
| 342 | 348 |
Matchcodes are not supported in Unicode systems (see long text) | Space: object requires documentation | |
| 343 | 349 |
Matchcodes no longer supported (-> Long text) | Space: object requires documentation | |
| 344 | 350 |
Lock object & created | Space: object requires documentation | |
| 345 | 351 |
Table & not found | Space: object requires documentation | |
| 346 | 352 |
Lock object & is not active | ||
| 347 | 353 |
Lock object & could not be generated | Space: object requires documentation | |
| 348 | 354 |
Lock mode & not allowed | Space: object requires documentation | |
| 349 | 355 |
Caution: Function modules contain reference structures | Space: object requires documentation | |
| 350 | 356 |
No base tables for lock object & found | ||
| 351 | 357 |
No foreign key fields were found for field &-& | ||
| 352 | 358 |
Field &-& could not be found as lock argument | ||
| 353 | 359 |
Function module & already exists and is locked | ||
| 354 | 360 |
Function module & already exists and was not deleted | ||
| 355 | 361 |
Function group & is locked | ||
| 356 | 362 |
Function block & could not be generated | ||
| 357 | 363 |
Report & could not be found | ||
| 358 | 364 |
The function groups &Q, &0,...,& are already full | ||
| 359 | 365 |
Generated function groups for lock objects cannot be changed | ||
| 360 | 366 |
XPRA XDDENQAC: | ||
| 361 | 367 |
Application: Basis Client: * | ||
| 362 | 368 |
Function modules for lock object & could not be generated | ||
| 363 | 370 |
********* Dependencies table change<-> views *** PROG RADVIDEP | ||
| 364 | 371 |
Table type change not allowed for base table of view & | ||
| 365 | 372 |
Field &-& is still being used as a view field in view & | ||
| 366 | 373 |
Field &-& is still being used in selection condition/join of view & | ||
| 367 | 374 |
Adjust type/length/decimal places of view field &-& | ||
| 368 | 375 |
Adjust data element of view field &-& | ||
| 369 | 376 |
Adjust selection condition of view & to type change | ||
| 370 | 385 |
Activation caused by view & | Space: object requires documentation | |
| 371 | 386 |
&2 must be a maintenance view for view variant &1 | Space: object requires documentation | |
| 372 | 391 |
Standard append & for view & already exists | Space: object requires documentation | |
| 373 | 392 |
Standard name & for append view for view & is not allowed | Space: object requires documentation | |
| 374 | 393 |
Standard name & for append view for view & is already assigned | Space: object requires documentation | |
| 375 | 394 |
Editing of the append view for view & was terminated | Space: object requires documentation | |
| 376 | 395 |
Define a name for the append view | Space: object requires documentation | |
| 377 | 400 |
View checker for VIEW & started | ||
| 378 | 401 |
View & is not in ABAP Dictionary | Space: object requires documentation | |
| 379 | 402 |
View & is not created at database level | ||
| 380 | 403 |
View definitions in the ABAP Dictionary and database are not consistent | ||
| 381 | 404 |
View definition from the database could not be read | ||
| 382 | 405 |
Syntax of the view definition on the database is unknown | ||
| 383 | 406 |
Error from consistency layer (& - &) | ||
| 384 | 407 |
Undefined entry '&' in & | ||
| 385 | 408 |
Problems reading the joins from DD05P | ||
| 386 | 409 |
Number of fields in view differs from number in SELECT statement. | ||
| 387 | 410 |
View definitions at DD and DB level are consistent | Space: object requires documentation | |
| 388 | 411 |
View uses different tables at DD and DB level | ||
| 389 | 412 |
View uses different fields at DD and DB level | ||
| 390 | 413 |
JOIN conditions at DD and DB level are different | ||
| 391 | 414 |
Different selection conditions at DD and DB level | ||
| 392 | 415 |
Compare active version with the database | ||
| 393 | 416 |
Compare revised version with the database | ||
| 394 | 419 |
******* View check for VIEW & complete ****** | ||
| 395 | 420 |
Version management for object type & is not allowed here. | Space: object requires documentation | |
| 396 | 421 |
Number of key fields was limited to maximum number & | The short text describes the object sufficiently | |
| 397 | 440 |
Check matchcode objects for consistency | ||
| 398 | 441 |
Error when checking matchcode object (&) | ||
| 399 | 442 |
Naming convention vor & violated | ||
| 400 | 443 |
No root table defined for matchcode object & | ||
| 401 | 444 |
Table &2 used in matchcode object &1 does not exist in the DD | ||
| 402 | 445 |
No fields defined for matchcode object & | ||
| 403 | 446 |
Field &-& does not exist | ||
| 404 | 450 |
Convert IDs of matchcode object & | ||
| 405 | 451 |
Matchcode object & and its IDs successfully converted | ||
| 406 | 452 |
Warning/error in conversion of matchcode object & with IDs | ||
| 407 | 455 |
Runtime object deleted for matchcode object & | ||
| 408 | 456 |
Error when deleting runtime object matchcode object & | ||
| 409 | 457 |
Runtime object deleted for matchcode ID &-& | ||
| 410 | 458 |
Error when deleting runtime object matchcode ID &-& | ||
| 411 | 461 |
Incorrect entry for matchcode conversion program & & & & | ||
| 412 | 462 |
Utility function modules deleted (matchcode object &) | ||
| 413 | 463 |
Error in deleting utility function modules (MC object &) | ||
| 414 | 464 |
Function module MC_UPDATE_& deleted | Space: object requires documentation | |
| 415 | 465 |
Error when deleting function module MC_UPDATE_& | ||
| 416 | 466 |
Function module MC_UPDATE_& updated for ID &_& | ||
| 417 | 467 |
Error when updating function module MC_UPDATE_& ID &_& | ||
| 418 | 468 |
Utility function module generated (matchcode object &) | ||
| 419 | 469 |
Error when generating utility function modules (MC object &) | ||
| 420 | 470 |
Generate matchcode records for matchcode object & and IDs | ||
| 421 | 471 |
Matchcode records for matchcode object & and IDs constructed | ||
| 422 | 472 |
Function module MC_UPDATE_& was generated | Space: object requires documentation | |
| 423 | 473 |
Error when generating the function module MC_UPDATE_& | Space: object requires documentation | |
| 424 | 474 |
No active version of matchcode ID &-& | ||
| 425 | 475 |
Runtime object for matchcode object & was created | ||
| 426 | 476 |
Runtime object was created for matchcode ID &-& | ||
| 427 | 477 |
& & & is entered for background conversion | ||
| 428 | 478 |
& & & for background conversion already entered | ||
| 429 | 479 |
No physical pool created for matchcode object & | Space: object requires documentation | |
| 430 | 480 |
Function module MC_CREATE/UPDATE/DELETE_& not generated -> long text | Space: object requires documentation | |
| 431 | 482 |
Error during check whether & is a DDL SQL view | The short text describes the object sufficiently | |
| 432 | 504 |
Join fields &1-&2 and &3-&4 come from the same table | Space: object requires documentation | |
| 433 | 505 |
Define foreign key &-& for join operation correctly | Space: object requires documentation | |
| 434 | 506 |
Inconsistency in reference field for &-& | ||
| 435 | 507 |
& & activated | Space: object requires documentation | |
| 436 | 508 |
& & could not be activated (see log) | Space: object requires documentation | |
| 437 | 509 |
Search help & not inherited: Basis field &-& missing in view | The short text describes the object sufficiently | |
| 438 | 510 |
A view with the name & already exists | Space: object requires documentation | |
| 439 | 511 |
Primary table changed. Dependent elements will be deleted | Space: object requires documentation | |
| 440 | 512 |
& & is not active | Space: object requires documentation | |
| 441 | 513 |
Join views are always read-only | Space: object requires documentation | |
| 442 | 514 |
Help views are always read-only | ||
| 443 | 516 |
A matchcode object with the name & already exists | Space: object requires documentation | |
| 444 | 517 |
 lock object with the name & already exists | Space: object requires documentation | |
| 445 | 518 |
A table with the name & already exists | Space: object requires documentation | |
| 446 | 520 |
& & currently locked by user & | Space: object requires documentation | |
| 447 | 521 |
No authorization for & & | Space: object requires documentation | |
| 448 | 522 |
Enter a view type | Space: object requires documentation | |
| 449 | 523 |
Database views should contain only transparent tables | Space: object requires documentation | |
| 450 | 524 |
View contains more than one table | Space: object requires documentation | |
| 451 | 525 |
View & was deleted in the database | ||
| 452 | 526 |
View & was created in the database | ||
| 453 | 527 |
View & was converted in the database | ||
| 454 | 528 |
Database function was not performed (see log) | ||
| 455 | 530 |
& & is being processed by & | Space: object requires documentation | |
| 456 | 531 |
& & is new and is being processed by & | Space: object requires documentation | |
| 457 | 532 |
An error occurred when deleting view $ in the database | ||
| 458 | 533 |
An error occurred when creating view & in the database | ||
| 459 | 534 |
An error occurred when converting view & in the database | ||
| 460 | 535 |
Data element does not fit type/length of base fields | Space: object requires documentation | |
| 461 | 536 |
Domain for data element & conflicts with base field | Space: object requires documentation | |
| 462 | 537 |
Specify valid data element | Space: object requires documentation | |
| 463 | 538 |
Domain for &-& has changed | ||
| 464 | 539 |
Changed data element for &1-&2 was accepted for view field &3 | Space: object requires documentation | |
| 465 | 540 |
& & saved | Space: object requires documentation | |
| 466 | 541 |
Chosen tables and relations saved | Space: object requires documentation | |
| 467 | 542 |
Fields were saved | Space: object requires documentation | |
| 468 | 543 |
Required key fields transferred automatically | Space: object requires documentation | |
| 469 | 544 |
Tables changed. Field selection adapted accordingly | Space: object requires documentation | |
| 470 | 545 |
& & already saved | Space: object requires documentation | |
| 471 | 546 |
Table & is either not active or inconsistent | Space: object requires documentation | |
| 472 | 547 |
Tables and relationships already saved | Space: object requires documentation | |
| 473 | 548 |
Key fields proposed | Space: object requires documentation | |
| 474 | 549 |
No fields chosen. Saving not possible | Space: object requires documentation | |
| 475 | 550 |
Inconsistency found in fields. (Please correct.) | Space: object requires documentation | |
| 476 | 551 |
& & reset | Space: object requires documentation | |
| 477 | 552 |
The key fields of a database view must be kept together at the start | Space: object requires documentation | |
| 478 | 553 |
Views of type & are no longer supported. | Space: object requires documentation | |
| 479 | 554 |
View allows read-only access only. Maintenance not possible. | Space: object requires documentation | |
| 480 | 555 |
& & deleted | ||
| 481 | 556 |
All dependent elements deleted | Space: object requires documentation | |
| 482 | 557 |
& & could not be deleted (log) | Space: object requires documentation | |
| 483 | 558 |
'Display using Data Browser only' was set automatically | Space: object requires documentation | |
| 484 | 559 |
Restriction has no effect on primary table (see long text) | Space: object requires documentation | |
| 485 | 560 |
Field &-& does not exist | Space: object requires documentation | |
| 486 | 561 |
Table & does not belong to view & | Space: object requires documentation | |
| 487 | 562 |
Define an operator | Space: object requires documentation | |
| 488 | 563 |
Enter a continuation line | Space: object requires documentation | |
| 489 | 564 |
Define a condition for link & | Space: object requires documentation | |
| 490 | 565 |
Selection condition saved | Space: object requires documentation | |
| 491 | 566 |
Selection condition already saved | Space: object requires documentation | |
| 492 | 567 |
Correct entry in the continuation line | Space: object requires documentation | |
| 493 | 568 |
Enter a table name | Space: object requires documentation | |
| 494 | 569 |
Enter a field name | Space: object requires documentation | |
| 495 | 570 |
Define an "AND" or "OR" link | Space: object requires documentation | |
| 496 | 571 |
"OR" links only permitted for the same field | Space: object requires documentation | |
| 497 | 572 |
"AND" and "OR" are not allowed in a continuation line | ||
| 498 | 573 |
Correct the text constant | Space: object requires documentation | |
| 499 | 574 |
Constants must be enclosed in '...' | Space: object requires documentation | |
| 500 | 575 |
Correct number of constants for operator & | Space: object requires documentation | |
| 501 | 576 |
Enter a text literal or numeric constant | ||
| 502 | 577 |
Please correct the numeric constant | Space: object requires documentation | |
| 503 | 578 |
Enter a text literal as a constant | Space: object requires documentation | |
| 504 | 579 |
Field & is not contained in MC object & | Space: object requires documentation | |
| 505 | 580 |
Enter the base field in full | Space: object requires documentation | |
| 506 | 581 |
Enter a name for the view field | ||
| 507 | 582 |
Field & was copied to the selection condition | Space: object requires documentation | |
| 508 | 583 |
Enter a data element | ||
| 509 | 584 |
Data element does not exist | ||
| 510 | 585 |
Field &-& does not belong to one of the base tables | Space: object requires documentation | |
| 511 | 586 |
Entry of FORM routine and base field not allowed | Space: object requires documentation | |
| 512 | 587 |
Already saved | ||
| 513 | 588 |
Restrictions on fields with data type & not allowed | ||
| 514 | 589 |
Operator not yet supported | ||
| 515 | 590 |
Target field may only be assigned once | Space: object requires documentation | |
| 516 | 591 |
Select a target field | Space: object requires documentation | |
| 517 | 592 |
Define a lock mode | Space: object requires documentation | |
| 518 | 593 |
Please assign a name to the lock argument | Space: object requires documentation | |
| 519 | 594 |
Lock object names should begin with 'E' | Space: object requires documentation | |
| 520 | 595 |
Table & is not contained in lock object & | Space: object requires documentation | |
| 521 | 596 |
Name & for lock objects not allowed | Space: object requires documentation | |
| 522 | 600 |
System error occurred during lock management | Space: object requires documentation | |
| 523 | 601 |
Object requested is currently locked by user & | Space: object requires documentation | |
| 524 | 602 |
The requested object is locked by your own transaction | Space: object requires documentation | |
| 525 | 603 |
Lock table overflow | Space: object requires documentation | |
| 526 | 604 |
Own lock is no longer set for object requested | Space: object requires documentation | |
| 527 | 605 |
Invalid values in the enqueue/dequeue request | The short text describes the object sufficiently | |
| 528 | 610 |
Nametab inconsistency for matchcode ID &-& | ||
| 529 | 611 |
SQL error & occurred when deleting pooled table & | ||
| 530 | 612 |
Pooled table & successfully deleted | ||
| 531 | 613 |
Internal error occurred in function module & | ||
| 532 | 614 |
No adjustment of matchcode objects necessary | ||
| 533 | 615 |
Matchcode object & successfully adjusted | ||
| 534 | 616 |
Error occurred when adjusting matchcode object & | ||
| 535 | 619 |
Transparent matchcode IDs can no longer be created -> long text | Space: object requires documentation | |
| 536 | 620 |
Matchcode ID was migrated successfully | Space: object requires documentation | |
| 537 | 621 |
Search help & was already migrated | Space: object requires documentation | |
| 538 | 622 |
Search help & was not migrated | Space: object requires documentation | |
| 539 | 623 |
& search helps successfully created or enhanced | Space: object requires documentation | |
| 540 | 624 |
Search help & could not be created due to TADIR problem & | Space: object requires documentation | |
| 541 | 625 |
Matchcode ID &-& could not be migrated due to missing output field | Space: object requires documentation | |
| 542 | 626 |
Edit search help & (-> long text) | Space: object requires documentation | |
| 543 | 627 |
No enhanced SAP matchcodes exist | Space: object requires documentation | |
| 544 | 628 |
% extended SAP collective search helps are included in the correction | Space: object requires documentation | |
| 545 | 629 |
Creation of the request for SAP collective search helps failed | Space: object requires documentation | |
| 546 | 630 |
Request & created for extended SAP collective search helps | Space: object requires documentation | |
| 547 | 631 |
Release of request for extended SAP collective search helps failed | Space: object requires documentation | |
| 548 | 632 |
Collective search help & could not be marked as modified | Space: object requires documentation | |
| 549 | 633 |
M_ views could not be marked as modified | Space: object requires documentation | |
| 550 | 635 |
View logging: active nametab header could not be read | Space: object requires documentation | |
| 551 | 636 |
View logging: inactive nametab header could not be read | Space: object requires documentation | |
| 552 | 637 |
View logging: active nametab could not be read | Space: object requires documentation | |
| 553 | 638 |
View logging: active nametab could not be written | Space: object requires documentation | |
| 554 | 639 |
View logging: active nametab header was not written | Space: object requires documentation | |
| 555 | 640 |
View logging: inactive nametab header was not written | Space: object requires documentation | |
| 556 | 650 |
Consistency check for & & | ||
| 557 | 651 |
& & is consistent | ||
| 558 | 652 |
& & is not consistent | ||
| 559 | 653 |
Activate lock object & | ||
| 560 | 654 |
Check lock object & | ||
| 561 | 655 |
Lock object & is consistent | ||
| 562 | 656 |
Lock object & is not consistent | ||
| 563 | 659 |
Lock object & was activated without generating the function modules | ||
| 564 | 660 |
Lock object & activated | ||
| 565 | 661 |
Lock object & not activated | ||
| 566 | 662 |
& & not found | Space: object requires documentation | |
| 567 | 663 |
Data element & not found | ||
| 568 | 664 |
Domain & not found | ||
| 569 | 665 |
Table & already exists. Please choose another name | ||
| 570 | 666 |
View structure & could not be activated | ||
| 571 | 667 |
View structure & was activated | ||
| 572 | 668 |
View structure & was created | ||
| 573 | 669 |
View type not allowed | ||
| 574 | 670 |
Activate & & | ||
| 575 | 671 |
Activation currently locked by user & | ||
| 576 | 672 |
& & does not contain fields | Space: object requires documentation | |
| 577 | 673 |
& & could not be read | ||
| 578 | 674 |
Selection program & generated | ||
| 579 | 675 |
Selection program & could not be generated | ||
| 580 | 676 |
Relationship structure of & & inconsistent | Space: object requires documentation | |
| 581 | 677 |
Required field &-& missing | ||
| 582 | 678 |
ENQUEUE functions could not be generated | ||
| 583 | 679 |
Function module & in function group & generated | ||
| 584 | 680 |
Projection views may not contain more than one table | ||
| 585 | 681 |
View change. Database view & must be converted | ||
| 586 | 682 |
View & does not yet exist in the database | ||
| 587 | 683 |
Relationship &-& for table & does not exist | Space: object requires documentation | |
| 588 | 684 |
Error from database interface: (& &-&) | ||
| 589 | 685 |
View & still exists in the database | ||
| 590 | 686 |
ENQUEUE functions could not be deleted | ||
| 591 | 687 |
Entry 'Convert DB view &' made for background run | ||
| 592 | 688 |
Entry 'Generate DB view &' made for background run | ||
| 593 | 689 |
Entry 'Delete DB view &' made for background run | ||
| 594 | 690 |
Delete $ $ | ||
| 595 | 691 |
& & deleted | ||
| 596 | 692 |
& & not deleted | ||
| 597 | 693 |
Delete matchcode ID &-& | ||
| 598 | 694 |
Matchcode ID &-& deleted | ||
| 599 | 695 |
Matchcode ID &-& was not deleted | ||
| 600 | 696 |
Delete matchcode object & | ||
| 601 | 697 |
Matchcode object & was not deleted | ||
| 602 | 698 |
Matchcode object & deleted | ||
| 603 | 699 |
Not possible to enter function & for background | ||
| 604 | 700 |
Partial foreign key not allowed with customizing and help views | ||
| 605 | 701 |
Invalid foreign key dependency for help views | ||
| 606 | 702 |
Incorrect selection condition (& & & &) | ||
| 607 | 703 |
Base table & was included more than once | ||
| 608 | 704 |
No fields were defined for view $ | Space: object requires documentation | |
| 609 | 705 |
Key fields are not together at the beginning of the view | ||
| 610 | 706 |
& is not a view (aggregate type: &) | ||
| 611 | 707 |
Field name cannot be changed for view type P | ||
| 612 | 708 |
Selection conditions are ignored for projection views | ||
| 613 | 709 |
Base tables of type & not permitted for this view type | ||
| 614 | 710 |
Base tables of type & not permitted | ||
| 615 | 711 |
Field &-& of the selection conditions was not found | ||
| 616 | 712 |
Selection condition not permitted for client | ||
| 617 | 713 |
&-& is not a semantic foreign key | ||
| 618 | 714 |
Cardinality & of the foreign key &-& is not permitted here | ||
| 619 | 715 |
Foreign key &-& is partial | ||
| 620 | 716 |
Foreign key &-& contains a constant | ||
| 621 | 717 |
Foreign key &-& refers to a SYST-field | ||
| 622 | 718 |
Foreign key &-& (reference to external field) | ||
| 623 | 719 |
Foreign key &-& (transitive reference to external field) | ||
| 624 | 720 |
Selection program & was changed manually | ||
| 625 | 721 |
View field &-& (view type does not permit data elements to be changed) | ||
| 626 | 722 |
View field &-& (domains of the data elements not equal) | ||
| 627 | 723 |
View & could not be read | ||
| 628 | 724 |
Access error when reading view & | ||
| 629 | 725 |
Do not define a link for the last selection condition | ||
| 630 | 726 |
View must be created in the database | ||
| 631 | 727 |
View must be deleted in the database | ||
| 632 | 728 |
View must be deleted from the database and created again | ||
| 633 | 729 |
Key field &-& missing. Specify maintenance status 'read only'. | ||
| 634 | 730 |
Join from & to & not defined with foreign key | ||
| 635 | 731 |
Required field &-& is not a key field | ||
| 636 | 732 |
All fields are evaluated as key field | ||
| 637 | 733 |
Invalid foreign key dependency for lock objects | Space: object requires documentation | |
| 638 | 734 |
Selection condition & for field &-& not allowed | ||
| 639 | 735 |
The view ignores client-dependency of the base tables | Space: object requires documentation | |
| 640 | 736 |
Not all the base tables are linked with join conditions | Space: object requires documentation | |
| 641 | 737 |
Invalid type in join &-& = &-& | Space: object requires documentation | |
| 642 | 738 |
Activate view & | ||
| 643 | 739 |
Check view & | ||
| 644 | 740 |
View & was activated | ||
| 645 | 741 |
View & is consistent | ||
| 646 | 742 |
View & was not activated | ||
| 647 | 743 |
View & is not consistent | ||
| 648 | 744 |
You do not have authorization for the database modification | ||
| 649 | 745 |
The delivery classes of the view and the primary table do not agree | Space: object requires documentation | |
| 650 | 746 |
Field & is a language field. Check usage in key | Space: object requires documentation | |
| 651 | 747 |
View field &-& (type not consistent with base field) | ||
| 652 | 748 |
View field &-& (data element not adjusted to base field) | ||
| 653 | 749 |
Synonym for external view needs to be created | The short text describes the object sufficiently | |
| 654 | 750 |
Field &-& (type conflict in selection condition) | The short text describes the object sufficiently | |
| 655 | 751 |
Field &-& (selection condition for type & not allowed) | The short text describes the object sufficiently | |
| 656 | 752 |
Field &-&: Do not specify integer constants in quotation marks | The short text describes the object sufficiently | |
| 657 | 753 |
Field &-&: Selection condition not allowed for SY field | The short text describes the object sufficiently | |
| 658 | 754 |
Selection condition &-&: Apostrophes are added | Space: object requires documentation | |
| 659 | 755 |
Joins must be defined with foreign key | ||
| 660 | 756 |
Field &-& from join condition does not exist | ||
| 661 | 757 |
Selection/join from external field &-& | ||
| 662 | 758 |
Field &-& does not belong to a base table | Space: object requires documentation | |
| 663 | 759 |
Join for field &-& uses an SY field | ||
| 664 | 760 |
Field &-& for transparent implementation inserted | ||
| 665 | 761 |
View field &1 missing in union &2 | ||
| 666 | 762 |
View field & (data element or type/length different in union) | ||
| 667 | 763 |
Key field &1-&2 missing | ||
| 668 | 764 |
Type conflict in join &-& = &-& | ||
| 669 | 765 |
Field specification with * and - only allowed for DB views | ||
| 670 | 766 |
Key field & of primary table & missing | Space: object requires documentation | |
| 671 | 767 |
Specify at least one base table | Space: object requires documentation | |
| 672 | 768 |
Cannot expand or collapse line | Space: object requires documentation | |
| 673 | 769 |
Selection condition for &-& contains lowercase | Space: object requires documentation | |
| 674 | 770 |
Buffering only possible for database views | ||
| 675 | 771 |
Technical settings are deleted upon activation | ||
| 676 | 772 |
Not possible to update buffering flag for & | ||
| 677 | 773 |
Maximum number of buffered views for base table & exceeded | Space: object requires documentation | |
| 678 | 774 |
Link the selection conditions with AND or OR | Space: object requires documentation | |
| 679 | 775 |
Operator & is not allowed in a selection condition. | Space: object requires documentation | |
| 680 | 776 |
Append views are only allowed for database views and projection views | Space: object requires documentation | |
| 681 | 777 |
Field groups are only permitted for database and projection views | Space: object requires documentation | |
| 682 | 778 |
Field &: Position relative to Basis table cannot be exchanged | Space: object requires documentation | |
| 683 | 779 |
Feld &-&: Type conflict, length of comparison value & is too large | The short text describes the object sufficiently | |
| 684 | 780 |
Check to ensure ABAP Dictionary views consistent with database views | ||
| 685 | 781 |
View & is not consistent in the fields with database view | ||
| 686 | 782 |
Selection conditions for view & are not consistent with database view | ||
| 687 | 783 |
View Field &: Invalid type use (&) in union | The short text describes the object sufficiently | |
| 688 | 784 |
Base object & is neither a transparent table nor a view | The short text describes the object sufficiently | |
| 689 | 790 |
Rename statements generated using & | Space: object requires documentation | |
| 690 | 791 |
Could not generate rename statements using & | Space: object requires documentation | |
| 691 | 792 |
Generated create statements for view & | Space: object requires documentation | |
| 692 | 793 |
Could not generate create statements for view & | Space: object requires documentation | |
| 693 | 794 |
Generated statements for RENAME TABLE/CREATE VIEW & | Space: object requires documentation | |
| 694 | 795 |
Modeflaf 'V' noted in runtime object | Space: object requires documentation | |
| 695 | 796 |
Mode flag 'V' could not be set in runtime object | Space: object requires documentation | |
| 696 | 797 |
Alle dependent views of DB table & are deleted: | Space: object requires documentation | |
| 697 | 798 |
Table &: DROP statements could not be generated for all dependent views | Space: object requires documentation | |
| 698 | 800 |
************ Views Cheecks ************************* | Space: object requires documentation | |
| 699 | 801 |
View &-& can only be used in union & if a join with & exists | Space: object requires documentation | |
| 700 | 802 |
Union &: number of columns is not correct | The short text describes the object sufficiently | |
| 701 | 803 |
View field & in & Union select: Length of 1st occurrence must be larger | Space: object requires documentation | |
| 702 | 804 |
View field & in & Union select: Length of constant should be shortened | Space: object requires documentation | |
| 703 | 805 |
Selection condition for &-&: Type of right-hand side &-& does not match | Space: object requires documentation | |
| 704 | 806 |
Entity type & is not assigned to a view | Space: object requires documentation | |
| 705 | 807 |
View & and assignment to & were deleted logically. | Space: object requires documentation | |
| 706 | 808 |
Assignment of view & to entity type & had not yet been saved | Space: object requires documentation | |
| 707 | 809 |
Selection condition for &-&: quot. marks missing for comparison value & | The short text describes the object sufficiently | |
| 708 | 810 |
Selection condition for &-&: comparison value is missing | The short text describes the object sufficiently | |
| 709 | 811 |
Join condition for &-& contains lowercase letters | The short text describes the object sufficiently | |
| 710 | 812 |
Field &-&: Join condition for type & is not allowed | The short text describes the object sufficiently | |
| 711 | 813 |
Join condition &-&: Quotation marks will be added | The short text describes the object sufficiently | |
| 712 | 814 |
Join condition &-&: Quotation marks missing for comparison value | The short text describes the object sufficiently | |
| 713 | 815 |
Field &-&: Type conflict in join conidition | The short text describes the object sufficiently | |
| 714 | 816 |
Comparison value &: Specification as constant field name not possible | The short text describes the object sufficiently | |
| 715 | 817 |
Operator & is not allowed in a join condition | The short text describes the object sufficiently | |
| 716 | 827 |
Assignment deleted, but view & not deleted. Function modules exist | ||
| 717 | 841 |
There are several generalizations for view &: | Space: object requires documentation | |
| 718 | 842 |
No active generalization for view & | Space: object requires documentation | |
| 719 | 843 |
Settings transferred from view/table & | Space: object requires documentation | |
| 720 | 844 |
Table & is not a base table of & | Space: object requires documentation | |
| 721 | 845 |
Object is assigned to entity & in the data model | Space: object requires documentation | |
| 722 | 846 |
This entity has the following specializations: | Space: object requires documentation | |
| 723 | 850 |
Error in RDD25UDM (& & & &) | Space: object requires documentation | |
| 724 | 860 |
Inherited table & cannot be deleted. | Space: object requires documentation | |
| 725 | 861 |
Inherited condition cannot be deleted. | Space: object requires documentation | |
| 726 | 862 |
You cannot insert in front of an inherited condition. | Space: object requires documentation | |
| 727 | 863 |
You cannot paste in front of an inherited condition. | Space: object requires documentation | |
| 728 | 864 |
You cannot select an inherited condition. | Space: object requires documentation | |
| 729 | 880 |
INHERIT from gen. &, view & | Space: object requires documentation | |
| 730 | 881 |
Bequeath & to &, view & to & | Space: object requires documentation | |
| 731 | 882 |
View & is not active. | Space: object requires documentation | |
| 732 | 883 |
The primary table of & must occur in &. | The short text describes the object sufficiently | |
| 733 | 884 |
Name & for field &-& was replaced by &. | The short text describes the object sufficiently | |
| 734 | 885 |
Secondary table & is now the subsequent table of & instead of &. | The short text describes the object sufficiently | |
| 735 | 886 |
Prim.tab. & now follow-on table from & | The short text describes the object sufficiently | |
| 736 | 897 |
& | ||
| 737 | 898 |
& & | ||
| 738 | 899 |
& & & & | Space: object requires documentation | |
| 739 | 990 |
Log flag successfully initialized in DDNTT | ||
| 740 | 991 |
Initialization error with log flag in table DDNTT | ||
| 741 | 998 |
Matchcode upgrade with repository switch | ||
| 742 | 999 |
Conventional matchcode upgrade | Space: object requires documentation |
History
| Last changed on/by | |
20141121 | SAP |
| SAP Release Created in |
