Security Controls on data for P6 Analytics
Posted
by Jeffrey McDaniel
on Oracle Blogs
See other posts from Oracle Blogs
or by Jeffrey McDaniel
Published on Wed, 17 Oct 2012 12:57:15 +0000
Indexed on
2012/10/17
17:11 UTC
Read the original article
Hit count: 412
/Oracle
1. Determining if a user has cost security is based on the Project level security privileges - either View Project Costs/Financials or Edit EPS Financials. If expecting to see costs make sure one of these permissions are allocated.
3. Resource Access is determined by what is granted in P6. Verify the resource access granted to this user in P6. Resource security is hierarchical. Project access will override Resource access based on the way security policies are applied.
5. For P6 Reporting Database versions 2.2 and higher, the Extended Schema Security service must be run to calculate all security. Any changes to privileges or security this service must be rerun before any ETL.
7. Cache in OBI is another area that can sometimes make it seem a user isn't seeing the data they expect. While cache can be beneficial for performance in OBI. If the data is outdated it can retrieve older, stale data. Clearing or turning off cache when rerunning a query can determine if the returned result set was from cache or from the database.
© Oracle Blogs or respective owner
