Scheduled request remains Inactive / On Hold after a client browser or forms session ends abruptly
Last updated on JULY 31, 2017
Applies to:Oracle Concurrent Processing - Version 12.1.3 and later
Information in this document applies to any platform.
An E-Business Suite (EBS) user was updating a scheduled request; however, the client browser / forms session ended abruptly, either crashing or accidentally closed.
The EBS user did not return to the task of updating the schedule request and the schedule was missed because the request remain Inactive / On Hold
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