Restarting a scheduled request set (which got error out) is invoking new schedule.
Last updated on DECEMBER 20, 2017
Applies to:Oracle Application Object Library - Version 12.2.6 and later
Oracle Concurrent Processing - Version 12.2 and later
Information in this document applies to any platform.
E-Business Suite 12.2 Concurrent Processing, Request Set related issues
Restarting a concurrent request set resubmits all the request set schedules.
For example if a request set is scheduled to be invoked daily, when one of the stage completes with error and is restarted, it invokes a new schedule of the request set instead of restarting the same request.
The business implementation requirements are to restart request set from the stage where error occurred, but instead a new instance of scheduled request set is created.
Hence the same request sets with the same schedules exists as duplicate.
How we can restart request set without invoking new schedule.
In case of error, when restarting a request set the request set should complete the original schedule and not invoke new one.
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