275114
275114 - NA-83KSLE/ Debrief (POD) Interface from MTS
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
At West Thurrock, Unilever require both the actual delivery date/time together with any early/late delivery reason and in the case of discrepancies the actual rejection line(s) together with refusal reason. The Order Receipt flow will be sent twice, once upon receipt of the order and then at the point of despatched i.e. in case of any differences during picking. This will be handled by the EVENT_TYPE field i.e ORD and LOA. At the point of debrief, the actual delivery date/time together with any early/late delivery reason and any refusal needs to be sent back to DAI. It is proposed that this will be via a POD flow so based on EVENT_TYPE DEL in MTS. MTS debrief at line level currently only works via LOTS but initially the West Thurrock operation will not be live with LOTS so screens need to be amended to be able to do manually via the screen with the option to move to LOTS at a later date.
Solution
Inbound EDI (Generic) Changes
A new entry will be added to the EDI tab on the IMPORTS_EXEC screen for the order update flow. This flow will use the existing code in INT_XML_OUT to process the order updates and update the quantities as required. It is expected that the inbound files will have an EVENT_TYPE of LOA or MAR to distinguish them for the new order files.
Outbound EDI (Generic) Changes
The outbound trip files already contain the actual depart and arrive times as well as the delivery quantity. The files do not currently have the non conformity reason codes; however the XSD does contain the necessary fields. The outbound trip message will be altered to include the reason codes.
The outbound message will be triggered twice; firstly when the actual arrive and depart times are entered for the delivery stop. At this point the file will be sent containing the actual times, but no actual quantities. The trigger for this message will be an update of the actual times where the stop is a delivery. This option will be controlled by the EDI Maintenance / Param functionality a new trigger will be available.
A second outbound message will be triggered when the actual delivered quantity is entered, this will trigger another message in the same format but this time containing the actual quantities. The trigger for this message will be an update of the actual delivered quantity. This option will be controlled by the EDI Maintenance / Param functionality a new trigger will be available.
Trip Debrief Changes
A new tab will be added to the Trip Debrief screen. The tab will be next to the current Order Debrief tab and will contain the order item information. When accessed the item information for the order that has the current focus will be displayed. The new tab will be similar in structure to the order items tab on the orders screen and will contain the following information:
Identifier Product Aka Code Item Description Factor Lifts Stack Ordered To Deliver Delivered Diff Weight Volume
The tab will contain a button that will apply the actuals automatically for all items on the specific order. The main orders tab will also contain a new button to apply all the item actuals for all orders on a trip. This will be separate to the apply actuals button that is already in place on the tab.
Scope
This change will be applied to system version 10.6.
FUNCTIONAL DESCRIPTION
Imports Screen
A new entry will be added to the EDI section of the Imports Exec screen. This will provide the parameters that will control the inbound flow for the order updates.
The file format field indicates the prefix for the filename that will be processed with this flow. This will contain LOA which will indicate that the file is an update to an order rather than the input of a new order.
The directory parameters (Deliver, Archive, Failures) will contain the folders which will receive the files and the folders which will contain the processed files.
Outbound File
The XSD for the Outbound trip messages already contains the fields to show the Non conformance reason codes.
The outbound file will be changed to include the reason codes for the orders on the trip. The message will be triggered when the trip is set to status ‘Completed’ as this will allow all debriefs to have been entered.
The outbound files already contain the actual depart and arrive times so no change is required to include these.
There will be two new triggers for the outbound file.
- When the actual arrive and depart times are entered for a delivery stop a file will be created. This will contain the actual times entered but no actual quantities. This message will be triggered when the actual times are entered on a stop that is a delivery. The sending of this file will be controlled by that parameter functionality on the EDI Maintenance form.
- When the actual delivered quantity is entered a file will be created. This will contain the actual times and the actual quantities. This message will be triggered when the actual delivered quantity is entered. The sending of this file will be controlled by that parameter functionality on the EDI Maintenance form.
Trip Debrief
A new tab will be added to the debrief screen after the existing Order Debrief tab. The New tab will be call Order Items Debrief and will contain the order item level information.
When moving to this tab the order item information for the current order ( on the order debrief tab) will be shown.
The information on the Order Items tab will be similar in structure to the data shown on the orders screen (see below).
The information displayed will be Identifier Product AKA code Item Description Factor Lifts Stack Ordered To Deliver Delivered Diff Weight Volume
The data will be taken from the SCH_ORD_ITEMS table.
The order items tab will contain a button that will apply the actuals for all the items on the tab. This will work in a similar way to the ‘Apply Actuals’ button on the main order details tab.
A button will also be applied to the Order Details tab that will apply the item actuals for all of the orders on the trip.
NB this will be a separate button to the existing ‘Apply Actuals’ button.
REFERENCES
Not Available
DOCUMENT HISTORY
| Initial version | ||||
| Reviewed and Issued |
AUTHORISED BY
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
