EGL: Any Performance Implications on Commitment Control - Budget Overview Page When Increasing Value for MAX_ROWS_SCROLL Field?
(Doc ID 3042027.1)
Last updated on AUGUST 19, 2024
Applies to:
PeopleSoft Enterprise FIN General Ledger - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Goal
With Max Rows (MAX_ROWS_SCROLL) field being defaulted to 100 in Commitment Control - Budget Overview, when resulting data is more than 100 rows, the system pops up a warning message --
'More rows are available. The number of rows retrieved exceeds the Maximum Row criteria. (18021,342)
The number of selected rows exceeds the Max Rows criteria. Modify your selection criteria or increase the Max Rows criteria.'
What is the impact or performance issue it can result to if MAX_ROWS_SCROLL field default value is set up from 100 to 99999?
Solution
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
| Goal |
| Solution |