Introduction:
In Oracle E-Business Suite 12.2, concurrent requests can occasionally be placed on hold due to various system behaviors and user actions. This blog will outline the key scenarios that may lead to concurrent requests being put on hold by concurrent manager helping users and administrators troubleshoot and resolve such issues efficiently.
Cause:
Here are two scenarios where concurrent requests may be put on hold by concurrent manager:
a) If users abruptly close the browser window after clicking the “Schedule” or “Options” button, the concurrent request remains inactive or on hold.
b) If users leave the session window open for an extended period, it may expire, causing the scheduled request to remain inactive or on hold.
Solution:
To resolve the issue test the following steps in development instance and then migrate accordingly:
Step 1: For EBS 12.2 download and review
Patch 30790157: NAVIGATION TO RUN REQUEST SET FROM ANY RESPONSIBILITY SHOWS ALL REQUEST SETS.
Step 2: Ensure that you have taken backup of your system before applying the recommended patch.
Step 3: Apply the patch in a Test environment initially before application to any Production instance.
Step 4: Confirm the following file versions by using the command below.
appldev@****** ~]$ strings -a $AU_TOP/forms/US/FNDRSRUN.fmb | grep Header
Step 5: Retest the issue and confirm the requests are no longer placed on hold.
Conclusion:
In summary, the unexpected hold placed on the concurrent request by the Concurrent Manager requires immediate attention to identify and address the underlying issue. It is crucial to analyze the root cause, whether it is a configuration error, resource limitation, or another factor, and take appropriate corrective actions.
