APPSINFODB – Information Technology Group

Finding Solutions for DBA's to smile…….!!!!!!! DBA its just not Administration, its core of customer’s data integrity

  • Blog Stats

    • 34,994 hits
  • Visitors

    free counters
  • Vistors Access

  • Calendar

    April 2009
    M T W T F S S
    « Mar   May »
     12345
    6789101112
    13141516171819
    20212223242526
    27282930  
  • Archives

  • Authors

Oracle Application Auditing

Posted by appsinfo on April 29, 2009

Oracle Application Auditing

 

We have 2 types of audit in Oracle Applications:


1) Audit users who sign in to Oracle Applications
2) Audit changed data in database

 

Login Tables used in Audit

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 (concurrent) that you can use:


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.
Signon Audit Forms: Show audit information about which user enter to which form, when and for how long.
Signon Audit Responsibilities: Show audit information about which user choose which responsibility, when and how long he stayed in each responsibility.
Signon Audit Unsuccessful Logins: Show audit information about unsuccessful logins to Oracle Applications.
Signon Audit Users: Show audit information about who sign on, when and for how long.


Sign-On: Audit Level profile:


This profile can be set to one of the four possible values at site level,

What you need to do in order to enable it is:


NONE – no audit enabled (Default value)
USER – audit user login to system, the logon time and the logoff time.
RESPONSIBILITY – audit all the above + which responsibilities the user chose and how long he stayed in each responsibility.
FORM – audit all the above + which forms the user used and how long he stayed in each form.

At each level audit information is populated in the tables:


USER – populates the FND_LOGINS table only.
RESPONSIBILITY – populates FND_LOGINS and FND_LOGIN_RESPONSIBILITIES tables.
FORM – populates FND_LOGINS, FND_LOGIN_RESPONSIBILITIES and FND_LOGIN_RESP_FORMS tables.

You can see online data using monitor screen for the 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.

For more information about audit you can read “Oracle Applications System Administrator’s Guide – Security Release 11i” – Chapter 5 – User and Data Auditing

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

 
%d bloggers like this: