Yes agree, its useful to have the report so the changes can be effectively monitored and audited.

Thanks
Sreenivas

Excellent.  This is soooo critical from an external audit perspective.

I agree that this capability and actually other Oracle Audit features need reevaluated and enhanced.

Agreed.  Very necessary for year end audits coming up. 

Thanks for your vote on this Lori.  This is a necessary step at least until Oracle develops a full audit trail for changes to Audit Policies.  There are two Ideas to support the development of those audit policies as follows:

Thanks Lori.  We are gaining traction on our core three most important Ideas.  For those that haven't reviewed them, here they are:

Audit Policy over Core Audit Policies - Need full change tracking when Core Audit Policies are enabled / disabled / changed;  Critical from an audit perspective

https://cloudcustomerconnect.oracle.com/posts/81c53ece43

Audit Policy over Functional Audit Policies - Need full change tracking when Core Audit Policies are enabled / disabled / changed;  Critical from an audit perspective

https://cloudcustomerconnect.oracle.com/posts/d0c940b933

The reason both of these are necessary is because the data is stored in different places.  We currently have visibility to the functional audit policy configurations through the FND_AUDIT_ATTRIBUTES table.  Oracle has confirmed that the core audit polices (SOA Suite, Platform Security Services, etc) are stored in middleware tables and not available to be queried via OTBI.