/SAPAPO/DM_SCHEDFAIL - Explanation Component Messages (ScheduleFailures)
The following messages are stored in message class /SAPAPO/DM_SCHEDFAIL: Explanation Component Messages (ScheduleFailures).
It is part of development package /SAPAPO/DM in software component SCM-APO-CA. This development package consists of objects that can be grouped under "Data manager (central object management in Livecache & DB)".
It is part of development package /SAPAPO/DM in software component SCM-APO-CA. This development package consists of objects that can be grouped under "Data manager (central object management in Livecache & DB)".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Scheduling/rescheduling was successful |
| 001 | Scheduling/rescheduling successful - BOM invalid |
| 002 | Scheduling/rescheduling successful - no object was rescheduled |
| 003 | Limit exceeded |
| 004 | No activity was specified for scheduling |
| 005 | Validity of activity &1 lies outside planning period |
| 006 | No slot available for activity &1 |
| 007 | Minimum or maximum time interval cannot be adhered to |
| 008 | Fixed pegging relationship could not be adhered to |
| 009 | Dynamic pegging could not be adhered to |
| 010 | Object locked by another user |
| 011 | Obsolete object |
| 012 | Fixed activity &1 |
| 013 | No valid modes available for activity &1 |
| 014 | Activity &1 does not have a mode for predefined resource &2 |
| 015 | Product not in propagation area |
| 016 | A max time interval cannot be adhered to |
| 017 | Activity &1 could not be scheduled or rescheduled |
| 018 | System cannot schedule or reschedule an activity &1 |
| 019 | Timeout |
| 020 | Activity &1 already confirmed |
| 021 | Activity &1 is outside the planning period |
| 022 | Order structure contains a cycle |
| 023 | Specified time was not met |
| 024 | Date of an activity lies outside the maximum planning time period |
| 025 | Validity period cannot be adhered to |
| 026 | Mode linkage of a relationship to the activity &1 cannot be adhered to |
| 027 | Campaign conditions cannot be adhered to |
| 028 | Locked activity chain of other activities is blocking gap for activity |
| 029 | Sequence-dependent setup activity follows gap; no scheduling possible |
| 030 | No gap found for activity &1 in suitable block |
| 031 | No gap for activity &1 due to synchronization condition |
| 032 | No gap for activity &1 due to fixing interval |
| 040 | Activity &1 not in propagation range and cannot be shifted |
| 041 | Activity &1 is already confirmed and so cannot be shifted |
| 042 | Activity &1 is fixed because it is in the fixing interval of the resource |
| 043 | Activity &1 is fixed because it is in a fixed block |
| 044 | No gap for activity &1 found within the planning horizon |
| 060 | The system has switched to infinite planning |
| 061 | The activity was deallocated |
| 062 | Dynamic pegging has been violated - minimum pegging relationship |
| 063 | Dynamic pegging has been violated - maximum pegging relationship |
| 064 | Fixed pegging was broken - min. edge |
| 065 | Fixed pegging was broken - max. edge |
| 066 | External relationships have been violated - minimum pegging relationship |
| 067 | External relationships have been violated - maximum pegging relationship |
| 068 | Internal relationships have been violated - minimum pegging relationship |
| 069 | Internal relationships have been violated - maximum pegging relationship |
| 070 | Activity &1 cannot be scheduled on specified mode |
| 071 | Activity &1 could not be scheduled nor deallocated |
| 072 | Order &1 was reset to original item |
| 073 | Pegging relationship to matrix order could not be adhered to |
| 074 | Activity &1 was reset to original position |
| 899 | Unknown error. Error number: &1 |