Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Scheduled concurrent request - submit next run if program completes in error or is terminated

Hello experts,

When a concurrent request, or request set, is scheduled and the concurrent request or request set fails/aborts/terminates - I believe, as far as I know, standard EBS is not able to submit the next concurrent request or set so that it can run on the date/time that's scheduled next - is that correct?

When configuring a concurrent request, request set, or the schedule - is there a way to configure it so that if the concurrent request, request set stage, or the request set fails/aborts or is Terminated - then EBS is still able to submit the next request or set so that it still runs on the next date/time that's scheduled?

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center