Defining a Responsibility
When you define a responsibility, you assign to it some or all of the components described below:
A Data Group defines the mapping between Oracle Applications products and ORACLE IDs. A Data Group determines which Oracle database accounts a responsibility's forms, concurrent programs, and reports connect to. See: Defining Data Groups.
A request security group defines the concurrent programs, including requests and request sets, that may be run by an application user under a particular responsibility. See: Defining a Request Security Group. See: Organizing Programs into Request Groups.
A menu is a hierarchical arrangement of application functions (forms) that displays in the Navigate window. Menus can also point to non-form functions (subfunctions) that do not display in the Navigate window, but that define the range of application functionality available for a responsibility. Each responsibility is associated with a menu. See: Overview of Function Security.
Function and Menu
A responsibility may optionally have function and menu exclusion rules associated with it to restrict the application functionality enabled for that responsibility. See: Overview of Function Security.
Additional Notes About Responsibilities
All Oracle Applications products are installed with predefined responsibilities. Consult the reference guide for your Oracle Applications product for the names of those predefined responsibilities.
Additionally, instances of the major components that help define a responsibility (data groups, request security groups, menus, and functions) are predefined for Oracle Applications.
Responsibilities and Request Security Groups
When a request group is assigned to a responsibility, it becomes a request security group.
From a standard submission form, such as the Submit Requests form, users can run only the reports, concurrent programs, and request sets that are in their responsibility's request security group.
- If you do not include the Submit Requests form on the menu for a responsibility, then you do not need to assign a request security group to the responsibility.
- If a request security group is not assigned to a responsibility, then users working under that responsibility cannot run any reports, request sets, or other concurrent programs from a standard submission form.
Responsibilities and Function Security
Oracle Applications GUI-based architecture aggregates several related business functions into a single form. Parts of an application's functionality may be identified as individual Oracle Applications functions, which can then be secured (i.e., included or excluded from a responsibility).
See: Overview of Function Security
Overview of Oracle Applications Security
Defining a Request Security Group
How Function Security Works
Implementing Function Security
Defining a New Menu Structure