An application user enters this username to sign on to Oracle Applications.
Suggestion: We recommend that you define meaningful usernames, such as the employee's first initial followed by their last name. Or, for a group account, you can define the application username so as to indicate the purpose or nature of the group account.
Enter the initial password of an application user. An application user enters this password along with her or his username to sign on to Oracle Applications.
If the application user already exists and the two entries do not match, the original password is NOT changed, and you navigate automatically to the next field.
If you are defining a new application user and the two entries do not match, you are required to enter the password again. For a new user, you cannot navigate to the next field until the two entries match.
The first time an application user signs on, they must change his or her password. If a user forgets their password, you can reassign a new password in this field.
As System Administrator, you can set an initial password or change an existing password, but you cannot access the user's chosen password.
Person, Customer, and Supplier
Use these fields to enter the name of an employee (person), customer, or supplier contact. Enter the last name and first name, separated by a comma, of the employee, customer, or supplier who is using this application username and password. Use the List of Values to select a valid name.
Enter the E-mail address and/or fax number for this user.
Enter the maximum number of days between password changes. A pop-up window prompts an application user to change her or his password after the maximum number of days you specify has elapsed.
Enter the maximum allowed number of sign-ons to Oracle Applications allowed between password changes. A pop-up window prompts an application user to change her or his password after the maximum number of accesses you specify has elapsed.
Suggestion: We recommend that you require application users to make frequent password changes. This reduces the likelihood of unauthorized access to Oracle Applications.
The user cannot sign onto Oracle Applications before the start date and after the end date. The default for the start date is the current date. If you do not enter an end date, the username is valid indefinitely.
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.
Select the name of a responsibility you wish to assign to this application user. A responsibility is uniquely identified by application name and responsibility name.
You cannot delete a responsibility because this information helps to provide an audit trail. You can deactivate a user's responsibility at any time by setting the End Date to the current date.
If you wish to reactivate the responsibility for the user, change the End Date to a date after the current date, or clear the End Date.
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.
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 for the attribute you want used to determine which records this user can access.
Defining a Responsibility
Overview of Function Security