OracleFree referencePDF, Excel, Word exportOracle E-Business Suite

Oracle EBS Concurrent Request Phase and Status Codes Reference

Every concurrent request in Oracle E-Business Suite carries a phase and a status, stored as one-letter codes. This page lists the combinations you see most in the Requests form and in SQL, with the first thing to check for each.

Download:

phase_code	Phase	status_code	Status	What it means	First thing to check
P	Pending	I	Normal	Request is queued and eligible to run as soon as a manager slot is free.	Manager queue size, target processes and workshift for the manager that handles the program.
P	Pending	Q	Standby	A conflicting program is running, so this request waits under the incompatibility rules.	Program incompatibilities and the request that holds the conflicting lock.
P	Pending	P	Scheduled	Request is scheduled for a future start date or is a repeating request.	Requested start date and the resubmit settings on the request.
P	Pending	A	Waiting	Child request waiting for its parent to finish or for a set to move to the next stage.	Parent request status and request set stage links.
R	Running	R	Normal	Request is executing under a concurrent manager.	Elapsed time against history, then the database session and its wait events.
R	Running	W	Paused	Parent request is paused while its child requests run.	Status of the child requests.
R	Running	B	Resuming	Parent request is resuming after its children completed.	Usually transient. If it persists, check the manager log.
R	Running	T	Terminating	A terminate action was issued and the manager is stopping the process.	OS process of the request. A stuck terminate may need a manual kill and a status fix.
C	Completed	C	Normal	Request finished successfully.	Nothing, unless the output looks wrong.
C	Completed	E	Error	Request ended with an error.	Request log file and completion_text in fnd_concurrent_requests.
C	Completed	G	Warning	Request finished but reported a warning, for example some rows rejected.	Log file warnings and any rejection or error report from the program.
C	Completed	X	Terminated	Request was terminated by a user or by the manager shutting down.	Who terminated it, and whether it can be resubmitted safely.
C	Completed	D	Cancelled	Request was cancelled before it started.	Cancelled by whom, and whether a resubmit is needed.
I	Inactive	H	On Hold	Request was submitted or placed on hold and will not run until released.	Release the hold from the Requests form, or check the submit options.
I	Inactive	M	No Manager	No concurrent manager is defined to process this program.	Specialization rules and include/exclude entries on the managers, then restart managers.
I	Inactive	U	Disabled	The concurrent program is disabled.	Enabled flag on the Concurrent Programs form.

Codes come from fnd_concurrent_requests.phase_code and status_code. Display wording can differ slightly between EBS releases and patch levels, so confirm against the lookups CP_PHASE_CODE and CP_STATUS_CODE in your instance.

Want request triage automated from your EBS data?

An optional review of how a read-only assistant could answer request status questions for your support team.

Optional. The tool and every export work without this. No spam.

How to use the reference

Search by letter or by wording. If a user tells you a request is Pending/Standby, type Standby and read the row. If you are reading raw rows from fnd_concurrent_requests, search the code pair, for example C and E. The last column gives the first diagnostic step, so you can triage a ticket in under a minute without opening Oracle Support notes. Use the Excel export to paste the table into your runbook or a ticket template.

Phase tells you where the request is in its life cycle
Status tells you the condition inside that phase
A phase and status pair is what the Requests form shows as Phase/Status

The four phases and how requests move

A request is submitted into Pending or Inactive. Pending/Normal moves to Running/Normal when a manager picks it up, and Running ends in Completed with Normal, Warning or Error. Parent requests that submit children show Running/Paused while the children work. Inactive requests do not move on their own: On Hold needs a release, No Manager needs a manager definition fix, and Disabled needs the program enabled. Knowing which phases move by themselves tells you which ones deserve a ticket.

Common mistakes when reading statuses

The most common error is treating Pending/Standby as a stuck request. Standby is the incompatibility engine doing its job, and the fix is to find the blocking request, not to restart managers. The second is treating Completed/Warning as success without reading the log, because many financial interfaces use Warning to report rejected rows. The third is bouncing the Internal Concurrent Manager for a No Manager request when the real cause is a missing specialization rule.

Check the log file, not only the status, for Warning and Error
Standby means look at conflicts, not at the manager
Terminating that never ends usually needs an OS process check
Compare run time to history before calling a Running request hung

Frequently Asked Questions

Where are phase and status stored in Oracle EBS?

They are the columns phase_code and status_code on the table fnd_concurrent_requests. The Requests form translates them using lookups, so a code pair such as P and Q is shown as Pending and Standby. You can join to the lookup values if you want readable text in a SQL report.

What does Inactive No Manager mean?

It means no concurrent manager has a specialization rule that includes the program, or the manager that does is not running. Check the include and exclude rules on your managers, confirm the manager is active, and restart if you changed definitions.

Why is my request Pending Standby?

Standby is shown when the program is incompatible with another running program, or with itself, under the incompatibility rules. The request starts when the conflicting request finishes. Find the running request that conflicts and decide whether to wait or reschedule.

Does a Warning status mean the data posted?

Not always. Warning means the program completed but flagged something, which may be rejected rows or skipped records. Read the log and any exception report the program produces before you assume the data is complete.

If your team spends time answering where a request is stuck, we can build a read-only assistant over your EBS views that explains the status and shows the query it used. It runs on your own infrastructure.

Talk to an Expert Explore More Free Tools