Message Number list used by SAP ABAP Class CL_FDT_DATA_OBJECT (FDT: Abstract Data Object Class)
SAP ABAP Class
CL_FDT_DATA_OBJECT (FDT: Abstract Data Object Class) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | FDT_CHANGE_INFO - 217 | DDIC type was removed | ||
| 2 | FDT_CHANGE_INFO - 216 | DDIC type was set to &1 | ||
| 3 | FDT_CHANGE_INFO - 221 | GDT binding was changed from &1 to &2 | ||
| 4 | FDT_CHANGE_INFO - 220 | GDT binding was removed | ||
| 5 | FDT_CHANGE_INFO - 219 | GDT binding was done | ||
| 6 | FDT_CHANGE_INFO - 218 | DDIC type name was changed from &1 to &2 | ||
| 7 | FDT_CORE - 151 | ID of data object must be unique. ID &1 already exists in context | ||
| 8 | FDT_CORE - 283 | Name of data object must be unique. Name &1 already exists in context | ||
| 9 | FDT_CORE - 283 | Name of data object must be unique. Name &1 already exists in context | ||
| 10 | FDT_CORE - 373 | ID of data object must be unique in signature. ID &1 already exists in &2 | ||
| 11 | FDT_CORE - 374 | Invalid &1 data object (&2). No name is set | ||
| 12 | FDT_CORE - 374 | Invalid &1 data object (&2). No name is set | ||
| 13 | FDT_CORE - 376 | Multiple use of identical objects (&1 and &2) in context not allowed | ||
| 14 | FDT_CORE - 377 | Multi use of identic objects (&1 and &2) in ruleset variables not allowed | ||
| 15 | FDT_CORE - 378 | Multiple use of identical objects (&1 and &2) in &3/&4 not allowed | ||
| 16 | FDT_CORE - 379 | ID of data object must be unique in signature. &1 already exists in &2 | ||
| 17 | FDT_CORE - 382 | Nested object &2 has a lower access level (&1) than top object (&3) | ||
| 18 | FDT_CORE - 383 | Restricting the access level for a transported data object is not allowed | ||
| 19 | FDT_CORE - 384 | Setting access level to &1 is due to usage &2 (ID &3) not allowed | ||
| 20 | FDT_CORE - 400 | Invalid data object binding; data object is bound to more than one type | ||
| 21 | FDT_CORE - 411 | Not all entries needed to create the path are provided | ||
| 22 | FDT_CORE - 412 | Invalid sequence of nodes provided for creation of path | ||
| 23 | FDT_CORE - 413 | Invalid sequence of attributes provided for creation of path | ||
| 24 | FDT_CORE - 448 | Data dictionary (DDIC) type &1 is switched off by switch &2 (&3) | ||
| 25 | FDT_CORE - 449 | Data dictionary (DDIC) type &1 is controlled by switch &2 (&3) | ||
| 26 | FDT_CORE - 490 | Data objects that are part of a bound data structure cannot be renamed | ||
| 27 | FDT_CORE - 491 | Data objects that are part of a bound data structure cannot be unbound | ||
| 28 | FDT_CORE - 501 | Generation is not yet supported &1->&2 | ||
| 29 | FDT_CORE - 501 | Generation is not yet supported &1->&2 | ||
| 30 | FDT_CORE - 158 | Multiple use of object in context/result not allowed (&1 and &2) | ||
| 31 | FDT_CORE - 002 | Version &1 does not exist | ||
| 32 | FDT_CORE - 006 | No active version found for &1 with timestamp &2 | ||
| 33 | FDT_CORE - 021 | Type not supported; not element, structure or table type | ||
| 34 | FDT_CORE - 038 | Invalid method call | ||
| 35 | FDT_CORE - 038 | Invalid method call | ||
| 36 | FDT_CORE - 058 | Invalid data object or data object with wrong type (&1) | ||
| 37 | FDT_CORE - 066 | Type &1 not supported yet | ||
| 38 | FDT_CORE - 066 | Type &1 not supported yet | ||
| 39 | FDT_CORE - 066 | Type &1 not supported yet | ||
| 40 | FDT_CORE - 074 | Invalid context/result data object (&1); no name set | ||
| 41 | FDT_CORE - 074 | Invalid context/result data object (&1); no name set | ||
| 42 | FDT_CORE - 087 | Invalid node &1; ID does not exist or has the wrong object type | ||
| 43 | FDT_CORE - 087 | Invalid node &1; ID does not exist or has the wrong object type | ||
| 44 | FDT_CORE - 087 | Invalid node &1; ID does not exist or has the wrong object type | ||
| 45 | FDT_CORE - 087 | Invalid node &1; ID does not exist or has the wrong object type | ||
| 46 | FDT_CORE - 099 | Data object conversion not possible (&1 &2 to &3 &4 / data dependent) | ||
| 47 | FDT_CORE - 100 | Data object conversion not possible (&1 &2 to &3 &4 / general mismatch) | ||
| 48 | FDT_CORE - 130 | No active data dictionary (DDIC) type '&1' found | ||
| 49 | FDT_CORE - 136 | Invalid type name supplied | ||
| 50 | FDT_CORE - 151 | ID of data object must be unique. ID &1 already exists in context | ||
| 51 | FDT_CORE - 184 | ID &1 does not belong to application &2 | ||
| 52 | FDT_CORE2 - 006 | Provide exactly one of: exit class, text symbol or free text |