Example 01
select distinct fu.user_name User_Name,
fr.RESPONSIBILITY_KEY Responsibility,
ic.first_connect Connect_Start,
ic.last_connect Connect_Stop,
decode(ic.Function_type,
'JSP',
'OAF Form',
'FORM',
'Oracle Java Form',
'') Menu,
ic.function_id
from fnd_user fu, fnd_responsibility fr, icx_sessions ic
where fu.user_id = ic.user_id
AND fr.responsibility_id = ic.responsibility_id
AND ic.disabled_flag = 'N'
AND ic.responsibility_id is not null
and fu.user_id = :UserID
FND tables for login details
How to find user logged in Oracle Applications and and I would like restrict some user login during weekends to oracle applications.
How Logged to Forms
select distinct fu.user_name User_Name,fr.RESPONSIBILITY_KEY Responsibility from fnd_user fu,
fnd_responsibility fr, icx_sessions ic
where fu.user_id = ic.user_id AND
fr.responsibility_id = ic.responsibility_id AND
ic.disabled_flag=’N’ AND
ic.responsibility_id is not null AND
ic.last_connect like sysdate;
There are three primary tables which are involved in using the system profile ‘Sign-On:Audit Level’:
1) FND_LOGINS
2) FND_LOGIN_RESPONSIBILITIES
3) FND_LOGIN_RESP_FORMS
- When the profile is set to “User”, the only table that gets updated is the table FND_LOGINS and only one record per user session
- When the profile is set to “Responsibility”, both FND_LOGINS and FND_LOGIN_RESPONSIBILITIES will be updated:
a) FND_LOGINS gets only one record per user session
b) FND_LOGIN_RESPONSIBILITIES will be updated with one record for each responsibility selected during the session
- When the profile is set to “Form” all three tables are involved:
a) FND_LOGINS gets only one record per user session
b) FND_LOGIN_RESPONSIBILITIES will be updated with one record for each responsibility selected during the session
c) FND_LOGIN_RESP_FORMS will be updated with one record for each form selected during the session
In terms of performance, the data capture has negligible overhead.
No comments:
Post a Comment