Oracle Apps Tutorials : Sys Admin - Users and Responsibilities This tutorial provides you with a conceptual overview

of users and responsibilities, covering the following topics: Creation of User, Creation of Responsibilities and Assigning Responsibilities to 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. ou can create users, responsibility through system administrator responsibility in oracle applications. Creation of User !avigation " #ystem Administrator $%#ecurity $% User $% &efine

'igure (. Create User !avigation 'ollow the above the navigation path and click on &efine. following screen in front of you. ou will see

'igure ). Create User

'igure *. Create User +ndirect Responsibilities

'igure ,. Create User #ecuring Attributes Fields User!ame $-ive the username in this field. .assword $ /nter desired password twice in this field. ou would be re0uired to change the password when you login first time with this username. &escription $ .rovide brief description of the user in this field. .assword /1piration $ &ays $ !o. of &ays after which the password will e1pire for the user. Accesses $ !o. of Accesses after which the password will e1pire for the user. !one $ The password will never e1pire .erson $ ou can attach employee to this user. This is used for 2R3# applications Customer $ To attach customer to this user. #upplier $ To attach supplier to this user.

/mail $ .rovide email address for the user. +ts use to send notifications to the user through oracle applications. 'a1 $ 'a1 number for the user. /ffective &ates active. $ 'rom and To dates between which the user would be

Responsibilities $ 4ist of responsibilities assigned to the user. #ecuring attributes are used by 5racle 2T34$based applications to allow rows 6records7 of data to be visible to specified users or responsibilities based on the specific data 6attribute values7 contained in the row. ou may assign one or more values for any of the securing attributes assigned to the user. +f 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. 'or e1ample, to allow a user in the A&3+! responsibility to see rows containing a CU#T53/R8+& value of (999, assign the securing attribute of CU#T53/R8+& to the A&3+! responsibility. Then give the user a security attribute CU#T53/R8+& value of (999. :hen the user logs into the Admin responsibility, the only customer data they have access to has a CU#T53/R8+& value of (999. Fields Attribute : #elect an attribute you want used to determine which records this user can access. ou can select from any of the attributes assigned to the user;s responsibility. Value : /nter the value for the attribute you want used to determine which records this user can access. Creation of Responsibility !avigation " #ystem Administrator $%#ecurity $% Responsibility $% &efine

'igure <. Create Responsibility !avigation 'ollow the above the navigation path and click on &efine. following screen in front of you. ou will see

'igure =. Create Responsibility Fields Responsibility ame $ +f 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 !ey $ This is a uni0ue name for a responsibility that is used by loader programs. 4oaders are concurrent programs used to >load> such information as messages, user profiles and user profile values into your 5racle Applications tables. To help ensure that your responsibility key is uni0ue throughout your system, begin each Responsibility ?ey name with the application short name associated with this responsibility. "ffective #ates From$To $ /nter 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. ou cannot delete a responsibility because its information helps to provide an audit trail. ou can deactivate a responsibility at any time by setting the end date to the current date. +f you wish to reactivate

the responsibility, change the end date to a date after the current date, or clear the end date. Available From $ A responsibility may be associated with only one applications system. #elect between 5racle #elf$#ervice :eb Applications or 5racle Applications. #ata %roup $ !ame@Application The data group defines the pairing of application and 5RAC4/ username. #elect the application whose 5RAC4/ username forms connect to when you choose this responsibility. The 5RAC4/ username determines the database tables and table privileges accessible by your responsibility. Transaction managers can only process re0uests from responsibilities assigned the same data group as the transaction manager. &enu $ The menu whose name you enter must already be defined with 5racle Applications. 'eb (ost ame $ +f your :eb #erver resides on a different machine from your database, you must designate the host name 6UR47 here. 5therwise, the :eb 2ost !ame defaults to the current database host server. 'eb A)ent ame $ /nter the .4@#A4 Agent !ame for the database used by this responsibility. +f you do not specify an Agent !ame, the responsibility defaults to the agent name current at log$on. Re*uest %roup ame$Application $ +f you do not assign a re0uest security group to this responsibility, a user with this responsibility cannot run re0uests, re0uest sets, or concurrent programs from the #ubmit Re0uests window, e1cept for re0uest sets owned by the user. The user can access re0uests from a #ubmit Re0uests window you customiBe with a re0uest group code through menu parameters. &enu "+clusions ,loc&efine function and menu e1clusion rules to restrict the application functionality accessible to a responsibility. Type : #elect either 'unction or 3enu as the type of e1clusion rule to apply against this responsibility. :hen you e1clude a function from a responsibility, all occurrences of that function throughout the responsibility;s menu structure are e1cluded. :hen you e1clude a menu, all of its menu entries, that is, all the functions and menus of functions that it selects are e1cluded. ame : #elect the name of the function or menu you wish to e1clude from this responsibility. The function or menu you specify must already be defined in 5racle Applications.

'igure C. Create Responsibility /1cluded +tems "+cluded .tems : Use the 4ist of Dalues to select valid attributes. can assign any number of /1cluded Attributes to a responsibility ou

'igure E. Create Responsibility #ecuring Attributes