CRM_WSC - WSC: Message Class for web Service Consumption Tool
The following messages are stored in message class CRM_WSC: WSC: Message Class for web Service Consumption Tool.
It is part of development package CRM_GENIL_WSC in software component CA-WUI-WST. This development package consists of objects that can be grouped under "GenIL Component for Web Service Consumption".
It is part of development package CRM_GENIL_WSC in software component CA-WUI-WST. This development package consists of objects that can be grouped under "GenIL Component for Web Service Consumption".
Message Nr ▲ | Message Text |
---|---|
000 | &1 &2 &3 &4 |
001 | Operation &1 does not exist |
002 | Generation of component &1 started |
003 | Generation of component &1 completed |
101 | Specify the component name |
102 | Specify the prefix for business objects |
103 | Select an existing Web service proxy or create a new one |
104 | Select any operation |
105 | Specify the application name |
106 | Specify the target ID |
107 | Specify the package for application |
108 | Web Client application &1 generated |
109 | Transport request is not set |
110 | Proxy &1 generated |
111 | System cannot generate a proxy; use transaction SPROXY instead |
112 | Use SOAMANAGER to create a logical port for &1 |
113 | Component &1 already exists |
114 | Specify a valid URL to access a WSDL document |
115 | Use the transaction SOAMANAGER to create a logical port |
116 | Generation failed; it is not possible to consume &1 operation |
200 | Not all fields required to create a new operation have been filled |
201 | Component has to be generated again after a prefix change |
202 | Component &1 could not be deleted |
203 | Operation &1 could not be deleted |
204 | Tree could not be deleted |
205 | Component &1 could not be saved |
206 | Another new operation exists that has not yet been saved |
207 | Data entered is not unique; &1 appears more than once |
208 | Read input: at least one field must be designated as a key field |
209 | Read output: selected structure/table &1 must have the BO name filled |
210 | Query &1 input: at least one field must be selected |
211 | Query &1 output: at least one field must be designated as a key field |
212 | Only one read operation is allowed per component |
213 | Prefix must be unique; prefix &1 is already used |
214 | Read output: selected table &1 must have at least one key field |
215 | Component &1 already exists in IMG under Generic Interaction Layer/Object |
216 | Component &1 could not be stored in general component table CRMC_GIL_COMP |
217 | Component must have one read operation |
218 | You can only copy operations of type "Query" |
219 | Number of key fields in read input is not the same as in query &1 output |
220 | Field &1 is set as key field in query &2 output but not in read input |
221 | Field &1 is set as key field in read input but not in query &2 output |
222 | Messages for component &1: |
223 | No errors found for component &1 |
224 | Number of key fields in read input is not the same as in read output |
225 | Field &1 is set as key field in read input but not in read output |
226 | Field &1 is set as key field in read output but not in read input |
227 | Operation with name &1 already exists in the component |
228 | Operation cannot be renamed as it does not exist |
229 | Only "Read" and "Query" are supported |
230 | You are not allowed to change the prefix of an existing component |
231 | Operation name must start with the component prefix |
232 | Read output: exactly one structure must be designated as entry point |
233 | Query output: exactly one structure must be designated as entry point |
234 | Query output: parent of designated entry point must be a table |
235 | Proxy class &1 is invalid |
236 | Proxy method &1 is invalid |
237 | Prefix for component &1 is empty; saving is not possible |
238 | Function not supported; save first |
239 | Unsaved changes exist; try to cancel and save before creating |
240 | BO name must not be empty |
241 | BOL field name must not be empty |
242 | Save before making the next change |
243 | Key fields in query output &1 must be inside a structure (not a table) |
244 | Key fields in read output do not match the generated key structure |
245 | Key fields in query output &1 do not match the generated key structure |
300 | Creation of structure &1 failed |
301 | Activation of structure &1 failed |
302 | Error generating DDIC name &1 |
303 | Field could not be added to structure &1 |
304 | DDIC structure check failed |
305 | Deletion of structure &1 failed |
306 | Deletion of structure &1 for proxy object &2 failed |
307 | TADIR entry for &1 could not be written |
308 | Generation of DDIC structures failed |
309 | Generation of table failed; name is missing for &1 |
310 | Structure name for updating field table is missing |
311 | BOL field name &1 is already used within the structure |
312 | Root node &2 with BOL name &1 has an empty key structure |
313 | Node is initial |
314 | Select a structure for the query input |
315 | Only one child should exist for table type |
316 | Do not select a node of type "element" for the query input |
317 | Could not find entry point for operation of type "&1" |
318 | No attribute exists in the structure &1 |
350 | Creation of target tree failed for proxy object &1 |
351 | Creation of target tree failed for component &1 |
352 | Error occurred when creating node for flat structure |
353 | Error occurred when creating root node for proxy object &1 |
354 | Error occurred when creating target tree |
355 | Error occurred when adding nodes to target tree |
356 | Error occurred when adding fields to a node (flat structure) |
400 | Source tree cannot be created as class &1 was not found |
401 | Source tree cannot be created as method &1 was not found for class &2 |
402 | Source tree cannot be created as method &1 has no input parameter |
403 | Source tree cannot be created as method &1 has no output parameter |
500 | Nothing found |
501 | System error when calling method &1 in proxy class &2 |
600 | Transport request used: &1 |
601 | Table &1 cannot be included in transport request |
602 | No entries to be transported in table &1 |
603 | Authorization &1 is not assigned to user &2 for &3 |
604 | Object &1 &2 &3 could not be included in transport request |
605 | Object &1 &2 &3 of component &4 will not be transported |
606 | Local object &1 &2 &3 will not be transported |
700 | Pre-activation check failed; further processing stopped |
800 | No proxy created; check system proxy setting and appl. log with handle &1 |
801 | Content of local file must be provided as XSTRING |
802 | No proxy was created; it may already exist or a generic error occurred |
803 | The given URL is not usable; no proxies generated |
804 | Proxy for port type &1 already exists; no new proxy created |