USERS

Overview
Users and Responsibilities are created in oracle applications in order to control the
access to the data. Users are assigned a set of responsibilities through which they
can retrieve or modify certain set of data. Responsibility is a grouping of access in a
logical manner. Accounts payable responsibility would contain all the privileges to
create invoices, make payments etc. All the users from the payables department
would be given this responsibility. You can create users, responsibility through
system administrator responsibility in oracle applications.

Creation of User
Navigation – System Administrator ->Security -> User -> Define

Figure 1. Create User Navigation

Follow the above the navigation path and click on Define. You will see following screen in front of
you.
Figure 2. Create User

Fields
UserName Give the username in this field.
Password Enter desired password twice in this field. You would be required to
change the password when you login first time with this username.
Description Provide brief description of the user in this field.

Password Expiration Days

Νο. ο φ ∆ α ψ σ α φ τ ε ρ ω η ι χ η τ η ε π α σ σ ω ο ρ δ
ωιλ λ ε ξ π ι ρ ε φ ο ρ τ η ε υ σ ε ρ .
Accesses
Νο. ο φ Α χ χ ε σ σ ε σ α φ τ ε ρ ω η ι χ η τ η ε π α σ σ
ωο ρ δ ω ι λ λ ε ξ π ι ρ ε φ ο ρ τ η ε υ σ ε ρ .
None Τ η ε π α σ σ ω ο ρ δ ω ι λ λ ν ε ϖ ε ρ ε ξ π ι ρ ε
Person You can attach employee to this user. This is used for HRMS applications

Customer To attach customer to this user.

Supplier To attach supplier to this user.

Email Provide email address for the user. Its use to send notifications to the user
through oracle applications.
Fax Fax number for the user.

Effective Dates From and To dates between which the user would be active.
Responsibilities List of responsibilities assigned to the user.

Figure 3. Create User Indirect Responsibilities

Securing attributes are used by Oracle HTML-based applications to allow rows
(records) of data to be visible to specified users or responsibilities based on the
specific data (attribute values) contained in the row. You may assign one or more
values for any of the securing attributes assigned to the user. If a securing attribute
is assigned to both a responsibility and to a user, but the user does not have a value
for that securing attribute, no information is returned for that attribute.

For example, to allow a user in the ADMIN responsibility to see rows containing a
CUSTOMER_ID value of 1000, assign the securing attribute of CUSTOMER_ID to the
ADMIN responsibility. Then give the user a security attribute CUSTOMER_ID value of
1000.

When the user logs into the Admin responsibility, the only customer data they have
access to has a CUSTOMER_ID value of 1000.

Fields
Attribute : Select an attribute you want used to determine which records this user
can access. You can select from any of the attributes assigned to the user's
responsibility.

Value : Enter the value for the attribute you want used to determine which records
this user can access.

Creation of Responsibility
Navigation – System Administrator ->Security -> Responsibility -> Define
Figure 5. Create Responsibility Navigation

Follow the above the navigation path and click on Define. You will see following screen in front of
you.
Figure 6. Create Responsibility

Fields
Responsibility Name - If you have multiple responsibilities, a pop-up window
includes this name after you sign on.

Application - This application name does not prevent the user of this responsibility
from accessing other applications' forms and functions if you define the menu to
access other applications.

Responsibility Key - This is a unique name for a responsibility that is used by

loader programs. Loaders are concurrent programs used to "load" such information
as messages, user profiles and user profile values into your Oracle Applications
tables. To help ensure that your responsibility key is unique throughout your system,
begin each Responsibility Key name with the application short name associated with
this responsibility.

Effective Dates From/To - Enter the start/end dates on which the responsibility
becomes active/inactive. The default value for the start date is the current date, and
if you do not enter an end date, the responsibility is valid indefinitely.