ER CTMS 044-008: Difference between revisions
No edit summary |
m (Text replacement - "[[Category:{{#var:System}} ER]]↵" to "[[Category:{{#var:System}} ER]]Category:ER CTMS 044") |
||
Line 55: | Line 55: | ||
<noinclude> | <noinclude> | ||
[[Category:{{#var:System}} ER]] | [[Category:{{#var:System}} ER]][[Category:ER CTMS 044]]</noinclude> | ||
</noinclude> |
Latest revision as of 09:50, 14 July 2025
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER044-008
Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
---|---|---|---|---|---|---|
DP_3PL_SCHED.sql | 3PL Scheduling Engine Database Package | 5.5 | 00474273 | 19873 | 2 | The orders are assigned by the 3PL scheduling engine to trip stops based on their activity at those stops.
The orders will be loaded or unloaded at a stop. DP_CTMS_IMPORT is modified the error message where it said DEP/DEL address cannot be NULL when ext_ref is not found be reported with a better message. Corrected the logic which caused unique constraint violated error. The API for the orders will prevent an attempt to create duplicate locations. |
DP_CTMS_IMPORT | Import Package | 5.28 | " | " | " | " |
Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
---|---|---|---|---|---|---|
DP_3PL_SCHED.sql | 3PL Scheduling Engine Database Package | 5.6 | 00478672 | 19874 | 2 | 1. Any depot that is listed in the system parameter 'AUTO_SCHED_INACTIVE_DEPOTS' will not be processing its orders in the 3PL scheduling engine.
These orders will be marked for manual scheduling and they will have an audit message 'The depot is inactive for scheduling, order cannot be scheduled'. 2. If a drop number cannot be derived for the location for the route, then an order for that location will not be scheduled. A default drop number cannot be applied for the position of the trip stop. These orders will be marked for manual scheduling and they will have an audit message 'Cannot pre-plan no drop number available'. |