Scheduled request remains Inactive / On Hold after a client browser or forms session ends abruptly
(Doc ID 2290269.1)
Last updated on MARCH 20, 2019
Applies to:Oracle Concurrent Processing - Version 12.1.3 to 12.1.3 [Release 12.1]
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
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document