SAP ABAP Message Class SWF_SLS (Message Class for Deadline Monitoring (Deadline Service))
Basic Data
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-BMT-WFM (Application Component) SAP Business Workflow
⤷ SWF_SLS (Package) Deadline Service - Deadline Monitoring
⤷ BC-BMT-WFM (Application Component) SAP Business Workflow
⤷ SWF_SLS (Package) Deadline Service - Deadline Monitoring
Attributes
Message class | SWF_SLS | |
Short Description | Message Class for Deadline Monitoring (Deadline Service) | |
Changed On | 20041228 | |
Last Changed At | 182854 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Insufficient authorization for &1 deadlines of application &2 | The short text describes the object sufficiently | |
2 | 001 | Unable to determine dimension key for this time | The short text describes the object sufficiently | |
3 | 002 | Time unit &1 specified does not correspond to any of the possible values | The short text describes the object sufficiently | |
4 | 003 | Unable to determine internal time unit for counter &1 | The short text describes the object sufficiently | |
5 | 004 | Time stamp to be monitored missing for the deadline you want to create | The short text describes the object sufficiently | |
6 | 005 | Callback class for deadline to be created is missing | The short text describes the object sufficiently | |
7 | 006 | &1 is not a valid callback class | Space: object requires documentation | |
8 | 007 | Unable to save the data container of the deadline to be created | The short text describes the object sufficiently | |
9 | 008 | Parameters for scheduling periodic deadlines are missing | Space: object requires documentation | |
10 | 009 | &1 is not a valid calculation class for periodic deadlines | The short text describes the object sufficiently | |
11 | 010 | Negative or initial time quantity for the periodic deadline | The short text describes the object sufficiently | |
12 | 011 | Deadlines not changed due to duplicate entries | The short text describes the object sufficiently | |
13 | 012 | Alert category is missing for deadline to be created | The short text describes the object sufficiently | |
14 | 013 | Alert category &1 does not exist | The short text describes the object sufficiently | |
15 | 014 | &1 missing; deadline event cannot be triggered | The short text describes the object sufficiently | |
16 | 015 | Interval until next due date of periodic deadline is less than & | The short text describes the object sufficiently | |
17 | 016 | Error when calculating the next due date of the periodic deadline | The short text describes the object sufficiently | |
18 | 017 | Periodic deadline & is after the last possible deadline & | The short text describes the object sufficiently | |
19 | 018 | Background job & from deadline monitoring scheduled successfully | Space: object requires documentation | |
20 | 019 | & package(s) from due deadlines from previous jobs not fully processed | The short text describes the object sufficiently | |
21 | 020 | Due deadlines (time stamp <=&) locked against changes | The short text describes the object sufficiently | |
22 | 021 | & due deadlines selected and their status set to in processing | The short text describes the object sufficiently | |
23 | 022 | & deadline package(s) for async. processing created for component &2 | The short text describes the object sufficiently | |
24 | 023 | Event for processing &1 deadlines for component &2 triggered | The short text describes the object sufficiently | |
25 | 024 | Synchronous processing of &1 deadlines for component &2 started | The short text describes the object sufficiently | |
26 | 025 | Deadline processing for component &1 executed at destination &2 | The short text describes the object sufficiently | |
27 | 026 | Deadlines of & package(s) had to be partly reactivated | The short text describes the object sufficiently | |
28 | 027 | Asynchronous job & (& deadlines) not processed completely | The short text describes the object sufficiently | |
29 | 028 | Package & (& deadlines) from last job still exists | The short text describes the object sufficiently | |
30 | 029 | Deadlines from & components. Deadlines bundled into components | The short text describes the object sufficiently | |
31 | 030 | Callbacks for component & started for the deadline package | The short text describes the object sufficiently | |
32 | 031 | Scheduling of periodic deadlines of package from component & started | The short text describes the object sufficiently | |
33 | 032 | Background job for deadline monitoring not scheduled | The short text describes the object sufficiently | |
34 | 033 | &. Deadline of periodic series & overdue at scheduling | Space: object requires documentation | |
35 | 034 | Problems in deadline monitoring and scheduling of periodic deadline | The short text describes the object sufficiently | |
36 | 035 | Error while scheduling & periodic deadlines of component &: & | The short text describes the object sufficiently | |
37 | 036 | Cannot change trace catalog | The short text describes the object sufficiently | |
38 | 037 | Error while calculating time stamp for periodic deadline & | The short text describes the object sufficiently | |
39 | 038 | Deadline scheduling class is missing for periodic deadline series & | The short text describes the object sufficiently | |
40 | 039 | Callback for deadline & not possible due to invalid callback class & | The short text describes the object sufficiently | |
41 | 040 | &1 unsuccessful callbacks for deadline &2 | The short text describes the object sufficiently |
History
Last changed on/by | 20041228 | SAP | |
SAP Release Created in | 700 |