/SCMTMS/PLN_OPT_APP - Optimizer Massages concerning the application
The following messages are stored in message class /SCMTMS/PLN_OPT_APP: Optimizer Massages concerning the application.
It is part of development package /SCMTMS/PLN_EXECUTION in software component TM-PLN. This development package consists of objects that can be grouped under "Planning: Execution".
It is part of development package /SCMTMS/PLN_EXECUTION in software component TM-PLN. This development package consists of objects that can be grouped under "Planning: Execution".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Internal error: &1 &2 &3 &4 |
| 001 | Optimizer version does not support application version |
| 002 | Canceled due to insufficient memory; current memory consumption: &1 MB |
| 003 | Time limit without improvement reached |
| 004 | Optimizer set runtime to &1 seconds |
| 005 | Obsolete: Data for optimizer run anonymized |
| 099 | Calling &1 for not supported application &2, only supporting &3 |
| 100 | Initial solution contains errors |
| 110 | First solution read with cost of &1 |
| 111 | Initial solution more expensive than planning none of the transp. demands |
| 112 | Only initial solution is checked |
| 200 | Error while importing data |
| 201 | Error while creating model |
| 202 | Error while returning solution |
| 300 | None of the transportation demands can be planned |
| 302 | No requirement documents passed to the optimizer |
| 303 | No transportation proposal found |
| 304 | No transportation proposal found for freight unit &1 |
| 306 | All planning-relevant transportation demands are fixed |
| 310 | Best solution found is not to plan any of the transportation demands |
| 320 | Runtime is too short; initial solution was not determined |
| 330 | No (scheduled) vehicles passed to the optimizer |
| 331 | No transportation lanes passed to the optimizer |
| 332 | Utilization of &1 freight orders is below threshold for min. utilization |
| 333 | &1 requirement documents are not planned because of minimum utilization |
| 334 | &1 is a consignment order; the optimizer doesn't support COs |
| 335 | Vehicle combination &1 can't be created; subordinate veh. comb. missing |
| 336 | Optimizer doesn't support local items for passive veh. res./veh. types |
| 337 | Subcontracted veh. &1 is part of a veh. comb. and therefore ignored |
| 338 | Subcontracted veh. &1 is not an unlimited multires. and therefore ignored |
| 350 | No transportation proposal found for container unit &1 |
| 351 | No transportation proposal found for railcar unit &1 |
| 352 | No transportation proposal found for package unit &1 |
| 353 | No transportation proposal found for consignment order &1 |
| 400 | Vehicle &1 cannot be used for optimization |
| 401 | Schedule vehicle &1 (departure time &2) cannot be used for optimization |
| 402 | &2 cannot be used |
| 403 | Schedule/booking with means of transport &2 cannot be used |
| 404 | Stop sequence &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 |
| 408 | Means of transport &1 not usable; no transp. lanes out of depot location |
| 409 | Means of transport &1 not usable; no transp. lanes into depot location |
| 410 | Freight unit &1 cannot be completely planned |
| 411 | &1 freight units cannot be planned |
| 412 | &1 of &2 freight units can be planned |
| 416 | FU &1 cannot be completely planned; no usable (scheduled) vehicle exists |
| 418 | &1 freight orders and trailer units additionally fixed for optimization |
| 421 | Parts of freight unit &1 not within the planning horizon |
| 422 | Carrier &1 can't be used by any useable vehicle |
| 423 | There are no useable transportation lanes for carrier &1 |
| 450 | Container unit &1 cannot be completely planned |
| 451 | Railcar unit &1 cannot be completely planned |
| 452 | &1 container units cannot be planned |
| 453 | &1 railcar units cannot be planned |
| 454 | &1 of &2 container units can be planned |
| 455 | &1 of &2 railcar units can be planned |
| 456 | CU &1 cannot be completely planned; no usable (scheduled) vehicle exists |
| 457 | RU &1 cannot be completely planned; no usable (scheduled) vehicle exists |
| 458 | Parts of container unit &1 not within the planning horizon |
| 459 | Parts of railcar unit &1 not within the planning horizon |
| 460 | Package unit &1 can't be completely planned |
| 461 | &1 package units can't be planned |
| 462 | &1 of &2 package units can be planned |
| 464 | Parts of package unit &1 not within the planning horizon |
| 470 | Consignment order &1 can't be planned completely |
| 471 | &1 consignment orders can't be planned |
| 472 | &1 of &2 consignment orders can be planned |
| 474 | Parts of consignment order &1 are not within the planning horizon |
| 500 | FU &1 is inconsistent and is therefore fixed for this optimization run |
| 501 | No master data found for schedule vehicle belonging to FO &1 |
| 502 | Means of transport &1 is not a schedule but is used in a schedule |
| 503 | Resource or equipment type &1 has no valid means of transport |
| 504 | Duration from prev. stop to stop &1 at loc. &2 of sched. &3 must be >=0 |
| 505 | Activity type &1 of activity group &2 is not valid and is ignored |
| 506 | Assign an activity type to activity group &1 |
| 507 | Time constraint &1 has a maximum duration of 0 or below |
| 508 | Time constraint &1 has a constraint length of 0 or below |
| 509 | Activity group &2 of time constraint &1 does not exist |
| 510 | Constraint type &2 of time constraint &1 is unknown |
| 511 | Constraint set &1 uses an undefined time constraint |
| 512 | Constraint set &1 has no time constraints assigned to it |
| 513 | Inconsistent cost function &1 ignored |
| 514 | Inconsistent cost function ignored on MTr &1 |
| 515 | FO &1 is inconsistent and is therefore fixed for this optimization run |
| 516 | Passive means of transport &1 must not be a multiresource |
| 517 | Passive means of transport &1 not used in any combination |
| 518 | Vehicle &1 cannot be used; it is stranded in location &2 |
| 519 | FOR &1 will be fixed for optimization due to aberrant travel information |
| 520 | FO &1 has no resource/equi. type assigned and is fixed for this opt. run |
| 521 | Some schedules can't be used due to data inconsistencies |
| 522 | Schedules modified due to data inconsistencies |
| 523 | Vehicle resource/type, schedule, or booking has incorrect or missing MTr |
| 524 | Define a transportation mode for means of transport &1 |
| 525 | Distance and duration between location &1 and &2 are missing; DD set to 0 |
| 526 | Freight order &1 can�t be scheduled, no additional assignments possible |
| 550 | CU &1 is inconsistent and therefore fixed for this optimizer run |
| 551 | RU &1 is inconsistent and therefore fixed for this optimizer run |
| 552 | |
| 560 | Res/equi. type &1: Horiz. split deck section must cover compl. cargo body |
| 600 | No valid route that fulfills all constraints |
| 601 | No valid connection from source location |
| 602 | No valid connection to destination location |
| 603 | No valid connection from transshipment location that must be used |
| 604 | No valid connection to transshipment location that must be used |
| 605 | No valid direct connection between locations for given stage |
| 606 | No valid route due to stage constraints |
| 608 | No valid route due to transportation mode constraints |
| 612 | No valid route due to shipping type |
| 614 | No valid route due to capacities |
| 616 | No valid route since acceptable dates cannot be met |
| 618 | No valid route that contains all given stages |
| 619 | No valid route that fulfills all constraints; skip detailed analysis |
| 620 | No valid route due to max. number of transshipment locations |
| 621 | FU has too many ADR points to be transported on provided vehicle res/type |
| 623 | No valid route due to default route constraints |
| 625 | No valid route since only default routes are considered |
| 627 | No valid route due to incomp. betw. FU and vehicle, schedule, or booking |
| 628 | No valid route due to incompatibilities between FU and transshipment loc. |
| 629 | No valid route due to incompatibilities between FU and compartment |
| 630 | No valid route due to incomp. between vehicle res. and stay at location |
| 631 | No valid route due to incomp. betw. vehicle res. and (un-)loading at loc. |
| 632 | No valid route since resulting FO would exceed maximum distance/duration |
| 633 | No valid route since no booking exists for the given equipment type |
| 634 | No valid route due to loading/unl. restrictions of provided veh res/type |
| 635 | No valid route due to package dimensions |
| 636 | No valid route due to incompatibilities between FU and carrier |
| 637 | No valid route due to incomp. between carrier and stay at location |
| 690 | &1 req. docs not planned: costs for delivery higher than non-del. costs |
| 691 | &1 requirement documents not planned due to lack of vehicle resources |
| 692 | &1 requirement documents not planned due to time constraints |
| 693 | &1 req. documents not planned due to time constr. or lack of veh. res. |
| 777 | Available memory on optimization server is low (available: &1%) |
| 999 | Calling &1 for not supported application &2, only supporting &3 |