/IWXBE/CORE -
The following messages are stored in message class /IWXBE/CORE: .
It is part of development package /IWXBE/CORE_MESSAGES in software component OPU-XBE. This development package consists of objects that can be grouped under "SAP Unified Eventing - Core - Message Classes".
It is part of development package /IWXBE/CORE_MESSAGES in software component OPU-XBE. This development package consists of objects that can be grouped under "SAP Unified Eventing - Core - Message Classes".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Fatal error in enterprise eventing |
| 001 | Internal error in enterprise eventing |
| 002 | Internal error in enterprise eventing runtime |
| 003 | Internal error in enterprise eventing setup |
| 004 | '&1' '&2' '&3' '&4' |
| 005 | Active |
| 006 | Inactive |
| 007 | Service '&1' does already exist |
| 008 | Service name must not be initial |
| 009 | Service name '&1' contains invalid characters |
| 010 | Protocol name must not be initial |
| 011 | Protocol name '&1' is invalid |
| 012 | Topic entered more than once |
| 013 | Consumer '&1' for topic '&2' and channel '&3' does not exist |
| 014 | Already marked for deletion |
| 015 | Class required for activation |
| 016 | Class '&1' could not be found |
| 017 | Class '&1' cannot be used; implementation is set to abstract |
| 018 | Class '&1' cannot be used; inheritence from class '&2' required |
| 019 | Class '&1' cannot be used; derive an own sub-class |
| 020 | Class '&1' cannot be used; runtime internal class |
| 021 | Service name '&1' is invalid, Y* or Z* name space is not allowed |
| 022 | Consumer '&1' is not registered |
| 023 | Service '&1' is not active |
| 024 | Service '&1' load error using class '&2' |
| 025 | Service '&1' failed to provide producer '&2' |
| 026 | Service '&1' failed to provide consumer '&2' |
| 027 | Service '&1' failed to provide topic browser |
| 028 | Service '&1' failed to provide event tracker |
| 029 | Service '&1' failed to provide consume browser |
| 030 | Parameter name must not be initial |
| 031 | Parameter name '&1' contains invalid characters |
| 032 | Parameter type '&1' cannot be used; select a data element (char or numc) |
| 033 | Parameter '&1' does not allow value '&2' |
| 034 | Parameter '&1' does not exist in setup. |
| 035 | Parameter '&1' does not exist for channel '&2' |
| 036 | For Channel '&1' |
| 037 | Parameter '&1' does already exist for channel '&2' |
| 038 | Only existing and unchanged parameter sets can be deleted |
| 039 | Channel '&1' could not be saved |
| 040 | Channel '&1' does not exist |
| 041 | Channel '&1' is not active |
| 042 | Channel '&1' setup error, no destination defined |
| 043 | Channel '&1' setup error, protocol '&2' not supported |
| 044 | Invalid mode selected |
| 045 | Channel '&1' load error using class '&2' |
| 046 | Channel '&1' already exists |
| 047 | Invalid HTTP Destination |
| 048 | Object requested is currently locked by user '&1' |
| 049 | Transactional field value invalid; Enter ' ' or 'X' |
| 050 | Payload data structure not declared for topic '&1' |
| 051 | Payload data structure mismatch for topic '&1' |
| 052 | Channel description must not be initial |
| 053 | Destination '&1' does not exist |
| 054 | Service for topic '&1' does not exist |
| 055 | Topic '&1' is already subscribed |
| 056 | Invalid consumer '&1' |
| 057 | Invalid topic '&1' |
| 058 | One or more topic filters are not assigned to channel '&1' |
| 059 | Topic filter '&1' already exists for channel '&2' |
| 060 | Topic syntax error |
| 061 | Invalid characters found in segment '&1' |
| 062 | Empty topic segment not allowed, pos &1 in '&2&3&4' |
| 063 | Unknown service topic value '&1' |
| 064 | Invalid service topic space '&1'; use 2 to 4 characters (A-Z, a-z, 0-9) |
| 065 | Invalid topic space '&1'. Enter exactly 3 segments (A-Z, a-z, 0-9) |
| 066 | Invalid topic filter '&1' |
| 067 | The provided topic '&1' is invalid |
| 068 | Enter a unique topic space for the service &1 |
| 069 | Channel name '&1' invalid; Allowed character set {A-Z,0-9,'_'} |
| 070 | Channel name must not be initial |
| 071 | The requested object is locked by another transaction |
| 072 | Internal error from enqueue server |
| 073 | Channel name is mandatory to bind a topic filter |
| 074 | Topic space XBE is reserved for service TEST_SERVICE |
| 075 | Topic filter with more than 20 segments not allowed |
| 076 | Invalid topic space '&1'.Rule: 4 characters -'/sap/' - installed product. |
| 077 | Invalid topic space '&1'. Enter max. 4 characters (A-Z, a-z, 0-9). |
| 078 | Not implemented |
| 079 | Service topic space '&1' already exists |
| 080 | Missing authorization; authority check for object '&1' and '&2' failed |
| 081 | Missing authorization; authority check for object '&1' failed |
| 082 | Event payload exceeds the limit of &1 MB. |
| 083 | Runtime channel created with destination '&1' |
| 084 | Payload structure found '&1' |
| 085 | '&1' event channel binding(s) found |
| 086 | Event producer '&1' created |
| 087 | Event payload created |
| 088 | Event '&1' published via channel '&2' |
| 089 | Payload structure not found |
| 090 | Event channel binding not found |
| 091 | Event producer not created |
| 092 | Event payload not created |
| 093 | Event '&1' not published to channel |
| 094 | Daemon initialized for channel '&1' |
| 095 | Daemon starting for channel '&1' |
| 096 | Error when starting Daemon for channel '&1' |
| 097 | Daemon channel publishing event |
| 098 | Daemon channel error at publishing event |
| 099 | Daemon channel disconnecting |
| 100 | Attached to daemon |
| 101 | Daemon started for channel '&1' |
| 102 | Daemon on start error for channel '&1' |
| 103 | Daemon publishing event |
| 104 | Daemon error during publishing event |
| 105 | Daemon on error for channel '&1' |
| 106 | Daemon for channel '&1' stopped |
| 107 | Daemon restarted for channel '&1' |
| 108 | Error at Daemon on restart |
| 109 | Daemon on Server shutdown for channel '&1' |
| 110 | Daemon on System shutdown for channel '&1' |
| 111 | Daemon before restart by system for channel '&1' |
| 112 | MQTT channel '&1' initialized - MQTT client created |
| 113 | MQTT channel '&1' initialized - OAuth2.0 client created |
| 114 | Error while getting MQTT client for channel '&1' |
| 115 | MQTT channel '&1' connecting - MQTT client connected |
| 116 | MQTT channel connecting - MQTT client connection error |
| 117 | MQTT channel '&3' published the QOS '&1' event '&2' |
| 118 | MQTT channel error during publishing event |
| 119 | MQTT connection disconnected for channel '&1' |
| 120 | MQTT connection request sent |
| 121 | MQTT connection acknowledge received for channel '&1' |
| 122 | MQTT connection - error during message reception |
| 123 | MQTT channel error - MQTT connection error |
| 124 | MQTT channel connecting - MQTT client reconnected |
| 125 | MQTT channel connecting - MQTT client reconnection error |
| 126 | MQTT channel '&3' acknowledged the QOS '&1' event '&2' |
| 127 | Error while disconnecting the MQTT connection for channel '&1' |
| 128 | One or more topic filters entered are exceeding 85 characters |
| 129 | Topic filter must not have duplicate entries |
| 130 | Max reconnect reached, channel '&1' deactivated |
| 131 | Max reconnect reached, channel '&1' could not be deactivated |
| 132 | Channel '&1' cannot be renamed |
| 133 | Daemon error on before restart by system |
| 134 | Daemon on server shutdown no active host found in system |
| 135 | Error while getting channel instance or initialization of MQTT or Daemon |
| 136 | No active channels found to publish event |
| 137 | Processing acknowledged events for channel '&1' |
| 138 | No active channel found for topic '&1' |
| 139 | Service tracker not created for service '&1' |
| 140 | AMC ping sent for channel '&1' |
| 141 | Daemon processing the received AMC ping for channel '&1' |
| 142 | Channel '&1' deactivated |
| 143 | Subscription '&1' in channel '&2' does already exist |
| 144 | MQTT on connection - No events to be picked for channel '&1' |
| 145 | MQTT connection disconnected for channel '&1' and events are reset. |
| 146 | MQTT on disconnect for channel '&1' - Error while starting timer |
| 147 | MQTT on disconnect for channel '&1' - Error in oauth configuration |
| 148 | MQTT on disconnect for channel '&1' - Error in destination |
| 149 | MQTT on disconnect for channel '&1' - Error when getting envelope |
| 150 | Error while creating OAuth2.0 client for channel '&1' |
| 151 | MQTT connection not established in reconnect attempt '&1' |
| 152 | MQTT connection not established |
| 153 | MQTT on timeout for channel '&1' - error while starting timer |
| 154 | Daemon on start - error while stopping started Daemon for channel '&1' |
| 155 | Daemon for channel '&1' stopped on start |
| 156 | MQTT on timeout triggered for channel '&1', connection attempt '&2' |
| 157 | MQTT on timeout triggered for channel '&1' |
| 158 | Error at Daemon on stop |
| 159 | Error at Daemon on error for channel '&1' |
| 160 | Daemon on error - restarting websocket for channel '&1' |
| 161 | Accepting daemon for channel '&1' |
| 162 | Rejecting daemon for channel '&1' |
| 163 | Error at Daemon on accept |
| 164 | Error at Daemon on system shutdown |
| 165 | Error while processing the received AMC ping for stopping daemon |
| 166 | Error while processing the received AMC ping |
| 167 | Error at Daemon on server shutdown while starting daemon |
| 168 | Error at Daemon on server shutdown while getting list of daemons |
| 169 | Error at Daemon on server shutdown |
| 170 | Processing event '&1' for service '&2' in transactional mode |
| 171 | Processing event '&1' for service '&2' in non-transactional mode |
| 172 | Error while creating or attaching to an existing ccms monitoring context |
| 173 | Error while creating or attaching to an existing ccms monitoring object |
| 174 | Error while creating or attaching to an existing ccms message container |
| 175 | Error while attaching the message to corresponding CCMS container |
| 176 | I_CODE '&1' |
| 177 | I_REASON &1 &2 &3 &4 |
| 178 | Error while sending subscribe request(s) to channel. |
| 179 | Error while sending unsubscribe request(s) to channel. |
| 180 | Subscription Id: &1 |
| 181 | MQTT channel error while sending subscribe request(s). |
| 182 | MQTT channel error while sending unsubscribe request(s). |
| 183 | Daemon configuration for channel '&1' could not be created |
| 184 | Daemon configuration for channel '&1' could not be deleted |
| 185 | Existence of daemon configuration for channel '&1' could not checked |
| 186 | Topic '&1' does not exist for channel '&2' |
| 187 | Only existing and unchanged bindings can be deleted |
| 188 | Outbound topic '&1' does not exist and cannot be used as outbound binding |
| 189 | Outbound topic '&1' already exists for channel '&2' |
| 190 | Connection test for channel '&1' failed |
| 191 | Determination of communication partner ID failed |
| 192 | Mandatory parameter must not be initial |
| 193 | Subscription '&1' does not exist in channel '&2' |
| 194 | Initializing of daemon instance failed for channel '&1' |
| 195 | For service '&1' |
| 196 | Exception '&1' occurred |
| 197 | Channel '&1': '&2&3' |
| 198 | Deserialization for topic '&1' failed for description '&2' |
| 199 | Not all daemons for channel '&1' are up and running |
| 200 | Outbound Services URL is initial or invalid |
| 201 | Connection test failed. Verify Outbound Service Path URL and OAuth Detail |
| 202 | Connection test failed. Verify Outbound Services Path and Service URL. |
| 203 | Connection test failed. Verify the OAuth 2.0 Endpoints and Outbound User |
| 204 | Channel cannot be activated due to the connection test failure. |
| 205 | Verify the destination and parameter values. |
| 206 | OAuth 2.0 client profile and configuration are initial. |
| 207 | Connection test failed.Verify destination and channel parameter values |
| 208 | channel parameters OAUTH_20_CLIENT_PROFILE and OAUTH_20_CONFIGURATION. |
| 209 | channel protocol and destination. |
| 210 | Connection test successful |
| 211 | Connection test failed |
| 212 | Channel deactivated as connection test failed. |
| 213 | Channel deactivated successfully |
| 214 | Channel activated successfully |
| 215 | Channel cannot be activated as the connection test failed |
| 216 | Connection test error in MQTT. Verify Destination. |
| 217 | Connection test failed due to OAuth. Verify OAuth details |
| 218 | Channel '&1' deactivated as connection test failed while saving. |
| 219 | Protocol for channel '&1' is not available |
| 220 | You do not have authorization to perform this operation (only display) |
| 221 | Internal error from DB server while saving |
| 222 | channel protocol, destination or channel parameters. |
| 223 | Assignement of topic '&1' to channel '&2' failed |
| 224 | Removing assignement of topic '&1' from channel '&2' failed |
| 225 | Removing assignement of service '&1' from inbound binding '&2' failed |
| 226 | Assignement of service '&1' to inbound binding '&2' failed |
| 227 | Removing subscription '&1' from channel '&2' failed |
| 228 | Connection test failed. Daemon is not running. Reactivate the channel |
| 229 | Consumer '&1' for topic '&2' and channel '&3' does already exist |
| 230 | Publishing event '&1' for channel '&2' |
| 231 | Producer '&1' does not exist |
| 232 | No messaging protocol found in service key |
| 233 | Channel '&1' deactivated since max num of '&2' reconnect attempts reached |
| 234 | On server '&1' |
| 235 | Invalid time stamp |
| 236 | Update of topic space only allowed via Update by Service Key |
| 237 | Internal error in daemon |
| 238 | OAuth 2.0 client credential flow already locked for channel '&1' |
| 239 | No business data available |
| 240 | Update of topic consumer buffer failed for channel '&1' |
| 241 | Cloud Event Version '&1' not supported |
| 242 | Content type '&1' of cloud event not supported. |
| 243 | Channel '&1' uses MQTT protocol. Consumption for MQTT is not supported |
| 244 | Channel protocol can be updated to AMQP via Communication Arrangement |
| 245 | Maximum number of 10 subscriptions for channel '&1' exceeded |
| 246 | Subscription address '&1' must start with topic space '&2' of channel |
| 247 | Deprecated and no longer supported |
| 248 | Cloud Event envelope does not match version 1.0 specifications |
| 249 | Not supported |
| 250 | This method of producer handler must be implemented in sub class |
| 251 | MQTT channel does not support handling of failed events |
| 252 | Namespace of EMS exceeds '&1' characters limit for EEE framework |
| 253 | Not all AMC receivers for channel '&1' are up and running |
| 254 | AMQP application properties are empty for cloud event '&1' |
| 255 | Daemon on_error called; Code &1 - &2 |
| 256 | Content Encoding '&1' of cloud event '&2' not supported |
| 257 | Message decompression of cloud event '&1' failed |
| 301 | Error when creating OAuth2 client for channel '&1' |
| 302 | Destination not configured for the channel '&1' |
| 303 | Error when setting access token in http client for destination '&1' |
| 304 | with OAuth 2.0 profile '&1' and configuration id '&2' |
| 305 | Access token has expired for destination '&1' |
| 306 | The destination '&1' is invalid for channel '&2' |
| 307 | OAuth profile or the configuration id is missing for the channel '&1' |
| 308 | Channel '&1' is not active |
| 309 | Channel '&1' has no destination |
| 310 | Channel '&1' has an invalid destination '&2' |
| 311 | Access token lacks scope for requested profile for destination '&1' |
| 312 | OA2C not supported by Service Provider for destination '&1' |
| 313 | OAuth 2.0 client BADI implementation error for destination '&1' |
| 314 | OAuth 2.0 client runtime - Secure store error for destination '&1' |
| 315 | OAuth client id '&1' does not contain communication partner id '&2' |
| 316 | from http response |
| 317 | OAuth 2.0 client runtime - Invalid parameters for destination '&1' |
| 318 | Unknown error received from ICF for destination '&1' |
| 319 | Browser is not implemented for the service '&1' |
| 320 | Producer is not implemented for the service '&1' |
| 321 | Type '&1' is not defined |
| 322 | CommunicationPartnerId does not match for channel &1 with destination &2 |
| 323 | CommunicationPartnerId does not exist for channel &1 with destination &2 |
| 324 | CommunicationPartnerId is initial for channel &1 with destination &2 |
| 325 | RFC Error: Commnunication failure for destination &1 |
| 326 | RFC Error: Invalid state for destination &1 |
| 327 | RFC Error: Processing failure for destination &1 |
| 328 | RFC Error: Invalid timeout for destination &1 |
| 329 | Http client response code for channel '&1' is '&2': reason '&3' |
| 330 | Channel '&1' is not in background mode |
| 331 | Channel '&1' is not transactional |
| 332 | Event '&1' for channel '&2' could not be processed |
| 333 | Channel '&1' has failed undelivered events |
| 334 | Function only possible for single entry |
| 335 | Producer '&1' version '&2' deleted |
| 336 | Channel '&1' deleted |
| 337 | Service key does not contain an entry for messaging protocol amqp |
| 338 | OAuth configuration '&1' does not exist |
| 339 | OAuth configuration '&1' for profile '&2' does not exist |
| 340 | OAuth profile '&1' unknown |
| 341 | Channel protocol successfully changed to AMQP |
| 342 | Handshake with Enterprise Messaging failed |
| 343 | Topic Space does not match Namespace of Event Mesh '&1' |
| 344 | Invalid JSON string supplied |