268520
268520 - JB-7V5JP2 Unilever Interface
Copyright OBS Logistics © 2009
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
West Thurrock is having a new WMS implemented (DAI Matflo system). DHL will re-use and modify slightly the message specs used in the BEIG development as that was a DAI WMS messaging into MTS.
Requirements are to send a T_ORD via ESI into MTS and for MTS to send a T_LOAD to the WMS. This will be over ftp and we would like the same functionality as BEIG , push messaging for the T_LOAD , and the changes made to cater for the cross docking. T_LOADS should only be sent where the loading depot is DHLUNWTK.
Solution
A new flow will be set up in MTS. The flow will be controlled by a new database job that will run at set intervals. Inbound files will be placed (by ESI) in the agreed directory, and these files will be picked up and processed using the existing inbound order packages. Validation will be identical to the Birdseye interface previously developed the format will be based on TripOrderv2.3.xsd.
A new trigger will be created to process the outbound messages. This trigger will be specific for Unilever, so only trips with a loading depot of DHLUNWTK will be picked up by the trigger. A new procedure will be added to the existing XML creation process to create and send the files in generic XML format based on TripOrderv2.3.xsd
Scope
This change will be applied to system version 10.6.
Data
System Parameters are required for the inbound flow.
UNI_INBOUND_PATH - Area where files are placed to be processed
UNI_INBOUND_ARCH - Area where processed files are placed.
UNI_INBOUND_FAIL - Area where failed files are placed.
UNI_INBOUND_IDENTIFIER - Filename Prefix
UNI_INBOUND_LISTING_NAME - List which will hold files to be processed.
UNI_LISTING_SCRIPT_NAME - Script will process the files
UNI_FTP_DESTINATION_DIRECTORY
UNI_FTP_DESTINATION_IP_ADDRESS
UNI_FTP_DESTINATION_PASSWORD
UNI_FTP_DESTINATION_PORT
UNI_FTP_DESTINATION_USERNAME
UNI_OUTBOUND_ARCH
UNI_OUTBOUND_FAIL
UNI_OUTBOUND_PATH
Functional Description
Files will be placed in the directory specified in the system registry UNI_INBOUND_PATH. A new database job will be set up specifically for Unilever files. This job will run at a set interval, and will pick up files and process them creating the necessary orders.
The existing inbound process will be used to import and process the files.
A trigger will be added to the following tables:-
SCH_HAULAGE_ACTIVITY
SCH_TRIP
SCH_TRIP_STOP
When one of the following actions is performed a record will be written to the table INT_XML_CONTROL. The record will only be written if the loading depot is DHLUNWTK
Trip set to accepted
Trip at accepted and times changed
Trip at accepted and order added to the trip.
A new database job will be setup to run at a set interval. This job will retrieve any records from the table for Unilever and run a new procedure in INT_XML_OUT2. For each record that is found an XML file will be created and placed in the outbound directory listed in the system registry. The xml files will be created in the generic XML format based on TripOrderv2.3.xsd (attached in section 1).
The processed files will then be pushed via FTP to ESI. The destination for the FTP can be set at a system registry level.
References
Not Available
Document History
| Initial version | ||||
| Reviewed and Issued |
Authorised By
| Matt Crisford | Development Manager | |
| Peter Greer | TMSCC MTS Product Manager |
