Concurrent Manager Has Put The Concurrent Request On Hold all of Sudden
Last updated on DECEMBER 04, 2017
Applies to:Oracle Concurrent Processing - Version 12.1.3 to 12.2 [Release 12.1 to 12.2]
Information in this document applies to any platform.
E-Business Suite R12 Concurrent Processing, Request Processing related issues
When users close the browser window after clicking on the "Schedule" or "Options" button within the Request Detail (FNDRSRUN) form, the status of the concurrent request remains Inactive/On Hold.
End users may not be aware that this navigation causes the request to stay in On Hold forever.
This results in a problem as those requests will stay in On Hold forever, until you cancel the hold using "Remove Hold" button.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms