249804 - Revision history

Kingj at 11:37, 5 February 2009

2009-02-05T11:37:13Z

← Older revision		Revision as of 13:37, 5 February 2009
Line 154:		Line 154:

	IMAGE		IMAGE




	== Document History ==		== Document History ==

Kingj at 09:37, 5 February 2009

2009-02-05T09:37:57Z

← Older revision		Revision as of 11:37, 5 February 2009
Line 141:		Line 141:
	IMAGE		IMAGE


	~~= QUOTE & DOCUMENT HISTORY =~~

Kingj at 09:17, 5 February 2009

2009-02-05T09:17:45Z

@@ Line 59: / Line 59: @@
-== 	Scope =
+== 	Scope ==
 This change will be applied to system version 10.6 on CONTST and once approved CONPRD. This was requested by Consumer Networks, but as this is an improvement to current functionality, it will be released over time to all contracts, excluding SAR as it has its own code stream for screen TRIPDTL.
 = 	FUNCTIONAL DESCRIPTION =
@@ Line 157: / Line 142: @@
-= APPENDIX A     TABLE UPDATES REQUIRED =
+=  QUOTE & DOCUMENT HISTORY =

Kingj: /* Authorised By */

2009-02-04T12:28:14Z

Authorised By

← Older revision		Revision as of 14:28, 4 February 2009
Line 188:		Line 188:
	== Authorised By ==		== Authorised By ==

	~~=== Authorised By ===~~

	{\| border="1"		{\| border="1"

Kingj: /* Authorised By */

2009-02-04T12:27:28Z

Authorised By

← Older revision		Revision as of 14:27, 4 February 2009
Line 188:		Line 188:
	== Authorised By ==		== Authorised By ==

	~~IMAGE~~		=== Authorised By ===

			{\| border="1"
			\| '''''Dave Meir'''''
			\| Development Manager
			\|-
			\| '''Suk Sandhu'''
			\| TMSCC MTS Product Manager
			\|}

Kingj at 11:12, 4 February 2009

2009-02-04T11:12:10Z

← Older revision		Revision as of 13:12, 4 February 2009
Line 7:		Line 7:


	== FUNCTIONAL OVERVIEW ==		= FUNCTIONAL OVERVIEW =


	=== Client Requirement ===		== Client Requirement ==
	Amend Debrief Screen - TRIPDTL v2.54 - Reduce level of input, but retain ability to change by exception		Amend Debrief Screen - TRIPDTL v2.54 - Reduce level of input, but retain ability to change by exception

Line 24:		Line 24:


	=== Solution ===		== Solution ==
	When the Trip Debrief (TRIPDTL) screen is opened, whether from the Main Menu or when called from another screen, it will always default into the ‘Order Debrief’ tab, instead of the current ‘General’ tab.		When the Trip Debrief (TRIPDTL) screen is opened, whether from the Main Menu or when called from another screen, it will always default into the ‘Order Debrief’ tab, instead of the current ‘General’ tab.

Line 59:		Line 59:


	=== Scope ===		== Scope =
	This change will be applied to system version 10.6 on CONTST and once approved CONPRD. This was requested by Consumer Networks, but as this is an improvement to current functionality, it will be released over time to all contracts, excluding SAR as it has its own code stream for screen TRIPDTL.		This change will be applied to system version 10.6 on CONTST and once approved CONPRD. This was requested by Consumer Networks, but as this is an improvement to current functionality, it will be released over time to all contracts, excluding SAR as it has its own code stream for screen TRIPDTL.


	== SET-UP ==		= SET-UP =

	=== Pre-requisites ===		== Pre-requisites ==
	None		None


	=== Menu Structure ===		== Menu Structure ==
	Unchanged		Unchanged


	=== Data ===		== Data ==
	Unchanged		Unchanged


	== FUNCTIONAL DESCRIPTION ==		= FUNCTIONAL DESCRIPTION =

	=== New Functionality ===		== New Functionality ==

	Below is a sample screenshot of the new TRIPDTL screen display – once opened.		Below is a sample screenshot of the new TRIPDTL screen display – once opened.
Line 98:		Line 98:


	==== Process Flow for ‘Set Actuals’ button ====		=== Process Flow for ‘Set Actuals’ button ===

	Below is a sample screenshot of a trip with the Order Details and Trip Stop details displayed. User enters Actuals for 2 stops, as these are exceptions, meaning that the planned Arr/Dep times were not met.		Below is a sample screenshot of a trip with the Order Details and Trip Stop details displayed. User enters Actuals for 2 stops, as these are exceptions, meaning that the planned Arr/Dep times were not met.
Line 121:		Line 121:


	==== Process Flow for ‘Set Desp’ and ‘Set Del’ buttons ====		=== Process Flow for ‘Set Desp’ and ‘Set Del’ buttons ===

	The ‘Set Desp’ and ‘Set Del’ buttons on the ‘Order Debrief’ tab will work in a similar fashion. When a user enters some despatched quantities, and clicks the ‘Set Desp’ button, all other values will be pre-populated with the Planned values.		The ‘Set Desp’ and ‘Set Del’ buttons on the ‘Order Debrief’ tab will work in a similar fashion. When a user enters some despatched quantities, and clicks the ‘Set Desp’ button, all other values will be pre-populated with the Planned values.
Line 135:		Line 135:


	==== Process Flow for ‘POC All’ and ‘POD All’ buttons ====		=== Process Flow for ‘POC All’ and ‘POD All’ buttons ===

	The ‘POC All’ and ‘POD All’ buttons will apply a POC or POD for all orders in the ‘Order Debrief’ tab. If a few orders already have a POC or POD applied, the ‘POC All’/’POD All’ will apply a POC or POD to those that do not.		The ‘POC All’ and ‘POD All’ buttons will apply a POC or POD for all orders in the ‘Order Debrief’ tab. If a few orders already have a POC or POD applied, the ‘POC All’/’POD All’ will apply a POC or POD to those that do not.
Line 148:		Line 148:
	All current error trapping functionality will remain on this screen. E.g. Trying to Apply a POC when no Actual Date/Times entered will display message ‘You must specify the Actual Arrive Date’.		All current error trapping functionality will remain on this screen. E.g. Trying to Apply a POC when no Actual Date/Times entered will display message ‘You must specify the Actual Arrive Date’.

	==== Process Flow for ‘Set All Actuals’ button ====		=== Process Flow for ‘Set All Actuals’ button ===
	Finally, the button ‘Set All Actuals’ will be used to pre-populate all actual values, and perform an automatic save. This is to be used only if there have been no exceptions on Stop times, despatched quantities or delivered quantities. Below is a sample screenshot of a trip with no actual data entered - it is again followed by a screenshot displaying the trip details, if the ‘Set All Actuals’ button was clicked:		Finally, the button ‘Set All Actuals’ will be used to pre-populate all actual values, and perform an automatic save. This is to be used only if there have been no exceptions on Stop times, despatched quantities or delivered quantities. Below is a sample screenshot of a trip with no actual data entered - it is again followed by a screenshot displaying the trip details, if the ‘Set All Actuals’ button was clicked:

Line 157:		Line 157:


	== APPENDIX A TABLE UPDATES REQUIRED ==		= APPENDIX A TABLE UPDATES REQUIRED =

	No table changes are required for this development.		No table changes are required for this development.
Line 163:		Line 163:


	== APPENDIX B QUOTE & DOCUMENT HISTORY ==		= APPENDIX B QUOTE & DOCUMENT HISTORY =


Line 170:		Line 170:


	=== References ===		== References ==

	IMAGE		IMAGE

	=== Glossary ===		== Glossary ==

	IMAGE		IMAGE
Line 181:		Line 181:


	=== Document History ===		== Document History ==


	IMAGE		IMAGE

	=== Authorised By ===		== Authorised By ==

	IMAGE		IMAGE

Kingj at 11:01, 4 February 2009

2009-02-04T11:01:01Z

Show changes

Kingj: New page: = 249804 PA-7DJDPE Amend Debrief Screen - TRIPDTL v2.54 = Copyright OBS Logistics © 2008 The information contained herein is the property of OBS Logistics and is supplied without liabi...

2009-02-04T10:48:45Z

New page

= 249804 PA-7DJDPE Amend Debrief Screen - TRIPDTL v2.54 =

Copyright OBS Logistics © 2008

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

== 1. FUNCTIONAL OVERVIEW ==

=== 1.1 Client Requirement ===
Amend Debrief Screen - TRIPDTL v2.54 - Reduce level of input, but retain ability to change by exception

Default into Order Debrief Screen.
When accessed from amended OVERVIEW v1.6(Waterfall) screen, open Trip highlighted in waterfall screen.
Pre populate 'Actual' times, 'Actual Weight' and 'Actual Volume' from 'Planned' where appropriate.
Move 'Set Status' button to more prominent position on Right hand side.
Widen or amend font of POD column to allow 'POD' label to be visible when highlighted.
Add Message on screen to 'Change Actual values if incorrect'
Allow multiple selection of orders for POD confirmation.

=== 1.2 Solution ===
When the Trip Debrief (TRIPDTL) screen is opened, whether from the Main Menu or when called from another screen, it will always default into the ‘Order Debrief’ tab, instead of the current ‘General’ tab.

The ‘Set Status’ button and associated Status drop down list will be moved to the right hand side of the screen, so it is more prominent. The 2 buttons originally next to ‘Set Status’ will be aligned on the left hand side; these include ‘Add Order’ and ‘Calc Time’.

When the ‘Debrief’ button in the Waterfall (TRIP_OVERVIEW) screen is clicked, the Trip Debrief (TRIPDTL) screen will be opened and the Trip Details of the currently selected Trip will be passed in.

A new button will be placed on the TRIPDTL screen, on the left side of the Save button below the Actuals input area. It will be named ‘Set Actuals’, and when clicked will pre-populate all the Actual Arrive and Depart Times, and Save these. It will also include the functionality to allow the user to Debrief by Exception.

This is achieved through the following process:
User enters Actual Date/Times only at stops that do not match their Planned Date/Times
User clicks new ‘Set Actuals’ button and the system automatically pre-populates the other stops Actuals.

System will not pre-populate Stop Actuals if they can not be met when compared to previous stop Actuals entered manually by the user
E.g If the manually entered Actual Depart time at Stop 2 is after the Planned Arrive time at Stop 3, the system will not pre-populate Stop 3 Actuals as it is not possible to meet this Planned Arrive deadline when compared to the Actual Depart Time at Stop 2.

In the Order Debrief tab 2 new buttons will be added to allow pre-population of Actual Quantities:
• The first one will be placed directly below the ‘Actual Despatched’ input area and named ‘Set Desp’. This will pre-populate ‘Actual Despatched’, ‘Actual Weight’ and ‘Actual Volume’ for all Order Lines. This also has the Debrief by Exception functionality, where if the user manually enters Actuals for 1 order line and clicks ‘Set Desp’ all other Order Line quantities will be pre-populated, except those manually entered.
• The second button will be placed below the ‘Actual Delivered’ input area and named ‘Set Del’. This button will only pre-populate ‘Actual Delivered’ quantities, and again, it has the Debrief by Exception functionality.

‘POC’ and ‘POD’ column buttons will be amended so that the Text is visible when an Order Line is in focus.

Also in the Order Debrief tab, 2 new buttons will be placed below the current ‘POC’ and ‘POD’ columns of buttons. They will be named ‘POC All’ and ‘POD All’. They will have the same functionality as the current ‘POC’ and ‘POD’ buttons, except that instead of only applying a POC/POD to the corresponding Order Line, they will apply a POC or POD to all Order Lines in the Order Debrief tab. If some Order Lines have a POC/POD already applied, then the ‘POC All’/’POD All’ will only apply POC/POD to those that do not have a POC/POD. Please note than these 2 buttons will not include the functionality to Remove All POC/POD. This will have to be done by individual line using the current ‘POC’ or ‘POD’ buttons next to an Order Line.

The current ‘Non-Conformance’ button and ‘POD/CMR No.’ Text Box will be moved down a line to make space for the new buttons.

Finally, there will be an overall ‘Set All Actuals’ button placed on the bottom right hand side of the TRIPDTL screen. This will be used to pre-populate all Actuals with the current Planned Quantities. This is only to be used if there is no Exceptions during Debrief as it will pre-populate all Stops ‘Actual Arrive Dates/Times’ and ‘Depart Times’, all Orders ‘ Actual Despatched’, ‘Actual Delivered’, ‘Actual Weight’ and ‘Actual Volumes’ and then automatically Save all Actuals.

RIO includes change request for ‘Add Message on screen to 'Change Actual values if incorrect'’, but this will not be required due to the nature of the new functionality.

=== 1.3 Scope ===
This change will be applied to system version 10.6 on CONTST and once approved CONPRD. This was requested by Consumer Networks, but as this is an improvement to current functionality, it will be released over time to all contracts, excluding SAR as it has its own code stream for screen TRIPDTL.