SAP ABAP Message Class /IWFND/CM_MGW (OData Channel Messages)
Basic Data
Hierarchy
☛
SAP_GWFND (Software Component) SAP Gateway Foundation
⤷ OPU-FND-CS (Application Component) IWF Common Services
⤷ /IWFND/COS_SHARED_OBJECTS (Package) GW Framework - Shared Objects among Package /IWFND/COS
⤷ OPU-FND-CS (Application Component) IWF Common Services
⤷ /IWFND/COS_SHARED_OBJECTS (Package) GW Framework - Shared Objects among Package /IWFND/COS
Attributes
Message class | /IWFND/CM_MGW | |
Short Description | OData Channel Messages | |
Changed On | 20141120 | |
Last Changed At | 212332 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | The RFC call was not successful because of system failure '&1' | The short text describes the object sufficiently | |
2 | 001 | The RFC call was not successful because of communication failure '&1' | The short text describes the object sufficiently | |
3 | 002 | The RFC call was not successful for unknown reasons | The short text describes the object sufficiently | |
4 | 003 | Start data remote exchange for operation '&1' | The short text describes the object sufficiently | |
5 | 004 | Finished processing the remote data exchange | The short text describes the object sufficiently | |
6 | 005 | Executing data exchange: RFC '&1', destination '&2' | The short text describes the object sufficiently | |
7 | 006 | Serializing data to XML: transformation '&1' | The short text describes the object sufficiently | |
8 | 007 | Deserializing data from XML: transformation '&1' | The short text describes the object sufficiently | |
9 | 008 | Serialization of XML failed via transformation '&1' | The short text describes the object sufficiently | |
10 | 009 | Deserialization of XML failed via transformation '&1' | The short text describes the object sufficiently | |
11 | 010 | Failed to retrieve data container for entity '&1' | The short text describes the object sufficiently | |
12 | 011 | &1 | The short text describes the object sufficiently | |
13 | 012 | &1 | The short text describes the object sufficiently | |
14 | 013 | System alias '&1' not available | The short text describes the object sufficiently | |
15 | 014 | Package '&1' not available | The short text describes the object sufficiently | |
16 | 015 | Model for the service group '&1' not found | The short text describes the object sufficiently | |
17 | 016 | Error while creating the field catalog for ALV | The short text describes the object sufficiently | |
18 | 017 | Service '&1' already exists | The short text describes the object sufficiently | |
19 | 018 | Service group name '&1' '&2' '&3' still existing | The short text describes the object sufficiently | |
20 | 019 | ICF Service '&1' already enabled; nothing to do | The short text describes the object sufficiently | |
21 | 020 | ICF-Service '&1' enabled | The short text describes the object sufficiently | |
22 | 021 | ICF-Service '&1' disabled | The short text describes the object sufficiently | |
23 | 022 | ICF-Service '&1' not enabled | The short text describes the object sufficiently | |
24 | 023 | ICF-Service '&1' not disabled | The short text describes the object sufficiently | |
25 | 024 | ICF-Service '&1' already disabled; nothing to do | The short text describes the object sufficiently | |
26 | 025 | ICF-Service '&1' not active; browser will not be started | The short text describes the object sufficiently | |
27 | 026 | URL for Service '&1' not available | The short text describes the object sufficiently | |
28 | 027 | Action was cancelled by the user | The short text describes the object sufficiently | |
29 | 028 | Namespace &1 not allowed; use 'Y' or 'Z' as first character in the prefix | The short text describes the object sufficiently | |
30 | 029 | Service '&1' is locked | The short text describes the object sufficiently | |
31 | 030 | Service '&1' is not available | The short text describes the object sufficiently | |
32 | 031 | OData Channel starts operation '&1' | The short text describes the object sufficiently | |
33 | 032 | OData Channel finished operation successfully | The short text describes the object sufficiently | |
34 | 033 | OData Channel failed to finish operation | The short text describes the object sufficiently | |
35 | 034 | OData Channel failed | The short text describes the object sufficiently | |
36 | 035 | Mark at least one entry | The short text describes the object sufficiently | |
37 | 036 | Cannot refresh ALV service group | The short text describes the object sufficiently | |
38 | 037 | Service not available; browser will not be started | The short text describes the object sufficiently | |
39 | 038 | List refreshed | The short text describes the object sufficiently | |
40 | 039 | Customizing table '&1' locked by user '&2' | The short text describes the object sufficiently | |
41 | 040 | Cannot delete local service | The short text describes the object sufficiently | |
42 | 041 | Service '&1' reset | The short text describes the object sufficiently | |
43 | 042 | No authority to change service '&1' | The short text describes the object sufficiently | |
44 | 043 | Action not allowed for this service | The short text describes the object sufficiently | |
45 | 044 | You are not authorized to work with Web Services | The short text describes the object sufficiently | |
46 | 045 | You do not have the authority to activate an ICF service | The short text describes the object sufficiently | |
47 | 046 | Method '&1' not implemented in data provider class | The short text describes the object sufficiently | |
48 | 047 | Package '&1' does not exist | The short text describes the object sufficiently | |
49 | 048 | Version has to be larger than zero | The short text describes the object sufficiently | |
50 | 049 | Changeset operation data collected | The short text describes the object sufficiently | |
51 | 050 | Changeset processing failed | Space: object requires documentation | |
52 | 051 | Resource not found for the segment '&' | The short text describes the object sufficiently | |
53 | 052 | &1 | The short text describes the object sufficiently | |
54 | 053 | Missing customizing; contact your system administrator | The short text describes the object sufficiently | |
55 | 054 | No system alias found for consumption model '&1' | The short text describes the object sufficiently | |
56 | 055 | Wrong GSDO group assignment for consumption model '&1' | Space: object requires documentation | |
57 | 056 | Wrong customizing; more than one role and system alias for current user | The short text describes the object sufficiently | |
58 | 057 | Operation '&1' not supported for '&2' | The short text describes the object sufficiently | |
59 | 058 | Navigation property '&1' not supported for '&2' | The short text describes the object sufficiently | |
60 | 059 | Delegation failed. Neither entity name nor function name provided. | The short text describes the object sufficiently | |
61 | 060 | Batch with changeset is not supported for current service | Space: object requires documentation | |
62 | 061 | Unsupported combination of query options | The short text describes the object sufficiently | |
63 | 062 | Navigation Property '&1' not supported for '&2' with ref constraint '&3' | The short text describes the object sufficiently | |
64 | 063 | Changeset in multiple origin context not supported | Space: object requires documentation | |
65 | 064 | Changeset containing different system aliases not supported | Space: object requires documentation | |
66 | 065 | Metadata has been loaded successfully | Space: object requires documentation | |
67 | 066 | Loading the metadata for service '&1' failed. Check the error log. | The short text describes the object sufficiently | |
68 | 067 | Soft-state mode for service activated. | The short text describes the object sufficiently | |
69 | 068 | Soft-state mode for service deactivated. | The short text describes the object sufficiently | |
70 | 070 | Sending notifications for service '&1', namespace '&2', version '&3' | The short text describes the object sufficiently | |
71 | 071 | Notifications successfully sent to consumers | The short text describes the object sufficiently | |
72 | 072 | Failed to send notifications to consumers | The short text describes the object sufficiently | |
73 | 073 | Failed to send notification for user '&1' to address '&2' | The short text describes the object sufficiently | |
74 | 074 | User not found. Notification cannot be stored. | The short text describes the object sufficiently | |
75 | 075 | Bulk notification processing started | The short text describes the object sufficiently | |
76 | 076 | Bulk notification processing completed | The short text describes the object sufficiently | |
77 | 077 | No implementation found for Feed Aggregator BAdI | The short text describes the object sufficiently | |
78 | 078 | Bulk notification processing failed | The short text describes the object sufficiently | |
79 | 080 | ***** BADI for Data Provider Delegator ***** | The short text describes the object sufficiently | |
80 | 081 | Data Provider Delegator called: Service=&1, Namespace=&2, Version=&3 | The short text describes the object sufficiently | |
81 | 082 | Data Provider Delegator succeeded | The short text describes the object sufficiently | |
82 | 083 | Data Provider Delegator failed | The short text describes the object sufficiently | |
83 | 084 | No model was found for service '&1' and entity '&2' | The short text describes the object sufficiently | |
84 | 085 | Data Provider Delegator instantiated data provider class '&1' | The short text describes the object sufficiently | |
85 | 086 | Data Provider Delegator resolves external link from '&1' to '&2' | The short text describes the object sufficiently | |
86 | 087 | Metadata Routing is based on IWF customizing (GSDO Group based) | The short text describes the object sufficiently | |
87 | 088 | Data Provider Instantiation for service '&1' is based on fallback. | Space: object requires documentation | |
88 | 089 | System Alias not found. | The short text describes the object sufficiently | |
89 | 090 | Invalid Delta Token | The short text describes the object sufficiently | |
90 | 091 | ETag handling is not supported for function import | The short text describes the object sufficiently | |
91 | 092 | Target Entityset not found | The short text describes the object sufficiently | |
92 | 099 | Unspecified error occurred. See Error Context for more details | The short text describes the object sufficiently | |
93 | 100 | &1&2 | The short text describes the object sufficiently | |
94 | 101 | ******** OData V4 ************* | The short text describes the object sufficiently | |
95 | 102 | The processing of the OData V4 request failed | The short text describes the object sufficiently | |
96 | 150 | ********Notification related************* | The short text describes the object sufficiently | |
97 | 151 | Notification Sending failed; Subscribed collection does not exist | The short text describes the object sufficiently | |
98 | 152 | Not authorized, bulk notification sending failed | The short text describes the object sufficiently | |
99 | 153 | Not authorized, notification sending failed | The short text describes the object sufficiently | |
100 | 154 | Error while transforming inbound notification xml | The short text describes the object sufficiently | |
101 | 180 | ********CATALOGSERVICE************* | The short text describes the object sufficiently | |
102 | 181 | Filter by '&1' is not supported by Catalogservice for this entity set | The short text describes the object sufficiently | |
103 | 182 | This combination of filter query is not supported by Catalogservice | The short text describes the object sufficiently | |
104 | 200 | ***********MGW Pull Based Notifications******** | The short text describes the object sufficiently | |
105 | 201 | Username &1 is invalid | The short text describes the object sufficiently | |
106 | 202 | Service Document &1 does not exist | The short text describes the object sufficiently | |
107 | 203 | Date/Time from &1 &2 is greater than Date/Time to &3 &4 | The short text describes the object sufficiently | |
108 | 204 | Notification Serializer could not be instantiated | The short text describes the object sufficiently | |
109 | 205 | No authorization for recipient based filter in NOTIFICATIONSTORE | The short text describes the object sufficiently | |
110 | 206 | No authorization to read other recipient's notification | The short text describes the object sufficiently | |
111 | 207 | $Orderby is not supported in NOTIFICATIONSTORE service | The short text describes the object sufficiently | |
112 | 208 | Filter parameter '&1' is not supported | The short text describes the object sufficiently | |
113 | 209 | Error while deleting single notification from database | The short text describes the object sufficiently | |
114 | 230 | ***********MGW Facade******** | The short text describes the object sufficiently | |
115 | 231 | Gateway not active | The short text describes the object sufficiently | |
116 | 250 | ***** Multi Destination Compostion ****** | The short text describes the object sufficiently | |
117 | 251 | No support by Service '&1' for System Alias '&2' - Property 'SAP__Origin' | The short text describes the object sufficiently | |
118 | 252 | For HTTP Header field '&1' MDC found different values during merge. | The short text describes the object sufficiently | |
119 | 253 | No support for complex filter expression including Property 'SAP__Origin' | The short text describes the object sufficiently | |
120 | 254 | Calling the backend systems &1 triggered an error. | The short text describes the object sufficiently | |
121 | 255 | The sort operation is not supported in this context | The short text describes the object sufficiently | |
122 | 300 | *** Program /IWFND/R_MGW_REGISTRATION *** | The short text describes the object sufficiently | |
123 | 301 | Service cannot be deleted, delete ICF Node first | Space: object requires documentation | |
124 | 302 | ICF-Node '&1' for Service '&2' is active | The short text describes the object sufficiently | |
125 | 303 | ICF-Node '&1' for Service '&2' activated | The short text describes the object sufficiently | |
126 | 304 | ICF-Node '&1' for Service '&2' deactivated | The short text describes the object sufficiently | |
127 | 305 | ICF-Node '&1' for Service '&2' deleted | The short text describes the object sufficiently | |
128 | 306 | Selected Service and Service for deletion are not identical | The short text describes the object sufficiently | |
129 | 307 | Service cannot be deleted, delete Destination Assignment(s) first | The short text describes the object sufficiently | |
130 | 308 | No Backend Services found | The short text describes the object sufficiently | |
131 | 309 | Service '&1' successfully created | The short text describes the object sufficiently | |
132 | 310 | Service '&1' successfully deleted | The short text describes the object sufficiently | |
133 | 311 | 'Call Browser' failed | The short text describes the object sufficiently | |
134 | 312 | No Model assigned to Service '&1'; assign Model first | The short text describes the object sufficiently | |
135 | 313 | No System Alias Assignment and GSDO Group maintained | The short text describes the object sufficiently | |
136 | 314 | Backend Services are already registered for System Alias '&1' | The short text describes the object sufficiently | |
137 | 315 | Backend System '&1' does not contain required software components | The short text describes the object sufficiently | |
138 | 316 | Empty import parameter in function module '&1' | The short text describes the object sufficiently | |
139 | 317 | Service '&1' successfully enabled for OAuth | The short text describes the object sufficiently | |
140 | 318 | Creation of OAuth scope for service '&1' failed: '&2' | The short text describes the object sufficiently | |
141 | 319 | OAuth Scope for service '&1' already exists | The short text describes the object sufficiently | |
142 | 320 | Service '&1' was created and its metadata was loaded succesfully. | The short text describes the object sufficiently | |
143 | 321 | Service '&1' was created but its metadata could not be loaded. | The short text describes the object sufficiently | |
144 | 322 | Service '&1' does not support soft-state mode. | Space: object requires documentation | |
145 | 323 | Type BW is not supported; Sevice '&1' was not created | The short text describes the object sufficiently | |
146 | 327 | Prefix not specified but selected services are not in same name space | Space: object requires documentation | |
147 | 328 | Specify a prefix for the technical service name and technical model name | Space: object requires documentation | |
148 | 350 | *****************MDC Subscription*************** | The short text describes the object sufficiently | |
149 | 351 | Multi-destination Subscription create started | The short text describes the object sufficiently | |
150 | 352 | Multi-destination Subscription create completed | The short text describes the object sufficiently | |
151 | 353 | Multi-destination Subscriptions were created partially. Please check log. | The short text describes the object sufficiently | |
152 | 354 | Multi-destination Subscription create failed in backend &1 | The short text describes the object sufficiently | |
153 | 355 | Multi-destination Subscription query started | The short text describes the object sufficiently | |
154 | 356 | Multi-destination Subscription query completed | The short text describes the object sufficiently | |
155 | 357 | Multi-destination Subscriptions were read partially. Please check log. | The short text describes the object sufficiently | |
156 | 358 | Multi-destination Subscription query failed in backend &1 | The short text describes the object sufficiently | |
157 | 359 | Multi-destination Subscription update started | The short text describes the object sufficiently | |
158 | 360 | Multi-destination Subscription update completed | The short text describes the object sufficiently | |
159 | 361 | Multi-destination Subscriptions were updated partially. Please check log. | The short text describes the object sufficiently | |
160 | 362 | Multi-destination Subscription update failed in backend &1 | The short text describes the object sufficiently | |
161 | 363 | Multi-destination Subscription delete started | The short text describes the object sufficiently | |
162 | 364 | Multi-destination Subscription delete completed | The short text describes the object sufficiently | |
163 | 365 | Multi-destination Subscriptions were deleted partially. Please check log. | The short text describes the object sufficiently | |
164 | 366 | Multi-destination Subscription delete failed in backend &1 | The short text describes the object sufficiently | |
165 | 367 | Multi-destination Subscription read started | The short text describes the object sufficiently | |
166 | 368 | Multi-destination Subscription read completed | The short text describes the object sufficiently | |
167 | 369 | Multi-destination Subscription read failed in backend &1 | The short text describes the object sufficiently | |
168 | 370 | System Alias specification not supported in Multi-destination context | The short text describes the object sufficiently | |
169 | 371 | Multi-destination Subscription create failed | The short text describes the object sufficiently | |
170 | 372 | Multi-destination Subscription update failed | The short text describes the object sufficiently | |
171 | 373 | Multi-destination Subscription delete failed | The short text describes the object sufficiently | |
172 | 400 | **************Subscription********************** | The short text describes the object sufficiently | |
173 | 401 | Subscription create failed | The short text describes the object sufficiently | |
174 | 402 | Subscription read failed | The short text describes the object sufficiently | |
175 | 403 | Subscription update failed | The short text describes the object sufficiently | |
176 | 404 | Subscription delete failed | The short text describes the object sufficiently | |
177 | 405 | The short text describes the object sufficiently | ||
178 | 450 | **********Feed Aggregator: Bulk Notification********** | The short text describes the object sufficiently | |
179 | 451 | Notification processing started by Queue: &1 | The short text describes the object sufficiently | |
180 | 452 | Notification processing completed by Queue: &1 | The short text describes the object sufficiently | |
181 | 453 | Function Module &1 does not exist | The short text describes the object sufficiently | |
182 | 528 | Business Object disclosed to a client in the response. See details. | The short text describes the object sufficiently | |
183 | 529 | &1 of the Business Object were disclosed to a client in the response. | The short text describes the object sufficiently | |
184 | 530 | Entity disclosed to a client in the response. See details. | The short text describes the object sufficiently | |
185 | 531 | Properties &1 of the Entity were disclosed to a client in the response. | The short text describes the object sufficiently |
History
Last changed on/by | 20141120 | SAP | |
SAP Release Created in | 250 |