Applies To:
Oracle Fusion Cloud
Objective Summary:
Audit History in Oracle Fusion Cloud tracks all user actions and system changes within the application. It provides transparency by recording details such as who made the change, when it was made, and the nature of the modification. This feature helps organizations maintain compliance, troubleshoot issues, and enhance security by monitoring critical activities.
This article provides steps to enable and different ways of accessing audit history. Audit includes both application and object level audit on create, update and delete.
Important Notes:
1) Audit will not support the view or read event.
2) Enable only the most relevant and useful modules, entities, child entities ,attributes for auditing for better performance of the overall application.
3) No Limit on enabling on enabling entities or attributes.
4) Audit history data will never be purged, but you can access only specific date range of data. eg audit data between 30 days.
5) P2T can wipe the data in lower instances.
Privileges Required:
1) To manage and setup audit history user should have FND_MANAGE_AUDIT_POLICIES_PRIV.
2) To view or access the audit history user should have FND_VIEW_AUDIT_HISTORY_PRIV.
3) Application Implementation Consultant or Sales Administrator like roles will have these privileges by default.
Setup Audit History:
1) Navigate to setup and maintenance , search for the task Manage Audit Policies.
2) Enable audit for Oracle Fusion Application by selecting value as auditing. The default value is none.
View Audit History:
1) View Audit History From UI:
1) Navigate to Tools > Audit Reports.
2) Choose the filter criteria to view audit.
select
VIEW_OBJECT, VIEW_ATTRIBUTE, AUDIT_SWITCH
from
fusion.fnd_audit_attributes
where
ENABLED_FLAG='Y' order by 1 For example table MOO_OPTY will use table MOO_OPTY_
Audit table will contain additional columns like:
- AUDIT_ACTION_TYPE_ - Action Type - have values like INSERT, UPDATE and DELETE.
- AUDIT_CHANGE_BIT_MAP_ - Used to store a bit map of 1's and 0s for each row. 1 will be stored if the value has changed and 0 will be stored if the value hasn't.
Choose all the relevant filter criteria for generating a report. if it is erroring because of large data adjust criteria to limit.
Endpoint: https://abcd-dev2.fa.us2.oraclecloud.com/fscmRestApi/fndAuditRESTService/audittrail/getaudithistory
Method: POST
Content-Type: application/json
Body:
1) Sample payload for getting opportunity audit history
2) Sample payload for getting Service Request audit history
Sales - sales
