264763

FUNCTIONAL OVERVIEW

Client Requirement

Create delivery documentation from MTS in Polish as per the attached examples. Specific in country requirements to allow MTS to be deployed in Poland.

Solution

Create 3 Oracle 10g Reports as per sample attachments with ‘_pl’ in the name in RIO system. The 3 new reports will be available from the standard Reports form when promoted to User Groups via the Access Control screen.

The naming of the reports in the drop down list will be as follows:

Sample ‘plts_ticket_pl_new.xls’ -> ‘PL Pallets Ticket’
Sample ‘transp_order_pl.xls’ -> ‘PL Transport Order’
Sample ‘trip_sheet_pl.doc’ -> ‘PL Trip Sheet’

These reports will be available to client ‘Poland’ only and will display in Polish where detailed in samples provided.

All 3 reports will run with selection criteria below, where from/to dates are the only mandatory parameters. Those parameters left blank will return All:

From Date/Time 
To Date/Time 
Load Location    
Carrier                
Group Name      
Owning Depot    

The full details of the reports and what data will be displayed on each of them, along with the required sql select statements, will be outlined in the functional specification.

Please note the following summary description;

Transport Order

This 1 page document will be printed for each trip and forms the transport contract between DHL and the Carrier. Each order will be uniquely identified by the MTS trip number (this in future will need to be a PO number for Oracle AP). The order print will contain the deport giving the order, the carrier providing haulage, the driver name and vehicle registration number, the unloading place(s) and freight net value. The document will then contain a list of small print terms and conditions of the order in Polish.

Pallet Ticket

A pallet ticket will be printed for each trip delivery stop. The pallet ticket number will be uniquely identified using the trip reference suffixed by “-“ and the trip stop sequence number. The pallet ticket print will show the list of delivery note numbers (MTS customer ref) delivered at the stop, the issuing depot, consignee name and address and a table of all possible packing codes with space for the quantity of units to be recorded from DHL DC, consignee in, consignee out and back to DHL DC.

Trip Sheet

A trip sheet will be printed for each trip and is uniquely identified by the trip reference. The trip sheet print will contain as header information the issuing depot and address, the deliver date, carrier, vehicle registration number, driver name and mobile telephone number. Space will be provided for the driver to write the actual arrival time at and departure time from the loading depot The detail section will list each delivery consignment (order) showing delivery sequence, delivery note number (customer ref), consignee, address and order delivery window. Space is then provided for the driver to write in actual arrival and departure times and confirmation signature. Additional to the provided design, the DU and qty to deliver will also be included. Further space will be provided for the driver to write the total kms and lump sum cost.

Scope

These changes will be applied to system version 10.6 on EURTST and once approved EURPRD.

SET-UP

Pre-requisites

None

Menu Structure

Unchanged

Data

Report Data

The 3 new reports will be added to the standing data to allow it to be selected from the standard reports form. The selection criteria for the 3 reports will include the following: Date Range, Load Location, Carrier, Group Name and Owning Depot.

Note with the exception of Group Name parameter in ‘PL Transport Order’. See section 4.2 for more details.

The report data will need to be created as follows :-

PL Pallets Ticket

REP_REPORT :-

Name: ‘PL Pallets Ticket’
Report_Type: REP	
Filename: PL_PALLETS_TICKET.rep
Printer_Type: Laser
Orientation: LANDSCAPE

PL Transport Order

REP_REPORT :-

Name: ‘PL Transport Order’
Report_Type: REP	
Filename: PL_TRANSPORT_ORDER.rep
Printer_Type: Laser
Orientation: PORTRAIT

PL Trip Sheet

REP_REPORT :-

Name: ‘PL Trip Sheet’
Report_Type: REP	
Filename: PL_TRIP_SHEET.rep
Printer_Type: Laser
Orientation: LANDSCAPE

Note the ‘PL Trip Sheet’ and ‘PL Pallets Ticket’ reports will be in landscape format due to the amount of data content displayed on both reports.

All reports selection parameters will be set up as below, with Date Range being the only mandatory parameters. Date Range will query the Start Time against a trip (SCH_TRIP.START_TIME)

REP_REPORT_PARAM :-

Specific :-

