SWF_HTTP - Webservices im Workflow: Server-Funktionalit�t
The following messages are stored in message class SWF_HTTP: Webservices im Workflow: Server-Funktionalit�t.
It is part of development package SWF_HTTP in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Incorporation of External Services with HTTP into a Workflow".
It is part of development package SWF_HTTP in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Incorporation of External Services with HTTP into a Workflow".
Message Nr ▲ | Message Text |
|---|---|
| 000 | The launch handler was called with an incomplete parameter list |
| 001 | No RFC destination can be found for logical system &1 |
| 002 | Communication error in RFC in the workflow system |
| 003 | System error in RFC in the workflow system |
| 004 | Work item could not be selected by user &1 |
| 005 | Work item could not be replaced |
| 006 | Work item could not be completed |
| 007 | Error when reading the work item container |
| 008 | Test successful |
| 009 | Invalid execution GUID. Work item could not be completed. |
| 010 | The ABAP type &1 is not supported by the execution server |
| 011 | ABAP structure types are not supported by the execution server |
| 012 | ABAP table types are not supported by the execution server |
| 013 | ABAP reference types are not supported by the execution server |
| 014 | Invalid ABAP data type |
| 015 | The XML procedure type &1 is not supported by the execution server |
| 016 | Execution GUID could not be set |
| 017 | Callback URL could not be determined |
| 018 | Error when writing the instance coupling (&1.&2, WI ID &3) |
| 020 | Message part &1 does not exist |
| 021 | Export message of service could not be processed |
| 022 | Message does not contain mandatory parameter &1 |
| 023 | Standard value for parameter &1 could not be set |
| 024 | Mandatory parameter &1 could not be set |
| 025 | Container does not contain mandatory import parameter '&1' |
| 030 | Service URL too long for redirect (&1 characters, but max. &2 characters) |
| 031 | Element '&1' does not exist in the work item container |
| 032 | Error in the value assignment in message part '&1' |
| 033 | Error when reading the Basis URL of the callback dialogs |
| 034 | Path information of the callback dialogs not maintained |
| 040 | Error when generating the HTTP client |
| 041 | Error when sending the HTTP request |
| 042 | Error when receiving the HTTP response |
| 043 | HTTP error (response code &1): &2 |
| 060 | HTTP error when executing the callback |
| 061 | Callback URL incomplete (missing parameter) |
| 062 | Parameter "&1" cannot be converted to a simple data type |
| 063 | Error when converting parameter "&1" to XML format |
| 064 | Error when reading the attribute for task '&1' |
| 065 | Task &1 does not refer to a service |
| 066 | No suitable launch handler entry maintained |
| 067 | System is a handler server: No remote handler entry available! |
| 068 | No launch handler entries maintained in the system |
| 069 | Error when reading the work item header for work item '&1' |
| 070 | No remote launch handler entry maintained in the system |
| 071 | No local launch handler entry maintained in the system |
| 072 | Launch handler URL(s) successfully generated |
| 073 | Work item '&1' closed successfully |
| 074 | Work item '&1' was not closed and remains in your Inbox |
| 100 | WSDL document does not contain any suitable service definitions |
| 101 | Attribute '&1' in WSDL element <&2> refers to an external WSDL document |
| 102 | Reference '&1' in WSDL element <&2> is invalid |
| 103 | SOAP binding is not yet supported |
| 104 | Invalid Binding |
| 105 | Asynchronous property was set |
| 106 | Callback property was set |
| 107 | Binding element <&1> does not contain valid elements |
| 108 | Complex types are not supported (element reference '&1') |
| 109 | Self-defined types are not supported (type reference '&1') |
| 110 | XML schema type '&1' is not supported |
| 111 | Conversion error in the container serialization |
| 112 | Conversion error when writing message part '&1' |
| 113 | Error when converting from XML to ABAP (message part '&1') |
| 114 | Arithmetic Overflow (Message Part '&1') |
| 115 | Error in the service interface |
| 116 | Error when generating output message from HTTP response of service |
| 117 | Error when generating the output message from the service callback |
| 118 | Error when generating the input message from the container |
| 119 | Error when setting container element '&1' |
| 120 | Interface definition '&1' not available |
| 121 | There is no binding for interface definition '&1' |
| 122 | There is no port for interface definition '&1' |
| 123 | Error when loading the service definitions |
| 124 | Binding definition '&1' not available |
| 125 | Error when starting the service |
| 126 | Error in callback processing |
| 127 | Error when opening file |
| 128 | XSLT error when importing the WSDL file |
| 129 | Error when opening the file selection dialog |
| 130 | No interface definition with the name '&1' available |
| 131 | The MIME type '&1' is not supported |
| 132 | The element '&1' is not allowed or is not supported |
| 133 | Service definition deleted |
| 134 | Temporary error when starting service |
| 135 | Temporary error when processing callback |
| 200 | Import of WebFlow service definitions was canceled |
| 201 | WebFlow service definitions successfully imported |
| 202 | Interface already available |
| 203 | Corresponding interface is already available |
| 204 | Definition can be imported |
| 205 | WSDL document does not contain any definitions that can be imported |
| 206 | Load port definition from the database |
| 207 | Port definition saved successfully |
| 208 | No definitions selected |
| 209 | Definition is not in change mode |
| 210 | Error when saving the interface definition |
| 211 | Error when saving the binding definition |
| 212 | Error when saving the port definition |
| 213 | Interface '&1' has been changed since it was last saved |
| 214 | Binding '&1' has been changed since it was last saved |
| 215 | Port '&1' has been changed since it was last saved |
| 216 | Error when reading the interface definition |
| 217 | Error when reading the binding definition |
| 218 | Error when reading the port definition |
| 219 | Error when importing the WebFlow service definitions |
| 220 | No service definitions found |
| 300 | The separate logical system could not be determined |
| 301 | The logical system '&1' is not maintained as the client system |
| 302 | Service definition '&1' could not be found |
| 303 | Interface definition could not be found |
| 304 | Error when generating the task generators |
| 305 | Error when writing the task service relation |
| 306 | Error when generating the task |
| 307 | Task generation from XML service cache in Plugin not possible |
| 308 | RFC error in the task generation |
| 309 | Error in the task generation |
| 310 | Error when writing the task service relation |
| 311 | Error when generating the task container |
| 312 | Error when writing the task abbreviation and task name |
| 313 | Error when writing the work item text |
| 314 | '&1' is an invalid XML type |
| 315 | Error in the Task Serialization |
| 316 | Choose a logical system |
| 317 | Task successfully generated |
| 318 | Port '&1' does not exist |
| 319 | Choose a service definition |