285419
DHL C-TMS
Balance of Debrief Unilever
FUNCTIONAL SPECIFICATION - 10.6
01/07/2011 - 1.0
Reference: FS 285419 KM-8DAN4M
Client Requirement
Balance of Debrief Unilever outstanding points as a result of rio KM-8A6DYZ and KM-8A6EC
If “Time Reason” is set to Mandatory it is not looking at the “Delivery Threshold”. In particular – Early. If it is early we want to just default the reason “early” and not have to enter a reason. The interface already handles this but currently by setting “Time Reason” to Mandatory it is over-riding the rule in the interface.
If “Line Item” Reason is set to Mandatory, an un-necessary “OK” is required for each time If “Line Item” Reason is not Mandatory, items are off but set to “order and line debrief”, when you come to “save” it still makes you press “OK” twice. Once for order and one for lines.
The simple answer is the rules are still applicable and to raise the popup when the Time Variance would normally display Red. However, the customer KPI tolerance allows x mins and initially operations would only want to capture reason if outside tolerance so ideally I think if we had a parameter defined by customer for when it should raise the Late Reason popup e.g. Unilever we could set it to 30 mins so if Time Variance is Red and it is greater than 30 mins a popup box is raised.
In terms of when we raise the popup, usually we debrief times separately to quantities so should be at stop level.
Solution
If the delivery time is between the order delivery windows (including any variance for the customer) then the time variance field shows green and a reason code is not be required. If the actual arrival is outside of the order delivery windows (including any variance) then the time variance field shows red and a reason code is required (providing the customer is set up to enter reason codes).
Currently there is one parameter against the customer called mandatory time reason code. This controls whether a reason code is required for late or early arrivals. A new parameter will be added called mandatory early reason code.
If this new parameter is set then if the actual arrival time is earlier than the early del time of the order, the variance field will show as red and a default reason code of ‘EARLY’ will be added to SCH_ORD_LATE_REASON for the order. This will prevent the user having to enter a reason code manually.
There are currently messages that pop up when a discrepancy is entered on the Item and Line level quantities. These messages inform the user that a non conformance must be entered. This will be changed to remove the messages and just show the Non conformance reason pop up window without displaying the message, as users did not want to press ‘Ok’ each time.
N.B. If non conformance is not required (as set in the customer parameters) the existing message informing the user that they can enter non conformance reasons if required will still display.
Scope
This change will be applied to system version 10.6
Set-up
Pre-requisites
N/A
Menu Structure
N/A
Data
N/A
Implementation Advice
Any one of the above tick boxes must be set an early threshold must be entered for Customers requiring this functionality.
Functional Description
Currently in the Customer Maintenance screen, there is a Debrief tab which controls how orders for the customer should be de-briefed.
There is a check box labelled ‘Time Reason Code’ and if this is checked for a customer, any order that is delivered later that the order window will require a reason code.
If the checkbox has been selected , the user will enter a threshold time for early and late deliveries. The values are always entered in minutes. If an order is delivered LATE after the late threshold time is added, the user is automatically informed that the delivery is late and is taken to the Time reasons screen.
However, if an order is delivered EARLY, after the early threshold time is added, the user is not currently directed to the Time reasons screen.
The functionality will be changed so that when an order is delivered earlier than the delivery window including the early threshold time, a record will be automatically created in the reason table for the order. The record will be based on the following data:
| SCHED_NAME | The schedule the trip is on |
| OMS_REF | The oms_ref of the order delivered early |
| TRIP_ID | The Trip_id of the trip being debriefed |
| LATE_CODE | ‘EARLY’ |
| COMMENTS | ‘Order was delivered earlier than the threshold time’ |
The variance field will display as red, to indicate that the order was delivered outside of the delivery window, including threshold times.
Example
Delivery Window:30/06/2011 15:30 – 17:45
Early Threshold time30 MINUTES
If the order is delivered before 30/06/2011 15:00 an ‘EARLY’ non conformance record will be automatically generated against the order.
If the user enters quantities at item or line level which are different to the planned quantities, they are informed that they will be forced to enter a non-conformance before being forwarded to the Non Conformance screen.
The functionality will be changed so that the user is forced to the Non conformance screen without the message being displayed first. This functionality will apply to all levels of debrief, ensuring the user does not have to select Ok before the non-conformance screen is displayed.
If the customer has not been set up for non-conformance , where all the check boxes for the de-brief options are unchecked (see next screen shot), messages will still be displayed informing the user that they can create non-conformance .
Any attempt to suppress the non-conformance messages must be based on at least one of the above check boxes being checked.
Table Updates Required
Insert into SCH_LATE_CODES (LATE_CODE, DESCRIPTION)
VALUES (‘EARLY’,’Order was delivered Earlier than threshold time’);
References
| EST- 285419 KM-8DAN4M Balance of Debrief Unilever v3.0 | |||
Glossary
| C-TMS | Calidus TMS |
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
