291358 - Revision history

Middletong at 12:43, 16 October 2012

2012-10-16T12:43:22Z

← Older revision		Revision as of 14:43, 16 October 2012
Line 277:		Line 277:

	[[Image:291358_19.png]]		[[Image:291358_19.png]]

			=REFERENCES=

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

			\|-
			\| <center>1</center>
			\| EST-291358 MS-8KNFRL Order Addresses DU and Del Type
			\| <center>1.0</center>
			\| <center>13/09/11</center>
			\|}


			=DOCUMENT HISTORY=

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

			\|-
			\| <center>0.1</center>
			\| <center>05/10/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>CAK</center>

			\|-
			\| <center>0.2</center>
			\| <center>06/10/11</center>
			\| <center>Draft</center>
			\| Reviewed
			\| <center>MJC</center>

			\|-
			\| <center>0.3</center>
			\| <center>10/10/11</center>
			\| <center>Draft</center>
			\| Revised
			\| <center>CAK</center>

			\|-
			\| <center>0.4</center>
			\| <center>11/10/11</center>
			\| <center>Draft</center>
			\| Revised
			\| <center>CAK</center>

			\|-
			\| <center>0.5</center>
			\| <center>12/10/11</center>
			\| <center>Draft</center>
			\| Revised
			\| <center>CAK</center>

			\|-
			\| <center>1.0</center>
			\| <center>12/10/11</center>
			\| <center>Issue</center>
			\| Reviewed and Issued
			\| <center>MJC</center>

			\|-
			\| <center>1.1</center>
			\| <center>13/10/11</center>
			\| <center>Draft</center>
			\| Create table changed to Alter table
			\| <center>CAK</center>

			\|-
			\| <center>1.2</center>
			\| <center>19/10/11</center>
			\| <center>Draft</center>
			\| Changes after review by S Allen
			\| <center>CAK</center>

			\|-
			\| <center>2.0</center>
			\| <center>19/10/11</center>
			\| <center>Issue</center>
			\| Reviewed and Issued
			\| <center>MJC</center>

			\|-
			\| <center>2.1</center>
			\| <center>24/10/11</center>
			\| <center>Draft</center>
			\| Revised
			\| <center>CAK</center>

			\|-
			\| <center>3.0</center>
			\| <center>24/10/11</center>
			\| <center>Issue</center>
			\| Reviewed and Issued
			\| <center>MJC</center>

			\|-
			\| <center>3.1</center>
			\| <center>25/10/11</center>
			\| <center>Draft</center>
			\| Revised
			\| <center>CAK</center>

			\|-
			\| <center>4.0</center>
			\| <center>27/10/11</center>
			\| <center>Issue</center>
			\| Reviewed and Issued
			\| <center>MJC</center>
			\|}


			=AUTHORISED BY=



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

			\|-
			\| '''''Peter Greer'''''
			\| TMSCC MTS Product Manager
			\|

			\|}

Middletong at 11:44, 16 October 2012

2012-10-16T11:44:48Z

← Older revision		Revision as of 13:44, 16 October 2012
Line 275:		Line 275:

	The vehicle type will also be added to the configurable layout in the order well of the Trip Planning, Trip Manipulation and Execution forms. As with all other fields in the configurable layout it is a display only field. An example of the configurable layout in Trip Planning is shown below, the Trip Manipulation and Execution screens will have similar functionality and will need to be changed accordingly.		The vehicle type will also be added to the configurable layout in the order well of the Trip Planning, Trip Manipulation and Execution forms. As with all other fields in the configurable layout it is a display only field. An example of the configurable layout in Trip Planning is shown below, the Trip Manipulation and Execution screens will have similar functionality and will need to be changed accordingly.

			[[Image:291358_19.png]]

Middletong at 10:52, 16 October 2012

2012-10-16T10:52:49Z

