281794 - Revision history

DuttonT at 08:42, 12 May 2011

2011-05-12T08:42:50Z

← Older revision		Revision as of 10:42, 12 May 2011
Line 214:		Line 214:


	~~'''~~Authorised By~~'''~~		= Authorised By =
			{\| Border="1"
	{\| ~~style~~="~~border-spacing:0;~~"		\| '''''Matt Crisford'''''
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"~~\| '''''Matt Crisford'''''		\| Development Manager
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"~~\| Development Manager		\|
	\| ~~style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~

	\|-		\|-
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"~~\| '''''Peter Greer'''''		\| '''''Peter Greer'''''
	~~\| style="border:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"~~\| TMSCC ~~CTMS~~ Product Manager		\| TMSCC MTS Product Manager
	\| ~~style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:none;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\|~~		\|

	\|}		\|}

Middletong at 07:59, 12 May 2011

2011-05-12T07:59:19Z

← Older revision		Revision as of 09:59, 12 May 2011
Line 59:		Line 59:
	None		None
	== Menu Structure ==		== Menu Structure ==
	~~˜Unchanged~~		Unchanged
	== Data ==		== Data ==
	New record will be added to the ACC_PAYMENT_TYPE table similar to the existing payment type ORDER_COST.		New record will be added to the ACC_PAYMENT_TYPE table similar to the existing payment type ORDER_COST.

DuttonT at 09:52, 11 May 2011

2011-05-11T09:52:30Z

← Older revision		Revision as of 11:52, 11 May 2011
Line 136:		Line 136:

	It is noted that users who do not have access to the group name of the order will still be able to amend the quantities as per current functionality, which will potentially amend revenue generated by contracts.		It is noted that users who do not have access to the group name of the order will still be able to amend the quantities as per current functionality, which will potentially amend revenue generated by contracts.


	'''References'''		'''References'''


	{\| style="border-spacing:0;"		{\| style="border-spacing:0;"
Line 165:		Line 165:

	\|}		\|}


	'''Document History '''		'''Document History '''


	{\| style="border-spacing:0;"		{\| style="border-spacing:0;"
Line 212:		Line 212:

	\|}		\|}


	'''Authorised By'''		'''Authorised By'''


	{\| style="border-spacing:0;"		{\| style="border-spacing:0;"

DuttonT at 09:51, 11 May 2011

2011-05-11T09:51:45Z

← Older revision		Revision as of 11:51, 11 May 2011
Line 136:		Line 136:

	It is noted that users who do not have access to the group name of the order will still be able to amend the quantities as per current functionality, which will potentially amend revenue generated by contracts.		It is noted that users who do not have access to the group name of the order will still be able to amend the quantities as per current functionality, which will potentially amend revenue generated by contracts.



	'''References'''		'''References'''
Line 167:		Line 165:

	\|}		\|}

	'''Document History '''		'''Document History '''

Line 213:		Line 212:

	\|}		\|}

	'''Authorised By'''		'''Authorised By'''

DuttonT at 09:50, 11 May 2011

2011-05-11T09:50:44Z

@@ Line 163: / Line 163: @@
 | style="border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"|
 | style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"|
 | style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"|
 | style="border-top:none;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"|

DuttonT at 09:49, 11 May 2011

2011-05-11T09:49:16Z

← Older revision		Revision as of 11:49, 11 May 2011
Line 55:		Line 55:
	== Scope ==		== Scope ==
	This change will be applied to system version 10.6.0.		This change will be applied to system version 10.6.0.

	= Set-up =		= Set-up =
	== Pre-requisites ==		== Pre-requisites ==
	None		None


	== Menu Structure ==		== Menu Structure ==
	˜Unchanged		˜Unchanged


	== Data ==		== Data ==
	New record will be added to the ACC_PAYMENT_TYPE table similar to the existing payment type ORDER_COST.		New record will be added to the ACC_PAYMENT_TYPE table similar to the existing payment type ORDER_COST.
