Use this window to define an Oracle E-Business Suite user. This user is an authorized user of Oracle E-Business Suite, and is uniquely identified by a username.
Once defined, a new Oracle E-Business Suite user can sign on to Oracle E-Business Suite and access data through Oracle E-Business Suite windows.
Note: If you have upgraded from a previous release of Oracle E-Business Suite, ensure that you have run the Party Merge concurrent program to update your user data. If you have not run this program, you may receive errors in querying your user data.
For more information, see the Oracle Trading Community Architecture documentation.
Enter these fields for the user.
An application user enters this username to sign on to Oracle E-Business Suite.
The username should only contain characters allowed by Oracle Single Sign-On.
Tip: We recommend that you define meaningful user names, 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 his username to sign on to Oracle E-Business Suite.
A password must be at least five (5) characters and can be up to thirty (30) characters.
All characters are allowed except control characters, which are non-printable. Oracle encourages the use of non-alphanumeric characters because they add complexity, making passwords harder to guess.
This window does not display the password you enter. After you enter a password, you must re-enter it to ensure you did not make a typing error.
If the application user already exists and the two entries do not match, the original password is not changed and an error message is displayed.
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, he must change his password. If a user forgets his 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.
You can set the minimum length of Oracle E-Business Suite user passwords using the profile option Signon Password Length. If this profile option is left unset, the minimum length defaults to 5.
You can set the minimum number of days that a user must wait before being allowed to reuse a password with the Signon Password No Reuse profile option.
You can use the profile option Signon Password Hard to Guess to set rules for choosing passwords to ensure that they will be "hard to guess." A password is considered hard-to-guess if it follows these rules:
The password contains at least one letter and at least one number.
The password does not contain the username.
The password does not contain repeating characters.
The Signon Password Failure Limit profile option determines the maximum number of login attempts before the user's account is disabled.
For information on case sensitivity in passwords, see: Case Sensitivity in Oracle E-Business Suite User Passwords.
The Status field indicates the status of the user account. This field is display-only and values are generated by the system. This field is similar to Status in Oracle User Management for managing user accounts.
Possible statuses of a user account are:
Unassigned - This status is used for the moment of creating a new user in the form, before committing the transaction. Since a user ID hasn't been assigned yet at that moment, the record status is Unassigned.
Pending - This user account exists but cannot be used yet. For example, a user account with "Effective Dates" that are in the future would have a Pending status.
Locked - This user account is locked. For example, if a user has unsuccessfully tried to log in over the maximum number of tries allowed (per the profile option "Signon Password FailureLimit"), then the user account becomes locked.
Active - The status for a user account is Active if both of the following conditions are true:
The start date is not NULL and is before or equal to the current date
The end date is NULL or is after the current date
Inactive - This user has an inactive account. For example, a user account with "Effective Dates" that are in the past would have an Inactive status.
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.
For more information on using these fields, see the Oracle Trading Community Architecture documentation.
Enter the email address for this user.
Enter the fax number for this user.
Days - Enter the maximum number of days between password changes. A pop-up window prompts an application user to change his password after the maximum number of days you specify has elapsed.
Accesses - Enter the maximum allowed number of sign-ons to Oracle E-Business Suite allowed between password changes. A pop-up window prompts an application user to change his password after the maximum number of accesses you specify has elapsed.
Tip: We recommend that you requireall application users to make regular password changes. This reduces the likelihood of unauthorized access to Oracle E-Business Suite.
The user cannot sign on to Oracle E-Business Suite before the start date or 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 E-Business Suite because this information helps to provide an audit trail. You can deactivate an Oracle E-Business Suite 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.
Direct responsibilities are responsibilities assigned to the user directly.
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.
This field is for HRMS security only. See: Customizing, Reporting, and System Administration in Oracle HRMS.
This field is enabled only if the profile Enable Security Groups is enabled.
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.
Indirect responsibilities are used with Oracle User Management only. A user may "inherit" an indirect responsibility through membership of a group to which the responsibility has been assigned.
This block is read-only.
Securing attributes are used by some 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.
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.