Inclusive and Exclusive Transaction Controls (Oracle Projects Help)


	Previous	Next		Contents	Index	Navigation	Glossary	Library

Inclusive and Exclusive Transaction Controls

You specify whether the transaction controls you enter are inclusive or exclusive.

Inclusive transaction controls limit charges to only the transaction controls entered; Oracle Projects then rejects any charges that are not listed as chargeable in the transaction controls.

You make your transaction controls inclusive by checking the Limit to Transaction Controls box on the Transaction Controls window.

Exclusive transaction controls allow all charges except those that are specified as non-chargeable in the transaction controls. Oracle Projects defaults to exclusive transaction controls.

For either method of transaction controls, you need to enter the following information:

Expenditure category

Expenditure type

Non-labor resource

Employee

Chargeable

Billable

Effective from

Effective to

You must specify an employee or expenditure category for each record. You can specify a non-labor resource for usage expenditure types.

Employee controls with usage and supplier transactions

Transaction controls that you define by employee do not apply to transactions that are not associated to an employee. This includes purchasing and supplier invoice transactions entered for a supplier not associated to an employee, and usage items incurred by an organization and not an employee.

If you define transaction controls to list employees who can charge to your project, Oracle Projects allows transactions from those employees along with any purchasing transactions, supplier invoice transactions, and usage items incurred by an organization and any other transactions that do not require an employee number.

Employee controls with expense reports entered in Oracle Payables

If you enter expense reports in Oracle Payables, and use suppliers associated to employees, Oracle Projects validates the transaction using the employee associated to the supplier. For example, if you specify that Donald Gray cannot charge to the project, and you enter an expense report item for the supplier GRAY, DONALD who is associated to the employee Donald Gray, Oracle Projects does not allow you to charge the item to the project, because it validates the transaction controls that you have defined.

Allowable charges for each transaction control

You can further control charges for each transaction control record by specifying whether to allow charges. The default value is to allow charges.

You usually select Chargeable when you are using inclusive transaction controls. For example, if you wanted to allow employees to charge only labor to your project, you would check Limit To Transaction Controls to limit charges to only the transaction controls entered. Then you would define a transaction control with the Labor category, and allow charges to that transaction control.

You usually do not select Chargeable when you are using exclusive transaction controls because exclusive transaction controls list the exceptions to chargeable transactions.

You can also record exceptions by defining some transaction controls to allow charges and others not to allow charges. For example, say you want to define that employees can charge all labor except administrative labor. Select limit to transaction control to make the transaction control inclusive. You then enter one transaction control record with the Labor category that allows charges, and another transaction control record with the Labor category, Administrative type that does not allow charges.

Specifying billable and capitalizable transactions

You can control what transactions for contract projects are non-billable and what transactions for capital projects are non-capitalizable when you set the Billable/Capitalizable field . You can choose between the options of No or Task Level. You select No if you want the charges to be non-billable or non-capitalizable; you select Task Level if you want the billable or capitalizable status to default from the task to which the item is charged.

You define the billable or capitalizable status for a task in the Task Details window. This value defaults to all expenditure items charged to the task.

Effective Dates