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
⤷
⤷
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 | &1 &2 &3 &4 | The short text describes the object sufficiently | ||
| 2 | Operation &1 does not exist | The short text describes the object sufficiently | ||
| 3 | Generation of component &1 started | The short text describes the object sufficiently | ||
| 4 | Generation of component &1 completed | The short text describes the object sufficiently | ||
| 5 | Specify the component name | The short text describes the object sufficiently | ||
| 6 | Specify the prefix for business objects | The short text describes the object sufficiently | ||
| 7 | Select an existing Web service proxy or create a new one | The short text describes the object sufficiently | ||
| 8 | Select any operation | The short text describes the object sufficiently | ||
| 9 | Specify the application name | The short text describes the object sufficiently | ||
| 10 | Specify the target ID | The short text describes the object sufficiently | ||
| 11 | Specify the package for application | The short text describes the object sufficiently | ||
| 12 | Web Client application &1 generated | The short text describes the object sufficiently | ||
| 13 | Transport request is not set | The short text describes the object sufficiently | ||
| 14 | Proxy &1 generated | The short text describes the object sufficiently | ||
| 15 | System cannot generate a proxy; use transaction SPROXY instead | The short text describes the object sufficiently | ||
| 16 | Use SOAMANAGER to create a logical port for &1 | The short text describes the object sufficiently | ||
| 17 | Component &1 already exists | The short text describes the object sufficiently | ||
| 18 | Specify a valid URL to access a WSDL document | The short text describes the object sufficiently | ||
| 19 | Use the transaction SOAMANAGER to create a logical port | The short text describes the object sufficiently | ||
| 20 | Generation failed; it is not possible to consume &1 operation | The short text describes the object sufficiently | ||
| 21 | Not all fields required to create a new operation have been filled | The short text describes the object sufficiently | ||
| 22 | Component has to be generated again after a prefix change | The short text describes the object sufficiently | ||
| 23 | Component &1 could not be deleted | The short text describes the object sufficiently | ||
| 24 | Operation &1 could not be deleted | The short text describes the object sufficiently | ||
| 25 | Tree could not be deleted | The short text describes the object sufficiently | ||
| 26 | Component &1 could not be saved | The short text describes the object sufficiently | ||
| 27 | Another new operation exists that has not yet been saved | The short text describes the object sufficiently | ||
| 28 | Data entered is not unique; &1 appears more than once | The short text describes the object sufficiently | ||
| 29 | Read input: at least one field must be designated as a key field | The short text describes the object sufficiently | ||
| 30 | Read output: selected structure/table &1 must have the BO name filled | The short text describes the object sufficiently | ||
| 31 | Query &1 input: at least one field must be selected | The short text describes the object sufficiently | ||
| 32 | Query &1 output: at least one field must be designated as a key field | The short text describes the object sufficiently | ||
| 33 | Only one read operation is allowed per component | The short text describes the object sufficiently | ||
| 34 | Prefix must be unique; prefix &1 is already used | The short text describes the object sufficiently | ||
| 35 | Read output: selected table &1 must have at least one key field | The short text describes the object sufficiently | ||
| 36 | Component &1 already exists in IMG under Generic Interaction Layer/Object | The short text describes the object sufficiently | ||
| 37 | Component &1 could not be stored in general component table CRMC_GIL_COMP | Space: object requires documentation | ||
| 38 | Component must have one read operation | The short text describes the object sufficiently | ||
| 39 | You can only copy operations of type "Query" | The short text describes the object sufficiently | ||
| 40 | Number of key fields in read input is not the same as in query &1 output | The short text describes the object sufficiently | ||
| 41 | Field &1 is set as key field in query &2 output but not in read input | The short text describes the object sufficiently | ||
| 42 | Field &1 is set as key field in read input but not in query &2 output | The short text describes the object sufficiently | ||
| 43 | Messages for component &1: | The short text describes the object sufficiently | ||
| 44 | No errors found for component &1 | The short text describes the object sufficiently | ||
| 45 | Number of key fields in read input is not the same as in read output | The short text describes the object sufficiently | ||
| 46 | Field &1 is set as key field in read input but not in read output | The short text describes the object sufficiently | ||
| 47 | Field &1 is set as key field in read output but not in read input | The short text describes the object sufficiently | ||
| 48 | Operation with name &1 already exists in the component | The short text describes the object sufficiently | ||
| 49 | Operation cannot be renamed as it does not exist | The short text describes the object sufficiently | ||
| 50 | Only "Read" and "Query" are supported | The short text describes the object sufficiently | ||
| 51 | You are not allowed to change the prefix of an existing component | The short text describes the object sufficiently | ||
| 52 | Operation name must start with the component prefix | The short text describes the object sufficiently | ||
| 53 | Read output: exactly one structure must be designated as entry point | The short text describes the object sufficiently | ||
| 54 | Query output: exactly one structure must be designated as entry point | The short text describes the object sufficiently | ||
| 55 | Query output: parent of designated entry point must be a table | The short text describes the object sufficiently | ||
| 56 | Proxy class &1 is invalid | The short text describes the object sufficiently | ||
| 57 | Proxy method &1 is invalid | The short text describes the object sufficiently | ||
| 58 | Prefix for component &1 is empty; saving is not possible | The short text describes the object sufficiently | ||
| 59 | Function not supported; save first | The short text describes the object sufficiently | ||
| 60 | Unsaved changes exist; try to cancel and save before creating | The short text describes the object sufficiently | ||
| 61 | BO name must not be empty | The short text describes the object sufficiently | ||
| 62 | BOL field name must not be empty | The short text describes the object sufficiently | ||
| 63 | Save before making the next change | The short text describes the object sufficiently | ||
| 64 | Key fields in query output &1 must be inside a structure (not a table) | The short text describes the object sufficiently | ||
| 65 | Key fields in read output do not match the generated key structure | Space: object requires documentation | ||
| 66 | Key fields in query output &1 do not match the generated key structure | Space: object requires documentation | ||
| 67 | Creation of structure &1 failed | The short text describes the object sufficiently | ||
| 68 | Activation of structure &1 failed | The short text describes the object sufficiently | ||
| 69 | Error generating DDIC name &1 | The short text describes the object sufficiently | ||
| 70 | Field could not be added to structure &1 | The short text describes the object sufficiently | ||
| 71 | DDIC structure check failed | The short text describes the object sufficiently | ||
| 72 | Deletion of structure &1 failed | The short text describes the object sufficiently | ||
| 73 | Deletion of structure &1 for proxy object &2 failed | The short text describes the object sufficiently | ||
| 74 | TADIR entry for &1 could not be written | The short text describes the object sufficiently | ||
| 75 | Generation of DDIC structures failed | The short text describes the object sufficiently | ||
| 76 | Generation of table failed; name is missing for &1 | The short text describes the object sufficiently | ||
| 77 | Structure name for updating field table is missing | The short text describes the object sufficiently | ||
| 78 | BOL field name &1 is already used within the structure | The short text describes the object sufficiently | ||
| 79 | Root node &2 with BOL name &1 has an empty key structure | Space: object requires documentation | ||
| 80 | Node is initial | The short text describes the object sufficiently | ||
| 81 | Select a structure for the query input | The short text describes the object sufficiently | ||
| 82 | Only one child should exist for table type | The short text describes the object sufficiently | ||
| 83 | Do not select a node of type "element" for the query input | The short text describes the object sufficiently | ||
| 84 | Could not find entry point for operation of type "&1" | The short text describes the object sufficiently | ||
| 85 | No attribute exists in the structure &1 | The short text describes the object sufficiently | ||
| 86 | Creation of target tree failed for proxy object &1 | The short text describes the object sufficiently | ||
| 87 | Creation of target tree failed for component &1 | The short text describes the object sufficiently | ||
| 88 | Error occurred when creating node for flat structure | The short text describes the object sufficiently | ||
| 89 | Error occurred when creating root node for proxy object &1 | The short text describes the object sufficiently | ||
| 90 | Error occurred when creating target tree | The short text describes the object sufficiently | ||
| 91 | Error occurred when adding nodes to target tree | The short text describes the object sufficiently | ||
| 92 | Error occurred when adding fields to a node (flat structure) | The short text describes the object sufficiently | ||
| 93 | Source tree cannot be created as class &1 was not found | The short text describes the object sufficiently | ||
| 94 | Source tree cannot be created as method &1 was not found for class &2 | The short text describes the object sufficiently | ||
| 95 | Source tree cannot be created as method &1 has no input parameter | The short text describes the object sufficiently | ||
| 96 | Source tree cannot be created as method &1 has no output parameter | The short text describes the object sufficiently | ||
| 97 | Nothing found | The short text describes the object sufficiently | ||
| 98 | System error when calling method &1 in proxy class &2 | Space: object requires documentation | ||
| 99 | Transport request used: &1 | The short text describes the object sufficiently | ||
| 100 | Table &1 cannot be included in transport request | The short text describes the object sufficiently | ||
| 101 | No entries to be transported in table &1 | The short text describes the object sufficiently | ||
| 102 | Authorization &1 is not assigned to user &2 for &3 | The short text describes the object sufficiently | ||
| 103 | Object &1 &2 &3 could not be included in transport request | The short text describes the object sufficiently | ||
| 104 | Object &1 &2 &3 of component &4 will not be transported | The short text describes the object sufficiently | ||
| 105 | Local object &1 &2 &3 will not be transported | The short text describes the object sufficiently | ||
| 106 | Pre-activation check failed; further processing stopped | The short text describes the object sufficiently | ||
| 107 | No proxy created; check system proxy setting and appl. log with handle &1 | The short text describes the object sufficiently | ||
| 108 | Content of local file must be provided as XSTRING | The short text describes the object sufficiently | ||
| 109 | No proxy was created; it may already exist or a generic error occurred | The short text describes the object sufficiently | ||
| 110 | The given URL is not usable; no proxies generated | The short text describes the object sufficiently | ||
| 111 | 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 |