SAP ABAP Message Class /MRSS/OPT_VSR (VSR Optimizer Messages)
Basic Data
Hierarchy
☛
MRSS_NW (Software Component) SAP Multiresource Scheduling for SAP Net
⤷ PM-WOC-MO (Application Component) Maintenance Orders
⤷ /MRSS/OPT (Package) Multi Resource Scheduling: Optimizer
⤷ PM-WOC-MO (Application Component) Maintenance Orders
⤷ /MRSS/OPT (Package) Multi Resource Scheduling: Optimizer
Attributes
Message class | /MRSS/OPT_VSR | |
Short Description | VSR Optimizer Messages | |
Changed On | 20141109 | |
Last Changed At | 161323 |
Messages
# | Message | Message Short Text | Documentation status | Authorization check |
---|---|---|---|---|
1 | 000 | Internal error: &1 &2 &3 &4 | The short text describes the object sufficiently | |
2 | 001 | The optimizer version does not support the application version | The short text describes the object sufficiently | |
3 | 002 | Canceled due to lack of memory space; current memory consumption: &1 MB | The short text describes the object sufficiently | |
4 | 003 | Time limit reached without improvement | The short text describes the object sufficiently | |
5 | 004 | Optimizer has set validity period to &1 seconds | The short text describes the object sufficiently | |
6 | 100 | Initial solution ignored | The short text describes the object sufficiently | |
7 | 101 | Freight unit &1 exceeds maximum goods wait time in location &2 | The short text describes the object sufficiently | |
8 | 102 | Resource &1 has an unauthorized journey scheduled from &2 to &3 | The short text describes the object sufficiently | |
9 | 103 | Resource &1 has an unauthorized scheduled freight unit &2 | The short text describes the object sufficiently | |
10 | 104 | Resource &1 is planned without permission | The short text describes the object sufficiently | |
11 | 105 | Freight unit &2 does not meet minimum goods wait time in location &2 | The short text describes the object sufficiently | |
12 | 106 | Travel from &2 to &3 (&1) not scheduled for &4 due to fixed assignments | Space: object requires documentation | |
13 | 107 | Max. allowed time exceeded (is: &1, limit: &2); resource &3 ignored | The short text describes the object sufficiently | |
14 | 108 | Max. allowed distance exceeded (is: &1, limit: &2); resource &3 ignored | The short text describes the object sufficiently | |
15 | 109 | Max. allowed no. of assignments exceeded (is: &1, limit: &2); &3 ignored | The short text describes the object sufficiently | |
16 | 110 | Initial solution with costs &2 read | The short text describes the object sufficiently | |
17 | 111 | Initial solution is more expensive than not meeting all demands (costs &) | The short text describes the object sufficiently | |
18 | 200 | Error while importing data | The short text describes the object sufficiently | |
19 | 201 | Error while setting up model | The short text describes the object sufficiently | |
20 | 202 | Error while writing back solution | The short text describes the object sufficiently | |
21 | 210 | Freight unit &2 has multiple compatible transshipment locations | The short text describes the object sufficiently | |
22 | 300 | Cannot execute demands | The short text describes the object sufficiently | |
23 | 301 | Cannot plan demands in planning horizon | The short text describes the object sufficiently | |
24 | 302 | No demands forwarded to optimizer | The short text describes the object sufficiently | |
25 | 303 | Cannot plan any of the demands | The short text describes the object sufficiently | |
26 | 304 | Demand &1 remains unplanned | The short text describes the object sufficiently | |
27 | 305 | Cannot restore initial plan; &1 freight units not delivered | The short text describes the object sufficiently | |
28 | 310 | Best solution is to not meet all demands | The short text describes the object sufficiently | |
29 | 320 | Runtime is too short; could not determine initial solution | The short text describes the object sufficiently | |
30 | 330 | No resources transferred to optimizer | The short text describes the object sufficiently | |
31 | 331 | No distances (distance matrix) transferred to optimizer | The short text describes the object sufficiently | |
32 | 400 | Resource &1 is not required | The short text describes the object sufficiently | |
33 | 401 | Scheduled vehicle &1 (departure time &2) is not required | The short text describes the object sufficiently | |
34 | 402 | Cannot use resource &1 | The short text describes the object sufficiently | |
35 | 403 | Means of transport &2 cannot be used (scheduled vehicle) | The short text describes the object sufficiently | |
36 | 404 | Stop sequence &1 cannot be used | The short text describes the object sufficiently | |
37 | 410 | Demand &1 is not planned and results in costs to the amount of &2 | The short text describes the object sufficiently | |
38 | 411 | &1 unplannable demands result in costs to a total amount of &2 | The short text describes the object sufficiently | |
39 | 412 | &1 of &2 demands planned | The short text describes the object sufficiently | |
40 | 413 | Freight unit &1 is too large for the resources; non-delivery costs: &2 | The short text describes the object sufficiently | |
41 | 414 | Demand &1 does not have non-fulfillment costs | The short text describes the object sufficiently | |
42 | 415 | Freight unit &1 in fixed area cannot be delivered in full; costs: &2 | The short text describes the object sufficiently | |
43 | 416 | FU &1 does not have transportation lanes to/from location &2; costs: &3 | The short text describes the object sufficiently | |
44 | 417 | FP &1 cannot be planned; no non-delivery costs | The short text describes the object sufficiently | |
45 | 418 | &1 demands were additionally fixed for the optimization | The short text describes the object sufficiently | |
46 | 419 | Demand &1 cannot be planned due to predecessor &2 | The short text describes the object sufficiently | |
47 | 420 | Demand &1 is part of a group that cannot be planned | The short text describes the object sufficiently | |
48 | 421 | Demand &1 cannot be planned in the optimization horizon (&2) | The short text describes the object sufficiently |
History
Last changed on/by | 20141109 | SAP | |
SAP Release Created in | 610 |