R12: How To Avoid Bouncing Middle Tier Each Time Profile Option "FND: VIEW OBJECT MAX FETCH SIZE" Is Changed (Doc ID 2210969.1)

Last updated on SEPTEMBER 05, 2024

Applies to:

Goal

Use of the profile option, FND: View Object Max Fetch Size, does not work as expected for viewing large number of resources. We have a Project workplan that has over 200 resources. We are trying to update the workplan amounts and get the error and only see 201 resources.

Error message: Query has exceeded 200 rows. Potentially more rows exist, please restrict your query.

Profile option "FND: View Object Max Fetch Size" set to:
Site Level = 200
Application (Projects) = 400

Changed the profile option to 700 at the application level, but still get the message.

Tested the following:

- Set the value to 700 at the site level, projects application level, responsibility level and user level. Cleared cache - closed the browser and opened a browser. This works and able to go to the last resource for that task.
- Changed the profile settings back to 200 at the site level and 700 at the application level. Cleared the cache again - logged out and closed the browser. Now when trying it, do not get the message.
- Logout and log back in a few times (without having to clear the cache) and retested. Tried this multiple times and the application allows to see the end of the list.

How to avoid bouncing the middle tier each time the profile option, FND: VIEW OBJECT MAX FETCH SIZE, is changed?

Solution

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.