Note: Responsibilities cannot be deleted. To remove a responsibility from use, set the Effective Date's To field to a past date. You must restart Oracle Applications to see the effect of your change.
See: Overview of Function Security
If you have multiple responsibilities, a pop-up window includes this name after you sign on.
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.
This is a unique name for a responsibility that is used by loader programs. Loaders are concurrent programs used to "load" such information as messages, user profiles and user profile values into your Oracle Applications tables. To help ensure that your responsibility key is unique throughout your system, begin each Responsibility Key name with the application short name associated with this responsibility.
The menu whose name you enter must already be defined with Oracle Applications. See: Menus.
Web Host Name
If your Web Server resides on a different machine from your database, you must designate the host name (URL) here. Otherwise, the Web Host Name defaults to the current database host server.
Web Agent Name
Enter the PL/SQL Agent Name for the database used by this responsibility. If you do not specify an Agent Name, the responsibility defaults to the agent name current at log-on.
Enter 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.
You cannot delete a responsibility because its information helps to provide an audit trail. You can deactivate a responsibility at any time by setting the end date to the current date. If you wish to reactivate the responsibility, change the end date to a date after the current date, or clear the end date.
The data group defines the pairing of application and ORACLE username.
Select the application whose ORACLE username forms connect to when you choose this responsibility. The ORACLE username determines the database tables and table privileges accessible by your responsibility. Transaction managers can only process requests from responsibilities assigned the same data group as the transaction manager.
If you do not assign a request security group to this responsibility, a user with this responsibility cannot run requests, request sets, or concurrent programs from the Submit Requests window, except for request sets owned by the user. The user can access requests from a Submit Requests window you customize with a request group code through menu parameters.
Overview of Oracle Applications Security
Customizing the Submit Requests Window Using Codes
Select either Function or Menu as the type of exclusion rule to apply against this responsibility.
Select the name of the function or menu you wish to exclude from this responsibility. The function or menu you specify must already be defined in Oracle Applications.
Defining Attributes: (Oracle Self-Service Applications for the Web User's Guide)
Use the List of Values to select valid attributes. You may assign any number of securing attributes to the responsibility.
Use the List of Values to select valid attributes. You can assign any number of Excluded Attributes to a responsibility.