CM_EHFND_SCHEDULER -
 The following messages are stored in message class CM_EHFND_SCHEDULER: .
It is part of development package EHFND_COMN in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Common objects for all components".
 It is part of development package EHFND_COMN in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Common objects for all components".
| Message Nr ▲ | Message Text | 
|---|---|
| 000 | Scheduler run complete; &1 schedules executed | 
| 001 | Scheduler is starting up | 
| 002 | PCO assigned to process (&1; &2; &3) has the wrong type | 
| 003 | Process definition of setup &1: (&2; &3; &4) is not valid | 
| 004 | Scheduled run for process (&1; &2; &3) complete | 
| 005 | Undefined error when starting PCO for process (&1; &2; &3) | 
| 006 | Generated cron string &1 has an invalid format | 
| 007 | Cannot open job with the name &1 | 
| 008 | Cannot submit job &1:&2 for report &3 | 
| 009 | Cannot schedule job &1:&2 for &3 &4 | 
| 010 | Error while creating the fallback job for report &1 | 
| 011 | Error while deleting the fallback job for report &1 | 
| 012 | Error while creating a job for report &1 on &2 &3 | 
| 013 | Authorizations are missing for releasing a job for report &1 | 
| 014 | Entry &1 of the process scheduler is invalid | 
| 015 | Run of schedule &1 complete; process (&2, &3, &4) started | 
| 016 | Scheduler has executed all schedules and is not rescheduled for now | 
| 017 | Scheduler executes the next time on &1 (UTC) | 
| 018 | Attempting to clone the BO template for setup &1, process (&2, &3, &4) | 
| 019 | BO template for setup &1 cloned; process (&2, &3, &4) | 
| 020 | Attempting to create the PCBO for setup &1, process (&2, &3, &4) | 
| 021 | PCBO for setup &1 created; process (&2, &3, &4) | 
| 022 | Error while attempting to clone the BO template for setup &1 | 
| 023 | Error while attempting to create the PCBO for setup &1 | 
| 024 | Setup &1 is defined to create the PCBO directly on the related BO | 
| 025 | Setup &1 is defined to create the PCBO on a clone of the related BO | 
| 026 | Error in setup &1; related node has no "clone" action "&2" (BO: &3) | 
| 027 | Error in setup &1; related node has no "create PCBO" action "&2" (BO: &3) | 
| 028 | Error while attempting to execute the setup &1 | 
| 029 | Setup &1 executed | 
| 030 | Start date &1 must be before end date &2 | 
| 031 | Start date &1 must be in the future | 
| 032 | EXECUTE action of the process setup was called for more than one node | 
| 033 | Keys for the related BO of process setup &1 are invalid | 
| 034 | Template node (&1:&2:&3) for the creation of the clone was not found | 
| 035 | Node instance (&1:&2:&3) for the execution was not found | 
| 036 | Execution of process setup root node &1 | 
| 037 | Attempting to execute setup &1 | 
| 038 | Error while attempting to execute the setup &1; state "Executing" | 
| 039 | Error while attempting to execute the setup &1; state "Write Back" | 
| 040 | Error while attempting to execute the setup &1; state "Saving" | 
| 041 | Error while attempting to execute the setup &1; exception: &2 | 
| 042 | End date is before the first execution date | 
| 043 | Setup &1 disabled; use report R_EHFND_PSE_ENABLE_ENTRY to re-enable it | 
| 044 | Cannot delete job &1:&2 for report &3 | 
| 045 | Cannot schedule job &1 in the past (at &2 &3) | 
| 050 | User &1 triggered rescheduling of job to start scheduled processes | 
| 051 | Job to start scheduled process was rescheduled; next execution: &1 (UTC) | 
| 052 | Rescheduling of job to start scheduled processes failed |