My Oracle Support Banner

Restarting a Scheduled Request Set That Errors Out Without Invoking a New Schedule (Doc ID 2330693.1)

Last updated on FEBRUARY 14, 2019

Applies to:

Oracle Concurrent Processing - Version 12.2 to 12.2 [Release 12.2]
Oracle Application Object Library - Version 12.2.6 to 12.2 [Release 12.2]
Information in this document applies to any platform.
Reviewed for relevance 28 Oct 18.


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.

Need to 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.


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.