SAP ABAP Message Class BCOM_EC_R (BCOM RBR: Messages for Return Codes of Router)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷
BC-SRV-COM (Application Component) Communication Services: Mail, Fax, SMS, Telephony
⤷
SBCOM_ROUTING (Package) Business Communication Rule-Based Routing
⤷
⤷
Attributes
| Message class | BCOM_EC_R | |
| Short Description | BCOM RBR: Messages for Return Codes of Router | |
| Changed On | 20000703 | |
| Last Changed At | 083147 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | The function was successfully executed | Space: object requires documentation | ||
| 2 | The function is not supported by the routing server | Space: object requires documentation | ||
| 3 | The function could not be executed | Space: object requires documentation | ||
| 4 | The function could not be executed due to lack of authorization | Space: object requires documentation | ||
| 5 | The connection to the routing server is broken | Space: object requires documentation | ||
| 6 | A system error has occurred in the routing server | Space: object requires documentation | ||
| 7 | A required resource does not exist (or not in sufficient quantity) | Space: object requires documentation | ||
| 8 | System error: &2 | Space: object requires documentation | ||
| 9 | Communication error: &2 | Space: object requires documentation | ||
| 10 | Unknown return code &3 | Space: object requires documentation | ||
| 11 | One of the destinations is already used in another scenario | Space: object requires documentation | ||
| 12 | The scenario '&3' is inconsistent | Space: object requires documentation | ||
| 13 | The channel of the destination is not known to the routing server '&1' | Space: object requires documentation | ||
| 14 | The address of the destination is invalid | Space: object requires documentation | ||
| 15 | The routing server '&1' does not support inactive scenarios | Space: object requires documentation | ||
| 16 | The scenario '&3' contains too many routing attributes | Space: object requires documentation | ||
| 17 | The scenario '&3' does not exist on the routing server '&1' | Space: object requires documentation | ||
| 18 | The agent group '&3' contains too many agents | Space: object requires documentation | ||
| 19 | The agent group '&3' contains unknown agents | Space: object requires documentation | ||
| 20 | The agent group '&3' does not exist on the routing server '&1' | Space: object requires documentation | ||
| 21 | The attribute group '&3' contains too many members | Space: object requires documentation | ||
| 22 | The attribute group '&3' does not exist on the routing server '&1' | Space: object requires documentation | ||
| 23 | Not all specified members could be deleted | Space: object requires documentation | ||
| 24 | Not all specified members could be added | Space: object requires documentation | ||
| 25 | The search field ID '&3' is unknown | Space: object requires documentation | ||
| 26 | The search table for '&3' contains too many entries | Space: object requires documentation | ||
| 27 | Not all specified entries could be deleted | Space: object requires documentation | ||
| 28 | Not all specified entries could be added/changed | Space: object requires documentation | ||
| 29 | The search table for '&3' does not exist on the routing server '&1' | Space: object requires documentation | ||
| 30 | The sender's channel is not known to the routing server '&1' | Space: object requires documentation | ||
| 31 | The address of the sender/caller is invalid | Space: object requires documentation | ||
| 32 | The download sequence cannot currently be started | Space: object requires documentation | ||
| 33 | The download sequence could not be successfully completed | Space: object requires documentation | ||
| 34 | The start of the download sequence could not be identified | Space: object requires documentation |
History
| Last changed on/by | 20000703 | SAP | |
| SAP Release Created in | 46D |