SWF_SLS - Nachrichtenklasse der Termin�berwachung (Deadline Service)
The following messages are stored in message class SWF_SLS: Nachrichtenklasse der Termin�berwachung (Deadline Service).
It is part of development package SWF_SLS in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Deadline Service - Deadline Monitoring".
It is part of development package SWF_SLS in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Deadline Service - Deadline Monitoring".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Insufficient authorization for &1 deadlines of application &2 |
| 001 | Unable to determine dimension key for this time |
| 002 | Time unit &1 specified does not correspond to any of the possible values |
| 003 | Unable to determine internal time unit for counter &1 |
| 004 | Time stamp to be monitored missing for the deadline you want to create |
| 005 | Callback class for deadline to be created is missing |
| 006 | &1 is not a valid callback class |
| 007 | Unable to save the data container of the deadline to be created |
| 008 | Parameters for scheduling periodic deadlines are missing |
| 009 | &1 is not a valid calculation class for periodic deadlines |
| 010 | Negative or initial time quantity for the periodic deadline |
| 011 | Deadlines not changed due to duplicate entries |
| 012 | Alert category is missing for deadline to be created |
| 013 | Alert category &1 does not exist |
| 014 | &1 missing; deadline event cannot be triggered |
| 015 | Interval until next due date of periodic deadline is less than & |
| 016 | Error when calculating the next due date of the periodic deadline |
| 017 | Periodic deadline & is after the last possible deadline & |
| 018 | Background job & from deadline monitoring scheduled successfully |
| 019 | & package(s) from due deadlines from previous jobs not fully processed |
| 020 | Due deadlines (time stamp <=&) locked against changes |
| 021 | & due deadlines selected and their status set to in processing |
| 022 | & deadline package(s) for async. processing created for component &2 |
| 023 | Event for processing &1 deadlines for component &2 triggered |
| 024 | Synchronous processing of &1 deadlines for component &2 started |
| 025 | Deadline processing for component &1 executed at destination &2 |
| 026 | Some of the deadlines of & package(s) had to be reactivated |
| 027 | Asynchronous job & (& deadlines) not processed completely |
| 028 | Package & (& deadlines) from last job still exists |
| 029 | Deadlines from & components. Deadlines bundled into components |
| 030 | Callbacks for component & started for the deadline package |
| 031 | Scheduling of periodic deadlines of package from component & started |
| 032 | Background job for deadline monitoring not scheduled |
| 033 | &. Deadline of periodic series & overdue at scheduling |
| 034 | Problems in deadline monitoring and scheduling of periodic deadline |
| 035 | Error while scheduling & periodic deadlines of component &: & |
| 036 | Cannot change trace catalog |
| 037 | Error while calculating time stamp for periodic deadline & |
| 038 | Deadline scheduling class is missing for periodic deadline series & |
| 039 | Callback for deadline & not possible due to invalid callback class & |
| 040 | &1 unsuccessful callbacks for deadline &2 |