Any person who needs to access the Oracle Applications should have a user id. A user is registered by System Administrator (or anybody having System Administrator responsibility). Often, first the person is registered in HR module as an employee or contractor and then associated with the user. The following screen shows the user definition screen.
A user is assigned a user name and password. The password needs to be reset on the first login of the user.
The person field is a list of value coming from HR. If the person is already registered in HR, his name is selected in the Person field.
User can be assigned the access for a limited period by giving Effective Dates.
User can be forced to change password periodically by giving password expiration date values.
User is also assigned the responsibilities. The responsibilities can be assigned for a particular period by giving effective dates.
Oracle Applications comes with default some default users like SYSADMIN, APPSMGR, and AUTOINSTALL. These users are used for carrying out administrative tasks in Oracle Applications.
Technical Details on User Definition
User definition is stored in FND_USER table. This table is owned by FND module. The main fields of this table are as follows:
User_ID Automatically generated unique number
User_Name Name as entered on the user definition screen
Employee_ID Employee ID from HR module. Populated if the Employee name is associated with the user.
Party_ID Party_ID from HZ_PARTIES table. Each user is also created in HZ_PARTIES table as a party.
Whenever user creates or updates a transaction in any module, the transaction record is stamped with the user id. The user id is usually stored as CREATED_BY or LAST_UPDATED_BY field in the respective transaction table.
User ID of the current user can be accessed using a package FND_GLOBAL. Suppose, we need to get the current user id in a custom program. We can get the user id using the following code:
l_user_id := FND_GLOBAL.USER_ID;
When a user record is created, it is also automatically inserted in the workflow role table (WF_ROLES). This table is used for sending workflow notification to the user whenever a workflow requires such notification to be sent.
No comments:
Post a Comment