create a user in oracle apps


Define User

Navigate to:
Security > User > Define





Tip:  Tab through the fields when completing this form and watch the status bar for field specific prompts

User Name:
Enter the name of an application user. An application user enters this username to sign on to Oracle Applications and/or Oracle Self-Service Web Applications.  The  following guidelines apply to this field:
·         Can only be one word
·         Define a standard naming convention such as first initial, last name.
·         User name is always in Upper Case
·         Alphanumeric ('A' through 'Z') and Numeric ('0' through '9') are permitted.
Description:
Enter a description for this user.  Enter a user friendly name as description e.g. ‘Jane Doe’.

Note:  Description entered is displayed on the user’s OSSWA home page when signing on to Self Server Web Applications.

Tip:  You may also enter html tags in this field to format how the user’s name is displayed, for example, entering ‘<font color=”red”>Jane Doe</font>’, will display the user’s name in red on the OSSWA home page.
Password:
Enter the initial password of an application user.  The user will be prompted to change this password the first time they sign in.  The following guidelines apply to this field:
·         Must be at least 5 characters and no more than 100.
·         Alphanumeric ('A' through 'Z') and Numeric ('0' through '9') are permitted.

Note:  You will need to enter this field twice for verification
Person:
If this user is an employee select the employee's full name from the LOV.
Customer:
If this user is a customer select the customer's name from the LOV.
Supplier:
If this user is a supplier select the supplier's name from the LOV.
E-Mail:
Optionally enter the email address for this user.
Fax:
Optionally enter the fax number for this user.
Password Expiration> Days: 
Maximum number of days between password changes.
Password Expiration> Accesses:
Maximum allowed number of sign-ons to Oracle Applications or Self-Service Web Applications allowed between password changes.
Password Expiration> None:
Select none if you do not wish to have passwords expire by number of days or accesses.
Effective Dates>From:
Optionally enter a start date when this user can begin accessing the applications.
Effective Dates>To:
Optionally enter an end date when this user can no longer access the applications.
Responsibility:
Select a responsibility you wish to assign this user.

Note: In order for a user to access the applications they must be assigned at least one responsibility. Once a user is assigned to a responsibility it cannot be deleted, therefore, you must deactivate the responsibility by entering an end date. If you want to reactivate a deactivated responsibility for a user change the end date to a date after the current date or highlight the current end date and delete.
Responsibility>
Effective Dates>From:
Optionally enter a start date when this user can begin accessing the applications with this responsibility.
Responsibility>
Effective Dates>To:
Optionally enter an end date when this user can no longer access the applications with this responsibility.

Securing Attributes
Securing Attributes are used by the Oracle Self-Service Web Applications. Securing Attributes allow rows of data to be visible to specified users or responsibilities based on the values contained in the row.  Securing Attributes must be assigned at both the user and responsibility level.

Example: If you want to restrict the user Jane with responsibility of 'Admin' to see only those rows where customer_id = 1000 then assign the securing attribute ICX_CUSTOMER_ID to the responsibility 'Admin' then the securing attribute ICX_CUSTOMER_ID and value of 1000 to the user, Jane.

Navigate to:
Security > User > Define
Select:
Securing Attributes



Securing Attributes> Attributes:
Select an attribute from the LOV to be used to determine which records this user can access.
Securing Attributes> Application:
Oracle Self-Service Web Application
Securing Attributes> Value:
Enter the value to be used to determine which specific rows of records this user can access.
                       

Excluding Attributes
Excluding Attributes are used by the Oracle Self-Service Web Applications and are defined at the responsibility level.  Please refer to the AOL Application Responsibilities Training.doc

Note:  Once assigned a responsibility, a user is excluded from any columns defined as excluding attributes for that responsibility.