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