Core Concurrent Processing - EBS (MOSC)

MOSC Banner

What is the supported way to remove old data from fnd_concurrent_requests that is skipped by the pur

edited Feb 13, 2019 2:41PM in Core Concurrent Processing - EBS (MOSC) 10 commentsAnswered ✓

12.2.5 ad/txk 10

We have a few records that have collected over the years in FND_CONCURRENT_REQUESTS where the phase is inactive and the status is on hold.  These were submitted by now-terminated users who are no longer with the company.  The purge program does not purge these records.

What is the supported method to cancel these requests?  As the sysadmin user I cannot cancel another user's request because the button to do so is grayed out, and all I see on web searches is to use an update query to manually set the status to "C" - complete.  However, manually updating system tables is rarely a supported method so I am reluctant to do that.  The documentation says to use the cancel button, which has never been an option for another user's request.  In my experience, only the submitter of the request can cancel their own requests, which

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