SAP ABAP Message Class SWF_HTTP (Web Services in the Workflow: Server Functions)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-BMT-WFM (Application Component) SAP Business Workflow
⤷ SWF_HTTP (Package) Incorporation of External Services with HTTP into a Workflow
⤷ BC-BMT-WFM (Application Component) SAP Business Workflow
⤷ SWF_HTTP (Package) Incorporation of External Services with HTTP into a Workflow
Attributes
Message class | SWF_HTTP | |
Short Description | Web Services in the Workflow: Server Functions | |
Changed On | 20110908 | |
Last Changed At | 153359 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | The launch handler was called with an incomplete parameter list | Space: object requires documentation | |
2 | 001 | No RFC destination can be found for logical system &1 | Space: object requires documentation | |
3 | 002 | Communication error in RFC in the workflow system | Space: object requires documentation | |
4 | 003 | System error in RFC in the workflow system | Space: object requires documentation | |
5 | 004 | Work item could not be selected by user &1 | Space: object requires documentation | |
6 | 005 | Work item could not be replaced | Space: object requires documentation | |
7 | 006 | Work item could not be completed | Space: object requires documentation | |
8 | 007 | Error when reading the work item container | Space: object requires documentation | |
9 | 008 | Test successful | Space: object requires documentation | |
10 | 009 | Invalid execution GUID. Work item could not be completed. | The short text describes the object sufficiently | |
11 | 010 | The ABAP type &1 is not supported by the execution server | Space: object requires documentation | |
12 | 011 | ABAP structure types are not supported by the execution server | Space: object requires documentation | |
13 | 012 | ABAP table types are not supported by the execution server | Space: object requires documentation | |
14 | 013 | ABAP reference types are not supported by the execution server | Space: object requires documentation | |
15 | 014 | Invalid ABAP data type | Space: object requires documentation | |
16 | 015 | The XML procedure type &1 is not supported by the execution server | Space: object requires documentation | |
17 | 016 | Execution GUID could not be set | The short text describes the object sufficiently | |
18 | 017 | Callback URL could not be determined | The short text describes the object sufficiently | |
19 | 018 | Error when writing the instance coupling (&1.&2, WI ID &3) | The short text describes the object sufficiently | |
20 | 020 | Message part &1 not available | Space: object requires documentation | |
21 | 021 | Export message of service could not be processed | Space: object requires documentation | |
22 | 022 | Message does not contain obligatory parameter &1 | Space: object requires documentation | |
23 | 023 | Standard value for parameter &1 could not be set | Space: object requires documentation | |
24 | 024 | Obligatory parameter &1 could not be set | Space: object requires documentation | |
25 | 025 | Container does not contain obligatory import parameter '&1' | Space: object requires documentation | |
26 | 030 | Service URL too long for redirect (&1 characters, but max. &2 characters) | Space: object requires documentation | |
27 | 031 | Element '&1' is not available in the work item container | Space: object requires documentation | |
28 | 032 | Error in the value assignment in message part '&1' | Space: object requires documentation | |
29 | 033 | Error when reading the Basis URL of the callback dialogs | Space: object requires documentation | |
30 | 034 | Path information of the callback dialogs not maintained | Space: object requires documentation | |
31 | 040 | Error when generating the HTTP client | Space: object requires documentation | |
32 | 041 | Error when sending the HTTP request | Space: object requires documentation | |
33 | 042 | Error when receiving the HTTP response | Space: object requires documentation | |
34 | 043 | HTTP error (response code &1): &2 | Space: object requires documentation | |
35 | 060 | HTTP error when executing the callback | Space: object requires documentation | |
36 | 061 | Callback URL incomplete (missing parameter) | Space: object requires documentation | |
37 | 062 | Parameter "&1" cannot be converted to a simple data type | Space: object requires documentation | |
38 | 063 | Error when converting parameter "&1" to XML format | Space: object requires documentation | |
39 | 064 | Error when reading the attribute for task '&1' | Space: object requires documentation | |
40 | 065 | Task &1 does not refer to a service | Space: object requires documentation | |
41 | 066 | No suitable launch handler entry maintained | Space: object requires documentation | |
42 | 067 | System is a handler server: No remote handler entry available! | Space: object requires documentation | |
43 | 068 | No launch handler entries maintained in the system | Space: object requires documentation | |
44 | 069 | Error when reading the work item header for work item '&1' | Space: object requires documentation | |
45 | 070 | No remote launch handler entry maintained in the system | Space: object requires documentation | |
46 | 071 | No local launch handler entry maintained in the system | Space: object requires documentation | |
47 | 072 | Launch handler URL(s) successfully generated | Space: object requires documentation | |
48 | 073 | Work item '&1' closed successfully | Space: object requires documentation | |
49 | 074 | Work item '&1' was not closed and remains in your Inbox | Space: object requires documentation | |
50 | 100 | WSDL document does not contain any suitable service definitions | Space: object requires documentation | |
51 | 101 | Attribute '&1' in WSDL element <&2> refers to an external WSDL document | Space: object requires documentation | |
52 | 102 | Reference '&1' in WSDL element <&2> is invalid | Space: object requires documentation | |
53 | 103 | SOAP binding is not yet supported | Space: object requires documentation | |
54 | 104 | Invalid Binding | Space: object requires documentation | |
55 | 105 | Asynchronous property was set | Space: object requires documentation | |
56 | 106 | Callback property was set | Space: object requires documentation | |
57 | 107 | Binding element <&1> does not contain valid elements | Space: object requires documentation | |
58 | 108 | Complex types are not supported (element reference '&1') | Space: object requires documentation | |
59 | 109 | Self-defined types are not supported (type reference '&1') | Space: object requires documentation | |
60 | 110 | XML schema type '&1' is not supported | Space: object requires documentation | |
61 | 111 | Conversion error in the container serialization | Space: object requires documentation | |
62 | 112 | Conversion error when writing message part '&1' | Space: object requires documentation | |
63 | 113 | Error when converting from XML to ABAP (message part '&1') | Space: object requires documentation | |
64 | 114 | Arithmetic Overflow (Message Part '&1') | Space: object requires documentation | |
65 | 115 | Error in the service interface | Space: object requires documentation | |
66 | 116 | Error when generating output message from HTTP response of service | Space: object requires documentation | |
67 | 117 | Error when generating the output message from the service callback | Space: object requires documentation | |
68 | 118 | Error when generating the input message from the container | Space: object requires documentation | |
69 | 119 | Error when setting container element '&1' | Space: object requires documentation | |
70 | 120 | Interface definition '&1' not available | Space: object requires documentation | |
71 | 121 | There is no binding for interface definition '&1' | Space: object requires documentation | |
72 | 122 | There is no port for interface definition '&1' | Space: object requires documentation | |
73 | 123 | Error when loading the service definitions | Space: object requires documentation | |
74 | 124 | Binding definition '&1' not available | Space: object requires documentation | |
75 | 125 | Error when starting the service | Space: object requires documentation | |
76 | 126 | Error in callback processing | Space: object requires documentation | |
77 | 127 | Error when opening file | Space: object requires documentation | |
78 | 128 | XSLT error when importing the WSDL file | Space: object requires documentation | |
79 | 129 | Error when opening the file selection dialog | Space: object requires documentation | |
80 | 130 | No interface definition with the name '&1' available | Space: object requires documentation | |
81 | 131 | The MIME type '&1' is not supported | Space: object requires documentation | |
82 | 132 | The element '&1' is not allowed or is not supported | Space: object requires documentation | |
83 | 133 | Service definition deleted | The short text describes the object sufficiently | |
84 | 134 | Temporary error when starting service | The short text describes the object sufficiently | |
85 | 135 | Temporary error when processing callback | The short text describes the object sufficiently | |
86 | 200 | Import of WebFlow service definitions was canceled | Space: object requires documentation | |
87 | 201 | WebFlow service definitions successfully imported | Space: object requires documentation | |
88 | 202 | Interface already available | Space: object requires documentation | |
89 | 203 | Corresponding interface is already available | Space: object requires documentation | |
90 | 204 | Definition can be imported | Space: object requires documentation | |
91 | 205 | WSDL document does not contain any definitions that can be imported | Space: object requires documentation | |
92 | 206 | Load port definition from the database | Space: object requires documentation | |
93 | 207 | Port definition saved successfully | Space: object requires documentation | |
94 | 208 | No definitions selected | Space: object requires documentation | |
95 | 209 | Definition is not in change mode | Space: object requires documentation | |
96 | 210 | Error when saving the interface definition | Space: object requires documentation | |
97 | 211 | Error when saving the binding definition | Space: object requires documentation | |
98 | 212 | Error when saving the port definition | Space: object requires documentation | |
99 | 213 | Interface '&1' has been changed since it was last saved | Space: object requires documentation | |
100 | 214 | Binding '&1' has been changed since it was last saved | Space: object requires documentation | |
101 | 215 | Port '&1' has been changed since it was last saved | Space: object requires documentation | |
102 | 216 | Error when reading the interface definition | Space: object requires documentation | |
103 | 217 | Error when reading the binding definition | Space: object requires documentation | |
104 | 218 | Error when reading the port definition | Space: object requires documentation | |
105 | 219 | Error when importing the WebFlow service definitions | Space: object requires documentation | |
106 | 220 | No service definitions found | Space: object requires documentation | |
107 | 300 | The separate logical system could not be determined | Space: object requires documentation | |
108 | 301 | The logical system '&1' is not maintained as the client system | Space: object requires documentation | |
109 | 302 | Service definition '&1' could not be found | Space: object requires documentation | |
110 | 303 | Interface definition could not be found | Space: object requires documentation | |
111 | 304 | Error when generating the task generators | Space: object requires documentation | |
112 | 305 | Error when writing the task service relation | Space: object requires documentation | |
113 | 306 | Error when generating the task | Space: object requires documentation | |
114 | 307 | Task generation from XML service cache in Plugin not possible | Space: object requires documentation | |
115 | 308 | RFC error in the task generation | Space: object requires documentation | |
116 | 309 | Error in the task generation | Space: object requires documentation | |
117 | 310 | Error when writing the task service relation | Space: object requires documentation | |
118 | 311 | Error when generating the task container | Space: object requires documentation | |
119 | 312 | Error when writing the task abbreviation and task name | Space: object requires documentation | |
120 | 313 | Error when writing the work item text | Space: object requires documentation | |
121 | 314 | '&1' is an invalid XML type | Space: object requires documentation | |
122 | 315 | Error in the Task Serialization | Space: object requires documentation | |
123 | 316 | Choose a logical system | Space: object requires documentation | |
124 | 317 | Task successfully generated | Space: object requires documentation | |
125 | 318 | Port '&1' not available | Space: object requires documentation | |
126 | 319 | Choose a service definition | Space: object requires documentation |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 620 |