FDT_CORE - Formula & Derivation Tool: Core
The following messages are stored in message class FDT_CORE: Formula & Derivation Tool: Core.
It is part of development package SFDT_CORE in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Core".
It is part of development package SFDT_CORE in software component BC-SRV-BR. This development package consists of objects that can be grouped under "BRFplus: Core".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Unknown ID &1 |
| 001 | &1 &2 &3 &4 |
| 002 | Version &1 does not exist |
| 003 | Name &1 does not begin with a letter or a slash |
| 004 | Name &1 contains a forbidden character |
| 005 | Name TABLE_LINE is not allowed for data objects (reserved word) |
| 006 | No active version found for &1 with timestamp &2 |
| 007 | No application set |
| 008 | No application component supplied |
| 009 | No software component supplied |
| 010 | Data cannot be saved; missing lock |
| 011 | &1 is an unknown access level |
| 012 | Unnamed objects cannot have an access level other than APPLICATION |
| 013 | Illegal instance creation; object type &1 instead of object type &2 |
| 014 | No objects found for this application |
| 015 | &1 does not exist |
| 016 | Version &1 is not a valid version |
| 017 | &1 Application not possible; object already saved as &2 |
| 018 | &1 Application not possible; other objects use this object already |
| 019 | Invalid application ID &1 |
| 020 | ID &1 is initial, unknown, or it does not have the correct object type |
| 021 | Type not supported; not element, structure or table type |
| 022 | User &1 is unknown |
| 023 | Class / interface (ABAP-OO) &1 does not exist |
| 024 | Application component &1 does not exist |
| 025 | Software component &1 does not exist |
| 026 | Name changed for a transported application. |
| 027 | Invalid data object type &2 for object &1, actual data object type is &3 |
| 028 | Invalid expression type &2 for object &1, actual expression type is &3 |
| 029 | A class and an interface must be defined |
| 030 | Error occurred during the processing of &1 |
| 031 | Unnamed expression type is not supported |
| 032 | Class CL_FDT_CONTEXT cannot be used as the application's context class |
| 033 | No data object type supplied |
| 034 | No expression type supplied |
| 035 | Expression type &1 cannot be used to create expressions, no class defined |
| 036 | Class / interface cannot be changed, active version exists |
| 037 | Invalid method call, no flat table supplied |
| 038 | Invalid method call |
| 039 | Neither data type nor reference defined |
| 040 | &1 is not a constant |
| 041 | No valid elementary type set for &1 |
| 042 | No elementary objects set for &1 |
| 043 | Two elementary objects with field name &2 in &1 |
| 044 | Component without name in &1 |
| 045 | No valid line type set for &1 |
| 046 | Type of constant &1 is not suitable |
| 047 | Reference to a data object type that is not elementary |
| 048 | Binding to &1 not possible; &1 is already bound to &2; see long text |
| 049 | Complex comparisons combined with unique identifiers may cause problems |
| 050 | Filter type &1 is invalid |
| 051 | Object ID &1 is invalid |
| 052 | Object type &1 is not supported |
| 053 | Only EQUAL comparisons allowed as col. &1 is compounded to col. &2 |
| 054 | Invalid method call, no elementary input supplied |
| 055 | Invalid method call, no structured input supplied |
| 056 | No elementary objects set |
| 057 | Invalid structure definition |
| 058 | Invalid data object or data object with wrong type (&1) |
| 059 | Invalid table definition |
| 060 | Invalid method call, invalid combination of input parameters |
| 061 | Software component &1 does not have a software release |
| 062 | Error occurred when calling GTABKEY service (registration) |
| 063 | Error occurred when calling GTABKEY service (de-registration) |
| 064 | Application name &1 already used in comp &2 within SAP dev. landscape |
| 065 | Name &1 has already been used |
| 066 | Type &1 not supported yet |
| 067 | Activation not successful; veto by exit defined in application &1 |
| 068 | '//' is not a permitted sequence of characters in a name (name was &1) |
| 069 | &1 is not a valid language key |
| 070 | &1 is the current filter (circular reference) |
| 071 | Data object compounded to &1 is invalid |
| 072 | Incompatible change of type or timepoint type (usages do exist) |
| 073 | Software component &1 cannot be changed in system &2 |
| 074 | Invalid context/result data object (&1); no name set |
| 075 | Two or more context data objects with the same name are not allowed |
| 076 | Class/interface (ABAP-OO) &1 does not implement interface &2 |
| 077 | Action type properties cannot be changed; active version exists |
| 078 | Trace mode &1 not supported |
| 079 | No expression set |
| 080 | No result data object set |
| 081 | Unknown function mode |
| 082 | Event mode with expression set; expression will not be processed |
| 083 | Application is already locked in transport request &1 |
| 084 | Data object &1 compounded to &2 is not in context |
| 085 | &1 is not in the context |
| 086 | No expression type set |
| 087 | Invalid node &1; ID does not exist or has the wrong object type |
| 088 | Invalid usage; &1 objects must not be used by &2 objects |
| 089 | &1 with top component &2 cannot use &3 with top component &4 |
| 090 | Invalid context class &1 |
| 091 | Supplied UUID is not a "true" UUID (&1) |
| 092 | &1 with superord. component &2 cannot use &3 with superord. component &4 |
| 093 | No application component set for &1 |
| 094 | Usage of &1 is not allowed because of access level "application" |
| 095 | Invalid application ID &1 |
| 096 | Invalid application; object is &1 but new application &2 is &3 |
| 097 | Function name &1 already used in application within SAP dev. landscape |
| 098 | Invalid ID &1; ID is deleted logically |
| 099 | Data object conversion not possible (&1 &2 to &3 &4 / data dependent) |
| 100 | Data object conversion not possible (&1 &2 to &3 &4 / general mismatch) |
| 101 | System error during conversion of data objects (&1) |
| 102 | System error not found during conversion of data objects (&1) |
| 103 | Settings context classes is obsolete and must not be used anymore |
| 104 | No valid comparison settings |
| 105 | Missing options and signs for user-defined comparisons |
| 106 | Unnamed functions are not supported |
| 107 | Invalid usage of unnamed &1 that belongs to &2 |
| 108 | Invalid option &1 |
| 109 | Invalid sign &1 |
| 110 | Activation error for &1; see following messages for details |
| 111 | &1 does not have an active version |
| 112 | &1 does not exist in database |
| 113 | Expression type &1 was not transported yet |
| 114 | Time stamp &1 does not meet the objects' time consistency constraints |
| 115 | Class/interface (ABAP-OO) not supplied |
| 116 | Allowed comparison type &1 does not fit signs, options, or multiple |
| 117 | &1&2&3&4 |
| 118 | Error while getting the code list provider &1 |
| 119 | General problem in enterprise service framework (ESF) |
| 120 | Current scope option &1 must not be different from existing locks (&2) |
| 121 | Unnamed application is not supported |
| 122 | Name &1 belongs to unchangeable namespace |
| 123 | The retention time has to be 0 if all objects shall be logically deleted |
| 124 | An invalid object &1 is used: Object is marked for deletion |
| 125 | An invalid object &1 is used: Object is obsolete |
| 126 | Error occurred while trying to retrieve values from the Business Object |
| 127 | No objects found for this selection |
| 128 | &1 applications have been selected for processing |
| 129 | &1 objects have been selected for processing |
| 130 | No active data dictionary (DDIC) type '&1' found |
| 131 | &1 is not a data dictionary (DDIC) element type |
| 132 | &1 is not a data dictionary (DDIC) structure type |
| 133 | &1 is not a data dictionary (DDIC) table type |
| 134 | Type of value for &1 may not be a structure |
| 135 | Value table &1 for domain &2 in data dictionary (DDIC) does not exist |
| 136 | Invalid type name supplied |
| 137 | Processing started for &1 |
| 138 | Activation veto by exit in application &1 is suppressed during import |
| 139 | &1 objects found without access level value "application" |
| 140 | Usage of application &1 that is obsolete or marked to be deleted |
| 141 | Use of local object &1 is not allowed |
| 142 | Unknown text/documentation dependency type &1 |
| 143 | Version-dependent text/documentation is not allowed for shipped objects |
| 144 | Log constraint 'mandatory' defined but no log object provided |
| 145 | Initial exit classname supplied |
| 146 | Invalid log constraint value &1 |
| 147 | No valid class, &1 does not exist or does not implement interface &2 |
| 148 | No valid interface, &1 does not exist |
| 149 | It is strongly recommended to nest interfaces |
| 150 | No valid interface &1 |
| 151 | ID of data object must be unique. ID &1 already exists in context |
| 152 | Application TMP is a special BRFplus application and cannot be deleted |
| 153 | App TMP is a special BRFplus application and cannot be set to obsolete |
| 154 | Possible data conversion conflict; &1 to &2 |
| 155 | Data conversion conflict; &1 to &2 |
| 156 | Assigned expression &1 does not have a result |
| 157 | Assigned expression uses &1 which is not in the context |
| 158 | Multiple use of object in context/result not allowed (&1 and &2) |
| 159 | Expression types need to be assigned to system applications |
| 160 | Value exceeds maximum length &1 |
| 161 | Maximum length of 255 is exceeded |
| 162 | &1 is exceeding the maximum length of 31 (including decimals) |
| 163 | Number of decimal places is bigger than the length of the number |
| 164 | Invalid Timepoint-Type &1 |
| 165 | Element type of &1 does not support additional type attributes |
| 166 | Maximum number of decimal places is 10 |
| 167 | Element is not bound to a DDIC element |
| 168 | Domain value &1 has a different result data object |
| 169 | Invalid number &1; only positive numbers allowed |
| 170 | Cross version in combination with timestamp makes no sense |
| 171 | Object with ID &1 not persisted yet |
| 172 | Application name '&1' is not registered |
| 173 | Function name '&1' is not registered for application '&2' |
| 174 | Development package for application '&1' cannot be determined |
| 175 | You have no authorization to create object &1 |
| 176 | You have no authorization to display object &1 |
| 177 | You have no authorization to change object &1 |
| 178 | You have no authorization to delete object &1 |
| 179 | You have no authorization to activate object &1 |
| 180 | You have no authorization for this action |
| 181 | For the timestamp filter, only values EQ, LE, and GE are allowed |
| 182 | Deployable applications cannot be copied in current runtime mode |
| 183 | Copy of a customizing application cannot be created in BCF client |
| 184 | ID &1 does not belong to application &2 |
| 185 | Local applications can only be assigned to a local package |
| 186 | Software component of package &1 has changed from &2 to &3 |
| 187 | Application component of package &1 has changed from &2 to &3 |
| 188 | Invalid application; &1 is a local object |
| 189 | Invalid application; &1 is not a local object |
| 190 | Local application not possible; object already saved as non-local |
| 191 | Local application not possible; other objects use this object already |
| 192 | Local objects must not be transported |
| 193 | Development package is missing |
| 194 | Development package &1 cannot be changed |
| 195 | Development package &1 is invalid |
| 196 | Invalid system settings, T-table mode is only supported in AP systems |
| 197 | Local packages can only be assigned to local applications |
| 198 | Transport of objects with local package/software comp is not allowed |
| 199 | Software component LOCAL can only be used for local applications |
| 200 | --- BEGIN MESSAGES OF WHERE-USED CHECK AND DELETE ------------ |
| 201 | &1 is still used and cannot be deleted; see messages that follow |
| 202 | &1 cannot be locked for changes because it is deleted |
| 203 | Object &1 is not logically deleted; physical deletion not possible |
| 204 | &1 (application: &2) uses &3 (application: &4) |
| 205 | Object &1 cannot be undeleted; its state is: Not deleted |
| 206 | Object &1 cannot be undeleted; used object &2 already lost |
| 207 | Object &1 not undeleted; undelete used object &2 first |
| 208 | Object &1 not undeleted as its application &2 (&3) is in deleted state |
| 209 | &1 cannot be deleted; object is still used |
| 210 | &1 is still used |
| 211 | Development package &1 is a main package or a structure package |
| 212 | Invalid or no namespace in application name: &1 |
| 213 | Invalid versioning mode &1 |
| 214 | &1 is not versioned; text or documentation must not be version-dependent |
| 215 | Invalid name: '&1' |
| 216 | Invalid name (&1); use namespace correctly "/.../..." |
| 217 | Version &1 is discarded completely by timestamp &2 |
| 218 | Object type &1 of &2 is not in the list of allowed object types |
| 219 | Invalid dynamic call to method &1 |
| 220 | Invalid dynamic call to class &1 |
| 221 | Invalid Range for Random generation |
| 222 | Messages from node &1 with node ID &2 |
| 223 | Only supply one of structure, table or element per position (position &1) |
| 224 | Recursive definitions are not supported (position &1) |
| 225 | Structure &1 not supported; no component has a supported type |
| 226 | Name TMP is a reserved name; cannot be used to create new applications |
| 227 | &1 is (part of) a table in the context; cannot be accessed directly |
| 228 | No tables exists for this NODE_ID or the NODE_ID is invalid |
| 229 | The NODE_ID does not exist |
| 230 | Transport is not supported for table type A (master data) |
| 231 | Invalid table type &1 |
| 232 | No transport object for system tables supplied |
| 233 | No transport object for customizing tables supplied |
| 234 | Transport object '&1' for type &2 does not exist |
| 235 | Transport object &1; invalid object type &2 (T needed) |
| 236 | Problematic header settings for &1; compare to &2 with transaction SOBJ |
| 237 | Transport object settings cannot be changed incompatibly (&1/&2) |
| 238 | Table &1 from &2 is also listed on a different transport object |
| 239 | Number of tables on the transport objects for C and &1 tables differ |
| 240 | Table names listed in transport object &1 should end with the letter &2 |
| 241 | The &1-table &2 misses its C-table equivalent &3 |
| 242 | Only Table type S (system) is supported for expression types. |
| 243 | Metadata for table &1 could not be retrieved. See following messages |
| 244 | The structure of &1 and its C equivalent &2 differ |
| 245 | The C table &1 must be client-dependent |
| 246 | The &1 table &2 must be client-independent |
| 247 | Tables &1 and &2 must either both contain an ID keyfield or both not |
| 248 | Tables &1 and &2 must either both contain an version keyfield or both not |
| 249 | The C table name &1 must end with a number |
| 250 | Access level SAP is not supported any more. Use GLOBAL instead. |
| 251 | Local object cannot be transported: No transport object should be set |
| 252 | Customizing expression type should not set S-table (transport) object |
| 253 | Supplied trace mode contradicts supplied trace instance |
| 254 | &1 nests an unnamed data object |
| 255 | Applications at SAP must not be created in customer namespace |
| 256 | &1 with application component &2 cannot use &3 with appl. component &4 |
| 257 | Reverting local appl. not possible; object already saved as non-local |
| 258 | Reverting local appl. not possible; other objects use this object already |
| 259 | Reverting of local appl. not possible because it is a masterdata object |
| 260 | Transport object '&1' only allowed for application '&2' |
| 261 | Report FDT_TABDIRDEVC_UPDATE needs to be executed for application &1 |
| 262 | Application &1 does not exist |
| 263 | Application &1 has syntax errors or is not active |
| 264 | No check for accessibility due to missing application for object &1 |
| 265 | Data exchange between Business ByDesign and other systems not supported |
| 266 | &1 not changeable applications have been excluded from processing |
| 267 | Table &1 is not ID dependent. |
| 268 | Table &1 is not version dependent. |
| 269 | Invalid value "&1" for field ruleset restart. |
| 270 | Timepoint type must not be set for element type &1 |
| 271 | "Only positive numbers"-property must not be set for element type &1 |
| 272 | Number of decimals must not be set for element type &1 |
| 273 | Length-property must not be set for element type &1 |
| 274 | Invalid value '&1' for parameter &2 |
| 275 | Number of decimals (&1) does not fit into length (&2) |
| 276 | Data cannot be moved into table due to duplicate keys |
| 277 | Class &1 does not have the mandatory direct or indirect superclass &2 |
| 278 | The expression type of expression &1 has syntax errors |
| 279 | The current restart option defined at the application is needed for &1 |
| 280 | Error in exit of application &1 for custom object check |
| 281 | Default settings: Version dependent texts require versioned objects |
| 282 | Default settings: Version dependent docum. requires versioned objects |
| 283 | Name of data object must be unique. Name &1 already exists in context |
| 284 | No class could be determined for object |
| 285 | Dimension-property must not be set for element type &1 |
| 286 | Provide XML file. |
| 287 | Length was reduced to &1 compared to &2 in DDIC |
| 288 | Number of decimals was reduced to &1 compared to &2 in DDIC |
| 289 | Customer applications should be created in customer namespace |
| 290 | The interrupt once saved can not be saved again into the batch table |
| 291 | No interrupt record found in the batch table for interrupt id &1 |
| 292 | Can not delete the unsaved interrupt |
| 293 | Table &1 has no valid structure |
| 294 | Problem during the deletion of unnamed unused object &1; see log files |
| 295 | Data object type &1 is not supported |
| 296 | &2 is already locked on &3; transport request &1 cannot be used |
| 297 | "Convert to uppercase" property is set but &1 in &2 uses lower case |
| 298 | Import conflict; object &1 was previously deleted |
| 299 | Provide either an XML string or an XML DOM object |
| 300 | Invalid XML |
| 301 | Invalid document or root element; root element must be &1 |
| 302 | No &1 supplied for &2 |
| 303 | The object with ID &1 occurs multiple times in the XML document |
| 304 | Import conflict; object &1 already exists with a different object type |
| 305 | Creation of object instance failed for &1 |
| 306 | Problem in the import of &1 ID &2 |
| 307 | No transport request for &1 supplied |
| 308 | &1 empty for &2 |
| 309 | Error in file &1 |
| 310 | Problem with import of ID &1; ID unknown |
| 311 | Object &1 cannot be imported; it is marked for deletion |
| 312 | Error when translating to external type |
| 313 | Error when translating to internal type |
| 314 | Error when adding internal DTD |
| 315 | Error when calling transformation for XML validation |
| 316 | &1 node cannot be empty |
| 317 | &1 node cannot be empty for &2 |
| 318 | Errors in the XML import |
| 319 | Error occurred while looking for user-defined expression &1 |
| 320 | Call to class &1 is illegal |
| 321 | XML version &1 does not support direct value in expressions |
| 322 | XML version &1 not supported; import XML version &2 from source system |
| 323 | Trace hierarchy could not be created for the supplied information |
| 324 | XML has been exported successfully with transport request ID &1 |
| 325 | XML has been imported successfully with transport request ID &1 |
| 326 | XML transformation not supported |
| 327 | XML version &1 not supported |
| 328 | Application &1 already exists and is not a local object |
| 329 | XML import contains more than one application |
| 330 | XML import type local copy not allowed for local objects |
| 331 | Missing authorization for application &1 |
| 332 | &1 applications with missing authorizations have been excluded |
| 333 | Supply any one of the optional parameters |
| 334 | No active version found for &1 ; time stamp &2 |
| 335 | Supply one of the optional parameters |
| 336 | Invalid method settings for &1; see long text |
| 337 | Object &1 cannot be imported; problem in deleting object physically |
| 338 | Enhancement Category of object &1 not supported in XML Version &2 |
| 339 | Buffer is initial |
| 340 | Import canceled due to deletion status of object &1 |
| 341 | &1 expression is not supported in lower XML versions |
| 342 | &1 is not supported in lower XML versions |
| 343 | Application &1 has syntax errors or is not active |
| 344 | Object(s) in XML file is consistent |
| 345 | Object(s) with errors found; erroneous objects not imported |
| 346 | Object(s) in XML file is inconsistent |
| 347 | Application &1 is not changeable in this system |
| 348 | Enqueue failed on object with ID &1 |
| 349 | Errors when saving &1 |
| 350 | Enqueue failed on &1, object locked by &2 |
| 351 | Invalid object ID &1 |
| 352 | Enqueue failed - objects locked by user &1 |
| 353 | Method call &1 => &2 invalid for objects deleted or marked for deletion |
| 354 | Method call &1 => &2 is invalid for obsolete objects |
| 355 | For boolean elements, only simple comparison operations are supported |
| 356 | Timepoint type &1 is only allowed in AP systems |
| 357 | Timepoint type has been changed from '&1' (active version) to '&2' |
| 358 | Element type has been changed from '&1' (active version) to '&2' |
| 359 | Quantity dimension has been changed from '&1' (active version) to '&2' |
| 360 | Software Component has been adapted to &1 for package &2 |
| 361 | Application Component has been adapted to &1 for package &2 |
| 362 | Timepoint type &1 does not fit to date element &2 |
| 363 | Message log action &1 has deviating log settings |
| 364 | At least one message type has to be allowed |
| 365 | Invalid message type defined |
| 366 | Invalid number of denied message types |
| 367 | Ruleset restart option cannot be disabled since ruleset &1 uses it |
| 368 | Value &1 for selection field &2 is longer than &3 characters |
| 369 | Value &1 for selection field &2 contains a not allowed character " ' " |
| 370 | Domain values are language dependent (see value table &1 in DDIC) |
| 371 | Provide either the version or the timestamp for version comparison |
| 372 | Provide a valid version for the version comparison |
| 373 | ID of data object must be unique in signature. ID &1 already exists in &2 |
| 374 | Invalid &1 data object (&2). No name is set |
| 375 | Name of data object must be unique in signature name &1 also exists in &2 |
| 376 | Multiple use of identical objects (&1 and &2) in context not allowed |
| 377 | Multi use of identic objects (&1 and &2) in ruleset variables not allowed |
| 378 | Multiple use of identical objects (&1 and &2) in &3/&4 not allowed |
| 379 | ID of data object must be unique in signature. &1 already exists in &2 |
| 380 | Could not process function &2 in event mode; see longtext |
| 381 | Nested object &2 has different access level (&1) than top object (&3) |
| 382 | Nested object &2 has a lower access level (&1) than top object (&3) |
| 383 | Restricting the access level for a transported data object is not allowed |
| 384 | Setting access level to &1 is due to usage &2 (ID &3) not allowed |
| 385 | Versioning mode "transport" is not allowed for local applications |
| 386 | The changeability of the object was restricted by an application exit |
| 387 | Domain values are language dependent (see value table &1 in DDIC) |
| 388 | Domain values may not be unique (see value table &1 in DDIC) |
| 389 | Text &1 is not convertible into a boolean. |
| 390 | Invalid recursion: &1 holds a reference to itself |
| 391 | Invalid recursion: &1 uses &2 uses &1 |
| 392 | Invalid recursion: &1 uses &2 uses &3 uses &1 |
| 393 | Invalid recursion: &1 uses &2 uses &3 uses &4 uses &1 |
| 394 | Invalid recursion: &1 uses &2 uses &3 uses &4 uses ... uses &1 |
| 395 | Select only one file to save the data |
| 396 | Component '&1' no longer exists in DDIC structure &2 |
| 397 | Component '&1' of DDIC structure &2 is missing |
| 398 | Data type of Data Dictionary (DDIC) type '&1' does not match |
| 399 | &1 is not a valid message severity |
| 400 | Invalid data object binding; data object is bound to more than one type |
| 401 | Address is incorrect; BO name or namespace does not exist |
| 402 | Address is incorrect; BO node does not exist |
| 403 | No reference to GDT element or structure assigned |
| 404 | Structure contains structure type data |
| 405 | Element is not part of the structure, but other GDT types are |
| 406 | Referenced data type is not supported |
| 407 | Code type GDT contains another structure code |
| 408 | Only one of the path format, ESR path or proxy path has to be supplied |
| 409 | External reference fields for amount or quantity are not supported |
| 410 | Connection &1 does not refer to a SAP HANA DB - see transaction DBCO |
| 411 | Not all entries needed to create the path are provided |
| 412 | Invalid sequence of nodes provided for creation of path |
| 413 | Invalid sequence of attributes provided for creation of path |
| 414 | Table &1 has a key field of type string |
| 415 | |
| 416 | Multiple compound objects are not supported |
| 417 | &1 (used by ruleset precondition) is missing in the function context |
| 418 | GTABKEY error while getting software release for &1: &2 not found |
| 419 | GTABKEY error while getting software release for &1: Addon does not exist |
| 420 | Unknown GTABKEY error while getting software release for &1 |
| 421 | AIM details for transport object &1 are incorrect; see long text |
| 422 | No inactive objects found for this application |
| 423 | Function can be activated only if context data objects were assigned |
| 424 | In NGAP no customizing application allowed |
| 425 | &1 using customizing object &2 cannot be copied to system application &3 |
| 426 | &1 using masterdata object &2 cannot be copied to &3 application &4 |
| 427 | &1 using local object &2 cannot be copied to a non-local application &3 |
| 429 | Uncaught exception &1 during function generation |
| 431 | Invalid data supplied |
| 432 | Invalid data reference supplied |
| 435 | "Convert to uppercase" property is set but &1 is not of type text |
| 440 | Object type is set to expression type but no expression type is supplied |
| 441 | Unknown object type &1 |
| 442 | Default object types are not included in the Filter |
| 444 | Component &1 of DDIC structure &2 not bound: switch &3 (&4) is on |
| 445 | Component &1 of DDIC structure &2 not bound: switch &3 (&4) is off |
| 446 | Component &1 of DDIC structure &2 is controlled by switch &3 (&4) |
| 447 | Component &1 is inactive in DDIC structure &2 due to switch &3 (&4) |
| 448 | Data dictionary (DDIC) type &1 is switched off by switch &2 (&3) |
| 449 | Data dictionary (DDIC) type &1 is controlled by switch &2 (&3) |
| 450 | Class &1 is inactive due to switch &2 (&3) |
| 454 | Missing selection for the object categories |
| 455 | Missing selection for local or not local objects |
| 456 | Missing selection for transported or not transported objects |
| 457 | Missing selection for transported or not transported applications |
| 459 | Invalid parameters: Action flag is set, but object type <> expression |
| 460 | Invalid parameters: Expression type is set, but object type <> expression |
| 461 | Invalid parameters: Data object type set, but object type <> data object |
| 462 | Method GET_DATA_OBJECT_STRUCTURE is not available for deployed services |
| 463 | Error while converting context (Context not found in generated class) |
| 464 | Processing with context object is not allowed in a deployed service |
| 466 | The function and its referenced objects have versioning turned on |
| 467 | List of objects which are not versioned: |
| 468 | For object &1, versioning is turned off |
| 469 | All assigned rulesets are consistent |
| 470 | Turning versioning off is not allowed due to application settings |
| 471 | Versioning not turned on for &1 because it is inactive |
| 472 | Versioning not turned on for &1 due to the following check errors |
| 473 | Versioning turned on for &1 |
| 474 | &1 could not be activated after setting versioning on |
| 475 | Object &1 is not versioned |
| 476 | Versioning is set to mandatory, but the following objects are unversioned |
| 477 | &1 is currently inactive; see long text |
| 478 | No used obejct has an inactive version |
| 479 | No timepoint type is specified |
| 480 | Used data object &1 has an inactive state, activate before simulation |
| 482 | Ruleset condition cannot be determined (unknown ID: &1) |
| 483 | Invalid object &1 set as ruleset condition |
| 484 | Rule condition cannot be determined (unknown ID: &1) |
| 485 | Invalid object &1 set as rule condition |
| 486 | Target &1 is recorded on another transport request |
| 490 | Data objects that are part of a bound data structure cannot be renamed |
| 491 | Data objects that are part of a bound data structure cannot be unbound |
| 497 | Provide either Dictionary Type or Application ID or Application Component |
| 500 | Generation is not possible: &1 &2 &3 |
| 501 | Generation is not yet supported &1->&2 |
| 502 | Generation for &1 not possible |
| 503 | Generation for function &1 failed: &2 |
| 504 | Generation for element type &1 not supported |
| 505 | Generation for data object type &1 not supported |
| 506 | Generation for the operation code &1 not supported |
| 507 | Generated code for function &1 contains &2 lines |
| 508 | Generated code for &1 contains &2 switches to interpretation mode |
| 509 | Generated class for function &1 is &2 |
| 510 | Generation for &1 failed. |
| 511 | Generation for &1 failed - probably due to enqueue a problem |
| 512 | Processing in generation mode is currently not possible |
| 513 | Generation not possible as there are unsaved objects in memory |
| 514 | Generated object has to be a class, not type &1 |
| 515 | Generated object &1 could not be read |
| 516 | Generation not possible, because it is turned off manually |
| 517 | Error in context generation: &1 is neither in the context nor the result |
| 518 | Generation of context data object &1 with type any not allowed |
| 519 | Error saving generated class, two components have the same name |
| 520 | Data element cannot be moved into a table |
| 521 | Data cannot be move |
| 522 | Error saving generated class (sy-subrc = &1) |
| 523 | Generation manager is registered on &2, so it is not usable for &1 |
| 524 | Access to context object not possible, as it doesn't exist |
| 525 | Data object &1 is neither in the context nor the result |
| 526 | Inconsistent buffer entry, generation not possible |
| 527 | Class cannot be generated |
| 528 | No generation manager found, method not called during generation |
| 530 | Only positive number values accepted for element &1 |
| 531 | Application &1 cannot be assigned to another application |
| 532 | Generated code switched to interpretation mode, deployment not possible |
| 535 | In analytical function ruleset conditions are not supported |
| 536 | Rules are not allowed in a ruleset assigned to an analytical function |
| 537 | Ruleset variables not allowed in ruleset assigned to analytical function |
| 538 | Ruleset assigned to the analytical function does not contain expressions |
| 539 | Result data object of analytical function cannot be structure or element |
| 540 | Cannot generate analytical function with current system configurationn |
| 542 | View Parameter data object &1 is missing in function context |
| 543 | Context data object &1 is not used |
| 550 | Object is used in client &1; check manually for potential problems |
| 569 | Association ID missing for &1; Use Refresh Binding to resolve |
| 570 | Data object &1 is not a structure or not bound to CDS view |
| 571 | Service URL and Property Path must contain values or both must be empty |
| 572 | Wrong format of Rule Expression Language Version |
| 573 | Previous Rule Expression Language Version is greater than new one |
| 574 | OData service-based value help is only supported for text elements |
| 575 | &1 cannot be used in expression language; type not supported |
| 599 | The following messages were issued by CTS-checks |
| 600 | Undefined CTS-check error |
| 601 | System &1 / client &2 does not allow object changes for the object |
| 602 | Object is marked for deletion; attribute changes cannot be saved |
| 603 | Object is marked as obsolete; attribute changes cannot be saved |
| 604 | BRFplus standard objects of application FDT_SYSTEM cannot be changed |
| 605 | System settings do not allow changes for client-independent objects |
| 606 | System settings do not allow changes for customizing objects |
| 607 | Deployable objects cannot be changed in customer systems |
| 608 | Changeability cannot be determined for client &1 in runtime client &2 |
| 609 | In zero downtime mode BRFplus objects must not be created or changed |
| 680 | &1 is not an action |
| 698 | No change allowed (no change of t- or s-table objects) |
| 699 | No modifications allowed (no change of system objects) |
| 700 | &1 (ID &2) has not been saved to the database yet |
| 701 | There is no active version of &1 in the database yet |
| 702 | &1 must not use &2 of virtual system '&3' |
| 703 | The &1 does not exist; deep save has to be aborted |
| 704 | The transport request is initial |
| 705 | Transport request is missing. It cannot be determined automatically |
| 707 | &1 is a &2 object; only customizing objects allowed in BCF mode |
| 710 | &1 cannot be transported; it is a temporary object |
| 715 | Transport request or task &1 is invalid |
| 716 | &1 is not recordable into a request |
| 717 | Customizing objects can only be transported from the development client |
| 718 | Transport request &1 cannot be used because change recording is disabled |
| 719 | Transport request or task &1 is already released |
| 720 | Transport request or task &1 not found |
| 721 | User &1 has no task assigned to transport request &2 |
| 722 | User &1 is not the owner of task &2 |
| 730 | Object &1 is not enqueued; inactive version cannot be deleted |
| 731 | Object &1 cannot be enqueued; inactive version cannot be deleted |
| 746 | Versioned catalogs can lead to high storage requirements |
| 749 | Either node ID or node UUID needs to be supplied |
| 750 | Unknown node ID &1 |
| 751 | Invalid attribute &1; must be an elementary data object |
| 752 | Object type &1 is not supported |
| 753 | Invalid method call; either link or leaf properties can be set |
| 754 | Node ID &1 (&2) has children(stuct.node);no leaf/link attributes possible |
| 755 | &1 is not a catalog |
| 756 | Unknown sibling &1 |
| 757 | Unknown parent &1 |
| 758 | Sibling &1 does not belong to parent &2 |
| 759 | Value &2 set for invalid attribute &1 (not part of attribute list) |
| 760 | Unknown node &1 |
| 761 | Node ID &1 (&2) cannot be moved underneath itself (recursion) |
| 762 | Node ID &1 is a node of type structure and has no name |
| 763 | Attribute of element type &1 is currently not supported |
| 764 | Node UUID &1 is unknown; link is invalid |
| 765 | Node ID &1 (&2) needs to be of type Leaf |
| 766 | Node ID &1 (&2) needs to be of type Object |
| 768 | &3: node UUID &1 does not belong to node ID &2 (&4) |
| 770 | Node ID &1 is of type structure; text binding is not possible |
| 771 | Node ID &1: Either enable node text binding or provide node texts |
| 775 | |
| 780 | Error encountered while relocating functions in GTABKEY service |
| 781 | Application successfully registered in GTABKEY with software component &1 |
| 782 | Application successfully registered in GTABKEY with new name |
| 783 | Error encountered while registering application in GTABKEY |
| 790 | ID &1 is not of type expression |
| 791 | Context structure could not be created; check nested exceptions |
| 792 | Invalid Element Type &1 |
| 799 | Message class &1 does not exist |
| 800 | No message found |
| 801 | Invalid variable &1 |
| 802 | Message number &1 in message class &2 does not exist |
| 803 | Message text of &1(&2) does not have a first message variable |
| 804 | Message text of &1(&2) does not have a second message variable |
| 805 | Message text of &1(&2) does not have a third message variable |
| 806 | Message text of &1(&2) does not have a fourth message variable |
| 807 | Message text of &1(&2) requires a first message variable |
| 808 | Message text of &1(&2) requires a second message variable |
| 809 | Message text of &1(&2) requires a third message variable |
| 810 | Message text of &1(&2) requires a fourth message variable |
| 811 | Variable &1 cannot be converted into text |
| 812 | No check for variable &1 possible; data-dependent conversion into text |
| 813 | Either supply ID or text for a message variable &1, but not both |
| 814 | Either supply free text or a T100 message for message, but not both |
| 815 | Wrong message type set. |
| 816 | Maximum length for the message almost reached; message may be truncated |
| 817 | &1 &2 is not explicitly allowed in the current object context |
| 818 | &1 &2 is explicitly not allowed in the current object context |
| 819 | &1 &2 with the current parameter combination in not allowed |
| 820 | Message text does not have a first message variable |
| 821 | Message text does not have a second message variable |
| 822 | Message text does not have a third message variable |
| 823 | Message text does not have a fourth message variable |
| 824 | Message text requires a first message variable |
| 825 | Message text requires a second message variable |
| 826 | Message text requires a third message variable |
| 827 | Message text requires a fourth message variable |
| 828 | Message contains invalid message variable |
| 829 | Message number &1 in message class &2 does not exist for language &3 |
| 830 | Message &1 &2 can contain only up to 4 placeholders |
| 831 | Enter the placeholders in right order |
| 832 | Result size &1 exceeds maximum result size &2 |
| 833 | Enter either &1 or &2 but not both |
| 834 | Message number &1 in message class &2 does not exist for any language |
| 835 | Message type '&1' (message &2) is not allowed in this application |
| 836 | Exception &1 raised while executing function module &2 |
| 837 | Invalid context value: &1 |
| 838 | Supply either a free text or a predefined message for message number &1 |
| 839 | Action definition incomplete (no message defined) |
| 840 | Message text for message &1 exceeds maximum length (255 characters) |
| 841 | More than 255 operations are not allowed in a rule |
| 845 | Different number of placeholders for message &1(&2) in language &3 and &4 |
| 849 | |
| 850 | Operation &1 is not allowed during LUW Mode |
| 853 | Data object ID &1 from Initialize variable is missing in ruleset context |
| 854 | Data object &1 from Initialize variable is missing in the ruleset context |
| 855 | Temporary ruleset variable &1 needs a name (Pos&2) |
| 856 | Temporary ruleset variable &1 needs to have a unique name |
| 857 | Temporary ruleset variable &1 is not unique within the function context |
| 858 | Condition ID &1 from rule (pos &2) is missing in the ruleset context |
| 859 | ID &1 in range from rule (pos &2) is missing in the ruleset context |
| 860 | Data object ID &1 from rule (pos &2) is missing in the ruleset context |
| 861 | &1 (ruleset precondition) is missing in the function context |
| 862 | ID &1 in ruleset condition range is missing in the ruleset context |
| 863 | Condition &1 from rule (pos &2) is missing in the ruleset context |
| 864 | Data object &1 from rule (pos &2) is missing in the ruleset context |
| 866 | Exception occured while checking the context for ruleset &1. |
| 867 | No function assigned to ruleset &1 |
| 868 | Neither ruleset &1 nor any of its rules has a function assigned |
| 869 | Nested function &1 was not deployed |
| 870 | Local version of nested function &1 will be used during processing |
| 871 | Not more than 255 variables are allowed in a ruleset |
| 872 | Not more than 255 rules are allowed in a ruleset |
| 873 | No ruleset registered on the function |
| 874 | Exit condition at position &1 is disabled |
| 875 | Rule &1 at position &2 is disabled |
| 876 | Error in initialization with &1 |
| 877 | &1 occurs multiple times in the ruleset variables list |
| 878 | Invalid object &1; expression or data object needed |
| 879 | Ruleset &1 is disabled |
| 880 | Conflict with rule set function restriction in line &1 |
| 881 | Invalid condition; &1 does not have a boolean value |
| 882 | Missing condition for ruleset exit (position &1) |
| 883 | Either provide rule or ruleset exit but not both (position &1) |
| 884 | Invalid state of switch in line &1 (only "X" and " " are possible values) |
| 885 | Invalid time stamps in line &1; to-value &2 smaller / equal from-value &3 |
| 886 | No rule provided at position &1 |
| 887 | Invalid rule &2 at position &1 |
| 888 | Function &1 used in rule(s) but does not support event mode |
| 889 | Invalid state of rule set switch (only "X" and " " are possible values) |
| 890 | ID &1 is unknown or is not of type Application |
| 891 | Position &1: functions cannot be assigned to expressions (not supported) |
| 892 | Invalid change mode in line &1 (only " " and "I" are possible values) |
| 893 | Invalid change mode (only " " and "I" are possible values) |
| 894 | No rules provided |
| 895 | &1 is used twice in the ruleset initialization |
| 896 | &1 is not a data object (position &2) |
| 897 | No object set at position &1 |
| 898 | ID &1 is not of type Application |
| 899 | Restart options are only allowed for a ruleset exit (position &1) |
| 900 | &1 is unnamed and not used by any object |
| 901 | &1 is unnamed and is used by more than one object |
| 902 | Text symbol &1 was not found in program &2 with language &3 |
| 903 | SAPscript object &1 with ID &2 was not found |
| 904 | SAPscript object &1 with ID &2 was not found with language &3 |
| 905 | Text symbol: Program &1 is not valid |
| 906 | Provide exactly one of: exit class, text symbol or free text |
| 907 | Provide exactly one of: exit class, SAPscript obj. or free documentation |
| 908 | No rules are enabled in the ruleset |
| 909 | Restart option defined (position &1) but not supported by application |
| 910 | The XML file does not contain the entire application |
| 911 | |
| 912 | |
| 920 | Context structure could not be created. Check nested exceptions |
| 921 | Invalid Element Type &1 |
| 980 | Transport failure |
| 981 | Transport failure; no active version of &1 |