/IWBEP/CM_MGW_RT - OData Channel Runtime Messages
The following messages are stored in message class /IWBEP/CM_MGW_RT: OData Channel Runtime Messages.
It is part of development package /IWBEP/MGW_GSR_CORE in software component OPU-BSE-SDE. This development package consists of objects that can be grouped under "OData Channel - Service Interface - Core".
It is part of development package /IWBEP/MGW_GSR_CORE in software component OPU-BSE-SDE. This development package consists of objects that can be grouped under "OData Channel - Service Interface - Core".
Message Nr ▲ | Message Text |
---|---|
000 | User does not have the sufficient authorizations |
001 | Not supported - Routing information needed |
002 | Outdated metadata - Cache refresh triggered - Try again the request |
003 | Metadata cache on hub system for current model is outdated |
004 | Metadata cache on hub system outdated; execute OData request again |
005 | Cached request on hub system inconsistent; Cache refresh triggered |
006 | Cached request processing failed during response serialization for &1 |
007 | Request cache deprecated; Cache refresh triggered |
008 | Soft-State is not enabled |
009 | Soft-State Delay Invocation is not enabled |
010 | '&1' |
011 | Default value of property '&1' not bound |
012 | Unsupported combination of query options |
013 | Function Import '&1' is for testing only and contains no functionality |
014 | An error occured while trying to perform an Input Conversion Exit |
015 | Filter select options could not be created |
016 | Value control property '&1' is not set as technical property |
017 | Model '&1' version '&2' has cycling dependecies |
018 | eTag handling for function import not implemented by provider application |
019 | Function import '&1' cannot use return type '&2' if no data is returned |
020 | Resource not found for segment '&' |
021 | Method '&1' not implemented in data provider class |
022 | &1 |
023 | Model '&1' version '&2' not found |
024 | Model provider class is empty for model '&1' version '&2' |
025 | Data provider class is empty for internal service name '&1' version '&2' |
026 | No service found for namespace &1, name &2, version &3 |
027 | Operation '&1' not supported for entity type '&2' |
028 | Transformation error on deserialization |
029 | Transformation error on serialization |
030 | Duplicate resource |
031 | No TADIR entry found for service &1, version &2 |
032 | Internal error occurred, contact your system administrator |
033 | Model '&1' version '&2' not created |
034 | Model '&1' version '&2' not deleted |
035 | Model '&1' version '&2' not updated |
036 | Model '&1' version '&2' not locked |
037 | Model '&1' version '&2' exists |
038 | Service '&1' version '&2' not created |
039 | Service '&1' version '&2' not deleted |
040 | Service '&1' version '&2' not updated |
041 | Service '&1' version '&2' not locked |
042 | Service '&1' version '&2' exists |
043 | Model '&1' (vers '&2') to service '&3' (vers '&4') assignment not created |
044 | Model '&1' (vers '&2') to service '&3' (vers '&4') assignment not deleted |
045 | Model '&1' (vers '&2') to service '&3' (vers '&4') assignment not locked |
046 | Model '&1' (vers '&2') to service '&3' (vers '&4') assignment exists |
047 | Model to service assignment exists |
048 | Changeset not supported for entity type '&' |
049 | Rollbacked because of error during changeset processing |
050 | Rejected because of error during changeset processing |
051 | Commit work during changeset processing not allowed |
052 | Rollback work during changeset processing not allowed |
053 | Default changeset implementation allows only one operation |
054 | Namespace '&1' not valid |
055 | Namespaces not allowed in external name of service |
056 | Different provider instances during a changeset processing |
057 | Function is not allowed in a deferred processing mode of a changeset. |
058 | Missing response data in changeset deferred processing mode |
059 | Property '&1': Only conversion exits supported on default values |
060 | Start sending notifications to system '&1', client '&2' |
061 | Failed to send notifications |
062 | Successfully sent notifications |
063 | Filter parameter '&1' is not supported |
064 | HTTP: Start sending notifications to destination '&1' |
065 | HTTP: Successfully sent notifications |
066 | HTTP: Failed to send notifications; Status Code:&1;Reason:&2 |
067 | Soft state processing mode is not supported by the Data Provider |
068 | Unsupported response context in expand query option |
069 | Unsupported response context |
070 | Vocabulary annotation '&1' version '&2' already exists |
071 | Create vocabulary annotation '&1' version '&2' failed |
072 | Delete vocabulary annotation '&1' version '&2' failed |
073 | Update vocabulary annotation '&1' version '&2' failed |
074 | Lock vocabulary annotation '&1' version '&2' failed |
075 | Vocabulary annotation '&1' version '&2' not found |
076 | Vocabulary annotation locked by user '&1' |
077 | Vocabulary annotation '&1' version '&2' already assigned to service |
078 | Vocabulary annotation '&1' version '&2' not assigned to service |
079 | Set a new main service necessary before unassign the old one |
080 | Vocabulary '&1' version '&2' already exists |
081 | Create vocabulary '&1' version '&2' failed |
082 | Delete vocabulary '&1' version '&2' failed |
083 | Update vocabulary '&1' version '&2' failed |
084 | Lock vocabulary '&1' version '&2' failed |
085 | Vocabulary '&1' version '&2' not found |
086 | Vocabulary locked by user '&1' |
087 | You have defined &1 parameters. For IF two or three parameters supported. |
088 | You have defined &1 parameters. For NOT only one parameters supported. |
089 | You have defined &1 parameters. For &2 only two parameters supported. |
090 | Property conversion not allowed because model is set to "no conversions" |
091 | Caching on hub not allowed by configuration (Softstate or Service Config) |
092 | Method '&1' not implemented in model provider class |
093 | Provided text type for the annotation simple value is not supported |
094 | Provided text element symbol for the simple value may not be initial |
095 | Provided text element container for the simple value may not be initial |
096 | Provided text type for the simple value may not be initial |
097 | Provided text id for the simple value may not be initial |
098 | Provided text id already exists |
099 | Caching on hub not allowed if read access logging is configured |
100 | Property (external name) '&1' not found for entity '&2' |
101 | Data object '&1' not found |
102 | Complex type '&1' not found |
103 | Function import '&1' not found |
104 | Association '&1' not found |
105 | Entity by ID '&1' not found |
106 | ABAP Dictionary element '&1' not found |
107 | Metadata ABAP Dictionary text loading |
108 | Metadata loading for model name '&1' and version '&2' |
109 | Metadata loaded |
110 | Data object name: '&1' already exists |
111 | Association name: '&1' ABAP field name '&2' already exists |
112 | Property name: '&1' ABAP field name '&2' already exists |
113 | Complex type name: '&1' already exists |
114 | Action name: '&1' already exists |
115 | Property field already exists name: '&1' ABAP field name '&2' |
116 | Property '&2' of data object '&1' has no EDM type assigned |
117 | Property with field '&2' of data object '&1' has no name assigned |
118 | Property '&2' of data object '&1' has no field assigned |
119 | Data object '&1' has no key field assigned |
120 | Data type not found '&1' |
121 | Association '&1' has the same name as data object '&2' |
122 | Navigation property '&1' of data object '&2' is inconsistent |
123 | Navigation property '&1' named identical to property '&2' of entity '&3' |
124 | Property '&1' not found on principal '&2' |
125 | Property '&1' not found on dependent '&2' |
126 | Metadata class text elements loading |
127 | Metadata class text elements loaded |
128 | Inheritance for entity '&1' already exists |
129 | Class element ID '&1' does not exist in class '&2' |
130 | Association with identical name as entity type '&1' already exists |
131 | Action '&1' inconsistent |
132 | Association set '&1' references to disabled association '&2' |
133 | Association set '&1' references to disabled entity set '&2' |
134 | Navigation property '&1' references to disabled association '&2' |
135 | Complex type property '&1' references to disabled complex type '&2' |
136 | Input node entity type '&1' for function import '&2' is disabled |
137 | Output node entity type '&1' for function import '&2' is disabled |
138 | Association set '&1' references to disabled entity type '&2' |
139 | No entity type found for entity set '&1' |
140 | No complex type found for complex type property '&1' |
141 | No association found for navigation property '&1' |
142 | No entity type found for input node of function import '&1' |
143 | No entity type found for output node of function import '&1' |
144 | Association &1: referential constraint property not found in entity &2 |
145 | Association &1: referential constraint property &3 disabled in entity &2 |
146 | Extend the same model '&1' and version '&2' not allowed |
147 | Association set '&1' has no proper entity sets assigned |
148 | Model is corrupt. Expand data container cannot be created. |
149 | Property '&2' of data object '&1' has no Internal type assigned |
150 | Specify an object name |
151 | Separator '/' for namespace not paired or in wrong position |
152 | Maximum name length '&1' exceeded |
153 | Do not use any special characters |
154 | Name range /.../ is too long |
155 | Characters 'SPACE' and '/.,()'"=_%*����' are not allowed |
156 | Only use '/' as a namespace delimiter |
157 | Type of data container returned by DPC is wrong. '&1' is expected |
158 | ABAP Dictionary structure '&1' not found |
159 | ABAP Dictionary type '&1' not supported (flat structure only) |
160 | Structure type '&1' provided by the application does not exist |
161 | Type '&1' provided by the app is not a strcuture (Type KIND_STRUCT) |
162 | Source name for complex type '&1' was not provided |
163 | Tag '&1' already exists. Application programming error |
164 | Name for complex type '&1' was not provided |
165 | Dummy field '&1' not found in include '&2' |
166 | Property '&1' of entity '&2' already added: SFE logic from include '&3' |
167 | Property '&1' of entity type '&2' has already been added |
168 | Property item with internal name '&1' not found for entity '&2' |
169 | Property item with internal name '&1' not found for complex type '&2' |
170 | 'to-many' associations are not supported in target calculation |
171 | XSD ABAP data types are not supported |
172 | XSD ABAP data types are not supported; check property '&1' |
173 | Specify an entity key to calculate a target in an entity list |
174 | Specify a key for navigation &1 |
175 | Key structure for entity type &1 not created; check service model |
176 | Internal error during filter tree processing |
177 | The data provider requires batch processing for this request (RAL) |
178 | &1 is not a valid On Delete Action for association &2 |
179 | Uppercase setting is not allowed for property &1 |
180 | If Max-Age is not initial then Do-Not-Cache-On-Client must be set to '-' |
181 | Is-Not-Modified is not allowed in case If-Modified-Since is initial |
182 | Is-Not-Modified is not allowed in case of framework expand |
183 | Is-Not-Modified must have the same values in all nodes for data provider |
184 | Error during read access logging |
185 | No target found for association &1 with source entity &2 |
186 | Value control property '&1' can not be set as ETag property |
187 | Content referencing is only allowed for changeset at once |
188 | Service provider did not return any business data |
189 | An exception occurred when accessing cached data in shared memory |
190 | State of the resource (entity) was already changed (If-Match) |
191 | Request caching is not allowed in this context |
192 | Result caching on hub not allowed for cached request processing |
193 | Conversion '&1' of property '&2' and move to data container failed |
194 | Precondition required |
195 | Data provided by the application causes transformation for '&1' to fail |
196 | Batch operation ID &1 not found |
197 | Unknown exception during conversion |
198 | The data provider did not respond to all batch operations |
199 | Value Control Property '&1' assigned to property '&2' has incorrect value |
200 | Text based on OTR may not be initial |
201 | Text based on OTR could not be read |
202 | Conversion '&1' of property '&2' and move to data container failed |
203 | Conversion for select option &1 failed |
204 | Call '&1' for '&2' failed |
205 | Error in '&1' for '&2' without T100 message information |
206 | Unknown transport error for object '&1' |
207 | Technical model name or version not supplied |
208 | Problem with Model Provider Class '&1' |
209 | X-CSRF protection needed for Read Access Logging (RAL) |
210 | No content-id found in batch request for content-id-reference '&1' |
211 | Navigation not implemented for entity type '&1' |
212 | Changeset operation type '&1' not supported for entity type '&2' |
213 | No key set for content-id-ref '&1' |
214 | No key table found for content-id-reference '&1' |
215 | Entity Set '&1' has no media type. It cannot support a 'Context Token' |
216 | Entity for type '&1' not found |
217 | Error occured while calculating SAP-MESSAGE-SCOPE |
218 | Invalid skiptoken |
219 | Invalid pagesize |
220 | Additional messages exist |
221 | Currency amount conversion failed (decimals) for property '&1' |
222 | Converted currency amount assignment failed for property '&1' |
223 | Entity Type '&1': Key property '&2' must not be technical |
224 | Entity Type '&1': Technical ETag must not be combined with other ETag |
225 | Value Control Property '&1' assigned to property '&2' not found |
226 | Technical properties not supported by hub |
227 | Value Control Properties not allowed inside a complex property |
228 | Converting the filter tree via a RANGE failed for property '&1' |
229 | HTTP client create failed (return code: '&1') |
230 | HTTP client send failed for vocabulary: '&1', '&2' (return code: '&3') |
231 | HTTP client receive failed for vocabulary: '&1', '&2' (return code: '&3') |
232 | Parser error: line '&1', column '&2' |
233 | Vocabulary document '&1', '&2': '&3' |
234 | Parsing failed for vocabulary document '&1', '&2' |
235 | Transport not specified |
236 | Transport '&1' is invalid |
237 | Add vocabulary '&1'/'&2' to transport '&3' failed (return code '&4') |
238 | Vocabulary document '&1', '&2': Not ok http status received '&3' |
239 | Documentation access for service '&1', version '&2' failed |
240 | Documentation delete for service '&1', version '&2' failed |
241 | Characteristic '&1' was not found |
242 | SAP Object Type value '&1' not assigned to OData service '&2' V '&3' |
243 | Could not retrieve SAP Object Type value for OData V2 service '&1' V '&2' |
244 | Authorization missing for using the SAP Object Type functionalities |
245 | SAP Object Type value not unassigned from OData V2 service '&1' V '&2' |
246 | Source or destination resource is locked |
247 | Invalid Edm type for 'Content-Value' type property '&2' of entity '&1' |
248 | Entity '&1' has multiple 'Content-Value' properties |
249 | URI kind supplied is not supported. |
250 | Transformation error on serialization of data for media entity '&1' |
251 | Invalid Content disposition property type, allowed is "attachment/inline" |
252 | Failed due to Operation or Field Control Violation |
253 | Request cannot be executed as dependent request failed |