270873
270873 - NW-7XBFJW/ Empty Visits from Paragon
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
Switch on functionality to enable the Paragon XML file to create stops of type VT in MTS, these should be Trip Stops that do not have an associated Order.
Solution
New functionality required to enable ‘VT’ to be passed in the <STOP_TYPE> tab below the <STOP_DETAIL> structure in the standard TripOrder (2.3) xsd from Paragon to MTS when creating/updating trips.
NB) The code will by default also be available for 2.4 and 2.5 versions of the xsd.
The procedure XML_TRIPS_FROM_PARAGON within the package PAR needs changing to allow this new value ‘VT’ to be received as a valid value.
The code will also need changing so that if a stop type of ‘VT’ is provided then as well as creating the trip stop record as now an additional dummy SCH_HAULAGE_ACTIVITY record is also created with an activity name of ‘Visit’ and a blank OMS Reference which should then ensure that the trip stop with no real orders will not automatically get deleted as part of the standard trip validation.
Scope
This change will be applied to system version 10.6.
FUNCTIONAL DESCRIPTION
Within the existing 2.3 version of the TripOrder XSD then is already a tab called <STOP_TYPE> within the <STOP_DETAIL> structure.
Currently this is allowed to be one off ‘SU’,’PK’,’DL’ or ‘CL’.
A new value ‘VT’ is going to be allowed and this will be populated by the interface from Paragon to MTS for creating/updating trips information for stops without any orders assigned.
The procedure XML_TRIPS_FROM_PARAGON within the package PAR needs changing to allow this extra value as currently this would be rejected with invalid stop type.
NB) The XSD has had to be changed slightly in order to allow for this extra value. This may be needed by ESI in order for them to be allowed to create the new value in the XSD.
An additional change to the same procedure is to automatically create a dummy SCH_HAULAGE_ACTIVITY (SHA) record with an ACTIVITY_NAME value of ‘Visit’. The OMS Reference will be left blank.
This will ensure that the trip validation routine run later in the process does not delete the stop as it now does have a (SHA) record.
REFERENCES
Not Available
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
