281873

DHL MTS

10.6

FUNCTIONAL SPECIFICATION FS 281873 JC-89ZGU4 Order Visibility v1.0

Version :

0.1

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

Contents

[#1.Functional Overview|outline 1. Functional Overview3]

[#1.1.Client Requirement|outline 1.1 Client Requirement3]

[#1.2.Solution|outline 1.2 Solution3]

[#1.3.Scope|outline 1.3 Scope3]

[#2.Set-up|outline 2. Set-up4]

[#2.1.Pre-requisites|outline 2.1 Pre-requisites4]

[#2.2.Menu Structure|outline 2.2 Menu Structure4]

[#2.3.Data|outline 2.3 Data4]

[#3.Functional Description|outline 3. Functional Description5]

Appendix A table updates REQUIRED7

Appendix B QUOTE & DoCuMENT History8= Functional Overview =

Client Requirement

Change Request Summary:

Users working in Consolidation Centres need visibility of orders through the Order Summary screen in the systemStuart Foster/Milton Keynes/UK/NFC

Change Request Details:

Users at Consolidation Centres are delivering orders on behalf of other depots in the network, all orders they deliver are Cross Docked. When using the Order Summary screen, a user at a Consol Centre will see no orders as the visibility is based on the Group Name of the orders. The Group Name of the orders remains as that of the originating site. Users need visibilty in the Order Summary screen of any orders which they have delivered (Eg Cross Docked through their Consol Centre)

Benefits identified as a result of the change:

Order Summary is a fundamental part of MTS and as such it is essential that users at Consol Centres have use of it

Solution

The query behind the Order Summary screen will be amended to allow users to see orders which have passed through their Consolidation Centre.

The Consolidation Centre will be identified by the SCHED_GROUP that the user has access to. They will be able to see all orders which have this sched_group as the group name and all orders which have been loaded at the SCHED_GROUP location.

To identify where the order has been loaded , the where clause for the Order Summary block must include a link to the sch_haulage_activity and sch_trip_stop tables. This introduces a new level of data to the Order Summary screen and must be coded carefully to ensure no duplicates or missing orders.

In addition we must ensure that users are able to access the orders which do not belong to their consolidation Centre

Scope

This change will be applied to system version 10.6.0 on CONTST and once approved CONPRD.

Set-up

Pre-requisites

None

Menu Structure

Unchanged

Data

No changes

Functional Description

Currently, when the user opens the Order summary and selects search, the orders returned to the screen are based on the SCHED_GROUP and other user parameters that have been set for the user.

This will result in users only seeing orders which belong to their sched group and excludes any cross docked orders that have been delivered by their sched group on behalf of others.

To rectify this issue, we intend to change the search criteria to include any orders that have passed through a users SCHED GROUP. Pass through includes Loading and Unloading at the location.

The data block on the order summary screen is based on a where clause which is applied when the user selects refresh from the Order Search. Currently the where clause looks at the SCHED_GROUP the user has access to and adds in the clause ‘GROUP_NAME || v_sched_group’ where v_sched_group is an = or IN statement based on the number of sched groups the user has access to. There is a second part of the where clause which looks at the value of Group Name in the Order search.

The general part of the where clause will be amended to accommodate this change. The general search will look for all orders which have been loaded at the BASED_AT the user has access to in addition to the orders where the group name is the sched groups the user has access to.

The specific search will look for all orders where the GROUP NAME equals the Group name the user has selected.

Based on a system parameter called ‘ORDER_SEARCH_CONSOL’ the where clause code will be changed as follows:

General Where

Oms_ref in (select oms_ref from sch_haulage_activity, sch_trip_stop

Where sch_trip_stop.stop_id = sch_haulage_activity.stop_id

and sch_haulage_activity.activity_name = ‘Load’

and sch_trip_stop.location_id || v_BASED_AT)

Specific Group Name Where

Group_name = :specific_group_name – no change

In addition to seeing the orders in the summary block, the users will also be required to access and view the orders.

1. 1. table updates REQUIRED

N/A

1. 1. QUOTE & DoCuMENT History

Activity	Estimate	Quote
No. of Days	No. of Days	Daily Rate (£)	Cost (£) Exc. VAT
Work to Date	0.00	0.00	500
Change Request Evaluation	0.75	0.75	500
Functional Specification	0.75	0.75	500
Technical Specification	0.00	0.00	500
Development	1.50	1.50	417
Testing & Release	0.75	0.75	417
Implementation	0.00	0.00	462
==== TOTAL ====

References

Ref No	Document Title & ID	Version	Date
	EST 281873 JC-89ZGU4 Order Visibility v1.0	1.0	30/11/2010

Glossary

Term or Acronym	Meaning

Document History

Version	Date	Status	Reason	Initials
0.1		Draft	Initial version	SEW
1.0		First	First issued, amendments made .	SEW

Authorised By

Matt Crisford	Development Manager
Peter Greer	TMSCC MTS Product Manager