Unexpected Behavior When Assigning Multiple GL Roles for Different Data Access Sets to One User
Last updated on APRIL 24, 2017
Applies to:Oracle Fusion General Ledger Cloud Service - Version 188.8.131.52.0 and later
Oracle Fusion General Ledger - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
A user has assigned a Financial Analyst role for one data access set (DAS) and a General Accountant role for another data access set.
The expectation is that the user cannot create journals in the data access set for which the Financial Analyst role was assigned and that he should be able
to create journals in the DAS for which the General Accountant role was assigned but what is observed is that the user can create journals in the DAS where
he should not be able to.
If only one of the two roles (Financial Analyst or General Accountant) is assigned to the user the system works as expected.
Steps to reproduce:
1. Create two Data Access Sets with full access, for example:
2. Assign the roles Financial Analyst and General Accountant to a user
3. Assign the Security Context Value for each role in the Manage Data Access for Users UI:
Role Financial Analyst for DAS CAD PL
Role General Accountant for DAS USD PL
4. User logs into the application and selects the Data Access Set as CAD PL. The user is able to create and post journals which is not expected behavior because
this DAS has only Financial analyst role and that role doesn't allow to create or post journals.
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