| SRT_WSP149 |
Characters &2 and blanks are not permitted in string "&1" |
| SRT_WSP150 |
Configuration name "&1" is invalid |
| SRT_WSP151 |
Configuration does not have an endpoint node |
| SRT_WSP152 |
Endpoints of configuration are in different namespaces |
| SRT_WSP153 |
Invalid name for profile "&1" |
| SRT_WSP154 |
Configuration &1 already exists for interface &2 |
| SRT_WSP155 |
Source and target configuration use the same name (&1) |
| SRT_WSP156 |
No service exists within this configuration |
| SRT_WSP157 |
Undefined value &1 for WSDL section parameter |
| SRT_WSP158 |
You cannot specify both an endpoint key and an endpoint name |
| SRT_WSP159 |
No endpoint key or endpoint name specified |
| SRT_WSP160 |
Specified endpoint key '&1' is invalid |
| SRT_WSP161 |
Specified endpoint name (&1:&2) is invalid |
| SRT_WSP162 |
WSDL HTTP handler not initialized correctly; (&1='&2'?) |
| SRT_WSP163 |
Configuration '&1' of interface '&2' is not active |
| SRT_WSP164 |
Parameters are incomplete or invalid |
| SRT_WSP165 |
Configuration is part of a profile assignment; no changes possible |
| SRT_WSP166 |
Configuration &1 (type &2) is already assigned in &3 (type &4) |
| SRT_WSP167 |
Unknown value '&1' for WSDL style parameter |
| SRT_WSP168 |
Unknown assignment type '&1' found |
| SRT_WSP169 |
Error when opening Web service configuration |
| SRT_WSP170 |
No configuration for proxy class "&1" and logical port "&2" |
| SRT_WSP171 |
No Web service configuration for this access path: "&1" |
| SRT_WSP172 |
Subject &1: &2 of type &3 is not active |
| SRT_WSP173 |
No interface exists with name (&1:&2) |
| SRT_WSP174 |
No operation exists with name (&1:&2) |
| SRT_WSP175 |
No service exsits with name (&1:&2) |
| SRT_WSP176 |
No endpoint exists with name (&1:&2) |
| SRT_WSP177 |
No endpoint operation exists with name (&1:&2) |
| SRT_WSP178 |
Web service configuration not yet initialized |
| SRT_WSP179 |
Web service configuration not yet initialized (specific to operation) |
| SRT_WSP180 |
Error in WS configuration when determining location (server/client) |
| SRT_WSP181 |
Assignment for configuration &1 (type &2) is not unique (number: &3) |
| SRT_WSP182 |
Inbound XI interface does not exist: &1 (&2) |
| SRT_WSP183 |
Outbound XI interface does not exist: &1 (&2) |
| SRT_WSP184 |
No design time object or variant specified |
| SRT_WSP185 |
Cannot read ESR design time information; &1 |
| SRT_WSP186 |
Configuration generated by ESR input but profile is missing |
| SRT_WSP187 |
No access URL specified for binding &1 (configuration &2) |
| SRT_WSP188 |
No selected property list exists for binding &1 (&2) |
| SRT_WSP189 |
ESR channel not specified |
| SRT_WSP190 |
Client: IF not specified or specified generically for &1 |
| SRT_WSP191 |
Server: IF not specified or specified generically for &1 |
| SRT_WSP192 |
Specified profile &1 (type &2) cannot be used |
| SRT_WSP193 |
Could not generate configuration for channel/profile &1 |
| SRT_WSP194 |
External access URL not set for channel &1 |
| SRT_WSP195 |
Generic interface information is not permitted here |
| SRT_WSP196 |
More than one configuration created (IIF: &1.&2) |
| SRT_WSP197 |
No interface objects or multiple objects found for proxy &1 (using SIDL) |
| SRT_WSP198 |
No operations foumd for proxy &1 (using SIDL) |
| SRT_WSP199 |
No endpoints or multiple endpoints exist for configuration &1 |
| SRT_WSP200 |
Property &1 not set for channel &2 |
| SRT_WSP2000 |
& & & & |
| SRT_WSP2001 |
Logical port '&1' is polling related; no details available |
| SRT_WSP2002 |
Initialization of object failed. &1 |
| SRT_WSP2003 |
Deletion not possible, because client is not a system client. |
| SRT_WSP2004 |
Invalid name "&1" for DT Mapping |
| SRT_WSP2005 |
SIDL not supported for endpoint type '&1' |
| SRT_WSP2006 |
MLP error: &1&2&3&4 |
| SRT_WSP2007 |
The LP '&1' (proxy '&2') is not a polling LP. This API can not delete it. |
| SRT_WSP2008 |
Proxy '&1' can not be used for polling. Not all operations are async. |
| SRT_WSP2009 |
Binding with key '&1' has different DT object: '&2' instead of '&3' |
| SRT_WSP201 |
Calculation error in access URL for channel &1; &2 |
| SRT_WSP2010 |
Could not get internal operation name of proxy &1 (Operation=&2{&3}) |
| SRT_WSP2011 |
Mapping &1 doesn't provide details for operation &2 |
| SRT_WSP2012 |
No target operation found in Mediation LP. (mapping=&1 message=&2) |
| SRT_WSP2013 |
No target LP found in Mediation LP.(target proxy=&1) |
| SRT_WSP202 |
No unique active proxy definition exists for OIF &1:&2 (number: &3) |
| SRT_WSP203 |
Target host not specified: binding &1; configuration &2 |
| SRT_WSP204 |
Unknown protocol '&1': binding &2; configuration &3 |
| SRT_WSP205 |
Calculate property failed: binding '&1'; configuration '&2'. &3&4 |
| SRT_WSP2051 |
Attribute &1 does not exist in structure &2 for ServiceGroup &3 |
| SRT_WSP206 |
Property missing: &1 (&2) |
| SRT_WSP207 |
Configurations are assigned to the profile; special change required |
| SRT_WSP208 |
Error in deserialization of DT configuration |
| SRT_WSP209 |
URL path not specified; usage relationship cannot be resolved |
| SRT_WSP210 |
Internal error when reading usage condition; &1 |
| SRT_WSP2100 |
Error retrieving Remote System Application List |
| SRT_WSP2101 |
Error in GUID generation |
| SRT_WSP2102 |
Interface Mapping for '&1' does not exist |
| SRT_WSP2103 |
Service Definition for Proxy '&1' does not exist |
| SRT_WSP2104 |
Session '&1' is already open |
| SRT_WSP2105 |
System is not a central system. |
| SRT_WSP2106 |
Error during close of session '&1' |
| SRT_WSP2107 |
Application data is incomplete |
| SRT_WSP2108 |
Error during communication with remote system |
| SRT_WSP2109 |
Application error occured during remote system call |
| SRT_WSP211 |
Invalid input; not all parameters determined |
| SRT_WSP2110 |
No application data found for given search criteria |
| SRT_WSP2111 |
Error during save of application data |
| SRT_WSP2112 |
No Application ID´s defined in this system |
| SRT_WSP2113 |
Error during BAdI call |
| SRT_WSP2114 |
Wrong call of method DISTRIBUTE_DATA. Please check you input data. |
| SRT_WSP2115 |
Requests with technical Status "Invalid" must not be processed |
| SRT_WSP2116 |
Application '&1' with version '&2' is not supported by system '&3' |
| SRT_WSP2117 |
Structure '&1' for Service Group '&2' contains component of type '&3' |
| SRT_WSP2118 |
No (possible) violation found during routing check |
| SRT_WSP2119 |
Routing '&1' is Created in Inactive Status; Check Routing |
| SRT_WSP212 |
Could not save usage relationship |
| SRT_WSP2120 |
Routing '&1' is Updated in Inactive Status; Check Routing |