R12: Changes Made To Burden Schedule Revision Not Saved Due To Performance Issue
(Doc ID 2327701.1)
Last updated on FEBRUARY 21, 2019
Applies to:Oracle Project Costing - Version 12.1.3 and later
Information in this document applies to any platform.
Users create a new burden schedule. As part of the process they are updating the current burden schedule to field and saving. When they
save, the system hangs and they are not able to get a commit on the new value.
The following SQL is causing the performance issue:
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