270869 - Revision history

Middletong: /* Authorised By */

2010-11-25T13:17:06Z

Authorised By

← Older revision		Revision as of 15:17, 25 November 2010
Line 174:		Line 174:


	~~=Authorised By=~~

	~~====Matt Crisford====~~
	~~Development Manager~~

	~~====Suk Sandhu====~~
	~~TMSCC MTS Product Manager~~



	Copyright OBS Logistics © 2010		Copyright OBS Logistics © 2010

	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		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

2010-11-25T13:16:44Z

Finding Radial Revenue

2010-11-25T13:16:35Z

Finding Radial Revenue

← Older revision		Revision as of 15:16, 25 November 2010
Line 125:		Line 125:

	PAYMENT.TO_LOC = ORDER.TO_LOC		PAYMENT.TO_LOC = ORDER.TO_LOC

			<br>
			<br>

	The amount fields will be updated in the post query trigger. A cursor will be created to identify the oms_ref of all orders on the current trip.		The amount fields will be updated in the post query trigger. A cursor will be created to identify the oms_ref of all orders on the current trip.

2010-11-25T13:16:03Z

Finding Radial Revenue

← Older revision		Revision as of 15:16, 25 November 2010
Line 118:		Line 118:
	==Finding Radial Revenue==		==Finding Radial Revenue==

	Oms_ref = ‘xxxxxxxxx’		Oms_ref = ‘xxxxxxxxx’
	Payment type = ‘ORDER COST’
	LOAD_LOCATION = PAYMENT.FROM_LOCATION		Payment type = ‘ORDER COST’
	PAYMENT.TO_LOC = ORDER.TO_LOC
			LOAD_LOCATION = PAYMENT.FROM_LOCATION

			PAYMENT.TO_LOC = ORDER.TO_LOC

	The amount fields will be updated in the post query trigger. A cursor will be created to identify the oms_ref of all orders on the current trip.		The amount fields will be updated in the post query trigger. A cursor will be created to identify the oms_ref of all orders on the current trip.
Line 128:		Line 131:

	The final calculation will be to determine the profit/loss of the trip by subtracting the loss from the profit. A positive value will be displayed with a green background, a negative value will be displayed with a red background.		The final calculation will be to determine the profit/loss of the trip by subtracting the loss from the profit. A positive value will be displayed with a green background, a negative value will be displayed with a red background.


	=REFERENCES=		=REFERENCES=

2010-11-25T13:15:43Z

Finding Trunk Revenue

← Older revision		Revision as of 15:15, 25 November 2010
Line 108:		Line 108:
	==Finding Trunk Revenue==		==Finding Trunk Revenue==

	Oms_ref = ‘xxxxxxxxx’		Oms_ref = ‘xxxxxxxxx’
	Payment type = ‘ORDER COST’
	LOAD_LOCATION = PAYMENT.FROM_LOC		Payment type = ‘ORDER COST’
	UNLOAD_LOCATION = PAYMENT.TO_LOC
			LOAD_LOCATION = PAYMENT.FROM_LOC

			UNLOAD_LOCATION = PAYMENT.TO_LOC

	==Finding Radial Revenue==		==Finding Radial Revenue==

2010-11-25T13:15:15Z

Finding Radial Cost

← Older revision		Revision as of 15:15, 25 November 2010
Line 98:		Line 98:
	==Finding Radial Cost==		==Finding Radial Cost==

	Oms_ref = ‘xxxxxxxxx’		Oms_ref = ‘xxxxxxxxx’
	Payment type = ‘ORDER COST’
	UNLOAD_LOCATION = PAYMENT.FROM_LOC		Payment type = ‘ORDER COST’
	PAYMENT.TO_LOC = ORDER.TO_LOC
			UNLOAD_LOCATION = PAYMENT.FROM_LOC

			PAYMENT.TO_LOC = ORDER.TO_LOC

	==Finding Trunk Revenue==		==Finding Trunk Revenue==

2010-11-25T13:14:53Z

Finding Trunk Cost

← Older revision		Revision as of 15:14, 25 November 2010
Line 91:		Line 91:
	Oms_ref = ‘xxxxxxxxx’		Oms_ref = ‘xxxxxxxxx’
	Payment type = ‘ORDER COST’		Payment type = ‘ORDER COST’

	LOAD_LOCATION = PAYMENT.FROM_LOC		LOAD_LOCATION = PAYMENT.FROM_LOC

	UNLOAD_LOCATION = PAYMENT.TO_LOC		UNLOAD_LOCATION = PAYMENT.TO_LOC

2010-11-25T13:14:33Z

Finding Trunk Cost

← Older revision		Revision as of 15:14, 25 November 2010
Line 89:		Line 89:
	==Finding Trunk Cost==		==Finding Trunk Cost==

	Oms_ref = ‘xxxxxxxxx’		Oms_ref = ‘xxxxxxxxx’
	Payment type = ‘ORDER COST’		Payment type = ‘ORDER COST’
	LOAD_LOCATION = PAYMENT.FROM_LOC		LOAD_LOCATION = PAYMENT.FROM_LOC
	UNLOAD_LOCATION = PAYMENT.TO_LOC		UNLOAD_LOCATION = PAYMENT.TO_LOC

	==Finding Radial Cost==		==Finding Radial Cost==

2010-11-25T13:13:30Z

@@ Line 77: / Line 77: @@
 ORDER 2938475
-{|
+[[Image:270869_1.png]]
 ==Identifying Payments==

2010-11-25T12:58:57Z

Identifying the Relevant Payments

← Older revision		Revision as of 14:58, 25 November 2010
Line 41:		Line 41:
	Three new fields will be added to the SCH_TRIP table		Three new fields will be added to the SCH_TRIP table

	INTERNAL_COST		*INTERNAL_COST
	INTERNAL_REVENUE		*INTERNAL_REVENUE
	PROFIT_LOSS		*PROFIT_LOSS

	The extra fields will allow the information to be reported in exports. The current population of TRIP REVENUE will be amended to only show ORDER revenue when it is applicable to the trip. As part of this RIO, the GROUP NAME field on the locations screen will be disabled, so the value can only be amended using the tab page from the maintenance menu.		The extra fields will allow the information to be reported in exports. The current population of TRIP REVENUE will be amended to only show ORDER revenue when it is applicable to the trip. As part of this RIO, the GROUP NAME field on the locations screen will be disabled, so the value can only be amended using the tab page from the maintenance menu.