Transaction Control Extensions
Transaction control extensions allow you to define your own rules to implement company-specific expenditure entry policies. Some examples of rules that you may define are:
- You cannot charge labor hours for a future date
- You cannot charge new transactions to projects for which the work is complete; you can only transfer items to these projects
- You can only charge to tasks that are managed by the organization you are assigned to
- All entertainment expenses are non-billable
Validation
You can use transaction control extensions to provide additional validation based on any type of data you enter in Oracle Projects. For example, you can check the project status for a particular project during expenditure entry.
You can validate any transaction entered into Oracle Projects, including transactions from other Oracle Applications and from external systems. For example, you can validate project-related supplier invoices entered into Oracle Payables. You can also validate items that you transfer from one project to another.
Transaction control extensions validate expenditures items one at a time; all validation is done for each expenditure item. Oracle Projects checks each expenditure item during data entry; the transaction is validated before you commit it to the database.
Processing
Oracle Projects processes transaction control extensions after the standard validation performed for expenditure entry, and after validating any transaction controls entered at the project or task level.
Transaction is within start and completion dates of project/task
Project status is not Closed
Transaction controls at project/task level
2. Transaction control extension validation
