290936 - Revision history

Middletong at 14:05, 18 October 2012

2012-10-18T14:05:53Z

← Older revision		Revision as of 16:05, 18 October 2012
Line 423:		Line 423:

	[[Image:290936_8.png]]		[[Image:290936_8.png]]

			If a consolidated order is selected in the screen and the user attempts to edit the details a warning message indicating the consolidated orders can not be edited will be displayed to the user. The user will be able to view the order details but all fields will be protected against update. Validate existing access control functions to ensure no overlap or conflict.

			A button will be provided in the screen that will allow the order to be removed from the shipment. When this button is pressed the order’s status will be changed back to Unscheduled. All of the order lines that were against a shipment will be removed from the shipment. The order can only be removed from the shipment if the shipment status is OPEN or PENDING. If the shipment status is at another status a warning message will be displayed and the action will be stopped (this will be managed as a manual exception covered within SOP’s within the operation).

			A new field called Shipment Status will be added to the Order Details screen. This will show the status of the shipment. For consolidated orders the field will show the status of the shipment that the order has been included in.

			When a shipment or consolidated order is being viewed, double clicking the Shipment Status will call the shipment enquiry screen. This will allow the user to easily see the shipment details and the other orders included in the shipment.

			If a shipment is being viewed a double click option will be added to the lines on the shipment. Double clicking on the line will take the user to the order details for the line.

			==Changes to Customer Screen==

			A button will be added to the customers screen (CUST_COST.fmx) labelled consolidation. Pressing this button will show a pop up window which will allow the compatible consolidation customers to be entered.

			The pop up window will consist of a customer id field, customer id for consolidation and a customer name. The customer ID field will include an LOV to allow a look up to take place.

			When saved the records will be added to the new table ORG_CUSTOMER_CONSOLIDATION. A record will also be written as a reverse of the record being entered, this will indicate that the consolidation works both ways.

			[[Image:290936_9.png]]

			A check box will also be included labelled ‘ALL’, when this is checked the customer is considered to be compatible with all other customers when consolidating.

			[[Image:290936_10.png]]

			==Changes to Product Screen==

			A change will be made to the products screen (PRODUCT.fmx). A new button will be added labelled Add Restrictions. This button will call a pop up window that will allow the list of products that are compatible with the current selected product type to be entered.

			One or more restricted products can be added in this screen. If the product type can be consolidated with any other product types an ‘ALL’ check box will be available. This box will be ticked by default.

			The pop up window will contain the Product Type, Temperature Type and Product Name. An LOV will be available to allow users to look up product types.

			[[Image:290936_11.png]]

			==Changes to Resource Screen==

			A new field will be added to the carrier edit screen to allow the maximum DU size for a carrier to be entered.

			[[Image:290936_12.png]]

			This will be used when deciding whether an order can be added to a shipment, if a carrier has already been assigned.

			==Changes to Trip Screens==

			The scheduled order section of the Trip Sum and Trip Planning screens will also be changed to allow a user to drill down into the Shipment Enquiry screen rather than the orders screen when the order is a shipment order.

			If the order on the trip is a shipment order double clicking on the order will bring up the Shipment Enquiry screen, showing the details of this shipment.

			[[Image:290936_13.png]]

			Shipment Status and Shipment Ref will be added to the list of configurable fields in the unscheduled orders section of the screen. This will allow them to be displayed as required.

			This will also apply when viewing the order details from the Execution screen. If the order is a shipment order the Shipment Enquiry screen will be displayed when choosing the View Order Details option.

			[[Image:290936_14.png]]

			'''DU Mapping'''

			Orders entered into C-TMS either manually, via .CSV import or from WISE will contain specific DU information. Orders from Unison will be treated slightly differently:

			Unison will calculate the pallet equivalent of the order based on the volumetric data and pallet type held against the SKU. This value will be passed to C-TMS and rounded up to the nearest integer to give the pallet DU quantity for an order.

			A separate RIO will be raised to apply additional logic and functionality within Unison to derive the associated box types and quantities for parcel orders which will also be passed to C-TMS.

			An additional calculation will need to take place in C-TMS around mapping inner and outer DU’s, this should be managed via a table mapping inner DU’s to outer DU’s to work as part of consolidated shipment management. This will take place at Shipment Order level. This will prevent shipments scheduled to parcel carriers automatically becoming pallets due to the new max shipment DU size constraint. A recalculation function should be available to allow recalculation at shipment order level in the instance where a shipment order is manually moved from a carrier to own fleet.

			=DOCUMENT HISTORY=

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

			\|-
			\| <center>0.1</center>
			\| <center>14/09/11</center>
			\| <center>Draft</center>
			\| Initial version
			\| <center>DNG</center>

			\|-
			\| <center>0.1</center>
			\| <center>30/09/11</center>
			\| <center>Draft</center>
			\| Review of the initial version
			\| <center>PJH</center>

			\|-
			\| <center>1.2</center>
			\| <center>04/11/11</center>
			\| <center>Amendment</center>
			\| Changes after review
			\| <center>DNG</center>

			\|-
			\| <center>2.0</center>
			\| <center>07/11/11</center>
			\| <center>Issue</center>
			\| Issued to client
			\| <center>PJH</center>
			\|}


			=AUTHORISED BY=



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

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

			\|}

