Troubleshooting Multi-Org Access Control (MOAC) Issues in Oracle Projects
(Doc ID 414013.1)
Last updated on JULY 22, 2024
Applies to:
Oracle Project Foundation - Version 12.0.0 and laterInformation in this document applies to any platform.
Purpose
This document is designed to assist customers and support engineers to get solutions for common issues occurring when using the Multi-Org Access Control (MOAC) feature.
Troubleshooting Steps
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
| Purpose |
| Troubleshooting Steps |
| In R12, why were views like 'PA_EXPENDITURES' and 'PA_EXPENDITURE_ITEMS' changed to synonyms? |
| How to ascertain if a particular synonym has a security policy enabled |
| Why do queries containing 'security policy' enabled synonyms return no data? |
| How to check if MOAC is enabled for a product |
| Why are the customizations not working after upgrading to Release 12? |
| After upgrading from 11.5.x to R12 what is needed if you do not wish to use MOAC features? |
| If both MO: Security Profile and MO: Operating Unit, are set then what is the impact? |
| If a transaction is entered in the wrong operating unit because the user has access to multiple operating units, how can it be corrected? |
| After changes to the security profile, why are the expected operating units not accessible to the user? |
| What 'Security Policy' is implemented on objects in the R12 MOAC Architecture? |
| How is the application context attribute 'current_org_id' set? |
| References |