/SCMTMS/VSS_ENGINE - Messages from scheduler engine
The following messages are stored in message class /SCMTMS/VSS_ENGINE: Messages from scheduler engine.
It is part of development package /SCMTMS/PLN_VSS_CMN_IL in software component TM-PLN-MP. This development package consists of objects that can be grouped under "Scheduling Common Elements - Inner Layer".
It is part of development package /SCMTMS/PLN_VSS_CMN_IL in software component TM-PLN-MP. This development package consists of objects that can be grouped under "Scheduling Common Elements - Inner Layer".
Message Nr ▲ | Message Text |
|---|---|
| 000 | Scheduling failed |
| 030 | Un-/loading of doc. &2 can't be scheduled after its earliest start date |
| 031 | Un-/loading of doc. &2 can't be scheduled before its latest start date |
| 032 | Un-/loading of doc. &2 can't be scheduled after its earliest end date |
| 033 | Un-/loading of doc. &2 can't be scheduled before its latest end date |
| 034 | Un-/load. of doc. &2 can't be sched. between earliest start and end date |
| 035 | Un-/loading of doc. &2 can't be sched. between latest start and end date |
| 036 | Un-/loading of document &2 with maximum durations can't be scheduled |
| 037 | No free time slot for un-/loading of freight document &2 at location &3 |
| 038 | The loading or unloading of document &2 takes too long |
| 040 | Transport from &2 to &3 can't be scheduled after its earliest start date |
| 041 | Transport from &2 to &3 can't be scheduled before its latest start date |
| 042 | Transport from &2 to &3 can't be scheduled after its earliest end date |
| 043 | Transport from &2 to &3 can't be scheduled before its latest end date |
| 044 | Transp. from &2 to &3 can't be sched. between earliest start and end date |
| 045 | Transp. from &2 to &3 can't be sched. between latest start and end date |
| 046 | Transport of freight document &2 with max. durations cannot be scheduled |
| 047 | No free time slot available for transp. of freight doc. &1 from &2 to &3 |
| 048 | The transport of freight document &1 takes too long |
| 049 | Accptbl load times of req. docs. of freight order &2 at &3 do not overlap |
| 050 | Un-/coupling of TU &2 can't be scheduled after its earliest start date |
| 051 | Un-/coupling of TU &2 can't be scheduled before its latest start date |
| 052 | Un-/coupling of TU &2 can't be scheduled after its earliest end date |
| 053 | Un-/coupling of TU &2 can't be scheduled before its latest end date |
| 054 | Un-/coupling of TU &2 can't be sched. betw. earliest start and end date |
| 055 | Un-/coupling of TU &2 can't be sched. between latest start and end date |
| 056 | Max. goods wait time &1 at location &2 exceeded |
| 057 | No free time slot available for un-/coupling of transportation unit &2 |
| 058 | The un-/coupling of transportation unit &2 takes too long |
| 060 | Internal error while creating model |
| 061 | The sorting of the freight orders or transportation units is inconsistent |
| 062 | It is not possible to meet the requested dates for freight unit &2 at &3 |
| 063 | It is not possible to meet the requested dates for trailer unit &2 at &3 |
| 064 | Acceptable times of req. docs. assigned to &2 at &3 are incompatible |
| 111 | (Un)loading of doc. &2 at &3; can't meet the acc. dates for req. docs. |
| 777 | Available memory on optimization server is low (available: &1%) |