| BCOM_EC_R118 |
Not all specified entries could be added/changed |
| BCOM_EC_R119 |
The search table for '&3' does not exist on the routing server '&1' |
| BCOM_EC_R120 |
The sender's channel is not known to the routing server '&1' |
| BCOM_EC_R121 |
The address of the sender/caller is invalid |
| BCOM_EC_R122 |
The download sequence cannot currently be started |
| BCOM_EC_R123 |
The download sequence could not be successfully completed |
| BCOM_EC_R124 |
The start of the download sequence could not be identified |
| BCOM_IR001 |
&1 &2: Start of agent determination in internal router for request &3 &4 |
| BCOM_IR002 |
Routing scenario &1 does not exist in the internal router |
| BCOM_IR003 |
Agent determination is carried out with scenario &1 |
| BCOM_IR004 |
Scenario is not current at present (valid from &1 to &2) |
| BCOM_IR005 |
List of attribute values that are used for routing (see Details) |
| BCOM_IR006 |
No agent groups are assigned to the scenario, routing is not possible |
| BCOM_IR007 |
Determination of agent groups |
| BCOM_IR008 |
Agent group &1 excluded because another attribute value supported |
| BCOM_IR009 |
The following agent groups remain (see Details) |
| BCOM_IR010 |
No agent group remains, therefore new search with reduced attribute list |
| BCOM_IR011 |
Attribute &1 is removed from list |
| BCOM_IR012 |
Attribute list cannot be reduced further, routing not possible |
| BCOM_IR013 |
One agent group found, end of agent group determination |
| BCOM_IR014 |
More than one agent group found, attempt to limit further |
| BCOM_IR015 |
Agent group &1 removed since support of attribute &2 is worse |
| BCOM_IR016 |
The following agent groups were chosen (see Details) |
| BCOM_MIME001 |
There is no MIME description for code page &1 |
| BCOM_MIME002 |
Mixed code pages are not supported in MIME conversion |
| BCOM_MIME003 |
Error when checking that the system code page is a EBCDIC code page |
| BCOM_MIME004 |
Error when determining ASCII code page for EBCDIC system code page |
| BCOM_MIME007 |
MIME data flow is not syntactically correct: Starts with a blank row |
| BCOM_R001 |
Action canceled by user |
| BCOM_R002 |
The routing scenario does not exist in the database |
| BCOM_R003 |
First enter the routing attribute &1 in the list for the scenario |
| BCOM_R004 |
Server '&1' does not support any address types used in the scenario |
| BCOM_R005 |
No destinations are assigned to the scenario |
| BCOM_R007 |
The scenario has been changed, save before downloading |
| BCOM_R008 |
The scenario has not been changed, therefore it is not necessary to save |
| BCOM_R009 |
The destination '&1 (&2)' is also used in the scenario '&3' |
| BCOM_R010 |
The scenario cannot be saved without a description |
| BCOM_R012 |
The download was not performed due to inconsistencies in the scenario |
| BCOM_R013 |
The agent group '&1' is already assigned to the scenario |
| BCOM_R020 |
No connection to server '&1' |
| BCOM_R021 |
The scenario has to be deleted on server '&1' |
| BCOM_R022 |
The scenario does not exist on server '&1' |
| BCOM_R023 |
The scenario is obsolete on server '&1' |
| BCOM_R024 |
The address specifications for the scenario are incomplete on server '&1' |
| BCOM_R025 |
Server '&1' is not in use |
| BCOM_R026 |
At least one server must be assigned to the scenario |
| BCOM_R027 |
The scenario must contain at least one agent group with responsibility |
| BCOM_R028 |
Attribute &1& has the same priority as attribute &2& |
| BCOM_R029 |
Server '&1' does not support downloading of data by RFC |
| BCOM_R030 |
Server '&1' does not receive address data, assign internal router |
| BCOM_R031 |
Attribute &1 is not used in workflows, is not suppported by scenario |
| BCOM_R032 |
Assign server '&1' responsible for WF routing |
| BCOM_R033 |
Assign internal router |
| BCOM_R034 |
Assign a priority to attribute &1 |
| BCOM_R050 |
Trace messages |
| BCOM_R051 |
The return code of the routing server is: &1 |
| BCOM_R052 |
The following data was transferred when the function was called: |
| BCOM_R053 |
The following data was received after the function was called: |
| BCOM_R054 |
Recipient address (parameter name DESTINATION): s. Detail |
| BCOM_R055 |
Original address (parameter name ORIGIN): s. Detail |
| BCOM_R056 |
Scenario ID (parameter name SCENARIO_ID): &1 |
| BCOM_R057 |
Attribute value list (parameter name ATTRIBUTE_VALUE_LIST): s. Detail |
| BCOM_R058 |
Scenario description (parameter name DESCRIPTION): &1 |
| BCOM_R059 |
Validity period (parameter VALID_FROM / VALID_UNTIL): From &1 to &2 |
| BCOM_R060 |
List of destination addresses (parameter name DESTINATION_LIST):s. Detail |
| BCOM_R061 |
List of routing attributes (parameter name ATTRIBUTE_LIST): s. Detail |
| BCOM_R062 |
List of responsibilities (parameter name RESPONSIBILITY_LIST): s. Detail |
| BCOM_R063 |
Agent group ID (parameter name AGENTGROUP_ID): &1 |
| BCOM_R064 |
Time stamp (parameter name TIMESTAMP): s. Detail |
| BCOM_R065 |
Attribute ID (parameter name ATTRIBUTE_ID): &1 |
| BCOM_R066 |
Attribute group name (parameter name ATTRIBUTE_VALUE): &1 |
| BCOM_R067 |
Members of the group that were not deleted/added: s. Detail |
| BCOM_R068 |
Delete all members of a group (parameter name DELETE_ALL): '&1' |
| BCOM_R069 |
Time stamp (parameter name TS_DL_START): &1 |
| BCOM_R070 |
Existence of scenario '&2' on server '&1' cannot be checked |
| BCOM_R071 |
&2 &3: Download of scenario '&1' and all objects involved |
| BCOM_R072 |
Only the objects that are not current are downloaded |
| BCOM_R073 |
All (including current) objects are downloaded |
| BCOM_R074 |
List of servers on which the scenario is to be downloaded: s.Detail |
| BCOM_R075 |
List of servers on which the scenario already exists: s. Detail |
| BCOM_R076 |
Server '&1': The scenario was successfully deleted |
| BCOM_R077 |
Server '&1': Start of download sequence with time stamp &2 |
| BCOM_R078 |
No download because server has current version (&1) of scenario |
| BCOM_R079 |
Download because address type &1 on server '&2' is unknown |
| BCOM_R080 |
Download because server has obsolete version (&2) of scenario |
| BCOM_R081 |
List of address types that the server knows: s. Detail |
| BCOM_R082 |
List of destinations that are downloaded: s. Detail |
| BCOM_R083 |
Scenario was downloaded on server '&1' |
| BCOM_R084 |
Server '&1' is not included due to errors in another download |
| BCOM_R085 |
Download sequence on server '&1' successfully completed |
| BCOM_R086 |
Scenarios must be deleted from servers that are no longer current |
| BCOM_R087 |
Server '&1': Download of scenario |
| BCOM_R088 |
Download because scenario is unknown on server |
| BCOM_R089 |
Calculation of destination list that is downloaded |
| BCOM_R090 |
Destination '&1' not downloaded because the address type is not supported |
| BCOM_R091 |
End of download of scenario '&1' and all objects involved |
| BCOM_R092 |
End of download not set as incomplete due to errors |
| BCOM_R093 |
Entries in search table that were not deleted/added: s.Detail |
| BCOM_R094 |
Search field ID (parameter name SEARCHKEY_ID): &1 |
| BCOM_R095 |
Deletion indicator (values see long text, parameter name DELETE_FLAG): &1 |