Message Number list used by SAP ABAP Class CL_FDT_APPLICATION (FDT: Application)
SAP ABAP Class
CL_FDT_APPLICATION (FDT: Application) is using
| # | Object Type | Object Name | Object Description | Note |
|---|---|---|---|---|
| 1 | FDT_CHANGE_INFO - 023 | Default for document dependency type was changed from &1 to &2 | ||
| 2 | FDT_CHANGE_INFO - 024 | Default for text dependency type was changed from &1 to &2 | ||
| 3 | FDT_CHANGE_INFO - 201 | Application component was set to &1 | ||
| 4 | FDT_CHANGE_INFO - 202 | Application component was removed | ||
| 5 | FDT_CHANGE_INFO - 203 | Application component was changed from &1 to &2 | ||
| 6 | FDT_CHANGE_INFO - 204 | Software component was set to &1 | ||
| 7 | FDT_CHANGE_INFO - 205 | Software component was removed | ||
| 8 | FDT_CHANGE_INFO - 206 | Software component was changed from &1 to &2 | ||
| 9 | FDT_CHANGE_INFO - 207 | Settings class was set to &1 | ||
| 10 | FDT_CHANGE_INFO - 208 | Settings class was removed | ||
| 11 | FDT_CHANGE_INFO - 209 | Settings class was changed from &1 to &2 | ||
| 12 | FDT_CHANGE_INFO - 210 | Development package was set to &1 | ||
| 13 | FDT_CHANGE_INFO - 211 | Development package was removed | ||
| 14 | FDT_CHANGE_INFO - 212 | Development package was changed from &1 to &2 | ||
| 15 | FDT_CHANGE_INFO - 407 | A new application was created in software component &1 | ||
| 16 | FDT_CHANGE_INFO - 563 | Custom attribute &1 has been added at posittion &2 | ||
| 17 | FDT_CHANGE_INFO - 564 | Custom attribute &1 has been removed | ||
| 18 | FDT_CHANGE_INFO - 565 | The usage type of custom attribute &1 has been changed from &2 to &3 | ||
| 19 | FDT_CHANGE_INFO - 566 | The position of custom attribute &1 has been changed from &2 to &3 | ||
| 20 | FDT_CHANGE_INFO - 577 | Versioning Mode was set to &1 | ||
| 21 | FDT_CHANGE_INFO - 578 | Versioning Mode was removed | ||
| 22 | FDT_CHANGE_INFO - 579 | Versioning Mode was changed from &1 to &2 | ||
| 23 | FDT_CHANGE_INFO - 580 | Log Object was set to &1 | ||
| 24 | FDT_CHANGE_INFO - 581 | Log Object was removed | ||
| 25 | FDT_CHANGE_INFO - 582 | Log Object was changed from &1 to &2 | ||
| 26 | FDT_CHANGE_INFO - 583 | Log Sub-Object was set to &1 | ||
| 27 | FDT_CHANGE_INFO - 584 | Log Sub-Object was removed | ||
| 28 | FDT_CHANGE_INFO - 585 | Log Sub-Object was changed from &1 to &2 | ||
| 29 | FDT_CHANGE_INFO - 586 | Log Persistence was set | ||
| 30 | FDT_CHANGE_INFO - 587 | Log Persistence was removed | ||
| 31 | FDT_CHANGE_INFO - 588 | Log Constraint was set to &1 | ||
| 32 | FDT_CHANGE_INFO - 589 | Log Constraint was removed | ||
| 33 | FDT_CHANGE_INFO - 590 | Log Constraint was changed from &1 to &2 | ||
| 34 | FDT_CHANGE_INFO - 659 | Restarts of rulesets were enabled for the application | ||
| 35 | FDT_CHANGE_INFO - 660 | Restarts of rulesets were disabled for the application | ||
| 36 | FDT_CHANGE_INFO - 664 | External identification was set to hidden for the application | ||
| 37 | FDT_CHANGE_INFO - 665 | External identification was set to visible for the application | ||
| 38 | FDT_CHANGE_INFO - 666 | Allowed message types were changed | ||
| 39 | FDT_CHANGE_INFO - 667 | Default currency was changed from &1 to &2 | ||
| 40 | FDT_CHANGE_INFO - 668 | Message severity for default currency was changed from &1 to &2 | ||
| 41 | FDT_CHANGE_INFO - 669 | Database connection was changed from &1 to &2 | ||
| 42 | FDT_CHANGE_INFO - 683 | Numeric comparison for NUMC bindings was set to true | ||
| 43 | FDT_CHANGE_INFO - 684 | Numeric comparison for NUMC bindings was set to false | ||
| 44 | FDT_CORE - 000 | Unknown ID &1 | ||
| 45 | FDT_CORE - 000 | Unknown ID &1 | ||
| 46 | FDT_CORE - 002 | Version &1 does not exist | ||
| 47 | FDT_CORE - 006 | No active version found for &1 with timestamp &2 | ||
| 48 | FDT_CORE - 008 | No application component supplied | ||
| 49 | FDT_CORE - 009 | No software component supplied | ||
| 50 | FDT_CORE - 014 | No objects found for this application | ||
| 51 | FDT_CORE - 017 | &1 Application not possible; object already saved as &2 | ||
| 52 | FDT_CORE - 017 | &1 Application not possible; object already saved as &2 | ||
| 53 | FDT_CORE - 017 | &1 Application not possible; object already saved as &2 | ||
| 54 | FDT_CORE - 018 | &1 Application not possible; other objects use this object already | ||
| 55 | FDT_CORE - 018 | &1 Application not possible; other objects use this object already | ||
| 56 | FDT_CORE - 018 | &1 Application not possible; other objects use this object already | ||
| 57 | FDT_CORE - 019 | Invalid application ID &1 | ||
| 58 | FDT_CORE - 019 | Invalid application ID &1 | ||
| 59 | FDT_CORE - 020 | ID &1 is initial, unknown, or it does not have the correct object type | ||
| 60 | FDT_CORE - 023 | Class / interface (ABAP-OO) &1 does not exist | ||
| 61 | FDT_CORE - 024 | Application component &1 does not exist | ||
| 62 | FDT_CORE - 025 | Software component &1 does not exist | ||
| 63 | FDT_CORE - 026 | Name changed for a transported application. | ||
| 64 | FDT_CORE - 038 | Invalid method call | ||
| 65 | FDT_CORE - 064 | Application name &1 already used in comp &2 within SAP dev. landscape | ||
| 66 | FDT_CORE - 064 | Application name &1 already used in comp &2 within SAP dev. landscape | ||
| 67 | FDT_CORE - 065 | Name &1 has already been used | ||
| 68 | FDT_CORE - 073 | Software component &1 cannot be changed in system &2 | ||
| 69 | FDT_CORE - 076 | Class/interface (ABAP-OO) &1 does not implement interface &2 | ||
| 70 | FDT_CORE - 121 | Unnamed application is not supported | ||
| 71 | FDT_CORE - 137 | Processing started for &1 | ||
| 72 | FDT_CORE - 144 | Log constraint 'mandatory' defined but no log object provided | ||
| 73 | FDT_CORE - 146 | Invalid log constraint value &1 | ||
| 74 | FDT_CORE - 184 | ID &1 does not belong to application &2 | ||
| 75 | FDT_CORE - 185 | Local applications can only be assigned to a local package | ||
| 76 | FDT_CORE - 186 | Software component of package &1 has changed from &2 to &3 | ||
| 77 | FDT_CORE - 187 | Application component of package &1 has changed from &2 to &3 | ||
| 78 | FDT_CORE - 193 | Development package is missing | ||
| 79 | FDT_CORE - 194 | Development package &1 cannot be changed | ||
| 80 | FDT_CORE - 195 | Development package &1 is invalid | ||
| 81 | FDT_CORE - 195 | Development package &1 is invalid | ||
| 82 | FDT_CORE - 197 | Local packages can only be assigned to local applications | ||
| 83 | FDT_CORE - 199 | Software component LOCAL can only be used for local applications | ||
| 84 | FDT_CORE - 211 | Development package &1 is a main package or a structure package | ||
| 85 | FDT_CORE - 212 | Invalid or no namespace in application name: &1 | ||
| 86 | FDT_CORE - 213 | Invalid versioning mode &1 | ||
| 87 | FDT_CORE - 226 | Name TMP is a reserved name; cannot be used to create new applications | ||
| 88 | FDT_CORE - 255 | Applications at SAP must not be created in customer namespace | ||
| 89 | FDT_CORE - 259 | Reverting of local appl. not possible because it is a masterdata object | ||
| 90 | FDT_CORE - 261 | Report FDT_TABDIRDEVC_UPDATE needs to be executed for application &1 | ||
| 91 | FDT_CORE - 269 | Invalid value "&1" for field ruleset restart. | ||
| 92 | FDT_CORE - 279 | The current restart option defined at the application is needed for &1 | ||
| 93 | FDT_CORE - 281 | Default settings: Version dependent texts require versioned objects | ||
| 94 | FDT_CORE - 282 | Default settings: Version dependent docum. requires versioned objects | ||
| 95 | FDT_CORE - 289 | Customer applications should be created in customer namespace | ||
| 96 | FDT_CORE - 302 | No &1 supplied for &2 | ||
| 97 | FDT_CORE - 360 | Software Component has been adapted to &1 for package &2 | ||
| 98 | FDT_CORE - 361 | Application Component has been adapted to &1 for package &2 | ||
| 99 | FDT_CORE - 363 | Message log action &1 has deviating log settings | ||
| 100 | FDT_CORE - 364 | At least one message type has to be allowed | ||
| 101 | FDT_CORE - 365 | Invalid message type defined | ||
| 102 | FDT_CORE - 366 | Invalid number of denied message types | ||
| 103 | FDT_CORE - 367 | Ruleset restart option cannot be disabled since ruleset &1 uses it | ||
| 104 | FDT_CORE - 385 | Versioning mode "transport" is not allowed for local applications | ||
| 105 | FDT_CORE - 399 | &1 is not a valid message severity | ||
| 106 | FDT_CORE - 410 | Connection &1 does not refer to a SAP HANA DB - see transaction DBCO | ||
| 107 | FDT_CORE - 422 | No inactive objects found for this application | ||
| 108 | FDT_CORE - 475 | Object &1 is not versioned | ||
| 109 | FDT_CORE - 476 | Versioning is set to mandatory, but the following objects are unversioned | ||
| 110 | FDT_CORE - 531 | Application &1 cannot be assigned to another application | ||
| 111 | FDT_CORE - 731 | Object &1 cannot be enqueued; inactive version cannot be deleted | ||
| 112 | FDT_CORE - 783 | Error encountered while registering application in GTABKEY | ||
| 113 | FDT_CORE - 832 | Result size &1 exceeds maximum result size &2 | ||
| 114 | FDT_CORE - 832 | Result size &1 exceeds maximum result size &2 | ||
| 115 | FDT_CORE - 832 | Result size &1 exceeds maximum result size &2 | ||
| 116 | FDT_CORE - 832 | Result size &1 exceeds maximum result size &2 | ||
| 117 | FDT_CORE2 - 020 | Maximum number of custom attributes (&1) exceeded: &2 | ||
| 118 | FDT_CORE2 - 021 | Invalid object set for custom attribute at position &1: '&2' (&3) | ||
| 119 | FDT_CORE2 - 023 | No value specified for mandatory custom attribute '&1' | ||
| 120 | FDT_CORE2 - 030 | Invalid value (&1) for NUMC numeric comparison setting specified | ||
| 121 | FDT_DSM - 025 | Add-on SAP NetWeaver Decision Service Management is not installed | ||
| 122 | FDT_DSM - 079 | Service '&1' is not active in managed system &2 | ||
| 123 | FDT_EXPRESSIONS - 010 | Invalid currency &1; see long text | ||
| 124 | FDT_HANA - 010 | Could not establish database connection &1 - see transaction DBCO | ||
| 125 | FDT_HANA - 022 | Assign DB connection 'DEFAULT' or secondary DB connection to application | ||
| 126 | FDT_HANA - 024 | &2 '&3' is inconsistent with database connection &1: |