CTMS 11.0 ER023-087: Difference between revisions
No edit summary |
No edit summary |
||
| Line 16: | Line 16: | ||
|The scheduling engine has been changed to enable various scenarios to create and updated trips for the fixed routes as the orders are scheduled at different stages for the trips based on the network solution. | |The scheduling engine has been changed to enable various scenarios to create and updated trips for the fixed routes as the orders are scheduled at different stages for the trips based on the network solution. | ||
Primarily, the changes relate to trips via the Park locations. | Primarily, the changes relate to trips via the Park locations. | ||
Changes include ensuring that the cut-off times are assessed in the format MI:SS (i.e. nn:nn when entered as n:nn). | Changes include ensuring that the cut-off times are assessed in the format MI:SS (i.e. nn:nn when entered as n:nn). | ||
Ensuring that the collection and delivery stops are created using the route sequence number for when trip stops exist with the same route sequence number (which may be for collection, delivery or both activities) or stops do not exist. | Ensuring that the collection and delivery stops are created using the route sequence number for when trip stops exist with the same route sequence number (which may be for collection, delivery or both activities) or stops do not exist. | ||
Ensuring that the first stop on the trip sets its planned arrival and departure times to the appropriate cut-off and start times of the fixed route itself or the fixed route stop. This includes when empty locations are deleted and then recreated as a hub location for the carrier of the trip. | Ensuring that the first stop on the trip sets its planned arrival and departure times to the appropriate cut-off and start times of the fixed route itself or the fixed route stop. This includes when empty locations are deleted and then recreated as a hub location for the carrier of the trip. | ||
Ensuring that the orders are transported to the local depot from the Park location for next day delivery when they are not being delivered on a radial route via the Park on the same day. | Ensuring that the orders are transported to the local depot from the Park location for next day delivery when they are not being delivered on a radial route via the Park on the same day. | ||
|Michelle | |Michelle | ||
}} | }} | ||
Latest revision as of 14:37, 25 April 2017
EMERGENCY RELEASE - CTMS 11.0
RELNOTE ER023-087
| Module | Program Name | Ver | Call/Iss | Client Ref | Pr'ty | Remarks | Reporter |
| DP_SCHEDULING_ENGINE.sql | Scheduling Engine Package | 5.102 | 342129 | - | 2 | The scheduling engine has been changed to enable various scenarios to create and updated trips for the fixed routes as the orders are scheduled at different stages for the trips based on the network solution.
Primarily, the changes relate to trips via the Park locations. Changes include ensuring that the cut-off times are assessed in the format MI:SS (i.e. nn:nn when entered as n:nn). Ensuring that the collection and delivery stops are created using the route sequence number for when trip stops exist with the same route sequence number (which may be for collection, delivery or both activities) or stops do not exist. Ensuring that the first stop on the trip sets its planned arrival and departure times to the appropriate cut-off and start times of the fixed route itself or the fixed route stop. This includes when empty locations are deleted and then recreated as a hub location for the carrier of the trip. Ensuring that the orders are transported to the local depot from the Park location for next day delivery when they are not being delivered on a radial route via the Park on the same day. |
Michelle |
