AXT_COMMON - Extensibility common messages
The following messages are stored in message class AXT_COMMON: Extensibility common messages.
It is part of development package AXT_COMMON in software component CA-GTF-EEW. This development package consists of objects that can be grouped under "Common Extensibility objects".
It is part of development package AXT_COMMON in software component CA-GTF-EEW. This development package consists of objects that can be grouped under "Common Extensibility objects".
Message Nr ▲ | Message Text |
---|---|
000 | *****001 - 049: Service class check ************************** |
001 | Table &1 does not exist |
002 | Size category &1 is invalid |
003 | Object reference type &1 is invalid |
004 | Domain &1 not found |
005 | Delivery class &1 is invalid |
006 | Element status &1 is invalid |
007 | Package &1 does not exist |
008 | Transport request/task &1 not found |
009 | Data type &1 is invalid |
010 | Data element &1 not found |
011 | Category of dictionary type &1 is invalid |
012 | Buffering type &1 is invalid |
013 | Buffering status &1 is invalid |
014 | System settings for logical system &1 could not be read |
015 | Logical system could not be determined |
016 | Dropdown list box &1 does not exist |
017 | Dropdown list box &1 is not compatible |
018 | Domain &1 is inactive |
019 | Data element &1 is inactive |
020 | Check table &1 does not exist |
021 | Check table &1 is not compatible |
022 | Transport request/task &1 has been released |
023 | Object &1 cannot be created with package &2 |
024 | Object key definition is inconsistent |
025 | Structure &1 does not exist |
026 | Package &1 is not changeable |
027 | Package &1 and object &2 have different consolidation targets ('&3'/'&4') |
030 | &1&2&3&4 |
031 | Enhancement category &1 is invalid |
032 | &1&2&3 |
042 | Search help &1 does not exist |
043 | Search help parameter &1 does not exist in search help &2 |
044 | Search help &1 is not compatible |
050 | Namespace & not editable in this system |
051 | Namespace is required in customer systems |
052 | In SAP systems a transportable enhancement requires a /*/ namespace |
058 | Program: &1 Include: &2 Line: &3 |
059 | Dynpro popup was raised during generation; see note 1346123 |
060 | Unknown dynpro popup (&3 &4) was raised during generation of &1 &2 |
061 | Transport request dynpro was raised during generation of &1 &2 |
062 | Internal API might have become inconsistent; a restart is recommended |
063 | You cannot edit the repository object (&1 &2) |
064 | You are not registered as a developer |
065 | Confirmation dynpro was raised to update BDoc &1 to the latest version |
066 | A package selection popup has been opened |
100 | *****100 - 139: Name determination *********** |
101 | Counter overflow for number range &1 |
102 | Object type &1 is unknown |
103 | Number range &1 is unknown |
104 | Field &1 is not specified |
140 | *****140 - 199: Data type checks *********** |
141 | Specify a field subtype |
142 | &1 is not a valid field subtype |
143 | Navigation object &1 is inconsistent |
144 | Navigation object &1 is not compatible with the data type |
145 | Images can only be calculated; specify a rule |
146 | Cannot convert &1 to the requested data type; &1 might be too long |
147 | Cannot convert &1 to the requested data type; &1 is negative |
148 | You cannot combine &1 with &2; choose a compatible value |
149 | Specify a check table |
150 | Type &1 is designed for &2; it might be rendered incorrectly in other UIs |
151 | Field type is not supported; choose a different one |
152 | Text area field &1 (&2) is rendered as an input field in table views |
153 | Text area is not supported; field &1 (&2) appears only in table views |
200 | *Table extensibility |
201 | Metadata inconsistent for table &1 |
202 | Table &1 has no field &2 |
203 | Table &1 has no valid update function |
204 | Component &1 not found for table &2 |
205 | Component &1 not found for structure &2 |
206 | Error when accessing text elements in the ABAP Dictionary |
300 | *****300-399 for AET in general***** |
301 | Creation of AET Field is not supported |