/SAPAPO/OPT_VSR_MSG - VSR Optimizer Messages
The following messages are stored in message class /SAPAPO/OPT_VSR_MSG: VSR Optimizer Messages.
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 | Internal error |
| 001 | Optimizer version does not support application version |
| 002 | Canceled due to insufficient memory. Current memory consumption: &1 MB |
| 003 | Timelimit without improvement reached |
| 004 | Optimizer set runtime to &1 seconds |
| 099 | Calling &1 for not supported application &2, only supporting &3 |
| 100 | Initial solution has errors |
| 101 | Order &1 exceeds the maximum goods wait time at location &2 |
| 102 | Trip scheduled for vehicle &1 from &2 to &3 is infeasible |
| 103 | Order &2 scheduled for vehicle &1 is infeasible |
| 104 | Schedule for vehicle &1 is infeasible |
| 105 | Order &1 falls short of minimum goods wait time at location &2 |
| 110 | First solution read with costs of &1 |
| 111 | Initial solution more expensive than non-deliv. of all orders (cost &1) |
| 112 | Only initial solution is checked |
| 200 | Error while importing data |
| 201 | Error while creating model |
| 202 | Error while writing back solution |
| 210 | Order & has several compatible transshipment locations for location &2 |
| 300 | No orders can be delivered |
| 301 | Orders cannot be scheduled in the planning horizon |
| 302 | No orders passed to optimizer |
| 310 | The best solution found is to not deliver any orders |
| 320 | Runtime too short. Initial solution was not determined |
| 330 | No (scheduled) vehicles passed to optimizer |
| 331 | No transportation lanes passed to optimizer |
| 400 | Vehicle &1 is not required |
| 401 | Schedule vehicle &1 (departure time &2) is not required |
| 402 | Means of transport &2 cannot be used |
| 403 | Means of transport &2 cannot be used (schedule vehicle) |
| 404 | Itinerary &1 cannot be used |
| 405 | Means of Transport &1 cannot be used because of maximum distance of 0 |
| 406 | Means of Transport &1 cannot be used because of maximum duration of 0 |
| 407 | Lanes for means of transport &1 not transferred to the optimizer |
| 410 | Order &1 cannot be delivered |
| 411 | In total &1 orders that cannot be delivered at all |
| 412 | &1 of &2 orders could be delivered |
| 413 | Order &1 is too large for any of the resources |
| 414 | Order &1 has no non-delivery cost |
| 416 | Order &1 cannot be delivered; no usable (scheduled) vehicle exists |
| 418 | &1 additional orders fixed for optimization |
| 419 | Cannot plan freight unit &1 due to predecessor &2 |
| 420 | Cannot plan group containing freight unit &1 |
| 421 | Parts of freight unit &1 not within the time horizon |
| 504 | Duration from prev. stop to stop &1 at loc. &2 of sched. &3 must be >=0 |
| 513 | Inconsistent cost function ignored |
| 514 | Inconsistent cost function ignored on MTr &1 |
| 517 | Passive means of transport &1 not used in any combination |
| 518 | Vehicle &1 cannot be used; it is stranded in location &2 |
| 521 | Some schedules can't be used due to data inconsistencies |
| 522 | Schedules modified due to data inconsistencies |
| 523 | Vehicle resource or schedule has incorrect or missing MTr |
| 777 | Available memory on optimization server is low (available: &1%) |
| 999 | Calling &1 for not supported application &2, only supporting &3 |