Con. Req. 'Receiving Transaction Manager' Inactive/No Manager : This request is an unconstrained request. (queue_method_code = I) , No concurrent manager is defined to process this request, so it cannot be processed.

Question

Hi Gurus,
I need your help on a concurrent request ( Receiving Transaction Manager ) showing as Inactive/No Manager.
EBS: R12.1.2 on Linux
Database: 11.2.0.3 on HP UX Itanium
A user is submitting the concurrent request - "Receiving Transaction Manager" (It is a concurrent program not a concurrent manager).  The request ends up as Inactive/No Manager. When I click on the diagnostics button this is what it shows -
"No concurrent manager is defined to process this request, so it cannot be processed.
Contact your system administrator to define a concurrent manager to process this request or to verify that existing concurrent managers have the correct specialization rules."
I ran analyzereq.sql and the analysis is
Analysis:
Request 1427025 is in phase "Pending" with status " Normal".
                           (phase_code = P)   (status_code = I)
This request is an unconstrained request. (queue_method_code = I)
It is in a "Pending/Normal" status, ready
to be run by the next available manager.
Checking managers available to run this request...
There is no manager defined that can run this request
This should show on the form as Inactive/No Manager
Check the specialization rules for each
manager to make sure they are defined correctly.
Additional information (from apps.FND_CONC.DIAGNOSE):
No concurrent manager is defined to process this request, so it cannot be processed.
Contact your system administrator to define a concurrent manager to process this  request or to verify that existing concurrent managers have the correct specialization rules.
I ran another SQL to find out which manager runs the program :
select CONTROLLING_MANAGER,request_id
from fnd_concurrent_requests
where request_id=1427025;
It returned blank (or) NULL for controlling Manager.
select b.USER_CONCURRENT_QUEUE_NAME from fnd_concurrent_processes a,
fnd_concurrent_queues_vl b, fnd_concurrent_requests c
where  a.CONCURRENT_QUEUE_ID = b.CONCURRENT_QUEUE_ID
and    a.CONCURRENT_PROCESS_ID = c.controlling_manager
and    c.request_id = 1427025;
Returned Nothing.
I thought that for a concurrent program when no specific manager is defined, Standard Manager is the default. Is my understanding wrong ?? Have anyone of you faced this issue? How did you fix it ?
I did check the profile - Concurrent: Conflict Domain for the responsibility and it is blank.
Appreciate any help.
Thanks
Cherrish Vaidiyan

Answer 1

Was this working before? If yes, any changes been done recently?
Your understanding is correct, unless this concurrent program is excluded from being processed by standard manager.
If the request was not processed then the no rows output is an expected behavior -- (Doc ID 344011.1)
Have you tried the solution in (Doc ID 1303315.1)?
Thanks,
Hussein