R11.5 Transaction Controls fail to prevent charges on a task
(Doc ID 801136.1)
Last updated on FEBRUARY 10, 2019
Applies to:Oracle Project Costing - Version 220.127.116.11 to 18.104.22.168 [Release 11.5.10]
Information in this document applies to any platform.
This issue contradicts with the Limit to transaction control flag.
When the flag is set for controlling it is explicitly listing what charges are allowed on the task, and by whom.
The task should not accept any other charges.
It violates the principle behind the "Limit to Transaction control flag"
Expect the transaction controls to work.
The issue can be reproduced at will with the following steps:
1. Transaction Control setup : No controls defined at Project level.
2. As an example, Task level control on task 015557: For this task only transactions allowed are of expenditure type LLNL LABOR by an unnamed person. ( Limit transaction controls flag is set “Y”)
3. It can now be seen that some transactions are allowed on this task.
4. The system should now allow these transactions to be saved.
Strangely if the transaction controls are modified and the employee name is removed, it works.
But it would allow all employees to charge.
The issue has the following business impact:
Due to this issue, unwanted charges occur on projects. It is a big issue to correct them as
the cost transfers need approval.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document