Audit users in Oracle Applications

The auditing in Oracle Application could be a three step process.
Setting up Audit
Review the audit information
Purge the Audit information

Setting up front end access Audit:

As a standard feature, Oracle application does store information for user logon, wrong password attempt, and concurrent process execution. To enable the auditing at user, responsibility and form access, we need to enable the profile option ‘Sign-On: Audit Level’. This profile option has four values. Each value has different capability to capture audit information.

1. If the value is setup as ‘None’
No additional information is tracked.

2. If the value is setup as ‘User’
System tracks:
who signs on to Oracle Apps
the time users log on and off
the terminals in use

3. If the value is setup as ‘Responsibility’
System tracks:
User Info
the responsibilities user choose
how much time users spend using each responsibility

4. If the value is setup as ‘Form’
Tracks:
User Info
Responsibility Info
the forms users choose
how long users spend using each form

Apart from this below mentioned information is logged in oracle by default

Unsuccessful Logins

Unsuccessful password attempts are automatically recorded in the APPLSYS.FND_UNSUCCESSFUL_LOGINS and ICX.ICX_FAILURES tables. There is no way to disable this functionality.

Concurrent Requests

All concurrent requests are recorded in the FND_CONCURRENT_REQUESTS table. There is no configuration required

Review the Audit information

There are two methods to access and review end user access audit information

Using Oracle Applications
There are standard reports to access signon, unsuccessful signon, responsibility usage, form usage, and concurrent request usage. These reports are accessed through the system administrator responsibility. The following are the standard reports for end-user auditing –
Signon Audit Users
Signon Audit Responsibilities
Signon Audit Forms
Signon Audit Concurrent Requests
Signon Audit Unsuccessful Logins
Or the same information can be retrieved from the sql plus as the information captured in the below tables

FND_LOGINS – holds information about users login to system, when and how long.

This table holds one row for each login.

FND_LOGIN_RESPONSIBILITIES – holds information about changes of responsibilities, when and how long being at each responsibility.
For each change this table holds one row with values that identify the user's login session, the user's current responsibility, and when the user is in the responsibility

FND_LOGIN_RESP_FORMS – holds information about using forms, when and how long.
This table holds one row for each form used in the same session with values that identify the user's login session, current responsibility, when and how long using each form.

In order to see the user audit information, there are 5 reports (concurrents) that you can use:
1) Signon Audit Concurrent Request
Show concurrent requests audit information – the user who run this request, when, from which responsibility and form, for all concurrent requests run in the system.

2) Signon Audit Forms
Show audit information about which user enter to which form, when and for how long.

3) Signon Audit Responsibilities
Show audit information about which user choose which responsibility, when and how long he stayed in each responsibility.

4) Signon Audit Unsuccessful Logins
Show audit information about unsuccessful logins to Oracle Applications.

5) Signon Audit Users
Show audit information about who sign on, when and for how long.


- In addition there is a monitor screen where you can see online data about users connected to system, which responsibility and form they are using and how long they are connected.
You can use this monitor from:
System Administrator responsibility -> security -> User -> Monitor.

- To inform users about unsuccessful logins to their account, you can set the “Sign-On:Notification” profile to Yes.