/SAPAPO/OPT_DPS_EXP - PP/DS Optimization: Explanation Log
The following messages are stored in message class /SAPAPO/OPT_DPS_EXP: PP/DS Optimization: Explanation Log.
It is part of development package /SAPAPO/OPT in software component SCM-APO-OPT. This development package consists of objects that can be grouped under "Optimization".
It is part of development package /SAPAPO/OPT in software component SCM-APO-OPT. This development package consists of objects that can be grouped under "Optimization".
Message Nr ▲ | Message Text |
|---|---|
| 000 | No explanation found |
| 002 | Loading explanation log |
| 009 | Overview |
| 010 | Delays (&1) |
| 012 | Delaying Times (&1) |
| 020 | Fixings (&1) |
| 030 | Delay: Resources (&1) |
| 040 | Delay: Products (&1) |
| 050 | Deallocations (&1) |
| 060 | Solutions (&1) |
| 070 | Reschedulings (&1) |
| 080 | Changed Orders (&1) |
| 090 | Exploded Products (&1) |
| 100 | Mode not possible due to missing resource |
| 101 | Some modes have been dropped due to too low priority |
| 102 | Mode not possible due to mode compatibility |
| 103 | Mode not possible due to mode compatibility with fixed activity |
| 104 | Mode fixed |
| 105 | Mode not possible because of missing secondary resource |
| 106 | Mode cannot be scheduled |
| 107 | All modes are allowed |
| 108 | Order ignored; mode selection is not possible |
| 120 | Fixed, reason unknown |
| 121 | Fixed because start date is before optimization horizon |
| 122 | Fixed because end date is after optimization horizon |
| 123 | Fixed due to order category |
| 124 | Fixed by fixing interval |
| 125 | Fixed due to release |
| 126 | Fixed because resource not selected |
| 127 | Fixed due to partial fixing of order |
| 128 | Fixed because only deallocated activities can be rescheduled |
| 129 | Fixed by system |
| 130 | Fixed because it is an SNP order |
| 132 | Fixed because the rest of the purchase requisition is also fixed |
| 133 | Fixed due to confirmation |
| 134 | Fixed due to fixing interval |
| 135 | Fixed due to release |
| 137 | Fixed by fixed activity in same locked activity chain |
| 138 | Fixed due to partial fixing of order by right optimization horizon |
| 139 | Fixed due to partial fixing of order by left optimization horizon |
| 141 | Fixed by fixed storage activity in the same operation |
| 142 | Fixed by fixed production activity in the same operation |
| 150 | Earliest Start Date |
| 151 | Earliest start date due to start date of optimized plan |
| 152 | Earliest start date due to start of optimization horizon |
| 153 | Earliest start date due to order validity |
| 154 | Earliest start date due to planned delivery time |
| 155 | Earliest start date due to replenishment lead time |
| 156 | Earliest start date due to activity relationship |
| 157 | Earliest start date due to maximum interval |
| 158 | Earliest start date due to pegging |
| 159 | Earliest start date due to dynamic pegging |
| 160 | Earliest start date due to priorisation |
| 161 | Earliest start date due to sequence fixation |
| 162 | Earliest start date due to sequence fixation of a resource |
| 180 | Earliest end date |
| 181 | Earliest end date due to validity |
| 182 | Earliest end date due to activity relationship |
| 183 | Earliest end date due to maximum interval |
| 184 | Earliest end date due to pegging |
| 185 | Earliest end date due to dynamic pegging relationships |
| 210 | Latest start date (hard constraint) |
| 211 | Latest start date due to validity (hard constraint) |
| 212 | Latest start date due to activity relationship (hard constraint) |
| 213 | Latest start date due to maximum interval (hard constraint) |
| 214 | Demand at start date (hard constraint) |
| 215 | Lastest start date due to dynamic pegging relationship (hard constraint) |
| 240 | Latest end date (hard constraint) |
| 241 | Latest end date due to validity (hard constraint) |
| 242 | Latest end date due to maximum interval (hard constraint) |
| 243 | Demand represents a hard constraint |
| 244 | Latest end date due to dynamic pegging relationship (hard constraint) |
| 270 | Latest start |
| 271 | Latest start date due to validity |
| 272 | Latest start date due to activity relationship |
| 273 | Latest start date due to maximum interval |
| 274 | Demand at start date |
| 275 | Latest start date due to dynamic pegging relationship |
| 300 | Latest end date |
| 301 | Latest end date due to end of optimization horizon |
| 302 | Latest end date due to validity |
| 303 | Latest end date due to activity relationship |
| 304 | Latest end date due to maximum interval |
| 305 | Demand |
| 306 | Latest end date due to dynamic pegging relationship |
| 307 | Desired Date |
| 330 | Delay |
| 331 | Delay due to capacity conflict |
| 332 | Delay due to operation-internal maximum intervals |
| 333 | Delay due to maximum interval and subsequent capacity conflict |
| 334 | Delay due to subsequent capacity conflict |
| 335 | Delay caused by bucket capacity conflict |
| 336 | Delay due to maximal fill level of storage resource |
| 337 | Delay due to product purity of storage resource |
| 360 | Deallocation |
| 361 | Keep deallocation |
| 362 | Keep deallocation due to fixing |
| 363 | Deallocation due to end of optimization horizon |
| 364 | Deallocation due to delay despite infinite scheduling |
| 365 | Deallocation due to delay caused by lack of capacity |
| 366 | Deallocation due to delay |
| 367 | Deallocation due to deallocated predecessor |
| 390 | End of optimization horizon |
| 391 | End of Validity |
| 392 | Latest date/time for operation to be on time |
| 393 |