ESH_OM_OBJ_MODEL_RP2 - Object Model Repository (2)
The following messages are stored in message class ESH_OM_OBJ_MODEL_RP2: Object Model Repository (2).
It is part of development package S_ESH_ENG_OBJ_MOD_REP in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Model Repository".
It is part of development package S_ESH_ENG_OBJ_MOD_REP in software component BC-EIM-ESH. This development package consists of objects that can be grouped under "Model Repository".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Data provider &1, attribute group &2 does not exist |
| 002 | Data provider &1, attribute group &2, language &3: |
| 003 | Attribute group &1 does not exist |
| 004 | Assignment of data provider &1, field &3 to attribute group &2 |
| 005 | Data provider &1, field &2 does not exist |
| 006 | Data provider &1, attribute group &2: |
| 007 | Hierarchy of attribute groups contains a loop |
| 008 | Data provider &1, attribute group &2 already exists |
| 009 | Field &3 is already assigned to data provider &1, atrribute group &2 |
| 010 | Attribute group &3 is already used data provider &1,attribute group &2 |
| 011 | Description already exists in language &3 |
| 012 | Node attribute groups: Node type ID &1, attribute group &2 |
| 013 | Node attribute group texts: Node type ID &1, attr. group &2, language &3 |
| 014 | Node type ID &1, node attribute group &2 is not provided |
| 015 | Node attribute group fields: Node type ID &1, group ID &2, field &3 |
| 016 | Parent node attribute group &1 is not provided |
| 017 | Response attribute groups: Node type ID &1, attribute group &2 |
| 018 | Parent response attribute group &1 is not provided |
| 019 | Resp. attribute group texts: Node type ID &1, attr. group &2, language &3 |
| 020 | Node type ID &1, response attribute group &2 is not provided |
| 021 | Request attribute groups: Node type ID &1, request ID &2, group &3 |
| 022 | Parent request attribute group &1 is not provided |
| 023 | Response attribute group texts: |
| 024 | Node type ID &1, request &2, attribute group &3, language &4 |
| 025 | Node type ID &1, request &2,attribute group &3 is not provided |
| 026 | Response attribute group fields: Node type ID &1, group ID &2, field &3 |
| 027 | Response attribute group fields: |
| 028 | Node type ID &1, request &2, attibute group ID &3, field &4 |
| 029 | Response field texts: Node type &1, field &2, language &3 |
| 030 | Node type ID &1, response field ID &2 is not provided |
| 031 | Only one field can have semantics "Searchable file" |
| 032 | UI area &1 is not possible for response attribute groups |
| 033 | Flag for interactive navigation belongs to request fields now |
| 034 | Flag for interactive navigation belongs to request fields now |
| 035 | Request attribute group texts: |
| 036 | Request attribute group fields: |
| 037 | Node &1 has fields with the same description |
| 038 | Node &1 has response fields with the same description |
| 039 | Request &1 has fields with the same description |
| 040 | ODP ID &1, ODP semantics &2 has fields with the same description |
| 041 | Field with semantic "Searchable File" must be of type RSTR (RAWSTRING) |
| 042 | Term not found |
| 043 | Enter a search term |
| 044 | Node &1 has no field with semantic "MIME Type" |
| 045 | Node &1 has an unpaired field with semantic "MIME Type" |
| 046 | Node &1 has no field with semantic "MIME Type" |
| 047 | Connectors of system software component &1 cannot be created |
| 048 | ODP ID &1, ODP semantics &2 has fields with the same description |
| 049 | Data type &1 is not used in area &2 (model &3, sysrel. &4) |
| 050 | Attribute group &1 does not contain fields or other attribute groups |
| 051 | No field of the attribute group is assigned to UI area &1 |
| 052 | Connector for model &1 already exists and is up-to-date |
| 053 | Flag "Based on BW Data Sources" cannot be changed |
| 054 | Node &1 should not have response fields with UI area assignments |
| 055 | Response attribute group areas: Node type ID &1, group ID &2, UI area &3 |
| 056 | Navigation path of object type &1, node &2, response field &3: |
| 057 | Navigation path of object type &1, node &2, request &3, field &4: |
| 058 | Navigation path of object type &1, node &2, ODP &3, field &4: |
| 059 | Navigation path of path-based authorization check &1: |
| 060 | Navigation path for ABAP authorization check &1, authorization field &2: |
| 061 | Node &1 has been updated successfully |
| 062 | Node &1 has been reset successfully |
| 063 | Object type &1 has been locked by user &2 |
| 064 | Object type &1: System failure during lock |
| 065 | Authorization checks are defined for the reference node |
| 066 | Authorization check &1 has been locked by user &2 |
| 067 | Authorization check &1: System failure during lock |
| 068 | Common attribute &1 is in customer namespace (&2) |
| 069 | Common attribute &1 has to start with &2 in customer systems |
| 070 | Common attribute &1 contains forbidden chararcters |
| 071 | Common attribute &1 must start with prefix &2 |
| 072 | Common attribute &1 must start with prefix &2 or &3 |
| 073 | Common attribute is initial |
| 074 | Common attribute &1: |
| 075 | Common attribute &1 has no superordinate software component |
| 076 | Common attribute &1, language &2: |
| 077 | Key of assignment to common attribute &1 is not fully specified |
| 078 | Key of common attribute description is not fully specified |
| 079 | Common attribute &1 does not exist |
| 080 | Common attribute &1 already exists |
| 081 | Assignment to common attribute &1 already exists |
| 082 | The request field cannot be assigned to common attriubte &1 |
| 083 | Request &1 has fields with assignments to common attributes |
| 084 | Cannot delete common attribute |
| 085 | Common attribute contains request fields of object type &1 in SWC &2 |
| 086 | Assignment of common attributes: Node type ID &1, request ID &2, ... |
| 087 | Common attributes: Common attribute ID &1: |
| 088 | Common attribute texts: Common attribute ID &1, language &2: |
| 089 | The software component contains object types with initial ID |
| 090 | Object type &1 contains nodes with initial ID |
| 091 | System failure during lock |
| 092 | Request &3 of object type &1, node &2 is not a rational related request |
| 093 | Node &1 does not contain the necessary response fields for navigation |
| 094 | User &2 is editing content of software component &1 |
| 095 | User &2 is editing content of system &1 |
| 096 | Authorization object &1 has been locked by user &2 |
| 097 | Authorization object &1: System failure during lock |
| 098 | Data provider &1 has been locked by user &2 |
| 099 | Data provider &1: System failure during lock |
| 100 | Several users are editing content of software component &1 |
| 101 | Several users are editing content of system &1 |
| 102 | Referenced node field &3 of object type &1, node &2 does not exist |
| 103 | External references were deleted: |
| 104 | The referenced node field does not exist |
| 105 | External usages were created: |
| 106 | Relation &1 has been locked by user &2 |
| 107 | Relation &1: System failure during lock |
| 108 | Referenced node field &3 of object type &1, node &2 does not exist |
| 109 | Referenced node field &3 of object type &1, node &2 does not exist |
| 110 | Referenced authorization check &1 does not exist |
| 111 | Referenced node field &3 of object type &1, node &2 does not exist |
| 112 | The referenced node field does not exist |
| 113 | User &2 is saving their work in software component &1, try again later... |
| 114 | User &2 is saving their work in system &1, try again later... |
| 115 | Node is referenced in association &1 |
| 116 | Referenced node &2 of object type &1 does not exist |
| 117 | The referenced node does not exist |
| 118 | The common attribute contains request fields of incompatible types: |
| 119 | Referenced data provider &1 does not exist |
| 120 | The referenced data provider does not exist |
| 121 | The node where the path starts does not exist |
| 122 | The node where the path ends does not exist |
| 123 | Referenced filter &2 of data provider &1 does not exist |
| 124 | The referenced data provider filter does not exist |
| 125 | Node &2 of object type &1 that is used in the path does not exist |
| 126 | A node that is used in the path does not exist |
| 127 | Unexpected error during import of software component &1 |
| 128 | Node is referenced in navigation path of: |
| 129 | Request &3 of object type &1, node &2 (related request) does not exist |
| 130 | The request that is used as a related request does not exist |
| 131 | The request is used as a related request in object type &1, node &2 |
| 132 | Model node reference object type &1, node &2, does not exist |
| 133 | The model node reference does not exist |
| 134 | Node is referenced in virtual model &1 |
| 135 | Assignment of authorization field &2 to a node field does not exist |
| 136 | The assignment of an authorization field to a node field does not exist |
| 137 | Relation is referenced assignment of authorization check to a node: |
| 138 | Referenced node field &3 of object type &1, node &2 does not exist |
| 139 | The referenced node field does not exist |
| 140 | Referenced authorization check &1 does not exist |
| 141 | The referenced authorization check does not exist |
| 142 | Referenced authorization object key &1 (auth. object &2) does not exist |
| 143 | The referenced authorization object key does not exist |
| 144 | The data provider filter is referenced in object type &1, node &2 |
| 145 | Authorization check &1 has been created in the meantime |
| 146 | Authorization object key &1 has been created in the meantime |
| 147 | Data provider &1 has been created in the meantime |
| 148 | Referenced data type &1 does not exist |
| 149 | The referenced data type does not exist |
| 150 | Referenced data type &1 does not exist |
| 151 | The referenced data type does not exist |
| 152 | Data provider &1 has been deleted in the meantime |
| 153 | Authorization check &1 has been deleted in the meantime |
| 154 | Referenced category &1 does not exist |
| 155 | The referenced category does not exist |
| 156 | Common attribute &1 does not exist |
| 157 | The common attribute does not exist |
| 158 | Categories have been locked by user &2 |
| 159 | Categories: System failure during lock |
| 160 | Common attributes: System failure during lock |
| 161 | Common attributes have been locked by user &2 |
| 162 | Common attribute contains request fields of globally-defined SWC |
| 163 | Category is the parent of a globally-defined category |
| 164 | ODP is used in ODP field &4 of object type &1, node &2, ODP &3 |
| 165 | Association &1 that is used in the path does not exist |
| 166 | Composition from node &1 to node &2 in object type &3 does not exist |
| 167 | A relation that is used in the path does not exist |
| 168 | Field &3 of authorization object key &1 (auth. object &2) does not exist |
| 169 | The referenced authorization object field does not exist |
| 170 | Error when creating hash code for effective authorization checks |
| 171 | Node &3 of object type &2 cannot be deleted as user &1 locks associations |
| 172 | Node &2 of object type &1 cannot be deleted due to locked associations |
| 173 | User &1 locks associations assigned to object type &2 |
| 174 | Associations assigned to object type &2 have been locked |
| 175 | Authorization check &1 cannot be assigned as it has been changed |
| 176 | Package &1 does not exist |
| 177 | Software component type &1 does not exist |
| 178 | Type &1 is not character-like, alpha-conversion is not possible |
| 179 | ODP semantics &1 does not exist |
| 180 | ODP semantics is initial |
| 181 | Node field cannot contain text as it is used in authorization checks |
| 182 | Node field cannot be assigned because it contains text |
| 183 | Node field cannot be assigned to authorization field &1 |
| 184 | Authorization object key &1 has been deleted in the meantime |
| 185 | Select a back-end connectivity |
| 186 | The virtual model has to have a reference node |
| 187 | The model has no package assignment |
| 188 | There has to be at least one node |
| 189 | There are nodes without parent node |
| 190 | The model has no requests maintained |
| 191 | The model has no response and UI area assignments maintained |
| 192 | The model has no authorization checks maintained |
| 193 | The model has no related actions maintained |
| 194 | The model has no operational data provider maintained |
| 195 | The path of auth. field &1 does not fit to node &2 of object type &3 |
| 196 | More than one field of request &1 is assigned to common attribute &2 |
| 197 | Only one field of request &1 can be assigned to common attribute &2 |
| 198 | Request &3 of object type &1, node &2 is not relevant for ODPs |
| 199 | Request is used in object type &1, node &2, ODP &3, field &4 |
| 200 | Request &3 of object type &1, node &2 (navigation request) does not exist |
| 201 | The request that is used as a navigation request does not exist |
| 202 | The request is used as a navigation request ODP-field &1/&2/&3/&4 |
| 203 | Join operators other than = are currently not supported in search |
| 204 | Join operator &1 does not exist |
| 205 | A relation already exists between node field &1 and &2 |
| 206 | The relation has no field assignment with join operator '=' (equal) |
| 207 | A cross-system reference cannot be set in software component &1 |
| 208 | Model GUID &1 cannot be used in cross-system reference |
| 209 | Cross-system references can only be set on Enterprise Search hubs |
| 210 | Cross-system reference model GUID for source node |
| 211 | Cross-system reference model GUID for target node |
| 212 | Cross-system reference model GUID for source field |
| 213 | Cross-system reference model GUID for target field |
| 214 | Model GUID &1 does not exist |
| 215 | In SWC &1, it is not possible to use cross references in: &2 |
| 216 | In SWC &1, it is not possible to use cross references in: &2 |
| 217 | Cross references are impossible between central cross-system SWCs |
| 218 | No cross references between cross-system SWCs |
| 219 | No cross references from central cross-system SWCs and cross-system SWCs |
| 220 | No cross-references between software components within the same stack |
| 221 | Choose a software component first |
| 222 | ODP usage &1 does not exist |
| 223 | Mapping role &1 does not exist |
| 224 | A composition must not have an association type |
| 225 | The composition links different object types |
| 226 | Object type &1, usage ID &2: |
| 227 | Key of usage is not fully specified |
| 228 | Source object type &1 does not exist |
| 229 | Target object type &1 does not exist |
| 230 | Usage ID &1 already exists |
| 231 | The relation is not a cross-system rel. but has cross-system references |
| 232 | Field &1 of fixed value defintion is no field of source or target node |
| 233 | Source object type model GUID does not exist |
| 234 | Target object type model GUID does not exist |
| 235 | Software comp. &1 is not a cross-system SWC or central cross-system SWC |
| 236 | Software component &1 is not a cross-system software component |
| 237 | Key of usage description is not fully specified |
| 238 | Authorization type &1 does not exist |
| 239 | Logical conjunctions to object type &1, node &2: syntax error |
| 240 | Usage description in language &1 already exists |
| 241 | Connectors of competitive software component &1 already exist |
| 242 | Conversion of model from generic to nongeneric unsuccessful |
| 243 | Data provider 'DDIC' is not available |
| 244 | Default request cannot be created: Define response attributes first |
| 245 | Object type &1, usage ID &2, usage field &3: |
| 246 | Key of usage field is not fully specified |
| 247 | Object type &1, usage ID &2 does not exist |
| 248 | Usage field model GUID does not exist |
| 249 | Usage ID &1, usage field &2 already exists |
| 250 | Internal error when creating MUID-matrix - Inform SAP |
| 251 | Not all authorization checks are listed in logical conjunction (type &1) |
| 252 | Data provider &1 has raised an exception during import |
| 253 | Data provider &1 has raised an exception during import of node &2 |
| 254 | Model &1 is assigned to package $$TMP |
| 255 | Model &1 must not start with Y or Z |
| 256 | Request &1 must be flagged for at least one usage |
| 257 | The request cannot be the default ODP request as it is not OPD-relevant |
| 258 | There must be exactly one default ODP request |
| 259 | You cannot change the default ODP request because it is inherited |
| 260 | There are requests relevant for ODP but none of these is set as default |
| 261 | Field with semantic "Content URL" must be of type STRG (STRING) |
| 262 | Assign selected connectivity to software component &1 first |
| 263 | Import of software component &1 from XML file was unsuccessful (&2) |
| 264 | Data provider controller cannot retrieve data providers |
| 265 | Metadata provider did not provide any data |
| 266 | There is more than one logical conjunction of type &1 for node type ID &2 |
| 267 | Node type ID &1: Initial logical conjunction type was set to &2 |
| 268 | Software component &1 cannot be assigned to system software component &3 |
| 269 | The following object types are assigned to package &1: |
| 270 | &1 |
| 271 | Authorization check &1 is user-based but has check value definitions |
| 272 | Select a file path for upload |
| 273 | Metadata provider is not available (class &1) |
| 274 | ODP ID &1 is longer than 12 characters |
| 275 | ODP field &1 is longer than 12 characters |
| 276 | Cannot delete ODP &1 with semantics &2 |
| 277 | ODP &3 of object type &1, node &2 (navigation ODP) does not exist |
| 278 | The ODP that is used as a navigation ODP does not exist |
| 279 | The ODP is used as a navigation ODP in object type &1, node &2 |
| 280 | Node type I &1, request ID &2: No flags are provided, so default is used |
| 281 | &1 is a reserved node field name |
| 282 | &1 is a reserved node field GUID |
| 283 | Basis software component &1 cannot use non-basis software component &2 |
| 284 | "Basis SWC" flag cannot be added to software component &1 |
| 285 | "Basis SWC" flag cannot be removed from software component &2 |
| 286 | Authorization check &1 already exists |
| 287 | Wrong call of method CL_ESH_OM_MODELS=>CONVERT_MODEL_GUID_TO_NONGEN |
| 288 | Wrong call of method CL_ESH_OM_MODELS=>CONVERT_MODEL_GUID_TO_GEN |
| 289 | URL &1 is not valid |
| 290 | Usage ID &1, attribute group &2 already exists |
| 291 | Usage ID &1, attr. group &2, usage field &3: Assignment already exists |
| 292 | Attribute group description in language &1 already exists |
| 293 | Object type &1, usage ID &2, attribute group &3: |
| 294 | Object type &1, attribute group &2 |
| 295 | Error when creating hash code - inform SAP |
| 296 | Request auto-tagging type &1 does not exist |
| 297 | Node &2 cannot be enhanced with key attributes in software component &4 |
| 298 | Assignment of object type &1, usage id &2, field &4 to attribute group &3 |
| 299 | Key of usage field assignment to attribute group is not fully specified |
| 300 | Key of usage attribute group is not fully specified |
| 301 | Key of usage attribute group description is not fully specified |
| 302 | Object type &1, usage ID &2, usage field &3 does not exist |
| 303 | Object type &1, usage ID &2, usage attribute group &3 does not exist |
| 304 | Object type &1, usage ID &2, usage attribute group &3, language &4: |
| 305 | Object type &1, usage ID &2, language &3: |
| 306 | Package &1 cannot be assigned to software component &2 |
| 307 | Usage type &1 does not exist |
| 308 | Selected models of another software component got deselected |
| 309 | Software component &1 cannot be transported because it has type &2 |
| 310 | Wrong setting of get-own-model-flags: inform SAP |
| 311 | CL_ESH_OM_MODEL_SERVICES not initialized: inform SAP |
| 312 | More than one request is flagged as default request |
| 313 | Repository context &1 does not exist (internal error): inform SAP |
| 314 | Old software component &2 was registered for transport |
| 315 | New software component &2 is not registered for transport |
| 316 | Old software component &2 was registered for transport |
| 317 | New software component &2 is not registered for transport |
| 318 | OPD field &1 and OPD field &2 refer to the same node field |
| 319 | Logical conjunction type &1 does not exist |
| 320 | Reverse/source cardinality "&3" does not fit to foreign key definitions |
| 321 | Cardinality "&3" does not fit to foreign key definitions |
| 322 | Reverse/source cardinality "&3" does not fit to foreign key definitions |
| 323 | Cardinality "&3" does not fit to foreign key definitions |
| 324 | Cardinality "&3" does not fit to foreign key definitions |
| 325 | Cardinality "&3" does not fit to foreign key definitions |
| 326 | Connector for object type &1 is assigned to the category |
| 327 | Common attribute contains request fields of connector for object type &1 |
| 328 | Node is referenced in data provider &1, filter &2 |
| 329 | Data provider filter cannot be assigned to object type &1, node &2 |
| 330 | Data provider filter cannot be assigned to object type &3, node &4 |
| 331 | Initialization error in CL_ESH_OM_MODEL_SERVICES: inform SAP |
| 332 | OBSOLETE |
| 333 | Software component is free of conflicts |
| 334 | Repeat check regularily (Actions -> Resolve Conflicts) |
| 335 | &1 is not a data base table |
| 336 | Connector for model &1 cannot be created as data is not extractable |
| 337 | RFC destination &1 does not exist |
| 338 | There are more than two response attributes with UI area "Longtext" |
| 339 | Root node cannot be changed as object type is inherited from lower SWC |
| 340 | Request fields have been removed |
| 341 | Object type &1 cannot be directly accessible |
| 342 | Object type &1 direct accessible: Authorization check &3 incompatible |
| 343 | Filter conditions are not valid for application based object type |
| 344 | Client fields cannot be used in association |
| 345 | Client fields cannot be used in composition |
| 346 | Node &2 references another node but object type &1 is not virtual |
| 347 | ODP ID &1, semantic &2, has been renamed to ODP ID &3, semantic &4 |
| 348 | Connectors must be deleted, recreated and indexed in target systems |
| 350 | Connector for object type &1 cannot be updated |
| 351 | Connector for object type &1 cannot be updated |
| 352 | Auto completion cannot be set |
| 353 | Layout configuration &1: |
| 354 | Layout configuration &1 already exists |
| 355 | Layout configuration is initial |
| 356 | Platform &1 does not exist |
| 357 | Secondary key of layout configuration is inconsistent |
| 358 | Technology &1 does not exist |
| 359 | Attribute &1 must be numerical but value is &2 |
| 360 | Layout configuration &1 is not assigned to a software component |
| 361 | Cannot delete layout configuration |
| 362 | Object type &1, node &2, layout configuration &3: |
| 363 | Layout configuration &1 does not exist |
| 364 | Layout configuration &4 is used in object type &1, node &2 of SWC &3 |
| 365 | The layout configuration does not exist |
| 366 | Layout configurations have been locked by user &2 |
| 367 | Layout configurations: System failure during lock |
| 368 | Layout template for layout configuration &1 already exists |
| 369 | Layout configuration is initial |
| 370 | Layout template cannot be created because node &2 has no response fields |
| 371 | Node &2 has at least one layout template but no response fields |
| 372 | Related perspective for object type &1, node &2: |
| 373 | Key of related perspective &1/&2 is not fully specified |
| 374 | Mapping number for related perspective &1/&2 is initial |
| 375 | Perspective &1/&2 is already assigned with mapping number &3 |
| 376 | Related perspective &1/&2/&3/&4: |
| 377 | Description of related perspective in language &1 already exists. |
| 378 | Key of related perspective description is not fully specified |
| 379 | Related perspective &1/&2/&3, language &4: |
| 380 | Related perspective does not exist |
| 381 | Related perspectives &1 and &2 have the same description in language &3 |
| 382 | Related perspective field mapping &1/&2/&3/&4: |
| 383 | Key of related perspective was not fully specified |
| 384 | Related perspective &1/&2/&3/&4 does not exist |
| 385 | Response field is initial |
| 386 | Cannot delete response field |
| 387 | Response field is used in related perspective field mapping &1/&2/&3/&4 |
| 388 | Response field &3 of object type &1, node &2 does not exist |
| 389 | The response field used in a related perspect. field map. does not exist |
| 390 | Field is referenced in related perspective field mapping &1/&2/&3/&4 |
| 391 | Field mapping resp. fld. &1 / rel. persp. attribute &2 already exists |
| 392 | Fixed value definition of related perspective &1/&2/&3/&4: |
| 393 | Related perspectives fixed valued definition: Key is not fully specified |
| 394 | Related perspective attribute &1 is already assigned to a response field |
| 395 | Related perspective attribute &1 is already given fixed values |
| 396 | Related perspectives: Node type ID &1, related perspective &2/&3/&4 |
| 397 | Related perspective texts: Node type id &1, perspect. &2/&3, lanugage &4 |
| 398 | Node type id &1, package &2, perspect. &3, mapping no. &4 is not provided |
| 399 | Related perspective field mappings: Node type id &1, mapping &2/&3/&4 |
| 400 | Related perspect. fixed val.: Related persp. &1/&2/&3/&4 is not provided |
| 401 | Response field must be freestyle or assigned to a perspective attribute |
| 402 | Related perspective field mapping &1/&2/&3 (freestyle): |
| 403 | Response field is used in related persp. field mapping &1/&2/&3 (freest.) |
| 404 | Field is referenced in related perspect. field mapp. &1/&2/&3 (freestyle) |
| 405 | Layout type &1 does not exist |
| 406 | Mapping number for related request &1/&2/&3 is initial |
| 407 | The subquery flag only be set for UI technology &1 |
| 408 | Related requests &1/&2 and &3/&4 have the same navigation ID |
| 409 | Related request &1/&2 and related perspective &3/&4 have the same ID |
| 410 | Related request &1/&2 and backend navigation &3/&4 have the same ID |
| 411 | Related perspectives &1/&2 and &3/&4 have the same navigation ID |
| 412 | Related perspectives &1/&2 and related request &3/&4 have the same ID |
| 413 | Related perspectives &1/&2 and backend navigation &3/&4 have the same ID |
| 414 | Backend navigation &1/&2 and related request &3/&4 have the same ID |
| 415 | Backend navigation &1/&2 and related perspective &3/&4 have the same ID |
| 416 | Internal error when updaten temporary buffer &1: Inform SAP |
| 417 | Navigation ID of related request &1/&2/&3/&4 contains forbidden char. |
| 418 | Navigation ID of related perspective &1/&2/&3 contains forbidden char. |
| 419 | Navigation ID of backend navigation &1/&2 contains forbidden characters |
| 420 | Related request &1/&2/&3, language &4: |
| 421 | Key of related request description is not fully specified |
| 422 | Description of related request in language &1 already exists. |
| 423 | Related requests &1 and &2 have the same description in language &3 |
| 424 | Related request field mapping &1/&2/&3/&4; |
| 425 | Related request field mapping &1/&2/&3 (freestyle): |
| 426 | Key of related request field mapping is not fully specified |
| 427 | Related request &1/&2/&3/&4 does not exist |
| 428 | Object type &1, node &2, request &3, request field &4 does not exist |
| 429 | Response field must be freestyle or assigned to a request field |
| 430 | Response field is used in related request field mapping &1/&2/&3/&4 |
| 431 | Response field is used in related req. field mapping &1/&2/&3 (freest.) |
| 432 | Request field is used in related request field mapping &1/&2/&3/&4 |
| 433 | Related request texts: Node type id &1, request &2/&3, lanugage &4 |
| 434 | Related request &1/&2&/&3/&4 is not provided |
| 435 | Related request field mappings: Node type id &1, mapping &2/&3/&4 |
| 436 | Fixed value definition of related request &1/&2/&3/&4: |
| 437 | Key of related request was not fully specified |
| 438 | Related request &1/&2/&3/&4 does not exist |
| 439 | Related request fixed valued definition: Key is not fully specified |
| 440 | Related request field is initial |
| 441 | Related request field &1/&2/&3/&4 is already assigned to a response field |
| 442 | Related request field &1/&2/&3/&4 is already given fixed values |
| 443 | Request field is used in fixed values def. of related request &1/&2/&3/&4 |
| 444 | Response field &3 of object type &1, node &2 does not exist |
| 445 | The response field used in a related request field mapping does not exist |
| 446 | Request field &4 of object type &1, node &2, request &3 does not exist |
| 447 | The request field used in a related request field mapping does not exist |
| 448 | Field is referenced in related request field mapping &1/&2/&3/&4 |
| 449 | Field is referenced in related request field mapping &1/&2/&3/&4 |
| 450 | Request field &4 of object type &1, node &2, request &3 does not exist |
| 451 | The request field used in a related req. fixed value def. does not exist |
| 452 | Field is referenced in fixed value def. of related request &1/&2/&3/&4 |
| 453 | Cannot delete request field |
| 454 | Related perspective fixed values: Node type id &1, values for &2/&3/&4 |
| 455 | Related request fixed values: Node type id &1, values for &2/&3/&4 |
| 456 | Request &3 does not reference all keyfields of node &2 |
| 457 | Mapping numbers greater than &1 are reserved for special use |
| 458 | Related request &1/&2/&3/&4: |
| 459 | Field mapping resp. fld. &1 <-> rel. request field &2 already exists |
| 460 | Response field &1 is already flagged for freestyle search |
| 461 | Value is incompatible with type of node request field |
| 462 | Types of response field &1 and request field &2 are incompatible |
| 463 | Types of response field &1 and request field &2 are incompatible |
| 464 | Horizontal size must be positive |
| 465 | Vertical size must be positive |
| 466 | Data provider &1 cannot be direct accessible |
| 467 | Table &1 does not exist or has status "New" |
| 468 | Error when checking existence of table &1 |
| 469 | &1 must be a transparent table |
| 470 | Node name contains slashes that do not indicate a namespace |
| 471 | No field of the default request is flagged for freestyle search |
| 472 | The root node must not have a parent node |
| 473 | Object type &1 has no root node |
| 474 | Data provider is direct accessible but no database table is specified |
| 475 | Object type is direct accessible but has an extraction implementation |
| 476 | Flag "Contains Text" is ignored in connectors created on a HANA Data Base |
| 477 | The related perspective has no field mapping or fixed value definiton |
| 478 | Navigation ID &1 has been flagged as object link |
| 479 | Request field &4 does not belong to object type &1, node &2, request &3 |
| 480 | Node &2 has no response fields but is flagged for subquery |
| 481 | Object type &1 (software component &2) is already predecessor of &3 |
| 482 | Object type GUID &2 (software component &1) is already a predecessor |
| 483 | Object type GUID &2 (software component GUID &1) is already a predecessor |
| 484 | Object type &1, predecessor: software component &2, object type &3 |
| 485 | Object type is initial |
| 486 | Predecessor software component (PSWC) and PSWC-GUID are initial |
| 487 | Software component of predecessor object type is initial |
| 488 | Predecessor object type and predecessor object type GUID are initial |
| 489 | Predecessor software component &1 does not exist |
| 490 | Predecessor object type &2 from software component &1 does not exist |
| 491 | Object type &1 is used as predecessor of object type &3 from SWC&2 |
| 492 | Object type &1 has more than one successors |
| 493 | The predecesor relations starting at object type &1 are circular |
| 494 | Only business templates or virtual templates may have predecessors |
| 495 | Navigation id &1 must start with &2 |
| 496 | Navigation id &1 must not start with &2 |
| 497 | Error when checking table in DDIC |
| 498 | Table &1 does not exist or has status "New" |
| 499 | Table &1 is a pool-/cluster table but data provider is not flagged |
| 500 | Table &1 is no pool-/cluster table but data provider is flagged |
| 501 | Response field is used in backend navigation field ass. &1/&2/&3/&4 |
| 502 | Attribute &1 has a fulltext index defined in DDIC |
| 503 | No data provider of object type &1 is based on a pool-/cluster table |
| 504 | Data provider &2 is not based on pool-/cluster table |
| 505 | &1 is no database table but data provider &1 is flagged for pool/cluster |
| 506 | Authorization check cannot be assigned to node &2 |
| 507 | Filter conditions are not valid |
| 508 | Node &1 cannot be used in path of authorization check &2 |
| 509 | Field &3 of node &2 of object type &1 must be flagged to contain text |
| 510 | XML-error at row &1, column &2 |
| 511 | Rendering template is initial |
| 512 | &1 |
| 513 | You cannot enter &1 because &1 is a reserved keyword |
| 514 | Key field &3 of node &2 of object type &1 cannot used in field mapping |
| 515 | Key field &4 cannot have semantics "Language Code" |
| 516 | Key field &4 cannot have semantics "Language Code" |
| 517 | Field &3 cannot be flagged to "Contain text" |
| 518 | Field &4 cannot be flagged to "Contain text" |
| 519 | Update/reset node cannot be executed |
| 520 | It is not possible to change the node of attribute group &1 |
| 521 | Inactive or active storage could not be instantiated -> no where used |
| 522 | Stack of software component &1 is inconsistent -> where used not possible |
| 523 | Technical model &1 could not be generated |
| 524 | Technical model &1 generated and linked to node &2 |
| 525 | No technical model could be generated for node &1 |
| 526 | Default request does not reference key field &3 (object type &1, node &2) |
| 527 | Field &3 of node &2 is not referenced in a response field node &2 |
| 528 | Default request does not reference all key fields of node &2 |
| 529 | SAP System is currently locked as upgrade is in progress |
| 530 | A response attribute and an attribute group have the same name (&3) |
| 531 | Could not resolve GUID &1 (&2) - maybe generated program is missing |
| 532 | Could not fully resolve GUID &1 (&2) because GUID &3 (&4) is unknown |
| 533 | It is not possible to enhance object type &1 |
| 534 | It is not possible to enhance data type &1 |
| 535 | It is not possible to enhance relation &1 |
| 536 | It is not possible to enhance authorization check &1 |
| 537 | It is not possible to enhance navigation path id &1 |
| 538 | Software comoponent &1 is a basis software component: cannot be enhanced |
| 539 | Source client identical to target client |
| 540 | Error creating table of type &1 |
| 541 | Error inserting into table &1 |
| 542 | Error updating model import log |
| 543 | Generic update allowed from source client 000 only |
| 544 | Renaming not possible because of GTABKEY registration |
| 545 | New entry not possible because of GTABKEY registration |
| 546 | No message specified - inform SAP |
| 547 | Object type &1, node &2, request attribute group &3, ref. attr. group &4 |
| 548 | Object type &1, node &2, attribute group &3, ref. attribute group &4: |
| 549 | Object_type &1, node &2, ODP/semantics &3, field &4 |
| 550 | Object type &1, node &2, request/field &3, common attribute &4 |
| 551 | Assignment of field &4 to object type &1, node &2, request/attr. group &3 |
| 552 | Object type &1, node &2, UI type/navigation id &3, field &4 |
| 553 | Source field &1, target field &2 |
| 554 | Software component usage: Including SWC &2 in SWC &1 |
| 555 | Predecessor object type &1 does not exist |
| 556 | Data provider &1, filter &2, ref. data prov./field &3, counter &4 |
| 557 | Data provider &1, attribute group &2 |
| 558 | Data provider &1: usage of attribute group &2 in attribute group &3 |
| 559 | Renaming not possible because of GTABKEY registration |
| 560 | New entry not possible because of GTABKEY registration |
| 561 | Renaming not possible because of GTABKEY registration |
| 562 | New entry not possible because of GTABKEY registration |
| 563 | Renaming not possible because of GTABKEY registration |
| 564 | New entry not possible because of GTABKEY registration |
| 565 | Field assignment of authorization check &1, authorization field &2 |
| 566 | Fixed value defintion: authorization check &1, field &2, counter &3 |
| 567 | Assignment of switch id &1 to: |
| 568 | System software component cannot be assigned due to GTABKEY registration |
| 569 | New entry not possible because of GTABKEY registration |
| 570 | Wrong call of RECORD_GTABKEY_REGISTRATIONS - inform SAP |
| 571 | Entry can't be registered because there is already a GTABKEY registration |
| 572 | Category cannot be assigned to SWC &1 due to GTABKEY registration |
| 573 | GTABKEY-registration: user &1, transport request &2 |
| 574 | GTABKEY-registration: user &1 |
| 575 | GTABKEY-registration: transport request &2 |
| 576 | Common attribute &1: |
| 577 | Common attr. cannot be assigned to SWC &1 due to GTABKEY registration |
| 578 | Error during save (&1) because of change of GTABKEY-registration |
| 579 | Error during save because of change of GTABKEY-registration |
| 580 | Software component &1 already exists in another system (&2) |
| 581 | System software component &2 of software component &1 cannot be changed |
| 582 | Software component &1 cannot be renamed to &3 |
| 583 | Wrong call of method &1 - inform SAP |
| 584 | Error when accessing the GTABKEY server: |
| 585 | Change of data not allowed due to GTABKEY registrations - inform SAP |
| 586 | More than one filed has semantics "Content URL" |
| 587 | More than one filed has semantics "Searchable file |
| 588 | Only one field can have semantics "Content URL" or "Searchable file |
| 589 | Only one field can have semantics "Content URL" or "Searchable file |
| 590 | Category &1 cannot be assigned to object type &2 |
| 591 | Default request &1 cannot be flagged to be internal |
| 592 | Object type &1 has internal default request and categories assigned |
| 593 | Node field &1 cannot be a key field because it is of type &2 (string) |
| 594 | Data type &1 cannot have type &1 (string) as it's used in the key fields: |
| 595 | Software component &1 needs included software component &2 |
| 596 | Ranking factor &1 already exists |
| 597 | Ranking factor &1 |
| 598 | Ranking factor is initial |
| 599 | Old software component &2 was registered for transport |
| 600 | New software component &2 is not registered for transport |
| 601 | Ranking factor &1 is in customer namespace (&2) |
| 602 | Ranking factor &1 has to start with &2 in customer systems |
| 603 | Ranking factor &1 contains forbidden chararcters |
| 604 | Description for ranking factor &1, language &2: |
| 605 | Key of ranking factor description is not fully specified |
| 606 | Ranking factor is initial |
| 607 | Object type &1, node &2, request &3, ranking factor &4 |
| 608 | Assignment of ranking factor attribute to request field &1 |
| 609 | Key of ranking factor assignment or request is not fully specified |
| 610 | Ranking factor &1 for application object type id &2 does not exist |
| 611 | Common attribute &1 is assigned to softw. comp. &2 and cannot be deleted |
| 612 | Ranking factor &1, attribute &2 already exists |
| 613 | Key of mapping req. fld - rank. factors attribute is not fully specified |
| 614 | Object type &1, node &2, requ. &3, ranking factor &4 does not exist |
| 615 | Object type &1, node &2, requ. &3, assgn. to rank.fact. &4 already exists |
| 616 | Mapping request field - ranking factor attribute &1 already exists |
| 617 | Object type &1 already existed or exists in another system/client |
| 618 | Object type &1 is equivalent to object type &2 in another system/client |
| 619 | The corresponding transport request is &1 |
| 620 | Software component &1 already existed or exists in another system/client |
| 621 | Softw. comp. &1 is equivalent to softw. comp. &2 in another system/client |
| 622 | Common attribute &1 already existed or exists in another system/client |
| 623 | Common attr. &1 is equivalent to common attr. &2 in another system/client |
| 624 | Category &1 already existed or exists in another system/client |
| 625 | Category &1 is equivalent to category &2 in another system/client |
| 626 | Model content update; this can take up to half an hour |
| 627 | A composition cannot be changed into an assoziation |
| 628 | An assoziation cannot be changed to a composition |
| 629 | Source node or the target node of a composition cannot be changed |
| 630 | SWC &1 not fetched; reason: |
| 631 | &1 not fetched: ABAP-SWC &2 is set as editable |
| 632 | &1 not fetched: SP-level unchanged, no update by transports |
| 633 | &1 not fetched: TABU-transport not relevant any more |
| 634 | &1 not fetched: Model data is up to date |
| 635 | SWC &1 is updated |
| 636 | &1 fetched: Initial import (ABAP-SWC &2) |
| 637 | No import for ABAP-SWC &1; reason: |
| 638 | &1 fetched: Import because of new SP (ABAP-SWC &2) |
| 639 | No ES-SWC exists |
| 640 | GTABKEY-registration: original system(client) of registration &1 |
| 641 | GTABKEY-registration: user &1, original system(client) of registration &2 |
| 642 | The corresponding original system(client) of registration is &1 |
| 643 | Ranking factor &1 for application object type id &2 already exists |
| 644 | Rank. factor &1 for appl. obj. type id &2, attribute &3 already exists |
| 645 | Ranking factor &1 for application object type id &2 |
| 646 | Description ranking factor &1 for appl. object type id &2, language &3 |
| 647 | Object type &1, node &2, request &3, rank. fact. for appl. object type &4 |
| 648 | Ranking factor &1 does not exist |
| 649 | Object type &1, node &2, requ. &3, assgn. to rank.fact. &4 already exists |
| 650 | Key of ranking factor attribute is not fully specified |
| 651 | Text ranking factors must not have attributes |
| 652 | Ranking factor &1 for application object type id &2, attribute &3 |
| 653 | Ranking factor &1, attribute &2 |
| 654 | Object type &1, node &2, requ. &3, ranking factor &4 does not exist |
| 655 | Stack of software component &1 is inconsistent -> where used not possible |
| 656 | Inactive or active storage could not be instantiated -> no where used |
| 657 | Ranking factor &1 |
| 658 | Cannot delete ranking factor |
| 659 | Rank. fact. is assigned to object type/node/request &1 of softw. comp. &2 |
| 660 | Ranking factor is already assigned to a globally-defined object type |
| 661 | Cannot delete ranking factor attribute |
| 662 | Rank. fact. is assigned to object type/node/request &1 of softw. comp. &2 |
| 663 | Category &1 does not have an owning software component |
| 664 | The ranking factor must have an owning software component |
| 665 | Owning SWC for ranking factor has no system software component |
| 666 | Owning SC for ranking factor &1 has no system software comp. |
| 667 | Owning SC for ranking factor/appl. object type id &1 has no system SC |
| 668 | Ranking factor is assigned to softw. comp. &1 and cannot be deleted |
| 669 | Mapping request field - ranking factor attribute &1 |
| 670 | Ranking factor &1 for object type &2 is not assigned to request &4 |
| 671 | Ranking factor &1 is not assigned to request &3 |
| 672 | The ranking factor attribute is not specified |
| 673 | Ranking factor &1, attribute &2 does not exist |
| 674 | Ranking fact. &1 for appl. object type id &2, attribute &3 does not exist |
| 675 | Assignment of ranking factor to request field &1 |
| 676 | Attribute is assigned to object type/node/requ./fld &1 of softw. comp. &2 |
| 677 | Not all key fields of node &1 are referenced in response fields |
| 678 | Ranking factor is &1 and Application object type is &2 simultaneously |
| 679 | Rannk. factor cannot be assigned to SWC &1 due to GTABKEY registration |
| 680 | Rank. factor assignmnts: Node type ID &1, request ID &2, rank. fact. &3 |
| 681 | Rank. fact. assignmnts: Node type ID &1, request ID &2, rank. fact. &3,.. |
| 682 | Attribute mapping for ranking factor assignment |
| 683 | Node type ID &1, request ID &2, rank. factor &3, request field ID &4 |
| 684 | Node type ID &1, request ID &2, rank. factor / appl. object type ID &3 .. |
| 685 | Node type ID &1, request ID &2, rank. factor &3 is not provided |
| 686 | Node type ID &1, request ID &2, rank. fact. &3, object &4 is not provided |
| 687 | Software component texts: Software component &1, language &2 |
| 688 | No attribute of the ranking factor is assigned to a request field |
| 689 | No attribute of the ranking factor is assigned to a request field |
| 690 | Ranking factor attributes are assigned to more than one request field |
| 691 | No authorization fields are mapped to node fields or constants |
| 692 | Ranking factor attributes are assigned to more than one request field |
| 693 | Ranking factor attributes are assigned to more than one request field |
| 694 | Ranking factor attribute &1 references more than one request field |
| 695 | Could not find object type id &1, node id &2 referenced in virtual model |
| 696 | Not all ranking factor attributes are assigned to a request field |
| 697 | Not all ranking factor attributes are assigned to a request field |
| 698 | Ranking factor attribute &1 is not mapped to a request field |
| 699 | Adjust the ranking factor attribute mapping of model &1 |
| 700 | Reverse/source cardinality "&3" does not fit to foreign key definitions |
| 701 | Reverse/source cardinality "&3" does not fit to foreign key definitions |
| 702 | Cardinality "&3" does not fit to foreign key definitions |
| 703 | Cardinality "&3" does not fit to foreign key definitions |
| 704 | Cardinality "&3" does not fit to foreign key definitions |
| 705 | Cardinality "&3" does not fit to foreign key definitions |
| 706 | Semantic object type is not specified - No navigation possible |
| 707 | There is no response field with a semantic object type |
| 708 | Maintenance type &1 does not exist |
| 709 | Maintenance type is inital |
| 710 | Personalized search provider is not specified |
| 711 | Personalized search provider &1 does not implement interface &2 |
| 712 | Object type &1 has no semantic object type |
| 713 | Wrong call of method CL_ESH_OM_GREPL_WORKPLAN=>UPDATE_WORKPLAN |
| 714 | Ranking factor &1 has no attributes |
| 715 | Ranking factor &1 for application object type &2 has no attributes |
| 716 | Ranking factor &1 must have an application object type |
| 717 | Ranking factor &1 must have an application object type |
| 718 | Ranking factor = &1 and application object type id =&2 is not possible |
| 719 | Ranking factor attribute &1 is no parameter for dynamic ranking |
| 720 | Method &3: Sysrel_guid mismatch - Inform SAP (&1,&2) |
| 721 | Connector of object type &1 for system &2 is assigned to the rank. factor |
| 722 | Error occurred when deleting boost data |
| 723 | Application object type &1 contains forbidden characters |
| 724 | Ranking factor attribute &1 contains forbidden characters |
| 725 | Ranking factor &1, user &2, boost guid &3 |
| 726 | Ranking factor &1, appl. object type &2, user &3, boost guid &4 |
| 727 | Key of boost is not fully specified |
| 728 | Ranking factor &1, user &2, boost guid &3 already exists |
| 729 | Rank. fact. &1 for obj. type id &2, user &3, boost guid &4 already exists |
| 730 | Boost condition &1 (no user) |
| 731 | Ranking factor boost condition &1 |
| 732 | Boost condition &1 (no user) |
| 733 | Boost condition &1 |
| 734 | Key of boost condition is not fully specified |
| 735 | Ranking factor &1, boost guid &2 |
| 736 | Ranking factor &1, appl. object type &2, boost guid &3 |
| 737 | Rnking factor &1, user &2, boost guid &3, does not exist |
| 738 | Rank. fact. &1/appl. object type &2/user &3/boost guid &4 does not exist |
| 739 | Ranking factor &1, boost guid &2, does not exist |
| 740 | Ranking factor &1, appl. object type &2, boost guid &3 does not exist |
| 741 | RDIMSS_GUID is initial |
| 742 | Ranking factor &1: attribute &2 cannot be assigned |
| 743 | Rank. fact. &1 for appl. object type &2: attribute &3 cannot be assigned |
| 744 | Boost must have at least one condition that is not initial |
| 745 | SIGN, OPT and LOW or HIGH must be filled |
| 746 | Boost condition &1 (no user) already exists |
| 747 | Boost condition &1 already exists |
| 748 | Boost condition &1 (no user) already exists |
| 749 | Boost condition &1 already exists |
| 750 | Boost condition &1 (no user), condition guid &2 already exists |
| 751 | Boost condition &1, condition guid &2 already exists |
| 752 | Boost condition &1 (no user), selection &2 already exists |
| 753 | Boost condition &1, condition guid &2 already exists |
| 754 | Where-used request for categories could not be executed |
| 755 | Stack of software component &1 is damaged |
| 756 | Where-used request for ranking factors could not be executed |
| 757 | Where-used request for common attributes could not be executed |
| 758 | Model &1 in area &2 could not be instantiated |
| 759 | Where-used request for ranking factor attributes could not be executed |
| 760 | Attribute &1 can only act as constraint if it is a parameter |
| 761 | All attributes of ranking factor &1 act as constraint |
| 762 | All attributes of rank. fact. &1 for object type id &2 act as constraint |
| 763 | Attribute is assigned to object type &1, node &2, request &3, field &4 |
| 764 | The ranking factor attribute cannot act as constraint |
| 765 | The ranking factor attribute cannot act as constraint |
| 766 | The attribute is assigned to request fields of software component &1: |
| 767 | The attribute is assigned to the following request fields: |
| 768 | Ranking factor attribute &2 cannot be assigned as it acts as constraint |
| 769 | Ranking factor attribute &3 cannot be assigned as it acts as constraint |
| 770 | Software component &1 cannot be chosen - see note 2233630 |
| 771 | Parallel process for fetching the meta data is running |
| 772 | Not all backend navigations with navigation id &1 are an object link |
| 773 | Navigation targets of object type &1, node &2: |
| 774 | Object type &1, node &2: no response field uses node key field &3 |
| 775 | Object type &1 cannot be used in multi selections |
| 776 | Request field &1 cannot be assigned because it is of type &2 |
| 777 | Request field &2 is referenced in ranking factor field mapping &1 |
| 778 | Request field &2 is referenced in ranking factor field mapping &1 |
| 779 | Node field &1 cannot be assigned to request field &2 as it is of type &3 |
| 780 | Node field is assigned to object type &1, node &2, request &3, field &4 |
| 781 | Node field &3 (object type &1, node &2) cannot be of type &4 |
| 782 | Request field &1 has type &2: Searches using the request field will fail |
| 783 | Request field is assigned to a ranking factor attribute in the cockpit |
| 784 | Could not resolve GUID &1 (&2) - report data inconsistent |
| 785 | Replacing CDS-entities are in preparation |
| 786 | Ranking factor &1 is assigned to package '$TMP' |
| 787 | Ranking factor &1 (appl. object type &2) is assigned to package '$ |
| 788 | Data type &1 must begin with &2. This cannot be changed. |
| 789 | Attribute mapping does not exist for ranking factor attribute &1 |
| 790 | Rename not possible - delete and recreate entry (&1) |
| 791 | Error when checking compatibility of packages |
| 792 | Package cannot be changed from &1 to &2 |
| 793 | Paramter &1 cannot be used in the ranking factor |
| 794 | Ranking factor scale definition &1 contains forbidden characters |
| 795 | Parameter &1 has no package assignment |
| 796 | The ranking factor cannot be given a package |
| 797 | Ranking factor &1 for application object type id &2, scale &3 |
| 798 | Ranking factor &1, scale &2 |
| 799 | Key of ranking factor scale is not fully specified |
| 800 | Usage type is initial |
| 801 | Usage type &1 does not exist |
| 802 | Scale type is initial |
| 803 | Scale type &1 does not exist |
| 804 | Function type of scale definition is initial |
| 805 | Function type of scale definition &1 does not exist |
| 806 | The attribute is used in the scale definition (&1) |
| 807 | The scale cannot be added as a ranking factor can only have one scale |
| 808 | ranking factor &1, scale definition &2 already exists |
| 809 | Ranking factor &1 for appl. obj. type id &2, scale &3 already exists |
| 810 | The ranking factor can only have up to one scale definition |
| 811 | &1 = &4 : The condition "&3" is violated (&2) |
| 812 | Parameter &1 must not be filled |
| 813 | Could not start report &1 to adjust runtime storage of ranking factors |
| 814 | Adjust runtime storage of ranking factors - START - |
| 815 | Adjust runtime storage of ranking factors - END - |
| 816 | Runtime storage for ranking factors successfully updated |
| 817 | Ranking factors: System failure during lock |
| 818 | Ranking factors have been locked by user &2 |
| 819 | Enterprise Search repository is corrupt (Reason &1) |
| 820 | New execution of report scheduled in &1 seconds |
| 821 | No ranking factors to be processed |
| 822 | Could not lock storages |
| 823 | Personalized search provider &1 cannot be used in the ranking factor |
| 824 | Adjust runtime buffer - START - |
| 825 | Adjust runtime buffer - END - |
| 826 | Runtime buffer successfully updated |
| 827 | Could not schedule report &1 again |
| 828 | Nothing to do |
| 829 | Could not start report &1 to adjust runtime buffer |
| 830 | Error(s) occurred during adjustment of runtime storage |
| 831 | Field RDIMS_GUID contains no GUID |
| 832 | Ranking factor is assigned to CDS-entity &1 |
| 833 | Ranking factor attribute is assigned to CDS-Entit�t &1, element &2 |
| 834 | Connector &1 cannot be enhanced |
| 835 | It is not allowed to set the COMMIT flag |
| 836 | Response field &1 is newly referenced in the following objects: |
| 837 | Request field &1 is newly referenced in the following objects: |
| 838 | Switch id &1 |
| 839 | Related request field mapping &1/&2/&3/&4 |
| 840 | Related request field mapping &1/&2/&3 (freestyle) |
| 841 | Fixed value definition of related request &1/&2/&3/&4 |
| 842 | Related perspective field mapping &1/&2/&3/&4 |
| 843 | Related perspective field mapping &1/&2/&3 (freestyle) |
| 844 | Response field &1 has been newly enhanced with the following objects: |
| 845 | Request field &1 has been newly enhanced with the following objects: |
| 846 | &1: Model &2 exists already |
| 847 | Dimension key &1 does not exist |
| 848 | Unit of measure &1 does not exist |
| 849 | Unit of measure &1 of using scale &2 does not exist |
| 850 | The attribute is of dimension &1 but scale &2 is of dimension &4 (uom &3) |
| 851 | Attribute &1 has no dimension but scale &2 is of dimension &4 (uom &3) |
| 852 | Attribute &1 is of dimension &2 with SI-unit &3 but scale &4 has no uom |
| 853 | Dimension key &1 of refrenced attribute &2 does not exist |
| 854 | The scale is of dimension &4 (uom &3) but attribute &1 is of dimension &2 |
| 855 | The scale is of dimension &3 (uom &2) but attribute &1 has no dimension |
| 856 | The scale has no uom but attribute &1 is of dimension &2 with si-unit &3 |
| 857 | Node &1 has no parent node - maybe relation report missing |
| 858 | ES-Modeler Semantics &1: Use customer name space (V*/W*/Y*/Z*) |
| 859 | ES-Modeler Semantics &1: Must not be in customer name space (V*/W*/Y*/Z*) |
| 860 | Ranking factor is assigned to meta data extension &2 cds entity &1 |
| 861 | Ranking factor is assigned to cds entity &1 |
| 862 | Response field name &1 cannot be used here |
| 863 | Not all key fields of node &2 are referenced in the nodes response fields |
| 864 | Not all key fields of node &1 are referenced in a request of the node |
| 865 | Software component &1 cannot be assigned to the ranking factor |
| 866 | Package of software component &1 cannot be changed |
| 867 | Node field &1 (key field) is not referenced in a response field |
| 868 | Node field &1 (key field) is not referenced in a request field |
| 869 | The ranking weight must be between &1 and &2 |
| 870 | An inherited logical conjuntion cannot be deleted |
| 871 | The software component stack is corrupt (Reason &1) |
| 872 | Model repository: Fundamental tables are empty |
| 873 | Model repository: The software component stack is corrupt |
| 874 | Error during renaming of object types because of GTABKEY registration |
| 875 | Inconsistent state in &1 (&2) |
| 876 | Using software component: &1 |
| 877 | Used software component: &1 |
| 878 | GUID of using software component: &1 |
| 879 | GUID of used software component: &1 |
| 880 | Labels are limited to &1 language codes: &2 |
| 881 | Language code &1 could not be interpreted |
| 882 | No language limitations configured |
| 883 | &1 valid language limitation(s) configured: &2 |
| 884 | &1 valid language limitation(s) configured |
| 885 | There must be no more than one field of type &1 or &2 |
| 886 | Model data is currently being fetched from another client |
| 887 | Ranking factors could be locked in the &2. trial (area &1) |
| 888 | Locking of ranking factors finally terminated after &2 trials (area &1) |
| 889 | Condition "&1" is violated: |
| 890 | &1 = &2 |
| 891 | Object types &1 and &2 have the same plural description in language &3 |
| 892 | Language code &1 is not installed |
| 893 | Request field cannot be flagged as a facet because it is of type &1 |
| 894 | The data type cannot have type &1 as it is used in the following facets: |
| 895 | The node field cannot have type &1 as it is used in the following facets: |
| 896 | Manual boost maitenance mode &1 does not exist |
| 897 | The ranking factor cannot be 'Maintenance only by customer' |
| 898 | Association id &1 ( &2 to &3 ): |
| 899 | Field &3 of node &2 (model &1) can have no fixed value as it has type &4 |