Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Purpose of FND_REQUEST_SETS.CONCURRENT_PROGRAM_ID?

edited May 28, 2014 12:00PM in Core Concurrent Processing - EBS (MOSC) 1 commentAnswered

Recently we were experiencing an issue where an exception was occurring whenever users attempted to submit certain request sets via the Submit Request Set form.  The text of the exception states:

ORA-01403:
no data found

--------------------------------------------------------------

FRM-40735:
ON-INSERT trigger raised unhandled exception ORA-06503.

The strange thing was that by creating a whole new request set that exactly matched the existing request set we could successfully submit the request set.  After investigation, I found that the offending request sets all had an ID in the CONCURRENT_PROGRAM_ID column of FND_REQUEST_SETS.  By setting this column to NULL I could successfully execute the previously broken request sets.

Tagged:

Howdy, Stranger!

Log In

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

Register

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

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center