Message Number list used by SAP ABAP Class CL_FDT_EXPRESSION_TYPE (FDT: Expression Type)
SAP ABAP Class CL_FDT_EXPRESSION_TYPE (FDT: Expression Type) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_CORE - 251 Local object cannot be transported: No transport object should be set
2 Message Number  FDT_CORE - 239 Number of tables on the transport objects for C and &1 tables differ
3 Message Number  FDT_CORE - 240 Table names listed in transport object &1 should end with the letter &2
4 Message Number  FDT_CORE - 241 The &1-table &2 misses its C-table equivalent &3
5 Message Number  FDT_CORE - 243 Metadata for table &1 could not be retrieved. See following messages
6 Message Number  FDT_CORE - 244 The structure of &1 and its C equivalent &2 differ
7 Message Number  FDT_CORE - 245 The C table &1 must be client-dependent
8 Message Number  FDT_CORE - 246 The &1 table &2 must be client-independent
9 Message Number  FDT_CORE - 247 Tables &1 and &2 must either both contain an ID keyfield or both not
10 Message Number  FDT_CORE - 248 Tables &1 and &2 must either both contain an version keyfield or both not
11 Message Number  FDT_CORE - 002 Version &1 does not exist
12 Message Number  FDT_CORE - 252 Customizing expression type should not set S-table (transport) object
13 Message Number  FDT_CORE - 260 Transport object '&1' only allowed for application '&2'
14 Message Number  FDT_CORE - 267 Table &1 is not ID dependent.
15 Message Number  FDT_CORE - 268 Table &1 is not version dependent.
16 Message Number  FDT_CORE - 277 Class &1 does not have the mandatory direct or indirect superclass &2
17 Message Number  FDT_CORE - 302 No &1 supplied for &2
18 Message Number  FDT_CORE - 307 No transport request for &1 supplied
19 Message Number  FDT_CORE - 336 Invalid method settings for &1; see long text
20 Message Number  FDT_CORE - 414 Table &1 has a key field of type string
21 Message Number  FDT_CORE - 237 Transport object settings cannot be changed incompatibly (&1/&2)
22 Message Number  FDT_CORE - 000 Unknown ID &1
23 Message Number  FDT_CORE - 006 No active version found for &1 with timestamp &2
24 Message Number  FDT_CORE - 029 A class and an interface must be defined
25 Message Number  FDT_CORE - 031 Unnamed expression type is not supported
26 Message Number  FDT_CORE - 036 Class / interface cannot be changed, active version exists
27 Message Number  FDT_CORE - 077 Action type properties cannot be changed; active version exists
28 Message Number  FDT_CORE - 115 Class/interface (ABAP-OO) not supplied
29 Message Number  FDT_CORE - 147 No valid class, &1 does not exist or does not implement interface &2
30 Message Number  FDT_CORE - 148 No valid interface, &1 does not exist
31 Message Number  FDT_CORE - 149 It is strongly recommended to nest interfaces
32 Message Number  FDT_CORE - 150 No valid interface &1
33 Message Number  FDT_CORE - 230 Transport is not supported for table type A (master data)
34 Message Number  FDT_CORE - 231 Invalid table type &1
35 Message Number  FDT_CORE - 232 No transport object for system tables supplied
36 Message Number  FDT_CORE - 233 No transport object for customizing tables supplied
37 Message Number  FDT_CORE - 234 Transport object '&1' for type &2 does not exist
38 Message Number  FDT_CORE - 235 Transport object &1; invalid object type &2 (T needed)
39 Message Number  FDT_CORE - 236 Problematic header settings for &1; compare to &2 with transaction SOBJ
40 Message Number  FDT_CORE - 238 Table &1 from &2 is also listed on a different transport object
41 Message Number  FDT_EXPRESSIONS - 303 Customer &1 has missing SCPRSTRANSP table entries; Transport it again