Id | Title |
---|---|
SPI21249 | Relation <&1> cannot be assigned to a relation rule |
SPI21250 | Technical relation of field <&1> in rule <&2> is consistent |
SPI21251 | Technical relation <&1>: invalid field <&2> |
SPI21252 | Unable to determine technical field names |
SPI21253 | Technical relation <&1>: Invalid field comparison |
SPI21255 | Transition <&1> is consistent |
SPI21256 | Transition <&1>: 1st step <&2> does not exist in process <&3> |
SPI21257 | Transition <&1>: 2nd step <&2> does not exist in process <&3> |
SPI21260 | RFC destination for step <&1> is consistent |
SPI21261 | URL of the ITS for the RFC destination for step <&1> is missing |
SPI21262 | Local system for the RFC destination for step <&1> is missing |
SPI21263 | No RFC destination specified for step <&1> |
SPI21264 | RFC destination <&1> for step <&2> has errors (&3) |
SPI21265 | Instance attribute <&1> is consistent |
SPI21266 | No tool maintained for symbol '&1' |
SPI21267 | No attribute entered for symbol '&1' |
SPI21268 | Attribute <&1> is missing in tool <&2> of process instance <&3> |
SPI21269 | Attribute <&1> is missing in tool <&2> of process step instance <&3> |
SPI21270 | An invalid process step instance <&2> has been entered for symbol <&1> |
SPI21271 | RFC destination <&1> is not available |
SPI21280 | Step <&3> does not have any relationships in variant &1, level &2 |
SPI21281 | Incomplete definition of relationships in variant &1, level &2 |
SPI21282 | Incomplete paths in definition of transitions in variant &1, level &2 |
SPI21283 | Missing initial steps in variant &1, level &2 |
SPI21284 | Step <&3> has no payload in variant &1, level &2 |
SPI21285 | Step <&3> in variant &1, level &2 has payload with higher level |
SPI21290 | Variant <&1>, level <&2> is consistent |
SPI21300 | Exception when loading steps of process <&1> |
SPI21301 | Authorization error when loading steps of process <&1> |
SPI21302 | Exception when loading transitions of process <&1> |
SPI21303 | Authorization error when loading transitions of process <&1> |
SPI21304 | Exception when loading relations of process <&1> |
SPI21305 | Authorization error when loading relations of process <&1> |
SPI21306 | Authorization error when loading the agent <&1> |
SPI21307 | Exception while loading process <&1> |
SPI21308 | Exception while loading attribute <&1> |
SPI21309 | Exception while loading tool <&1> |
SPI21310 | Authorization error while accessing the attribute tool |
SPI21311 | Authorization error in the transition chain |
SPI21312 | Exception when loading variant <&1> |
SPI21313 | Authorization error when loading variants of process <&1> |
SPI21350 | Exception when loading metric <&1> |
SPI21351 | Authorization error when loading metric <&1> |
SPI21352 | Step <&1> in metric <&2> does not exist |
SPI21353 | Field name <&1> in metric <&2> does not exist |
SPI21354 | The step for metric <&1> is not defined |
SPI21355 | The field name for metric <&1> is not defined |
SPI21356 | The first step for metric <&1> is not defined |
SPI21357 | The first step for metric <&1> is not defined |
SPI21358 | The third step for metric <&1> is not defined |
SPI3001 | &1: Assembling started for <&2> |
SPI3002 | Assembling ended for <&1> |
SPI3003 | Process type is already being assembled - processing stopped |
SPI3004 | No new data since last run - processing stopped |
SPI3005 | No incomplete process instances exist for <&1> |
SPI3006 | &2 incomplete process instances for <&1> loaded |
SPI3007 | Process type <&1> does not have a starting step |
SPI3008 | An exception has occurred |
SPI3009 | Very high volume of data (<&1> unassigned data records) |
SPI3010 | Step <&1>: no datasets available |
SPI3011 | Step <&2>: &1 datasets read |
SPI3012 | Step <&1>; no datasets added |
SPI3013 | Step <&2>: &1 datasets added |
SPI3014 | Step <&1>: no relationship to existing process instances available |
SPI3015 | Process type <&1>: &2 new instances created |
SPI3016 | Dispatcher: Tracking records for this run: &1 |
SPI3017 | Dispatcher: Period to be matched: &1 |
SPI3018 | Dispatcher: &1 obsolete tracking records deleted |
SPI3019 | Dispatcher: Adjusting job period (d/h/m): &1/&2/&3 |
SPI3020 | Assembler: &1 instances skipped |
SPI3021 | Assembler: no relationship between process instances |
SPI3022 | Update process instances: header (&1); steps (&2) |
SPI3023 | Insert process instances: header (&1); steps (&2) |
SPI3024 | Delete Tracking Records: Header (&1) |
SPI3025 | Insert process steps: failed (&1) |
SPI3026 | Deactivating process (backlog is too large) |
SPI3027 | Extracting tracking records for top processes: |
SPI3028 | Top process <&1>, step <&2> |
SPI3030 | Administration data could not be updated |
SPI3031 | Administration data was updated |
SPI3032 | &1: Assembler started for &2 with variant &3, level &4 |
SPI3035 | Inserts: &1 |
SPI3036 | Updates: &1 |
SPI3037 | Top process: Changes to subprocess instances (top process steps) |
SPI3038 | Number of deleted obsolete tracking records: &1 |
SPI3039 | Number of modified top process steps: &1 |
SPI3041 | Dispatcher: Database cursor on &1 could not be opened |
SPI3042 | RFC exception: &1 |
SPI3043 | Dispatcher: Active jobs of the previous run still exist |
SPI3044 | RFC exception: No resources for job &1 |
SPI3050 | Parallelization for assembling process instances |
SPI3051 | Parallelization exceeded |
SPI3052 | Duration of the assembler run in seconds |
SPI3053 | Duration of the assembler run exceeds the threshold value specified |
SPI3060 | &2 loaded for <&1> (&3) |
SPI3061 | &2/&3/&4 (Ins/Upd/Del) for <&1> |
SPI3062 | No confirmation for <&1> (&3) |
SPI3063 | Return code &2 for <&1> (&3) |
SPI3070 | Assembly started with step: &1 |
SPI3071 | &1 open process(es) |