Within Same Ledger Condition Is Failing in version (Doc ID 2068575.1)

Last updated on DECEMBER 10, 2015

Applies to:

Oracle Application Access Controls Governor - Version 8.6.5 and later
Information in this document applies to any platform.


On : version, Application Access Contr. Gov.

In Oracle Application Access Controls Governor (AACG), models and controls define conflicts among duties that can be assigned in a company’s applications, and identify users who have access to those conflicting duties.
Global Condition: Same Ledger is not producing the expected results.

When using GL:Same Ledger/same set of books , Control Analysis is causing false positives.

Using GL:Same Ledger/sam set of books Global Condition should not report incidents which are not in the same set of books

The issue can be reproduced at will with the following steps:
1. Create a Control with R1 and R2 logic.
2. Create a global condition

Within same ledger/set of books = YES
Exclude: Unchecked
3. In EBS, make sure R1 and R2 has different value set at responsibility level for GL:Ledger name and Set security profile.
4. Create a user and assign R1 and R2
5. Run Synch and CA
6. Check the result, it shows the new user identified in step 4.

The issue has the following business impact:
Due to this issue, users cannot use use the global condition effectively.


Sign In with your My Oracle Support account

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

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms