View source for EST 329393 AR-9ZGLFA Microlise Barcode Scanning

{{Template:Estimate
|Supimix_Client_Code=DHLT
|Supimix_Project_Code=IND
|Supimix_Site_Code=IN-BATH
|Supimix_Client_Reference=AR-9ZGLFA
|Supimix_Number=329393 
|The_version_of_the_document=1.0
|Your_Name=A N Walker
|Supimix_PO_Reference=GBMD30 . 10653 . 100089 . 123
|Supimix_Priority=3
|Date_(DD/MM/YY)=25/08/15
|Clients_Customer=Bathstore
|System_Version_being_changed=11.15
|Client_Request=Support barcode scanning at point of delivery with updates to interfaces and any affected reports.


;KER-CTMS - Delivery/Collection Lines:
*	<ORDER_DETAIL> section to be generated once for every unique value of input field Panther_Bar_Code within input field Product_Code within input field ConsignmentNo.
*	PALLET_ID item to be populated from input field Panther_Bar_Code

So, for Delivery lines, we should get a rolled-up quantity, weight and dims per label.
For Collection lines, we would get the same, but as the items would not have a label ID, they would sum at Product level, which is what we want.


;Microlise JourneySchedule:
*	consDetailInfo1 populated from PALLET_ID
Bearing in mind what we discussed on the call, this field seems the best as it's consistent in its use (i.e. we use the same field in the PODPOC), it's one of the fields Microlise said we could use, and it's not already in use in the mapping.
From an OBS perspective, we can achieve this through setting a Cost Centre-level system parameter, which then populates the tag in the OBS XML. We would need to test that nothing else is affected, and that this doesn't require changes to XSD's within DHL Link.


;Microlise PODPOC:
*	PALLET_ID item to be populated from input field consDetailInfo1
Note: The MSD document is out of date (the one I have seems to be an old format) - PALLET_ID is not in this format and should be added after ITEM_DESCRIPTION.


The rest of the interfaces are unaffected, namely:
*	Order Creation - At Order Header level, not at item level, so unaffected.
*	Paragon Import/Export - At Order Header level, not at item level, so unaffected.
*	Loading Plan export to Kerridge - At Order Header level, not at item level, so unaffected.
*	JourneySummary - At Trip Stop level, not Item level, so unaffected.


;Morning Reports:
The change to the Morning Reports (Failed Orders Report) could be achieved in 2 ways:
*	Consolidate the figures on the report to a Product level
*	Add the Pallet ID to the report.
In essence, the reports will run without this change, but the Product will repeat and the quantity will always be 1 for deliveries. Adding this is the complete solution.

|OBS_Solution=For the Bathstore Project, the initial requirements were that drivers would confirm quantity totals on the Microlise SmartPod device.  To enable drivers to scan the barcode label of each item to confirm delivery, changes are required in C-TMS.  The main change is to receive the barcode label numbers per item from the Kerridge interface and store them against the transport order in C-TMS and then send them on to Microlise.  This means that each individual delivery item for each order has to be stored in C-TMS with its corresponding label number (rather than just a list of product codes and quantity) and then debriefed and where appropriate reported at this level as well.  

This will be achieved using the existing Pallet ID field against the items. As an existing field, this is already visible (or can be made visible) against the items in the Orders screen. That means the following mapping:
*	ITEM_IDENTIFIER - The Product Code (unchanged)
*	ITEM_AKA_CODE - The Customer Return Code (CRC) (unchanged)
*	ITEM_DESCRIPTION - The Product Description (unchanged)
*	PALLET_ID - the Panther Barcode (additional mapping).

This will generate some changes to the Morning reports to add this field, and potentially some changes to the Microlise Import and Export. The DHL Link mapping for Order Details, Microlise journeySchedule and PODPOC will change slightly, to add in the mapping of this PALLET_ID field.


;KER-CTMS - Delivery/Collection Lines:
*	<ORDER_DETAIL> section to be generated once for every unique value of input field Panther_Bar_Code within input field Product_Code within input field ConsignmentNo.
*	PALLET_ID item to be populated from input field Panther_Bar_Code


;Microlise JourneySchedule:
*	consDetailInfo1 populated from PALLET_ID
The population of this field will be achieved through setting a Cost Centre-level system parameter, which then populates the tag in the OBS XML. The sending procedure will be modified to ensure that the setting of this parameter will not affect any other functionality.


;Microlise PODPOC:
*	PALLET_ID item to be populated from input field consDetailInfo1


The following reports will also require modification:

;Morning Reports:
The Failed Orders Report shows all the items that have failed delivery. Currently this is at Item level, but does not show the actual Label ID. The Pallet ID (where the Label ID is being stored) will be added to the report in a new column. This will be populated for the lines relating to Delivery orders and blank for lines relating to Collection orders.


;Return to Base Report:
This report shows all the items that have been returned. Currently this is at Item level, but does not show the actual Label ID. The Pallet ID (where the Label ID is being stored) will be added to the report in a new column. This will be populated for the lines relating to Delivery order and the quantity against these lines will always be 1. For lines relating to Collection orders, the Label ID will be blank and the quantity will show as the amount collected.


{{Note}} This change includes provision for up to 1 day to aid with the DHL Link mapping exercise.

|Requirements_Days=1.0
|Estimation_Days=0.75
|Functional_Specification_Days=2
|Technical_Specification_Days=0
|Development_Days=4
|Testing_and_Release_Days=0.50
|Implementation_Days=1.25
|Project_Management_Days=0.5
|Year=2015
|Free_Of_Charge|N=N
|Supimix_Client_Code|TEMPLATE=DHLT}}