SWF_CCMS - CCMS: Monitoring
The following messages are stored in message class SWF_CCMS: CCMS: Monitoring.
It is part of development package SWF_ALM in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Workflow: Alert Monitor Connection".
It is part of development package SWF_ALM in software component BC-BMT-WFM. This development package consists of objects that can be grouped under "Workflow: Alert Monitor Connection".
Message Nr ▲ | Message Text |
|---|---|
| 000 | ***************** CCMS Structure ***************** |
| 001 | Business Process Engine |
| 002 | Date management monitoring |
| 003 | Last successful run of automatic date monitoring |
| 004 | Dates with error status |
| 005 | Runtime environment monitoring |
| 006 | Error in XI cache during activation of processes |
| 007 | Process instances without definition data |
| 008 | Did not find RFC destination for client &1 |
| 009 | Process instances with error status |
| 010 | Inbound processing monitoring |
| 011 | Events with ERROR status in the event queue |
| 012 | Event linkages deactivated as the consequence of an error |
| 013 | At least one event waiting for x minutes for notification |
| 014 | Process start monitoring |
| 015 | Process instances not started in READY status |
| 016 | Process Engine monitoring |
| 017 | Traces and database |
| 018 | Event trace status |
| 019 | Process control monitoring |
| 020 | Last successful run of automatic error handling |
| 021 | Last successful run of automatic cleanup |
| 022 | Last successful run of event queue monitoring |
| 023 | Process trace status |
| 024 | Wait time in minutes for qRFC BPE entries |
| 025 | Oldest qRFC entry has not been processed for x minutes |
| 026 | Process Instances |
| 027 | Process data monitoring |
| 028 | Process terminated as consequence of locks |
| 029 | Process execution monitoring |
| 030 | XML Messages |
| 031 | Process instances with unsent messages |
| 032 | No value reported yet |
| 033 | Checks settings for event linkage error handling |
| 034 | Processes that cannot be restored after system crash |
| 035 | Checks BPE qRFC queues for entries with errors |
| 036 | Process instances with unprocessed messages |
| 037 | Messages in the PE Adapter |
| 038 | Process instance consistency check |
| 039 | Last successful buffer-update run |
| 040 | Overall Status |
| 041 | Status of Business Process Engine |
| 042 | Status of Automatic Customizing |
| 043 | Data collector started successfully |
| 044 | Last successful message-dispatching run |
| 045 | Message Dispatching Monitor |
| 046 | Entries with errors in BPE dispatcher |
| 047 | Canceled entries in BPE dispatcher |
| 048 | Rescheduled entries in BPE dispatcher |
| 049 | Last successful reorganization of BPE dispatcher |
| 055 | Undeliverable messages |
| 056 | Messages do not correspond to definition |
| 100 | ***************** Error when calling CCMS modules ***************** |
| 101 | Could not create summary nodes for ID & |
| 102 | Could not create CCMS context |
| 103 | Could not create monitor ID & |
| 104 | Could not create log attribute ID &1 |
| 105 | Could not create performance attribute ID &1 |
| 106 | Could not create status attribute for ID &1 |
| 107 | Error when reading alert for ID & |
| 108 | Could not create text attribute for ID &1 |
| 110 | Attribute type & invalid |
| 111 | Error & when reporting performance values |
| 112 | Error & when reporting status values |
| 113 | Error & when reporting log values |
| 114 | Error & when reporting text values |
| 120 | Class '&1' does not exist. Check CCMS method definition '&2' |
| 121 | Parameter '&1' is missing in CCMS method definition '&2' |
| 122 | Specify a value for parameter '&1' in method '&2' |
| 123 | Log on to call analysis method in client &1 |
| 124 | Error when formatting data for the analysis tool |
| 125 | No authorization for transaction &1 |
| 126 | Error when calling analysis tool &1 |
| 127 | Cannot call analysis tool |
| 128 | Start Program &1 ... |
| 129 | Function module '&1' does not exist. Check method definition '&2' |
| 130 | Error when calling data collector in destination &1 |
| 131 | No configuration authorization (authorization object: &1) |
| 132 | No authorization for authorization object &1, authorization group &2 |
| 133 | Data collector &1 started successfully |
| 134 | Could not start data collector &1 |
| 135 | Error during call in RFC destination &1 |
| 150 | ***************** Values that report applications ***************** |
| 151 | Last successful run on &1 at &2 (&3) |
| 152 | Dates with ERROR status exist |
| 153 | No dates with ERROR status exist |
| 154 | All processes have started |
| 155 | Some processes have not started |
| 156 | Process trace was switched on |
| 157 | Process trace was switched on (not a production system) |
| 158 | Process trace was switched off |
| 160 | Event queue contains events with ERROR status |
| 161 | Event queue does not contain events with ERROR status |
| 162 | Event linkages with ERROR status exist |
| 163 | No event linkages with ERROR status exist |
| 164 | Event trace was switched on |
| 165 | Event trace was switched on (not a production system) |
| 166 | Event trace was switched off |
| 167 | Processes with ERROR status exist |
| 168 | No processes with ERROR status exist |
| 169 | Processes with lock problems exist |
| 170 | No processes with lock problems exist |
| 171 | &1 process instances with unsent messages |
| 172 | Correct behavior set for error confirmation |
| 173 | Event linkages exist that can be deactivated in the event of errors |
| 174 | System settings deactivate event linkages in the event of errors |
| 175 | No processes found |
| 176 | At least one process found |
| 177 | BPE qRFC queue without errors |
| 178 | BPE qRFC queue contains entries with ERROR status |
| 179 | All messages were processed |
| 180 | Messages for process type &1 were parked and not processed immediately |
| 181 | No messages parked in PE Adapter |
| 182 | &1 messages could not be delivered (PE Adapter) |
| 183 | Inconsistent process instances |
| 184 | No inconsistent process instances |
| 185 | Message for ended process '&1' parked but not processed |
| 186 | BPE customizing not fully maintained |
| 187 | BPE customizing maintained |
| 188 | Message dispatching is not activated |
| 190 | BPE status: ready |
| 191 | BPE status: stopped |
| 192 | Stopping the BPE |
| 193 | Starting the BPE |
| 201 | XI cache contains process that could not be activated |
| 202 | XI cache does not contain any processes with errors |
| 205 | Process instances without definition & exist |
| 206 | Process instances without definition exist |
| 207 | No data selected; administration tool not started |
| 210 | Entries with status ERROR exist |
| 211 | No entries with status ERROR exist |
| 212 | Entries with status CANCEL exist |
| 213 | No entries with status CANCEL exist |
| 215 | & entries rescheduled |
| 220 | Message '&' not delivered due to missing correlation instance |
| 230 | Payload of message & is not in XML format |
| 231 | Payload of message & does not have the expected root tag |
| 235 | &1 deadlines for processing for party &2, component &3 (task &4) |
| 236 | No processes selected |
| 237 | &1 deadlines to process for task &2 |
| 238 | No delays with subordinate deadline monitoring jobs |
| 239 | Delays with &1 of &2 deadline monitoring jobs |
| 240 | No active subordinate deadline monitoring job |
| 241 | Delay with subordinate deadline monitoring job &1 |
| 242 | Status of subordinate deadline monitoring job |
| 243 | Execution of deadline monitoring with job &1 lasted &2 seconds |
| 300 | ***************** Other ***************** |
| 301 | Process category &1 is not supported |