Admin: /* Functional Description */

2012-05-11T15:33:22Z

Functional Description

← Older revision		Revision as of 17:33, 11 May 2012
Line 542:		Line 542:
	The list item against order non conformance is currently populated when the form is first opened. This will be changed to populate the list when an order has been selected and the Non Conformance button is pressed.		The list item against order non conformance is currently populated when the form is first opened. This will be changed to populate the list when an order has been selected and the Non Conformance button is pressed.

	[[Image:]]		[[Image:292360_10.png]]

	The LOV against the order items reason code will be populated dynamically based on the cost centre and cust group of the order selected.		The LOV against the order items reason code will be populated dynamically based on the cost centre and cust group of the order selected.

	[[Image:]]		[[Image:292360_11.png]]

Admin: /* Functional Description */

2012-05-11T15:26:28Z

Functional Description

← Older revision		Revision as of 17:26, 11 May 2012
Line 482:		Line 482:
	The Insert reason code canvas will be expanded to allow space for the two new fields.		The Insert reason code canvas will be expanded to allow space for the two new fields.

	[[Image:]]		[[Image:292360_1.png]]

	The edit canvas will also be changed to include the fields.		The edit canvas will also be changed to include the fields.

	[[Image:]]		[[Image:292360_2.png]]

	An LOV will be added for COST_CENTRE and CUST_GROUP. Each LOV will included a ‘+’ value. If no value is entered in the COST_CENTRE or CUST_GROUP field the value should default to ‘+’.		An LOV will be added for COST_CENTRE and CUST_GROUP. Each LOV will included a ‘+’ value. If no value is entered in the COST_CENTRE or CUST_GROUP field the value should default to ‘+’.
Line 494:		Line 494:
	The Interface Errors screen references SCH_REASON_CODE when displaying the PO Outbound information. The post query trigger on block INT_PO_OUTBOUND_NON_CONFORM will be changed to reference the customer (cust group) and cost centre of the purchase order when looking for the reason code.		The Interface Errors screen references SCH_REASON_CODE when displaying the PO Outbound information. The post query trigger on block INT_PO_OUTBOUND_NON_CONFORM will be changed to reference the customer (cust group) and cost centre of the purchase order when looking for the reason code.

	[[Image:]]		[[Image:292360_3.png]]

	Order Debrief		Order Debrief
Line 502:		Line 502:
	Collection		Collection

	[[Image:]]		[[Image:292360_4.png]]

	Delivery		Delivery

	[[Image:]]		[[Image:292360_5.png]]

	Orders		Orders
Line 512:		Line 512:
	The Orders form will be changed to include the cost centre and customer (cust group) for the orders to segregate the reason codes available. The reason codes can be selected in a list for the order non conformance. The population of this list will be moved to the processing behind the non conformance button so the current orders details can be used to segregate the reason codes.		The Orders form will be changed to include the cost centre and customer (cust group) for the orders to segregate the reason codes available. The reason codes can be selected in a list for the order non conformance. The population of this list will be moved to the processing behind the non conformance button so the current orders details can be used to segregate the reason codes.

	[[Image:]]		[[Image:292360_6.png]]

	The order items reason codes are validated against an LOV. This LOV will be dynamically set to restrict the reason codes based on the cost centre and customer (cust group) of the order.		The order items reason codes are validated against an LOV. This LOV will be dynamically set to restrict the reason codes based on the cost centre and customer (cust group) of the order.

	[[Image:]]		[[Image:292360_7.png]]

	The post query trigger on the item non conformance block will also be change to retrieve the correct description based on the order.		The post query trigger on the item non conformance block will also be change to retrieve the correct description based on the order.
Line 526:		Line 526:
	The LOV’s for the 3 reason code fields will be set dynamically when a PO is edited to populate the lists based on the PO’s cost centre and customer.		The LOV’s for the 3 reason code fields will be set dynamically when a PO is edited to populate the lists based on the PO’s cost centre and customer.

	[[Image:]]		[[Image:292360_8.png]]

	Tracking		Tracking
Line 534:		Line 534:
	The List for the reason codes is currently populated when the form is first opened. This will be changed to populate when the Non Conformance button is pressed for a particular order allowing the orders details to be used to segregate the list of reason codes.		The List for the reason codes is currently populated when the form is first opened. This will be changed to populate when the Non Conformance button is pressed for a particular order allowing the orders details to be used to segregate the list of reason codes.

	[[Image:]]		[[Image:292360_9.png]]

	Trip Debrief		Trip Debrief
Line 751:		Line 751:

	\|}		\|}

	=AUTHORISED BY=		=AUTHORISED BY=
	{\| Border="1"		{\| Border="1"

Admin: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Segrgate Reason Codes to Contract|Reference=292360 PM-8LZN7Z|Version=1.0|Date=17/11/11|Sysver=10.7|Client=DHL C-TMS}} == Client Requireme...

2012-05-11T15:18:32Z

New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Segrgate Reason Codes to Contract|Reference=292360 PM-8LZN7Z|Version=1.0|Date=17/11/11|Sysver=10.7|Client=DHL C-TMS}} == Client Requireme...

Show changes

292360 - Revision history

Admin: /* Functional Description */

Admin: /* Functional Description */

Admin: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Segrgate Reason Codes to Contract|Reference=292360 PM-8LZN7Z|Version=1.0|Date=17/11/11|Sysver=10.7|Client=DHL C-TMS}} == Client Requireme...