267850: Difference between revisions
Middletong (talk | contribs) (New page: =267850 - KL-7UEBAR/ Location Screen Validation= Copyright OBS Logistics © 2010 The information contained herein is the property of OBS Logistics and is supplied without liability for ...) |
Middletong (talk | contribs) No edit summary |
||
| Line 9: | Line 9: | ||
==Client Requirement== | ==Client Requirement== | ||
Within MTS there is a locations screen – this needs tighter control to stop users entering data in different formats and duplicating records as they can’t find the correct code. | |||
*Take access away from general users. Limit to 4-6 people throughout consumer | |||
*Add further controls on system to ensure data entering in correct format | |||
The id is made up of first characters of Company name and Town of Delivery ie ASDALUTT | |||
The id name is Town_Company Name_Postcode | |||
Currently there are no limitations to this. | |||
In the main body of the screen, users need to type in address, town, postcode, country. | |||
Requirement for Change | |||
The Name to be added into this section | |||
The Post Code to have control to ensure that only valid postcodes are entered and in the correct format. | |||
The name of the ID, then can be automatically populated from the data already received. | |||
(Note this still relies on users putting the Town in the town field etc) | |||
By putting the correct postcode the Longitude and Latitude should automatically be populated – for Country GB, do not allow user Long Lat update | |||
Requirement to Tidy the Current data | |||
Any duplicates can be checked, once have customer account numbers linked to the correct ID. the duplicates be made inactive. | |||
Create a list of Delivery points which have not had deliveries in past two years, these need to be made inactive also. | |||
Requirement for Change | |||
A parameter on system should change any delivery locations that have not been visited in the last xxx days to automatically go to inactive. | |||
Revision as of 12:26, 1 March 2010
267850 - KL-7UEBAR/ Location Screen Validation
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
Functiona Overview
Client Requirement
Within MTS there is a locations screen – this needs tighter control to stop users entering data in different formats and duplicating records as they can’t find the correct code.
- Take access away from general users. Limit to 4-6 people throughout consumer
- Add further controls on system to ensure data entering in correct format
The id is made up of first characters of Company name and Town of Delivery ie ASDALUTT The id name is Town_Company Name_Postcode Currently there are no limitations to this. In the main body of the screen, users need to type in address, town, postcode, country.
Requirement for Change The Name to be added into this section The Post Code to have control to ensure that only valid postcodes are entered and in the correct format. The name of the ID, then can be automatically populated from the data already received. (Note this still relies on users putting the Town in the town field etc) By putting the correct postcode the Longitude and Latitude should automatically be populated – for Country GB, do not allow user Long Lat update
Requirement to Tidy the Current data Any duplicates can be checked, once have customer account numbers linked to the correct ID. the duplicates be made inactive. Create a list of Delivery points which have not had deliveries in past two years, these need to be made inactive also.
Requirement for Change A parameter on system should change any delivery locations that have not been visited in the last xxx days to automatically go to inactive.
Solution
Scope
Data
Functional Description
References
| EST-259410 PA-7MKDYG CN Loading Schedule Report Changes v1.doc |
Document History
| Initial version | ||||
| Reviewed and Issued |
Authorised By
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
