Oracle Concurrent Request phase and status

A concurrent request within Oracle EBS always has a status and is in a phase. The phases and status are linked and only a limited number of combinations are possible. The phases are: PENDING, RUNNING, COMPLETED and INACTIVE.

you can have the following statuses within the PENDING phase:
- Normal: Request is waiting for the next available manager.
- Standby: Program to run request is incompatible with other program(s) currently running.
- Scheduled: Request is scheduled to start at a future time or date.
- Waiting: A child request is waiting for its Parent request to mark it ready to run. For example, a request in a request set that runs sequentially must wait for a prior request to complete.

For the RUNNING phase you can have the following statuses:
- Normal: Request is running normally.
- Paused: Parent request pauses for all its child requests to finish running. For example, a request set pauses for all requests in the set to complete.
- Resuming: All requests submitted by the same parent request have completed running. The Parent request resumes running.
- Terminating: Request is terminated by choosing the Cancel Request button in Requests window.

For the COMPLETED phase you can have the following statuses:
- Normal: Request completed successfully.
- Error: Request failed to complete successfully.
- Warning: Request completed with warnings. For example, a request is generated successfully but fails to print.
- Cancelled: Pending or Inactive request is cancelled by choosing the Cancel Request button in the Requests window.
- Terminated: Request is terminated by choosing the Cancel Request button in the Requests window.

For the INACTIVE phase you can have the following statuses:
- Disabled: Program to run request is not enabled. Contact your system administrator.
- On Hold: Pending request is placed on hold by choosing the Hold Request button in the Requests window.
- No Manager: No manager is defined to run the request. Check with your system administrator. A status of No Manager is also given when all managers are locked by run-alone requests.