272867
272867 - NW-7ZEMQY/ Add additional fields to the block configuration in the Trip Manipulation and Trip Planning forms
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
Add additional fields to the block configuration in the Trip Manipulation and Trip Planning forms.
In the Trip Stops block add the TO_LOC_TOWN and TO_LOC_POSTCODE if the stop is of type DL or CL and the FROM_LOC_TOWN and FROM_LOC_POSTCODE if the stop is of type SU or PK. These should be inserted after the LOCATION_STR.
In the Unscheduled Orders block add the same fields after the FROM_LOC_NAME and TO_LOC_NAME respectively.
Solution
The order well / unscheduled orders block will be enhanced to allow four additional fields to be selected from the configuration screen. The four fields will be FROM_LOC_TOWN, FROM_LOC_POSTCODE (these being sequenced after the existing field FROM_LOC_NAME) and TO_LOC_TOWN, TO_LOC_POSTCODE (these being sequenced after the existing field TO_LOC_NAME). The four extra columns will be display only and will be derived from the ‘from’ and ‘to’ location codes on each order shown in the block.
The trip stop block will be enhanced to allow two additional fields to be selected from the configuration screen. The two new fields will be LOCATION_TOWN and LOCATION_POSTCODE (these being sequenced after the existing field LOCATION_STR). The two extra columns will be display only and will be derived from the location code associated with the trip stop. There is no need to differentiate between the trip stop type (SU or PK or DL or CL) because each stop has a location code and by associated and reference to GEO_LOCATIONS a town and postcode.
This is an urgent development and due to the straight forward nature of the enhancement, no functional specification will be produced. Sign-off will be based on this estimate description.
Scope
N/A
Data
N/A
FUNCTIONAL DESCRIPTION
N/A
DOCUMENT HISTORY
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
