SRT_WSP2 - Messages for SRT WSP
The following messages are stored in message class SRT_WSP2: Messages for SRT WSP.
It is part of development package SOAP_CONFIG in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Framework".
It is part of development package SOAP_CONFIG in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Framework".
Message Nr ▲ | Message Text |
|---|---|
| 000 | & & & & |
| 001 | Logical port '&1' is polling related; no details available |
| 002 | Initialization of object failed. &1 |
| 003 | Deletion not possible, because client is not a system client. |
| 004 | Invalid name "&1" for DT Mapping |
| 005 | SIDL not supported for endpoint type '&1' |
| 006 | MLP error: &1&2&3&4 |
| 007 | The LP '&1' (proxy '&2') is not a polling LP. This API can not delete it. |
| 008 | Proxy '&1' can not be used for polling. Not all operations are async. |
| 009 | Binding with key '&1' has different DT object: '&2' instead of '&3' |
| 010 | Could not get internal operation name of proxy &1 (Operation=&2{&3}) |
| 011 | Mapping &1 doesn't provide details for operation &2 |
| 012 | No target operation found in Mediation LP. (mapping=&1 message=&2) |
| 013 | No target LP found in Mediation LP.(target proxy=&1) |
| 014 | Configuration task "&1" does not exist. |
| 015 | Failed to initialize SRT tenant API. &1&2&3&4 |
| 016 | Error while reading from Consumer Mapping "&1": &2&3&4 |
| 017 | Invalid source proxy name "&1" for Consumer Mapping "&2". |
| 018 | Could not find mapping object with name "&1". |
| 019 | Cannot delete logical port "&1", it is used in Consumer Mapping "&2". |
| 020 | Name for logical port is empty. Enter a name for it. |
| 021 | Target logical port for target proxy "&1" is not assigned. |
| 022 | Logical port with name "&1" already exists. |
| 023 | All provider got isolated |
| 024 | Providers for service definition '&1' isolated |
| 025 | All consumers got isolated |
| 026 | Consumer for proxy definition '&1' and LP '&2' got isolated |
| 027 | No isolated provider found |
| 028 | No isolated consumer found |
| 029 | All provider got deisolated |
| 030 | All consumers got deisolated |
| 031 | Providers for service definition '&1' deisolated |
| 032 | Consumer for proxy definition '&1' and LP '&2' got deisolated |
| 033 | There are already isolated provider and consumer configurations |
| 034 | There are already isolated provider configurations |
| 035 | There are already isolated consumer configurations |
| 036 | Error on generating ICF root nodes. &1&2&3&4 |
| 037 | Logon Data '&1' of type '&2' already exists |
| 038 | Type '&1' for Logon Data '&2' is invalid for central configuration |
| 039 | No virtual host assigned to current tenant (SAP client &1) |
| 040 | Assignment type '&1' for Logon Data '&2' is invalid for central config. |
| 041 | Type '&1' for Bus. Scenario '&2' is invalid for central configuration |
| 042 | Type '&1' for Provider System '&2' is invalid for central configuration |
| 043 | Type '&1' for Profile '&2' is invalid for central configuration |
| 044 | Delete not possible. LP &1 (proxy &2) is used as a target in a mapping LP |
| 045 | Target LP &1 for proxy &2 is not actively existing |
| 046 | There are no target LPs specified for binding '&1' (NS '&2') |
| 047 | Error while determining the host name |
| 048 | Inactive configurations exist (&1). See single configuration for details. |
| 049 | Target proxy &1 does not belong to Consumer Mapping &2. |
| 050 | Could not get external operation name of proxy &1 (Method=&2) |
| 051 | Attribute &1 does not exist in structure &2 for ServiceGroup &3 |
| 052 | Design Time to Runtime change management is already locked |
| 053 | Try to use Business User Acoount |
| 054 | Business User Acoount and profile &1 with version &2 do not match |
| 055 | Cancellation of task is not possible as task is already in process |
| 056 | Cancellation of task is not possible as task is already cancelled |
| 057 | Cancellation of task is not possible as task is already completed |
| 058 | Error during transformation of data to XSTRING: &1&2&3&4 |
| 059 | Error during transformation of XSTRING to data: &1&2&3&4 |
| 060 | Invalid Target Proxy "&1" |
| 061 | There are multiple Target LPs assigned to Target Proxy "&1" |
| 062 | There are no Target Proxies specified within this Mediation Logical Port. |
| 063 | Invalid Target Proxy LP assignment. (Proxy="&1" LP="&2") |
| 064 | Name for logical port is invalid. Specify a valid name. |
| 065 | Error while reading official tenant url: "&1&2&3&4" |
| 066 | No logical port selected. |
| 067 | Invalid tracing minutes specified. Use a number from range [1..180] only. |
| 068 | All used timestamps are in system time. There is no usage of timezones! |
| 069 | Configuration for Service Definition '&1' automatically checked |
| 070 | This is not a system client. Only the current client can be changed. |
| 071 | Internal error occurred |
| 072 | Failed to switch ICF users in SAP-client &1. &2&3&4 |
| 073 | Tenant access violation. Current client is not a system client. |
| 074 | Failed to switch ICF users. SAP-client: '&1'. VH: '&2' Path: &3&4 |
| 075 | User switched to alias [ICF service]. Client/VH:&1. Path: &2&3&4 |
| 076 | User switched to internal [ICF service]. Client/VH:&1. Path: &2&3&4 |
| 077 | User switched to alias [ICF alias]. Client/VH:&1. Path: &2&3&4 |
| 078 | User switched to internal [ICF alias]. Client/VH:&1. Path: &2&3&4 |
| 079 | XI Point to Point ping successful for LP '&1', proxy definition '&2'. |
| 080 | File name is not set. Enter a correct filename. |
| 081 | URL is not set. Enter a correct URL. |
| 082 | User or password are not set correctly. Enter correct values. |
| 083 | There is no SCP entry for DT object '&1'. |
| 084 | There are multiple SCP entries for DT object '&1'. |
| 085 | Business Scenario '&1' (type '&2') already exists. |
| 086 | Invalid use of method '&1' (class '&2') |
| 087 | Can not get DDIC information for structure '&1' |
| 088 | All consumers for proxy definition '&1' got isolated |
| 089 | All consumers for proxy definition '&1' got deisolated |
| 090 | Exception on ping processing: &1&2&3&4 |
| 091 | Sender '&1' is not registered with receiver &3(&2). |
| 092 | Error while instantiating the shortcut utility. |
| 093 | Error while creating shortcut LP name for Service Definition "&1". |
| 094 | Error while instantiating the rtc reader. |
| 095 | Error while calculating Service Definition from Interface "&1" |
| 096 | Error while calculating generic Shortcut LP for Interface "&1" |
| 097 | Error while reading the offical host name for this business tenant. |
| 098 | Could not read the offical host name for this system tenant. |
| 099 | Host name "&1" is configured as official tenant host name. |
| 100 | Error retrieving Remote System Application List (&1&2&3&4). |
| 101 | Error in GUID generation |
| 102 | Interface Mapping for '&1' does not exist |
| 103 | Service Definition for Proxy '&1' does not exist |
| 104 | Session '&1' is already open |
| 105 | System '&1/&2' is not a central system |
| 106 | Error during close of session '&1' |
| 107 | Application data is incomplete |
| 108 | Error during communication: &1&2&3&4 |
| 109 | Application error occured during remote system call: &1&2&3&4 |
| 110 | No application data found for given search criteria |
| 111 | Error during save of application data |
| 112 | No Application ID�s defined in this system |
| 113 | Error during BAdI call |
| 114 | Wrong call of method DISTRIBUTE_DATA. Check you input data. |
| 115 | Requests with technical Status "Invalid" must not be processed |
| 116 | Application '&1' with version '&2' is not supported by system '&3' |
| 117 | Structure '&1' for Service Group '&2' contains component of type '&3' |
| 118 | No (possible) violation found during routing check |
| 119 | Routing '&1' is Created in Inactive Status; Check Routing |
| 120 | Routing '&1' is Updated in Inactive Status; Check Routing |
| 121 | No Service Group is specified |
| 122 | Neither Service Group nor LRD Filter is specified; Check Input |
| 123 | You must not use defaults and specify an auth method at the same time. |
| 124 | Only Simple Client configurations can be deactivated or deleted. |
| 125 | No Simple Client Provider API defaults are maintained. |
| 126 | LRD Filter could not be retrieved from Service Group |
| 127 | No Routing matched to given LRD Filter Data |
| 128 | Service Identifier data could not be created |
| 129 | Service Identifier data successfully created |
| 130 | Error while reading the host name from the Virtual Host. |
| 131 | No Application Data found in structure '&1'. |
| 132 | No task found with ID '&1' and type '&2'. |
| 133 | Wrong call of method '&1'. Check input. |
| 134 | Error during save of central config task. |
| 135 | Task is in read-only mode and therefore cannot be modified. |
| 136 | Can not find ICF service. Node-ID='&1'. URL='&2&3&4'. |
| 137 | Can not find ICF alias. Node-ID='&1'. URL='&2&3&4'. |
| 138 | Failed to update ICF service. Node-ID='&1'. URL='&2&3&4'. |
| 139 | Failed to update ICF alias. Node-ID='&1'. URL='&2&3&4'. |
| 140 | Application '&1' does not support operation '&2'. |
| 141 | No response retrieved from connectivity.Appl. status:&1, tech.status:&2 |
| 142 | Processing Mode '&1' is not supported for &2 '&3' |
| 143 | Management Connection with key '&1' is not maintained |
| 144 | Task cannot be locked as Task status is already '&1'. |
| 145 | Cannot modify read-only instance of task "&2", type "&1" |
| 146 | SAP client and tenant host name must not be specified at the same time. |
| 147 | System connection '&1' is maintained, but not active. |
| 148 | Official tenant host name doesn't fit to the Virtual Host settings. |
| 149 | Official tenant host name fits to the Virtual Host for HTTP (Port=&1). |
| 150 | Deserialization of WSIL document failed |
| 151 | The retrieved WSIL document does not contain any web services |
| 152 | Deletion of health check could not be done. |
| 153 | Official tenant host name fits to the Virtual Host for HTTPS (Port=&1). |
| 154 | ICM is not active. |
| 155 | ICM is not active for protocol "&1". |
| 156 | ICF Plugin is not active. |
| 157 | ICF Plugin is not active for protocol "&1". |
| 158 | Error while reading from ICF plugin. |
| 159 | Error while reading from ICF pluginfor protocol "&1". |
| 160 | Business Application ID '&1' is maintained in this system. |
| 161 | No Business System ID is maintained in this system. |
| 162 | No Business Application ID maintained in this system. |
| 163 | Business System ID '&1' is maintained in this system. |
| 164 | Business System Name '&1' maintained in this system. |
| 165 | No Business System Name maintained in this system. |
| 166 | Organization Name '&1' maintained in this system. |
| 167 | No Organization Name maintained in this system. |
| 168 | ICF Plugin is configured for urls beginning with "&1". |
| 169 | &1 Reverse Proxies checked. (&2 active, &3 inactive, &4 errors) |
| 170 | Check of the Reverse Proxy Settings was successful. |
| 171 | Check of the Reverse Proxy Settings failed. |
| 172 | System is a multi-tenant system. |
| 173 | This tenant is a business tenant. |
| 174 | This tenant is a system tenant. |
| 175 | No Virtual Host exists for this tenant |
| 176 | Virtual Host found for this tenant.(Name="&1", Number="&2") |
| 177 | Error reading Endpoint information for Web Service Definition '&1'. |
| 178 | Service endpoint '&1' is consistent |
| 179 | Reverse Proxy "&1" has an undefined status "&2" |
| 180 | Reverse Proxy "&1" has an invalid incoming http header host name "&2" |
| 181 | Reverse Proxy "&1" has an invalid incoming ICM Port "&2" |
| 182 | Reverse Proxy "&1" has an invalid substitute host name "&2". |
| 183 | Reverse Proxy "&1" has an invalid substitute http port "&2". |
| 184 | Reverse Proxy "&1" has an invalid substitute https port "&2". |
| 185 | Error updating health Check Progress for Check ID:&1 Component:&2 |
| 186 | Error reading Health Check result for Check ID:&1 Component:&2 |
| 187 | Error updating Health Check result for Check ID:&1 Component:&2 |
| 188 | Error reading Health Check Progress for Check ID:&1 Component:&2 |
| 189 | Error generating Health Check ID |
| 190 | Error removing data for Check ID:&1 |
| 191 | Not a valid value for Check ID '&1' |
| 192 | Error updating Health Check status for Check ID:&1 Component:&2 |
| 193 | Reverse Proxy "&1" has an invalid meta data protocol substitution"&2". |
| 194 | Reverse Proxy "&1" has an invalid endpoint protocol substitution"&2". |
| 195 | Check active Reverse Proxy "&1". |
| 196 | Check inactive Reverse Proxy "&1". |
| 197 | Check Reverse Proxy "&1". |
| 198 | Check of Reverse Proxy "&1" completed without error. |
| 199 | Check of Reverse Proxy "&1" completed with 1 error. |
| 200 | Check of Reverse Proxy "&1" completed with &2 errors. |
| 201 | Successfully created logical port for local shortcut. |
| 202 | Failed to create logical port for local shortcut. |
| 203 | Local shortcut not possible. The provider application is not specified. |
| 204 | No service definition exists for inbound interface '&1' '&2' |
| 205 | Try to create a logical port using local shortcut. |
| 206 | Service definition '&1' found for inbound interface '&2' '&3' |
| 207 | Service group '&1' is assigned to the own business system |
| 208 | Service group '&1' is not assigned to the own business system. |
| 209 | Error during Connectivity setup request: &1 |
| 210 | Connectivity Setup:Connection data could not be written to database |
| 211 | Logical port '&1' of proxy '&2' could not be found! |
| 212 | Unsupported entity type '&1' for entity operation '&2'. |
| 213 | Remote connectivitiy to system '&1' client '&2' has already been setup. |
| 214 | Configuration for service group '&1' could not start. |
| 215 | No Endpoint exists for the Service Definition '&1'. |
| 216 | Local shortcut not possible. The target interface has not been specified |
| 217 | Preconfiguration is invalid: &1&2&3&4 |
| 218 | Error: & & & & |
| 219 | Services Registry Connection '&1' tested sucessfully. |
| 220 | The URL list could not be saved. |
| 221 | The URL list could not be read. |
| 222 | The security settings could not be read. |
| 223 | The ping URL settings dialog could not be opened. |
| 224 | The health check controller could not be opened. |
| 225 | Saving of URL list and security settings was successful. |
| 226 | Services Registry Connection '&1' not working. |
| 227 | No connection to Services Registry exists in this system. |
| 228 | PI integration ("WS" adapter) is not supported any more in this release |
| 229 | Error processing health check requests. |
| 230 | Repair was successful. |
| 231 | Repair failed. |
| 232 | Repair was done with warnings. |
| 233 | Error processing health check for component &1. |
| 234 | Error retrieving health check results of check '&1' on system '&2&3'. |
| 235 | Unknown error occured while getting health check history. |
| 236 | Problems in health check occured. |
| 237 | Unsupported WSRM Protocol "&1". (Proxy:"&2" LP: "&3") |
| 238 | Logical Port '&1' successfully activated |
| 239 | No remote system found for connection key '&1'. |
| 240 | API call failed [method '&1', class '&2'] |
| 241 | Invalid authorization check performed [method '&1', class '&2'] |
| 242 | Log history entries older than &1 days removed (entries: &2) |
| 243 | Failed to create a central logical port for inbound interface '&1' '&2' |
| 244 | Successfully created central logical port for inbound interface '&1' '&2' |
| 245 | No WSDLs with central profile were found for inbound interface '&1' '&2' |
| 246 | Property not set (name &1, namespace &2) |
| 247 | Low Value '&1' has to be less than High Value '&2' |
| 248 | Tenant UUID in XML file '&1' is not suitable for this system |
| 249 | Error retrieving Tenant UUID in this system |
| 250 | Security settings check failed: &1&2&3&4 |
| 251 | Error while retrieving log data from remote system: &1&2&3&4 |
| 252 | Retrieving log data from remote system &1 was successful. |
| 253 | Validity of Restricted Function '&1' ended on &2 |
| 254 | Restricted Function activated successfully. |
| 255 | Registration has been deleted. Save to persist your changes. |
| 256 | Restricted Function '&1' is not known. |
| 257 | Missing configuration property in DT Cache: &2(&1)=&3 |
| 258 | Additional configuration property in DT Cache: &2(&1)=&3 |
| 259 | DT Cache version "&2" is different to the current version "&1". |
| 260 | Interface names are different. DT Cache="&4(&3)" Current name="&2(&1)" |
| 261 | Missing binding property in DT Cache: &2(&1)=&3 |
| 262 | Additional configuration property in DT Cache: &2(&1)=&3 |
| 263 | Missing feature URI in DT Cache: &1 |
| 264 | Additional feature URI in DT Cache: &1 |
| 265 | Missing operation mapping in DT Cache. (Operation: &1, &2 Message: &3) |
| 266 | Additional operation mapping in DT Cache. (Operation: &1, &2 Message: &3) |
| 267 | Missing operation in DT Cache: &1(&2) |
| 268 | Additional operation in DT Cache: &1(&2) |
| 269 | Missing operation property in DT Cache. Operation=&1 Property=&3(&2)=&4 |
| 270 | Additional operation property in Cache:Operation=&1 Property=&3(&2)=&4 |
| 271 | Checking &1 Service Definitions and &2 Consumer Proxies |
| 272 | Service Definition &1 and its DT Cache content are equal. |
| 273 | Service Definition &1 and its DT Cache content are different. |
| 274 | Service Definition &1 was not cached until now. |
| 275 | Error while checking Service Definition &1. |
| 276 | Consumer Proxy &1 and its DT Cache content are equal. |
| 277 | Consumer Proxy &1 and its DT Cache content are different. |
| 278 | Consumer Proxy &1 was not cached until now. |
| 279 | Error while checking Consumer Proxy &1. |
| 280 | Search '&1' saved succesfully. |
| 281 | Search '&1' could not be saved. |
| 282 | Saved Search '&1' deleted succesfully. |
| 283 | Saved Search '&1' could not be deleted. |
| 284 | Initial value not allowed for property &2(&1) |
| 285 | Invalid WSDL flavour code: Incorrect SOAP style |
| 286 | Serialization failed for subject &1 type &2 with error &3 |
| 287 | Invalid WSDL flavour code: It must have &1 characters for version &2 |
| 288 | Invalid WSDL flavour code: Incorrect flavour version |
| 289 | Invalid WSDL flavour: Name '&1' is unknown |
| 290 | Invalid WSDL flavour code: Incorrect configuration code |
| 291 | Invalid WSDL flavour code: Incorrect security code |
| 292 | Invalid WSDL flavour code: Incorrect WSDL section |
| 293 | Invalid WSDL flavour code: Incorrect WSDL version |
| 294 | Invalid WSDL flavour code: Incorrect WS-Policy version |
| 295 | Invalid WSDL flavour code: Incorrect WS-Policy style |
| 296 | Invalid WSDL flavour code: Incorrect SOAP version |
| 297 | Invalid IDoc operation due to invalid namespace '&1'. |
| 298 | Invalid IDoc operation due to invalid IDoc Basic Type '&1'. |
| 299 | Invalid IDoc operation due to invalid Message Type '&1'. |
| 300 | Proxy '&1' is not an IDoc Consumer Proxy. |
| 301 | Invalid SOAP Application Name '&1'. |
| 302 | No value set for binding property '&1' ['&2&3&4'] |
| 303 | No value set for operation property '&1' ['&2&3'], operation '&4' |
| 304 | Parameter '&1' has invalid value '&2' |
| 305 | Service Definition '&1' used in IS '&2' does not exist in system '&3' |
| 306 | Parameter '&1' is not specified |
| 307 | No active Scenario exists for ServiceGroup '&1' and Bus. Application '&2' |
| 308 | There are neither HTTP nor HTTPS services running in the system |
| 309 | Only secure communication is selected but the system does not support it |
| 310 | Invalid WSDL flavour code: Incorrect SOAP action |
| 311 | IDoc Service Definition "&1" does not support the Local Shortcut. |
| 312 | IDoc Consumer Proxy "&1" does not support the Local Shortcut. |
| 313 | Failed to read application component. &1&2&3&4 |
| 314 | View with name "&1" already exists. Choose another name. |
| 315 | Enter a non-empty valid user name. |
| 316 | Enter at least one user assignment. |
| 317 | Enter at least one object. |
| 318 | Object Type is initial. Enter a valid object type. |
| 319 | Low value is empty. Enter a valid value. |
| 320 | High value is empty. Enter a valid value. |
| 321 | The remote system '&1' is not a central system. |
| 322 | Change management is switched off. No automatic updates will be done! |
| 323 | Change management switched on. Automatic updates are done periodically! |
| 324 | Source system information is missing in transported data |
| 325 | No Transport key [System ID: &1, Tenant ID: &2, SID ID: &3] |
| 326 | User or user group '&1' does not exists. Enter a valid user name/group. |
| 327 | Failed to save local transport entry [SAP client=&1, key=&2] |
| 328 | Failed to get own transport key |
| 329 | Binding key not found for binding &1 (&2) |
| 330 | Logical Port name not set in consumer configuration |
| 331 | You cannot start the connectivity setup from a central system. |
| 332 | You are already subscribed to central system &1/&2 (&3). |
| 333 | Invalid object key '&1' |
| 334 | Invalid system key '&1' |
| 335 | Deserialize failed: Version &1 not supported for serialize type &2 |
| 336 | Deserialize failed: Type &1 supported, but not &2 |
| 337 | Object was instanciated for deserialization, not serialization |
| 338 | Object was instanciated for serialization, not deserialization |
| 339 | Deletion of IBC with Id '&1' failed. |
| 340 | Save of IBC with Id '&1' failed. |
| 341 | IBC with ID '&1' not found. |
| 342 | IBC with Receiver Type '&1' and Receiver Name '&2' not found. |
| 343 | No description for IBC found in language '&1'. |
| 344 | Called method '&1' of class '&2' using an invalid parameter combination. |
| 345 | IBC Reference with ID '&1' not found. |
| 346 | IBC Reference with receiver type '&1',name '&2' and system '&3' not found |
| 347 | IBC with Receiver Type '&1' and Name '&2' already exists |
| 348 | IBC Reference with ID '&1' cannot be deleted due to application '&2(&3)'. |
| 349 | Cannot modify IBC Reference with ID '&1' as it is not locked. |
| 350 | Alias receiver type '&1' and alias receiver name '&2' do not exist. |
| 351 | Application class '&1' could not be instantiated! |
| 352 | IBC Reference with receiver type '&1',name '&2',system '&3' already exist |
| 353 | Provider System with key '&1' does not exist. |
| 354 | Application '&1 (&2)' has already declared usage of IBC Reference '&3'. |
| 355 | No IBC Reference is assigned to Provider System '&1'. |
| 356 | No transport key found. Tenant-ID: &1, version: &2 |
| 357 | No own transport key found for version &1 |
| 358 | Symmetric encryption key usage is not supported in this SAP instance |
| 359 | Failed to get constant value of 'CL_SEC_SXML_WRITER=>CO_TDES_ALGORITHM' |
| 360 | IBC Reference with ID '&1' already exists. |
| 361 | IBC Reference '&1' can only be assigned to inactive Provider Systems. |
| 362 | Provider System with Key '&1' must be inactive to unassign IBC Reference |
| 363 | Invalid version '&1' specified. Version must be at least 1. |
| 364 | Cannot overwrite keys of current tenant '&1' |
| 365 | IBC Reference '&1' is already assigned to Provider System with key '&2' |
| 366 | This SAP instance does not support SOAP Runtime transport encryption |
| 367 | This SAP instance does not support SOAP Runtime transport decryption |
| 368 | Specified key '&1' already in use |
| 369 | Class '&1' does not implement interface 'IF_SRT_WSP_IBC_APPLICATION' |
| 370 | Unsupported serialization type '&1' |
| 371 | Operation '&1' is not allowed for Receiver Type '&2' Name '&3' |
| 372 | Error during encryption for tenant '&1'. |
| 373 | Error during decryption. |
| 374 | No entry found for specified transport ID '&1' |
| 375 | No transport key found. Tenant-ID: &1, Version &2 |
| 376 | Can not process configuration serialisation type &1 |
| 377 | Configuration created successfully [type: &1, name: &2, DT name: &3] |
| 378 | Receiver Type '&1' and Receiver Name '&2' do not exist |
| 379 | Publication rule is not in change mode |
| 380 | XML Document for IBC does not contain any data |
| 381 | IBC ID &1 is invalid |
| 382 | You cannot specify more than one IBC ID |
| 383 | Text with Text ID '&1' in Language '&2' already exits |
| 384 | Entry processing |
| 385 | No configuration context deserialized from WSDL document |
| 386 | Multiple configuration contexts deserialized from WSDL (count &1) |
| 387 | Multiple authentication methods specified (count &1) |
| 388 | Unsupported authentication method found: '&1' |
| 389 | Multiple bindings found (count &1) |
| 390 | PSE file for PSE '&1' not found. PSE not usable. |
| 391 | Failed to get certificate from PSE file '&1&2&3' [RC=&2] |
| 392 | Unsupported (individual) PSE '&1' specified |
| 393 | WSDL Upload ID '&1' already exists in this system |
| 394 | Error saving data in the database with ID '&1' |
| 395 | Invalid WSDL upload ID '&1' |
| 396 | Enter a description for the uploaded WSDL |
| 397 | Enter a non-empty and valid WSDL |
| 398 | Invalid URL. Path part 'ext_' cannot be combined with further options. |
| 399 | Enter a non-empty name for the uploaded WSDL |
| 400 | IBC Reference with receiver type '&1' and name '&2' not found |
| 401 | Multiple IBC References with receiver type '&1' and name '&2' found |
| 402 | WSDL_URL is empty. Enter a valid WSDL URL. |
| 403 | User name is empty. Enter a valid user name. |
| 404 | Password field is empty. Enter the password. |
| 405 | Cannot delete IBC with ID '&1' due to existing IBC Reference |
| 406 | System is empty. Enter a valid system. |
| 407 | Internal name is empty. Enter an internal name. |
| 408 | Name '&1' exists already. Choose another one. |
| 409 | The file does not contain valid WSDL |
| 410 | Domain System with ID '&1' has no description in language '&2' |
| 411 | Domain System with ID '&1' does not exist |
| 412 | Domain System with ID '&1' is already assigned to Provider System '&2' |
| 413 | Domain System with ID '&1' is already assigned to Connection '&2' |
| 414 | Management connection with ID '&1' does not exist. |
| 415 | Save of Domain System with ID '&1' failed |
| 416 | Domain Systen with ID '&1' is not locked |
| 417 | Domain System '&1' already exists |
| 418 | System Name is empty. Enter a valid name |
| 419 | Host Name is empty.Enter a valid name |
| 420 | Domain with name '&1' does not exist |
| 421 | Status of WSDL upload ID '&1' is not active in the system |
| 422 | Enter classifications for the service |
| 423 | Domain with Connection Key '&1' does not exist |
| 424 | Subject of type '&1' missing |
| 425 | Cannot determine the release of the SAP_BASIS component [reason: '&1'] |
| 426 | Domain System '&1' cannot be deleted as it is assigned to Domain '&2' |
| 427 | Domain System '&1' cannot be deleted as it is assigned to Cfg. Req. '&2' |
| 428 | Connection '&1' cannot be deleted as it is assigned to Domain System '&2' |
| 429 | Domain System with Key '&1' has no management connection assigned |
| 430 | Domain System with Key '&1' has no Provider System assigned |
| 431 | Domain '&1' has no priority set. Set the domain's priority. |
| 432 | Domain '&1' already has priority '&2'. Choose another value. |
| 433 | Central Configuration Change Compiler is locked |
| 434 | No common domain found for domain systems '&1' ('&2') and '&3' ('&4') |
| 435 | Error while persisting Central Configuration Changes |
| 436 | Central Configuration Change Compiler is not locked |
| 437 | RFC call '&1' failed (RC=&2) |
| 438 | Error while retrieving user account with name '&1' and type '&2' |
| 439 | No Central Configuration Change found for Task ID '&1' |
| 440 | Received empty response from managed system |
| 441 | Started distributing central configuration entities to domain system |
| 442 | Started provider configuration on domain system |
| 443 | Started consumer configuration on domain system |
| 444 | Error while opening MIF for Service Group &3 (C-System &1, P-System &2) |
| 445 | Domain system reported to have successfully finished phase &1 |
| 446 | Finished successfully |
| 447 | Entry processed |
| 448 | Service Group &3 doesn't exist. (C-System &1, P-System &2) |
| 449 | No Consumer Proxies for Service Group &3. (C-System &1, P-System &2) |
| 450 | Consumer Proxy &3 doesn't exist on Service Group &2. (C-System &1) |
| 451 | Missing Interface Assignment for Consumer Proxy &1 |
| 452 | Invalid Interface Name "&2{&3}" for Consumer Proxy &1 |
| 453 | Invalid number of Interface Assignments. |
| 454 | Error while saving Interface Assignments for Service Group &2(C-Syst. &1) |
| 455 | Interface Assignment is not locked and cannot be changed. |
| 456 | Error while adding entry to export structure. (&1 &2 &3) |
| 457 | No domain system found for provider application with key '&1' |
| 458 | No Interface Assignment for Service Group &1 Consumer Proxy &2 Key &3 |
| 459 | Invalid Interface Assignment for ServiceGroup &1 ConsumerProxy &2 Key &3 |
| 460 | Invalid Interface Assignment for ServiceGroup &1 Application Key &2 |
| 461 | Duplicate Interface Assignment for ServiceGroup &1 Application Key &2 |
| 462 | Error while saving local Interface Assignments. |
| 463 | Change entries total: &1 [SAP client local &2] |
| 464 | Error scheduling background job for publication synchronization |
| 465 | No business application key found for domain system with key '&1' |
| 466 | Update of central changes in database failed (sy-subrc = '&1') |
| 467 | No Provider System with name '&1' and type '&2' exists |
| 468 | No domain system assigned to Provider system with name '&1' |
| 469 | WSDL passwords does not match |
| 470 | WSIL passwords does not match |
| 471 | Error while deleting publication keys for Service Definition '&1' |
| 472 | Error while inserting publication keys for Service Definition '&1' |
| 473 | No Active Publication Rule found for Services Registry '&1' |
| 474 | Service Definition '&1' does not match with the Rule assigned to SR '&2' |
| 475 | LP name '&1' is already used in basis proxy '&2' |
| 476 | Enhancement '&1' does not have a basis proxy assigned |
| 477 | LP '&1' is already assigned to proxy enhancement '&2' via proxy '&3' |
| 478 | Service Registry Interfaces successfully configured. |
| 479 | Configuration of Service Registry Interfaces failed. |
| 480 | Field 'Name' is empty. |
| 481 | Field 'Namespace' is empty. |
| 482 | Field 'Technical Name' is empty. |
| 483 | Value '&1' for Technical Name already exists. |
| 484 | No valid entry selected. Select a valid line. |
| 485 | This function is currently not implemented |
| 486 | WS Ping successful: LP '&1', basis proxy '&2' [proxy '&3' is enhancement] |
| 487 | Cannot get basis consumer proxy for enhancement proxy '&1' |
| 488 | Cannot get basis service def. for enhancement service def. '&1' |
| 489 | Specified proxy '&1' is not an enhancement proxy |
| 490 | Specified proxy '&1' does not have a basis proxy |
| 491 | LP '&1' is already used by basis proxy '&2' |
| 492 | LP '&1' is already used by an enhancement proxy |
| 493 | Invalid domain priority '&2' for domain '&1'. Allowed: 1 to 255 |
| 494 | Connectivity endpoint is not active.Configure using Remote Connections UI |
| 495 | No common Domain for Consumer System '&1' and Provider System '&2' |
| 496 | No Interface Assignment for Service Group &1 Consumer '&2' Provider '&3' |
| 497 | Failed to open STCM proxy &1. &2&3&4 |
| 498 | Failed to open STCM proxy &1: Invalid number of target proxies (&2) |
| 499 | No central change found for domain system with key '&1' |
| 500 | You cannot instantiate STCM object '&1' via the mapping class |
| 501 | Proxy '&1' is not an enhancement proxy |
| 502 | Enhancement proxy '&1' has basis proxy '&2', not proxy '&3' |
| 503 | STCM '&1' does not cover source proxy '&2' and/or target proxy '&3' |
| 504 | Started deletion of obsolete provider configurations |
| 505 | Specified object name '&1' is not a STCM object |
| 506 | STCM object '&1' does not have a source proxy assigned |
| 507 | Error during import of central configuration entities: &1&2&3&4 |
| 508 | Status cannot be retrieved. No remote GUID for given local GUID '&1' |
| 509 | Unsupported processing mode '&1' |
| 510 | Domain "&1" cannot be modified |
| 511 | Activation of an empty hierarchy is not possible. |
| 512 | KVMGroup with name '&1' does not exist |
| 513 | No SAP Developer Network URL found for topic '&1' |
| 514 | KVMGroup with name '&1' already exists |
| 515 | File does not exist '&1' ! |
| 516 | Processing IBCR has to be defined |
| 517 | Choose at least one object, either a consumer, IBC or service definition |
| 518 | Assigned communication partners in KVMGroup '&1' already exists |
| 519 | KVM with field name '&1' already exists |
| 520 | Select at least one classification to import. |
| 521 | Choose at least one system and one web service definition! |
| 522 | No classifications for selected entities available. |
| 523 | Choose either Consumer or Provider as processing IBCR |
| 524 | KVM does not exist and cannot be updated |
| 525 | Publishing of classification '&3' to registry '&2' failed: '&1' |
| 526 | Publishing of binding '&3' to registry '&2' failed &1 |
| 527 | Publishing of service definition '&3' to registry '&2' failed &1 |
| 528 | Deletion of bindings of wsd '&3' from registry '&2' failed: '&1' |
| 529 | Deletion of binding '&4' of wsd '&3' from registry '&2' failed &1 |
| 530 | Deletion of service definition '&3' from registry '&2' failed &1 |
| 531 | Deletion of IBC '&3' from registry '&2' failed &1 |
| 532 | Searching for services registry entity in registry '&2' failed &1 |
| 533 | Publishing of IBC '&3' to registry '&2' failed &1 |
| 534 | Register application failed &1 |
| 535 | Persisting application change key failed: &1 |
| 536 | Registry not found: &1 |
| 537 | Searching for registered applications failed. |
| 538 | Proxy instantiation for registry '&2' failed: &1 |
| 539 | Registry '&2' not found: &1 |
| 540 | STCM object '&1' does not have a unique target proxy assigned |
| 541 | No unique binding on STCM map object &1 |
| 542 | STCM target LP not uniquely assigned to map object (count: &1) |
| 543 | Invalid number of bindings for STCM target configuration (&1) |
| 544 | STCM map configuration not set |
| 545 | Invalid number of bindings for STCM source configuration (&1) |
| 546 | Maximum one binding for consumer or mapping configurations |
| 547 | No entry found |
| 548 | Source and target value are the same for KVM '&1' |
| 549 | STCM: Target binding not set |
| 550 | Facade name not set in target binding &1 (&2) |
| 551 | Source proxy name not set in target binding &1 (&2) |
| 552 | Source logical port not set in target binding &1 (&2) |
| 553 | Invalid STCM type '&1' specified on assignment |
| 554 | STCM facade '&1' does not exist |
| 555 | STCM facade name '&1' returns multiple facades |
| 556 | Facade '&1' is not a single target consumer mapping (STCM) |
| 557 | Invalid STCM input: facade='&1', source='&2', target='&3', source-LP='&4' |
| 558 | No direct change possible. This object is part of a STCM configuraiton. |
| 559 | KVMGroup with name (&1) has to be locked first |
| 560 | Multiple LP entries for binding key '&1' |
| 561 | Multiple LP assignments for STCM proxy '&1' and LP '&2' (&3) |
| 562 | Application key and/or application change key are empty: '&1' |
| 563 | Registry must not be empty |
| 564 | Proxy cannot be instantiated for registry '&2': '&1' |
| 565 | STCM map has target configuration name '&1', but needs name '&2' |
| 566 | STCM target LP assignment contains proxy '&1', but needs proxy '&2' |
| 567 | IBC Receiver Type '&1' Name '&2' is not locked |
| 568 | IBCR Receiver Type '&1' Name '&2' System '&3' is not locked |
| 569 | URL is already maintained for Article ID '&1', Release '&2', SP '&3' |
| 570 | LP '&1' is already used for source proxy '&2' of STCM '&3' |
| 571 | Cannot find target LP for source LP '&1' and source proxy '&2' |
| 572 | SOAP configuration related tables (number of entries found: &1) |
| 573 | Enter a description text. |
| 574 | Enter a valid language. |
| 575 | Description for language &1 already exists. |
| 576 | There is no description selected for editing. |
| 577 | There is no description selected for removal. |
| 578 | There are no entities available in export file. |
| 579 | Cannot import file since version is newer. |
| 580 | Cannot read export file: &1 |
| 581 | System logical key must not be empty. |
| 582 | Invalid parameter. Specify at least key version or hash with usage. |
| 583 | There are no encryption key versions available for usage '&1' |
| 584 | Key hash '&1' (usage '&2') not unique. Use key version instead. |
| 585 | Key version '&1' (usage '&2') does not exist |
| 586 | Key does not exist (version '&1', hash '&2', usage '&3', ID '&4') |
| 587 | Key hash '&1' (usage '&2') does not exist |
| 588 | Key version '&1' (usage '&2', key ref '&3') is missing in secure store |
| 589 | Deletion of consumer '&3' from registry '&2' failed &1 |
| 590 | Publishing of consumer '&3' to registry '&2' failed &1 |
| 591 | Encryption key version created. Version: '&1'. Hash: '&2'. Usage: '&3' |
| 592 | Encryption key version deleted. Version: '&1'. Hash: '&2'. Usage: '&3' |
| 593 | Encryption key overflow occurred for key usage type '&1' |
| 594 | System changed to "Central System" |
| 595 | System changed to "Managed System" |
| 596 | Specify at least one selection criterion |
| 597 | Business Scenario '&1' is empty |
| 598 | Business Scenario '&1' is inactive |
| 599 | Key version '&1' (usage '&2') not unique |
| 600 | Key version '&1' (usage '&2', ID '&3', ref '&4') not found |
| 601 | Key version '&1' (usage '&2', hash '&3') not found |
| 602 | Key version '&1' (usage '&2', hash '&3') not unique |
| 603 | Key version '&1' (usage '&2', ID '&3') not found or not unique |
| 604 | Configuration currently locked. &1&2&3&4 |
| 605 | Get registered applications failed &1 |
| 606 | IBC Ref. with ID '&1', type '&2',name '&3' and system '&4' does not exist |
| 607 | Provider System is inconsistent: Destination key '&1' does not exist |
| 608 | Provider System is inconsistent: System key '&1' does not exist |
| 609 | Domain System with id '&1' and name '&2' does not have a destination key |
| 610 | IBC '&1' does not match the publication rules maintained in this system |
| 611 | Services Registry connection '&1' does not support this service |
| 612 | Ensure 'https' protocol is set when using X.509 SSL client certificate |
| 613 | Getting IBC information for id '&3' for registry '&2' failed &1 |
| 614 | Getting Service Definition '&3' for registry '&2' failed &1 |
| 615 | Getting Bindings for IBC '&3' for registry '&2' failed '&1' |
| 616 | Function not supported in central system |
| 617 | Get bindings failed: Registry '&1', Application Key '&2', Object ID '&3' |
| 618 | IBC det. connection key '&1', user '&2', object '&3' already exists |
| 619 | IBC det. connection key '&1', user '&2', object '&3' does not exist |
| 620 | IBC det. connection key '&1', user '&2', object '&3' is not locked |
| 621 | Save of IBC det. connection key '&1', user '&2', object '&3' failed |
| 622 | Deletion of IBC det. connection key '&1', user '&2', object '&3' failed |
| 623 | Object '&1' in system '&2' does not exist |
| 624 | IBC Reference of IBC with ID '&1' does not exist |
| 625 | RT: Save of IBC/IBCR Determination with user '&1' and object '&2' failed |
| 626 | Error receiving application information of Services Registry |
| 627 | Pulling IBC information for id '&3' for registry '&2' failed: '&1' |
| 628 | Pulling Service Definition '&3' for registry '&2' failed: '&1' |
| 629 | Pulling Binding '&3' for registry '&2' failed:'&1' |
| 630 | Structure '&1' contains component '&2' of type '&3' |
| 631 | Pulling of application failed: &1. |
| 632 | UDDI query not possible. The provider IBCR has not been specified |
| 633 | Deletion of Application '&3' from registry '&2' failed &1 |
| 634 | No WSDL-URL selected |
| 635 | Entry for IBC ID'&1', Type '&2' and Name '&3' is missing in SRT_IBC_RT |
| 636 | Entry for IBC Ref. ID'&1' Type '&2' , Name '&3' is missing in SRT_IBCR_RT |
| 637 | No subscription possible without publication ID |
| 638 | Deletion of Consumer Factory '&1' failed. |
| 639 | Save of Consumer Factory '&1' failed. |
| 640 | No assignment of Consumer Factory '&1' to IBC ID '&2' and IBCR ID '&3' |
| 641 | Start deletion of logical port for source proxy '&1' and IBC/IBCR &2/&3 |
| 642 | Notification failed for Registry &2 &1 |
| 643 | Consumer Factory '&1' is not locked |
| 644 | Failed to find active Consumer Factory '&1' and Source Proxy '&2' |
| 645 | Configuration for Consumer Factory '&1' could not start |
| 646 | Error when initializing Consumer Factory '&1': '&2&3&4' |
| 647 | Consumer Factory '&1' does not exist |
| 648 | Start configuration of Consumer Factory '&1' |
| 649 | Configuration of Consumer Factory '&1' completed |
| 650 | Configuration of Consumer Factory '&1' failed |
| 651 | Delete configuration of Consumer Factory '&1' |
| 652 | Deletion of configuration for Consumer Factory '&1' finished |
| 653 | Deletion of configuration for Consumer Factory '&1' failed |
| 654 | IBC Reference '&1' cannot be deleted. Usage in Logon Data Assign. '&2' |
| 655 | IBC Reference '&1' cannot be deleted. Usage in Integration Scenario '&2' |
| 656 | Getting subscription from registry '&2' failed &1 |
| 657 | Getting notifications from registry '&2' failed &1 |
| 658 | Assigned provider contract impl. '&1{&2}' and prov. IBCR '&3' (ID &4) |
| 659 | IBC Reference setting is missing or invalid |
| 660 | No user account was assigned for IBC Reference ID &1 |
| 661 | Consumer Factory '&1' is not configured |
| 662 | Error during instantiation of Source Proxy for Consumer Factory '&1' |
| 663 | Logical port for source proxy '&1' and IBC/IBCR &2/&3 deleted |
| 664 | Deletion of logical port for source proxy '&1' and IBC/IBCR &2/&3 failed |
| 665 | Pull of subscription for Consumer Proxy '&2' and Log. Port &3 failed: &1 |
| 666 | Pull of notifications failed for Subscription '&2': &1 |
| 667 | ABAP data type '&1' is not supported |
| 668 | Data reference for ABAP data type '&1' could not be created |
| 669 | WSDL &1&2&3&4 does not have readable content |
| 670 | Application key '&1' not assigned to system key '&2' |
| 671 | Failed to convert data to raw |
| 672 | Failed to convert data from raw |
| 673 | Instance is already terminated |
| 674 | Select Option ID '&1' for config. '&2' in conditon '&3' does not exist |
| 675 | Expression ID '&1' for config. '&2' in condition '&3' does not exist |
| 676 | Condition ID '&1' for config. '&2' does not exist |
| 677 | Sel.opt. '&1' for config. '&2' in sel.option '&3' does not exist |
| 678 | Only ranges for the same field can be used in one select option |
| 679 | Select Option '&1' in expression '&2' in condition '&3' does not exist |
| 680 | Log Group '&1' already exists in configuration '&2' |
| 681 | Condition '&1' already exists in configuration '&2' |
| 682 | Expression '&1' already exists in configuration '&2' |
| 683 | Option '&1' in select option is not supported |
| 684 | IBC ID '&1' does not match the rule assigned to Services Registry '&2' |
| 685 | IBC Reference Assignment is missing for Symbolic IBC '&1' |
| 686 | Consumer Factory '&1' used in IS '&2' does not exist in system '&3' |
| 687 | Contract Implement. '&1' does not exist in system of IBC Reference '&2' |
| 688 | Consumer Factory is missing for semantic contract '&1' and IBCR '&2' |
| 689 | Contract Implementation is missing for actor '&1' in int. scenario '&2' |
| 690 | Consumer Factory '&1' does not use Semantic Contract '&2' |
| 691 | Contract Implementation '&1' is not inherited from Semantic Contract '&2' |
| 692 | Republishing of Binding '&1 ( &2 )' was successful |
| 693 | Republishing of Binding '&1 ( &2 )' failed: &3 |
| 694 | UDDI query not possible. Provider contract impl. has not been specified |
| 695 | Search in services registry for matching endpoints |
| 696 | Tolerant search in services registry for matching endpoints |
| 697 | No matching endpoints found in services registry |
| 698 | Successfully created a logical port for provider contract impl. '&1' '&2' |
| 699 | Failed to create a logical port for provider contract impl. '&1' '&2' |
| 700 | Expected version '&1' but version '&2' is found for destination '&3' |
| 701 | Provider IBCR '&1' is assigned to destination '&2' but '&3' is expected |
| 702 | Condition ID '&1' does not exist |
| 703 | Invalid Condition Priority '&2' for Condition '&1'. Allowed: 1 to 255 |
| 704 | Condition Key '&1' does not exist |
| 705 | Priority '&1' already exists |
| 706 | Condition ID '&1' contains no assigned fields |
| 707 | Condition ID '&1' is overlapping and can't be activated |
| 708 | No Condition configured for Determination Mode '&1' |
| 709 | Invalid WSDL flavour code: Only version 1 is supported |
| 710 | Condition ID '&1' already exists |
| 711 | No Binding found for access URL |
| 712 | Condition ID '&1', Expression: '&2' contains no Sender IBC Reference |
| 713 | Condition ID '&1', Expression: '&2' contains no Receiver IBC Reference |
| 714 | Condition ID '&1', Expression: '&2' contains no IBC References |
| 715 | IBCR ID '&1' does not exist |
| 716 | No entry found in 'System Guid Assignments' for destination key '&1' |
| 717 | No entry found in CDT-cache for system key '&1' and consumer factory '&2' |
| 718 | No entry found in CDT-cache for system key '&1' and contract impl. '&2' |
| 719 | Consumer Factory '&1' is not relevant for configuration |
| 720 | Actor '&1' is not defined in Semantic Contract '&2' |
| 721 | Managed System with connection key '&1' does not support application '&2' |
| 722 | No entry found in CDT-cache for system key '&1' and service group '&2' |
| 723 | No entry found in CDT-cache for system key '&1' and service def. '&2' |
| 724 | Rebuild Central Designtime Cache. Contract Impl. '&1' is inconsistent |
| 725 | No Target LP assignment for STCM '&1' and config key '&2' |
| 726 | Inconsistent Target LP assignment for STCM '&1' and config key '&2' |
| 727 | Assign IBC Reference &1 (ID = &2) to a Domain System |
| 728 | No LP Name found for configuration key '&1' |
| 729 | No binding key found for configuration key '&1' |
| 730 | ServiceGroup '&1' with Provider Appl. Key '&2' is already locked by '&3' |
| 731 | Assigned provider interface '&1' '&2' and business appl. ID '&3' |
| 732 | User &1 updated configuration &2 for interface &3 |
| 733 | Services registry query type &1 is invalid |
| 734 | Central Change Processor is locked by '&1' |
| 735 | Starting Services Registry Synchronization |
| 736 | Starting deletion of bindings from Services Registry |
| 737 | Starting publication of bindings into Services Registry |
| 738 | Deletion completed |
| 739 | Publication completed |
| 740 | Services Registry Synchronization completed |
| 741 | Delete binding with binding key '&1' |
| 742 | Publish binding with binding key '&1' |
| 743 | Change name '&1' for Contr. Impl. '&2' already exists in system '&3'. |
| 744 | Connection type '&1' in integration scenario '&2' is invalid |
| 745 | Consumer Factory or Service Group for actor '&1' in IS '&2' is invalid |
| 746 | IBC Reference is missing for actor '&1' in integration scenario '&2' |
| 747 | Cont.Impl. '&1' used in IS '&2' references contract with incomplete name |
| 748 | Contract Implementation Actor Type '&1' is invalid in int. scenario '&2' |
| 749 | Cont. Implementations '&1' and '&2' have the same QName '&3' in IS '&4' |
| 750 | Contract Impl. '&1' in system '&2' must contain Service Definition(s) |
| 751 | No Contract found for Contract Implementation '&1' used in IS '&2' |
| 752 | Contract Impl. '&1' and '&2' reference different contracts ('&3', '&4') |
| 753 | In conn. '&1' Sem. Cont. is missing in Cont. '&2' of Cont. Impl. '&3' |
| 754 | Sem.Cont.'&1' in Cont.Impl.'&2' does not match to Sem.Cont. from ISD '&3' |
| 755 | Cont.Impl. '&1' used in IS '&2' comm. type '&3' should not have SDEF(s) |
| 756 | Cont.Impl. '&1' used in IS '&2' comm. type '&3' should have SDEF(s) |
| 757 | Unknown error |
| 758 | Interfaces are not compatible |
| 759 | Error during calculation of required state: Consumer. Check scenario '&1' |
| 760 | Contract Implementation '&1' used in IS '&2' doesn't exist in system '&3' |
| 761 | Contract '&1' for Cont.Impl.'&2' (IS '&3') doesn't exist in system '&4' |
| 762 | Connection ID '&1' in IS '&2' with type '&3' has invalid entries |
| 763 | Service Group is missing for actor '&1' in integration scenario '&2' |
| 764 | Check connections. Integration Scenario cannot be activated |
| 765 | No Admin Service configured in this system |
| 766 | Admin virtual host is not configured, assignment not possible (Binding &) |
| 767 | Assignment to admin virtual host not possible (Not admin-relevant SDef &) |
| 768 | Binding Key &1 of Service Definition &2 contains an Admin Host assigment |
| 769 | Admin Host is maintained in this system |
| 770 | Admin Host is not maintained in this system |
| 771 | Admin Host assignment not found for Binding Key &1;Service Definition &2 |
| 772 | No Admin relevant services found in this system |
| 773 | No bindings found for Admin relevant Service definition &1 |
| 774 | There is no configuration of administrative host in the system |
| 775 | There is no configuration of administrative host for protocol HTTPS |
| 776 | Service Definition &1 does not correspond to the referenced Contract &2 |
| 777 | No binding selected from Services Registry. |
| 778 | Service Group &1 does not correspond to the referenced Contract &2 |
| 779 | ABAP destination &1 already exists |
| 780 | No connections defined |
| 781 | No service definition found for access URL |
| 782 | The property '&1' is mandatory. Enter valid value |
| 783 | No Matching IF defined for C(&1), P(&2) and Service Group '&3' in IS '&4' |
| 784 | Service Definition is missing in integration scenario '&1' |
| 785 | WSDL Identifier does not exist in WSDL Upload |
| 786 | Configuration saved |
| 787 | Configuration activated |
| 788 | Activation failed |
| 789 | System Key not found for IBC Reference '&1' (IBCR ID = '&2') |
| 790 | IBC ID is initial |
| 791 | Receiver Type is initial |
| 792 | Receiver Name is initial |
| 793 | Connection is a local call. Hence local Shortcut is used. |
| 794 | No compatible Consumer Factory for COIM &1 and IBCR &2 (ID = &3) found |
| 795 | Assign CLIENT IBC Reference for Service Group based connection (IS: '&1') |
| 796 | Assign IBC References to actors |
| 797 | From '&1' to '&2' in IS '&3' user account doesn't match settings in '&4' |
| 798 | For Connection Type '&1' Service Group must be assigned to both actors |
| 799 | For Connection Type '&1' Service Group must be assigned to one actor |
| 800 | Function is only supported in non-central (managed) systems |
| 801 | Implementing Class '&1' for IBC Reveiver Type '&2' is missing |
| 802 | Service Group '&1' used in IS '&2' does not exist in system '&3' |
| 803 | New IBC ID '&1' is assigned to service definition '&2' |
| 804 | IBC ID '&1' has been unassigned from service definition '&2' |
| 805 | Publication of new binding for service definition '&1' |
| 806 | Domain system '&1' (Key '&2') used in IS '&3' isn't assigned to a domain |
| 807 | Designtime object '&1' does not exist |
| 808 | Service group '&1' does not exist |
| 809 | IBC Reference '&1' is used in Logon Data Assignment '&2' |
| 810 | IBC Reference '&1' is used in Integration Scenario '&2' |
| 811 | Search criteria may lead to extensive resultset. Limit your criteria |
| 812 | ABAP destination &1 does not exists and cannot be modified |
| 813 | ABAP destination name is initial |
| 814 | Domain system '&1' (Key '&2') used in IS '&3' is not available |
| 815 | There is no binding selected. Please select one. |
| 816 | Initial ext. name of service definition '&1' in system '&2' (IS: '&3') |
| 817 | Matching IF for C(&1),P(&2) and Serv.Group '&3' is inconsistent (IS '&4') |
| 818 | Service Group for actor '&1' in IS '&2' is invalid |
| 819 | Cons.Factory/Serv.Group for actor '&1' and conn.type '&2' is initial (&3) |
| 820 | Contract Impl.'&1' doesn't contain consumer implementation in system '&2' |
| 821 | All MEX bindings are already used. |
| 822 | IBC Reference for actor '&1' should not be initial |
| 823 | Unsupported entity type '&1' for entity '&2' |
| 824 | WSDL &1&2&3&4 retrieved successfully |
| 825 | &1 WSDLs found in services registry |
| 826 | WSDL &1&2&3&4 cannot be retrieved |
| 827 | No authentification method. Please select at least one auth. method. |
| 828 | No common domain found for domain systems '&1' and '&2' used in IS '&3' |
| 829 | Assign CLIENT IBC Reference to Contract Impl. '&1' used in IS '&2' |
| 830 | System is not available |
| 831 | Name is too long. Restrict name to '&1' characters. |
| 832 | IBCR '&1' is substitued with CLIENT IBCR '&2' for Serv.Group connection |
| 833 | Domain System '&1' does not support IBC determination via SOAP Header |
| 834 | No Logical Receiver maintained for Consumer Factory &1 |
| 835 | No Logical Sender maintained for Consumer Factory &1 |
| 836 | No Technical Receiver maintained for Consumer Factory &1 |
| 837 | No services and bindings selected. Select at least one service or binding |
| 838 | All selected objects cannot be activated. |
| 839 | All selected objects cannot be deactivated. |
| 840 | All selected objects cannot be deleted. |
| 841 | No logical port selected. Select at least one logical port. |
| 842 | No logical port selected. Select one logical port. |
| 843 | Logical Port is PI based, it could not be a default logical port. |
| 844 | Invalid binding key '&1' found for object '&2' |
| 845 | No WSDLs found in services registry for inbound interface '&1' '&2' |
| 846 | IBC determination type must not be empty |
| 847 | No destination found for IBC Reference &1 (ID = &2) |
| 848 | No destination found for provider application key &1 |
| 849 | No system key for distribution found for destination key &1 |
| 850 | No destination key for distribution found for destination key &1 |
| 851 | No destination name for distribution found for destination key &1 |
| 852 | Image Version is not specified (DT object: &1 / &2) |
| 853 | Image Version &3 does not exist (DT object: &1 / &2) |
| 854 | Logon data assignment with ID = &1 and type = &2 does not exist |
| 855 | Error saving data in Database(DT object: &1 /&2) with Version ID: &3 |
| 856 | Image version &3 (DT object: &1 / &2) is not locked |
| 857 | Error reading DT data for object:'&1' Type: '&2' |
| 858 | Logon data container: '&1' Type: '&2' is inactive |
| 859 | Template with name '&1' already exists |
| 860 | Template name is initial. Please enter a name. |
| 861 | Image version &3 (DT object: &1 / &2) already exists |
| 862 | The logon data container doesn't support the auth.methods of profile '&1' |
| 863 | No template selected. Select at least one template. |
| 864 | Image for DT object &1 / &2 cannot be created: Transformation error |
| 865 | Object type &1 is not supported |
| 866 | WSIL query not possible. The provider IBCR has not been specified |
| 867 | Assigned provider IBCR '&1' (ID &2) |
| 868 | Try to create an RFC logical port using FM-based WSIL query |
| 869 | Integration scenario '&1' does not contain connections to ping |
| 870 | Ping is not possible because of inconsistencies. Perform check connection |
| 871 | Value of version ID2 '&2' must be greater than version ID1 '&1' |
| 872 | Version ID '&1' and '&2' are not adjacent |
| 873 | Error saving data in database '&1' |
| 874 | Managed system '&1' cannot complete operation ping |
| 875 | No ping results received from managed system '&1' |
| 876 | Invalid input supplied |
| 877 | Invalid previous version ID '&1' for object '&2' and type '&3' |
| 878 | Invalid change ID '&1' |
| 879 | Change already exists between versions '&1' and '&2'(Object:'&3'(&4)) |
| 880 | Change object with ID:'&3' (DT object: &1 / &2) is not locked |
| 881 | Change object with ID: &3 (DT object: &1 / &2) already exists |
| 882 | Republishing of Service Definition '&1' failed: &2 |
| 883 | No logical port found for the given consumer proxy and provider |
| 884 | Ping successful |
| 885 | Republishing of Service Definition '&1' was successful |
| 886 | No logical ports found for the given service group and provider |
| 887 | No logical ports found for the given consumer factory and provider |
| 888 | No delta found between image version &1 and &2 (DT object: &3/&4) |
| 889 | No agents found for DT object '&1' of type '&2' |
| 890 | Type &1 of configuration template is invalid |
| 891 | Change ID &1 created for delta between versions &2 and &3(DT object: &4) |
| 892 | Cannot modify read-only instance of config. template "&2", type "&1" |
| 893 | Image version '&1' saved for DT object '&2' of type '&3' |
| 894 | Token Issuer is required. Enter Token Issuer |
| 895 | Invalid Queue ID '&1' |
| 896 | Wrong function module info retrieved. Requested: '&1', Retrieved '&2' |
| 897 | Function module '&1' does not exist in provider system '&2' |
| 898 | Consumer proxy '&1' is not RFC type |
| 899 | No function modules found for consumer proxy '&1' |