SAP ABAP Message Class BCOM_R (Business Communication: Messages for Rule-Based Routing)
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_R | |
| Short Description | Business Communication: Messages for Rule-Based Routing | |
| Changed On | 20000906 | |
| Last Changed At | 091814 |
Messages
| # | Message | Message Short Text | Documentation status | Authorization check |
|---|---|---|---|---|
| 1 | Action canceled by user | Space: object requires documentation | ||
| 2 | The routing scenario does not exist in the database | Space: object requires documentation | ||
| 3 | First enter the routing attribute &1 in the list for the scenario | Space: object requires documentation | ||
| 4 | Server '&1' does not support any address types used in the scenario | Space: object requires documentation | ||
| 5 | No destinations are assigned to the scenario | Space: object requires documentation | ||
| 6 | The scenario has been changed, save before downloading | Space: object requires documentation | ||
| 7 | The scenario has not been changed, therefore it is not necessary to save | Space: object requires documentation | ||
| 8 | The destination '&1 (&2)' is also used in the scenario '&3' | Space: object requires documentation | ||
| 9 | The scenario cannot be saved without a description | Space: object requires documentation | ||
| 10 | The download was not performed due to inconsistencies in the scenario | Space: object requires documentation | ||
| 11 | The agent group '&1' is already assigned to the scenario | Space: object requires documentation | ||
| 12 | No connection to server '&1' | Space: object requires documentation | ||
| 13 | The scenario has to be deleted on server '&1' | Space: object requires documentation | ||
| 14 | The scenario does not exist on server '&1' | Space: object requires documentation | ||
| 15 | The scenario is obsolete on server '&1' | Space: object requires documentation | ||
| 16 | The address specifications for the scenario are incomplete on server '&1' | Space: object requires documentation | ||
| 17 | Server '&1' is not in use | Space: object requires documentation | ||
| 18 | At least one server must be assigned to the scenario | Space: object requires documentation | ||
| 19 | The scenario must contain at least one agent group with responsibility | Space: object requires documentation | ||
| 20 | Attribute &1& has the same priority as attribute &2& | Space: object requires documentation | ||
| 21 | Server '&1' does not support downloading of data by RFC | Space: object requires documentation | ||
| 22 | Server '&1' does not receive address data, assign internal router | Space: object requires documentation | ||
| 23 | Attribute &1 is not used in workflows, is not suppported by scenario | Space: object requires documentation | ||
| 24 | Assign server '&1' responsible for WF routing | Space: object requires documentation | ||
| 25 | Assign internal router | Space: object requires documentation | ||
| 26 | Assign a priority to attribute &1 | Space: object requires documentation | ||
| 27 | Trace messages | Space: object requires documentation | ||
| 28 | The return code of the routing server is: &1 | Space: object requires documentation | ||
| 29 | The following data was transferred when the function was called: | Space: object requires documentation | ||
| 30 | The following data was received after the function was called: | Space: object requires documentation | ||
| 31 | Recipient address (parameter name DESTINATION): s. Detail | Space: object requires documentation | ||
| 32 | Original address (parameter name ORIGIN): s. Detail | Space: object requires documentation | ||
| 33 | Scenario ID (parameter name SCENARIO_ID): &1 | Space: object requires documentation | ||
| 34 | Attribute value list (parameter name ATTRIBUTE_VALUE_LIST): s. Detail | Space: object requires documentation | ||
| 35 | Scenario description (parameter name DESCRIPTION): &1 | Space: object requires documentation | ||
| 36 | Validity period (parameter VALID_FROM / VALID_UNTIL): From &1 to &2 | Space: object requires documentation | ||
| 37 | List of destination addresses (parameter name DESTINATION_LIST):s. Detail | Space: object requires documentation | ||
| 38 | List of routing attributes (parameter name ATTRIBUTE_LIST): s. Detail | Space: object requires documentation | ||
| 39 | List of responsibilities (parameter name RESPONSIBILITY_LIST): s. Detail | Space: object requires documentation | ||
| 40 | Agent group ID (parameter name AGENTGROUP_ID): &1 | Space: object requires documentation | ||
| 41 | Time stamp (parameter name TIMESTAMP): s. Detail | Space: object requires documentation | ||
| 42 | Attribute ID (parameter name ATTRIBUTE_ID): &1 | Space: object requires documentation | ||
| 43 | Attribute group name (parameter name ATTRIBUTE_VALUE): &1 | Space: object requires documentation | ||
| 44 | Members of the group that were not deleted/added: s. Detail | Space: object requires documentation | ||
| 45 | Delete all members of a group (parameter name DELETE_ALL): '&1' | Space: object requires documentation | ||
| 46 | Time stamp (parameter name TS_DL_START): &1 | Space: object requires documentation | ||
| 47 | Existence of scenario '&2' on server '&1' cannot be checked | Space: object requires documentation | ||
| 48 | &2 &3: Download of scenario '&1' and all objects involved | Space: object requires documentation | ||
| 49 | Only the objects that are not current are downloaded | Space: object requires documentation | ||
| 50 | All (including current) objects are downloaded | Space: object requires documentation | ||
| 51 | List of servers on which the scenario is to be downloaded: s.Detail | Space: object requires documentation | ||
| 52 | List of servers on which the scenario already exists: s. Detail | Space: object requires documentation | ||
| 53 | Server '&1': The scenario was successfully deleted | Space: object requires documentation | ||
| 54 | Server '&1': Start of download sequence with time stamp &2 | Space: object requires documentation | ||
| 55 | No download because server has current version (&1) of scenario | Space: object requires documentation | ||
| 56 | Download because address type &1 on server '&2' is unknown | Space: object requires documentation | ||
| 57 | Download because server has obsolete version (&2) of scenario | Space: object requires documentation | ||
| 58 | List of address types that the server knows: s. Detail | Space: object requires documentation | ||
| 59 | List of destinations that are downloaded: s. Detail | Space: object requires documentation | ||
| 60 | Scenario was downloaded on server '&1' | Space: object requires documentation | ||
| 61 | Server '&1' is not included due to errors in another download | Space: object requires documentation | ||
| 62 | Download sequence on server '&1' successfully completed | Space: object requires documentation | ||
| 63 | Scenarios must be deleted from servers that are no longer current | Space: object requires documentation | ||
| 64 | Server '&1': Download of scenario | Space: object requires documentation | ||
| 65 | Download because scenario is unknown on server | Space: object requires documentation | ||
| 66 | Calculation of destination list that is downloaded | Space: object requires documentation | ||
| 67 | Destination '&1' not downloaded because the address type is not supported | Space: object requires documentation | ||
| 68 | End of download of scenario '&1' and all objects involved | Space: object requires documentation | ||
| 69 | End of download not set as incomplete due to errors | Space: object requires documentation | ||
| 70 | Entries in search table that were not deleted/added: s.Detail | Space: object requires documentation | ||
| 71 | Search field ID (parameter name SEARCHKEY_ID): &1 | Space: object requires documentation | ||
| 72 | Deletion indicator (values see long text, parameter name DELETE_FLAG): &1 | Space: object requires documentation | ||
| 73 | Members to be deleted (parameter name MEMBER_LIST): s. Detail | Space: object requires documentation | ||
| 74 | Search fields to be deleted (parameter name SEARCHKEY_LIST): s. Detail | Space: object requires documentation | ||
| 75 | Search field ID (parameter name SEARCHKEY_ID): &1 | Space: object requires documentation | ||
| 76 | Time stamp table (parameter name TIMESTAMP_LIST): s. Detail | Space: object requires documentation | ||
| 77 | Specify routing server | Space: object requires documentation | ||
| 78 | Error when deleting table: &1 | Space: object requires documentation | ||
| 79 | All tables successfully reset | Space: object requires documentation | ||
| 80 | Mode saved successfully | Space: object requires documentation | ||
| 81 | Information text not found | Space: object requires documentation | ||
| 82 | No obsolete objects exist, deletion not necessary | Space: object requires documentation | ||
| 83 | *Message texts for integration of business routing in Workflow | Space: object requires documentation | ||
| 84 | Agent determination via router can only be started for activities | Space: object requires documentation | ||
| 85 | Choose a business partner for binding for SAP_BUSINESSPARTNERGROUP | Space: object requires documentation | ||
| 86 | No router is responsible for WF routing, maintain a router | Space: object requires documentation | ||
| 87 | Rule contains attributes that are no longer supported in the scenario | Space: object requires documentation | ||
| 88 | Unknown error when assigning agents to work item &1 | Space: object requires documentation | ||
| 89 | There is no routing request in the system for work item &1 | Space: object requires documentation |
History
| Last changed on/by | 20000906 | SAP | |
| SAP Release Created in | 46D |