Audit Configuration for Business Object Attributes
Audit enables tracking the change history of particular attributes of a business object. However, those objects and their attributes must be selected for audit and auditing must be enabled for that application.
The configuration settings determine which attributes to audit for a given object, and when the audit starts and ends. Auditing takes into account all the operations performed on an object and its attributes, such as create, update, and delete. To configure audit business object attributes, use the Manage Audit Policies task in the Setup and Maintenance work area.
Selecting an Application
To set up auditing, you must select a web application that contains the required business objects that can be audited. From the list of business objects, select those business objects that you want to audit. Selecting a business object also displays its attributes that are enabled for auditing.
Selecting Attributes
For each selected business object to be audited, select the corresponding attributes to include in the audit. All attributes that belong to that object are by default selected for audit and appear on the user interface. However, you can add or remove attributes from the list. When you remove an attribute from the list, you stop auditing it even when the parent object is selected for audit. So, if you want an attribute to be audited, you must add it to the list. If the object selected in an audit hierarchy is also a part of several other audit hierarchies, the attribute configuration for that object is applicable to all the hierarchies in that application.
For business objects based on flexfields, select the Flexfields (Additional Attributes) check box to view, add, or remove flexfield attributes. The selected objects are audited.
Starting and Stopping Audit
The business object is ready for audit after you select its attributes and save the configuration changes. However, to start auditing, the audit level for Oracle Applications Cloud must be set to Auditing on the Manage Audit Policies page.
To stop auditing an object, you can deselect the entire object and save the configuration. As a result, all its selected attributes are automatically deselected and aren't audited. To continue to audit the business object with select attributes, deselect those attributes that aren't to be audited. When users view the audit history for an application, they can specify the period for which they want the results. Therefore, make a note of when you start and stop auditing an application.
For example, users intend to view the audit history of an object for the previous week, but auditing for that object was stopped last month. They wouldn't get any audit results for that week, because during the entire month that object wasn't audited. Even if you enable audit for that object today, users can't get the wanted results because audit data until today isn't available.
- For Oracle Fusion Middleware products, the maximum limit is 25000. By default, the limit is set as 10000. You can change this limit using the FND_AUDIT_FMW_EVENT_LIMIT profile option.
- For Oracle Fusion Application Business Objects, the maximum limit is 10000 per table. This is set as the default value. Sometimes, the actual rows returned might be more than the limit set, because a single transaction can update multiple tables. To decrease this limit, you can create the FND_AUDIT_EXPORT_ENTITY_LIMIT profile option and set a lesser value for it.