SAP ABAP Message Class CRM_WSC (WSC: Message Class for CRM web Service Consumption Tool)
Basic Data
Hierarchy
☛
WEBCUIF (Software Component) SAP Web UI Framework
⤷ CA-WUI-WST (Application Component) Web Services Tool
⤷ CRM_GENIL_WSC (Package) GenIL Component for Web Service Consumption
⤷ CA-WUI-WST (Application Component) Web Services Tool
⤷ CRM_GENIL_WSC (Package) GenIL Component for Web Service Consumption
Attributes
Message class | CRM_WSC | |
Short Description | WSC: Message Class for CRM web Service Consumption Tool | |
Changed On | 20110908 | |
Last Changed At | 163517 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | Operation &1 does not exist | The short text describes the object sufficiently | |
3 | 002 | Generation of component &1 started | The short text describes the object sufficiently | |
4 | 003 | Generation of component &1 completed | The short text describes the object sufficiently | |
5 | 101 | Specify the component name | The short text describes the object sufficiently | |
6 | 102 | Specify the prefix for business objects | The short text describes the object sufficiently | |
7 | 103 | Select an existing Web service proxy or create a new one | The short text describes the object sufficiently | |
8 | 104 | Select any operation | The short text describes the object sufficiently | |
9 | 105 | Specify the application name | The short text describes the object sufficiently | |
10 | 106 | Specify the target ID | The short text describes the object sufficiently | |
11 | 107 | Specify the package for application | The short text describes the object sufficiently | |
12 | 108 | Web Client application &1 generated | The short text describes the object sufficiently | |
13 | 109 | Transport request is not set | The short text describes the object sufficiently | |
14 | 110 | Proxy &1 generated | The short text describes the object sufficiently | |
15 | 111 | System cannot generate a proxy; use transaction SPROXY instead | The short text describes the object sufficiently | |
16 | 112 | Use SOAMANAGER to create a logical port for &1 | The short text describes the object sufficiently | |
17 | 113 | Component &1 already exists | The short text describes the object sufficiently | |
18 | 114 | Specify a valid URL to access a WSDL document | The short text describes the object sufficiently | |
19 | 115 | Use the transaction SOAMANAGER to create a logical port | The short text describes the object sufficiently | |
20 | 116 | Generation failed; it is not possible to consume &1 operation | The short text describes the object sufficiently | |
21 | 200 | Not all fields required to create a new operation have been filled | The short text describes the object sufficiently | |
22 | 201 | Component has to be generated again after a prefix change | The short text describes the object sufficiently | |
23 | 202 | Component &1 could not be deleted | The short text describes the object sufficiently | |
24 | 203 | Operation &1 could not be deleted | The short text describes the object sufficiently | |
25 | 204 | Tree could not be deleted | The short text describes the object sufficiently | |
26 | 205 | Component &1 could not be saved | The short text describes the object sufficiently | |
27 | 206 | Another new operation exists that has not yet been saved | The short text describes the object sufficiently | |
28 | 207 | Data entered is not unique; &1 appears more than once | The short text describes the object sufficiently | |
29 | 208 | Read input: at least one field must be designated as a key field | The short text describes the object sufficiently | |
30 | 209 | Read output: selected structure/table &1 must have the BO name filled | The short text describes the object sufficiently | |
31 | 210 | Query &1 input: at least one field must be selected | The short text describes the object sufficiently | |
32 | 211 | Query &1 output: at least one field must be designated as a key field | The short text describes the object sufficiently | |
33 | 212 | Only one read operation is allowed per component | The short text describes the object sufficiently | |
34 | 213 | Prefix must be unique; prefix &1 is already used | The short text describes the object sufficiently | |
35 | 214 | Read output: selected table &1 must have at least one key field | The short text describes the object sufficiently | |
36 | 215 | Component &1 already exists in IMG under Generic Interaction Layer/Object | The short text describes the object sufficiently | |
37 | 216 | Component &1 could not be stored in general component table CRMC_GIL_COMP | Space: object requires documentation | |
38 | 217 | Component must have one read operation | The short text describes the object sufficiently | |
39 | 218 | You can only copy operations of type "Query" | The short text describes the object sufficiently | |
40 | 219 | Number of key fields in read input is not the same as in query &1 output | The short text describes the object sufficiently | |
41 | 220 | Field &1 is set as key field in query &2 output but not in read input | The short text describes the object sufficiently | |
42 | 221 | Field &1 is set as key field in read input but not in query &2 output | The short text describes the object sufficiently | |
43 | 222 | Messages for component &1: | The short text describes the object sufficiently | |
44 | 223 | No errors found for component &1 | The short text describes the object sufficiently | |
45 | 224 | Number of key fields in read input is not the same as in read output | The short text describes the object sufficiently | |
46 | 225 | Field &1 is set as key field in read input but not in read output | The short text describes the object sufficiently | |
47 | 226 | Field &1 is set as key field in read output but not in read input | The short text describes the object sufficiently | |
48 | 227 | Operation with name &1 already exists in the component | The short text describes the object sufficiently | |
49 | 228 | Operation cannot be renamed as it does not exist | The short text describes the object sufficiently | |
50 | 229 | Only "Read" and "Query" are supported | The short text describes the object sufficiently | |
51 | 230 | You are not allowed to change the prefix of an existing component | The short text describes the object sufficiently | |
52 | 231 | Operation name must start with the component prefix | The short text describes the object sufficiently | |
53 | 232 | Read output: exactly one structure must be designated as entry point | The short text describes the object sufficiently | |
54 | 233 | Query output: exactly one structure must be designated as entry point | The short text describes the object sufficiently | |
55 | 234 | Query output: parent of designated entry point must be a table | The short text describes the object sufficiently | |
56 | 235 | Proxy class &1 is invalid | The short text describes the object sufficiently | |
57 | 236 | Proxy method &1 is invalid | The short text describes the object sufficiently | |
58 | 237 | Prefix for component &1 is empty; saving is not possible | The short text describes the object sufficiently | |
59 | 238 | Function not supported; save first | The short text describes the object sufficiently | |
60 | 239 | Unsaved changes exist; try to cancel and save before creating | The short text describes the object sufficiently | |
61 | 240 | BO name must not be empty | The short text describes the object sufficiently | |
62 | 241 | BOL field name must not be empty | The short text describes the object sufficiently | |
63 | 242 | Save before making the next change | The short text describes the object sufficiently | |
64 | 243 | Key fields in query output &1 must be inside a structure (not a table) | The short text describes the object sufficiently | |
65 | 244 | Key fields in read output do not match the generated key structure | Space: object requires documentation | |
66 | 245 | Key fields in query output &1 do not match the generated key structure | Space: object requires documentation | |
67 | 300 | Creation of structure &1 failed | The short text describes the object sufficiently | |
68 | 301 | Activation of structure &1 failed | The short text describes the object sufficiently | |
69 | 302 | Error generating DDIC name &1 | The short text describes the object sufficiently | |
70 | 303 | Field could not be added to structure &1 | The short text describes the object sufficiently | |
71 | 304 | DDIC structure check failed | The short text describes the object sufficiently | |
72 | 305 | Deletion of structure &1 failed | The short text describes the object sufficiently | |
73 | 306 | Deletion of structure &1 for proxy object &2 failed | The short text describes the object sufficiently | |
74 | 307 | TADIR entry for &1 could not be written | The short text describes the object sufficiently | |
75 | 308 | Generation of DDIC structures failed | The short text describes the object sufficiently | |
76 | 309 | Generation of table failed; name is missing for &1 | The short text describes the object sufficiently | |
77 | 310 | Structure name for updating field table is missing | The short text describes the object sufficiently | |
78 | 311 | BOL field name &1 is already used within the structure | The short text describes the object sufficiently | |
79 | 312 | Root node &2 with BOL name &1 has an empty key structure | Space: object requires documentation | |
80 | 313 | Node is initial | The short text describes the object sufficiently | |
81 | 314 | Select a structure for the query input | The short text describes the object sufficiently | |
82 | 315 | Only one child should exist for table type | The short text describes the object sufficiently | |
83 | 316 | Do not select a node of type "element" for the query input | The short text describes the object sufficiently | |
84 | 317 | Could not find entry point for operation of type "&1" | The short text describes the object sufficiently | |
85 | 318 | No attribute exists in the structure &1 | The short text describes the object sufficiently | |
86 | 350 | Creation of target tree failed for proxy object &1 | The short text describes the object sufficiently | |
87 | 351 | Creation of target tree failed for component &1 | The short text describes the object sufficiently | |
88 | 352 | Error occurred when creating node for flat structure | The short text describes the object sufficiently | |
89 | 353 | Error occurred when creating root node for proxy object &1 | The short text describes the object sufficiently | |
90 | 354 | Error occurred when creating target tree | The short text describes the object sufficiently | |
91 | 355 | Error occurred when adding nodes to target tree | The short text describes the object sufficiently | |
92 | 356 | Error occurred when adding fields to a node (flat structure) | The short text describes the object sufficiently | |
93 | 400 | Source tree cannot be created as class &1 was not found | The short text describes the object sufficiently | |
94 | 401 | Source tree cannot be created as method &1 was not found for class &2 | The short text describes the object sufficiently | |
95 | 402 | Source tree cannot be created as method &1 has no input parameter | The short text describes the object sufficiently | |
96 | 403 | Source tree cannot be created as method &1 has no output parameter | The short text describes the object sufficiently | |
97 | 500 | Nothing found | The short text describes the object sufficiently | |
98 | 501 | System error when calling method &1 in proxy class &2 | Space: object requires documentation | |
99 | 600 | Transport request used: &1 | The short text describes the object sufficiently | |
100 | 601 | Table &1 cannot be included in transport request | The short text describes the object sufficiently | |
101 | 602 | No entries to be transported in table &1 | The short text describes the object sufficiently | |
102 | 603 | Authorization &1 is not assigned to user &2 for &3 | The short text describes the object sufficiently | |
103 | 604 | Object &1 &2 &3 could not be included in transport request | The short text describes the object sufficiently | |
104 | 605 | Object &1 &2 &3 of component &4 will not be transported | The short text describes the object sufficiently | |
105 | 606 | Local object &1 &2 &3 will not be transported | The short text describes the object sufficiently | |
106 | 700 | Pre-activation check failed; further processing stopped | The short text describes the object sufficiently | |
107 | 800 | No proxy created; check system proxy setting and appl. log with handle &1 | The short text describes the object sufficiently | |
108 | 801 | Content of local file must be provided as XSTRING | The short text describes the object sufficiently | |
109 | 802 | No proxy was created; it may already exist or a generic error occurred | The short text describes the object sufficiently | |
110 | 803 | The given URL is not usable; no proxies generated | The short text describes the object sufficiently | |
111 | 804 | Proxy for port type &1 already exists; no new proxy created | The short text describes the object sufficiently |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 600 |