Message Number list used by SAP ABAP Class CL_AXT_TABLE_DEF (Active and inactive data for table extension)
SAP ABAP Class CL_AXT_TABLE_DEF (Active and inactive data for table extension) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | AXT_MODEL - 206 | 1:1 child table cannot have unmapped key fields (for example, &1) | |
2 | Message Number | AXT_MODEL - 185 | Key fields cannot be disabled | |
3 | Message Number | AXT_MODEL - 189 | Table ID &1 is already used by enhancement &2 | |
4 | Message Number | AXT_MODEL - 190 | Table uses namespace &1 but enhancement has namespace &2 | |
5 | Message Number | AXT_MODEL - 191 | Table &1 is not a database table or database view | |
6 | Message Number | AXT_MODEL - 202 | Existing table &1 cannot be a child of the new table &2 | |
7 | Message Number | AXT_MODEL - 203 | Parent key &1 can only be mapped once in table &2 | |
8 | Message Number | AXT_MODEL - 204 | Field &1 in table &2 is not compatible with parent key &3 | |
9 | Message Number | AXT_MODEL - 205 | Parent key field &1 is not mapped to a field in child table &2 | |
10 | Message Number | AXT_MODEL - 180 | Table &1 does not exist | |
11 | Message Number | AXT_MODEL - 214 | 1:N table (&1) requires an unmapped key field | |
12 | Message Number | AXT_MODEL - 219 | For the table, specify at least one field that is not calculated | |
13 | Message Number | AXT_MODEL - 226 | Only tables with a cardinality of 1:N can be table extensible | |
14 | Message Number | AXT_MODEL - 227 | Maximum DB size exceeded; remove fields or reduce their length | |
15 | Message Number | AXT_MODEL - 230 | Check table &2 is not supported for field &1 | |
16 | Message Number | AXT_MODEL - 231 | Search help &2 is not supported for field &1 | |
17 | Message Number | AXT_MODEL - 276 | Remaining table space is not enough to support field enhancements | |
18 | Message Number | AXT_MODEL - 277 | Reserved field quota has been exceeded | |
19 | Message Number | AXT_MODEL - 150 | Table already contains a field with ID &1 | |
20 | Message Number | AXT_MODEL - 115 | Logical key of an active enhancement cannot be changed | |
21 | Message Number | AXT_MODEL - 115 | Logical key of an active enhancement cannot be changed | |
22 | Message Number | AXT_MODEL - 116 | Changing the database table name would cause data loss | |
23 | Message Number | AXT_MODEL - 119 | All key fields have to be at the beginning of the table | |
24 | Message Number | AXT_MODEL - 127 | 'Enhanceable' checkbox can no longer be disabled | |
25 | Message Number | AXT_MODEL - 139 | View &1 is read-only | |
26 | Message Number | AXT_MODEL - 148 | Field &1 is set as navigation link but the field is disabled | |
27 | Message Number | AXT_MODEL - 150 | Table already contains a field with ID &1 | |
28 | Message Number | AXT_MODEL - 113 | You cannot change the reporting type to &1 | |
29 | Message Number | AXT_MODEL - 152 | Specify at least one field for table &1 | |
30 | Message Number | AXT_MODEL - 153 | Use namespace (&1) for table name &2 | |
31 | Message Number | AXT_MODEL - 159 | Select the first table field as logical key | |
32 | Message Number | AXT_MODEL - 160 | Checkbox &1 has also been selected for logical key field &2 | |
33 | Message Number | AXT_MODEL - 161 | Enhancing the search result list is only possible for 1:1 enhancements | |
34 | Message Number | AXT_MODEL - 173 | Enter a description | |
35 | Message Number | AXT_MODEL - 174 | Enter a description for language &1 |