289315

DHL C-TMSMTS

Change to Microlise interface

- 10.6

- 0.1

Reference: FS 289315 OB-8HTEV5

Change Request Summary:

Change to Microlise interface to surppress items prefixed with an 'X'Antony Truin/Daventry/UK/Exel

Change Request Details:

The business require a change to the Microlise interface to surppress items that are created as part of the WCS splitting functionality. Currently, in order to adapt to haow items are loaded on trunks, WCS and CTMS use 'Dunelm' functionality to handle items and can move them onto newly created OMS refs if they are loaded off plan. This is fine, however the interface currently sends all items out Microlise. This means that if a cage is loaded off plan and split onto a new OMS ref, the driver will see 2 items on his HHT, the first will be the actual item EL1111, and the second will be the same item but with the 'X' prefix XEL1111. The proposed solution to solve this problem is to surppress items on consignments where the <ITEM_IDENTIFIER> tag starts with an 'X' Please see the attached XML with a highlighted section showing the items prefixed with an 'X'

Benefits identified as a result of the change:

When orders are split, due to items being scanned on a different trip to plan, the item on the original order is amended to start with an X and the item is added to a new order.

The issue is we are currently sending data to MICROLISE for X items which have been moved to another order and trip. To resolve this issue, code changes will be made to remove x items from the MICROLISE outbound file.

In addition to excluding the X items, we must also deal with orders and stops based on only non X items.

To create the MICROLISE outbound file, the code selects all of the ‘MIC’ trip records waiting in the control file to be processed. For each trip a count of items will be created. If this count is greater than 0 a new variable( V_DETAIL) will be set to S to indicate that the orders on the trips are based on items and not lines.

A trip, stop and order level count of NON-X items will be created.

If V_DETAIL = S and the NON-X count for the trip returns 0, there will be no further code run for the current trip and the code will loop to the next trip.

If the variable is S and NON-X items do exist on the trip, the trip data will be processed and code will continue to the stop processing. For each stop, the count of NON-X items will be run. If there are no NON-X items at the current stop, the stop will not be processed and the code will loop to the next stop.

If the NON-X count for the stop is greater than 0, the current stop will be processed and the code will continue to the order processing.

For each order, the NON-X count will be calculated, where the count is 0, the orders will not be processed and the code will loop to the next order at the stop. When the NON-X count is greater than 0, the order will be processed and the code will continue to the order detail processing.

The code will only attempt to process the order details if an order has been identified as having NON-X items . Items are currently processed by the generic xml procedure GEN_ORDER_DET_STK. In this code, an oms_ref is passed in and all the items for the oms_ref and selected and the relevant data is extracted to be passed to MICROLISE.

In the generic code, a new where clause will be added when selecting the items, to exclude any items which start with X.

Due to this requirement , items starting with X should no longer be used.

Unique Identifier

When an order is split, the oms-ref changes but the new order retains the external_ref of the original order. In automotive, the SO_REF, TRIP_ID,STOP_SEQ acts as a unique identifier of an order in MICROLISE. The SO_REF is currently populated with the external ref. This means that the original and new orders cannot both be sent to MICROLISE as the SO_REF,TRIP_ID,STOP_SEQ will not be unique and will cause MICROLISE to reject the file.

A system parameter will be created call MIC_SO_REF. If this is set to Y, the so_ref will be populated with the oms_ref concatenated with the external_ref in the following format

OMS_REF||EXTERNAL_REF

This will provide each order with a unique identifier and prevent the MICROLISE flow from rejecting the file.

This fix is a temporary fix until ESI changes to SO_REF have been completed.