/SAPAPO/CDPSOPT - DPS Optimizer Messages
The following messages are stored in message class /SAPAPO/CDPSOPT: DPS 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 | Unknown error |
| 001 | &1 |
| 002 | Termination cause unknown |
| 003 | Floating point error |
| 004 | Illegal instruction |
| 005 | Segmentation error |
| 006 | Termination requested |
| 010 | Inconsistency in the optimization data model |
| 011 | Inconsistency in internal optimizer script |
| 012 | Internal error during optimization |
| 013 | Internal error in module supervisor |
| 014 | Log file could not be opened or written |
| 015 | Termination During Data Loading from liveCache |
| 016 | Incompatible COM object version |
| 017 | No campaign profile could be determined |
| 018 | There are additional error messages of the same type |
| 019 | Canceled Due to Insufficient Memory. Current Memory Consumption: &1 MB |
| 020 | Preprocessing not possible |
| 021 | Solution contains possible early orders |
| 022 | Mode costs may be too high |
| 023 | Start of optimization should fall within the optimization horizon |
| 024 | The start horizon should be before the end horizon |
| 025 | Data repair deactivated |
| 026 | Termination when writing data to liveCache |
| 027 | Mixing relative and absolute time values can cause problems |
| 028 | Invalid date: Value should be between 01.01.1901 and 31.12.9999 |
| 029 | Start of optimized plan is in the past |
| 040 | Invalid selection name in database. Entry has been cleared. |
| 041 | Invalid selection name. |
| 042 | No masterdata selection name has been specified. Switching to automatic. |
| 050 | RFC connection error |
| 051 | Remote function call (RFC) unsuccessful |
| 060 | Optimizer and COM Object are not compatible |
| 099 | Calling &1 for not supported application &2, only supporting &3 |
| 100 | Not enough memory |
| 101 | Resource &1 does not have a calendar |
| 102 | Resource &1 is unknown |
| 103 | Type of time relationship between &1 and &2 is unknown |
| 104 | Operation segment &1 is unknown |
| 105 | Calendar of resource &1 is unknown |
| 106 | Entry (&1, &2) in calendar is not valid |
| 107 | Error setting up the connection to SAP liveCache: &1 |
| 108 | No orders have been chosen |
| 109 | No resources selected |
| 110 | No orders chosen that can be planned by optimization |
| 111 | Scheduling could not adopt the solution |
| 112 | Scheduling has scheduled some activities differently |
| 113 | The newly created order &1 contains fixed activities |
| 115 | Resource &1: Calendar is not complete |
| 116 | Resource &1: Calendar start is too late |
| 117 | This is called from PP Optimizer |
| 150 | Maximum length of pegging relationship ignored between order &1 and &2 |
| 151 | Maximum interval of the internal order relationship in order &1 ignored |
| 152 | Maximum interval of relationship between order &1 and order &2 ignored |
| 153 | Pegging relationship ignored because it causes a cycle |
| 154 | Relationship in order &1 ignored because it causes a cycle |
| 155 | Relationship between order &1 and &2 ignored because it causes a cycle |
| 200 | Serious error in planning algorithm |
| 201 | There is no solution to the problem |
| 202 | No solution can be found for the problem |
| 203 | Resource constraint has a negative value |
| 204 | &1: Not available |
| 205 | Runtime chosen is possibly too short |
| 206 | Runtime chosen too short |
| 207 | Backward scheduling does not require the entire runtime specified |
| 208 | Invalid amount of resource constraints for resource &1 |
| 209 | Invalid definition of a time relationship between &1 and &2 |
| 210 | Invalid definition of a constraint at resource &1 |
| 211 | Invalid calendar &1 |
| 212 | &1: Invalid calendar |
| 213 | Activity &1 has multiple direct successors |
| 214 | Activity &1 has multiple direct predecessors |
| 215 | Link between modi with undefined limits |
| 216 | Duplicate link between activitites &1 and &2 exists |
| 217 | Mode &1 not valid |
| 218 | Activity &1 not valid |
| 219 | Resource &1 not valid |
| 220 | Activity/mode &1 not valid |
| 221 | Time relationship &1 not valid |
| 222 | Setup activity &1 not valid |
| 223 | Invalid optimizer internal mode &1 |
| 224 | Setup matrix &1 not valid |
| 225 | Order &1 not valid |
| 226 | Invalid operation &1 |
| 227 | Locked activity chain &1 not valid |
| 228 | Locked activity chain &1 has incompatible mode &2 |
| 229 | Locked activity chain &1:Primary resource is not a single-activity resrc. |
| 230 | Locked activity chain &1: Activities do not have the same setup ID |
| 231 | Activity &2 in locked activity chain &1 has a setup activity |
| 232 | Successor for activity &2 in locked activity chain &1 is not valid |
| 233 | Activity &2 in locked activity chain &1 does not have a setup ID |
| 234 | Mode &3 of actvy &2 in locked actvy chain &1 does not have a primary res. |
| 235 | There is no successor for activity &2 in locked activity chain &1 |
| 236 | Predecessor for activity &2 in locked activity chain &1 is not valid |
| 237 | Time Decomposition disabled |
| 240 | Mode &2 for activity &1: Primary resource is not a single activity resrc. |
| 241 | Order &1: Multiple operations on bottleneck resources |
| 242 | Activity &1 and order &2: Remove time dependencies |
| 243 | Activity &1 has more than one mode compatible link in the setup acts |
| 244 | Optimizer internal mode &1 is not allocated to an activity |
| 245 | Activity &1: Requirements/avail. date &2 lies before optimization horizon |
| 246 | Campaign optimization disabled |
| 247 | Order &1: Requirements/avail.date &2 lies before optimization horizon |
| 248 | No relationship defined between act. &1 and setup act. &2 |
| 250 | Error in context data consistency rule &1 |
| 251 | Activity &1 does not have a mode that can be selected |
| 252 | Value range for activity or mode &1 is not valid |
| 253 | Wrong start value range [&1, &2] |
| 254 | Wrong end value range [&1, &2] |
| 255 | &1: Activity &2 has no planning area |
| 256 | Order &1: mode has duration of 0 |
| 257 | Activity &1 does not have a mode |
| 258 | Activity/mode &1 starts outside of the optimization horizon |
| 259 | Activity/mode &1 finishes outside of the optimization horizon |
| 260 | Activity/mode &1 has a net duration outside of the optimization horizon |
| 261 | Planning period |
| 262 | Calendar &1 is empty |
| 263 | Calendar &1 has missing areas (gaps in the time stream) |
| 264 | Activity &1 is its own successor |
| 265 | Order &1: Mode linkage cannot be fulfilled |
| 266 | Order &1: Setup activity has continuous consumption |
| 267 | Order &1: continuous load not valid |
| 268 | Activity &1 has time relationships that are not valid |
| 269 | Order &2 requires &1 more than once |
| 270 | Activity &1 exceeds the capacity of resource &2 in mode &3 |
| 271 | Activity &1 has multiple predecessors |
| 272 | Activitiy &1 has multiple successors |
| 273 | Activitiy &1 has multiple successor |
| 274 | Activity &1 has multiple predecessor |
| 275 | Mode &2 of activity &1 has a variable net duration |
| 276 | Time relationship between activity &1 and &2 has an undefined interval |
| 277 | Activities &1 and &2 are cyclic with relationship type &3 |
| 278 | Activity &1 and &2 are cyclic with time relationship type &3 via modi |
| 279 | Mode &1 has undefined or no capacity requirements |
| 280 | Relationship of &1 fixed activities cannot be processed |
| 281 | Pegging relationship for fixed activity &1 cannot be processed |
| 282 | Transportation order &1 has several setup keys |
| 283 | |
| 284 | Setup matrix &1 is empty |
| 285 | &2: Dependent requirement on resource &1 |
| 286 | Mode &2 of activity &1 has multiple modes in the assigned setup activity |
| 287 | Mode &2 of activity &1 has no mode in the assigned setup activity |
| 288 | Mode &2 of activity &1 has no mode in the assigned setup activity |
| 289 | Activity &1 is linked to the setup activity by more than one relationship |
| 290 | Activity &1: Only a finish-start time relatnshp to setup activity allowed |
| 291 | Activity &1: Relationship to setup activity not valid |
| 292 | Activity &1 is not linked to your setup activity |
| 293 | Activity &1 is linked to your setup activity via the modi |
| 294 | Mode &2 of setup activity &1 uses more than one resource |
| 295 | Mode &2 of setup activity &1 does not use a resource |
| 296 | Mode &2 of setup activity &1: Primary resource has no setup matrix |
| 297 | Order &2: &1 is not a single-activity resource |
| 298 | Mode &2 of setup activity &1 does not have a primary resource |
| 299 | Mode &2 of activity &1: Primary resource has no setup matrix |
| 300 | Mode &1 needs &2 from resource &3 with maximum capacity &4 |
| 301 | Mode &1 has negative demand &2 at resource &3 |
| 302 | Invalid rel. between setup activity and production act. has been deleted |
| 303 | Invalid relationship between two activities has been deleted |
| 304 | Fixed setup activity &1 is not supported |
| 305 | Mode &1 of activity &2 has no primary resource |
| 306 | Activity &1 refers to a primary resource &2 with no re-setup |
| 307 | Setup activity &1 cannot setup resource &2 |
| 308 | Order &1: Material flow restriction is not valid |
| 310 | &1: Setup activity has predecessor(s) in locked activity chain |
| 311 | &1: Activity has multiple predecessors in locked activity chain |
| 312 | &1: Activity has multiple successors in locked activity chain |
| 315 | Start of optimization horizon cannot be processed |
| 316 | There are negative capacity values specified in calendar from resource &1 |
| 317 | More than 1 relationship with resource network indicator for activity &1 |
| 318 | Setup activity &1 has modes with identical primary resource |
| 319 | Order &2: Resource &1 consumption is zero |
| 320 | Mode &1 contains the same resource twice |
| 321 | Resource &1: Demand from order &2 does not equal 1 |
| 322 | &1: Setup activity &2 without setup key |
| 323 | Setup matrix &1 contains setup cost entries with negative values |
| 324 | No setup matrix assigned to resource &1 |
| 325 | Order &1: No modes in the setup activity have a setup matrix |
| 326 | Order &1: Setup activity has modes that have no setup matrix |
| 327 | Order &1: Activity cannot be scheduled, would violate maximum intervals |
| 330 | A pegging relationship is linking order &1 to itself |
| 331 | Continuous usage of storage resource mapped to discrete usage |
| 350 | Order &1 in more than one campaign |
| 351 | There is no valid start time for order &1; optimization terminating |
| 352 | Campaign optimization: Only one activity/locked activity chain per order |
| 353 | Resource &1 is not a single resource |
| 358 | Constraint &1 for resource &2 cannot be evaluated |
| 359 | &1: Order &2 generates capacity overload |
| 360 | Resource &1: Undefined initial load |
| 361 | Resource &1: Initial load is outside of the capacity range |
| 362 | Resource &1: Storage characteristic can not be considered |
| 363 | Resource &1: Fill level change will be added |
| 364 | Resource &1: Too many material receipts |
| 365 | Resource &1: Too few material receipts |
| 366 | Resource &1: Storage property causes unsolvable problems |
| 367 | No product can be uniquely assigned to resource &1 |
| 368 | Maximum earliness of product receipts is not considered |
| 370 | Resource &1: Bucket resources can not be planned |
| 371 | Activity in order &1 cannot be moved; no solution is possible |
| 372 | Storage characteristics cannot be considered; see long text |
| 373 | Latest start or end times as hard constraints |
| 374 | Order &1 ignored: Mode selection is not possible |
| 380 | Activities &1 and &2 are linked using mode linkage w/o associated modes |
| 381 | SOS &1 for product &2 can't be used because it contains cycles |
| 382 | Product &1 can't be exploded because no valid SOS exists |
| 383 | SOS &1 can't be used because at least one activity has no valid modes |
| 384 | Mode &1 of SOS &2 can't be used |
| 385 | SOS &1 for product &2 can't be used because of inconsistency |
| 500 | 500 - 600 Help texts |
| 501 | Constraint propagation |
| 502 | Genetic algorithm |
| 510 | Maximum runtime |
| 511 | Additional information on optimization run available |
| 520 | Minimizing the total lead time |
| 521 | Minimizing the setup times |
| 522 | Minimizing the setup costs |
| 523 | Minimizing the maximum delay |
| 524 | Minimizing the average delay |
| 525 | Weighting for total costs |
| 601 | Number of resources: &1, number of which selected: &2 |
| 602 | Number of activities for optimization: &1 |
| 603 | Number of selected activities: &1 |
| 604 | Number of activities after preprocessing: &1 |
| 605 | Number of activities scheduled before preprocessing: &1 |
| 606 | Number of activities deallocated before preprocessing: &1 |
| 607 | Number of activities scheduled after preprocessing: &1 |
| 608 | Number of activities deallocated after preprocessing: &1 |
| 609 | You have only selected deallocated activities |
| 610 | Number of scheduled activities after optimization: &1 |
| 611 | Number of deallocated activities after optimization: &1 |
| 612 | Number of deleted orders: &1 |
| 613 | Number of newly created orders: &1 |
| 700 | Resource capacity is too high |
| 701 | There are too many modes in one block of activities |
| 702 | Start interval of &1 changed in order to save the non-valid solution |
| 703 | Finish interval of &1 changed in order to save the non-valid solution |
| 704 | Change gross time interval of &1 in order to save the invalid solution |
| 705 | &1 '&2' unknown, optimizer uses &3 |
| 706 | Unknown key word &1 will be ignored |
| 707 | Operation of order &1 deallocated on resource &2 after end of horizon |
| 708 | Mode &1 does not have an earliest start time |
| 709 | Mode &1 does not have a latest start time |
| 710 | Activity &1 has a due date that cannot be met |
| 711 | Order &1 can only be scheduled with a delay |
| 712 | Order &1 in dependency cycle &2 |
| 713 | Storage characteristic not considered with deallocation funcitonality |
| 714 | Bottleneck optimization may not be used with deallocation functionality |
| 715 | Campaigns used with deallocation functionality |
| 716 | Optimization must schedule an operation of order &1 |
| 717 | Number of activities deallocated and expedited in horizon: &1 |
| 718 | Activity &1 rescheduled for another date |
| 719 | Activity &1 not rescheduled |
| 720 | Bucket capacity not considered during bottleneck optimization. |
| 723 | Activity &1 has mode with a duration of zero |
| 724 | Resource &1 required but is not selected |
| 725 | Resource &1 not in propagation range |
| 726 | Optimization profile does not contain mode costs |
| 727 | Control &1 cannot be displayed |
| 730 | Resource &1 has not been chosen from a current mode |
| 731 | Resource &1 has not been chosen from a non-current mode |
| 732 | Order &1: Related to a non-selected resource |
| 733 | Critical Activity &3 %: Order &1 on &2 |
| 748 | Capacity of resource &1 changed to zero |
| 749 | There is a possible overload of resource capacity &1 |
| 750 | Propagator: Internal problem with time relationship &1. |
| 752 | Activity &1 at resource &2: Constraint without capacity requirement |
| 753 | Activity &1 at storage resource &2: Condition without capacity requiremt |
| 754 | Constraint engine warning: &1 - &2 (error code &3) |
| 755 | Inconsistent data for mode &2 in activity &1 |
| 756 | Mode linkage for order &1 cannot be processed |
| 757 | All activities are fixed |
| 758 | Planned delivery time for order &1 not reached |
| 759 | Order &1 cannot be scheduled on time |
| 777 | Available memory on optimization server is low (available: &1%) |
| 800 | Generate optimization system |
| 801 | Search for initial solution |
| 802 | Trying to improve solution |
| 803 | Genetic algorithm has been started |
| 804 | Constraint progagator has been started |
| 805 | Genetic algorithm has finished |
| 806 | Constraint propagator has finished |
| 807 | Read parameters |
| 808 | Topological sorting |
| 809 | Scheduling |
| 810 | Termination: Reached end of runtime |
| 811 | Cancelled by user |
| 812 | Checking consistency of data |
| 813 | Optimization run finished |
| 814 | Log is being created |
| 815 | Backwards scheduling started |
| 816 | Backwards scheduling finished |
| 817 | Campaign optimization started |
| 818 | Campaign optimization finished |
| 819 | Campaign optimization is being prepared |
| 820 | Campaign optimization is being completed |
| 821 | Multi-agent optimization started |
| 822 | Optimization run ended with no solution |
| 823 | Multi-agent optimization complete |
| 825 | Choose at least one bottleneck resource |
| 826 | Select orders that can be planned for campaign optimization |
| 827 | Order is allowed to contain one operation max. |
| 828 | Operation contains too many activities |
| 830 | Relax-and-Resolve optimizer begun |
| 831 | Relax-and-Resolve optimizer ended |
| 832 | Time decomposition begun |
| 833 | Time decomposition ended |
| 834 | Load data from liveCache |
| 835 | Write data back to liveCache |
| 836 | Compact scheduling started |
| 837 | Compact scheduling ended |
| 838 | Preprocessing for order creation started |
| 839 | Preprocessing for order creation ended |
| 850 | Capacity change active |
| 851 | Start of optimization horizon: &1 &2 |
| 852 | End of optimization horizon: &1 &2 |
| 853 | Start of optimized schedule: &1 &2 |
| 854 | Result of optimization run: |
| 855 | Result of campaign optimization: |
| 856 | Result of plan completion: |
| 857 | Lead time: &1 |
| 858 | Setup time: &1 |
| 859 | Setup costs: &1 |
| 860 | Maximum delay: &1 |
| 861 | Total delays: &1 |
| 862 | Mode cost total: &1 |
| 863 | Storage costs: &1 |
| 864 | Delay costs: &1 |
| 865 | Maximum runtime: &1 |
| 866 | Runtime distribution |
| 867 | Initial solution: &1 % |
| 868 | Initial solution improvement: &1 % |
| 869 | Backwards planning: &1 % |
| 870 | Campaign optimization: &1 % |
| 871 | Planning version: &1 |
| 872 | Weighted total costs:&1 |
| 873 | New mode is used to transfer explanation data |
| 874 | Default mode is used to transfer explanation data |