265781
265781 - MW-7SHBN2/ Order tracking change trip status
Copyright OBS Logistics © 2010
The information contained herein is the property of OBS Logistics and is supplied without liability for errors or omissions. No part may be reproduced or used except as authorised by contract or other written permission. The copyright and foregoing restriction on reproduction and use extend to all media in which the information may be embodied
FUNCTIONAL OVERVIEW
Client Requirement
We are looking on implementing consolidation across all customers - especially Tesco and Iggesund, who will have multiple orders from the same to and from locations within the same trip. When this function is switched on and the trip is tracked, the status of the trip is not triggered and normal - ie when a collection is confirmed and POC is triggered the status should go to Enroute and the same for the last POD the trip status should change to Completed - currently this does not work within the tracking screen.
Solution
The automatic setting of status will be brought in line with the current TRIPDTL functionality
After discussions a further requirement was raised for the access control on the screen to be changed. Currently the user can only view the stops that are assigned to their profile as a based at location. This means the delivery locations are often not visible as users will not have all the locations assigned.
To fix this the Owning depot of the trip will be used to restrict which users can see the details. This will bring the screen in line with the other trip screens, and allow the users to see any trips (including both load and unload legs) that are relevant to their based at location.
N.B. the estimate time for this RIO includes time taken to investigate the current functionality and also discussions with Mark Wilson about the RIO.
Scope
This change will be applied to system version 10.6.
FUNCTIONAL DESCRIPTION
The current functionality on the order tracking screen (Tracking) restricts the trips and stops visible to the user based on the BASED_AT location set up for the user. The based at location is compared to the location id of the stops on the trip and if it matches then that stop is visible to the user.
This functionality means users can only see stops that are at the BASED_AT location (s) set up for their username. This will result in users only being able to see on part of a trip for a particular order (either Collection or deliver stop).
The access control will be changed to restrict trips to those containing orders belonging to the user’s sched group. The order’s group will be compared to the users group (taken from the user parameter); if they match the corresponding trip will be visible.
The access control will also be changed to restrict trips based on the Owning Depot of the trip. This will be compared against the users Based At locations. Users will be able to view the details of trips were the owning depot is present in their based at options. If no based at location is set up for a user, this code will be ignored.
Currently the trip status is changed to En-route when the first actual time is entered for the trip, this will not be changed.
For POC’s the line of code IF TRM.Set_Actual( 'ORD_POC', :STOP_LIST.oms_Ref, v_value, v_errmsg, :STOP_LIST.sched_name, :STOP_LIST.trip_id ) THEN
Will be changed to IF TRM.Set_Actual( 'ORD_POC', :STOP_LIST.oms_Ref, NULL, v_errmsg, :STOP_LIST.sched_name, :STOP_LIST.trip_id ) THEN
This will prevent the trip being set to completed when the POC is set.
The system registry TRM_SET_TO_COMPLETED will be set to POC / POD, this will force the trip status to be changed to Completed when the last POD is entered for a Trip.
REFERENCES
Not Available
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued | ||||
| Updated totals |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
