EST 336598 Zenith Back Orders

STATEMENT OF WORK CHANGE REQUEST ESTIMATE

Client	ZEN	Project	DEV	Site	WHG
Client Reference	N/A	Aptean Reference	336598	Estimate Version	1.0
Prepared By	A N Walker			Estimate Date	13/07/2016
Invoice Reference				Priority	3
Customer	N/A			System Version	3.X

Client Request

Requirement 1: Back-order lines must be displayed on the POD note. Requirement 2: It is not always clear whether a product was not despatched or not delivered using the current POD format. This will be changed to display the Ordered, Despatched and Delivered quantities.

Aptean Solution

Note: All changes to the POD will be made to both the Priced and Unpriced formats. Requirement 1: Sage currently handles this requirement by adding product lines to an order, containing the free text describing the back order status. Sage will pass through additional product lines that have various levels of information Product Code - set if this is a back-order line for the product Description - the quantity back-ordered or the back-order reference, for example "Fully Back-Ordered for 1", "** Back-order to follow : XXXXXXX/1 **" Status - set to "C" - Complete. Sequence - This will be set as the same sequence as the line to which it pertains (for back ordered quantities) or 9000, plus 1 for each new back order reference line, e.g. 9001, 9002, etc. The Inbound webservice will be changed to allow the user to set a line to completed status - this will ensure that these lines are never prompted for the driver to deliver. The change to the webservice format (XSD) will be passed through to the Sage team for modification after sign-off of this change. All product lines on the POD will be ordered by Sequence, ensuring that the new lines will always appear at the end. The sequence should ensure that the line displaying the ordered, despatched and delivered quantity appears first, then the line for the back-ordered qty. Any back-order references should appear at the end after all product and back-order lines. Requirement 2: Sage will pass through the Ordered values for each product line. A "QTY DESP" column will be added after the existing column "QTY ORD". This will be populated from the planned quantities. The existing "QTY ORD" column will be changed so that this is populated from the Ordered quantities. The changes for both requirements will result with c change to the product table on the POD form as per the following example: PRODUCT CODE PRODUCT DESCRIPTION QTY ORD QTY DESP QTY DEL WG 011000 HARD WATER M/C DETERGENT 1 1 1 WG 100900 ULTRA FLOOR CLEANER 6 4 3 WG 100900 Fully Back-ordered for 2 0 0 0 WG 020500 PEBBLE SALT 1 1 1 WG 121700S CLOTHS ALL PURPOSE BLUE 1 1 1 190700 WINDOW SQUEEGEE 14" WITH HANDLE 1 0 0 190700 Fully Back-ordered for 1 0 0 0 ** Back-order to follow : XXXXXXX/1 ** 0 0 0 All other elements of the POD reports, including all other elements on the Product table, will remain unchanged.

Cost Details
Activity	No. of Days	Rate per Day (£)	Cost (£ Exc. VAT)
Requirements	0.00	750	£0.00
Change Request Evaluation	0.00	750	£0.00
Functional Specification	0.50	750	£375.00
Technical Specification	0.75	750	£562.50
Development	2.25	750	£1,687.50
Testing and Release	0.50	750	£375.00
Implementation	0.25	750	£187.50
Project Management	0.25	750	£187.50
TOTAL	4.50		£3,375.00

Copyright © OBS Logistics 2016. This estimate has an expiry date of 30 days from the specified Estimate Date. The information contained herein is supplied without liability for errors or omissions.