View source for 263313

=263313 - JB-7QNVRZ Birds Eye InOut EDI Flow =

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==
DHL have won a transport contract for BEIG (Birds Eye) due for transition on May 27th.

In order for this to occur, DHL require automated file interfaces for their Managed Transport System (MTS) for incoming Order Information, outgoing Order Information and Trip data.
All data transmissions will be XML documents.

Requirements:
Interface 1: DAI Matflo WMS to MTS (T_ORD message advising of order receipt)
Interface 2: MTS to DAI Matflo WMS (T_LOAD message to advise of load plans and alterations to load plans: the trigger being orders added or removed, changes to loading times, changes to delivery sequence or the order reaching planned status).


==Solution==
===Interface 1: (Inbound to the MTS System)===

OBS will set up an automated process running at an agreed interval to capture and process XML documents sent to the MTS server via ‘ESI file transmission’. 

When these XML document files are captured, the data will be stripped out of them, inserted into the MTS system, and as appropriate, the files will be placed in an archive or failure file depending on their processing status: success or failure.

Once this data has been captured from the incoming XML document, it will be validated according to an agreed set of minimum data requirements and disseminated into two interim (interface control) tables:
Int_xml_ord_header and int_xml_ord_detail.

OBS has XML document handling infrastructure that can be modified to suit this task. 

From this point, the user of the MTS system will be able to see the processing status of each received file using an existing tab on the interface errors display screen. From this screen the user will be able to see validation errors, and reasons why processing of inbound XML documents have failed.

The MTS system has this functionality built in – within the current build. The current Interface errors screen will have the current functionality checked and modified (If required.) for the ‘new’ information provided. 

Once the data has been uploaded into the inbound header and detail tables, it will be refined further, using an agreed set of minimum data requirements into either an update to a previously existing order, or a new order. 

OBS has an existing processing engine that it uses for this task that can be modified to accept DHL’s minimum data requirements in this case.

NB:  
*File formats to be used will be latest Generic MTS XML format.

===Interface 2: (Outbound From the MTS System)===
OBS will set up an automated process to send outgoing XML documents containing load information back to the DAI Matflo system. 

OBS has an existing processing engine that can be modified to suit this task. The modifications to this processing engine will comprise of the ‘trigger events’ which transmit the file back to the DAI Matflo system. Each trigger event will take ½ a day to program into the processing engine, with a further ¼ of a day to test. 

The requirement for this system lists triggers to send outgoing files as five ‘occurrences’: 

a)	Changes to Loading Times

b)	When an order is added to a trip

c)	When an order is removed from a trip

d)	Changes to the delivery sequence of the load.

e)	The order’s status changes to ‘planned’.

NB:  
*Triggers for message creation must be confirmed before specification is agreed. This may affect the cost of this change.)

*The outbound file will have the same structure as the inbound file – the latest generic MTS XML format.



==Scope==

==Data==

=Functional Description=

= References =

{| Border="1"	
| <center>'''Ref No'''</center>
| <center>'''Document Title & ID'''</center>
| <center>'''Version'''</center>
| <center>'''Date'''</center>

|-
| <center>1</center>
| EST-259410 PA-7MKDYG CN Loading Schedule Report Changes v1.doc
| <center>1</center>
| <center>06/01/09</center>
|}


= Document History =

{| Border="1"	
| <center>'''Version'''</center>
| <center>'''Date'''</center>
| <center>'''Status'''</center>
| <center>'''Reason'''</center>
| <center>'''Initials'''</center>

|-
| <center>1a</center>
| <center>12/01/09</center>
| <center>Draft</center>
| Initial version
| <center>PDR</center>

|-
| <center>1</center>
| <center>12/01/09</center>
| <center>Issue</center>
| Reviewed and Issued
| <center>MJC</center>
|}


= Authorised By =



{| Border="1"	
| '''''Matt Crisford'''''
| Development Manager
| 

|-
| '''''Suk Sandhu'''''
| TMSCC MTS Product Manager 
| 

|}