Message Number list used by SAP ABAP Class CL_STCTM_SESSION (Task List Run)
SAP ABAP Class CL_STCTM_SESSION (Task List Run) is using
# | Object Type | Object Name | Object Description | Note |
---|---|---|---|---|
1 | Message Number | STC_TM - 252 | Task list run has been executed before; choose resume functionality | |
2 | Message Number | STC_TM - 317 | Task &1 reports checkrun progess &2% | |
3 | Message Number | STC_TM - 316 | Task &1 reports execution progess &2% | |
4 | Message Number | STC_TM - 313 | Task list run &1 is finalized by user &2 and cannot be processed anymore | |
5 | Message Number | STC_TM - 313 | Task list run &1 is finalized by user &2 and cannot be processed anymore | |
6 | Message Number | STC_TM - 313 | Task list run &1 is finalized by user &2 and cannot be processed anymore | |
7 | Message Number | STC_TM - 311 | Task list run &1 is finalized and cannot be processed anymore | |
8 | Message Number | STC_TM - 311 | Task list run &1 is finalized and cannot be processed anymore | |
9 | Message Number | STC_TM - 311 | Task list run &1 is finalized and cannot be processed anymore | |
10 | Message Number | STC_TM - 295 | Action log has not been opened | |
11 | Message Number | STC_TM - 294 | Action log has not been closed | |
12 | Message Number | STC_TM - 275 | Parameters maintained in language '&2'; maintenance of run &1 denied | |
13 | Message Number | STC_TM - 269 | Task '&1' is skipped but have to be executed; set task manually in scope | |
14 | Message Number | STC_TM - 268 | Task '&1' is set in scope automatically because it is mandatory | |
15 | Message Number | STC_TM - 255 | Task list run is not processing; stop signal not required | |
16 | Message Number | STC_TM - 254 | No task in list to be checked; check run not necessary | |
17 | Message Number | STC_TM - 023 | Task list run &1 is currently locked by user &2 | |
18 | Message Number | STC_TM - 211 | Task list run aborted due to lost entry in lock table | |
19 | Message Number | STC_TM - 210 | Running task aborted because task list run is not processed anymore | |
20 | Message Number | STC_TM - 191 | Task '&1' is skipped automatically because it cannot be executed | |
21 | Message Number | STC_TM - 190 | Task '&1' is in scope but cannot be executed; skip task manually | |
22 | Message Number | STC_TM - 096 | Background job &1/&2 is aborted | |
23 | Message Number | STC_TM - 095 | Background job &1/&2 is released | |
24 | Message Number | STC_TM - 093 | Background job &1/&2 is aborted; see task log for details | |
25 | Message Number | STC_TM - 092 | Background job &1/&2 is ready to run | |
26 | Message Number | STC_TM - 091 | Background job &1/&2 is currently running | |
27 | Message Number | STC_TM - 090 | Background job &1/&2 is scheduled; no second execution allowed | |
28 | Message Number | STC_TM - 047 | Error &3 while checking the job status | |
29 | Message Number | STC_TM - 046 | Background job &1/&2 does not exist anymore | |
30 | Message Number | STC_TM - 023 | Task list run &1 is currently locked by user &2 | |
31 | Message Number | STC_TM - 023 | Task list run &1 is currently locked by user &2 | |
32 | Message Number | STC_TM - 023 | Task list run &1 is currently locked by user &2 |