Message Number list used by SAP ABAP Class CL_FDT_ELEMENT (FDT: Data Object Element)
SAP ABAP Class CL_FDT_ELEMENT (FDT: Data Object Element) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_CHANGE_INFO - 214 Conversion to uppercase has been activated
2 Message Number  FDT_CHANGE_INFO - 213 Conversion to uppercase has been deactivated
3 Message Number  FDT_CHANGE_INFO - 771 Binding to NUMC field has been deactivated
4 Message Number  FDT_CHANGE_INFO - 770 Binding to NUMC field has been activated
5 Message Number  FDT_CHANGE_INFO - 259 Timepoint type was changed from &1 to a generic type
6 Message Number  FDT_CHANGE_INFO - 258 Timepoint type was changed from a generic type to &1
7 Message Number  FDT_CHANGE_INFO - 245 Element inherits change of referenced object
8 Message Number  FDT_CHANGE_INFO - 244 Value for the allowed constants were changed
9 Message Number  FDT_CHANGE_INFO - 243 &1 constants were removed in allowed constants for element
10 Message Number  FDT_CHANGE_INFO - 242 &1 new constants were included in the allowed constants for element
11 Message Number  FDT_CHANGE_INFO - 241 Timepoint type was changed from &1 to &2
12 Message Number  FDT_CHANGE_INFO - 240 Restriction for only positive value was removed
13 Message Number  FDT_CHANGE_INFO - 239 Restriction for only positive value was imposed
14 Message Number  FDT_CHANGE_INFO - 238 Decimals restriction of the element was changed from &1 to &2
15 Message Number  FDT_CHANGE_INFO - 237 Length restriction of the element was changed from &1 to &2
16 Message Number  FDT_CHANGE_INFO - 236 Compounding was changed from &1 to &2
17 Message Number  FDT_CHANGE_INFO - 234 Compound ID was set to &1
18 Message Number  FDT_CHANGE_INFO - 235 Compound ID was removed
19 Message Number  FDT_CHANGE_INFO - 215 Element was created of type &1
20 Message Number  FDT_CHANGE_INFO - 222 Element type was changed from &1 to &2
21 Message Number  FDT_CHANGE_INFO - 223 Reference for the element was set to &1
22 Message Number  FDT_CHANGE_INFO - 224 Referencing element was removed
23 Message Number  FDT_CHANGE_INFO - 225 Referencing element was changed from &1 to &2
24 Message Number  FDT_CHANGE_INFO - 226 Allowed comparisons were changed from &1 to &2
25 Message Number  FDT_CHANGE_INFO - 228 Inclusion sign was set to "Not Allowed"
26 Message Number  FDT_CHANGE_INFO - 229 Exclusion sign was set to "Allowed"
27 Message Number  FDT_CHANGE_INFO - 230 Exclusion sign was set to "Not Allowed"
28 Message Number  FDT_CHANGE_INFO - 231 Usage of multiple options was set to "Allowed"
29 Message Number  FDT_CHANGE_INFO - 232 Usage of multiple options was set to "Not Allowed"
30 Message Number  FDT_CHANGE_INFO - 233 Option string was changed from &1 to &2
31 Message Number  FDT_CHANGE_INFO - 227 Inclusion sign was set to "Allowed"
32 Message Number  FDT_CORE - 356 Timepoint type &1 is only allowed in AP systems
33 Message Number  FDT_CORE - 105 Missing options and signs for user-defined comparisons
34 Message Number  FDT_CORE - 355 For boolean elements, only simple comparison operations are supported
35 Message Number  FDT_CORE - 302 No &1 supplied for &2
36 Message Number  FDT_CORE - 297 "Convert to uppercase" property is set but &1 in &2 uses lower case
37 Message Number  FDT_CORE - 288 Number of decimals was reduced to &1 compared to &2 in DDIC
38 Message Number  FDT_CORE - 287 Length was reduced to &1 compared to &2 in DDIC
39 Message Number  FDT_CORE - 285 Dimension-property must not be set for element type &1
40 Message Number  FDT_CORE - 275 Number of decimals (&1) does not fit into length (&2)
41 Message Number  FDT_CORE - 274 Invalid value '&1' for parameter &2
42 Message Number  FDT_CORE - 273 Length-property must not be set for element type &1
43 Message Number  FDT_CORE - 272 Number of decimals must not be set for element type &1
44 Message Number  FDT_CORE - 271 "Only positive numbers"-property must not be set for element type &1
45 Message Number  FDT_CORE - 270 Timepoint type must not be set for element type &1
46 Message Number  FDT_CORE - 357 Timepoint type has been changed from '&1' (active version) to '&2'
47 Message Number  FDT_CORE - 358 Element type has been changed from '&1' (active version) to '&2'
48 Message Number  FDT_CORE - 359 Quantity dimension has been changed from '&1' (active version) to '&2'
49 Message Number  FDT_CORE - 362 Timepoint type &1 does not fit to date element &2
50 Message Number  FDT_CORE - 387 Domain values are language dependent (see value table &1 in DDIC)
51 Message Number  FDT_CORE - 388 Domain values may not be unique (see value table &1 in DDIC)
52 Message Number  FDT_CORE - 389 Text &1 is not convertible into a boolean.
53 Message Number  FDT_CORE - 390 Invalid recursion: &1 holds a reference to itself
54 Message Number  FDT_CORE - 398 Data type of Data Dictionary (DDIC) type '&1' does not match
55 Message Number  FDT_CORE - 399 &1 is not a valid message severity
56 Message Number  FDT_CORE - 400 Invalid data object binding; data object is bound to more than one type
57 Message Number  FDT_CORE - 435 "Convert to uppercase" property is set but &1 is not of type text
58 Message Number  FDT_CORE - 479 No timepoint type is specified
59 Message Number  FDT_CORE - 520 Data element cannot be moved into a table
60 Message Number  FDT_CORE - 167 Element is not bound to a DDIC element
61 Message Number  FDT_CORE - 002 Version &1 does not exist
62 Message Number  FDT_CORE - 006 No active version found for &1 with timestamp &2
63 Message Number  FDT_CORE - 039 Neither data type nor reference defined
64 Message Number  FDT_CORE - 040 &1 is not a constant
65 Message Number  FDT_CORE - 041 No valid elementary type set for &1
66 Message Number  FDT_CORE - 041 No valid elementary type set for &1
67 Message Number  FDT_CORE - 046 Type of constant &1 is not suitable
68 Message Number  FDT_CORE - 047 Reference to a data object type that is not elementary
69 Message Number  FDT_CORE - 048 Binding to &1 not possible; &1 is already bound to &2; see long text
70 Message Number  FDT_CORE - 049 Complex comparisons combined with unique identifiers may cause problems
71 Message Number  FDT_CORE - 051 Object ID &1 is invalid
72 Message Number  FDT_CORE - 051 Object ID &1 is invalid
73 Message Number  FDT_CORE - 101 System error during conversion of data objects (&1)
74 Message Number  FDT_CORE - 104 No valid comparison settings
75 Message Number  FDT_CORE - 168 Domain value &1 has a different result data object
76 Message Number  FDT_CORE - 166 Maximum number of decimal places is 10
77 Message Number  FDT_CORE - 164 Invalid Timepoint-Type &1
78 Message Number  FDT_CORE - 162 &1 is exceeding the maximum length of 31 (including decimals)
79 Message Number  FDT_CORE - 161 Maximum length of 255 is exceeded
80 Message Number  FDT_CORE - 131 &1 is not a data dictionary (DDIC) element type
81 Message Number  FDT_CORE - 131 &1 is not a data dictionary (DDIC) element type
82 Message Number  FDT_CORE - 130 No active data dictionary (DDIC) type '&1' found
83 Message Number  FDT_CORE - 116 Allowed comparison type &1 does not fit signs, options, or multiple
84 Message Number  FDT_CORE - 109 Invalid sign &1
85 Message Number  FDT_CORE - 108 Invalid option &1
86 Message Number  FDT_CORE - 102 System error not found during conversion of data objects (&1)
87 Message Number  FDT_CORE2 - 006 Provide exactly one of: exit class, text symbol or free text
88 Message Number  FDT_CORE2 - 032 Invalid value (&1) for IS_NUMC setting specified
89 Message Number  FDT_EXPRESSIONS - 677 Quantity unit for field &1 is different from the reference field &2
90 Message Number  FDT_EXPRESSIONS - 678 Currency key for field &1 is different from the reference field &2
91 Message Number  FDT_SERVICE - 000 Exception Raised In Custom Application Exit (Further Information Follows)
92 Message Number  FDT_SERVICE - 000 Exception Raised In Custom Application Exit (Further Information Follows)
93 Message Number  FDT_SERVICE - 356 Dimension &1 does not exist