Use this window to define a responsibility. Each application user is assigned at least one responsibility.
Note: The information in this section can also be used to define a responsibility in the HTML-based Create Responsibility page.
A responsibility determines whether the user accesses Oracle E-Business Suite or Oracle Mobile Applications; which applications functions a user can use; which reports and concurrent programs the user can run; and which data those reports and concurrent programs can access.
Responsibilities cannot be deleted. To prevent a responsibility from being used, set the Effective Date's To field to a past date and restart Oracle E-Business Suite.
See: Overview of Function Security
Before defining your responsibility, do the following:
Use the Data Groups window to list the ORACLE username your responsibility's concurrent programs reference on an application-by-application basis.
Use the Request Groups window to define the Request Group you wish to make available with this responsibility.
Use the Menus window to view the predefined Menu you can assign to this responsibility.
An application name and a responsibility name uniquely identify a responsibility.
If you have multiple responsibilities, a pop-up window includes this name after you sign on.
The owning application for the responsibility.
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 the internal key for the responsibility that is used by loader programs, (concurrent programs that load messages, user profiles, user profile values, and other information into Oracle E-Business Suite tables). The responsibility key is unique per application.
Avoid using the following characters in the responsibility keys: !, ", ;, [, ], (, ), {, }, %, |, <, >.
Enter the start/end dates on which the responsibility becomes active/inactive. The default value for the start date is the current date. 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 later, either change the end date to a date after the current date, or clear the end date.
This is the navigator from which the responsibility will be available (Oracle E-Business Suite forms navigator, mobile navigator).
A responsibility may be associated with only one Oracle E-Business Suite system.
Note: Data groups are used for backward compatibility only. Oracle Application Framework does not support the data groups feature. You should not define any custom data groups.
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.
The menu whose name you enter must already be defined with Oracle E-Business Suite. See: Menus.
Specify a request security group to associate the responsibility to a set of requests, request sets, or concurrent programs that users logged in with this responsibility can run from the Submit Requests window. Note that such users can also access requests from a Submit Requests window you customize with a request group code through menu parameters
Note: The Request Security Groups feature is provided for backward compatibility.
New responsibilities should be created in accordance with Role-Based Access Control and should not have a default request security group.
See:
Overview of Oracle E-Business Suite Security
Customizing the Submit Requests Window Using Codes
Note: Menu exclusions should be used for backward compatibility only.
Define function and menu exclusion rules to restrict the application functionality accessible to a responsibility.
Select either Function or Menu as the type of exclusion rule to apply against this responsibility.
When you exclude a function from a responsibility, all occurrences of that function throughout the responsibility's menu structure are excluded.
When you exclude a menu, all of its menu entries, that is, all the functions and menus of functions that it selects, are excluded.
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 E-Business Suite.
Oracle HTML-based applications use columns, rows and values in database tables to define what information users can access. Table columns represent attributes that can be assigned to a responsibility as Securing Attributes or Excluded Attributes. These attributes are defined in the Web Application Dictionary.
Use the List of Values to select valid attributes. You can assign any number of Excluded Attributes to a responsibility.
Use the List of Values to select valid attributes. You can assign any number of securing attributes to the responsibility.