Param_Type	Param_Name	Conditional	Param_Title
P_START_DATETIME	P_START_DATETIME	M	Start Date
P_END_DATETIME	P_START_DATETIME	M	End Date
PG_SELECT_LIST1	P_CARRIER	O	Carrier
PG_SELECT_LIST2	P_GROUP_NAME	O	Group Name
PG_LOV1	P_LOAD_LOC	O	Load Location
PG_LOV2	P_DEPOT	O	Owning Depot

The report parameters in the REPORTS form should display as follows:

FUNCTIONAL DESCRIPTION

PL Pallets Ticket Layout

A pallet ticket will be printed for each trip delivery stop. The pallet ticket number will be uniquely identified using the trip reference suffixed by “-“ and the trip stop sequence number. The pallet ticket print will show the list of delivery note numbers (MTS customer ref) delivered at the stop, the issuing depot, consignee name and address and a table of all possible packing codes with space for the quantity of units to be recorded from DHL DC, consignee in, consignee out and back to DHL DC.

Below is the sample layout of what the ‘PL Pallets Ticket’ Report will look like. It will display as closely to the sample report provided ‘plts_ticket_pl_new.xls’, as below. The sample report has been edited slightly to show what data will be displayed in each area, what data will remain static and what fields are for manual entry by user. These details are displayed in red:

Note that this report will have the standard Reports header to keep it in line with all other Reports. This will include the Report Name, Date/Time printed, DHL Logo, Page No, Report version etc.

PL Transport Order Layout

This 1 page document will be printed for each trip and forms the transport contract between DHL and the Carrier. Each order will be uniquely identified by the MTS trip number (this in future will need to be a PO number for Oracle AP). The order print will contain the deport giving the order, the carrier providing haulage, the driver name and vehicle registration number, the unloading place(s) and freight net value. The document will then contain a list of small print terms and conditions of the order in Polish.

Below is the sample layout of what the ‘PL Transport Order’ Report will look like. It will display as closely to the sample report provided ‘transp_order_pl.xls’, as below. The sample report has been edited slightly to show what data will be displayed in each area, what data will remain static and what fields are for manual entry by user. These details are displayed in red:

Main Section of Report:

Footer – Terms and Conditions:

The Terms and Conditions will be copied exactly from the sample report, this includes text formatting, boxing around no. 12 and addresses/phone numbers etc.

Note that, if possible and there is enough room for a header, this report will have the standard Reports header to keep it in line with all other Reports. This will include the Report Name, Date/Time printed, DHL Logo, Page No, Report version etc.

PL Trip Sheet Layout

A trip sheet will be printed for each trip and is uniquely identified by the trip reference. The trip sheet print will contain as header information the issuing depot and address, the deliver date, carrier, vehicle registration number, driver name and mobile telephone number. Space will be provided for the driver to write the actual arrival time at and departure time from the loading depot The detail section will list each delivery consignment (order) showing delivery sequence, delivery note number (customer ref), consignee, address and order delivery window. Space is then provided for the driver to write in actual arrival and departure times and confirmation signature. Additional to the provided design, the DU and qty to deliver will also be included. Further space will be provided for the driver to write the total kms and lump sum cost.

On the next page is the sample layout of what the ‘PL Trip Sheet’ Report will look like. It will display as closely to the sample report provided ‘trip_sheet_pl.doc’, as below. The sample report has been edited slightly to show what data will be displayed in each area, what data will remain static and what fields are for manual entry by user. These details are displayed in red.

Note that this report will have the standard Reports header to keep it in line with all other Reports. This will include the Report Name, Date/Time printed, DHL Logo, Page No, Report version.

References

Ref No	Document Title & ID	Version	Date
	plts_ticket_en_new.xls
	plts_ticket_pl_new.xls
	transp_order_en.xls
	transp_order_pl.xls
	trip_sheet_en.doc
	trip_sheet_pl.doc
EST-264763	NW-7RGK5C Delivery Docs Poland v1.0.doc	1.0	07/05/09

Document History

Version	Date	Status	Reason	Initials
0.1	11/05/09	Draft	Initial version	LAD
1.0	27/05/09	Issue	Reviewed & Issued	MJC

Authorised By

Matt Crisford

Development Manager

Suk Sandhu

TMSCC MTS Product Manager

Copyright OBS Logistics © 2009

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