/IWFND/CM_MGW - OData Channel Messages
The following messages are stored in message class /IWFND/CM_MGW: OData Channel Messages.
It is part of development package /IWFND/COS_SHARED_OBJECTS in software component OPU-GW-V4. This development package consists of objects that can be grouped under "SAP GW Framework - Shared Objects among Package /IWFND/COS".
It is part of development package /IWFND/COS_SHARED_OBJECTS in software component OPU-GW-V4. This development package consists of objects that can be grouped under "SAP GW Framework - Shared Objects among Package /IWFND/COS".
Message Nr ▲ | Message Text |
---|---|
000 | The RFC call was not successful because of system failure '&1' |
001 | The RFC call was not successful because of communication failure '&1' |
002 | The RFC call was not successful for unknown reasons |
003 | Start data remote exchange for operation '&1' |
004 | Finished processing the remote data exchange |
005 | Executing data exchange: RFC '&1', destination '&2' |
006 | Serializing data to XML: transformation '&1' |
007 | Deserializing data from XML: transformation '&1' |
008 | Serialization of XML failed via transformation '&1' |
009 | Deserialization of XML failed via transformation '&1' |
010 | Failed to retrieve data container for entity '&1' |
011 | &1 |
012 | &1 |
013 | System alias '&1' not available |
014 | Package '&1' not available |
015 | Model for the service group '&1' not found |
016 | Error while creating the field catalog for ALV |
017 | Service '&1' already exists |
018 | Service group name '&1' '&2' '&3' still existing |
019 | ICF Service '&1' already enabled; nothing to do |
020 | ICF-Service '&1' enabled |
021 | ICF-Service '&1' disabled |
022 | ICF-Service '&1' not enabled |
023 | ICF-Service '&1' not disabled |
024 | ICF-Service '&1' already disabled; nothing to do |
025 | ICF-Service '&1' not active; browser will not be started |
026 | URL for Service '&1' not available |
027 | Action was cancelled by the user |
028 | Namespace &1 not allowed; use 'Y' or 'Z' as first character in the prefix |
029 | Service '&1' is locked |
030 | Service '&1' is not available |
031 | OData Channel starts operation '&1' |
032 | OData Channel finished operation successfully |
033 | OData Channel failed to finish operation |
034 | OData Channel failed |
035 | Mark at least one entry |
036 | Cannot refresh ALV service group |
037 | Service not available; browser will not be started |
038 | List refreshed |
039 | Customizing table '&1' locked by user '&2' |
040 | Cannot delete local service |
041 | Service '&1' reset |
042 | No authority to change service '&1' |
043 | Action not allowed for this service |
044 | You are not authorized to work with Web Services |
045 | You do not have the authority to activate an ICF service |
046 | Method '&1' not implemented in data provider class |
047 | Package '&1' does not exist |
048 | Version has to be larger than zero |
049 | Changeset operation data collected |
050 | Changeset processing failed |
051 | Resource not found for the segment '&' |
052 | &1 |
053 | Missing customizing; contact your system administrator |
054 | No system alias found for consumption model '&1' |
055 | Wrong GSDO group assignment for consumption model '&1' |
056 | Wrong customizing; more than one role and system alias for current user |
057 | Operation '&1' not supported for '&2' |
058 | Navigation property '&1' not supported for '&2' |
059 | Delegation failed. Neither entity name nor function name provided. |
060 | Batch with changeset is not supported for current service |
061 | Unsupported combination of query options |
062 | Navigation Property '&1' not supported for '&2' with ref constraint '&3' |
063 | Changeset in multiple origin context not supported |
064 | Changeset containing different system aliases not supported |
065 | Metadata has been loaded successfully |
066 | Loading the metadata for service '&1' failed. Check the error log. |
067 | Soft-state mode for service activated. |
068 | Soft-state mode for service deactivated. |
069 | POST not supported across navigation properties for composition services |
070 | Sending notifications for service '&1', namespace '&2', version '&3' |
071 | Notifications successfully sent to consumers |
072 | Failed to send notifications to consumers |
073 | Failed to send notification for user '&1' to address '&2' |
074 | User not found. Notification cannot be stored. |
075 | Bulk notification processing started |
076 | Bulk notification processing completed |
077 | No implementation found for Feed Aggregator BAdI |
078 | Bulk notification processing failed |
079 | MIME Type '&1' is not supported |
080 | ***** BADI for Data Provider Delegator ***** |
081 | Data Provider Delegator called: Service=&1, Namespace=&2, Version=&3 |
082 | Data Provider Delegator succeeded |
083 | Data Provider Delegator failed |
084 | No model was found for service '&1' and entity '&2' |
085 | Data Provider Delegator instantiated data provider class '&1' |
086 | Data Provider Delegator resolves external link from '&1' to '&2' |
087 | Metadata Routing is based on IWF customizing (GSDO Group based) |
088 | Data Provider Instantiation for service '&1' is based on fallback. |
089 | System Alias not found. |
090 | Invalid Delta Token |
091 | eTag handling not supported for this function import |
092 | Target Entityset not found |
093 | Format 'xslx' is not supported for this request |
094 | Invalid eTag format - The if-match header field has an invalid format |
095 | Invalid property &1 in query option totals |
096 | PATCH requests require components to be updated |
097 | Origin segment parameter not supported for Co-deployed services |
098 | X-CSRF token is needed for Batch Processing with modifying operation |
099 | Unspecified error occurred. See Error Context for more details |
100 | &1&2 |
101 | ******** OData V4 ************* |
102 | The processing of the OData V4 request failed |
103 | This service use Read Access Logging. X-CSRF token is required. |
104 | You are in read-only mode |
105 | Service group '&1' not found in backend for system alias '&2' |
106 | Release status for service group '&1' refreshed |
107 | Release status for service group '&1' is current |
108 | No Authority for Transaktion /IWFND/ROUTING |
109 | Context-id-reference '&1' found but without context-id |
110 | Content-id '&1' missing in any previous changeset |
120 | Co-deployment is not supported |
121 | Processing mode "OData on Backend": Error occurred in backend system. |
130 | &1&2&3&4 |
150 | ********Notification related************* |
151 | Notification Sending failed; Subscribed collection does not exist |
152 | Not authorized, bulk notification sending failed |
153 | Not authorized, notification sending failed |
154 | Error while transforming inbound notification xml |
180 | ********CATALOGSERVICE************* |
181 | Filter by '&1' is not supported by Catalogservice for this entity set |
182 | This combination of filter query is not supported by Catalogservice |
190 | Batch request processing failed in backend (&1) |
200 | ***********MGW Pull Based Notifications******** |
201 | Username &1 is invalid |
202 | Service Document &1 does not exist |
203 | Date/Time from &1 &2 is greater than Date/Time to &3 &4 |
204 | Notification Serializer could not be instantiated |
205 | No authorization for recipient based filter in NOTIFICATIONSTORE |
206 | No authorization to read other recipient's notification |
207 | $Orderby is not supported in NOTIFICATIONSTORE service |
208 | Filter parameter '&1' is not supported |
209 | Error while deleting single notification from database |
230 | ***********MGW Facade******** |
231 | SAP Gateway not active |
240 | Transformation of the entity set '&1' to format xslx failed. |
250 | ***** Multi Destination Compostion ****** |
251 | No support by Service '&1' for System Alias '&2' - Property 'SAP__Origin' |
252 | For HTTP Header field '&1' MDC found different values during merge. |
253 | No support for complex filter expression including Property 'SAP__Origin' |
254 | Calling the backend systems &1 triggered an error. |
255 | The sort operation is not supported in this context |
256 | Error occured for some backends; execute request with URI option: '&1' |
257 | "Co-deployement only" cannot be used because of assigned system alias(es) |
259 | Change the processing mode to "routing-based" before adding system alias |
260 | "Inherited" cannot be used because of assigned system alias(es) |
261 | Cache cannot be deleted for 'Inherited' service |
300 | *** Program /IWFND/R_MGW_REGISTRATION *** |
301 | Service cannot be deleted, delete ICF Node first |
302 | ICF-Node '&1' for Service '&2' is active |
303 | ICF-Node '&1' for Service '&2' activated |
304 | ICF-Node '&1' for Service '&2' deactivated |
305 | ICF-Node '&1' for Service '&2' deleted |
306 | Selected Service and Service for deletion are not identical |
307 | Service cannot be deleted, delete system aliases first |
308 | No Backend Services found |
309 | Service '&1' successfully created |
310 | Service '&1' successfully deleted |
311 | 'Call Browser' failed |
312 | No Model assigned to Service '&1'; assign Model first |
313 | No System Alias Assignment and GSDO Group maintained |
314 | Backend Services are already registered for System Alias '&1' |
315 | Backend System '&1' does not contain required software components |
316 | Empty import parameter in function module '&1' |
317 | Service '&1' successfully enabled for OAuth |
318 | Creation of OAuth scope for service '&1' failed: '&2' |
319 | OAuth Scope for service '&1' already exists |
320 | Service '&1' was created and its metadata was loaded successfully. |
321 | Service '&1' was created but its metadata could not be loaded. |
322 | Service '&1' does not support soft state mode. |
323 | Type BW is not supported; Sevice '&1' was not created |
324 | Soft state activation failed; ICF-Node '&1' missing for service '&2' |
325 | Soft state activation failed; session time-out of service '&1' is '&2' |
326 | Soft state activation failed; could not load metadata of service '&1' |
327 | Prefix not specified but selected services are not in same name space |
328 | Specify a prefix for the technical service name and technical model name |
350 | *****************MDC Subscription*************** |
351 | Multi-destination Subscription create started |
352 | Multi-destination Subscription create completed |
353 | Multi-destination Subscriptions were created partially. Please check log. |
354 | Multi-destination Subscription create failed in backend &1 |
355 | Multi-destination Subscription query started |
356 | Multi-destination Subscription query completed |
357 | Multi-destination Subscriptions were read partially. Please check log. |
358 | Multi-destination Subscription query failed in backend &1 |
359 | Multi-destination Subscription update started |
360 | Multi-destination Subscription update completed |
361 | Multi-destination Subscriptions were updated partially. Please check log. |
362 | Multi-destination Subscription update failed in backend &1 |
363 | Multi-destination Subscription delete started |
364 | Multi-destination Subscription delete completed |
365 | Multi-destination Subscriptions were deleted partially. Please check log. |
366 | Multi-destination Subscription delete failed in backend &1 |
367 | Multi-destination Subscription read started |
368 | Multi-destination Subscription read completed |
369 | Multi-destination Subscription read failed in backend &1 |
370 | System Alias specification not supported in Multi-destination context |
371 | Multi-destination Subscription create failed |
372 | Multi-destination Subscription update failed |
373 | Multi-destination Subscription delete failed |
390 | Context token '&1' is not valid; Needs to be a valid timestamp |
391 | Context token '&1' is in the future |
392 | Context token requests also need "sap-language" as URL parameter |
393 | Context token requests also need "sap-client" as URL parameter |
394 | Context token requests has incorrect "sap-language" URL parameter |
400 | **************Subscription********************** |
401 | Subscription create failed |
402 | Subscription read failed |
403 | Subscription update failed |
404 | Subscription delete failed |
405 | |
450 | **********Feed Aggregator: Bulk Notification********** |
451 | Notification processing started by Queue: &1 |
452 | Notification processing completed by Queue: &1 |
453 | Function Module &1 does not exist |
528 | Business Object disclosed to a client in the response. See details. |
529 | &1 of the Business Object were disclosed to a client in the response. |
530 | Entity disclosed to a client in the response. See details. |
531 | Properties &1 of the Entity were disclosed to a client in the response. |
535 | An exception occurred when accessing cached data in shared memory |
536 | Function import eTag handling not supported for http method '&1' |
537 | eTag handling not supported for http method '&1' |
538 | The entity type '&1' is not defined in the metadata |