How to Post Primary Journals When Reporting Ledger Has Privilege Read Only
(Doc ID 727420.1)
Last updated on SEPTEMBER 19, 2016
Applies to:Oracle General Ledger - Version 12.0.4 and later
Information in this document applies to any platform.
In the current R12 product if you give someone access to post journals in the Primary Ledger then they also need to have access to create journals in the Reporting Ledger. This is because posting the journal in the Primary Ledger generates a journal in the Reporting Ledger. There is no way to prevent that user creating a journal directly in the Reporting Ledger without creating a separate responsibility.
When using a Reporting Currency Ledger in currency NOK, exactly the same transaction in currency NOK is required, that matches the Primary Ledger in currency SEK. There cannot be any discrepancy between these ledgers.
How can the user be prevents from entering journals in the Reporting Currency Ledger. If the setup on the Data Access Set for the Reporting Currency Ledger is set to Read Only the Reporting Currency Ledger is not shown in the list of values for the Ledger in the Journal Entry screen. However with this option (privilege Read Only) journals cannot be posted in the Primary Ledger because it tries to create a journal in the Reporting Currency Ledger and fails.
How can users be prevented from creating Journals in the Reporting Currency Ledger and still be able to post using the same responsibility, as was possible before upgrading to R12?
There is no way to restrict the user from creating and posting journals in the Primary Ledger but posting only in the Reporting Ledger without creating another user or responsibility.
If full read write privilege is allowed in the Primary Ledger then when a journal is created using that responsibility the reporting ledger can be chosen from the ledger drop down list.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!