Middletong at 13:11, 18 October 2012

2012-10-18T13:11:30Z

Show changes

Middletong: /* Creating Shipments */

2012-10-18T11:31:16Z

Creating Shipments

← Older revision		Revision as of 13:31, 18 October 2012
Line 208:		Line 208:
	[[Image:290936_3.png]]		[[Image:290936_3.png]]

	The order collection windows of the shipment order will be set as the date the shipment is created and Late Del date of the shipment.		The order collection windows of the shipment order will be set as the date the shipment is created and Late Del date of the shipment.

			[[Image:290936_4.png]]

			If an order is available to be added to a shipment but the shipment is at maximum capacity the order will be left off the shipment. If more than one order is available to go into a full shipment, a second shipment will be created to accommodate these orders. This will continue until all orders have been consolidated.

			When a shipment is first created or when an order is added to a shipment a record will be written to the SCH_SHIPMENT_AUDIT table to provide a record of changes to the shipment.

			The SCH_SHIPMENT_AUDIT record will contain

			*Audit ID – Generated sequence number.
			*Shipment ID – Oms Reference of the shipment
			*Action – Indication that a shipment has been created or an order added.
			*Shipment Change – Change description or any errors or warnings related to the action. Will include the order oms reference if an order is added or deleted from the shipment.
			*Created Time – Time of action.
			*Created By – Username of the user performing the action
			*Other changes to key fields on shipment order to be audited i.e. order 123456 added, latest delivery time changed from 14:00 to 13:00

			A new trigger TRG_SCH_ORD_AUDIT_SHIPMENT will be created on the SCH_ORD table. When an order that contains a shipment status is added or removed a record will be written to the shipment audit table.

			A new database job will be created that will run every hour. The job will call a new procedure in DP_SHIPMENT that will set any shipments at a status of OPEN to a status of CLOSED. Any shipments at status PENDING will not be closed by this job.

			===Removing Orders from a Shipment===

			When an order is removed from a shipment, the corresponding order line will be removed from the shipment order. If the Shipment Order’s lines have been combined by DU_TYPE, the values from the order being removed will be deducted from the shipment lines.

			[[Image:290936_5.png]]

Middletong at 10:48, 18 October 2012

2012-10-18T10:48:50Z

← Older revision		Revision as of 12:48, 18 October 2012
Line 205:		Line 205:

	The order delivery windows will be set as the latest Early Del and earliest Late Del that can overlap all of the orders on the shipment. Each time a new order is added to the shipment these dates will be revised based on the consolidated orders windows.		The order delivery windows will be set as the latest Early Del and earliest Late Del that can overlap all of the orders on the shipment. Each time a new order is added to the shipment these dates will be revised based on the consolidated orders windows.

			[[Image:290936_3.png]]

			The order collection windows of the shipment order will be set as the date the shipment is created and Late Del date of the shipment.

Middletong at 10:44, 18 October 2012

2012-10-18T10:44:44Z

← Older revision		Revision as of 12:44, 18 October 2012
Line 188:		Line 188:

	When the shipment is closed, a process will run that combines lines of the same DU Type into one line. The new line will have the combined quantity, weight, volume and RPE of all the lines that have been combined.		When the shipment is closed, a process will run that combines lines of the same DU Type into one line. The new line will have the combined quantity, weight, volume and RPE of all the lines that have been combined.

			[[Image:290936_2.png]]

			The lines with a DU TYPE of ‘Carton’ have been combined to create a single line.


			Add parameter to recalculate DU’s at Shipment level. This will look to create a DU consolidation at shipment level so three orders each for a small box could become one shipment of one large box dependent on the associated DU mapping and potentially packing rules. This is to be scoped as a framework for future enhancements and will not initially be required for Rigel or Prospero.
			N.B. Further discussions with DHL are taking place regarding this functionality.


			The status of the consolidated orders will be changed to ‘CONSOLIDATED’, this will ensure they can easily be identified and are not included in the scheduling process.

			A new column SHIPMENT_STATUS will be added to SCH_ORD to hold the shipment status. This status will be visible in the orders screen.

			A new column SHIPMENT_REF will be added to SCH_ORD. When an order is added to a shipment the shipments OMS ref will be entered against the consolidation order. If during the consolidation process an order cannot be included with any other orders or shipments the SHIPMENT_REF will be set to its own OMS_REF.

			The order delivery windows will be set as the latest Early Del and earliest Late Del that can overlap all of the orders on the shipment. Each time a new order is added to the shipment these dates will be revised based on the consolidated orders windows.

