259681
259681 - PA-7JYD35/ Report Changes for Healthcare Deployment
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
Functiona Overview
Client Requirement
Amend the CN Trip Sheet as per the attached spreadsheet and rename to HC Trip Sheet.
Create a new report called HC Booking In Form as per the requirements in the attached spreadsheet.
Specific requirements to allow the HCUK operation to go live with MTS.
Solution
Part 1 ‘HC Trip Sheet’ A copy of Report TRIP_SHEET.rep v1.0 will be made and named to HC_TRIP_SHEET.rep v1.0. The name of the report that will appear in the Reports drop down list will be ‘HC Trip Sheet’. The Report Parameters required to run this report will remain unchanged.
v2 specific fields referenced Note that Actual DUs and Actual Lifts will only be shown if these have been entered at the time the report is printed
The following layout amendments will be made to HC_TRIP_SHEET.rep, as described in document ‘HCUK Report Requirements - NW-7N3G9P.xls’ attached to this RIO:
- Current field ‘Planned Lifts’ will be re-named ‘Planned DUs’ and reference Planned DUs (in database this is SCH_ORDER_LINE.QUANTITY)
- Current field ‘Actual Desp’ will be renamed to ‘Actual DUs’ and reference Actual DUs (in database this is SCH_ORDER_LINE.ACTUAL_QUANTITY)
- Current field ‘Actual Lifts’ will be renamed to ‘Planned Lifts’ and reference Planned Weight (in database this is SCH_ORDER_LINE.WEIGHT)
- Current field ‘Total Weight’ will be renamed ‘Actual Lifts’, aligned to the right of ‘Planned Lifts’ and reference Actual Weight (in database this is SCH_ORDER_LINE.ACTUAL_WEIGHT)
- Current field ‘Load Ref’ will be removed
- New column ‘DU Type’ will be included between ‘Booking Window’ and ‘Planned Cases’ and reference DU Type on the order line (in database this is SCH_ORDER_LINE.DU_TYPE)
- Stop Details will include total DUs by ‘DU Type’ – the position of this will be confirmed within the Functional Specification.
The SQL select statement will require amending to pick up the new data to be displayed on the amended report.
Part 2 ‘HC Booking In Form’
A new Report will be created called ‘BOOKING_IN_FORM.rep’ v1.0. The name of the Report when available from the Reports screen will be ‘HC Booking In Form’. The Report will have an A4 Portrait layout and is to run with selection criteria Schedule, Customer(s), Delivery Location, and Group Name.
- Schedule will allow entry of a single Schedule (e.g. 090201) and will be mandatory.
- Customer will allow entry of a single Customer (e.g. BILETH) and will be optional, meaning all Customers will be queried when left Blank
- Delivery Location will allow entry of a single Location_Id (e.g. PHOEABERD006) and will be optional, meaning all Locations will be queried when left Blank. It has been requested that this parameter is for Manual Entry by the user, rather than the normal Drop Down List. This parameter will therefore behave like ‘Trip Id (optional)’ in Report ‘CN Loading Schedule’. If a user types DHLCHER in this field only Location_Id DHLCHER will be searched for, however if the user enters DHL% then all location_id’s starting with DHL will be queried
- Group Name will allow entry of a single Group Name (e.g. CHER1) and will be optional, meaning all Group Names will be queried when left Blank.
The Header of the report will display a Title of ‘BOOKING IN FORM’ and will include the DHL Logo, along with Date/Time report run, Report Name/Version, MTS Version and Selection Parameters entered. This will keep the header of the report in line with all other Reports.
The purpose of this report is to return all orders that have not been booked in. Meaning that the ‘Booked In’ box in the ORDERS screen has not been checked. The Report will be ordered alphabetically be Delivery Destination, and ordered by Customer within each Delivery Destination.
The Layout of the Report will be as close to the design shown in document ‘HCUK Report Requirements - NW-7N3G9P.xls’ attached to this RIO.
A new SQL statement will be constructed to return data that is to be displayed on this report.
Scope
These reports will be applied to system version 10.6 on HCRTST and once approved HCRPRD.
SET-UP
Data
The new HC copy of the Trip Sheet report will be added to the standing data to allow it to be selected from the standard reports form. The parameters will be set up in the HCR database, the same as the parameters set up in the CON databases. The only difference will be that the HC Report will be named ‘HC Trip Sheet’
Part 2 – Report ‘HC Booking In Form’
The new report will be added to the standing data to allow it to be selected from the standard reports form. The report is to run with selection criteria Schedule, Customer(s) and Group Name.
The new report and parameter data will need to be created as follows :-
Table REP_REPORT :-
Name ‘HC Booking In Form’ Report_Type REP Filename HC_BOOKING_IN_FORM.rep Printer_Type Laser Show_Pform F Orientation PORTRAIT
Table REP_REPORT_PARAM :-
Common :-
Report_Name ‘HC Booking In Form’ Report_Type REP
Specific :-
| Param_Type | Param_Name | Conditional | Param_Title |
|---|---|---|---|
| PG_SELECT_LIST1 | P_SCHED_NAME | M | Schedule |
| PG_SELECT_LIST2 | P_CUSTOMER | O | Customer |
| PG_SELECT_LIST3 | P_GROUP_NAME | O | Group Name |
| PG_FFCHAR1 | P_DEL_LOCATION | O | Delivery Location |
Functional Description
Sample Layout
Part 1 ‘HC Trip Sheet’ The ‘CN Trip Sheet’ report was run with the following parameters against HCRTST:
Below is a partial screenshot of how the ‘CN Trip Sheet’ Report will look like when run with the parameters above, with the amendments made as per specified in the attached document with the RIO.
This example demonstrates how the report will look for an order that has 2 product lines. E.g. Customer Ref ‘006BIE501547’ has 2 order lines; PARCEL and EURO. It also demonstrates how the request of ‘Stop Details will include total DUs by DU Type’ will be displayed in the amended report. This is the section next to ‘Totals:’
Note that ‘Planned/Actual DUs’ have been moved next to ‘DU Type’ to make the layout of the ‘Totals:’ section easier to read.
Part 2 ‘HC Booking In Form’
A sample layout of how the Report Parameters for the new ‘HC Booking In Form’ are displayed below
Note that parameter Delivery Location is for Manual Entry by the user, rather than the normal Drop Down List, as requested by the client. This parameter will therefore behave like ‘Trip Id (optional)’ in Report ‘CN Loading Schedule’. If a user types DHLCHER in this field only Location_Id DHLCHER will be searched for, however if the user enters DHL% then all location_id’s starting with DHL will be queried
As this is to be a new report, we currently have no reports to base the design on. Therefore, the layout/design of the new report will be as close to the sample design provided with the RIO. A screenshot of this is below:
A screenshot below shows how the report will be displayed when there is an order with 2 order lines on it of different DU Type (example boxed in red):
The header section of the report will be amended to be in line with the header of all current MTS Reports. A preliminary example of this is below:
References
| HCUK Report Requirements - NW-7N3G9P.xls | |||
| HCUK Report Requirements - NW-7N3G9P - 090109.xls | |||
| EST-259681 NW-7N3G9P Report Changes for Healthcare deployment v1.doc | |||
| FS-259681 NW-7N3G9P Report Changes for Healthcare deployment v1.doc |
Document History
| Initial version | ||||
| Reviewed and Issued | ||||
| 'CN Trip Sheet’ amended fields specified, including ref to field in database |
Authorised By
| Matt Crisford | Development Manager | |
| Suk Sandhu | TMSCC MTS Product Manager |
