Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Scheduled Request Goes Inactive/On Hold Status Automatically by Concurrent Manager User

edited Jul 22, 2015 5:21AM in Core Concurrent Processing - EBS (MOSC) 14 commentsAnswered

Hi all,

We have encountered this error where a scheduled request it suddenly put on hold automatically by the CONCURRENT MANAGER user.

The diagnostics says that:

User CONCURRENT MANAGER placed this request on hold on ....

We have checked the Scheduled Request Goes Inactive/On Hold Status Automatically by Concurrent Manager User (Doc ID 737282.1) note, however we are already on R12 and are at a higher file version.

Recommended:

5. Confirm the following file versions:

FNDRSRUN.fmb 115.181

You can use the commands like the following:

strings -a $FND_TOP/forms/US/FNDRSRUN.fmx|grep '$Header'


We are at:

>strings -a $FND_TOP/forms/US/FNDRSRUN.fmx | grep Header

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center