/SCMTMS/PLN_OPT_EXP - Optimizer Explanation Tables: Codes
The following messages are stored in message class /SCMTMS/PLN_OPT_EXP: Optimizer Explanation Tables: Codes.
It is part of development package /SCMTMS/PLN_EXP_CMN in software component TM-PLN-EXP. This development package consists of objects that can be grouped under "Planning Engine Explaination Tools Common Parts".
It is part of development package /SCMTMS/PLN_EXP_CMN in software component TM-PLN-EXP. This development package consists of objects that can be grouped under "Planning Engine Explaination Tools Common Parts".
Message Nr ▲ | Message Text |
|---|---|
| 000 | |
| 498 | Requirement document fixed for optimization due to data inconsistency |
| 499 | Requirement document fixed for optimization; assigned FUs incompatible |
| 500 | Stop fixed for optimization due to propagation |
| 502 | Stop fixed for opt. due to inconsistent stop assignment |
| 503 | Stop fixed for opt. due to inconsistent stage assignment |
| 504 | Stop has initial status "Fixed" due to context determination |
| 505 | Stop has status "Fixed" set by user |
| 506 | FU fixed for opt. because not sel. for creation of transp. proposals |
| 508 | Assignment ignored for transp. proposal; FO might become inconsistent |
| 509 | Stop fixed for optimization; one location visited at least twice |
| 510 | Stop fixed for opt. due to data inconsistency; enter a valid UN/LOCODE |
| 511 | Stop fixed for opt. due to data inconsistency; enter a valid IATA code |
| 512 | Stop fixed for opt.; same UN/LOCODE as only location ID used twice |
| 513 | Stop fixed for opt.; same IATA code as only location ID used twice |
| 514 | Stop fixed for opt.; ID of first relevant location not unique |
| 515 | Stop fixed for opt.; ID of last relevant location not unique |
| 516 | Fixed for optimization; acceptable dates are invalid |
| 517 | Requirement document fixed for opt. due to inconsistent stop assignment |
| 518 | Requirement document fixed for opt. due to inconsistent stage assignment |
| 519 | Demand document fixed for optimization due to inconsistency (loading loc) |
| 520 | Stage cannot be used; fixed vehicles at stage are different |
| 522 | Stage cannot be used due to means of transport restrictions |
| 530 | No usable vehicle or scheduled vehicle exists to leave source location |
| 531 | No usable vehicle or scheduled vehicle exists to reach destination loc. |
| 540 | Stop has initial status "Executed" |
| 541 | Stop has initial status "Fixed" |
| 542 | Stop has initial status "Assignment Fixed" |
| 543 | Stop has status "Fixed" due to propagation |
| 544 | Stop has status "Assignment Fixed" due to propagation |
| 545 | Stop has status "Fixed" since outside planning horizon |
| 550 | No penalty costs defined for non-delivery |
| 551 | No valid route that fulfills all constraints |
| 552 | No valid connection to transshipment location that must be used |
| 553 | No valid direct connection between locations for given stage |
| 554 | No valid connection from source location |
| 555 | No valid route that contains all given stages |
| 556 | No valid connection from transshipment location that must be used |
| 558 | No valid connection to destination location |
| 559 | No valid route due to max. number of transshipment locations |
| 561 | Direct shipment not possible; freight unit might not be delivered |
| 562 | Time boundaries outside planning horizon |
| 563 | Departure and/or arrival times are invalid for direct shipment |
| 564 | Departure time of the direct shipment is outside the acceptable FU dates |
| 565 | Arrival time of the direct shipment is outside the acceptable FU dates |
| 566 | Load dimension is 0; loading does not consume any capacity |
| 569 | Requirement doc. can't be planned; acceptable times are incompatible |
| 570 | No valid route due to stage constraints |
| 572 | No valid route due to transportation mode constraints |
| 575 | No valid route due to shipping type |
| 577 | No valid route due to capacities |
| 579 | No valid route due to acceptable dates |
| 581 | No valid route that fulfills all constraints; skip detailed analysis |
| 582 | FU has too many ADR points to be transported on provided veh res/veh type |
| 584 | No valid route due to default route constraints |
| 586 | No valid route since only default routes are considered |
| 588 | No valid route due to incomp. betw. FU and vehicle, schedule, or booking |
| 589 | No valid route due to incompatibilities between FU and transshipment loc. |
| 590 | No valid route due to incompatibilities between FU and compartment |
| 591 | No valid route due to incomp. between vehicle res. and stay at location |
| 592 | No valid route due to incomp. betw. vehicle res. and (un-)loading at loc. |
| 593 | No valid route since resulting FO would exceed maximum distance/duration |
| 594 | No valid route since no booking exists for the given equipment type |
| 595 | No valid route due to loading/unl. restrictions of provided veh res/type |
| 596 | No valid route due to package dimensions |
| 597 | No valid route due to incompatibilities between FU and carrier |
| 598 | No valid route due to incomp. between carrier and stay at location |
| 600 | You have not entered a requested start date; earliness not penalized |
| 601 | You have not entered a requested end date; lateness not penalized |
| 602 | Acceptable date is outside the planning horizon |
| 603 | Requested date is before the planning horizon |
| 650 | Stage constraint for transportation mode lost due to rough planning |
| 651 | Stage constraint for means of transport lost due to rough planning |
| 652 | Stage constraint for vehicle lost due to rough planning |
| 653 | Stage constraint for vessel lost due to rough planning |
| 654 | Stage constraint for voyage lost due to rough planning |
| 655 | Stage constraint for flight code lost due to rough planning |
| 660 | No transportation mode defined for direct shipment option |
| 670 | Freight unit has more than the maximum of ADR points that are allowed |
| 680 | Requirement document not planned because of minimum utilization |
| 681 | Req. document not planned: costs for delivery higher than non-del. costs |
| 682 | Requirement document not planned due to lack of vehicle resources |
| 683 | Requirement document not planned due to time constraints |
| 684 | Req. document not planned due to time constr. or lack of veh. resources |
| 701 | You can create bookings only for port-to-port schedules |
| 702 | Schedule referenced by freight order does not exist |
| 703 | FO has relevant inbound stop without preceding relevant outbound stop |
| 704 | FO has relevant inbound stop with preceding relevant inbound stop |
| 705 | FO has relevant outbound stop with preceding relevant inbound stop |
| 706 | FO has relevant outbound stop with preceding relevant outbound stop |
| 707 | Enter a start time of departure that is before the end time |
| 708 | Departure cannot have more than one freight order |
| 709 | Departure and related freight order have different categories |
| 710 | Booking related to departure must have two relevant stops |
| 711 | Port-to-port FO related to departure must have two relevant stops |
| 712 | Departure and related freight order have different shipping types |
| 713 | Freight order for departure has fewer than two relevant stops |
| 714 | Freight order or booking differs from related departure |
| 715 | Freight order related to departure has unallowed capacity |
| 716 | Inconsistency; departure and related freight orders will be ignored |
| 717 | Booking related to departure has inconsistent capacity |
| 718 | Booking related to dep. has infinite capacity; processed as freight order |
| 719 | Schedule for non-port-to-port bookings must have two relevant stops |
| 720 | Booking item for schedule must not have compartments |
| 721 | Wait time of booking or schedule at location exceeds planning horizon |
| 722 | First allowed stop for departure is beyond available stops |
| 723 | First allowed stop for departure is beyond schedule availability |
| 724 | All stops for departure are beyond schedule availability |
| 725 | Departure time differs from time of first stop |
| 726 | Enter a departure time |
| 727 | Type mismatch between resource/equi. type and MTr; res/equi. type ignored |
| 728 | Type mismatch between schedule or booking and MTr; MTr ignored |
| 729 | Define a transportation mode for the booking |
| 730 | Downtime found for a subcontracted vehicle; such downtimes are ignored |
| 731 | Downtime found for a multiresource; such downtimes are ignored |
| 732 | Vehicle with depot can't be used; max. number of intermediate stops is 0 |
| 800 | Freight order has initial status "Fixed" due to context determination |
| 801 | Freight order has at least one stop with initial status "Partially Fixed" |
| 802 | Freight order has status "Fixed" due to propagation |
| 803 | FO has at least one stop with status "Partially Fixed" due to propagation |
| 804 | Incremental freight order with subcontracted vehicle is not supported |
| 810 | Max. no. of stops of FO with status "Partially Fixed" cannot be fulfilled |
| 811 | Max. distance of FO with status "Partially Fixed" cannot be fulfilled |
| 812 | Max. duration of FO with status "Partially Fixed" cannot be fulfilled |
| 813 | FO has inconsistent stages where no transportation demands can be added |
| 814 | Utilization of freight order is below the threshold for min. utilization |
| 815 | Tour &1 contains a local item for a passive vehicle resource |