CNVMBTPEM - PEM (Process Execution Manager)

The following messages are stored in message class CNVMBTPEM: PEM (Process Execution Manager).
It is part of development package CNV_MBT_PCL in software component CA-LT. This development package consists of objects that can be grouped under "Components of PCL to be imported into PCL system".
Message Nr ▲
Message Text
001Writing PEM state entry failed
002No state entry exist
003Updating state failed
004Not allowed to execute Dialog Blocks
005Object type expected &1 but gotten &2
006Background job with status &1
007Execution already with status FINISHED
008Start date &1 is in the past
009&1 already executed and restart is not allowed
010Maximum number of allowed restarts is &1 and already reached
011Block execution failed because of '&1'.
014Start mode for &1 is manually but executed in background.
015No active group could be determined
016Create block failed with error '&1'
017The ID &1 is not a block
018&1 started on &2 at &3
019&1 finished
020&1 has not finished predecessors
021Create &1 object failed with message &2
022&1 finished on &2 at &3
024Execution stopped by setting parameter &1
025&1 execution not possible. &1 already locked (foreign lock).
026Could not set an enqueue for the &1.
027Set enqueue for &1 successful.
028Called dequeue for &1.
029Maximum number 9999 of &1 executions reached.
030Action cancelled by program and caused by error.
031Start date is in the future
032PEM Plan updated. Get latest PEM Plan.
033Starting dialog activity &1 with PIFD variant
034Plan execution exceeds maximum allowed runtime
035Could not calculate period of time. Using default value of &1 hours.
036Activity &1 in phase &2 started by PEM on &3 at &4.
037Start time updated to &1
038Activity &1 reached maximum number of &2 re-starts
039Re-start for failed activities in block not allowed by scheduling.
040Re-start for failed activities in block &1 not allowed by scheduling.
041Program stopped execution at &1 on &2
042User stopped execution at &1 on &2
Privacy Policy