Set Up Adoption and Usage Tracking

To get started reporting on adoption and usage you first need to do a few setup steps.

• Enable adoption and usage tracking for the application.

• Add the user to the role of FBI_USER_SYSTEM_USAGE_TRANSACTION_ANALYSIS_DUTY .

Enable Adoption and Usage Tracking

1. Go to Setup and Maintenance.

2. Choose Setup: Sales.

3. Search for and select Manage Applications Core Administrator Profile Values.

   

4. Search for profile option code FND_TRACK_USER_ACTIVITY and ensure that it is enabled. If the value doesn't say enabled type in "ENABLED" and save.

   

5. After setting the profile option run or schedule the ESS process "Refresh BI Reports Audit Data for User Adoption Reporting". This scheduled process summarizes and aggregates data used for user adoption reporting. To run this process you must have set the profile option FND_TRACK_USER_ACTIVITY to "ENABLED" in the previous steps..

Get the Duty Role

The User System Usage subject area holds all the activity information for users of the application. This subject area is secured and can be accessed by users who have the role FBI_USER_SYSTEM_USAGE_TRANSACTION_ANALYSIS_DUTY or by users who have the BI Administrator role.

1. Sign in as a Security Manager. For example, IT_SECURITY_MANAGER.

2. Click Tools > Security Console.

3. Select Roles.

4. Click Create Role.

5. Fill in the required information. For Role Category choose BI - Abstract Roles

   

6. Click Next until you come to the Role Hierarchy page. Click Add Role. Search "user system". Choose User System User Transaction Analysis Duty - FBI_USER_SYSTEM_USAGE_TRANSACTION_ANALYSIS_DUTY. Click Add Role Membership.

   

   

7. Click Next to Users. Click Add User. Search for the user name and click Add User to Role.

   

8. Click Next to go to the Summary. Your new user should be listed there as assigned to your new role. Click Save and Close.

Enable Application Usage Charts and Click History Data Collection

All charts within Application Usage Insights are disabled by default beginning in Update 22D and must be enabled for use. Click history logging is also disabled by default beginning in Update 22D and must be enabled for use. Click history logging provides data for click history reports used in Application Usage Insights and reports run from the CRM – CRM Click History subject area in Oracle Transactional Business Intelligence (OTBI).

To use Application Usage Insights charts or click history reporting you need to enable them by changing the ORA_ZCA_CH_DISABLE profile option value to "NO". To do this, search for the profile option ORA_ZCA_CH_DISABLE. By default this profile option is set to "YES". Set Profile Option Values Setting this option to NO enables the processing of click history data and makes charts visible on the Application Usage Insights dashboards. If you've already been using Application Usage Insights charts or click history reports, they are disabled in the 22D update. You will need to re-enable them after you update, as a one-time step.

The processing of click history data and display of Application Usage Insights charts can only be enabled on the pod for all users. It can't be enabled for individual users.

Disable Login, Session, and Object Activity Data Collection

There might be cases when you don't want your application to collect login and object activity data on your employees. Login and object activity data are used both for Application Usage Insights as well as for reporting that uses the Sales - CRM Resource System Usage, and the Sales - CRM Object Activity subject areas.

The collection of object activity, log in and session data process runs automatically by default. To disable data collection turn off the ESS job "Refresh BI Reports Audit Data for User Adoption Reporting".

The collection of object activity, log in, and session data can only be disabled on the pod for all users. It can't be disabled for individual users.