273522
273522 - NW-823H5U/ Extend the Location Name Field
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
Extend the Location Name field length to 50 characters
Extend the length of the Location Name field to 50 characters and carry out any associated investigatory checks to ensure that this will not cause issues within the database, forms or reports. If any reports need to be amended they should be identified between estimate and specification so that the specification quote can be submitted with these amendments included if required. The actual appending or suffixing of the Bill to / Ship to codes and Post Codes will take place in CIM and will be passed through the interface.
Solution
MTS will be modified to extend the maximum size of the LOCATION_NAME from 35 to 50 characters.
The TripOrder XSD will be modified accordingly extending the field ADDRESS_NAME from 35 to 50 characters. This will allow the interface between CIM and MTS to carry longer address names (and these then get loaded into location names in MTS). This new version XSD will need to be applied by ESI and utilised by CIM for all integration file creation and validation when sending data to or receiving data from MTS that use the OBS TripOrder XSD.
The Microlise journeySchedule message has siteName as 50 characters already so there should be no impact on the Microlise interface.
The paragon export file from MTS is formatted as CSV so extending the location names has no impact on the output file generation; however, the project team should check that larger location names will not be a problem for Paragon generally.
An impact analysis will be done to identify the full extent of database object and code changes, both forms and reports. A contingency of 2 days analysis and 2 days development changes has been included. This might need to be revised based on the results of the impact analysis at quotation stage of the RIO process.
An initial search of the database objects indicates the following tables are affected – GEO_LOCATION, INT_XML_ORD_HEADER, ORD_CUSTOMER_EMPTIES and GEO_LOCATION_UPLOAD. The main packages will need to change namely GEO, TRIP and TRM. Additionally 15 package bodies, 2 triggers and 1 view and the procedure location_export will all need review and possible change. The number of forms and reports affected is unknown and will be established during the mentioned impact analysis.
Scope
This change will be applied to system version 10.5 on HCRTST and once approved HCRPRD.
FUNCTIONAL DESCRIPTION
The following database and front end changes will be needed to allow 50 characters to be entered and displayed in the Location Name field. The field is used extensively through out the C-TMS system as a display item to allow users to determine which location id they should choose, where trips/orders are travelling between etc.
Table Changes
| TABLE NAME | DESCRIPTION OF CHANGE REQUIRED |
|---|---|
| GEO_LOCATION | Alter LOCATION_NAME from 35 to 50 |
| GEO_LOCATION_UPLOAD | Alter LOCATION_NAME from 35 to 50 |
| INT_XML_ORD_HEADER | Alter LOCATION_NAME_DEL from 35 to 50 |
| INT_XML_ORD_HEADER | Alter LOCATION_NAME_DEP from 35 to 50 |
| JR_ORIG_LOCATION | Alter LOCATION_NAME from 35 to 50 |
| LOCATION | Alter NAME from 35 to 50 |
Form Changes
| FORM NAME | VERSION | SCALE OF CHANGE REQUIRED |
|---|---|---|
| ACC_CTRL | 2.35 | Minor |
| BDM | 2.37 | Significant |
| BOOKINGS | 2.27 | Significant |
| CAR_TRIP_MAN | 1.30 | Significant |
| CONTRACT | 2.41 | Minor |
| CREATE_TRIP | 1.8 | Minor |
| CUST_COST | 2.41 | Minor |
| DEBRIEF_DRVR | 1.6 | Minor |
| INT_ERR | 1.39 | Minor |
| LOCATION | 2.62 | Significant |
| NETWORK | 1.10 | Minor |
| ORD_ENTRY_TARGET | 2.27 | Minor |
| ORDERS | 2.119 | Significant |
| ORDTEMPL | 2.41 | Significant |
| PRODUCT | 2.14 | Significant |
| PURCH_ORD | 1.7 | Minor |
| ROUTES_EXEC | 2.21 | Minor |
| ROUTES_MAINT | 2.20 | Minor |
| SLOT_USAGE | 2.9 | Minor |
| TRACKING | 2.58 | Minor |
| TRIP_PLAN | 1.69 | Significant |
| TRIPSUM | 2.162 | Significant |
| WHS_MAINT | 2.10 | Minor |
9 – Significant Form Changes; 14 – Minor Form Changes
Report Changes
No Report changes have been considered; where Location Name is displayed on reports it will be truncated to 35 Chars.
Should specific reports require modification, to allow the full 50 chars to be displayed; these should be advised to OBS and will incur an approximate cost of 0.25 days per report.
Package Changes
| PACKAGE NAME | VERSION | DESRIPTION OF CHANGE REQUIRED |
|---|---|---|
| IMP | 5.18 | In FUNCTION Process_Location, code extracts values from the import file for a length of 35 characters. This will need to be altered to 50. NB Import Format is affected and existing templates will need to be amended. |
| GEO | 5.6 | In FUNCTION Get_Loc_Name_Id, code extracts LOCATION_NAME from GEO_LOCATION for a length of 35 characters into v_retchar. This will need to be altered to 50. |
| MSG_INSTRUCTOR | 5.8 | In FUNCTION p_trip_b, code extracts LOCATION_NAME from GEO_LOCATION for a length of 35 characters into v_3 and v_4 for the source and destination. This will need to be altered to 50. |
| TRIP | 5.1 | In FUNCTION Previous_Depot_Stop_Name, extracts LOCATION_NAME from GEO_LOCATION for a length of 35 characters into v_ret_val. This will need to be altered to 50. |
XSD Changes
The TripOrder XSD will be updated and issued to reflect the increase from 35 to 50 characters wherever Location Names are used.
REFERENCES
| EST-273522 NW-823H5U Extend the Location Name Field Length.doc |
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed with DJM and Issued | ||||
| Included changes for packages GEO, MSG_INSTRUCTOR and TRIP in section 3.4 |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