Middletong at 10:43, 18 October 2012

2012-10-18T10:43:16Z

← Older revision		Revision as of 12:43, 18 October 2012
Line 152:		Line 152:

	Each order line from the orders that have been consolidated will be included in the lines of the shipment. A new column will be added to SCH_ORDER_LINE to store the original order reference. This will allow the orders included in the shipment to be tracked.		Each order line from the orders that have been consolidated will be included in the lines of the shipment. A new column will be added to SCH_ORDER_LINE to store the original order reference. This will allow the orders included in the shipment to be tracked.

			==Consolidation Process==

			===Creating Shipments===

			The consolidation process can be run manually or automatically. The two processes will work in the same way. A new package DP_SHIPMENT will be created that will contain all the program units required to maintain and run the consolidation process. A function RUN_CONSOLIDATION will be called to start the consolidation process. All unscheduled orders will be considered for consolidation, unless a specific schedule is selected.

			Two new parameters will be added to control how many days in the past and future will be considered for consolidation. If a specific delivery date is passed into the consolidation process these parameters will determine which orders are to be consolidate. When running the process automatically the current date will be used.

			*Schedule range
			*From Location
			*To Location
			*Customer
			*Delivery Date (which drives the range controlled by the parameter above)

			These parameters are not mandatory and can be left blank.

			The function will return a Boolean value to indicate if the run was successful. The function will allow the input of the following parameters

			The consolidation process will loop through all the available orders. For each order a check will be made to determine if a shipment exists that can accommodate this order. The consolidation rules will be taken into consideration when looking for available shipments. If a shipment is available the order will be added to the shipment. The process will look for any Open shipments regardless of whether the shipments are scheduled onto a trip.

			If a shipment is not available for this order, the process will then look for other orders that could be combined into a shipment with this order. Again the consolidation rules must be considered, for each order. If one or more orders match the order being processed, they will be combined to create a shipment.

			If a shipment is available for this order the order will be added to the shipment by creating an order line on the shipment order that contains the details of the order being consolidated.

			Where an order can be scheduled onto multiple shipments the one with the earliest delivery date and time should be selected.

			When considering shipments that are currently scheduled onto a trip, if the shipment is crossdocked the capacity of the trailers for all trips containing this shipment must be considered.

			When one or more orders have been found that can be consolidated into a shipment a new “Shipment" order will be created. The order header will contain a new unique OMS Reference, and the From Location, To Location, Sched Name and Cost Centre of the orders being consolidated. These should all be the same for each of the orders being consolidated. If all orders have the same customer then this customer will be assigned to the new shipment order. If the customer is different the customer against the shipment order will show as CONSOL.

			Each order line from the orders being consolidated will then be assigned to the shipment order. All of the order line information from the consolidated orders will be stored as a line in the shipment order.

			[[Image:290936_1.png]]

			When the shipment is closed, a process will run that combines lines of the same DU Type into one line. The new line will have the combined quantity, weight, volume and RPE of all the lines that have been combined.

Middletong at 10:38, 18 October 2012

2012-10-18T10:38:29Z

Show changes

Middletong: New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=C-TMS Consolidation Process & Rules|Reference=FS 290936 NW-8KEMAG|Version=2.0|Date=07/11/11|Sysver=10.7|Client=DHL C-TMS}}

2012-10-18T10:12:37Z

New page: {{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=C-TMS Consolidation Process & Rules|Reference=FS 290936 NW-8KEMAG|Version=2.0|Date=07/11/11|Sysver=10.7|Client=DHL C-TMS}}

New page

{{Doc_Title|System=FUNCTIONAL SPECIFICATION|Title=C-TMS Consolidation Process & Rules|Reference=FS 290936 NW-8KEMAG|Version=2.0|Date=07/11/11|Sysver=10.7|Client=DHL C-TMS}}