Controlling Expenditures

This section describes how to use transaction controls to control the expenditures that can be charged to a project.
Oracle Projects provides you with many levels of charge controls:

  • Project Status You can use the project status to control whether any charges are allowed for the project.
  • Task Chargeable Status You can specify a lowest task as chargeable or non-chargeable, to control whether any charges are allowed for the task.
  • Start and Completion Dates You can specify the start and completion dates of a lowest task, to record the date range for which charges are allowed for the task. The start and completion dates of the project also limit when transactions can be charged.
  • Transaction Controls You can define transaction controls to specify the types of transactions that are chargeable or non-chargeable for the project and tasks.

Use transaction controls to configure your projects and tasks to allow only charges that you expect or plan. You can also define which items are billable and non-billable on your contract projects. For capital projects, you can define which items are capitalizable and non-capitalizable.
You enter transaction controls in the Project Options and Task Options windows.
You can configure transaction controls by the following:

  • Expenditure Category
  • Expenditure Type
  • Employee (includes contingent workers)
  • Non-Labor Resource

You can create any combination of transaction controls that you want; for example, you can create a transaction control for a specific person and expenditure type, or you can create a combination for a person, expenditure type, and non-labor resource. You also specify the date range to which each transaction control applies. If you do not enter transaction controls, you can charge expenditure items from any person, expenditure category, expenditure type, and non-labor resource to all lowest tasks on the project.

Inclusive and Exclusive Transaction Controls
You specify whether the transaction controls you enter are inclusive or exclusive.

  1. 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.
  2. 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 can enter the following information:

  • Expenditure category, Expenditure type, Non-labor resource & Employee (or contingent worker)

Note: You can enter bill rate and discount overrides for terminated employees.
The profile option PA: Display Terminated Employees: Number of Days determines how many days after their termination employees can have bill rate and discount overrides entered.

  • Scheduled Expenditure Only, Workplan Resources Only & Person Type
  • Chargeable,  Billable (contract projects) & Capitalizable (capital projects)
  • Effective from & Effective to

You must specify a person (employee or contingent worker) or expenditure category for each record. You can specify a non-labor resource for usage expenditure types.

Oracle Applications Fusion Cloud - Inventory

Oracle Cloud/Fusion Procurement training will help you develop the fundamental skills required to set up and use the Procurement module. This training covers all the tasks, setups, forms and reports used in Procurement and related modules