Auditing Custom Object Data

You can use Oracle Fusion Applications auditing features to configure auditing for user-defined business object attributes generated by your intake forms.

This topic describes how to:

• Configure business object attribute auditing for specific transaction types.

• Run an audit report for specific transaction types.

You use the Oracle Fusion Applications auditing features to set up auditing for Oracle Permitting and Licensing business objects.

Transaction-Specific Auditing Scope

A specific transaction type, such as a permit or a planning application are the business objects you can audit. Each transaction type, such as a permit, contains a limited set of fields that you can audit, which include:

• User-defined fields. These are the fields you added manually to your intake form.

• Fields from the base view object for that transaction type. These fields are the same for all transaction types, and they appear in the attributes list regardless if they appear in the intake form or not.

The transaction types included for custom object auditing are:

• Permits

• Planning and Zoning

• Business Licenses

Note: You will see Code Enforcement business objects in the list, but these objects are not supported for auditing at this time. You can select them but the attributes list will be empty.

You can audit other aspects of transaction data, such as changes to fee schedules and fee items, which is discussed in another topic. For more information, see Auditing Oracle Permitting and Licensing Data.

Note: The fields added to your intake forms by the field groups you’ve added are not currently available to be audited. Fields added to the intake form by field groups reside in a child table to the base view object for the transaction type. Auditing fields in child tables is not currently supported.

To determine what fields in a specific transaction are able to be audited, you can use any REST client to submit a describe for that transaction type. For example, you can send a GET request using the following URL:

https://servername.fa.us2.oraclecloud.com/fscmRestApi/resources/11.13.18.05/LNPFENCEPERMIT_c/describe

Where FENCEPERMT is the name of the transaction type. LNP is prepended and _c is appended automatically by the Intake Form Designer.

The attributes appearing in the returned payload of the describe that can’t be audited appear within the FieldGroups section. For example:

“FieldGroups” : {
         “discrColumnType” : false, 
			“title” : “Permit Details”,
			“attributes” : [ {
			...

Configuring Business Object Attribute Auditing for a Specific Transaction Type

Note: Before you can begin setting up auditing for a specific transaction type, the intake form needs to be published.

To configure auditing for a specific transaction type:

1. Access Functional Setup Manager.

2. Open your licensed offering from the Setup list, such as Public Sector Permits or Public Sector Planning and Zoning.

3. Select the Application Extensions functional area, and click the Manage Audit Policies task.

   Note: You can use the Search Tasks feature as well to navigate to the Manage Audit Policies task.

4. On the Manage Audit Policies page, locate the Oracle Fusion Applications group box.

5. To enable auditing, set Audit Level to Auditing.

6. Click Configure Business Object Attributes.

7. On the Configure Business Object Attributes page, select Supply Chain Management Common Components from the Product drop-down list, and expand the FscmCustomReferenceAuditAM node.

   Note: The Public Sector Compliance and Regulation offering resides in the Oracle Fusion Applications Financials and Supply Chain (FSCM) database. When searching for Oracle Permitting and Licensing custom business objects, you will find them within the Supply Chain Management Common Components section. If you are also an Oracle FSCM customer, you will see FSCM business objects mixed with your Oracle Permitting and Licensing products within the FscmCustomReferenceAuditAM node.

8. Click the business object for which you want to configure auditing.

   The business object name is the same as your transaction type code, such as the Permit Type value on the Permit Type page.

9. With the business object selected, select Actions > Create in the Attribute column on the right.

10. In the Select and Add Audit Attributes dialog box, select the attributes you want to audit.

    Note: The attributes available are limited to the base view object values and the custom fields you have added to your form.

11. Click OK.

12. Save your changes.

Running an Audit Report

To run an audit report:

1. Select Navigator > Tools > Audit Reports.

2. For Date, specify a date or date range for your audit report.

3. Select Supply Chain Management Common Components from the Product drop-down list.

4. From the Business Object Type drop-down list, select the permit type name for which you enabled auditing.

5. Use the Date, User, and Event Type criteria to refine your search, as needed.

6. Click Search.

For more information on Fusion Applications auditing, see Oracle Applications Cloud documentation for Implementing Applications, Audit Policies.