How to create a new user in Oracle E-Business Suite Application?

Oracle E-Business Suite is a widely used ERP product of Oracle. There comes a situation where we need to create a new user in Oracle ERP. Follow the below steps to create a new user in Oracle E-Business Suite Application.

Navigate to the path System Administrator ->Security->User->Define

new user in Oracle E-Business Suite 1

Steps to create a new user in Oracle E-Business Suite

First of all, enter a value in User Name.

The Password field is secured as it will show * instead of characters. The entry in password field is done for two times.

Enter other information like Description, Person, Customer, Supplier, E-Mail and Fax as and how you require.

new user in Oracle E-Business Suite 2

(1) Effective Dates

Effective Dates From and To is the period between which the user is active. You cannot delete an application user from Oracle Applications because this information helps to provide an audit trail. You can deactivate an Oracle Applications user at any time by setting the End Date to the current date.

If you wish to reactivate a user, change the End Date to a date after the current date, or clear the End Date field.

If you want to deactivate the user, enter the end date in Effective Dates To field.

The blank end date will make user active for an indefinite time.

You can reactivate user by removing the date from Effective Dates To field or extending it to the future date.

(2) Password Expiration


Password Expiration field denotes the maximum number of days between password changes. The majority of the times developers select option None but you can select as per your business requirement.

The rules for password expiration can be set with the help of profile options

a) Minimum password length – Minimum length of the password can be defined using profile option Signon       Password Length. The default length is 5 if nothing is entered.

b) Minimum number of days for password reset – To set minimum number of days a user must wait to reuse the password, give value in Signon Password No Reuse profile option

c) Make it difficult to guess rule – Use profile option Signon Password Hard to Guess to set rules as below

    • Password contains at least one letter and at least one number.
    • Username is not allowed in the password.
    • The password does not contain repeating characters.


Accesses field is the maximum number of sign-ins allowed between password changes.

(3) Assign responsibility to the user


Assign the responsibilities directly to the user from List of Values available in Responsibility field.


Once you select responsibility, an application of that responsibility will automatically appear in Application field.

Security Group

This field is for HRMS security only.


From date is the date from which the responsibility is effective. To date is the end date till which the responsibility will be active. You can deactivate any responsibility by adding value in To field. If you want to reactivate that user, remove the date from To field or give some future date. Blank To field will keep user active for an indefinite time.

Indirect Responsibilities

Indirect responsibilities are used with Oracle User Management only. A user may “inherit” an indirect responsibility through membership in a group to which the responsibility has been assigned.

Securing Attributes

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.

For example, to allow a user in the Order Management responsibility to see rows containing an ORDER_ID value of 100, assign the securing attribute of ORDER_ID to the Order Management responsibility. Then give the user a security attribute ORDER_ID value of 100.

When the user logs into the Order Management responsibility, the only order data they have access to has an ORDER_ID value of 100.


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.


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

If you liked the above post, please leave your comments below.

You can also Subscribe here to stay updated on latest posts of


Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.