266063

FUNCTIONAL OVERVIEW

Client Requirement

Currently user can not change the Trip Status from COMPLETED if trip has missing date/time. This request is to remove the validation MTS does and allow user to change the Trip Status any time he wants. All the User Group should be able to change the trip status.

Solution

Due to the ‘CL’ messages sent from the HHT updating the status to COMPLETED without validating date and time entries it is possible to COMPLETE a trip without setting these values.

To solve this issue super-users will be allowed change the status from COMPLETED to ACCEPTED (only). These users will be able to make these changes in both the TRIP_SUM screen and the TRIPDTL screen.

Changes will also be required to the following two database triggers:

TAU_SCH_TRIP_LABEL_OUTBOUND 
TAU_SCH_TRIP_HHT_OUTBOUND

These triggers produce records that are sent to the HHT. These will be amended so as to not fire if the previous status was COMPLETED.

Scope

These changes will be applied to system version 10.4.8 on SARTST and once approved SARPRD.

FUNCTIONAL DESCRIPTION

Current Functionality

Currently it is not possible to revert a trip from status COMPLETED to ACCEPTED in MTS as this was not a required process. When trying to do this in the TRIP screens (TRIP_PLAN, TRIPSUM and TRIPDTL) the following error is shown:

New Functionality

The new functionality to allow trip status change from COMPLETED to ACCEPTED requires amendments to the following:

TRM package amendments

When changing the status in TRIP_PLAN and TRIPSUM via the right-click and ‘Set Status’ option, or via the drop down list and ‘Set Status’ button in TRIPDTL, function SET_TRIP_STATUS in package TRM.sql is called. The status you are trying to set the trip to is passed in and compared to the current status of the trip. Currently there is no functionality around setting the status of a trip to ACCEPTED from COMPLETED so the user will get an error as detailed earlier informing them that the trip status change is not possible. The function SET_TRIP_STATUS will be amended to include the possibility of setting a trip status from COMPLETED to ACCEPTED only. Below highlighted in yellow is the piece of code that will be included within the section where a user is trying to set the status of a trip to ACCEPTED to incorporate the ability to revert from COMPLETED. After status reverted, the normal functionality within SET_TRIP_STATUS will complete.

Trigger Updates

Currently triggers TAU_SCH_TRIP_HHT_OUTBOUND and TAU_SCH_TRIP_LABEL_OUTBOUND both fire when a trip status is updated to ACCEPTED. As the new functionality will allow a user to set a trips status from COMPLETED to ACCEPTED, we do not want these triggers to fire in these instances. Therefore, a check will be done in each trigger to ensure the old status of the trip is not COMPLETED before firing the code within the trigger.

After a user changes the status from COMPLETED to ACCEPTED, this will be reflected in the ‘Audit’ tab in TRIP_PLAN, TRIPSUM and TRIPDTL via the current functionality in trigger TI_SCH_TRIP_AUDIT. The user will be able to see who reverted the status and when. Sample ‘Audit’ shown below:

References

Ref No	Document Title & ID	Version	Date
EST-266063	AA-7SCDFK Change Trip Status if Date-Time missing v1.0.doc	1.0	17/06/09

Document History

Version	Date	Status	Reason	Initials
0.1	07/07/09	Draft	Initial version	LAD
1.0	09/07/09	Issue	Reviewed and Issue	MJC

Authorised By

Matt Crisford

Development Manager

Suk Sandhu

TMSCC MTS Product Manager

Copyright OBS Logistics © 2009

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