255576 - Revision history

Middletong at 13:33, 10 September 2009

2009-09-10T13:33:41Z

← Older revision		Revision as of 15:33, 10 September 2009
Line 163:		Line 163:


	== Authorised By ==		= Authorised By =
	{\| Border="1"		{\| Border="1"
	\| '''''Matt Crisford'''''		\| '''''Matt Crisford'''''

Middletong at 13:33, 10 September 2009

2009-09-10T13:33:19Z

← Older revision		Revision as of 15:33, 10 September 2009
Line 1:		Line 1:
	==255576 PA-7JYHVP / Order Debrief Return Option==		=255576 PA-7JYHVP / Order Debrief Return Option=

	Copyright OBS Logistics © 2009		Copyright OBS Logistics © 2009
Line 5:		Line 5:
	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		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


			= Functional Overview =


Line 67:		Line 69:


	== Functional Decsription ==		= Functional Decsription =
	The returns process will be available in the Trip Debrief screen, in the Order Debrief tab.		The returns process will be available in the Trip Debrief screen, in the Order Debrief tab.
	When the delivered quantity is less than the despatched quantity a popup message will be displayed on screen		When the delivered quantity is less than the despatched quantity a popup message will be displayed on screen
Line 118:		Line 120:


	== References ==		= References =
	{\| Border="1"		{\| Border="1"
	\| <center>'''Ref No'''</center>		\| <center>'''Ref No'''</center>
Line 133:		Line 135:


	== Glossary ==		= Glossary =
	Not Available		Not Available


	== Document History ==		= Document History =
	{\| Border="1"		{\| Border="1"
	\| <center>'''Version'''</center>		\| <center>'''Version'''</center>

Middletong at 12:58, 10 September 2009

2009-09-10T12:58:19Z

← Older revision		Revision as of 14:58, 10 September 2009
Line 54:		Line 54:

	If the user selects not to create a RETURN order, the return process will be cancelled and they will be asked if they want to create a REBOOK order as per current functionality.		If the user selects not to create a RETURN order, the return process will be cancelled and they will be asked if they want to create a REBOOK order as per current functionality.



			== Scope ==
			This change will be applied to system version 10.5.0 on CONTST and once approved CONPRD.


			== Data ==
			The Return process will create new sch_ord and sch_order_line records. The EXTERNAL_REF and INFO fields of the new records will be updated as will the QTY ordered, this will be set to the difference between despatched and delivered.

			A new record will be added into the SCH_ORD_NON_CONFORM table. All audit tables will be updated in line with existing functionality using database triggers.


			== Functional Decsription ==
			The returns process will be available in the Trip Debrief screen, in the Order Debrief tab.
			When the delivered quantity is less than the despatched quantity a popup message will be displayed on screen

			[[Image:255576_2.png]]

			The Delivered quantity is less than the Despatched quantity, please press the Non Conformance button if you wish to enter a non conformance, a return and /or re-book the Order”

			In addition to the message being displayed, two variables NEED_TO_REBOOK and NEED_TO_RETURN will be set to Y.

			After selecting OK, the user will select Non-Conformance. The non-conformance screen will be displayed. There are no amendments required for this screen.

			Once the non-conformance information is entered and the user has selected OK, the system will check the values of the global variables NEED_TO_RETURN and NEED_TO_REBOOK. If NEED_TO_RETURN is equal to Y, a pop-up message will be displayed on screen

			“Do you want to return the quantity that has not been delivered?”

			If the user selects OK, they will be directed to the returns screen. This screen will be a copy of the re-book screen with some differences, the ‘to’ and ‘from’ locations will be set to null and must be populated by the user. There will be an additional field labelled: ‘Chargeable’, which will be displayed as a check box.

			Once this screen has been populated the return process will be launched, which copies the original order to a new return order. If the chargeable check box is not selected, all the financial data will be set to NULL in the new return order.

			The EXTERNAL_REF will have _RET concatenated at the end of the field and the INFO field will be populated with the value ‘RETURN’. This will be used to identify Return orders in the future.

			At the end of the return process a message will be displayed on screen

			“Do you want to rebook the quantity that has not been delivered?”

			[[Image:255576_3.png]]

			If the user selects OK, the re-book process will be launched. No changes will be made to this process. However, a minor functional change will be needed to prevent the re-booking of a return order.

			'''Return Records Functionality'''

			In order to maintain system integrity the following rules will be applied:

			'''>'''An order can be returned and then rebooked, creating 2 new orders.

			'''>'''A re-booked order can be re-booked

			'''>'''A re-booked order can be returned

			'''>'''A returned order cannot be RE-BOOKED or RETURNED. A new order should be generated.


			In short this means the system will not allow repeat ‘actions’ against a RETURN order.


			When a trip is debriefed and the despatched quantity is greater than the delivered quantity, a return check will run. If the order is a RETURN (_RET), the user will be asked to complete the non-conformance screen but will not be offered the chance to create a return or a re-book order, the message displayed will be: “The Delivered quantity is less than the Despatched quantity, please press the Non Conformance button if you wish to enter a non conformance for this RETURN order”

			A return order will be identified using the INFO field in the SCH_ORD table. When a return order is identified the global variables NEED_TO_RETURN and NEED_TO_REBOOK will be set to N, ensuring that the RETURN and REBOOK processes are not available.


			== References ==
			{\| Border="1"
			\| <center>'''Ref No'''</center>
			\| <center>'''Document Title & ID'''</center>
			\| <center>'''Version'''</center>
			\| <center>'''Date'''</center>

			\|-
			\| <center>1</center>
			\| EST 255576 PA-7JYHVP Order Debrief return option v1.doc
			\| <center>1</center>
			\| <center>14/11/08</center>
			\|}


			== Glossary ==
			Not Available


			== Document History ==
			{\| Border="1"
			\| <center>'''Version'''</center>
			\| <center>'''Date'''</center>
			\| <center>'''Status'''</center>
			\| <center>'''Reason'''</center>
			\| <center>'''Initials'''</center>

			\|-
			\| <center>1a</center>
			\| <center>26/11/08</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>SW</center>

			\|-
			\| <center>1</center>
			\| <center>26/11/08</center>
			\| <center>Issue</center>
			\| Reviewed and Issued
			\| <center>MJC</center>
			\|}


			== Authorised By ==
			{\| Border="1"
			\| '''''Matt Crisford'''''
			\| Development Manager
			\|

			\|-
			\| '''''Suk Sandhu'''''
			\| TMSCC MTS Product Manager
			\|

			\|}

Middletong: /* Solution */

2009-09-10T12:51:03Z

Solution

← Older revision		Revision as of 14:51, 10 September 2009
Line 47:		Line 47:

	'''>'''Financial information from the original order will not be inherited by the return order, if the return order has been flagged as NOT CHARGEABLE. Package OMS.copy_order and OMS.copy_order_for _rebook will be copied and re-written for return orders.		'''>'''Financial information from the original order will not be inherited by the return order, if the return order has been flagged as NOT CHARGEABLE. Package OMS.copy_order and OMS.copy_order_for _rebook will be copied and re-written for return orders.


	At the end of the RETURN process, the value of the existing global variable: NEED_TO_REBOOK will be checked. If this is Y, the message ‘Do you want to rebook the rest of the order’ will be displayed. If the user selects yes, the RE-BOOK process will be run as per current functionality.		At the end of the RETURN process, the value of the existing global variable: NEED_TO_REBOOK will be checked. If this is Y, the message ‘Do you want to rebook the rest of the order’ will be displayed. If the user selects yes, the RE-BOOK process will be run as per current functionality.

Middletong: /* Solution */

2009-09-10T12:50:33Z

Solution

← Older revision		Revision as of 14:50, 10 September 2009
Line 42:		Line 42:
	The RETURN procedure will be almost identical to the REBOOK procedure with the following exceptions:		The RETURN procedure will be almost identical to the REBOOK procedure with the following exceptions:

	~~'''Customer''' Ref will be appended with _RET~~

			'''>'''Customer Ref will be appended with _RET

	'''~~Financial~~''' information from the original order will not be inherited by the return order, if the return order has been flagged as NOT CHARGEABLE. Package OMS.copy_order and OMS.copy_order_for _rebook will be copied and re-written for return orders.
			'''>'''Financial information from the original order will not be inherited by the return order, if the return order has been flagged as NOT CHARGEABLE. Package OMS.copy_order and OMS.copy_order_for _rebook will be copied and re-written for return orders.

	At the end of the RETURN process, the value of the existing global variable: NEED_TO_REBOOK will be checked. If this is Y, the message ‘Do you want to rebook the rest of the order’ will be displayed. If the user selects yes, the RE-BOOK process will be run as per current functionality.		At the end of the RETURN process, the value of the existing global variable: NEED_TO_REBOOK will be checked. If this is Y, the message ‘Do you want to rebook the rest of the order’ will be displayed. If the user selects yes, the RE-BOOK process will be run as per current functionality.

Middletong: /* Solution */

2009-09-10T12:49:54Z

Solution

← Older revision		Revision as of 14:49, 10 September 2009
Line 36:		Line 36:

	'''>'''All text will be relevant to RETURN and not REBOOK.		'''>'''All text will be relevant to RETURN and not REBOOK.


	Once the user has populated the screen, and selected OK, the return procedure will run.		Once the user has populated the screen, and selected OK, the return procedure will run.

Middletong: /* Solution */

2009-09-10T12:49:36Z

Solution

← Older revision		Revision as of 14:49, 10 September 2009
Line 27:		Line 27:

	The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:		The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:


	'''>'''The location to and from fields will be set to null, and must be populated.		'''>'''The location to and from fields will be set to null, and must be populated.

Middletong: /* Solution */

2009-09-10T12:49:19Z

Solution

← Older revision		Revision as of 14:49, 10 September 2009
Line 28:		Line 28:
	The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:		The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:

	'''>'''The~~'''~~ location to and from fields will be set to null, and must be populated.		'''>'''The location to and from fields will be set to null, and must be populated.

Middletong: /* Solution */

2009-09-10T12:48:48Z

Solution

← Older revision		Revision as of 14:48, 10 September 2009
Line 28:		Line 28:
	The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:		The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:

	'''The''' location to and from fields will be set to null, and must be populated.		'''>'''The''' location to and from fields will be set to null, and must be populated.


	'''A''' CHARGEABLE radio button will be displayed		'''>'''A CHARGEABLE radio button will be displayed


	'''~~All~~''' text will be relevant to RETURN and not REBOOK.		'''>'''All text will be relevant to RETURN and not REBOOK.

	Once the user has populated the screen, and selected OK, the return procedure will run.		Once the user has populated the screen, and selected OK, the return procedure will run.

Middletong: New page: ==255576 PA-7JYHVP / Order Debrief Return Option== Copyright OBS Logistics © 2009 The information contained herein is the property of OBS Logistics and is supplied without liability for...

2009-09-10T12:47:01Z

New page

==255576 PA-7JYHVP / Order Debrief Return Option==

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

== Client Requirement ==
TripDtl v2.56 – Non Conformance Screen - add a button to create an image of the selected order with a suffix of [RET] to specify an order that has to be returned (decision made at delivery point) with the ability to edit the detail to cover chargeable or not, storage location if not direct return and collection date.

Added by SS 02/10/08 - When creating a non conformance user should have the option to create a return order in similar fashion to current rebook process, followed by the option to create a rebook order also where required.

When order details for the return order are displayed user should be able to enter both from and to location. Return order should be identifiable by adding _RET1 to the customer ref.

== Solution ==
Changes will be applied to the Trip Detail screen, in the Order Debrief tab.

This process will be driven by the delivered qty being less than the despatched qty. The when-validate-item trigger will run after the delivered qty is entered in the order debrief tab.

If the qty is less than the despatched qty, currently a pop-up message will be displayed informing the user that they should select non conformance and create a RETURN order. A global variable called NEED_TO_RETURN will be set to ‘Y’.

[[Image:255576_1.png]]

Once the non conformance screen has been populated, the user will select the save button. At this point the value of NEED_TO_RETURN variable is checked. If this is set to Y, then the user is asked ‘Do you want to create a RETURN order for the undelivered stock’ If the user selects yes, the RETURN screen is called.

The RETURN screen will be almost identical to the RE-BOOK screen with the following exceptions:

'''The''' location to and from fields will be set to null, and must be populated.

'''A''' CHARGEABLE radio button will be displayed

'''All''' text will be relevant to RETURN and not REBOOK.

Once the user has populated the screen, and selected OK, the return procedure will run.

The RETURN procedure will be almost identical to the REBOOK procedure with the following exceptions:

'''Customer''' Ref will be appended with _RET

'''Financial''' information from the original order will not be inherited by the return order, if the return order has been flagged as NOT CHARGEABLE. Package OMS.copy_order and OMS.copy_order_for _rebook will be copied and re-written for return orders.

At the end of the RETURN process, the value of the existing global variable: NEED_TO_REBOOK will be checked. If this is Y, the message ‘Do you want to rebook the rest of the order’ will be displayed. If the user selects yes, the RE-BOOK process will be run as per current functionality.

We must ensure that the process of creating the RETURN order does not inhibit the ability to create the REBOOK order. The REBOOK process must be run against the original order and not the RETURN order record, for this reason we cannot clear the original order record from the screen after the RETURN process has completed.

If the user selects not to create a RETURN order, the return process will be cancelled and they will be asked if they want to create a REBOOK order as per current functionality.