Message Number list used by SAP ABAP Class CL_FDT_MAINTENANCE (FDT: Abstract Maintenance Class)
SAP ABAP Class CL_FDT_MAINTENANCE (FDT: Abstract Maintenance Class) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_CHANGE_INFO - 012 Name was changed from &1 to &2
2 Message Number  FDT_CHANGE_INFO - 011 Application was changed from &1 to &2
3 Message Number  FDT_CHANGE_INFO - 561 Value for custom attribute &1 has been removed.
4 Message Number  FDT_CHANGE_INFO - 560 Value for custom attribute &1 has been added: '&2'
5 Message Number  FDT_CHANGE_INFO - 021 The object was made version independent
6 Message Number  FDT_CHANGE_INFO - 020 The object was made version dependent
7 Message Number  FDT_CHANGE_INFO - 019 Document exit class was changed &1 to &2
8 Message Number  FDT_CHANGE_INFO - 018 Text exit class was changed from &1 to &2
9 Message Number  FDT_CHANGE_INFO - 017 Documentation was changed
10 Message Number  FDT_CHANGE_INFO - 016 Document dependency type was changed from &1 to &2
11 Message Number  FDT_CHANGE_INFO - 015 Texts were changed
12 Message Number  FDT_CHANGE_INFO - 014 Text dependency type was changed from &1 to &2
13 Message Number  FDT_CHANGE_INFO - 013 Access level was changed from &1 to &2
14 Message Number  FDT_CORE - 390 Invalid recursion: &1 holds a reference to itself
15 Message Number  FDT_CORE - 704 The transport request is initial
16 Message Number  FDT_CORE - 704 The transport request is initial
17 Message Number  FDT_CORE - 703 The &1 does not exist; deep save has to be aborted
18 Message Number  FDT_CORE - 702 &1 must not use &2 of virtual system '&3'
19 Message Number  FDT_CORE - 718 Transport request &1 cannot be used because change recording is disabled
20 Message Number  FDT_CORE - 701 There is no active version of &1 in the database yet
21 Message Number  FDT_CORE - 700 &1 (ID &2) has not been saved to the database yet
22 Message Number  FDT_CORE - 603 Object is marked as obsolete; attribute changes cannot be saved
23 Message Number  FDT_CORE - 602 Object is marked for deletion; attribute changes cannot be saved
24 Message Number  FDT_CORE - 550 Object is used in client &1; check manually for potential problems
25 Message Number  FDT_CORE - 394 Invalid recursion: &1 uses &2 uses &3 uses &4 uses ... uses &1
26 Message Number  FDT_CORE - 393 Invalid recursion: &1 uses &2 uses &3 uses &4 uses &1
27 Message Number  FDT_CORE - 392 Invalid recursion: &1 uses &2 uses &3 uses &1
28 Message Number  FDT_CORE - 391 Invalid recursion: &1 uses &2 uses &1
29 Message Number  FDT_CORE - 210 &1 is still used
30 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
31 Message Number  FDT_CORE - 890 ID &1 is unknown or is not of type Application
32 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
33 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
34 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
35 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
36 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
37 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
38 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
39 Message Number  FDT_CORE - 730 Object &1 is not enqueued; inactive version cannot be deleted
40 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
41 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
42 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
43 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
44 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
45 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
46 Message Number  FDT_CORE - 850 Operation &1 is not allowed during LUW Mode
47 Message Number  FDT_CORE - 089 &1 with top component &2 cannot use &3 with top component &4
48 Message Number  FDT_CORE - 125 An invalid object &1 is used: Object is obsolete
49 Message Number  FDT_CORE - 124 An invalid object &1 is used: Object is marked for deletion
50 Message Number  FDT_CORE - 110 Activation error for &1; see following messages for details
51 Message Number  FDT_CORE - 107 Invalid usage of unnamed &1 that belongs to &2
52 Message Number  FDT_CORE - 098 Invalid ID &1; ID is deleted logically
53 Message Number  FDT_CORE - 094 Usage of &1 is not allowed because of access level "application"
54 Message Number  FDT_CORE - 093 No application component set for &1
55 Message Number  FDT_CORE - 092 &1 with superord. component &2 cannot use &3 with superord. component &4
56 Message Number  FDT_CORE - 350 Enqueue failed on &1, object locked by &2
57 Message Number  FDT_CORE - 088 Invalid usage; &1 objects must not be used by &2 objects
58 Message Number  FDT_CORE - 088 Invalid usage; &1 objects must not be used by &2 objects
59 Message Number  FDT_CORE - 087 Invalid node &1; ID does not exist or has the wrong object type
60 Message Number  FDT_CORE - 067 Activation not successful; veto by exit defined in application &1
61 Message Number  FDT_CORE - 060 Invalid method call, invalid combination of input parameters
62 Message Number  FDT_CORE - 007 No application set
63 Message Number  FDT_CORE - 000 Unknown ID &1
64 Message Number  FDT_CORE - 152 Application TMP is a special BRFplus application and cannot be deleted
65 Message Number  FDT_CORE - 350 Enqueue failed on &1, object locked by &2
66 Message Number  FDT_CORE - 302 No &1 supplied for &2
67 Message Number  FDT_CORE - 280 Error in exit of application &1 for custom object check
68 Message Number  FDT_CORE - 264 No check for accessibility due to missing application for object &1
69 Message Number  FDT_CORE - 256 &1 with application component &2 cannot use &3 with appl. component &4
70 Message Number  FDT_CORE - 209 &1 cannot be deleted; object is still used
71 Message Number  FDT_CORE - 208 Object &1 not undeleted as its application &2 (&3) is in deleted state
72 Message Number  FDT_CORE - 207 Object &1 not undeleted; undelete used object &2 first
73 Message Number  FDT_CORE - 206 Object &1 cannot be undeleted; used object &2 already lost
74 Message Number  FDT_CORE - 205 Object &1 cannot be undeleted; its state is: Not deleted
75 Message Number  FDT_CORE - 203 Object &1 is not logically deleted; physical deletion not possible
76 Message Number  FDT_CORE - 192 Local objects must not be transported
77 Message Number  FDT_CORE - 170 Cross version in combination with timestamp makes no sense
78 Message Number  FDT_CORE - 153 App TMP is a special BRFplus application and cannot be set to obsolete
79 Message Number  FDT_CORE - 141 Use of local object &1 is not allowed
80 Message Number  FDT_CORE2 - 000 &1 is unnamed and not used by any object
81 Message Number  FDT_CORE2 - 001 &1 is unnamed and is used by more than one object