ER CTMS 041-028: Difference between revisions
No edit summary |
m (Text replacement - "[[Category:{{#var:System}} ER]]↵</noinclude>" to "[[Category:{{#var:System}} ER]]Category:ER CTMS 041 </noinclude>") |
||
| (One intermediate revision by one other user not shown) | |||
| Line 87: | Line 87: | ||
|The trips will not be set to status 'COMPLETED' for a load update. | |The trips will not be set to status 'COMPLETED' for a load update. | ||
|} | |} | ||
'''Note:''' CTL & EPOD changes are required with this release. | |||
<noinclude> | <noinclude> | ||
[[Category:{{#var:System}} ER]] | [[Category:{{#var:System}} ER]][[Category:ER CTMS 041]] | ||
</noinclude> | </noinclude> | ||
Latest revision as of 09:57, 14 July 2025
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER041-028
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks |
|---|---|---|---|---|---|---|
| DATA_ADM_SYSTEM_PARAM_261979.sql | Data Script | 1.1 | 261979 | 440451-26 | 2 | Updates from EPOD:
A new system parameter called 'EPOD_COMPLETE_ON_LOAD_UPDATE' can be configured by cost centre to enable the trips to be set to status 'COMPLETED' for a load update. The system parameter 'EPOD_COMPLETE_ON_RTD' should be set to 'N' when 'EPOD_COMPLETE_ON_LOAD_UPDATE' is set to 'Y'. The trip status will not be updated to 'COMPLETED' except when updating loads when 'EPOD_COMPLETE_ON_LOAD_UPDATE' is set to 'Y'.
The orders will be added to the trips for delivery. The driver, carrier and vehicle will be validated that they are active and for their combination. Any advised trips for the order must have the same driver, carrier and vehicle for the order to be added to that trip. The trips will have a shift for the driver if the order is being delivered within that shift and the driver does not have a planned diary exception for that time (e.g. for annual leave or sickness). These trips will have start and end times for the times for the shift. The trips will have a diary exception for the driver outside of the shift for the driver (e.g. overtime). These trips will have start and end times for the times for the diary exception. If an order is being planned outside of a shift for the driver and without a diary exception (e.g. overtime), the trip will have start and end times based on the standard distance and time calculations based on the time windows for the order. |
| DATA_ADM_SYSTEM_PARAM_CONFIG_261979.sql | Data Script | 1.1 | " | " | " | " |
| DP_EPOD_WEB_SERVICE.sql | EPOD Web Service Database Package | 1.137 | " | " | " | " |
| TRM.sql | Trip Management Database Package | 5.204 | " | " | " | " |
| New Parameters | |||
|---|---|---|---|
| Parameter Name | Config Level | Setting Value | Result |
| EPOD_COMPLETE_ON_LOAD_UPDATE | COST_CENTRE | Y | The trips will be set to status 'COMPLETED' for a load update. |
| EPOD_COMPLETE_ON_LOAD_UPDATE | COST_CENTRE | N | The trips will not be set to status 'COMPLETED' for a load update. |
Note: CTL & EPOD changes are required with this release.
