Message Number list used by SAP ABAP Class CL_FDT_CATALOG (FDT: Catalog)
SAP ABAP Class CL_FDT_CATALOG (FDT: Catalog) is using
# Object Type Object Name Object Description Note
     
1 Message Number  FDT_CHANGE_INFO - 411 A new node &1 was created at position &2
2 Message Number  FDT_CHANGE_INFO - 410 The node &1 was deleted from catalog at position &2
3 Message Number  FDT_CHANGE_INFO - 421 There was a creation of a new catalog
4 Message Number  FDT_CHANGE_INFO - 420 The object at node &1 was changed from &2 to &3
5 Message Number  FDT_CHANGE_INFO - 419 An object was set at the node &1
6 Message Number  FDT_CHANGE_INFO - 418 The object was removed from the node &1
7 Message Number  FDT_CHANGE_INFO - 417 The link of the node &1 was changed
8 Message Number  FDT_CHANGE_INFO - 416 The parent of the node &1 was changed from &2 to &3
9 Message Number  FDT_CHANGE_INFO - 415 Node &1 was changed
10 Message Number  FDT_CHANGE_INFO - 414 Exit class of node &1 was changed from &2 to &3
11 Message Number  FDT_CHANGE_INFO - 413 Node name of node at position &1 was changed from &2 to &3
12 Message Number  FDT_CHANGE_INFO - 412 Node type of the node &1 was changed from &2 to &3
13 Message Number  FDT_CORE - 753 Invalid method call; either link or leaf properties can be set
14 Message Number  FDT_CORE - 771 Node ID &1: Either enable node text binding or provide node texts
15 Message Number  FDT_CORE - 754 Node ID &1 (&2) has children(stuct.node);no leaf/link attributes possible
16 Message Number  FDT_CORE - 755 &1 is not a catalog
17 Message Number  FDT_CORE - 756 Unknown sibling &1
18 Message Number  FDT_CORE - 758 Sibling &1 does not belong to parent &2
19 Message Number  FDT_CORE - 759 Value &2 set for invalid attribute &1 (not part of attribute list)
20 Message Number  FDT_CORE - 761 Node ID &1 (&2) cannot be moved underneath itself (recursion)
21 Message Number  FDT_CORE - 762 Node ID &1 is a node of type structure and has no name
22 Message Number  FDT_CORE - 763 Attribute of element type &1 is currently not supported
23 Message Number  FDT_CORE - 764 Node UUID &1 is unknown; link is invalid
24 Message Number  FDT_CORE - 765 Node ID &1 (&2) needs to be of type Leaf
25 Message Number  FDT_CORE - 766 Node ID &1 (&2) needs to be of type Object
26 Message Number  FDT_CORE - 768 &3: node UUID &1 does not belong to node ID &2 (&4)
27 Message Number  FDT_CORE - 770 Node ID &1 is of type structure; text binding is not possible
28 Message Number  FDT_CORE - 752 Object type &1 is not supported
29 Message Number  FDT_CORE - 751 Invalid attribute &1; must be an elementary data object
30 Message Number  FDT_CORE - 750 Unknown node ID &1
31 Message Number  FDT_CORE - 750 Unknown node ID &1
32 Message Number  FDT_CORE - 750 Unknown node ID &1
33 Message Number  FDT_CORE - 746 Versioned catalogs can lead to high storage requirements
34 Message Number  FDT_CORE - 302 No &1 supplied for &2
35 Message Number  FDT_CORE - 222 Messages from node &1 with node ID &2
36 Message Number  FDT_CORE - 220 Invalid dynamic call to class &1
37 Message Number  FDT_CORE - 219 Invalid dynamic call to method &1
38 Message Number  FDT_CORE - 218 Object type &1 of &2 is not in the list of allowed object types
39 Message Number  FDT_CORE - 171 Object with ID &1 not persisted yet
40 Message Number  FDT_CORE - 087 Invalid node &1; ID does not exist or has the wrong object type
41 Message Number  FDT_CORE - 006 No active version found for &1 with timestamp &2
42 Message Number  FDT_CORE - 002 Version &1 does not exist