276908

276908 - JB-84YUY3/ Transport Only LOTS integration

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

Four sources of trigger:

1. Trigger from a pallet level ORD
2. Manual trigger for factory shuttles
3. EFX creation
4. Spreadsheet upload

C-TMS will need to check for source of order , if it is the WMS then do not trigger an ORD. Existing clients expected to be Birds Eye & ARDO , neither will require line level detail. Existing order interfaced are at plt level.

Solution

Order messages will be triggered for the following conditions.

• An order is created via the XML EDI flow
• An order is created manually in C-TMS
• An order is imported using the spreadsheet import
• A trip’s carrier is set to EFX (This is already in place).
• A button is pressed to manually send the message (Needs clarification at functional spec stage)

There is an existing message (BOO) that is sent only when the booked in flag is set. A new message type of ORD will be created based on the current message BOO. This message will be sent regardless of the booked in flag.

Before the message is sent C-TMS will check the source of the order (SCH_ORD.SOURCE_SYSTEM). A new flag against the Customer will determine which source systems should be used for ORD outbound messages.

Scope

This change will be applied to system version 10.5

FUNCTIONAL DESCRIPTION

There is an existing message of type BOO. A new message will be created based on the existing message. The new message will be of type ORD. The existing BOO message checks for a booked in flag before sending, this check will be removed from the ORD message process so the message is sent regardless of the booked in flag.

The message will have the same format as the BOO message, and will be created from a new procedure in INT_XML_OUT2.

This message will be triggered by the below actions.

• An order is created via the XML EDI flow
• An order is created manually in C-TMS
• An order is imported using the spreadsheet import
• A trip’s carrier is set to EFX (This is already in place).
• A button is pressed to manually send the message

A trigger will be written to create a record on the INT_XML_CONTROL table when an order is created by XML, Import or manually. This record will have a type of ORD to distinguish it from the other records in this table.

There is already code in place to send a message when the carrier of the trip (containing the order) is set to EFX. This will be altered slightly to include sending ORD messages.

A button will be added to the orders form that will allow the ORD message to be manually sent for a particular order. This button will add a record to the table INT_XML_CONTROL for the order.

The ORD message will only be sent for certain customers. Before adding a record to the interface the customer on the order will be checked. A new flag (SEND_ORD_MSG) will be added against the customer record to indicate if orders for this customer should be included in the ORD message.

NB Only LOTS enabled customers that do not have a WMS will have this functionality applied.

REFERENCES

Not Available

DOCUMENT HISTORY

Version	Date	Status	Reason	Initials
0.1	05/07/10	Draft	Initial version	DNG
1.0	07/07/10	Issue	Reviewed and Issued	MJC
1.1	08/07/10	Revised	Revised after comments from JB	DNG
2.0	12/07/10	Issue	Reviewed and Issued	MJC

AUTHORISED BY

Matt Crisford	Development Manager
Peter Greer	TMSCC MTS Product Manager