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