PAXPREPR : LIMIT_TO_TXN_CONTROLS Not Synchronized When Changing Task From The List
(Doc ID 2953625.1)
Last updated on JULY 19, 2023
Applies to:
Oracle Project Costing - Version 12.2.6 and laterInformation in this document applies to any platform.
Symptoms
When opening the Transaction Controls window for a task in PAXPREPR Projects Form, then using the Task Option window, it displays a list of Transaction Controls associated to the task. These selected in the Tasks window, which are in the block TXN_CONTROLS, plus the LIMIT_TO_TXN_CONTROLS flag which is a field from the PA_TASKS table displayed in the same window but in the TXN_CONTROLS_DUMMY block.
If you keep the windows open and just pick another task from the list in the Tasks window, the information is updated in the Transaction Controls window, like in any other window opened from the Task Options, except for the LIMIT_TO_TXN_CONTROLS flag in the TXN_CONTROLS_DUMMY block, which is not synchronized, and so it stays at the same value of the precedent task.
Steps to Reproduce:
(1) Projects Responsibility -> Projects -> Select Project, FIND
(2)Click on Tasks in the project Options, and find the Tasks with number beginning with TEST
(3) When opening the Transaction Controls window for a task in PAXPREPR Form, using the Task Option window, it displays a list of Transaction Controls associated to the task selected in the Tasks window, which
are in the block TXN_CONTROLS, plus the LIMIT_TO_TXN_CONTROLS flag which is a field from the PA_TASKS table displayed in the same window but in the TXN_CONTROLS_DUMMY block.
For the task number TEST1a
(4) For the task number TEST1b
(5) If you keep the windows open and just pick another task from the list in the Tasks window, the information is updated in the Transaction Controls window, like in any other window opened from the Task Options, except
for the LIMIT_TO_TXN_CONTROLS flag in the TXN_CONTROLS_DUMMY block, which is not synchronized, and so it stays at the same value of the precedent task.
(6) Here, picking back the task number TEST1a after displaying the TEST1b task’s transaction controls
(7) Then, refreshing the TEST1a task’s information by picking transaction controls in task options
(8)Then, picking again the task number TEST1a after displaying the TEST1b task’s transaction controls
(9) Then, refreshing the TEST1a task’s information by picking transaction controls in task options
(10) Here are displayed the true values of the LIMIT_TO_TXN_CONTROLS flag for these two tasks, via the
Examine function, against the displayed flag field in the Transaction controls window
Changes
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |