Best practice for enabling Audit policy in Audit framework- Attributes and performance consideration
in Sales
Summary:
Hi Experts,
We are planning to enable audit logging across Oracle fusion cloud modules to track user activities and changes to business transactions.
Each product contains multiple parent and child business objects with too many attributes available.
Would like to understand Oracle's recommendation
- IS there any recommended minimum or maximum no of business objects and attributes to enable for each module ?
- Can enabling large no of business objects and attributes impact system performance?
- Is there any recommended guidelines for selecting audit objects and attributes while balancing audit requirements and system performance?
- If so , how to track system performance after enabling attributes?
Tagged:
0