Discoverer Managed Summaries.

Question

Here is something that I gather from manuals of Discoverer 4.
"Some Applications Database Views contain row level security and return differing result sets depending upon the currently active responsibility. This means that the Summary Table or Materialized View (MV) (8.1.6+ databases) would contain different data depending on the responsibility of the user that refreshed the table.
If a user performs a query against the detail data associated with such a Managed Summary Folder, and Summary Redirection is performed, the user will be told that no rows satisfy this
criteria (this ensures that the user does not see data they should not have access to). As an administrator, you should ensure that Summary Folders that are based on Applications
Secure Views or Applications Business Views are created as External (rather than Managed).
Managed Summaries Folders on data without Applications row level security are completely unaffected. Users can continue to use External Summary Tables. If the External Summary Table is registered against an object with Applications row level security, it is the responsibility of the administrator to make sure the External Summary Table provides secure access.
Some views with row-level security, support "public" rows (particularly the Apps Human Resources). So sometimes Managed Summary Tables or MVs contain small amounts of data."
Now the question:
1.How can I know that a particular item is based on Applications secure Views?
2.Hhow will I know that particular secure view has row level security on that?
Any lessons leart, guide lines on this from people who have taken this path? Any relevant suggestions are welcome!!
Thanks,
Vinay.

Answer 1

That may be true for summaries, but query-rewrite could also occur once the query hits the database, and the optimizer determines that a materialized view would be better. I haven't experimented with this much, but you might be able to take the Disco generated SQL and run an explain plan in SQL plus (or TOAD or SQL Developer). You could also use SQL plus, and trace the session.