Middletong at 09:33, 16 October 2012

2012-10-16T09:33:41Z

← Older revision		Revision as of 11:33, 16 October 2012
Line 274:		Line 274:
	\| <center>CAK</center>		\| <center>CAK</center>

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

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

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

Middletong at 09:13, 16 October 2012

2012-10-16T09:13:12Z

← Older revision		Revision as of 11:13, 16 October 2012
Line 167:		Line 167:

	The action buttons at the top of each column will allow the data in each column to be sorted in ascending or descending order.		The action buttons at the top of each column will allow the data in each column to be sorted in ascending or descending order.

			==Trip Generation==

			Trips will be planned using the pre-defined milk round template. The RTE package will be amended to include a new process SCHEDULE_MILK_ROUNDS. This process will receive the day number i.e. 01 for Monday, 02 for Tuesday and so on, the schedule name (this will always be the next days schedule) and the OWNING DEPOT for which the milk rounds should be created.

			The process will then obtain the details of all the relevant milk rounds for the specified day and one by one create a trip and trip stops for each stop on the specified day schedule. As trips are created they will be assigned a unique trip ID prefixed with “MFR” the arrival and departure times of the stops will be taken from the arrival and departure times on the milk round template for each stop and the stop updated to indicate fixed times. The trips will be created at PLANNED status. The route code will also be stored against the trip and can be used to identify the route template used for the trip. A further development “292354 – PM-8LZMNV Visibility of Route Code” will depending on the value of a system parameter add the route code to the trip id in the trip screens to aid the visibility of route codes.

			This process will be submitted as a scheduled job which will run at a specified time each day and create all the trips for the next day this will enable the order import to auto plan the orders onto the correct routes. The scheduled job will be specified using the EDI Maintenance screen which will control the run times of the jobs, this can set either as a regular interval or a specified time see examples below

			[[Image:291367_8.png]]

			[[Image:291367_9.png]]

			A cost centre based system parameter will be created called MILK_ROUND_TRIP_GENERATION. If this parameter is set to Y and the trip is at PLANNED status the standard trip validation functionality will not delete unused stops on these trips as future orders may still need to be planned which will use these stops. When creating trips, if a trip is found for the route code on the specified schedule which has been created manually the process will not create trips for that template.

			==Order Processing==

			When orders are received via the EDI order interface they will be stamped with the Day, Route and Node. The order import package will be amended and based on the value of a cost centre system parameter OMS_ADD_ORDER_TO_MILK a new process will plan these orders onto trips.

			ADD_ORD_TO_MILK_ROUND to the RTE package.

			The function will receive an OMS_REF, SCHED_NAME, ROUTE CODE and NODE as input parameters. This information will then be used to correctly identify which milk round template the order should be added to. If no valid trip is found the order will not be planned and will remain in the order well for manual planning. If a valid trip is found then the order will be planned onto this trip. If an order is received to be planned with a valid Day and ROUTE but the NODE does not exist in C-TMS the order will be added to the trip and a new stop created for the required NODE as the last stop on the trip.

			For more detail on the creation of new addresses refer to -
			291356 MS-8KNFBJ Order EDI and Order Quarantine

			If an order is received to be planned which has no day number or route code information the value of the MILK_ROUND_ORDERS parameter will be checked, if this value has not been set or is set to N the order will not be planned onto a trip. If the value of the parameter is set to Y the early delivery date of the order will be used to define the day number and schedule the order should be planned to. This information in conjunction with the delivery location of the order will then be used to identify the correct trip to allocate the order to. If no trip can be found the order will remain in the order well for manual planning.

			==Manual Planning==
			The trip planning and trip manipulation screens will be amended to add a new right click option to the order well to allow the planning of orders onto milk round routes. The value of the system parameter OMS_ADD_ORDER_TO_MILK will be checked to ensure that milk round processing is authorised for the selected orders, if milk round processing is not allowed an appropriate message will be displayed.
			If milk round processing is allowed the orders will be planned and the RTE.ADD_ORD_TO_MILK_ROUND procedure will be called to add the orders to the correct template. This will allow orders to be manually planned onto existing milk round trips.


			=REFERENCES=

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

			\|-
			\| <center>1</center>
			\| EST-291397 MS-8KNH8N Milk round Processing
			\| <center>1.0</center>
			\| <center>16/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>03/10/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>CAK</center>

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

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

			\|-
			\| <center>0.4</center>
			\| <center>05/10/11</center>
			\| <center>Draft</center>
			\| Reviewed
			\| <center>MJC</center>

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

			\|-
			\| <center>1.0</center>
			\| <center>06/10/11</center>
			\| <center>Issue</center>
			\| Reviewed and Issued
			\| <center>DJM</center>

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

			\|}


			=AUTHORISED BY=



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

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

			\|}

Middletong at 09:02, 16 October 2012

2012-10-16T09:02:55Z

Show changes

Middletong: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Milkround Processing|Reference=FS 291367 MS-8KNH8N|Version=2.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}

2012-10-16T08:42:39Z

New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Milkround Processing|Reference=FS 291367 MS-8KNH8N|Version=2.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}

New page

{{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Milkround Processing|Reference=FS 291367 MS-8KNH8N|Version=2.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}

291367 - Revision history

Middletong at 09:33, 16 October 2012

Middletong at 09:13, 16 October 2012

Middletong at 09:02, 16 October 2012

Middletong: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=Milkround Processing|Reference=FS 291367 MS-8KNH8N|Version=2.0|Date=27/10/11|Sysver=10.7|Client=DHL C-TMS}}