SAP ABAP Message Class SPI21 (Metadata Maintenance: Process Monitoring)
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-SRV-PMI (Application Component) Process Monitoring Infrastructure
⤷ SPI21 (Package) Central Meta Data (Maintenance)
⤷ BC-SRV-PMI (Application Component) Process Monitoring Infrastructure
⤷ SPI21 (Package) Central Meta Data (Maintenance)
Attributes
Message class | SPI21 | |
Short Description | Metadata Maintenance: Process Monitoring | |
Changed On | 20110908 | |
Last Changed At | 153140 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | & | The short text describes the object sufficiently | |
2 | 007 | Release of process definition canceled | Space: object requires documentation | |
3 | 008 | Process definition was released | Space: object requires documentation | |
4 | 009 | Change not possible; Monitoring is activated | Space: object requires documentation | |
5 | 010 | Save not necessary. Process definition was not changed. | Space: object requires documentation | |
6 | 011 | Data saved | Space: object requires documentation | |
7 | 012 | Process definition was deleted | Space: object requires documentation | |
8 | 013 | Processing Cancelled | The short text describes the object sufficiently | |
9 | 014 | Process &1 successfully copied | The short text describes the object sufficiently | |
10 | 015 | Process &1 was not copied | The short text describes the object sufficiently | |
11 | 016 | Could not find any inconsistencies | Space: object requires documentation | |
12 | 017 | Check found errors (see log) | Space: object requires documentation | |
13 | 018 | Warnings occurred during the check (see log) | The short text describes the object sufficiently | |
14 | 019 | Process definition is not released | The short text describes the object sufficiently | |
15 | 020 | Select a valid process definition | Space: object requires documentation | |
16 | 021 | Select only one process step | Space: object requires documentation | |
17 | 022 | Select a valid process step | Space: object requires documentation | |
18 | 023 | Select a metric | The short text describes the object sufficiently | |
19 | 024 | The metric name already exists | The short text describes the object sufficiently | |
20 | 025 | Enter a description for the process definition | The short text describes the object sufficiently | |
21 | 026 | Select an interface | The short text describes the object sufficiently | |
22 | 027 | Interface name already exists | The short text describes the object sufficiently | |
23 | 028 | Field name already exists | The short text describes the object sufficiently | |
24 | 031 | Step cannot have a relationship with itself | Space: object requires documentation | |
25 | 032 | Select the data fields for the relationship | The short text describes the object sufficiently | |
26 | 033 | Field &1 does not belong to step <&2> | The short text describes the object sufficiently | |
27 | 034 | A relationship with these fields already exists | The short text describes the object sufficiently | |
28 | 035 | Field names were deleted from the relationship | The short text describes the object sufficiently | |
29 | 036 | Relation &2 for field &1 is not allowed in this relationship | Space: object requires documentation | |
30 | 037 | A relationship between these steps already exists | The short text describes the object sufficiently | |
31 | 038 | Specify valid steps for the relationship | The short text describes the object sufficiently | |
32 | 041 | Entry deleted | Space: object requires documentation | |
33 | 042 | The entry could not be deleted | The short text describes the object sufficiently | |
34 | 051 | Process definition was written to transport request &1 | The short text describes the object sufficiently | |
35 | 052 | Process definition cannot be completely transported | The short text describes the object sufficiently | |
36 | 061 | No transitions have been defined | The short text describes the object sufficiently | |
37 | 062 | Transitions do not define a linear chain | Space: object requires documentation | |
38 | 071 | The metric type does not exist | The short text describes the object sufficiently | |
39 | 072 | Select two different steps | The short text describes the object sufficiently | |
40 | 073 | Function not possible for step <&1> | The short text describes the object sufficiently | |
41 | 100 | Local change. Definition not transported automatically. | The short text describes the object sufficiently | |
42 | 110 | Error when process variant processed | The short text describes the object sufficiently | |
43 | 112 | Process variant deleted | The short text describes the object sufficiently | |
44 | 114 | Process variant &1 copied successfully | The short text describes the object sufficiently | |
45 | 115 | Process variant &1 not copied | The short text describes the object sufficiently | |
46 | 116 | Could not create default process variant | Space: object requires documentation | |
47 | 120 | Select a valid process variant | The short text describes the object sufficiently | |
48 | 151 | Only values lesser than or equal to &1 permitted for monitoring level | Space: object requires documentation | |
49 | 200 | Process <&1> is consistent | Space: object requires documentation | |
50 | 201 | Text description for process <&1> is missing | Space: object requires documentation | |
51 | 202 | Instance display for process <&1> is missing | The short text describes the object sufficiently | |
52 | 203 | Instance description for process <&1> is missing | The short text describes the object sufficiently | |
53 | 205 | Process <&1> has no process steps | The short text describes the object sufficiently | |
54 | 206 | Process <&1> has no transitions between process steps | The short text describes the object sufficiently | |
55 | 207 | Process <&1> has no relations between process steps | The short text describes the object sufficiently | |
56 | 208 | Transitions of process <&1> form a linear chain | The short text describes the object sufficiently | |
57 | 209 | Transitions of process <&1> do not form a linear chain | The short text describes the object sufficiently | |
58 | 210 | Instance description: <&1> does not match the chosen display | Space: object requires documentation | |
59 | 211 | No usage of the replacement variable <&1> in instance description | Space: object requires documentation | |
60 | 212 | Missing definition for replacement variable <&1> | Space: object requires documentation | |
61 | 215 | Step <&1> is consistent | Space: object requires documentation | |
62 | 216 | Signature for step <&1> is missing | Space: object requires documentation | |
63 | 217 | Invalid signature specified for step <&1> | Space: object requires documentation | |
64 | 220 | Step <&1> has no relations but it is not a system event | The short text describes the object sufficiently | |
65 | 221 | Incomplete definition of relations | Space: object requires documentation | |
66 | 222 | Incomplete paths in definition of transitions, step <&1> | The short text describes the object sufficiently | |
67 | 223 | Missing start steps while defining transitions | The short text describes the object sufficiently | |
68 | 225 | Signature <&1> is consistent | Space: object requires documentation | |
69 | 226 | No agent specified for signature <&1> | Space: object requires documentation | |
70 | 227 | Invalid agent specified for signature <&1> | Space: object requires documentation | |
71 | 228 | Text description for step <&1> is missing | Space: object requires documentation | |
72 | 229 | No payload fields or conditions exist for signature <&1> | The short text describes the object sufficiently | |
73 | 230 | Payload field <&1> is consistent | Space: object requires documentation | |
74 | 231 | Text description for payload field <&1> is missing | Space: object requires documentation | |
75 | 232 | Payload field <&1> for signature <&2> does not exist in agent <&3> | The short text describes the object sufficiently | |
76 | 233 | Complete all fields | The short text describes the object sufficiently | |
77 | 234 | No payload fields have been selected for signature <&1> | The short text describes the object sufficiently | |
78 | 235 | Field condition &3 for <&1> in <&2> is consistent | Space: object requires documentation | |
79 | 236 | Condition field <&1> for signature <&2> does not exist in agent <&3> | The short text describes the object sufficiently | |
80 | 240 | Step rule <&1> is consistent | Space: object requires documentation | |
81 | 241 | 1st step <&2> of rule <&1> does not exist in the process <&3> | Space: object requires documentation | |
82 | 242 | 2nd step <&2> of rule <&1> does not exist in process <&3> | Space: object requires documentation | |
83 | 243 | Step rule <&1> has no relations | The short text describes the object sufficiently | |
84 | 245 | Field relation <&1>~<&2> in rule <&3> is consistent | Space: object requires documentation | |
85 | 246 | Relation <&1>: 1st field <&2> does not exist in 1st step <&3> | The short text describes the object sufficiently | |
86 | 247 | Relation <&1>: 2nd field <&2> does not exist in 2nd step <&3> | The short text describes the object sufficiently | |
87 | 248 | Relation <&1>: Invalid field comparison | The short text describes the object sufficiently | |
88 | 249 | Relation <&1> cannot be assigned to a relation rule | The short text describes the object sufficiently | |
89 | 250 | Technical relation of field <&1> in rule <&2> is consistent | Space: object requires documentation | |
90 | 251 | Technical relation <&1>: invalid field <&2> | The short text describes the object sufficiently | |
91 | 252 | Unable to determine technical field names | The short text describes the object sufficiently | |
92 | 253 | Technical relation <&1>: Invalid field comparison | The short text describes the object sufficiently | |
93 | 255 | Transition <&1> is consistent | Space: object requires documentation | |
94 | 256 | Transition <&1>: 1st step <&2> does not exist in process <&3> | The short text describes the object sufficiently | |
95 | 257 | Transition <&1>: 2nd step <&2> does not exist in process <&3> | The short text describes the object sufficiently | |
96 | 260 | RFC destination for step <&1> is consistent | The short text describes the object sufficiently | |
97 | 261 | URL of the ITS for the RFC destination for step <&1> is missing | The short text describes the object sufficiently | |
98 | 262 | Local system for the RFC destination for step <&1> is missing | Space: object requires documentation | |
99 | 263 | No RFC destination specified for step <&1> | The short text describes the object sufficiently | |
100 | 264 | RFC destination <&1> for step <&2> has errors (&3) | The short text describes the object sufficiently | |
101 | 265 | Instance attribute <&1> is consistent | The short text describes the object sufficiently | |
102 | 266 | No tool maintained for symbol '&1' | The short text describes the object sufficiently | |
103 | 267 | No attribute entered for symbol '&1' | The short text describes the object sufficiently | |
104 | 268 | Attribute <&1> is missing in tool <&2> of process instance <&3> | The short text describes the object sufficiently | |
105 | 269 | Attribute <&1> is missing in tool <&2> of process step instance <&3> | The short text describes the object sufficiently | |
106 | 270 | An invalid process step instance <&2> has been entered for symbol <&1> | The short text describes the object sufficiently | |
107 | 271 | RFC destination <&1> is not available | The short text describes the object sufficiently | |
108 | 272 | No agent specified in RFC destination for step <&1> | The short text describes the object sufficiently | |
109 | 273 | "Local Data" not specified for RFC destination of step <&1> | The short text describes the object sufficiently | |
110 | 280 | Step <&3> does not have any relationships in variant &1, level &2 | The short text describes the object sufficiently | |
111 | 281 | Incomplete definition of relationships in variant &1, level &2 | The short text describes the object sufficiently | |
112 | 282 | Incomplete paths in definition of transitions in variant &1, level &2 | The short text describes the object sufficiently | |
113 | 283 | Missing initial steps in variant &1, level &2 | The short text describes the object sufficiently | |
114 | 284 | Step <&3> has no payload in variant &1, level &2 | The short text describes the object sufficiently | |
115 | 285 | Step <&3> in variant &1, level &2 has payload with higher level | The short text describes the object sufficiently | |
116 | 290 | Variant <&1>, level <&2> is consistent | The short text describes the object sufficiently | |
117 | 300 | Exception when loading steps of process <&1> | The short text describes the object sufficiently | |
118 | 301 | Authorization error when loading steps of process <&1> | The short text describes the object sufficiently | |
119 | 302 | Exception when loading transitions of process <&1> | The short text describes the object sufficiently | |
120 | 303 | Authorization error when loading transitions of process <&1> | The short text describes the object sufficiently | |
121 | 304 | Exception when loading relations of process <&1> | The short text describes the object sufficiently | |
122 | 305 | Authorization error when loading relations of process <&1> | The short text describes the object sufficiently | |
123 | 306 | Authorization error when loading the agent <&1> | The short text describes the object sufficiently | |
124 | 307 | Exception while loading process <&1> | The short text describes the object sufficiently | |
125 | 308 | Exception while loading attribute <&1> | The short text describes the object sufficiently | |
126 | 309 | Exception while loading tool <&1> | The short text describes the object sufficiently | |
127 | 310 | Authorization error while accessing the attribute tool | The short text describes the object sufficiently | |
128 | 311 | Authorization error in the transition chain | The short text describes the object sufficiently | |
129 | 312 | Exception when loading variant <&1> | The short text describes the object sufficiently | |
130 | 313 | Authorization error when loading variants of process <&1> | The short text describes the object sufficiently | |
131 | 350 | Exception when loading metric <&1> | The short text describes the object sufficiently | |
132 | 351 | Authorization error when loading metric <&1> | The short text describes the object sufficiently | |
133 | 352 | Step <&1> in metric <&2> does not exist | The short text describes the object sufficiently | |
134 | 353 | Field name <&1> in metric <&2> does not exist | The short text describes the object sufficiently | |
135 | 354 | The step for metric <&1> is not defined | The short text describes the object sufficiently | |
136 | 355 | The field name for metric <&1> is not defined | The short text describes the object sufficiently | |
137 | 356 | The first step for metric <&1> is not defined | The short text describes the object sufficiently | |
138 | 357 | The first step for metric <&1> is not defined | The short text describes the object sufficiently | |
139 | 358 | The third step for metric <&1> is not defined | The short text describes the object sufficiently | |
140 | 380 | Exception when loading interface <&1> | The short text describes the object sufficiently | |
141 | 381 | Authorization error when loading interface <&1> | The short text describes the object sufficiently | |
142 | 382 | Field names of interface <&1> not entered | The short text describes the object sufficiently |
History
Last changed on/by | 20110908 | SAP | |
SAP Release Created in | 630 |