Message Number list used by SAP ABAP Class CL_FDT_FUNCTION (FDT: Function)
SAP ABAP Class
CL_FDT_FUNCTION (FDT: Function) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | FDT_CHANGE_INFO - 262 | New data object(s) removed from function context: &1 | ||
| 2 | FDT_CHANGE_INFO - 261 | New data object(s) added to function context: &1 | ||
| 3 | FDT_CHANGE_INFO - 403 | A new function was created | ||
| 4 | FDT_CHANGE_INFO - 277 | Function mode was changed from &1 to &2 | ||
| 5 | FDT_CHANGE_INFO - 275 | Filter was changed from &1 to &2 | ||
| 6 | FDT_CHANGE_INFO - 274 | Filter was removed from function | ||
| 7 | FDT_CHANGE_INFO - 273 | Filter &1 was set | ||
| 8 | FDT_CHANGE_INFO - 272 | Expression was changed from &1 to &2 | ||
| 9 | FDT_CHANGE_INFO - 271 | Expression was removed from the function | ||
| 10 | FDT_CHANGE_INFO - 269 | Context class was changed from &1 to &2 | ||
| 11 | FDT_CHANGE_INFO - 270 | Expression &1 was set | ||
| 12 | FDT_CHANGE_INFO - 263 | Existing data object(s) were updated in the function context | ||
| 13 | FDT_CHANGE_INFO - 264 | Result &1 was set | ||
| 14 | FDT_CHANGE_INFO - 265 | Result was removed from the function | ||
| 15 | FDT_CHANGE_INFO - 266 | Result was changed from &1 to &2 | ||
| 16 | FDT_CHANGE_INFO - 267 | Context class &1 was set for the function | ||
| 17 | FDT_CHANGE_INFO - 268 | Context class assignment was removed | ||
| 18 | FDT_CORE - 095 | Invalid application ID &1 | ||
| 19 | FDT_CORE - 097 | Function name &1 already used in application within SAP dev. landscape | ||
| 20 | FDT_CORE - 098 | Invalid ID &1; ID is deleted logically | ||
| 21 | FDT_CORE - 103 | Settings context classes is obsolete and must not be used anymore | ||
| 22 | FDT_CORE - 106 | Unnamed functions are not supported | ||
| 23 | FDT_CORE - 124 | An invalid object &1 is used: Object is marked for deletion | ||
| 24 | FDT_CORE - 154 | Possible data conversion conflict; &1 to &2 | ||
| 25 | FDT_CORE - 155 | Data conversion conflict; &1 to &2 | ||
| 26 | FDT_CORE - 156 | Assigned expression &1 does not have a result | ||
| 27 | FDT_CORE - 157 | Assigned expression uses &1 which is not in the context | ||
| 28 | FDT_CORE - 219 | Invalid dynamic call to method &1 | ||
| 29 | FDT_CORE - 219 | Invalid dynamic call to method &1 | ||
| 30 | FDT_CORE - 253 | Supplied trace mode contradicts supplied trace instance | ||
| 31 | FDT_CORE - 302 | No &1 supplied for &2 | ||
| 32 | FDT_CORE - 308 | &1 empty for &2 | ||
| 33 | FDT_CORE - 477 | &1 is currently inactive; see long text | ||
| 34 | FDT_CORE - 512 | Processing in generation mode is currently not possible | ||
| 35 | FDT_CORE - 873 | No ruleset registered on the function | ||
| 36 | FDT_CORE - 075 | Two or more context data objects with the same name are not allowed | ||
| 37 | FDT_CORE - 000 | Unknown ID &1 | ||
| 38 | FDT_CORE - 002 | Version &1 does not exist | ||
| 39 | FDT_CORE - 006 | No active version found for &1 with timestamp &2 | ||
| 40 | FDT_CORE - 023 | Class / interface (ABAP-OO) &1 does not exist | ||
| 41 | FDT_CORE - 032 | Class CL_FDT_CONTEXT cannot be used as the application's context class | ||
| 42 | FDT_CORE - 065 | Name &1 has already been used | ||
| 43 | FDT_CORE - 071 | Data object compounded to &1 is invalid | ||
| 44 | FDT_CORE - 074 | Invalid context/result data object (&1); no name set | ||
| 45 | FDT_CORE - 090 | Invalid context class &1 | ||
| 46 | FDT_CORE - 076 | Class/interface (ABAP-OO) &1 does not implement interface &2 | ||
| 47 | FDT_CORE - 078 | Trace mode &1 not supported | ||
| 48 | FDT_CORE - 079 | No expression set | ||
| 49 | FDT_CORE - 080 | No result data object set | ||
| 50 | FDT_CORE - 081 | Unknown function mode | ||
| 51 | FDT_CORE - 082 | Event mode with expression set; expression will not be processed | ||
| 52 | FDT_CORE - 084 | Data object &1 compounded to &2 is not in context | ||
| 53 | FDT_CORE - 090 | Invalid context class &1 |