Attention: To align with new corporate security policies, and to match policies adopted by other communities within Oracle, the My Oracle Support Community access requirements will change beginning September 18, 2025. MOSC will now require that member accounts in our community be associated to a *corporate* email address. This means that users with generic domains (such as gmail.com, yahoo.com, and others) will no longer be granted access to the discussion forums and ideas labs. If this policy affects you, act now to change the email address that is associated with your Oracle (and community) account. Alternatively, you can opt to create a new Oracle account that uses your corporate email domain.

Human Capital Management - EBS (MOSC)

Work-arounds for 'Query has exceeded 300 rows. Potentially more rows exist, please restrict your que

Sep 2, 2013 11:16PM edited Sep 4, 2013 5:43PM in Human Capital Management - EBS (MOSC) 5 commentsAnswered

Description: User encountered the following error after clicking the 'Add' button in the self-service screen

'Query has exceeded 300 rows. Potentially more rows exist, please restrict your query.'

Current Work-around: Updated the profile 'FND: View Object Max Fetch Size' to a value greater than 300 at the responsibility level

Area of Concern: Concerns on performance issues brought about by more records being selected.

Tagged:

EBS-HCM-HCM

0

Howdy, Stranger!

To view full details, sign in to My Oracle Support Community.

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month