SAP ABAP Message Class ESH_OM_OBJ_MODEL_RP2 (Messages for Object Model Repository)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search
⤷
S_ESH_ENG_OBJ_MOD_REP (Package) Model Repository
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-EIM-ESH (Application Component) NetWeaver Enterprise Search⤷
S_ESH_ENG_OBJ_MOD_REP (Package) Model Repository 
Attributes
| Message class |  |
ESH_OM_OBJ_MODEL_RP2 |
| Short Description |  |
Messages for Object Model Repository |
| Changed On |  |
20141121 |
| Last Changed At |  |
124012 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 |  001 |
Data provider &1, attribute group &2 does not exist | The short text describes the object sufficiently | |
| 2 | 002 |
Data provider &1, attribute group &2, language &3: | The short text describes the object sufficiently | |
| 3 | 003 |
Attribute group &1 does not exist | The short text describes the object sufficiently | |
| 4 | 004 |
Assignment of data provider &1, field &3 to attribute group &2 | The short text describes the object sufficiently | |
| 5 | 005 |
Data provider &1, field &2 does not exist | The short text describes the object sufficiently | |
| 6 | 006 |
Data provider &1, attribute group &2: | The short text describes the object sufficiently | |
| 7 | 007 |
Hierarchy of attribute groups contains a loop | The short text describes the object sufficiently | |
| 8 | 008 |
Data provider &1, attribute group &2 already exists | The short text describes the object sufficiently | |
| 9 | 009 |
Field &3 is already assigned to data provider &1, atrribute group &2 | The short text describes the object sufficiently | |
| 10 | 010 |
Attribute group &3 is already used data provider &1,attribute group &2 | The short text describes the object sufficiently | |
| 11 | 011 |
Description already exists in language &3 | Space: object requires documentation | |
| 12 | 012 |
Node attribute groups: Node type ID &1, attribute group &2 | The short text describes the object sufficiently | |
| 13 | 013 |
Node attribute group texts: Node type ID &1, attr. group &2, language &3 | The short text describes the object sufficiently | |
| 14 | 014 |
Node type ID &1, node attribute group &2 is not provided | The short text describes the object sufficiently | |
| 15 | 015 |
Node attribute group fields: Node type ID &1, group ID &2, field &3 | The short text describes the object sufficiently | |
| 16 | 016 |
Parent node attribute group &1 is not provided | The short text describes the object sufficiently | |
| 17 | 017 |
Response attribute groups: Node type ID &1, attribute group &2 | The short text describes the object sufficiently | |
| 18 | 018 |
Parent response attribute group &1 is not provided | The short text describes the object sufficiently | |
| 19 | 019 |
Resp. attribute group texts: Node type ID &1, attr. group &2, language &3 | The short text describes the object sufficiently | |
| 20 | 020 |
Node type ID &1, response attribute group &2 is not provided | The short text describes the object sufficiently | |
| 21 | 021 |
Request attribute groups: Node type ID &1, request ID &2, group &3 | The short text describes the object sufficiently | |
| 22 | 022 |
Parent request attribute group &1 is not provided | The short text describes the object sufficiently | |
| 23 | 023 |
Response attribute group texts: | The short text describes the object sufficiently | |
| 24 | 024 |
Node type ID &1, request &2, attribute group &3, language &4 | The short text describes the object sufficiently | |
| 25 | 025 |
Node type ID &1, request &2,attribute group &3 is not provided | The short text describes the object sufficiently | |
| 26 | 026 |
Response attribute group fields: Node type ID &1, group ID &2, field &3 | The short text describes the object sufficiently | |
| 27 | 027 |
Response attribute group fields: | The short text describes the object sufficiently | |
| 28 | 028 |
Node type ID &1, request &2, attibute group ID &3, field &4 | The short text describes the object sufficiently | |
| 29 | 029 |
Response field texts: Node type &1, field &2, language &3 | The short text describes the object sufficiently | |
| 30 | 030 |
Node type ID &1, response field ID &2 is not provided | The short text describes the object sufficiently | |
| 31 | 031 |
Only one field can have semantics "Searchable file" | The short text describes the object sufficiently | |
| 32 | 032 |
UI area &1 is not possible for response attribute groups | The short text describes the object sufficiently | |
| 33 | 033 |
Flag for interactive navigation belongs to request fields now | Space: object requires documentation | |
| 34 | 034 |
Flag for interactive navigation belongs to request fields now | Space: object requires documentation | |
| 35 | 035 |
Request attribute group texts: | The short text describes the object sufficiently | |
| 36 | 036 |
Request attribute group fields: | The short text describes the object sufficiently | |
| 37 | 037 |
Node &1 has fields with the same description | The short text describes the object sufficiently | |
| 38 | 038 |
Node &1 has response fields with the same description | The short text describes the object sufficiently | |
| 39 | 039 |
Request &1 has fields with the same description | The short text describes the object sufficiently | |
| 40 | 040 |
ODP ID &1, ODP semantics &2 has fields with the same description | The short text describes the object sufficiently | |
| 41 | 041 |
Field with semantic "Searchable File" must be of type RSTR (RAWSTRING) | Space: object requires documentation | |
| 42 | 042 |
Term not found | The short text describes the object sufficiently | |
| 43 | 043 |
Enter a search term | The short text describes the object sufficiently | |
| 44 | 044 |
Node &1 has no field with semantic "MIME Type" | Space: object requires documentation | |
| 45 | 045 |
Node &1 has an unpaired field with semantic "MIME Type" | Space: object requires documentation | |
| 46 | 046 |
Node &1 has no field with semantic "MIME Type" | Space: object requires documentation | |
| 47 | 047 |
Connectors of system software component &1 cannot be created | Space: object requires documentation | |
| 48 | 048 |
ODP ID &1, ODP semantics &2 has fields with the same description | The short text describes the object sufficiently | |
| 49 | 049 |
Data type &1 is not used in area &2 (model &3, sysrel. &4) | The short text describes the object sufficiently | |
| 50 | 050 |
Attribute group &1 does not contain fields or other attribute groups | The short text describes the object sufficiently | |
| 51 | 051 |
No field of the attribute group is assigned to UI area &1 | Space: object requires documentation | |
| 52 | 052 |
Connector for model &1 already exists and is up-to-date | The short text describes the object sufficiently | |
| 53 | 053 |
Flag "Based on BW Data Sources" cannot be changed | Space: object requires documentation | |
| 54 | 054 |
Node &1 should not have response fields with UI area assignments | Space: object requires documentation | |
| 55 | 055 |
Response attribute group areas: Node type ID &1, group ID &2, UI area &3 | The short text describes the object sufficiently | |
| 56 | 056 |
Navigation path of object type &1, node &2, response field &3: | The short text describes the object sufficiently | |
| 57 | 057 |
Navigation path of object type &1, node &2, request &3, field &4: | The short text describes the object sufficiently | |
| 58 | 058 |
Navigation path of object type &1, node &2, ODP &3, field &4: | Space: object requires documentation | |
| 59 | 059 |
Navigation path of path-based authorization check &1: | The short text describes the object sufficiently | |
| 60 | 060 |
Navigation path for ABAP authorization check &1, authorization field &2: | The short text describes the object sufficiently | |
| 61 | 061 |
Node &1 has been updated successfully | The short text describes the object sufficiently | |
| 62 | 062 |
Node &1 has been reset successfully | The short text describes the object sufficiently | |
| 63 | 063 |
Object type &1 has been locked by user &2 | The short text describes the object sufficiently | |
| 64 | 064 |
Object type &1: System failure during lock | The short text describes the object sufficiently | |
| 65 | 065 |
Authorization checks are defined for the reference node | Space: object requires documentation | |
| 66 | 066 |
Authorization check &1 has been locked by user &2 | The short text describes the object sufficiently | |
| 67 | 067 |
Authorization check &1: System failure during lock | The short text describes the object sufficiently | |
| 68 | 068 |
Common attribute &1 is in customer namespace (&2) | The short text describes the object sufficiently | |
| 69 | 069 |
Common attribute &1 has to start with &2 in customer systems | The short text describes the object sufficiently | |
| 70 | 070 |
Common attribute &1 contains forbidden chararcters | Space: object requires documentation | |
| 71 | 071 |
Common attribute &1 must start with prefix &2 | Space: object requires documentation | |
| 72 | 072 |
Common attribute &1 must start with prefix &2 or &3 | Space: object requires documentation | |
| 73 | 073 |
Common attribute is initial | The short text describes the object sufficiently | |
| 74 | 074 |
Common attribute &1: | The short text describes the object sufficiently | |
| 75 | 075 |
Common attribute &1 has no superordinate software component | The short text describes the object sufficiently | |
| 76 | 076 |
Common attribute &1, language &2: | The short text describes the object sufficiently | |
| 77 | 077 |
Key of assignment to common attribute &1 is not fully specified | The short text describes the object sufficiently | |
| 78 | 078 |
Key of common attribute description is not fully specified | The short text describes the object sufficiently | |
| 79 | 079 |
Common attribute &1 does not exist | The short text describes the object sufficiently | |
| 80 | 080 |
Common attribute &1 already exists | The short text describes the object sufficiently | |
| 81 | 081 |
Assignment to common attribute &1 already exists | The short text describes the object sufficiently | |
| 82 | 082 |
The request field cannot be assigned to common attriubte &1 | Space: object requires documentation | |
| 83 | 083 |
Request &1 has fields with assignments to common attributes | Space: object requires documentation | |
| 84 | 084 |
Cannot delete common attribute | The short text describes the object sufficiently | |
| 85 | 085 |
Common attribute contains request fields of object type &1 in SWC &2 | Space: object requires documentation | |
| 86 | 086 |
Assignment of common attributes: Node type ID &1, request ID &2, ... | Space: object requires documentation | |
| 87 | 087 |
Common attributes: Common attribute ID &1: | The short text describes the object sufficiently | |
| 88 | 088 |
Common attribute texts: Common attribute ID &1, language &2: | The short text describes the object sufficiently | |
| 89 | 089 |
The software component contains object types with initial ID | The short text describes the object sufficiently | |
| 90 | 090 |
Object type &1 contains nodes with initial ID | The short text describes the object sufficiently | |
| 91 | 091 |
System failure during lock | The short text describes the object sufficiently | |
| 92 | 092 |
Request &3 of object type &1, node &2 is not a rational related request | Space: object requires documentation | |
| 93 | 093 |
Node &1 does not contain the necessary response fields for navigation | Space: object requires documentation | |
| 94 | 094 |
User &2 is editing content of software component &1 | The short text describes the object sufficiently | |
| 95 | 095 |
User &2 is editing content of system &1 | The short text describes the object sufficiently | |
| 96 | 096 |
Authorization object &1 has been locked by user &2 | The short text describes the object sufficiently | |
| 97 | 097 |
Authorization object &1: System failure during lock | The short text describes the object sufficiently | |
| 98 | 098 |
Data provider &1 has been locked by user &2 | The short text describes the object sufficiently | |
| 99 | 099 |
Data provider &1: System failure during lock | The short text describes the object sufficiently | |
| 100 | 100 |
Several users are editing content of software component &1 | The short text describes the object sufficiently | |
| 101 | 101 |
Several users are editing content of system &1 | The short text describes the object sufficiently | |
| 102 | 102 |
Referenced node field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 103 | 103 |
External references were deleted: | Space: object requires documentation | |
| 104 | 104 |
The referenced node field does not exist | Space: object requires documentation | |
| 105 | 105 |
External usages were created: | Space: object requires documentation | |
| 106 | 106 |
Relation &1 has been locked by user &2 | The short text describes the object sufficiently | |
| 107 | 107 |
Relation &1: System failure during lock | The short text describes the object sufficiently | |
| 108 | 108 |
Referenced node field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 109 | 109 |
Referenced node field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 110 | 110 |
Referenced authorization check &1 does not exist | Space: object requires documentation | |
| 111 | 111 |
Referenced node field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 112 | 112 |
The referenced node field does not exist | Space: object requires documentation | |
| 113 | 113 |
User &2 is saving their work in software component &1, try again later... | Space: object requires documentation | |
| 114 | 114 |
User &2 is saving their work in system &1, try again later... | Space: object requires documentation | |
| 115 | 115 |
Node is referenced in association &1 | The short text describes the object sufficiently | |
| 116 | 116 |
Referenced node &2 of object type &1 does not exist | Space: object requires documentation | |
| 117 | 117 |
The referenced node does not exist | The short text describes the object sufficiently | |
| 118 | 118 |
The common attribute contains request fields of incompatible types: | Space: object requires documentation | |
| 119 | 119 |
Referenced data provider &1 does not exist | Space: object requires documentation | |
| 120 | 120 |
The referenced data provider does not exist | Space: object requires documentation | |
| 121 | 121 |
The node where the path starts does not exist | The short text describes the object sufficiently | |
| 122 | 122 |
The node where the path ends does not exist | The short text describes the object sufficiently | |
| 123 | 123 |
Referenced filter &2 of data provider &1 does not exist | Space: object requires documentation | |
| 124 | 124 |
The referenced data provider filter does not exist | Space: object requires documentation | |
| 125 | 125 |
Node &2 of object type &1 that is used in the path does not exist | The short text describes the object sufficiently | |
| 126 | 126 |
A node that is used in the path does not exist | The short text describes the object sufficiently | |
| 127 | 127 |
Unexpected error during import of software component &1 | Space: object requires documentation | |
| 128 | 128 |
Node is referenced in navigation path of: | The short text describes the object sufficiently | |
| 129 | 129 |
Request &3 of object type &1, node &2 (related request) does not exist | Space: object requires documentation | |
| 130 | 130 |
The request that is used as a related request does not exist | The short text describes the object sufficiently | |
| 131 | 131 |
The request is used as a related request in object type &1, node &2 | Space: object requires documentation | |
| 132 | 132 |
Model node reference object type &1, node &2, does not exist | Space: object requires documentation | |
| 133 | 133 |
The model node reference does not exist | Space: object requires documentation | |
| 134 | 134 |
Node is referenced in virtual model &1 | The short text describes the object sufficiently | |
| 135 | 135 |
Assignment of authorization field &2 to a node field does not exist | Space: object requires documentation | |
| 136 | 136 |
The assignment of an authorization field to a node field does not exist | The short text describes the object sufficiently | |
| 137 | 137 |
Relation is referenced assignment of authorization check to a node: | The short text describes the object sufficiently | |
| 138 | 138 |
Referenced node field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 139 | 139 |
The referenced node field does not exist | Space: object requires documentation | |
| 140 | 140 |
Referenced authorization check &1 does not exist | Space: object requires documentation | |
| 141 | 141 |
The referenced authorization check does not exist | Space: object requires documentation | |
| 142 | 142 |
Referenced authorization object key &1 (auth. object &2) does not exist | Space: object requires documentation | |
| 143 | 143 |
The referenced authorization object key does not exist | Space: object requires documentation | |
| 144 | 144 |
The data provider filter is referenced in object type &1, node &2 | The short text describes the object sufficiently | |
| 145 | 145 |
Authorization check &1 has been created in the meantime | Space: object requires documentation | |
| 146 | 146 |
Authorization object key &1 has been created in the meantime | Space: object requires documentation | |
| 147 | 147 |
Data provider &1 has been created in the meantime | Space: object requires documentation | |
| 148 | 148 |
Referenced data type &1 does not exist | Space: object requires documentation | |
| 149 | 149 |
The referenced data type does not exist | Space: object requires documentation | |
| 150 | 150 |
Referenced data type &1 does not exist | Space: object requires documentation | |
| 151 | 151 |
The referenced data type does not exist | Space: object requires documentation | |
| 152 | 152 |
Data provider &1 has been deleted in the meantime | The short text describes the object sufficiently | |
| 153 | 153 |
Authorization check &1 has been deleted in the meantime | The short text describes the object sufficiently | |
| 154 | 154 |
Referenced category &1 does not exist | Space: object requires documentation | |
| 155 | 155 |
The referenced category does not exist | Space: object requires documentation | |
| 156 | 156 |
Common attribute &1 does not exist | Space: object requires documentation | |
| 157 | 157 |
The common attribute does not exist | Space: object requires documentation | |
| 158 | 158 |
Categories have been locked by user &2 | Space: object requires documentation | |
| 159 | 159 |
Categories: System failure during lock | Space: object requires documentation | |
| 160 | 160 |
Common attributes: System failure during lock | Space: object requires documentation | |
| 161 | 161 |
Common attributes have been locked by user &2 | Space: object requires documentation | |
| 162 | 162 |
Common attribute contains request fields of globally-defined SWC | The short text describes the object sufficiently | |
| 163 | 163 |
Category is the parent of a globally-defined category | The short text describes the object sufficiently | |
| 164 | 164 |
ODP is used in ODP field &4 of object type &1, node &2, ODP &3 | Space: object requires documentation | |
| 165 | 165 |
Association &1 that is used in the path does not exist | The short text describes the object sufficiently | |
| 166 | 166 |
Composition from node &1 to node &2 in object type &3 does not exist | The short text describes the object sufficiently | |
| 167 | 167 |
A relation that is used in the path does not exist | The short text describes the object sufficiently | |
| 168 | 168 |
Field &3 of authorization object key &1 (auth. object &2) does not exist | The short text describes the object sufficiently | |
| 169 | 169 |
The referenced authorization object field does not exist | The short text describes the object sufficiently | |
| 170 | 170 |
Error when creating hash code for effective authorization checks | Space: object requires documentation | |
| 171 | 171 |
Node &3 of object type &2 cannot be deleted as user &1 locks associations | Space: object requires documentation | |
| 172 | 172 |
Node &2 of object type &1 cannot be deleted due to locked associations | Space: object requires documentation | |
| 173 | 173 |
User &1 locks associations assigned to object type &2 | The short text describes the object sufficiently | |
| 174 | 174 |
Associations assigned to object type &2 have been locked | The short text describes the object sufficiently | |
| 175 | 175 |
Authorization check &1 cannot be assigned as it has been changed | Space: object requires documentation | |
| 176 | 176 |
Package &1 does not exist | The short text describes the object sufficiently | |
| 177 | 177 |
Software component type &1 does not exist | The short text describes the object sufficiently | |
| 178 | 178 |
Type &1 is not character-like, alpha-conversion is not possible | The short text describes the object sufficiently | |
| 179 | 179 |
ODP semantics &1 does not exist | The short text describes the object sufficiently | |
| 180 | 180 |
ODP semantics is initial | The short text describes the object sufficiently | |
| 181 | 181 |
Node field cannot contain text as it is used in authorization checks | Space: object requires documentation | |
| 182 | 182 |
Node field cannot be assigned because it contains text | Space: object requires documentation | |
| 183 | 183 |
Node field cannot be assigned to authorization field &1 | Space: object requires documentation | |
| 184 | 184 |
Authorization object key &1 has been deleted in the meantime | The short text describes the object sufficiently | |
| 185 | 185 |
Select a back-end connectivity | The short text describes the object sufficiently | |
| 186 | 186 |
The virtual model has to have a reference node | The short text describes the object sufficiently | |
| 187 | 187 |
The model has no package assignment | Space: object requires documentation | |
| 188 | 188 |
There has to be at least one node | The short text describes the object sufficiently | |
| 189 | 189 |
There are nodes without parent node | The short text describes the object sufficiently | |
| 190 | 190 |
The model has no requests maintained | The short text describes the object sufficiently | |
| 191 | 191 |
The model has no response and UI area assignments maintained | The short text describes the object sufficiently | |
| 192 | 192 |
The model has no authorization checks maintained | The short text describes the object sufficiently | |
| 193 | 193 |
The model has no related actions maintained | The short text describes the object sufficiently | |
| 194 | 194 |
The model has no operational data provider maintained | The short text describes the object sufficiently | |
| 195 | 195 |
The path of auth. field &1 does not fit to node &2 of object type &3 | Space: object requires documentation | |
| 196 | 196 |
More than one field of request &1 is assigned to common attribute &2 | Space: object requires documentation | |
| 197 | 197 |
Only one field of request &1 can be assigned to common attribute &2 | Space: object requires documentation | |
| 198 | 198 |
Request &3 of object type &1, node &2 is not relevant for ODPs | Space: object requires documentation | |
| 199 | 199 |
Request is used in object type &1, node &2, ODP &3, field &4 | Space: object requires documentation | |
| 200 | 200 |
Request &3 of object type &1, node &2 (navigation request) does not exist | Space: object requires documentation | |
| 201 | 201 |
The request that is used as a navigation request does not exist | Space: object requires documentation | |
| 202 | 202 |
The request is used as a navigation request ODP-field &1/&2/&3/&4 | The short text describes the object sufficiently | |
| 203 | 203 |
Join operators other than = are currently not supported in search | The short text describes the object sufficiently | |
| 204 | 204 |
Join operator &1 does not exist | The short text describes the object sufficiently | |
| 205 | 205 |
A relation already exists between node field &1 and &2 | The short text describes the object sufficiently | |
| 206 | 206 |
The relation has no field assignment with join operator '=' (equal) | Space: object requires documentation | |
| 207 | 207 |
A cross-system reference cannot be set in software component &1 | Space: object requires documentation | |
| 208 | 208 |
Model GUID &1 cannot be used in cross-system reference | The short text describes the object sufficiently | |
| 209 | 209 |
Cross-system references can only be set on Enterprise Search hubs | The short text describes the object sufficiently | |
| 210 | 210 |
Cross-system reference model GUID for source node | The short text describes the object sufficiently | |
| 211 | 211 |
Cross-system reference model GUID for target node | The short text describes the object sufficiently | |
| 212 | 212 |
Cross-system reference model GUID for source field | The short text describes the object sufficiently | |
| 213 | 213 |
Cross-system reference model GUID for target field | The short text describes the object sufficiently | |
| 214 | 214 |
Model GUID &1 does not exist | The short text describes the object sufficiently | |
| 215 | 215 |
In SWC &1, it is not possible to use cross references in: &2 | Space: object requires documentation | |
| 216 | 216 |
In SWC &1, it is not possible to use cross references in: &2 | Space: object requires documentation | |
| 217 | 217 |
Cross references are impossible between central cross-system SWCs | Space: object requires documentation | |
| 218 | 218 |
No cross references between cross-system SWCs | Space: object requires documentation | |
| 219 | 219 |
No cross references from central cross-system SWCs and cross-system SWCs | Space: object requires documentation | |
| 220 | 220 |
No cross-references between software components within the same stack | Space: object requires documentation | |
| 221 | 221 |
Choose a software component first | The short text describes the object sufficiently | |
| 222 | 222 |
ODP usage &1 does not exist | The short text describes the object sufficiently | |
| 223 | 223 |
Mapping role &1 does not exist | The short text describes the object sufficiently | |
| 224 | 224 |
A composition must not have an association type | The short text describes the object sufficiently | |
| 225 | 225 |
The composition links different object types | The short text describes the object sufficiently | |
| 226 | 226 |
Object type &1, usage ID &2: | The short text describes the object sufficiently | |
| 227 | 227 |
Key of usage is not fully specified | The short text describes the object sufficiently | |
| 228 | 228 |
Source object type &1 does not exist | The short text describes the object sufficiently | |
| 229 | 229 |
Target object type &1 does not exist | The short text describes the object sufficiently | |
| 230 | 230 |
Usage ID &1 already exists | The short text describes the object sufficiently | |
| 231 | 231 |
The relation is not a cross-system rel. but has cross-system references | Space: object requires documentation | |
| 232 | 232 |
Field &1 of fixed value defintion is no field of source or target node | The short text describes the object sufficiently | |
| 233 | 233 |
Source object type model GUID does not exist | The short text describes the object sufficiently | |
| 234 | 234 |
Target object type model GUID does not exist | The short text describes the object sufficiently | |
| 235 | 235 |
Software comp. &1 is not a cross-system SWC or central cross-system SWC | Space: object requires documentation | |
| 236 | 236 |
Software component &1 is not a cross-system software component | Space: object requires documentation | |
| 237 | 237 |
Key of usage description is not fully specified | The short text describes the object sufficiently | |
| 238 | 238 |
Authorization type &1 does not exist | The short text describes the object sufficiently | |
| 239 | 239 |
Logical conjunctions to object type &1, node &2: syntax error | The short text describes the object sufficiently | |
| 240 | 240 |
Usage description in language &1 already exists | The short text describes the object sufficiently | |
| 241 | 241 |
Connectors of competitive software component &1 already exist | Space: object requires documentation | |
| 242 | 242 |
Conversion of model from generic to nongeneric unsuccessful | The short text describes the object sufficiently | |
| 243 | 243 |
Data provider 'DDIC' is not available | The short text describes the object sufficiently | |
| 244 | 244 |
Default request cannot be created: Define response attributes first | The short text describes the object sufficiently | |
| 245 | 245 |
Object type &1, usage ID &2, usage field &3: | The short text describes the object sufficiently | |
| 246 | 246 |
Key of usage field is not fully specified | The short text describes the object sufficiently | |
| 247 | 247 |
Object type &1, usage ID &2 does not exist | The short text describes the object sufficiently | |
| 248 | 248 |
Usage field model GUID does not exist | The short text describes the object sufficiently | |
| 249 | 249 |
Usage ID &1, usage field &2 already exists | Space: object requires documentation | |
| 250 | 250 |
Internal error when creating MUID-matrix - Inform SAP | The short text describes the object sufficiently | |
| 251 | 251 |
Not all authorization checks are listed in logical conjunction (type &1) | The short text describes the object sufficiently | |
| 252 | 252 |
Data provider &1 has raised an exception during import | Space: object requires documentation | |
| 253 | 253 |
Data provider &1 has raised an exception during import of node &2 | Space: object requires documentation | |
| 254 | 254 |
Model &1 is assigned to package $$TMP | Space: object requires documentation | |
| 255 | 255 |
Model &1 must not start with Y or Z | Space: object requires documentation | |
| 256 | 256 |
The request must be flagged for at least one usage | The short text describes the object sufficiently | |
| 257 | 257 |
The request cannot be the default ODP request as it is not OPD-relevant | The short text describes the object sufficiently | |
| 258 | 258 |
There must be exactly one default ODP request | The short text describes the object sufficiently | |
| 259 | 259 |
You cannot change the default ODP request because it is inherited | The short text describes the object sufficiently | |
| 260 | 260 |
There are requests relevant for ODP but none of these is set as default | Space: object requires documentation | |
| 261 | 261 |
Field with semantic "Content URL" must be of type STRG (STRING) | Space: object requires documentation | |
| 262 | 262 |
Assign selected connectivity to software component &1 first | Space: object requires documentation | |
| 263 | 263 |
Import of software component &1 from XML file was unsuccessful (&2) | The short text describes the object sufficiently | |
| 264 | 264 |
Data provider controller cannot retrieve data providers | The short text describes the object sufficiently | |
| 265 | 265 |
Metadata provider did not provide any data | Space: object requires documentation | |
| 266 | 266 |
There is more than one logical conjunction of type &1 for node type ID &2 | The short text describes the object sufficiently | |
| 267 | 267 |
Node type ID &1: Initial logical conjunction type was set to &2 | The short text describes the object sufficiently | |
| 268 | 268 |
Software component &1 cannot be assigned to system software component &3 | Space: object requires documentation | |
| 269 | 269 |
The following object types are assigned to package &1: | The short text describes the object sufficiently | |
| 270 | 270 |
&1 | The short text describes the object sufficiently | |
| 271 | 271 |
Authorization check &1 is user-based but has check value definitions | Space: object requires documentation | |
| 272 | 272 |
Select a file path for upload | The short text describes the object sufficiently | |
| 273 | 273 |
Metadata provider is not available (class &1) | Space: object requires documentation | |
| 274 | 274 |
ODP ID &1 is longer than 12 characters | The short text describes the object sufficiently | |
| 275 | 275 |
ODP field &1 is longer than 12 characters | The short text describes the object sufficiently | |
| 276 | 276 |
Cannot delete ODP &1 with semantics &2 | The short text describes the object sufficiently | |
| 277 | 277 |
ODP &3 of object type &1, node &2 (navigation ODP) does not exist | Space: object requires documentation | |
| 278 | 278 |
The ODP that is used as a navigation ODP does not exist | Space: object requires documentation | |
| 279 | 279 |
The ODP is used as a navigation ODP in object type &1, node &2 | Space: object requires documentation | |
| 280 | 280 |
Node type I &1, request ID &2: No flags are provided, so default is used | Space: object requires documentation | |
| 281 | 281 |
&1 is a reserved node field name | The short text describes the object sufficiently | |
| 282 | 282 |
&1 is a reserved node field GUID | The short text describes the object sufficiently | |
| 283 | 283 |
Basis software component &1 cannot use non-basis software component &2 | Space: object requires documentation | |
| 284 | 284 |
"Basis SWC" flag cannot be added to software component &1 | Space: object requires documentation | |
| 285 | 285 |
"Basis SWC" flag cannot be removed from software component &2 | Space: object requires documentation | |
| 286 | 286 |
Authorization check &1 already exists | The short text describes the object sufficiently | |
| 287 | 287 |
Wrong call of method CL_ESH_OM_MODELS=>CONVERT_MODEL_GUID_TO_NONGEN | Space: object requires documentation | |
| 288 | 288 |
Wrong call of method CL_ESH_OM_MODELS=>CONVERT_MODEL_GUID_TO_GEN | Space: object requires documentation | |
| 289 | 289 |
URL &1 is not valid | The short text describes the object sufficiently | |
| 290 | 290 |
Usage ID &1, attribute group &2 already exists | The short text describes the object sufficiently | |
| 291 | 291 |
Usage ID &1, attr. group &2, usage field &3: Assignment already exists | The short text describes the object sufficiently | |
| 292 | 292 |
Attribute group description in language &1 already exists | The short text describes the object sufficiently | |
| 293 | 293 |
Object type &1, usage ID &2, attribute group &3: | The short text describes the object sufficiently | |
| 294 | 294 |
Object type &1, attribute group &2 | The short text describes the object sufficiently | |
| 295 | 295 |
Error when creating hash code - inform SAP | The short text describes the object sufficiently | |
| 296 | 296 |
Request auto-tagging type &1 does not exist | The short text describes the object sufficiently | |
| 297 | 297 |
Node &2 cannot be enhanced with key attributes in software component &4 | Space: object requires documentation | |
| 298 | 298 |
Assignment of object type &1, usage id &2, field &4 to attribute group &3 | Space: object requires documentation | |
| 299 | 299 |
Key of usage field assignment to attribute group is not fully specified | The short text describes the object sufficiently | |
| 300 | 300 |
Key of usage attribute group is not fully specified | The short text describes the object sufficiently | |
| 301 | 301 |
Key of usage attribute group description is not fully specified | The short text describes the object sufficiently | |
| 302 | 302 |
Object type &1, usage ID &2, usage field &3 does not exist | The short text describes the object sufficiently | |
| 303 | 303 |
Object type &1, usage ID &2, usage attribute group &3 does not exist | The short text describes the object sufficiently | |
| 304 | 304 |
Object type &1, usage ID &2, usage attribute group &3, language &4: | The short text describes the object sufficiently | |
| 305 | 305 |
Object type &1, usage ID &2, language &3: | The short text describes the object sufficiently | |
| 306 | 306 |
Software component &1 cannot be edited in this system | The short text describes the object sufficiently | |
| 307 | 307 |
Usage type &1 does not exist | The short text describes the object sufficiently | |
| 308 | 308 |
Selected models of another software component got deselected | Space: object requires documentation | |
| 309 | 309 |
Software component &1 cannot be transported because it has type &2 | The short text describes the object sufficiently | |
| 310 | 310 |
Wrong setting of get-own-model-flags: inform SAP | The short text describes the object sufficiently | |
| 311 | 311 |
CL_ESH_OM_MODEL_SERVICES not initialized: inform SAP | The short text describes the object sufficiently | |
| 312 | 312 |
More than one request is flagged as default request | The short text describes the object sufficiently | |
| 313 | 313 |
Repository context &1 does not exist (internal error): inform SAP | The short text describes the object sufficiently | |
| 314 | 314 |
Old software component &2 was registered for transport | Space: object requires documentation | |
| 315 | 315 |
New software component &2 is not registered for transport | Space: object requires documentation | |
| 316 | 316 |
Old software component &2 was registered for transport | Space: object requires documentation | |
| 317 | 317 |
New software component &2 is not registered for transport | Space: object requires documentation | |
| 318 | 318 |
OPD field &1 and OPD field &2 refer to the same node field | Space: object requires documentation | |
| 319 | 319 |
Logical conjunction type &1 does not exist | The short text describes the object sufficiently | |
| 320 | 320 |
Reverse/source cardinality does not fit to foreign key definitions | Space: object requires documentation | |
| 321 | 321 |
Cardinality/target cardinality does not fit to foreign key definitions | Space: object requires documentation | |
| 322 | 322 |
Cardinality does not fit to foreign key definitions for search | Space: object requires documentation | |
| 323 | 323 |
Cardinality does not fit to foreign key definitions for search | Space: object requires documentation | |
| 324 | 324 |
Cardinality does not fit to foreign key definitions | Space: object requires documentation | |
| 325 | 325 |
Cardinality does not fit to foreign key definitions for search | Space: object requires documentation | |
| 326 | 326 |
Connector for object type &1 is assigned to the category | The short text describes the object sufficiently | |
| 327 | 327 |
Common attribute contains request fields of connector for object type &1 | The short text describes the object sufficiently | |
| 328 | 328 |
Node is referenced in data provider &1, filter &2 | The short text describes the object sufficiently | |
| 329 | 329 |
Data provider filter cannot be assigned to object type &1, node &2 | Space: object requires documentation | |
| 330 | 330 |
Data provider filter cannot be assigned to object type &3, node &4 | Space: object requires documentation | |
| 331 | 331 |
Initialization error in CL_ESH_OM_MODEL_SERVICES: inform SAP | The short text describes the object sufficiently | |
| 332 | 332 |
OBSOLETE | The short text describes the object sufficiently | |
| 333 | 333 |
Software component is free of conflicts | The short text describes the object sufficiently | |
| 334 | 334 |
Repeat check regularily (Actions -> Resolve Conflicts) | The short text describes the object sufficiently | |
| 335 | 335 |
&1 is not a data base table | The short text describes the object sufficiently | |
| 336 | 336 |
Connector for model &1 cannot be created as data is not extractable | The short text describes the object sufficiently | |
| 337 | 337 |
RFC destination &1 does not exist | Space: object requires documentation | |
| 338 | 338 |
There are more than two response attributes with UI area "Longtext" | The short text describes the object sufficiently | |
| 339 | 339 |
Root node cannot be changed as object type is inherited from lower SWC | Space: object requires documentation | |
| 340 | 340 |
Request fields have been removed | The short text describes the object sufficiently | |
| 341 | 341 |
Object type &1 cannot be directly accessible | Space: object requires documentation | |
| 342 | 342 |
Object type &1 direct accessible: Authorization check &3 incompatible | Space: object requires documentation | |
| 343 | 343 |
Filter conditions are not valid for application based object type | Space: object requires documentation | |
| 344 | 344 |
Client fields cannot be used in association | Space: object requires documentation | |
| 345 | 345 |
Client fields cannot be used in composition | Space: object requires documentation | |
| 346 | 346 |
Node &2 references another node but object type &1 is not virtual | The short text describes the object sufficiently | |
| 347 | 347 |
ODP ID &1, semantic &2, has been renamed to ODP ID &3, semantic &4 | The short text describes the object sufficiently | |
| 348 | 348 |
Connectors must be deleted, recreated and indexed in target systems | Space: object requires documentation | |
| 349 | 349 |
Renaming object tpye &1 may have impact on customer systems! | Space: object requires documentation | |
| 350 | 350 |
Connector for object type &1 cannot be updated | Space: object requires documentation | |
| 351 | 351 |
Connector for object type &1 cannot be updated | Space: object requires documentation | |
| 352 | 352 |
Auto completion cannot be set | Space: object requires documentation | |
| 353 | 353 |
Layout configuration &1: | The short text describes the object sufficiently | |
| 354 | 354 |
Layout configuration &1 already exists | The short text describes the object sufficiently | |
| 355 | 355 |
Layout configuration is initial | The short text describes the object sufficiently | |
| 356 | 356 |
Platform &1 does not exist | The short text describes the object sufficiently | |
| 357 | 357 |
Secondary key of layout configuration is inconsistent | Space: object requires documentation | |
| 358 | 358 |
Technology &1 does not exist | The short text describes the object sufficiently | |
| 359 | 359 |
Attribute &1 must be numerical but value is &2 | The short text describes the object sufficiently | |
| 360 | 360 |
Layout configuration &1 is not assigned to a software component | The short text describes the object sufficiently | |
| 361 | 361 |
Cannot delete layout configuration | The short text describes the object sufficiently | |
| 362 | 362 |
Object type &1, node &2, layout configuration &3: | The short text describes the object sufficiently | |
| 363 | 363 |
Layout configuration &1 does not exist | The short text describes the object sufficiently | |
| 364 | 364 |
Layout configuration &4 is used in object type &1, node &2 of SWC &3 | The short text describes the object sufficiently | |
| 365 | 365 |
The layout configuration does not exist | The short text describes the object sufficiently | |
| 366 | 366 |
Layout configurations have been locked by user &2 | The short text describes the object sufficiently | |
| 367 | 367 |
Layout configurations: System failure during lock | The short text describes the object sufficiently | |
| 368 | 368 |
Layout template for layout configuration &1 already exists | The short text describes the object sufficiently | |
| 369 | 369 |
Layout configuration is initial | The short text describes the object sufficiently | |
| 370 | 370 |
Layout template cannot be created because node &2 has no response fields | Space: object requires documentation | |
| 371 | 371 |
Node &2 has at least one layout template but no response fields | Space: object requires documentation | |
| 372 | 372 |
Related perspective for object type &1, node &2: | The short text describes the object sufficiently | |
| 373 | 373 |
Key of related perspective &1/&2 is not fully specified | Space: object requires documentation | |
| 374 | 374 |
Mapping number for related perspective &1/&2 is initial | Space: object requires documentation | |
| 375 | 375 |
Perspective &1/&2 is already assigned with mapping number &3 | The short text describes the object sufficiently | |
| 376 | 376 |
Related perspective &1/&2/&3/&4: | Space: object requires documentation | |
| 377 | 377 |
Description of related perspective in language &1 already exists. | The short text describes the object sufficiently | |
| 378 | 378 |
Key of related perspective description is not fully specified | The short text describes the object sufficiently | |
| 379 | 379 |
Related perspective &1/&2/&3, language &4: | The short text describes the object sufficiently | |
| 380 | 380 |
Related perspective does not exist | The short text describes the object sufficiently | |
| 381 | 381 |
Related perspectives &1 and &2 have the same description in language &3 | Space: object requires documentation | |
| 382 | 382 |
Related perspective field mapping &1/&2/&3/&4: | Space: object requires documentation | |
| 383 | 383 |
Key of related perspective was not fully specified | The short text describes the object sufficiently | |
| 384 | 384 |
Related perspective &1/&2/&3/&4 does not exist | Space: object requires documentation | |
| 385 | 385 |
Response field is initial | The short text describes the object sufficiently | |
| 386 | 386 |
Cannot delete response field | The short text describes the object sufficiently | |
| 387 | 387 |
Response field is used in related perspective field mapping &1/&2/&3/&4 | Space: object requires documentation | |
| 388 | 388 |
Response field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 389 | 389 |
The response field used in a related perspect. field map. does not exist | Space: object requires documentation | |
| 390 | 390 |
Field is referenced in related perspective field mapping &1/&2/&3/&4 | Space: object requires documentation | |
| 391 | 391 |
Field mapping resp. fld. &1 / rel. persp. attribute &2 already exists | Space: object requires documentation | |
| 392 | 392 |
Fixed value definition of related perspective &1/&2/&3/&4: | Space: object requires documentation | |
| 393 | 393 |
Related perspectives fixed valued definition: Key is not fully specified | Space: object requires documentation | |
| 394 | 394 |
Related perspective attribute &1 is already assigned to a response field | Space: object requires documentation | |
| 395 | 395 |
Related perspective attribute &1 is already given fixed values | Space: object requires documentation | |
| 396 | 396 |
Related perspectives: Node type ID &1, related perspective &2/&3/&4 | Space: object requires documentation | |
| 397 | 397 |
Related perspective texts: Node type id &1, perspect. &2/&3, lanugage &4 | Space: object requires documentation | |
| 398 | 398 |
Node type id &1, package &2, perspect. &3, mapping no. &4 is not provided | The short text describes the object sufficiently | |
| 399 | 399 |
Related perspective field mappings: Node type id &1, mapping &2/&3/&4 | Space: object requires documentation | |
| 400 | 400 |
Related perspect. fixed val.: Related persp. &1/&2/&3/&4 is not provided | Space: object requires documentation | |
| 401 | 401 |
Response field must be freestyle or assigned to a perspective attribute | Space: object requires documentation | |
| 402 | 402 |
Related perspective field mapping &1/&2/&3 (freestyle): | Space: object requires documentation | |
| 403 | 403 |
Response field is used in related persp. field mapping &1/&2/&3 (freest.) | Space: object requires documentation | |
| 404 | 404 |
Field is referenced in related perspect. field mapp. &1/&2/&3 (freestyle) | Space: object requires documentation | |
| 405 | 405 |
Layout type &1 does not exist | The short text describes the object sufficiently | |
| 406 | 406 |
Mapping number for related request &1/&2/&3 is initial | The short text describes the object sufficiently | |
| 407 | 407 |
The subquery flag only be set for UI technology &1 | The short text describes the object sufficiently | |
| 408 | 408 |
Related requests &1/&2 and &3/&4 have the same navigation ID | Space: object requires documentation | |
| 409 | 409 |
Related request &1/&2 and related perspective &3/&4 have the same ID | Space: object requires documentation | |
| 410 | 410 |
Related request &1/&2 and backend navigation &3/&4 have the same ID | Space: object requires documentation | |
| 411 | 411 |
Related perspectives &1/&2 and &3/&4 have the same navigation ID | Space: object requires documentation | |
| 412 | 412 |
Related perspectives &1/&2 and related request &3/&4 have the same ID | Space: object requires documentation | |
| 413 | 413 |
Related perspectives &1/&2 and backend navigation &3/&4 have the same ID | Space: object requires documentation | |
| 414 | 414 |
Backend navigation &1/&2 and related request &3/&4 have the same ID | Space: object requires documentation | |
| 415 | 415 |
Backend navigation &1/&2 and related perspective &3/&4 have the same ID | Space: object requires documentation | |
| 416 | 416 |
Internal error when updaten temporary buffer &1: Inform SAP | The short text describes the object sufficiently | |
| 417 | 417 |
Navigation ID of related request &1/&2/&3/&4 contains forbidden char. | Space: object requires documentation | |
| 418 | 418 |
Navigation ID of related perspective &1/&2/&3 contains forbidden char. | Space: object requires documentation | |
| 419 | 419 |
Navigation ID of backend navigatio &1/&2 contains forbidden characters | Space: object requires documentation | |
| 420 | 420 |
Related request &1/&2/&3, language &4: | Space: object requires documentation | |
| 421 | 421 |
Key of related request description is not fully specified | The short text describes the object sufficiently | |
| 422 | 422 |
Description of related request in language &1 already exists. | The short text describes the object sufficiently | |
| 423 | 423 |
Related requests &1 and &2 have the same description in language &3 | Space: object requires documentation | |
| 424 | 424 |
Related request field mapping &1/&2/&3/&4; | Space: object requires documentation | |
| 425 | 425 |
Related request field mapping &1/&2/&3 (freestyle): | Space: object requires documentation | |
| 426 | 426 |
Key of related request field mapping is not fully specified | The short text describes the object sufficiently | |
| 427 | 427 |
Related request &1/&2/&3/&4 does not exist | Space: object requires documentation | |
| 428 | 428 |
Object type &1, node &2, request &3, request field &4 does not exist | The short text describes the object sufficiently | |
| 429 | 429 |
Response field must be freestyle or assigned to a request field | Space: object requires documentation | |
| 430 | 430 |
Response field is used in related request field mapping &1/&2/&3/&4 | Space: object requires documentation | |
| 431 | 431 |
Response field is used in related req. field mapping &1/&2/&3 (freest.) | Space: object requires documentation | |
| 432 | 432 |
Request field is used in related request field mapping &1/&2/&3/&4 | Space: object requires documentation | |
| 433 | 433 |
Related request texts: Node type id &1, request &2/&3, lanugage &4 | Space: object requires documentation | |
| 434 | 434 |
Related request &1/&2&/&3/&4 is not provided | Space: object requires documentation | |
| 435 | 435 |
Related request field mappings: Node type id &1, mapping &2/&3/&4 | Space: object requires documentation | |
| 436 | 436 |
Fixed value definition of related request &1/&2/&3/&4: | Space: object requires documentation | |
| 437 | 437 |
Key of related request was not fully specified | The short text describes the object sufficiently | |
| 438 | 438 |
Related request &1/&2/&3/&4 does not exist | Space: object requires documentation | |
| 439 | 439 |
Related request fixed valued definition: Key is not fully specified | Space: object requires documentation | |
| 440 | 440 |
Related request field is initial | The short text describes the object sufficiently | |
| 441 | 441 |
Related request field &1/&2/&3/&4 is already assigned to a response field | Space: object requires documentation | |
| 442 | 442 |
Related request field &1/&2/&3/&4 is already given fixed values | Space: object requires documentation | |
| 443 | 443 |
Request field is used in fixed values def. of related request &1/&2/&3/&4 | Space: object requires documentation | |
| 444 | 444 |
Response field &3 of object type &1, node &2 does not exist | Space: object requires documentation | |
| 445 | 445 |
The response field used in a related request field mapping does not exist | The short text describes the object sufficiently | |
| 446 | 446 |
Request field &4 of object type &1, node &2, request &3 does not exist | Space: object requires documentation | |
| 447 | 447 |
The request field used in a related request field mapping does not exist | The short text describes the object sufficiently | |
| 448 | 448 |
Field is referenced in related request field mapping &1/&2/&3/&4 | Space: object requires documentation | |
| 449 | 449 |
Field is referenced in related request field mapping &1/&2/&3/&4 | The short text describes the object sufficiently | |
| 450 | 450 |
Request field &4 of object type &1, node &2, request &3 does not exist | Space: object requires documentation | |
| 451 | 451 |
The request field used in a related req. fixed value def. does not exist | Space: object requires documentation | |
| 452 | 452 |
Field is referenced in fixed value def. of related request &1/&2/&3/&4 | Space: object requires documentation | |
| 453 | 453 |
Cannot delete request field | The short text describes the object sufficiently | |
| 454 | 454 |
Related perspective fixed values: Node type id &1, values for &2/&3/&4 | Space: object requires documentation | |
| 455 | 455 |
Related request fixed values: Node type id &1, values for &2/&3/&4 | Space: object requires documentation | |
| 456 | 456 |
Request &3 does not reference all keyfields of node &2 | Space: object requires documentation | |
| 457 | 457 |
Mapping numbers greater than &1 are reserved for special use | The short text describes the object sufficiently | |
| 458 | 458 |
Related request &1/&2/&3/&4: | Space: object requires documentation | |
| 459 | 459 |
Field mapping resp. fld. &1 <-> rel. request field &2 already exists | The short text describes the object sufficiently | |
| 460 | 460 |
Response field &1 is already flagged for freestyle search | The short text describes the object sufficiently | |
| 461 | 461 |
Value is incompatible with type of node request field | Space: object requires documentation | |
| 462 | 462 |
Types of response field &1 and request field &2 are incompatible | Space: object requires documentation | |
| 463 | 463 |
Types of response field &1 and request field &2 are incompatible | Space: object requires documentation | |
| 464 | 464 |
Horizontal size must be positive | The short text describes the object sufficiently | |
| 465 | 465 |
Vertical size must be positive | The short text describes the object sufficiently | |
| 466 | 466 |
Data provider &1 cannot be direct accessible | Space: object requires documentation | |
| 467 | 467 |
Table &1 does not exist | The short text describes the object sufficiently | |
| 468 | 468 |
Error when checking existence of table &1 | The short text describes the object sufficiently | |
| 469 | 469 |
&1 must be a transparent table | Space: object requires documentation | |
| 470 | 470 |
Node name contains slashes that do not indicate a namespace | Space: object requires documentation | |
| 471 | 471 |
No field of the default request is flagged for freestyle search | Space: object requires documentation | |
| 472 | 472 |
The root node must not have a parent node | The short text describes the object sufficiently | |
| 473 | 473 |
Object type &1 has no root node | The short text describes the object sufficiently | |
| 474 | 474 |
Data provider is direct accessible but no database table is specified | The short text describes the object sufficiently | |
| 475 | 475 |
Object type is direct accessible but has an extraction implementation | The short text describes the object sufficiently | |
| 476 | 476 |
Flag "Contains Text" is ignored in connectors created on a HANA Data Base | Space: object requires documentation | |
| 477 | 477 |
The related perspective has no field mapping or fixed value definiton | The short text describes the object sufficiently | |
| 478 | 478 |
Navigation ID &1 has been flagged as object link | The short text describes the object sufficiently | |
| 479 | 479 |
Request field &4 does not belong to object type &1, node &2, request &3 | The short text describes the object sufficiently | |
| 480 | 480 |
Node &2 has no response fields but is flagged for subquery | Space: object requires documentation | |
| 481 | 481 |
Object type &1 (software component &2) is already predecessor of &3 | Space: object requires documentation | |
| 482 | 482 |
Object type GUID &2 (software component &1) is already a predecessor | Space: object requires documentation | |
| 483 | 483 |
Object type GUID &2 (software component GUID &1) is already a predecessor | Space: object requires documentation | |
| 484 | 484 |
Object type &1, predecessor: software component &2, object type &3 | The short text describes the object sufficiently | |
| 485 | 485 |
Object type is initial | The short text describes the object sufficiently | |
| 486 | 486 |
Predecessor software component (PSWC) and PSWC-GUID are initial | The short text describes the object sufficiently | |
| 487 | 487 |
Software component of predecessor object type is initial | The short text describes the object sufficiently | |
| 488 | 488 |
Predecessor object type and predecessor object type GUID are initial | The short text describes the object sufficiently | |
| 489 | 489 |
Predecessor software component &1 does not exist | The short text describes the object sufficiently | |
| 490 | 490 |
Predecessor object type &2 from software component &1 does not exist | The short text describes the object sufficiently | |
| 491 | 491 |
Object type &1 is used as predecessor of object type &3 from SWC&2 | Space: object requires documentation | |
| 492 | 492 |
Object type &1 has more than one successors | The short text describes the object sufficiently | |
| 493 | 493 |
The predecesor relations starting at object type &1 are circular | The short text describes the object sufficiently | |
| 494 | 494 |
Only business templates or virtual templates may have predecessors | The short text describes the object sufficiently | |
| 495 | 495 |
Navigation id &1 must start with &2 | The short text describes the object sufficiently | |
| 496 | 496 |
Navigation id &1 must not start with &2 | Space: object requires documentation | |
| 497 | 497 |
Error when checking table in DDIC | The short text describes the object sufficiently | |
| 498 | 498 |
Table &1 does not exist | The short text describes the object sufficiently | |
| 499 | 499 |
Table &1 is a pool-/cluster table but data provider is not flagged | The short text describes the object sufficiently | |
| 500 | 500 |
Table &1 is no pool-/cluster table but data provider is flagged | The short text describes the object sufficiently | |
| 501 | 501 |
Response field is used in backend navigation field ass. &1/&2/&3/&4 | Space: object requires documentation | |
| 502 | 502 |
Attribute &1 has a fulltext index defined in DDIC | Space: object requires documentation | |
| 503 | 503 |
No data provider of object type &1 is based on a pool-/cluster table | Space: object requires documentation | |
| 504 | 504 |
Data provider &2 is not based on pool-/cluster table | Space: object requires documentation | |
| 505 | 505 |
&1 is no database table but data provider &1 is flagged for pool/cluster | The short text describes the object sufficiently | |
| 506 | 506 |
Authorization check cannot be assigned to node &2 | Space: object requires documentation | |
| 507 | 507 |
Filter conditions are not valid | The short text describes the object sufficiently | |
| 508 | 508 |
Node &1 cannot be used in path of authorization check &2 | Space: object requires documentation | |
| 509 | 509 |
Field &3 of node &2 of object type &1 must be flagged to contain text | Space: object requires documentation | |
| 510 | 510 |
XML-error at row &1, column &2 | The short text describes the object sufficiently | |
| 511 | 511 |
Rendering template is initial | The short text describes the object sufficiently | |
| 512 | 512 |
&1 | The short text describes the object sufficiently | |
| 513 | 513 |
You cannot enter &1 because &1 is a reserved keyword | The short text describes the object sufficiently | |
| 514 | 514 |
Key field &3 of node &2 of object type &1 cannot used in field mapping | Space: object requires documentation | |
| 515 | 515 |
Key field &4 cannot have semantics "Language Code" | Space: object requires documentation | |
| 516 | 516 |
Key field &4 cannot have semantics "Language Code" | Space: object requires documentation | |
| 517 | 517 |
Field &3 cannot be flagged to "Contain text" | Space: object requires documentation | |
| 518 | 518 |
Field &4 cannot be flagged to "Contain text" | Space: object requires documentation | |
| 519 | 519 |
Update/reset node cannot be executed | Space: object requires documentation | |
| 520 | 520 |
It is not possible to change the node of attribute group &1 | Space: object requires documentation | |
| 521 | 521 |
Inactive or active storage could not be instantiated -> no where used | Space: object requires documentation | |
| 522 | 522 |
Stack of software component &1 is inconsistent -> where used not possible | Space: object requires documentation | |
| 523 | 523 |
Technical model &1 could not be generated | The short text describes the object sufficiently | |
| 524 | 524 |
Technical model &1 generated and linked to node &2 | The short text describes the object sufficiently | |
| 525 | 525 |
No technical model could be generated for node &1 | The short text describes the object sufficiently | |
| 526 | 526 |
Default request does not reference key field &3 (object type &1, node &2) | Space: object requires documentation | |
| 527 | 527 |
Field &3 of node &2 is not referenced in a response field node &2 | Space: object requires documentation | |
| 528 | 528 |
Default request does not reference all key fields of node &2 | Space: object requires documentation | |
| 529 | 529 |
SAP System is currently locked as upgrade is in progress | The short text describes the object sufficiently | |
| 530 | 530 |
A response attribute and an attribute group have the same name (&3) | Space: object requires documentation | |
| 531 | 531 |
Could not resolve GUID &1 (&2) - maybe SNOTE report missing | Space: object requires documentation | |
| 532 | 532 |
Could not fully resolve GUID &1 (&2) because GUID &3 (&4) is unknown | Space: object requires documentation | |
| 533 | 533 |
It is not possible to enhance object type &1 | Space: object requires documentation | |
| 534 | 534 |
It is not possible to enhance data type &1 | Space: object requires documentation | |
| 535 | 535 |
It is not possible to enhance relation &1 | Space: object requires documentation | |
| 536 | 536 |
It is not possible to enhance authorization check &1 | Space: object requires documentation | |
| 537 | 537 |
It is not possible to enhance navigation path id &1 | Space: object requires documentation | |
| 538 | 538 |
Software comoponent &1 is a basis software component: cannot be enhanced | The short text describes the object sufficiently | |
| 539 | 539 |
Source client identical to target client | The short text describes the object sufficiently | |
| 540 | 540 |
Error creating table of type &1 | The short text describes the object sufficiently | |
| 541 | 541 |
Error inserting into table &1 | The short text describes the object sufficiently | |
| 542 | 542 |
Error updating model import log | The short text describes the object sufficiently | |
| 543 | 543 |
Generic update allowed from source client 000 only | The short text describes the object sufficiently | |
| 544 | 544 |
Renaming not possible because of GTABKEY registration | Space: object requires documentation | |
| 545 | 545 |
New entry not possible because of GTABKEY registration | Space: object requires documentation | |
| 546 | 546 |
No message specified - inform SAP | The short text describes the object sufficiently | |
| 547 | 547 |
Object type &1, node &2, request attribute group &3, ref. attr. group &4 | The short text describes the object sufficiently | |
| 548 | 548 |
Object type &1, node &2, attribute group &3, ref. attribute group &4: | The short text describes the object sufficiently | |
| 549 | 549 |
Object_type &1, node &2, ODP/semantics &3, field &4 | The short text describes the object sufficiently | |
| 550 | 550 |
Object type &1, node &2, request/field &3, common attribute &4 | The short text describes the object sufficiently | |
| 551 | 551 |
Assignment of field &4 to object type &1, node &2, request/attr. group &3 | The short text describes the object sufficiently | |
| 552 | 552 |
Object type &1, node &2, UI type/navigation id &3, field &4 | The short text describes the object sufficiently | |
| 553 | 553 |
Source field &1, target field &2 | The short text describes the object sufficiently | |
| 554 | 554 |
Software component usage: Including SWC &2 in SWC &1 | The short text describes the object sufficiently | |
| 555 | 555 |
Predecessor object type &1 does not exist | The short text describes the object sufficiently | |
| 556 | 556 |
Data provider &1, filter &2, ref. data prov./field &3, counter &4 | The short text describes the object sufficiently | |
| 557 | 557 |
Data provider &1, attribute group &2 | The short text describes the object sufficiently | |
| 558 | 558 |
Data provider &1: usage of attribute group &2 in attribute group &3 | The short text describes the object sufficiently | |
| 559 | 559 |
Renaming not possible because of GTABKEY registration | Space: object requires documentation | |
| 560 | 560 |
New entry not possible because of GTABKEY registration | Space: object requires documentation | |
| 561 | 561 |
Renaming not possible because of GTABKEY registration | Space: object requires documentation | |
| 562 | 562 |
New entry not possible because of GTABKEY registration | Space: object requires documentation | |
| 563 | 563 |
Renaming not possible because of GTABKEY registration | Space: object requires documentation | |
| 564 | 564 |
New entry not possible because of GTABKEY registration | Space: object requires documentation | |
| 565 | 565 |
Field assignment of authorization check &1, authorization field &2 | The short text describes the object sufficiently | |
| 566 | 566 |
Fixed value defintion: authorization check &1, field &2, counter &3 | The short text describes the object sufficiently | |
| 567 | 567 |
Assignment of switch id &1 to: | The short text describes the object sufficiently | |
| 568 | 568 |
System software component cannot be assigned due to GTABKEY registration | Space: object requires documentation | |
| 569 | 569 |
New entry not possible because of GTABKEY registration | Space: object requires documentation | |
| 570 | 570 |
Wrong call of RECORD_GTABKEY_REGISTRATIONS - inform SAP | The short text describes the object sufficiently | |
| 571 | 571 |
Entry can't be registered because there is already a GTABKEY registration | The short text describes the object sufficiently | |
| 572 | 572 |
Category cannot be assigned to SWC &1 due to GTABKEY registration | The short text describes the object sufficiently | |
| 573 | 573 |
GTABKEY-registration: user &1, transport request &2 | The short text describes the object sufficiently | |
| 574 | 574 |
GTABKEY-registration: user &1 | The short text describes the object sufficiently | |
| 575 | 575 |
GTABKEY-registration: transport request &2 | The short text describes the object sufficiently | |
| 576 | 576 |
Common attribute &1: | The short text describes the object sufficiently | |
| 577 | 577 |
Common attr. cannot be assigned to SWC &1 due to GTABKEY registration | The short text describes the object sufficiently |
History
| Last changed on/by | |
20141121 | SAP |
| SAP Release Created in | 730 |
