SRT_WSP3 - SRT: Web Service Configuration Messages 3
The following messages are stored in message class SRT_WSP3: SRT: Web Service Configuration Messages 3.
It is part of development package SOAP_CONFIG in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Framework".
It is part of development package SOAP_CONFIG in software component BC-ESI-WS-ABA-CFG. This development package consists of objects that can be grouped under "SOAP Configuration Framework".
Message Nr ▲ | Message Text |
---|---|
000 | Failed to create an RFC logical port for consumer proxy '&1' |
001 | Domain System Group '&1' does not exist |
002 | Domain System Group '&1' already exists |
003 | Domain System Group '&1' is not locked. Lock it first |
004 | Domain System Group '&1' is already locked by '&2' |
005 | Domain System Group '&1' does not have a description in language '&2' |
006 | Domain System Group '&1' could not be saved |
007 | Domain System '&1' is already assigned to Domain System Group '&2' |
008 | Check of template '&1' was successful |
009 | Filename is initial. Enter a valid filename |
010 | Config. Template '&1' already exists and overwriting it not allowed |
011 | The imported configuration template structure is empty |
012 | Group name '&1' is not allowed. Choose a different name |
013 | You use a new layout for the Web Service Config. Click for old version |
014 | Connection from '&1' to '&2' with consumer factory '&3' already exists |
015 | No properties defined. Define at least one properties for the template |
016 | Phase '&1' successfully confirmed |
017 | Confirm phase '&1' manually |
018 | Config. template '&1' type '&2' is not valid. Run method check for detail |
019 | No properties defined for configuration template '&1' type '&2' |
020 | Configuration template '&1' type '&2' cannot be modified |
021 | Location of property '&1'{'&2'} doesn't match the type of template '&3' |
022 | Value '&1' of property '&2'{'&3'} is not valid in config. template '&4' |
023 | Error when parsing the WSDL |
024 | Used authentication method '&1' and username '&2' |
025 | No system key found for IBCR '&1' (ID &2) to access CDTC |
026 | Consumer factory '&1' is already assigned to IBCR '&2' in scenario '&3' |
027 | Service group '&1' is already assigned to IBCR '&2' in scenario '&3' |
028 | This binding was created or changed with new UI layout. |
029 | Use new layout of UI layout in order to display or edit this binding. |
030 | Repair connection(&1) from IBC Ref. '&2' to '&3' as it is inconsistent |
031 | Consumer factory is initial for actor '&1' |
032 | Contract implementation '&1' for actor '&2' should contain only one SDEF |
033 | Service group is initial for actor '&1' |
034 | Domain system '&1' supports only service group based contract impl. |
035 | Domain system '&1' does not support communication type RFC |
036 | LP of SGroup '&1' and provider appl. '&2' in '&3' cannot be deleted. |
037 | Profile changed from '&1'(&2) to '&3'(&4) |
038 | Destination changed from '&1'(&2) to '&3'(&4) |
039 | Matching interface changed from '&1'{'&2'} to '&3'{'&4'} |
040 | Scenario '&1' is active and cannot be deleted |
041 | Scenario '&1' cannot be deleted as there exist non-processed requests |
042 | Only one client application or external application is allowed. |
043 | SGroup '&1' will be configured in '&2' with provider application '&3' |
044 | Assigned consumer(source) proxy changed from '&1'(&2) to '&3'(&4) |
045 | User Account changed from '&1'(&2) to '&3'(&4) |
046 | Referred provider interface changed from '&1'{'&2'} to '&3'{'&4'} |
047 | Endpoint of SDef. '&1' will be created in '&2' with profile '&3'(&4) |
048 | Scenario based release is not supported from the involved domain systems |
049 | LP of CFact. '&1' cons IBCR '&2' prov IBCR in '&4' cannot be deleted. |
050 | LP of SGroup '&1' and provider appl. '&2' will be deleted in '&3' |
051 | LP of CFact. '&1' cons IBCR '&2' prov IBCR '&3' will be deleted in '&4' |
052 | CFact.'&1' will be config. in '&2' with cons IBCR '&3' and prov IBCR '&4' |
053 | Endpoint of SDef. '&1' with profile '&2'(&3) in '&4' cannot be deleted. |
054 | Endpoint of SDef. '&1' with profile '&2'(&3) will be deleted in '&4' |
055 | No information found for domain system key '&1' |
056 | No action is required |
057 | No consumer found for consumer factory '&1' in system '&2' |
058 | No consumer impl. found for contract implementation '&1' in system '&2' |
059 | The connection is inconsistent and cannot be distributed |
060 | Change processor is currently processing scenario '&1' of user '&2' |
061 | Central Design Time Cache is up to date |
062 | Central Design Time Cache is not up to date for system '&1' |
063 | Design Time Cache is being pulled from system '&1' |
064 | Update of Cache for system '&1' was not successfull |
065 | Endpoint of SDef. '&1' with profile '&2'(&3) already exists in '&4'. |
066 | Endpoint of SDef. '&1' with profile '&2'(&3) doesn't exists in '&4'. |
067 | Publication of SDef. '&1' needs to be updated with IBCR '&2' in '&3' |
068 | LP of CFact. '&1' cons IBCR '&2' prov IBCR '&3' already exists in '&4'. |
069 | LP of CFact. '&1' cons IBCR '&2' prov IBCR '&3' doesn't exists in '&4'. |
070 | Provider contract implementation changed from '&1'{'&2'} to '&3'{'&4'} |
071 | LP of CFact. '&1' cons IBCR '&2' prov IBCR '&3' will be updated in '&4'. |
072 | Central Design Time Cache is updated |
073 | Consumer contract implementation changed from '&1' to '&2' |
074 | It is used in other integration scenario connection |
075 | LP of SGroup '&1' and provider appl. '&2' doesn't exists in '&3'. |
076 | LP of CProxy '&1' in SGroup '&2' prov. appl. '&3' will be updated in '&4' |
077 | LP of CProxy '&1' in SGroup '&2' prov. appl. '&3' already exists in '&4' |
078 | LP of CProxy '&1' in SGroup '&2' prov. appl. '&3' will be created in '&4' |
079 | LP of CProxy '&1' in SGroup '&2' prov. appl. '&3' will be deleted in '&4' |
080 | Connection with assignment ID '&1' does not exist in scenario '&2' |
081 | Cache entry with ID '&1' does not exist |
082 | No provider system found for logical system '&1' |
083 | No need to maintain logon data assignments |
084 | Start configuration of Event Provider '&1' |
085 | Event Provider '&1' blocked by other object in memory |
086 | Configuration of Event Provider '&1' completed |
087 | Configuration of Event Provider '&1' failed |
088 | Delete configuration of Event Provider '&1' |
089 | Deletion of configuration for Event Provider '&1' completed |
090 | Deletion of configuration for Event Provider '&1' failed |
091 | Failed to find active Event Provider in Contract Implementation '&1' |
092 | Event Provider '&1' requested but '&2' found in COIM '&3' |
093 | Error when initializing Event Provider '&1': '&2&3&4' |
094 | Start deletion of logical port for Event Provider '&1' and IBC/IBCR &2/&3 |
095 | Logical port for Event Provider '&1' and IBC/IBCR &2/&3 deleted |
096 | Deletion of logic. port for Event Provider '&1' and IBC/IBCR &2/&3 failed |
097 | Invalid domain system '&1' chosen. Value ignored in search. |
098 | Search values are initials. Search can not be done. |
099 | Invalid provider system '&1' chosen. Value ignored in search. |
100 | WSDL assignment already exists for ID: &1 and Domain System key: &2 |
101 | Parameters are not properly filled |
102 | WSDL assignment already exists for this Interface & Domain System key |
103 | Referenced endpoint not found in Services Registry |
104 | ID: &1 is assigned to a Domain System key: &2 |
105 | LP of EventPr.'&1' cons IBCR '&2' prov IBCR '&3' in '&4' can't be deleted |
106 | LP of EventPr. '&1' cons IBCR '&2' prov IBCR '&3' will be deleted in '&4' |
107 | LP of EventPr. '&1' cons IBCR '&2' prov IBCR '&3' will be updated in '&4' |
108 | LP of EventPr. '&1' cons IBCR '&2' prov IBCR '&3' already exists in '&4' |
109 | LP of EventPr. '&1' cons IBCR '&2' prov IBCR '&3' doesn't exist in '&4' |
110 | EventPr.'&1' will be config. in '&2' with co. IBCR '&3' and pr. IBCR '&4' |
111 | Modification not supported for selected WSDL part |
112 | Subject '&1' ('&2') not found in WSDL |
113 | Different values for property '&1' in participating Service Definitions |
114 | Unknown type '&1' of Compound Service Definition |
115 | Unknown Compound Service Definition '&1' |
116 | Could not determine Service Definition for an operation in Compound SD |
117 | Initial Access URL for selected binding, WSDL cannot be completed |
118 | Management connection '&1' does not support 7.00/7.01 connectivity |
119 | Destination could not be determined from the task data for provider &v1 |
120 | System &1 already exists |
121 | Service Definition &1 in system &2 already exists |
122 | Upgrade of management connection to system &1/&2 failed |
123 | Data preparation in central system failed for service group &1 |
124 | No WSDLs were found for inbound interface '&1' '&2' |
125 | Build of Central Design Time Cache failed: &1&2&3&4 |
126 | Object with key &1 does not exist in Central Design Time Cache. |
127 | Alternative Access URL '&1' does not start with '/'. |
128 | Character '&2' in Alternative Access URL '&1' not allowed. |
129 | '/' after '/' in Alternative Access URL '&1' is not allowed. |
130 | Connection to Central Service Registry does not exist. |
131 | Archive name is initial |
132 | No archive file found that matches search criteria |
133 | Management Connection to System '&1' not available |
134 | Reverse Proxy &1 already exists |
135 | Error while adding a reverse proxy: &1 |
136 | Proxy Name must not be initial |
137 | Incoming host must not be initial |
138 | Incoming port must not be initial |
139 | Cannot read reverse proxy: &1 |
140 | Reverse proxy with name &1, incoming host &2 and port &3 does not exist |
141 | Can not delete reverse proxy with name &1, incoming host &2 and port &3. |
142 | Error while deletion of reverse proxy: &1 |
143 | System &1/&2 is already managed. Register it with same system/tenant key. |
144 | System &1/&2 is already managed. Register it with same external id. |
145 | System with id &1 is already managed. Register it with same system key. |
146 | System with id &1 is already managed. Register it with same tenant key. |
147 | System with id &1 is already managed. Register it with same system id. |
148 | System with id &1 is already managed. Register it with same client no. |
149 | System with tenant &1 is already managed. Register with same system key. |
150 | System with tenant &1 is already managed. Register with same external id |
151 | System with tenant &1 is already managed. Register with same system id. |
152 | System with tenant &1 is already managed. Register with same client no. |
153 | System &1 has same system key as system &2 that is already registered |
154 | No Service found in WSDL |
155 | No Interface found in WSDL |
156 | No Binding found in WSDL |
157 | No Binding Property found in WSDL |
158 | Cannot instantiate class &1 |
159 | Wrong authentication (HTTP Error '&1') for accesing WSDL '&2&3&4' |
160 | Missing authorization (HTTP Error '&1') for accessing WSDL '&2&3&4' |
161 | Error '&1' when accessing WSDL '&2&3&4' |
162 | Error while parsing WSDL '&1&2&3' |
163 | Inconsistency in Soamanager detected. User '&1' continued to work. |
164 | Inconsistency in Soamanager detected. User '&1' logged off. |
165 | Inconsistency in Soamanager detected. User '&1' went to consistency check |
166 | Inconsistency in Soamanager detected. Message: &1 |
167 | Invalid URL &1 |
168 | Own provider system can not be created. Name &1 already exists. |
169 | No authority: &1 |
170 | Getting business system name failed with return code: &1 |
171 | Lock error: &1 |
172 | Enter a non empty class name |
173 | Not authorized to perform '&1' for profile '&2' [Auth.Obj. &3] |
174 | Not authorized to perform '&1' for domain '&2' [Auth.Obj. &3] |
175 | Not authorized to perform '&1' for domain system '&2' [Auth.Obj. &3] |
176 | Not authorized to perform '&1' for scenario '&2' [Auth.Obj. &3] |
177 | Not authorized to perform '&1' for logon data '&2' [Auth.Obj. &3] |
178 | Not authorized to perform '&1' for provider system '&2' [Auth.Obj. &3] |
179 | Not authorized to perform '&1' for services registry [Auth.Obj. &2] |
180 | Not authorized to perform '&1' for system settings '&2' [Auth.Obj. &3] |
181 | Not authorized to perform '&1' for logon ass '&2' and '&3' [Auth.Obj. &4] |
182 | Not authorized to perform '&1' for LRD '&2' [Auth.Obj. &3] |
183 | Not authorized to perform '&1' for consumer config. '&2' [Auth.Obj. &3] |
184 | Not authorized to perform '&1' for provider config. '&2' [Auth.Obj. &3] |
185 | Not authorized to perform '&1' for system '&2' [Auth.Obj. &3] |
186 | Service Definition '&1' does not exist |
187 | &1 service(s) found in Services Registry |
188 | Operation &1 (Namespace &2) is not configured. |
189 | Not authorized to perform '&1' for configuration templates [Auth.Obj. &2] |
190 | Not authorized to perform '&1' for Design Time Cache [Auth.Obj. &2] |
191 | Not authorized to start report '&1' |
192 | &1&2&3&4 |
193 | Port Type &1 &2 does not exist |
194 | Service Group &1 does not exist |
195 | Consumer Proxy &1 does not exist |
196 | Service Definition &1 does not exists |
197 | Cannot open Soamanager |
198 | Provider system can not be created. Name &1 already exists. |
199 | Retrieve WSDL from Services Registry |
200 | Deserialization for type &1 failed: &2&3&4 |
201 | Service Registry (&1) does not contain any object with id &2. |
202 | Bus. Appl. Id from Service Registry is different from WSIL retrieval. |
203 | No Business Application Id could be retrieved. |
204 | Primary Service Registry is not set |
205 | Retrieved Business Application Id from &1 |
206 | Business Application Id from &1 is valid |
207 | Bus. Appl. Id from &1 is different from the one of provider system |
208 | Provider system has no Business Application ID assigned |
209 | Retrieval from &1 changed existing Business Application Id |
210 | No Business Application ID is maintained or retrieved |
211 | Skip configuration by Service Registry |
212 | Skip configuration by WSIL |
213 | SLD Id &2 can not be found in Service Registry &1. |
214 | Provider system is defined not to use Services Registry |
215 | Provider system is defined not to use WSIL |
216 | Nothing to delete from Service Registry |
217 | Nothing to publish to Service Registry |
218 | Initializing WSIL Cache |
219 | Initializing of WSIL Cache completed |
220 | Invalid WSDL flavour code: Incorrect value for Show Extensibility As Any |
221 | WSIL Cache successfully initialized |
222 | Initializing of WSIL Cache failed |
223 | Delete Logical Port &1 for Consumer Proxy &2 |
224 | Delete Endpoint for Service &1 and profile &2 version &3 |
225 | Consumer Factory &1 has already been configured. |
226 | Event provider &1 has already been configured |
227 | Create Endpoint for Service &1 and profile &2 version &3 |
228 | Activate Endpoint for Service &1 and profile &2 version &3 |
229 | Delete Configuration for Consumer factory &1 |
230 | Delete Configuration for Event Provider &1 |
231 | Endpoint for Service &1 and profile &2 version &3 created |
232 | Skip building DT cache for consumer proxy &1: &2&3&4 |
233 | Skip building DT cache for service definition &1: &2&3&4 |
234 | Consumer proxy &1 does not exist or is inconsistent |
235 | Service definition &1 does not have a simplified configuration |
236 | Binding key &1 is not valid for service definition &2 |
237 | Rule Name is initial. Please enter a name. |
238 | Rule Name &1 already exists |
239 | No available protocol, neither http nor https is availabe |
240 | Internal error - must only be called within http handler |
241 | Unsupported protocol: '&1' |
242 | No server for protocol '&1' |
243 | Connection for service group &1 refers to missing managed system &2 |
244 | Wrong usage - Binding key required |
245 | Path cannot be mapped to external: '&1' |
246 | Service is not released external, external node cannot be used |
247 | WSDL retrieval not supported by section '&1', only available by URL |
248 | Config key &1 is not valid for service definition &2 |
249 | No binding for config key &1 of service definition &2 |
250 | System can't be set as central system. It is managed by another system. |
251 | System can't be set as non-central: Unprocessed tasks in scenario &1 |
252 | System can't be set as non-central: There are managed systems |
253 | System can't be set as non-central: There are external systems |
254 | System can't be set as non-central: Scenario &1 is active |
255 | Invalid fragments are removed in WSDL &1 |
256 | Upload failed for WSDL &1 |
257 | No valid interfaces in WSDL &1 |
258 | Deletion failed for WSDL &1 |
259 | Update failed for WSDL &1 |
260 | Subject '&1', type '&2' deleted because of unsupported entitiies. |
261 | No Service found in WSDL. Subjects with unsupported policies removed |
262 | No Interface found in WSDL. Subjects with unsupported policies removed |
263 | No Binding found in WSDL. Subjects with unsupported policies removed |
264 | No Binding Property found in WSDL. Subjects with unsupp. policies removed |
265 | Unsupported property '&1' removed |
266 | Unsupported assertion '&1' removed |
267 | Logical port &1 for consumer proxy &2 already exists |
268 | Logical port &1 for consumer proxy &2 does not exist |
269 | Browser Plugin for Java not available, see SAP Note 2692483 |
270 | Multiple Receivers found with same priority found for Service Group &1 |
271 | Editing of Provider System is restricted as it is already used |
272 | Provider system for &1 missing. |
273 | Design Time Cache Error for &3 &1: &2 |
274 | Build Design Time Cache for &2 &1 was successful |
275 | Remove Design Time Cache for &2 &1 was successful |
276 | Configuration for Service Group &1 and Provider System &2 not available |
277 | Operation with name "&1" and namespace "&2" is defined more than once |
278 | Binding with name "&1" and namespace "&2" is defined more than once |
279 | Interface with name "&1" and namespace "&2" is defined more than once |
280 | Service with name "&1" and namespace "&2" is defined more than once |
281 | Object of type &1 with name "&2" namespace "&3" is defined more than once |
282 | Select a provider IBCR for logical retriever determination |
283 | Service Def. "&1" with auth level "&2" does not allow auth. method "&3" |
284 | Service Def. "&1" does not allow auth. method "&2" |
285 | Transport Level Security type is "&1", but "&1" is disabled. |
286 | Change of WSIL URL not possible as system would change. |
287 | Descryption of credentials failed: &1 &2 &3 &4 |
288 | Authentication &1 not supported for SAP Cloud Connector |