Script to HOLD and UNHOLD the scheduled concurrent requests

 
###################Holding Concurrent Request##################

update applsys.fnd_concurrent_requests
set hold_flag = 'Y',last_update_date =sysdate, last_updated_by = -1
where phase_code = 'P' and hold_flag<>'Y';

Commit;

select substr(fcrv.request_id,1,10)REQUEST,
substr
(fcrv.program,1,25)PROGRAM,
fcr.hold_flag,fcr.PHASE_CODE,fcr.status_code,fcr.last_updated_by
from apps.fnd_conc_req_summary_v fcrv,apps.fnd_concurrent_requests fcr
where fcrv.request_id = fcr.request_id and fcr.hold_flag = 'Y' and fcr.phase_code='P';

###################Un Holding Concurrent Request##################

update applsys.fnd_concurrent_requests a
set a.hold_flag = 'N' ,
last_update_date = sysdate,
last_updated_by = -1
where phase_code = 'P'
and a.hold_flag = 'Y'
and last_updated_by = -1
and last_update_date > sysdate-1;

Commit;

Script to terminate a Concurrent Request from backend - Concurrent Request Status and Phase Codes

 

Concurrent Requests can be terminated from front end. But we can also terminate the Concurrent Request from the back end.

SQL> update apps.fnd_concurrent_requests set phase_code='C' , status_code='X' where request_id='&REQUEST_ID';

SQL> commit;

Note: Please remember to kill the process for that request first before terminating the concurrent request .

The related process Id for the Concurrent Requests can be determined by

SQL> select ORACLE_PROCESS_ID from apps.fnd_concurrent_requests where REQUEST_ID='&REQUEST_ID';

Reference - Concurrent Processing - How to Cancel a Concurrent Request Stuck in the Queue? (Doc ID 749748.1)

Concurrent Request Status Codes and Phase Codes

PHASE_CODE	MEANING
C	Completed
I	Inactive
P	Pending
R	Running

 

STATUS_CODE	MEANING
R	Normal
I	Normal
Z	Waiting
D	Cancelled
U	Disabled
E	Error
M	No Manager
C	Normal
H	On Hold
W	Paused
B	Resuming
P	Scheduled
Q	Standby
S	Suspended
X	Terminated
T	Terminating
A	Waiting
G	Warning

Phase Code	Meaning with Description
Pending	Request is waiting to be run
Running	Request is running
Completed	Request has finished
Inactive	Request cannot be run

Within each phase, a request's condition or status may change. Below appears a listing of each phase and the various states that a concurrent request can go through.

The status and the description of each meaning given below:

Phase	Status	Description
PENDING	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 report in a report set that runs sequentially must wait for a prior report to complete.
RUNNING	Normal	Request is running normally.
	Paused	Parent request pauses for all its child requests to complete. For example, a report set pauses for all reports in the set to complete.
	Resuming	All requests submitted by the same parent request have completed running. The Parent request is waiting to be restarted.
	Terminating	Running request is terminated, by selecting Terminate in the Status field of   the Request Details zone.
COMPLETED	Normal	Request completes normally.
	Error	Request failed to complete successfully.
	Warning	Request completes with warnings. For example, a report is generated successfully but fails to print.
	Cancelled	Pending or Inactive request is cancelled, by selecting Cancel in the Status field of the Request Details zone.
	Terminated	Running request is terminated, by selecting Terminate in the Status field of   the Request Details zone.
INACTIVE	Disabled	Program to run request is not enabled. Contact your system administrator.
	On Hold	Pending request is placed on hold, by selecting Hold in the Status field of the Request Details zone.
	No Manager	No manager is defined to run the request. Check with your system administrator.