Core Concurrent Processing - EBS (MOSC)

MOSC Banner

Specialization Rules conflicting

edited Dec 28, 2017 4:01AM in Core Concurrent Processing - EBS (MOSC) 3 commentsAnswered

EBS 12.1.3

Question on the following scenario....

We have CUST_PROG1 a concurrent program that uses FND_REQUEST.SUBMIT to programmatically submit a second program CUST_PROG2.

We have defined specialization rules for CUST_PROG2.  It is to be Excluded from Standard Manager and Included on a custom manager CUST_MGR1. There are no specialization rules for CUST_PROG1.

There is also another specialization rule, where all concurrent programs submitted by a particular user SPEC_USER1 should run on another custom manager CUST_MGR2.

Is there somewhere in the application where we can identify which rule takes priority?

Right now when SPEC_USER1 submits CUST_PROG1 we are seeing CUST_PROG2 running on different managers.  Sometimes it will run on CUST_MGR1 (desired outcome) and other times it will run on CUST_MGR2 (not desired outcome).

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

EBS Concurrent Tags

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center