My Oracle Support Banner

New Security Rule setup - Not behaving as expected in Forms - FSG is working correctly (Doc ID 419611.1)

Last updated on OCTOBER 19, 2020

Applies to:

Oracle General Ledger - Version 11.5.9 to [Release 11.5.9 to 11.5.10]
Information in this document applies to any platform.


-- Problem Statement:
Initial setup of security rules and they are not behaving as expected.
Set Security up on Hierarchical security mode -
Secured one segment - one rule, allowing only one segment value to be seen by this rule.

Include 0000-9999
Exclude 0000-1099
Exclude 1101-9999

Parents of value 1100 are alpha values example 1100 is child to parent TEST.

Assigned the security rule to a General Ledger Responsibility.
When running FSG report - correct results are seen (only combinations with 1100 value).
When viewing data via account inquiry this is not the case. When selecting the segment value via
the list of values the correct behavior is seen - 1100 is the only value available in the List of Values.
But when queried the account combinations that use this segment value in the form do not display. No records are returned - even the ones that do return properly on the FSG report.
When the security rule is not assigned to this responsibility they combinations show correctly.
When attempting to create a journal in the enter journal form you are not allowed - receive the
Security Rule message.

Issue is not specific to the responsibility -

-- Steps To Reproduce:
Create a hierarchical security rule
Assign to a gl responsibility
attempt to use in FSG reports and Account Inquiry form - strange behavior seen in form.

-- Business Impact:
Cannot setup and use security rules as needed/expected.


New setup of Security Rules


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

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