Changing the Status of Concurrent Requests In Oracle Apps

Changing the Status of Concurrent Requests

This essay explains how to change a request's phase and status, and how to change the priority of a Pending or Inactive request.

Changing a Request's Phase and Status

A request is in one of four phases: Pending (waiting to be run), Running, Completed, or Inactive (unable to run). Within each phase, a request's condition is referred to as its status.
You can change the phase of a Pending, Running, or Inactive request by changing its status.

Pending and Inactive Requests

You may cancel Pending and Inactive requests. The request's phase and status becomes Completed - Cancelled.
You may place on hold Pending and Inactive requests. The request's phase and status becomes Inactive - On Hold. You can reverse this action by later selecting the request removing the hold.

Running Requests

You can terminate Running requests. The request's phase and status becomes Completed - Terminated.

Changing a Request's Status

You can change the status of a request, and its resulting phase, using the Requests window.

Changing the Priority of a Pending or Inactive request

Requests normally run according to start time, on "first-submitted, first-run" basis. However, a higher priority request starts before an earlier request.
As System Administrator, you can change the priority of any Pending or Inactive request using the Requests window.

Request Priority is associated with an application User

The priority of a user's requests defaults to the value you, as System Administrator, set for their Concurrent:Priority user profile option. Users cannot change the priority of their requests.
If a concurrent program has a defined priority, that priority overrides the user's profile option.

• Priorities range from 1 (highest) to 99 (lowest).

• The standard default is 50.

• Concurrent programs submitted by the Internal Concurrent Manager have a priority of zero (0), and override all other requests.