top of page

Query to identify concurrent requests that can't be cancelled.

Have you ever got the below error while cancelling a concurrent request from the front end:

Of course, you got it, otherwise you wouldn't be here 😊😊 .

Request xxxxxx can no longer be cancelled. The Concurrent Manager Process that was running this request has exited abnormally. The ICM will mark this request as completed with an error.

You can use the below query to cancel it from the backend.

UPDATE fnd_concurrent_requests
SET phase_code = 'C', status_code = 'X'
WHERE Request_id=&request_id.

But the catch is, what if you want to identify all these kinds of stuck requests in R12 and cancel the from backend

You can use the below query to get all requests that are stuck and don't have a database session.

select fcp.user_concurrent_program_name, fcr.request_id, fcr.status_code, fcr.phase_code, fcr.controlling_manager 
from apps.fnd_concurrent_requests fcr, apps.fnd_concurrent_programs_vl fcp where fcp.concurrent_program_id = fcp.concurrent_program_id 
and fcr.phase_code='R' 
and fcr.status_code <> 'W'
and fcr.controlling_manager is null;

Note: We offer professional training in Oracle Database and Oracle E-Business Suite coupled with job assistance. Please feel free to contact us via WhatsApp at +91 8985030907 for further inquiries.

19 views0 comments

Recent Posts

See All


Contact Me

Tel: 7989359581

  • Facebook Social Icon
  • LinkedIn Social Icon
  • Twitter Social Icon

Thanks for submitting!

© 2023 by Phil Steer . Proudly created with

bottom of page