/SCMTMS/LSO - Load Space Optimization messages
The following messages are stored in message class /SCMTMS/LSO: Load Space Optimization messages.
It is part of development package /SCMTMS/PLN_ENGINES_LSO in software component TM-PLN. This development package consists of objects that can be grouped under "Planning: Engines - Load Space Optimization".
It is part of development package /SCMTMS/PLN_ENGINES_LSO in software component TM-PLN. This development package consists of objects that can be grouped under "Planning: Engines - Load Space Optimization".
Message Nr ▲ | Message Text |
---|---|
000 | Internal error: &1 &2 &3 &4 |
001 | Canceled due to insufficient memory; current memory consumption: &1 MB |
002 | &1 of &2 items can be loaded |
003 | &1 of &2 freight units consolidated into &3 capacity documents |
004 | &1 of &2 freight units consolidated into &3 freight orders |
005 | &1 of &2 freight units consolidated into &3 container units |
006 | &1 of &2 freight units consolidated into &3 trailer units |
007 | None of the freight units can be consolidated |
008 | Invalid combination resource &1; load planning failed |
010 | Freight unit &1 is incompatible with all resources or equipment types |
011 | Package unit &1 is incompatible with all resources or equipment types |
020 | Load optimization failed due to an RCCF engine error |
025 | No optimization server available for &1 |
050 | No gross weight maintained for item &1; not considered in load planning |
051 | No load planning relevant documents selected; load planning is skipped |
052 | No measures maintained for item &1; not considered in load planning |
053 | No load planning relevant items selected; load planning is skipped |
054 | Loading sequence not supported; load planning is skipped |
055 | Multi-stage freight units not supported; freight unit &1 is skipped |
056 | Freight units consolidated in &1 groups |
057 | No resource or equipment types selected; load planning is skipped |
058 | Load consolidation for combination resources is not supported |
059 | Item &1 has a quantity greater than one; not considered in load planning |
099 | Calling &1 for application &2; only application &3 is supported |
100 | Error while importing data; create cust. message on comp. TM-PLN-LP-OPP |
101 | Error while creating model; create cust. message on comp. TM-PLN-LP-OPP |
102 | Error while writing back solution |
150 | Error while starting parallel task &1 for load planning |
151 | No free work process for task &1; check settings and retry |
152 | Error while starting task &1; &2 |
153 | Error while saving task &1 |
154 | Error while receiving results from task &1; &2 |
155 | Load planning performed for &1 of &2 freight documents |
156 | Load planning settings &1 not found |
157 | Load planning is triggered asynchronously for document &1 |
200 | Axle load for vehicle &1 cannot be calculated |
201 | Tare weight of vehicle resource or vehicle type &1 adjusted |
202 | Max. gross weight of veh. res./veh. type &1 adjusted to its tare weight |
203 | Trailing weight of vehicle resource or vehicle type &1 adjusted |
204 | Gross weight of vehicle combination &1 adjusted |
205 | Maximum weight on king pin of vehicle resource or vehicle type &1 |
206 | Split deck position of vehicle resource or vehicle type &1 set to zero |
207 | Axle load of veh. &1 not computed; enter connector dist. in master data |
250 | Package &1 incompatible with all resources or equipment types |
260 | Freight unit &1 contains packages that are incompatible with each other |
270 | Resource or equipment type &1: section type not supported by optimizer |
271 | Resource or equipment type &1: split deck type not supported by optimizer |
272 | Res/equi. type &1: horiz. split deck section must cover compl. cargo body |
273 | Resource or equip. type &1: vertical sections not supported by optimizer |
274 | Resource or equip. type &1: split deck weight not supported by optimizer |
275 | Res. or equip. type &1: removable split deck not supported by optimizer |
276 | Resource or equipment type &1: loading pattern not supported by optimizer |
277 | Heterogeneous package lengths not supported by optimizer |
278 | Stackable packages not supported by optimizer |
279 | Scenario not supported by optimizer |
280 | LSO explanation tool: error while initializing |
281 | LSO explanation tool: error while saving the input |
282 | LSO explanation tool: error while saving the result |
283 | LSO explanation tool: error while saving the RCC GUID |
300 | *************** Validation messages ****************** |
301 | Enter a valid equipment group for rule &1 |
302 | Enter a load planning rule |
303 | Enter a valid equipment type for rule &1 |
304 | Load planning rule &1 has already been defined |
305 | Load planning rule &1 and load planning rule &2 are mutually exclusive |
306 | Enter a unit of measure for rule &1 with dimension &2 |
307 | Load planning rule &1 does not exist; enter a valid load planning rule |
308 | Enter a priority for load planning rule &1 |
309 | Enter a unit of measure for load planning rule &1 |
310 | Enter a percentage between 0 and 100 for load planning rule &1 |
311 | Enter a valid load planning strategy |
312 | Enter an alphabetical value for rule &1 |
313 | Equip. type pattern of rule &1 does not match any equip. type in system |
314 | Enter a valid load consolidation strategy |
315 | Vehicle resource can�t be inserted; it�s part of a combination resource |
400 | Not enough load space for item &1 of freight document &2 on vehicle &3 |
500 | Load plan cleared |
501 | Item &1 has load plan item status "Finalized"; action skipped |
502 | Action skipped because load plan has been finalized |
503 | Action skipped due to warehouse processing status for some items |
600 | Planning not possible; no vehicle passed to the optimizer |
601 | Only one vehicle is allowed; other vehicles are ignored |
602 | Maximum gross weight of vehicle &1 is zero; changed to default max value |
603 | Empty weight of vehicle &1 is higher than its maximum weight |
604 | |
605 | |
606 | |
607 | |
608 | |
609 | |
610 | |
620 | Planning not possible; no package passed to the optimizer |
621 | Density of package &1 is too low; check master data |
622 | Package &1 doesn't fit into any vehicle; entry is ignored |
777 | Available memory on optimization server is low (available: &1%) |
999 | Calling &1 for not supported application &2, only supporting &3 |