← Older revision		Revision as of 12:52, 16 October 2012
Line 257:		Line 257:

	[[Image:291358_16.png]]		[[Image:291358_16.png]]

			A new system function will be created called: ALLOW_HOLD_ORDERS and only users with access to this function will be allowed to set orders to On Hold. If the current user does not have this function access the menu option should not available for selection. Only UNSCHEDULED or INVALID orders can be set to a status of On Hold.

			When the menu option is selected a message should be displayed asking the user to confirm the status change. When confirmation is received the OMS.CHANGE_STATUS function should be called passing the required OMS_REF and a status of ON-HOLD. If the function can not change the status an appropriate error should be displayed to the user.

			An additional item “Release from Hold” will also be added to the menu, access to this functionality will be controlled by access to the ALLOW_HOLD_ORDERS system function. Only orders currently at On Hold status are valid to be selected for this action, if an order is selected at any other status an error message should be displayed. When a valid order is selected a message should be displayed asking the user to confirm the status change. When confirmation is received the OMS.CHANGE_STATUS should be called passing the required OMS_REF and a status of UNSCHEDULED. If the function can not change the status an appropriate error should be displayed to the user. The option to set an Order to On Hold should also be added to the right click menu in the order well of the Trip Planning, Trip Manipulation and Execution screens an example of Trip Planning is shown below the Trip Manipulation and Execution screens will have a similar menu.

			[[Image:291358_17.png]]

			The access should be controlled in the same way and the functionality processed in the same way as for the orders screen. Orders at ON HOLD status can not be planned on to a trip and once an order is set to this status it should no longer be available in the order well. The TRM package will be amended to not allow orders at ON-HOLD status to be added to a trip.

			==Vehicle Type==

			The vehicle will be loaded if present by the CSV and XML uploads. It can also be manually keyed using the orders form. If entered using the orders form the value should be selected form a list built from the RES_TRAILER_TYPE table. A suggested layout is shown below.

			[[Image:291358_18.png]]

			The vehicle type will also be added to the configurable layout in the order well of the Trip Planning, Trip Manipulation and Execution forms. As with all other fields in the configurable layout it is a display only field. An example of the configurable layout in Trip Planning is shown below, the Trip Manipulation and Execution screens will have similar functionality and will need to be changed accordingly.

Middletong at 10:41, 16 October 2012

2012-10-16T10:41:46Z

Show changes

Middletong at 09:52, 16 October 2012

2012-10-16T09:52:36Z

← Older revision		Revision as of 11:52, 16 October 2012
Line 1:		Line 1:
	{{Doc_Title\|System=FUNCTIONAL SPECIFICATION\|Title=Order Addresses, DU & Del Type\|Reference=FS 291358 MS-8KNFRL\|Version=4.0\|Date=27/10/11\|Sysver=10.7\|Client=DHL C-TMS}}		{{Doc_Title\|System=FUNCTIONAL SPECIFICATION\|Title=Order Addresses, DU & Del Type\|Reference=FS 291358 MS-8KNFRL\|Version=4.0\|Date=27/10/11\|Sysver=10.7\|Client=DHL C-TMS}}

			=FUNCTIONAL OVERVIEW=

			==Client Requirement==

			Create child address and association with NR node MSP on orders for final delivery location. Order stores collection location, NR Node MSP main address location and full delivery location. Capture NR cost code (as additional reference) for each order (all orders except non Heavy have to carry a NR cost centre to support finance reporting).
			Include weight for commodity product DU Type and calculate weight of order for planning.

			Include product weight for commodity product DU Type and calculate weight of order for planning.

			Derive the order delivery type based on lead time order received to collection date. Maintain delivery type rules as master data to allow C-TMS to automatically set as Emergency, Next Day , Normal based on lead time.

			Extend Locations view in order to display contact name.

			Function to split orders. Copy from original to make x new orders and set unit qty on each.

			Interface and order maintenance must allow length to be defined and this length value to be visible in order well. Needed to differentiate rail lengths ordered and loading compatibility.

			Additional status to set orders to On-HOLD. This disables the order from planning.

			Required vehicle type will be necessary as an attribute of order. This required vehicle type will need to show on the order well for planners to see and assign the necessary equipment.


			==Solution==

			<u>Addresses</u>

			Please see 291356 MS-8KNFBJ RIO: 1 - Order EDI & Order Quarantine for more details regarding changes for parent and child addresses to facilitate milk-round planning for DISC non Heavy orders. For Heavy orders (all non-Heavy accounts, the NR cost centre code will be captured using the Additional References functionality in C-TMS.

			<u>Product Weights</u>

			The Product Item table will be used to store the weight for a commodity / DU type. Alterations will be needed to store the DU type against this table and for the information to be used within the Order CSV and XML uploads and Manual Order Entry. The weight of the Order Item and the weight of the corresponding DU order line will be calculated based on weight for each unit quantity of product held in master data. The CSV import process will be enhanced for item weights to be calculated.

			<u>Delivery Types</u>

			The Delivery Type will be one of Emergency, Next Day or Standard C-TMS will be modified to calculate the appropriate Delivery Type based on the lead time of the order date time received to required collection date time. The rules to calculate the delivery trype are shown below. The Delivery Type drives the rating calculation, so for example Emergency is more expensive than Next Day or Standard.

Middletong: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Order Addresses, DU & Del Type|Reference=FS 291358 MS-8KNFRL|Version=4.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}

2012-10-16T09:48:02Z

New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Order Addresses, DU & Del Type|Reference=FS 291358 MS-8KNFRL|Version=4.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}

New page

{{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Order Addresses, DU & Del Type|Reference=FS 291358 MS-8KNFRL|Version=4.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}