291805 - Revision history

Admin: /* Carrier Cost */

2012-05-03T09:50:52Z

Carrier Cost

← Older revision		Revision as of 11:50, 3 May 2012
Line 158:		Line 158:


	[[Image:]]		[[Image:291805_5.png]]

	The carrier contracts will be set up to rate based on the number of additional_stops. Fixed charges will be added for each trailer type. Carrier cost will always be generated from the cost per stop * additional delivery stops plus the relevant fixed cost based on the trailer type. A tariff will be generated per standard journey, which may be defined by planning region, postal region, country, postcode or location.		The carrier contracts will be set up to rate based on the number of additional_stops. Fixed charges will be added for each trailer type. Carrier cost will always be generated from the cost per stop * additional delivery stops plus the relevant fixed cost based on the trailer type. A tariff will be generated per standard journey, which may be defined by planning region, postal region, country, postcode or location.
Line 369:		Line 369:

	\|}		\|}


	=AUTHORISED BY=		=AUTHORISED BY=

Admin: /* Customer Contracts */

2012-05-03T09:46:56Z

Customer Contracts

← Older revision		Revision as of 11:46, 3 May 2012
Line 76:		Line 76:


	[[Image:]]		[[Image:291805_3.png]]

	The tier unit will be displayed as Add_Stops. Each tariff will have a charge per stop and a fixed charge which will be based on a specific trailer type. The standard journey tab will be used to set the ‘from’ and ‘to’ locations which may be defined as between any of the following planning region, postal region, postcode or country.		The tier unit will be displayed as Add_Stops. Each tariff will have a charge per stop and a fixed charge which will be based on a specific trailer type. The standard journey tab will be used to set the ‘from’ and ‘to’ locations which may be defined as between any of the following planning region, postal region, postcode or country.


	[[Image:]]		[[Image:291805_4.png]]

	A tariff will be required for each standard journey.		A tariff will be required for each standard journey.


	=== Maximum Stop Revenue ===		=== Maximum Stop Revenue ===

Admin: /* Tier Units */

2012-05-03T09:43:17Z

Tier Units

← Older revision		Revision as of 11:43, 3 May 2012
Line 63:		Line 63:


	[[Image:]]		[[Image:291805_2.png]]

	Functionality will be added to allow orders to be rated based on the number of additional stops on the trip the order has been scheduled on.		Functionality will be added to allow orders to be rated based on the number of additional stops on the trip the order has been scheduled on.

	The existing procedure in the rating engine which determines order quantities for each tier type will be amended to calculate quantities for the new ‘Add_Stop’ tier type. The count of stops will be based on the number of additional delivery stops, i.e any stop which performs an unload activity Trip Start (SU) and Trip End (CL) stops will not be included in revenue rating, however if a CL is delivering an order it will be included as an additional stop. Additional stops will be defined as the number of deliveries in addition to the delivery which has generated the maximum revenue. Collections will not be counted as an additional stop. A collection will be identified as an unload at an RDC, where the RDC is the to location on the order.		The existing procedure in the rating engine which determines order quantities for each tier type will be amended to calculate quantities for the new ‘Add_Stop’ tier type. The count of stops will be based on the number of additional delivery stops, i.e any stop which performs an unload activity Trip Start (SU) and Trip End (CL) stops will not be included in revenue rating, however if a CL is delivering an order it will be included as an additional stop. Additional stops will be defined as the number of deliveries in addition to the delivery which has generated the maximum revenue. Collections will not be counted as an additional stop. A collection will be identified as an unload at an RDC, where the RDC is the to location on the order.


	=== Trailer Types ===		=== Trailer Types ===

Admin: /* Implementation Advice */

2012-05-03T09:41:49Z

Implementation Advice

← Older revision		Revision as of 11:41, 3 May 2012
Line 49:		Line 49:


	[[Image:]]		[[Image:291805_1.png]]


	= Functional Description =		= Functional Description =

Admin at 09:39, 3 May 2012

2012-05-03T09:39:59Z

← Older revision		Revision as of 11:39, 3 May 2012
Line 1:		Line 1:
	{{Doc_Title\|System=FUNCTIONAL SPECIFICATION\|Title=Mods to the sales rating engine\|Reference=291805 TH-8LFCT5\|Version=2.0\|Date=4/11/11\|Sysver=10.6\|Client=DHL C-TMS}}		{{Doc_Title\|System=FUNCTIONAL SPECIFICATION\|Title=Mods to the sales rating engine\|Reference=291805 TH-8LFCT5\|Version=2.0\|Date=4/11/11\|Sysver=10.7\|Client=DHL C-TMS}}

Admin at 09:39, 3 May 2012

2012-05-03T09:39:21Z

