SBD_MESSAGES - Messages for source based DDIC
The following messages are stored in message class SBD_MESSAGES: Messages for source based DDIC.
It is part of development package SDDIC_ADT_SBD in software component BC-DWB-AIE-DIC. This development package consists of objects that can be grouped under "Resources and Registration for Source Based Dictionary".
It is part of development package SDDIC_ADT_SBD in software component BC-DWB-AIE-DIC. This development package consists of objects that can be grouped under "Resources and Registration for Source Based Dictionary".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Object name &1 differs from type &2 in source code |
| 002 | Token "&1" in line &2 does not match dictionary syntax rules |
| 003 | Mandatory annotation "&1" for structure &2 is missing |
| 004 | Annotation "&1" is redundant. First one wins on save |
| 005 | Annotation "&1" is not a valid annotation and will disappear on save |
| 006 | Invalid value "&1" assigned to annotation "&2" |
| 007 | Can't save due to errors in source; execute check for details |
| 008 | Structure name &1 is longer than 30 characters |
| 009 | Redundant annotations for field &1 exist |
| 010 | Object type &1 is not supported by the dictionary navigation service |
| 011 | Navigation not possible for the current cursor position |
| 012 | Cardinality &1 is invalid; valid values are "1","0..1","0..*","1..*" |
| 013 | Cardinality &1 is invalid; valid values at this position are "1","0..1" |
| 014 | The editor does not support certain elements of this object |
| 016 | Annotation &1 is invalid or does not allow the given value |
| 017 | Message Class and Message Number annotations must exist both or none |
| 018 | Internal error while executing code completion for "1" |
| 019 | Annotation Type "&1" is not supported |
| 020 | Description of field is too long; only 60 characters are allowed |
| 021 | Description of structure &1 is too long; only 60 characters are allowed |
| 023 | Enhancement category &1 of extended object &2 is incompatible |
| 024 | Compatible enhancement categories for &1 are: &2 &3 &4 |
| 025 | Extended object &1 prevents appending new fields in &2 |
| 026 | The attribute '&2' of the appended field &1 will not be used |
| 027 | Original language &1 differs from logon language &2 |
| 028 | Text from DDIC type is used instead. Annotation will disappear on save |
| 029 | Annotation &1 is useless in this context and will disappear on save |
| 030 | Value help parameter &1 is used multiple times; first one wins on save |
| 031 | Field &1 of checktable &2 is used multiple times; first one wins on save |
| 032 | Length addition for predefined ABAP types is limited to 6 digits |
| 033 | Decimals addition in predefined ABAP types is limited to 6 digits |
| 034 | Identifiers containing special characters must be written in "quotes" |
| 035 | Predefined ABAP type &1 does not exist |
| 037 | Annotation with reference to currency code for field &1 is missing |
| 038 | Annotation with reference to unit code for field &1 is missing |
| 039 | Use message for foreign key field &1 only with an enabled screen check |
| 040 | Referenced field &2 in &1 does not exist |
| 041 | Referenced field &2 in &1 is not typed correctly |
| 042 | Referenced field &2 in &1 does not exist or is not typed correctly |
| 043 | Type &1 does not exist or has no active version |
| 044 | Field name &1 is longer than 30 characters; it will be adjusted on save |
| 045 | Type &1 is a generated proxy type; use Proxy Editor for editing |
| 046 | syntax error use "define structure" to define structure &1 |
| 047 | syntax error use "define table" to define table &1 |
| 048 | Annotation with reference to currency code for field &1 is uncomplete |
| 049 | Annotation with reference to unit code for field &1 is uncomplete |
| 051 | Property &1 is not supported |
| 052 | Check Table is missing |
| 053 | Property &1 is not complete |
| 054 | Search Help is missing |
| 055 | Type &1 is not supported |
| 056 | Abap predefined type 'CUKY' is expected |
| 057 | Context &1 is invalid |
| 058 | Multiple object types are not supported |
| 059 | &1 is empty |
| 070 | -------Messages of Versioning--------------------------- |
| 071 | Version &1 of Structure &2 can not be read |
| 080 | -------Messages of Documentation--------------------------- |
| 081 | Documentation type &1 is not supported |
| 082 | Internal error when reading documentation status |
| 201 | &1 is still used and could not be deleted |
| 299 | -------Messages of Annotations--------------------------- |
| 300 | Enhancement Category |
| 301 | Can be enhanced in any way |
| 302 | Can be enhanced and character-like or numeric |
| 303 | Can be enhanced character-like |
| 304 | Cannot be enhanced |
| 305 | Unclassified |
| 310 | Delivery Class |
| 311 | Application table for master data and transaction data |
| 312 | Customer table for data entered only by the customer |
| 313 | Table used as a repository for temporary data |
| 314 | Customizing table, protected against SAP Update |
| 315 | Control table, SAP and customer have separate key areas |
| 316 | System table, maint. only by SAP, change = modification |
| 317 | System table, contents transportable by separate TR objects |
| 320 | Display and Maintenance |
| 321 | Display/maintenance allowed |
| 322 | Display/maintenance not allowed |
| 323 | Display/maintenance allowed with restrictions |
| 324 | Display only |
| 330 | Table Category |
| 331 | Transparent Database Table |
| 334 | Global Temporary Table |
| 340 | Activation Type |
| 341 | Can be activated directly from the ABAP Dictionary |
| 342 | The runtime object must be generated using a C program |
| 343 | Must be adjusted manually in the C program when the table is changed |
| 344 | Required before R3TRANS runs |
| 350 | Short Description |
| 362 | Primary key as INVERTED HASH |
| 363 | Foreign Key Short Description |
| 364 | Foreign Key Type |
| 365 | Input Value Check on Dynpro |
| 366 | Message Class |
| 367 | Message Number |
| 368 | Currency Field |
| 369 | Unit Field |
| 370 | Key fields/key candidates |
| 371 | No key fields/key candidates |
| 372 | Key fields of a text table |
| 373 | Replacement Object |
| 374 | Spatial Reference System Identifier |
| 380 | Output Style for Decfloat Types |
| 381 | Normal Output Style |
| 382 | Sign right Output Style |
| 383 | Scale-preserving Output Style |
| 384 | Scientific Output Style |
| 385 | Scientific with leading zero Output Style |
| 386 | Scale-preserving scientific Output Style |
| 387 | Engineering Output Style |
| 390 | Anonymization Indicator for User Field |
| 391 | Annotation @AbapCatalog.anonymizedWhenDelivered missing for field &1 |
| 392 | Annotation @AbapCatalog.anonymizedWhenDelivered missing in structrue &1 |
| 393 | Adjustment of table &1 was aborted |
| 394 | Adjustment of table &1 is running |
| 395 | Indicator for a Language Field |
| 396 | Table still contains data |
| 397 | Field Suffix |
| 398 | Quota Maximum Fields |
| 399 | Quota Maximum Bytes |
| 400 | Quota Share Partner |
| 401 | Quota Share Customer |
| 402 | Field Suffix &1 is too long; only 3 characters are allowed |
| 403 | &1 should be a numeric value with the length &2 |
| 404 | Annotation "&1" is empty and will disappear on save |