Line 172:		Line 167:

	\|}		\|}
	~~'''Glossary'''~~


	~~{\| style="border-spacing:0;"~~
	\| style="background-color:#c0c0c0;border-top:0.018cm solid #000000;border-bottom:0.018cm solid #000000;border-left:0.018cm solid #000000;border-right:none;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''Term or Acronym'''</center>
	~~\| style="background-color:#c0c0c0;border:0.018cm solid #000000;padding-top:0cm;padding-bottom:0cm;padding-left:0.191cm;padding-right:0.191cm;"\| <center>'''Meaning'''</center>~~

	\|-		\|-

DuttonT at 09:46, 11 May 2011

2011-05-11T09:46:33Z

← Older revision		Revision as of 11:46, 11 May 2011
Line 122:		Line 122:


	Any ORD_COST_MAN payments relating to a trip will be included in the costs and profit margin fields displayed on the ~~fiancÃ©~~ tab of the trip screen.		Any ORD_COST_MAN payments relating to a trip will be included in the costs and profit margin fields displayed on the "fianc" tab of the trip screen.

DuttonT at 09:45, 11 May 2011

2011-05-11T09:45:14Z

← Older revision		Revision as of 11:45, 11 May 2011
Line 88:		Line 88:


	Currently when this button is selected the payments screen is opened, but the new and edit buttons on the payment screen remain disabled. This will be amended, so that the payment and edit buttons are enabled based on the value of a user function ~~â€˜ALLOW_ORD_COST_MANâ€™~~ and the status of the order. The order must be at SCHEDULED, SCHED_COLL or DELIVERED status.		Currently when this button is selected the payments screen is opened, but the new and edit buttons on the payment screen remain disabled. This will be amended, so that the payment and edit buttons are enabled based on the value of a user function ˜ALLOW_ORD_COST_MAN" and the status of the order. The order must be at SCHEDULED, SCHED_COLL or DELIVERED status.

DuttonT at 09:43, 11 May 2011

2011-05-11T09:43:25Z

← Older revision		Revision as of 11:43, 11 May 2011
Line 38:		Line 38:


	The manual payments will be subject to the existing requirements for payments ~~â€“~~ accounts set up, invoice requirements created. If any are missing, the payment will fail.		The manual payments will be subject to the existing requirements for payments "accounts" set up, invoice requirements created. If any are missing, the payment will fail.

DuttonT at 09:42, 11 May 2011

2011-05-11T09:42:18Z

← Older revision		Revision as of 11:42, 11 May 2011
Line 23:		Line 23:

	== Solution ==		== Solution ==
	A new payment type will be created in the Accounts Maintenance screen called ORD_COST_MAN. The payment will be created with similar properties to the ~~â€˜ORDER COSTâ€™~~ payment type. Currently users are unable to enter any type of internal cost payment against an order. Internal costs are only generated from Contracts		A new payment type will be created in the Accounts Maintenance screen called ORD_COST_MAN. The payment will be created with similar properties to the ORDER COST payment type. Currently users are unable to enter any type of internal cost payment against an order. Internal costs are only generated from Contracts


Line 41:		Line 41:


	Manual payments will not replace any internal charges generated from contracts. If the contract payment is deemed too high, then an manual credit will be added ( an ORD_COST_MAN payment with a negative amount)		Manual payments will not replace any internal charges generated from contracts. If the contract payment is deemed too high, then an manual credit will be added (an ORD_COST_MAN payment with a negative amount)


Line 72:		Line 72:


	A new function will be created called ~~â€˜ALLOW_ORD_COST_MANâ€™~~ Only users with this function will be able to create manual internal charges. This will be added to the table ADM_FUNCTION and access to the function will be provided through the access control screen. Access is applied on a GROUP basis.		A new function will be created called ALLOW_ORD_COST_MAN Only users with this function will be able to create manual internal charges. This will be added to the table ADM_FUNCTION and access to the function will be provided through the access control screen. Access is applied on a GROUP basis.


Line 131:		Line 131:


	Only users whose order group parameter setup (SCHED_GROUP) access matches the GROUP NAME on the order will be able to add manual internal order costs, otherwise the ~~â€˜Costsâ€™~~ button on the Orders screen Finance tab will be disabled. In addition, if a user does not have access to the GROUP NAME of the order, the ~~â€˜Revenueâ€™~~ button on the Orders screen Finance tab will also be disabled.		Only users whose order group parameter setup (SCHED_GROUP) access matches the GROUP NAME on the order will be able to add manual internal order costs, otherwise the "Costs" button on the Orders screen Finance tab will be disabled. In addition, if a user does not have access to the GROUP NAME of the order, the ˜Revenue" button on the Orders screen Finance tab will also be disabled.