294448
DHL C-TMS
Change CN Trip Sheet Stationary Report
FUNCTIONAL SPECIFICATION - 10.7
19/12/11 - 1.0
Reference: FS 294448 ID-8P3G36
FUNCTIONAL OVERVIEW
Client Requirement
Currently the “Driver Trip Sheet” used by DHL Consumer, called “CN Trip Sheet” displays an IVR PIN code against all of the drops. This would be correct if all of the products sent on a drop are actually for a LOTS-enabled client and hence an IVR-enabled client. Unfortunately across a single multi-client site, or more importantly across a Pallet Network, different drops on a single trip may actually have a product that is, or is not, LOTS-enabled. Thus, if a driver were to action the transport event using IVR, all of these non-LOTS-enabled drops would fail the pin validation, thus leaving the drivers frustrated as to when, or when not, to use the IVR process. See the attached MS Word requirement document that outlines how we think the removal of IVR PIN codes for non-LOTS-enabled drops would work.
Solution
The ‘CN Trip Sheet’ will be changed to assess whether the customer of the transport orders on the drops has LOTS installed and thus whether the ‘IVR PIN’ information will be displayed in the report.
The ‘IVR PIN’ information will be displayed at the start-up (stop type ‘SU’) and close-down (‘CL’) drops if the trip contains any transport orders for customers with LOTS installed, but the individual drops (‘PK’ and ‘DL’) will be assessed at the trip stop for the presence of any transport orders for customers with LOTS installed.
Scope
This change will be applied to system version 10.7
SET-UP
Implementation Advice
The new version of the report may be applied without any setup changes required.
FUNCTIONAL DESCRIPTION
The ‘CN Trip Sheet’ (i.e. ‘TRIP_SHEET.rep’) will be changed to include the IVR PIN information based on certain conditions.
The report will be run using its existing selection criteria, for example:
The layout of the report will not be changed as the IVR PIN information may, or may not, be displayed at present.
The IVR PIN information is only required for customers that have LOTS installed, therefore, the information is only required at a trip stop if there is a transport order for such a customer present.
The IVR PIN information will display the stop ID after the ‘IVR PIN’ text under the following conditions:
1. The stop type is a start-up (i.e. ‘SU’) or a close-down (i.e. ‘CL’) and the trip contains any transport orders for customers with LOTS installed. 2. The stop type is a pick-up (i.e. ‘PK’) or a delivery (i.e. ‘DL’) and the trip stop contains any transport orders for customers with LOTS installed.
For condition 1, the function ‘CF_STOP_PIDFORMULA’ for field ‘F_SU_PID’ will be changed to assess whether the stop type is ‘SU’ and the trip contains any transport orders for customers with LOTS installed.
For condition 2, the function ‘CF_PIDFORMULA’ for field ‘F_STOP_PID’ will be changed to assess whether the stop type is ‘PK’ or ‘DL’ and the trip stop contains any transport orders for customers with LOTS installed; or whether the stop type is ‘CL’ and the trip contains any transport orders for customers with LOTS installed.
For example,
For the example above, if drop 2 did not contain any LOTS-enabled orders, then the ‘IVR PIN’ text would be excluded from the report and replaced with spaces for that stop only:
If the trip were to contain a close-down stop then it would include the ‘IVR PIN’ text because the trip contains transport orders for customers with LOTS installed, although the stop itself may not contain a transport order because all stock was delivered during the trip.
The same logic applies to the start-up stop because it does not include any transport orders until the pick-up at drop 2.
If the start-up or close-down stop were to contain transport orders for customers without LOTS installed but there is at least one transport order on another stop on the trip, the ‘IVR PIN’ text would be included for the start-up or close-down stops.
REFERENCES
| EST-294448 ID-8P3G36 Change CN Trip Sheet Stationery Report v1.0.doc |
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
