Previous  Next          Contents  Index  Navigation  Glossary  Library

Transaction Controls

Oracle Projects provides you with many levels of charge controls:

Project Status You can use the project status to indicate if any charges are allowed for the project.
Task Chargeable Status You can specify a lowest task as chargeable or non-chargeable, to indicate if 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 type 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 what items are capitalizable and non-capitalizable. This proactive means to control charges to projects enables you to better manage your projects.

You can configure transaction controls by the following:

You can create any combination of transaction controls that you want; for example, you can create a transaction control for an employee and a specific expenditure type, or you can create a combination for an employee, 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 employee, expenditure category, expenditure type, and non-labor resource to all lowest tasks on the project.

See Also

Expenditure Item Validation

Project and Task Options

Entering Project and Task Options

Inclusive and Exclusive Transaction Controls

Determining if an Item is Chargeable

Determining if an Item is Billable

Examples of Using Transaction Controls

Note: To define more complex rules for implementing company-specific expenditure entry policies, you may need to use transaction control extensions.

See: Transaction Control Extensions

Transaction Control Extensions Case Studies:

Case Study: New Charges Not Allowed

Case Study: Organization-Based Transaction Controls

Case Study: Default Billable Status by Expenditure type


         Previous  Next          Contents  Index  Navigation  Glossary  Library