← Older revision		Revision as of 11:39, 3 May 2012
Line 1:		Line 1:
	~~[[Image:]]~~		{{Doc_Title\|System=FUNCTIONAL SPECIFICATION\|Title=Mods to the sales rating engine\|Reference=291805 TH-8LFCT5\|Version=2.0\|Date=4/11/11\|Sysver=10.6\|Client=DHL C-TMS}}


	~~<center>'''DHL C-TMS'''</center>~~


	~~<center>'''10.7'''</center>~~



	~~{\| style="border-spacing:0;"~~
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''FUNCTIONAL SPECIFICATION'''</center>~~


	~~<center>'''291805 TH-8LFCT5 Mods to the sales rating engine'''</center>~~




	\|}

	~~{\| style="border-spacing:0;"~~
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <div align="right">'''Version :'''</div>~~
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''2.0'''</center>~~




	\|}
	~~'''Copyright OBS Logistics © 2011'''~~


	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 ==		== Client Requirement ==

Admin: /* Maximum Stop Revenue */

2012-05-03T09:36:29Z

Maximum Stop Revenue

← Older revision		Revision as of 11:36, 3 May 2012
Line 128:		Line 128:
	* Assigning the maximum revenue amount to the order rated highest and a single stop charge to an order at each delivery stop (where applicable)		* Assigning the maximum revenue amount to the order rated highest and a single stop charge to an order at each delivery stop (where applicable)
	* Set new flag ‘RATED_FROM_TRIP’ to ‘Y’ against each order on the trip.		* Set new flag ‘RATED_FROM_TRIP’ to ‘Y’ against each order on the trip.

	''The new procedure in the rating package will call get_charges, passing the charge type ‘FIXED’ to find the order which generates the most revenue. Once this has been identified, the GET_CHARGES procedure will be called again, passing the charge type ADD_STOPS. This will generate a charge based on the charge for additional stops multiplied by the number of additional stops. The system must identify the cost for one adddional stop and assign this charge to one of the orders at the stop.''

	Based on the value of a new cost centre parameter ‘TRM_MAX_STOP_REVENUE’		Based on the value of a new cost centre parameter ‘TRM_MAX_STOP_REVENUE’

Admin: /* Maximum Stop Revenue */

2012-05-03T09:35:54Z

Maximum Stop Revenue

← Older revision		Revision as of 11:35, 3 May 2012
Line 128:		Line 128:
	* Assigning the maximum revenue amount to the order rated highest and a single stop charge to an order at each delivery stop (where applicable)		* Assigning the maximum revenue amount to the order rated highest and a single stop charge to an order at each delivery stop (where applicable)
	* Set new flag ‘RATED_FROM_TRIP’ to ‘Y’ against each order on the trip.		* Set new flag ‘RATED_FROM_TRIP’ to ‘Y’ against each order on the trip.

	~~''<nowiki>** Developer Notes**</nowiki>''~~

	''The new rating procedure will order the oms_refs assigned to the trip by revenue (generated from the contract as part of standard functionality). The order with the highest revenue will be re rated using the new GET_CHARGES function , passing the charge type FIXED . The charge returned wil be assigned to the oms_ref. If there is more delivery stops, one orders will be selected per stop and assigned a stop charge, based on the charge assigned to ADD_STOP in the relevant customer contract. ''

	''The contracts package will be amended to allow users to generate charges based on a specific charge type. The existing procedure GET_CHARGES will be overloaded to include a new parameter charge_type. ''

	''The new procedure in the rating package will call get_charges, passing the charge type ‘FIXED’ to find the order which generates the most revenue. Once this has been identified, the GET_CHARGES procedure will be called again, passing the charge type ADD_STOPS. This will generate a charge based on the charge for additional stops multiplied by the number of additional stops. The system must identify the cost for one adddional stop and assign this charge to one of the orders at the stop.''		''The new procedure in the rating package will call get_charges, passing the charge type ‘FIXED’ to find the order which generates the most revenue. Once this has been identified, the GET_CHARGES procedure will be called again, passing the charge type ADD_STOPS. This will generate a charge based on the charge for additional stops multiplied by the number of additional stops. The system must identify the cost for one adddional stop and assign this charge to one of the orders at the stop.''
Line 193:		Line 187:

	A new field will be added to the order table called RATED_FROM_TRIP. When the revenue has been overwritten by an apportioned value calculated from the trip, this flag will be set to Y. When an order is validated it is automatically re rated. An order is validated as part of the SAVE process on the orders form. If this flag is set to Y and the SAVE button has been pressed, the order will not be re rated. This will ensure that when an order is rated based on the trip, the revenue is not overwritten by the existing contract functionality.		A new field will be added to the order table called RATED_FROM_TRIP. When the revenue has been overwritten by an apportioned value calculated from the trip, this flag will be set to Y. When an order is validated it is automatically re rated. An order is validated as part of the SAVE process on the orders form. If this flag is set to Y and the SAVE button has been pressed, the order will not be re rated. This will ensure that when an order is rated based on the trip, the revenue is not overwritten by the existing contract functionality.


	== Carrier Cost ==		== Carrier Cost ==

Admin: New page: Image: '''DHL C-TMS''' '''10.7''' {| style="border-spacing:0;" | style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;pad...

2012-05-03T09:34:18Z

New page: [[Image:]] <center>'''DHL C-TMS'''</center> <center>'''10.7'''</center> {| style="border-spacing:0;" | style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;pad...

Show changes