CM_EHFND_PCEP - Message Class Product Compliance Event Processing
The following messages are stored in message class CM_EHFND_PCEP: Message Class Product Compliance Event Processing.
It is part of development package EHFND_BO_PCEP in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Business Object Product Compliance Event Processing".
It is part of development package EHFND_BO_PCEP in software component EHS-SUS-FND. This development package consists of objects that can be grouped under "Business Object Product Compliance Event Processing".
Message Nr ▲ | Message Text |
|---|---|
| 001 | Required event parameter is missing. |
| 002 | An error occurred during event processing. See application log &1. |
| 003 | Event type &1 is not supported. |
| 004 | Event type &1 has no processor configured. |
| 005 | Created event &1 for synchronous processing on &2 system time &3 (&4). |
| 006 | Processing of event "&1" started on &2 system time &3 (&4). |
| 007 | Processing of event "&1" finished on &2 system time &3 (&4). |
| 008 | Dispatching event to consumer &1 on &2 system time &3 (&4). |
| 009 | Creating event &1 for asynchronous processing on &2 system time &3 (&4). |
| 010 | An error occurred during the finding of a job for program &1. |
| 011 | An error occurred during the creation of a job with job name &1. |
| 012 | An error occurred in closing the background job &1 with job name &2. |
| 013 | An error (&3) occurred during the start of job &1 with job name &2. |
| 014 | Event processing lock cannot be acquired. |
| 015 | Restart event "&1" for asynchronous processing on &2 system time &3 (&4). |
| 016 | Class &1, method &2, line &3 - Exception occurred. |
| 017 | Exception details: &1 &2 &3 &4. |
| 018 | Job &1 was started successfully. |
| 019 | Job was already started. Running job &1. |
| 020 | Events whose status changed from "In Progress" to "Fatal Error": &1 |
| 021 | Events in status "Completed" that have been removed: &1 |
| 022 | Events whose status changed to "Fatal" (maximum attempts reached): &1 |
| 023 | Events found for processing: &1 |
| 024 | Start event and task processing. |
| 025 | End event and task processing. |
| 026 | An error occured during the creation of notifications. |
| 027 | Exception details: &1 &2 &3 &4. |
| 028 | Event "&1" has been processed and has changed status to "Completed". |
| 029 | Error in saving the data. Saving ended with error code &1. |
| 030 | Changes are rolled back. |
| 031 | Database transaction rejected by BOPF transaction manager. |
| 032 | Job was scheduled on &1 system time &2 (&3). |
| 033 | An error occurred during event creation. |
| 034 | Authorization check failed. |
| 035 | Event "&1" was set to status "Failed" due to an unexpected error. |
| 036 | Synchronous events changed to asynchronous processing: &1 |
| 037 | Event "&1" was set to status "Failed"; max. number of attempts reached. |
| 038 | Event "&1" (&2) was changed to status "In Progress". |
| 039 | Event linkage for event type &1 is disabled or does not exist. |
| 040 | An error occurred in raising the background event. |
| 041 | Event "&1" (&2) set to status "Completed". Dependent object not found. |
| 042 | Task "&1" (&2) set to status "Completed". Dependent object not found. |
| 043 | Task type &1 is not supported. |
| 200 | Required task parameter is missing. |
| 201 | Task found for processing. |
| 202 | Task "&1" has been processed and has changed status to "Completed". |
| 203 | Tasks whose status changed from "In Progress" to "Failed": &1 |
| 204 | Processing of task "&1" started on &2 system time &3 (&4). |
| 205 | Processing of task "&1" finished on &2 system time &3 (&4). |
| 206 | An error occurred during task processing. See application log &1. |
| 207 | An error occured during task creation. |
| 208 | Created task &1 on &2 system time &3 (&4). |
| 209 | Expected the task class to implement the method "execute". |
| 210 | Processing of product compliance task failed. |
| 211 | Processing of product compliance event failed. |
| 212 | Event "&1" has failed and changed status to "Error". |
| 213 | Event "&1" has failed and changed status to "Fatal Error". |
| 214 | Task "&1" (&2) has failed and changed status to "Error". |
| 215 | Task "&1" has failed and changed status to "Fatal Error". |
| 216 | Tasks whose status changed to "Fatal" (maximum attempts reached): &1 |
| 217 | Tasks whose status changed from "In Progress" to "Fatal Error": &1 |
| 218 | Task was set to status "Failed" due to an unexpected error. |
| 219 | Task was set to status "Failed"; maximum number of attempts was reached. |
| 220 | Not yet implemented |
| 221 | Restart task "&1" on &2 system time &3 (&4). |
| 222 | Event processing started. |
| 223 | Task processing started. |
| 224 | Task "&1" (&2) was set to status "In Progress". |
| 225 | &1 Released |
| 226 | &1 Saved |
| 227 | &1 Created |
| 228 | Tasks in status "Completed" that have been removed: &1 |
| 229 | An error occured in looking up the data provider for &1 |
| 230 | Event set to completed as dependent object &1 of type &2 doesn't exist. |
| 231 | Task set to completed as dependent object &1 of type &2 doesn't exist. |
| 232 | Event source object &1 of type &2 doesn't exist. |
| 233 | Event class &1 has to derive from ABAP class CL_EHFND_PCEP_EVT_WF |