My Oracle Support Banner

Definition Access Set Restricts Based on Responsibility and User, Not Just Responsibility Assignment (Doc ID 2488983.1)

Last updated on FEBRUARY 25, 2019

Applies to:

Oracle General Ledger - Version 12.0.0 and later
Information in this document applies to any platform.

Symptoms

Definition Access Sets (DAS) were defined for Rate Types. These were assigned at Responsibility level for two users. 

It has been observed that the restriction is not considering only the assignment at Responsibility level but also at user level, joining all assignments for all Responsibilities granted to the user.

 

Example:

Definition Access Set 1 allowing access to ALL Rate Types - assigned to Responsibility1 and User1.

Definition Access Set 2 allowing restricted access to Rate Types - assigned to Responsibility2 and User2. Restriction is designed for rates upload.

User2 is also having Responsibility1 assigned as this user will run Revaluation and other processes and need access to all rates.

Result: User2 using Responsibility2 is not restricted regarding Rate Types even if DAS2 (restricted) should not allow such access for this Responsibility2.

Changes

New setup in place.

Cause

To view full details, sign in with your My Oracle Support account.

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


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.