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