294567

DHL C-TMS

AA Daily Performance Report

FUNCTIONAL SPECIFICATION - 10.7

07/19/12 - 1.0
Reference: FS 294567 OB-8NRE6H

FUNCTIONAL OVERVIEW

Client Requirement

The business requires 2 versions of a daily 'Delivery Performance' report that they can send out to the customers and use internally.

The report needs to detail the overall performance for each customer, and the performance by each site on the first page. On the second and subsequent pages, any exceptions should display (if there are any).

The parameters for what counts as an exception are detailed on the attached report design. If there are no exceptions, the report should just be on one page.

The business would like two versions of this report: one that excludes a certain range of ‘NON_CON’ codes from the ‘OTIF’ column and one that includes all ‘NON_CON’ codes in the ‘OTIF’ column.

The name of the report that excludes the range of ‘NON_CON’ codes is to be called 'Delivery Status Report'

The name of the report that includes all ‘NON_CON’ codes is to be called 'Delivery Status Report Internal'

The range of ‘NON_CON’ codes that is to be excluded from the 'Delivery Status Report' is ‘A01’ through to ‘A99’ (please note these codes have not been set up in AA test environment yet and will need doing once the report has been delivered).

The reports should be in a .pdf format.

The reports should have the following parameters to run:

• From Sched - [Mandatory]
• To Sched - [Mandatory]
• Customer - this should be a drop down of all the customers from the CUST_COST table. There should also be an option for 'ALL' customers. [Mandatory]

Solution

A new Oracle (PDF) report will be generated based on the attached requirements.

Two options for running the report will be provided to reduce the amount of code required where differences in layout and content are required these will be controlled programmatically within the report process. Two separate methods of running the report will be provided to avoid confusion for the users.

Scope

This change will be applied to system version 10.7.0.

SET-UP

Pre-Requisites

The new report and its selection parameters will need to be created.

Data

The new report and its selection parameters will need to be created. (See Appendix A for the scripts to add the new report.)

NB Two Reports should be set up in the Report Parameters one for Internal and One for External. The value of ‘usage’ will default accordingly.

Implementation Advice

The new report will need to be authorised for use by the relevant user groups:

FUNCTIONAL DESCRIPTION

AA Delivery Statuse Report Parameters

The new ‘AA Delivery Status Report’ will have the following selection parameters available:

• Start Schedule
• End Schedule
• Customer
• Usage

The customer parameter will default to ‘ALL’ to indicate that all customers will be valid unless otherwise specified and the list of customers will be restricted to the value of the ‘CUSTOMER’ parameter for the user:

The parameters will contain the following lookups and validation:

The default value for the ‘Usage’ selection parameter will be ‘INTERNAL’ for internal usage.

AA Delivery Status Report Layout

The proposed design of the report may be seen below:

N.B. The standard OBS report format and page headings will be used in the report.

Where ‘Driver Trip Sheet’ will be ‘Delivery Status Report’, ‘TRIP_SHEET’ will be ‘AA_DEL_STAT’ and ‘Depot’ will be blank.

The ‘Summary By Customer’ (at the customer level), ‘Summary By Site’ (at the location level) and ‘Exceptions’ (at the transport order level) sections will be developed as displayed in the example provided.

Comments present in the example provided:

AA Delivery Status Report Query

The new report will have two different queries for internal and external usage as determined by the ‘Usage’ selection parameter.

The ‘Usage’ refers to the type of reason code in the ‘Reason Codes’ tab page of the ‘Business Data Maintenance’ screen:

N.B. The reason codes may now be segregated by cost centre and a ‘+’ in the cost centre indicates that the reason code is available for all cost centres. Therefore, it is expected that the new ‘NON_CON’ reason codes will be created for cost centre ‘NRCC’.