How To Restrict Allocation Rules Based On The Ledger/data Access Set?
(Doc ID 2228305.1)
Last updated on FEBRUARY 03, 2019
Applies to:Oracle Fusion General Ledger Cloud Service - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Following is the scenario in which Functionality is required.
Two allocation rule having ledger name in the pov.
1. Ledger A provided in the POV of Rule 1.
2. Ledger B provided in the POV of Rule 2.
Now User has data access set only for Ledger A only.
Hence the requirement is that during the General Allocation Rule, User should be able to see only Rule 1.
User can see both the Rule 1 and Rule 2 in spite of selecting data access set of Leger A.
In fact user can also run the Rule 2 which imports the journal for Ledger B. But the posting program fails due to No write access to Leger B.
Now this posting program can be picked by auto post program defined in the Ledger B.
Hence this can create problems in future if rules are not restricted.
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