SAP ABAP Message Class SWF_XI_ADAPTER (XI BPM: Messages)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-XI-IS-BPE (Application Component) Business Process Engine
⤷ SWF_XI_ADAPTER (Package) Workflow Adapter for XI
⤷ BC-XI-IS-BPE (Application Component) Business Process Engine
⤷ SWF_XI_ADAPTER (Package) Workflow Adapter for XI
Attributes
Message class | SWF_XI_ADAPTER | |
Short Description | XI BPM: Messages | |
Changed On | 20110908 | |
Last Changed At | 153410 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 001 | Cache entry for directory process '&1' does not exist | The short text describes the object sufficiently | |
2 | 002 | Cache entry for directory process for '&1' is already up-to-date | The short text describes the object sufficiently | |
3 | 008 | No Directory process found for party '&1' and service '&2' | The short text describes the object sufficiently | |
4 | 010 | Error (&1) when importing process &2 (cache entry &3) | The short text describes the object sufficiently | |
5 | 015 | No proxy exists for message ID & | The short text describes the object sufficiently | |
6 | 050 | --------- Runtime ------------------------------------------------------ | The short text describes the object sufficiently | |
7 | 051 | No receivers specified | The short text describes the object sufficiently | |
8 | 052 | No reference message specified when sending a response | The short text describes the object sufficiently | |
9 | 053 | An empty container element was specified when sending | The short text describes the object sufficiently | |
10 | 054 | No valid XML message specified | The short text describes the object sufficiently | |
11 | 055 | Component &1 has reported an error | The short text describes the object sufficiently | |
12 | 056 | Only synchronous update mode is supported | The short text describes the object sufficiently | |
13 | 057 | Process instance &1 has unexpected status &2 | The short text describes the object sufficiently | |
14 | 058 | Fault message &1&2 from namespace &3&4 received | The short text describes the object sufficiently | |
15 | 059 | An internal error has occurred | The short text describes the object sufficiently | |
16 | 081 | No exception defined for fault message &1 &2 | The short text describes the object sufficiently | |
17 | 082 | No exception defined for negative acknowledgment &1 | The short text describes the object sufficiently | |
18 | 083 | No handler defined for this system exception | The short text describes the object sufficiently | |
19 | 100 | --------- Administration ------------------------------------------------ | The short text describes the object sufficiently | |
20 | 101 | &1 of &2 selected XI objects deleted | Space: object requires documentation | |
21 | 110 | --------- Payload Editor ------------------------------------------------ | The short text describes the object sufficiently | |
22 | 111 | Error determining SLD name of Integration Server | The short text describes the object sufficiently | |
23 | 112 | Error accessing parameter &1 in exchange profile | The short text describes the object sufficiently | |
24 | 113 | Error accessing the configuration of safe connections | The short text describes the object sufficiently | |
25 | 114 | Connection configuration in exchange profile contains errors | The short text describes the object sufficiently | |
26 | 115 | Specified activity is invalid | The short text describes the object sufficiently | |
27 | 116 | No change authorization for service &1, interface &2 in namespace &3 | The short text describes the object sufficiently | |
28 | 117 | You do not have authorization to change XML messages in processes | The short text describes the object sufficiently | |
29 | 200 | --------- CUSTOMIZING ----------------------------------------------- | The short text describes the object sufficiently | |
30 | 201 | User & does not have sufficient authorization to execute autocustomizing | The short text describes the object sufficiently | |
31 | 202 | BPM - Autocustomizing executed successfully | The short text describes the object sufficiently | |
32 | 203 | Error in BPM - Autocustomizing | The short text describes the object sufficiently | |
33 | 250 | --------- MONITORING ----------------------------------------------- | The short text describes the object sufficiently | |
34 | 251 | Message &1 held at process &2 but not yet processed | The short text describes the object sufficiently | |
35 | 300 | Message with ID &1 not found | The short text describes the object sufficiently | |
36 | 301 | Message with ID &1 has delivery status &2 | The short text describes the object sufficiently | |
37 | 400 | Setting for process type &1 already exists | Space: object requires documentation | |
38 | 401 | Setting for process type &1 does not exist. Cannot delete. | Space: object requires documentation | |
39 | 402 | Setting for process type &1 does not exist. Cannot change. | Space: object requires documentation | |
40 | 403 | Action &1 is not currently supported | Space: object requires documentation | |
41 | 404 | Mode for process type &1 has unexpected values (DB &2; buffer &3) | Space: object requires documentation | |
42 | 405 | Inbound queue &1 (SMQ2) for process type &2 is not stopped | Space: object requires documentation | |
43 | 406 | An LUW is being processed in inbound queue &1 (SMQ2) for process type &2 | Space: object requires documentation | |
44 | 407 | Inbound queue &1 (SMQ2) for process type &2 has LUW with errors | Space: object requires documentation | |
45 | 410 | Maintenance only permitted on Integration Server (client &1) | The short text describes the object sufficiently | |
46 | 411 | Process type &1: Combination of delivery mode and queue handling invalid | The short text describes the object sufficiently | |
47 | 412 | Canceled by user | The short text describes the object sufficiently | |
48 | 413 | Last change for process type &1 not complete; try again later | The short text describes the object sufficiently | |
49 | 415 | Processing canceled by user | The short text describes the object sufficiently | |
50 | 416 | Enter the queues or confirm that &1 only receives EO messages | The short text describes the object sufficiently | |
51 | 417 | Process type &1 does not exist | The short text describes the object sufficiently | |
52 | 418 | Prozess type &1: Queue assignment does not match setting in Repository | Space: object requires documentation | |
53 | 419 | Queue &1 is not unique; check your entries are correct | Space: object requires documentation | |
54 | 420 | Queue &1 is not registered; check your entries are correct | Space: object requires documentation | |
55 | 421 | Could not persist queue name | The short text describes the object sufficiently | |
56 | 500 | Select the lines to be deleted | The short text describes the object sufficiently | |
57 | 600 | No process found for party &1 and service &2 | The short text describes the object sufficiently | |
58 | 601 | No process found for service &1 | The short text describes the object sufficiently | |
59 | 602 | No changes made to process definition &1 | The short text describes the object sufficiently | |
60 | 603 | Version &1 of process definition &2 created and activated | The short text describes the object sufficiently | |
61 | 604 | Could not activate process &1 |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 640 |