FND_CONCURRENT_REQUESTS table contains the Concurrent Request Phase and Status of each concurrent request.
Here are the information about Concurrent Request Phase and Status
Values and Meaning for Status code
SELECT LOOKUP_CODE STATUS_CODE, MEANING FROM FND_LOOKUP_VALUES WHERE LOOKUP_TYPE = 'CP_STATUS_CODE' AND ENABLED_FLAG = 'Y' AND VIEW_APPLICATION_ID = 0 ORDER BY LOOKUP_CODE
| STATUS_CODE | MEANING |
| A | Waiting |
| B | Resuming |
| C | Normal |
| D | Cancelled |
| E | Error |
| G | Warning |
| H | On Hold |
| I | Normal |
| M | No Manager |
| P | Scheduled |
| Q | Standby |
| R | Normal |
| S | Suspended |
| T | Terminating |
| U | Disabled |
| W | Paused |
| X | Terminated |
| Z | Waiting |
Values and Meaning for phase code
SELECT LOOKUP_CODE PHASE_CODE, MEANING FROM FND_LOOKUP_VALUES WHERE LOOKUP_TYPE = 'CP_PHASE_CODE' AND ENABLED_FLAG = 'Y' AND VIEW_APPLICATION_ID = 0 ORDER BY PHASE_CODE
| STATUS_CODE | MEANING |
| C | Completed |
| I | Inactive |
| P | Pending |
| R | Running |
Here are the meaning Concurrent Request Phase and Status combined
|
Phase
|
Status
|
Description
|
|
PENDING
|
Normal
|
Request is waiting for the next available manager.
|
|
PENDING
|
Standby
|
Program to run request is incompatible with other program(s) currently running.
|
|
PENDING
|
Scheduled
|
Request is scheduled to start at a future time or date.
|
|
PENDING
|
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.
|
|
RUNNING
|
Normal
|
Request is running normally.
|
|
RUNNING
|
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.
|
|
RUNNING
|
Resuming
|
All requests submitted by the same parent request have completed running. The Parent request resumes running.
|
|
RUNNING
|
Terminating
|
Request is terminated by choosing the Cancel Request button in Requests window.
|
|
COMPLETED
|
Normal
|
Request completed successfully.
|
|
COMPLETED
|
Error
|
Request failed to complete successfully.
|
|
COMPLETED
|
Warning
|
Request completed with warnings. For example, a request is generated successfully but fails to print.
|
|
COMPLETED
|
Cancelled
|
Pending or Inactive request is cancelled by choosing the Cancel Request button in the
Requests window. |
|
COMPLETED
|
Terminated
|
Request is terminated by choosing the Cancel Request button in the Requests window.
|
|
INACTIVE
|
Disabled
|
Program to run request is not enabled. Contact your system administrator.
|
|
INACTIVE
|
On Hold
|
Pending request is placed on hold by choosing the Hold Request button in the Requests window.
|
|
INACTIVE
|
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.
|
Related Articles
Concurrent Manager Queries :This article contains awesome top 30 Concurrent Manager Queries for Concurrent Manager troubleshooting ,resolution ,run time, details
ORA-01427 :Check out this for the solution on ORA-01427: single-row subquery returns more than one row error ,how to resolve it when it happens with Concurrent Manager
request set in oracle apps : Request set gives the capability to submit the same set of requests regularly using a single transaction.
Concurrent Manager Interview questions ::Check out 24 Concurrent Manager Interview questions to help you in EBS interview. This consists of all sort of question on standard manager,service manager
Parallel Concurrent Processing :What is PCP, How to setup it, how to define internal monitor
Oracle Concurrent Manager :How an E-Business Suite Concurrent Manager Process Works,Oracle Concurrent Manager,What is internal monitor,What is service manager and troubleshooting