Function security lets you restrict application functionality to authorized users.
Application developers register functions when they develop forms. A System Administrator administers function security by creating responsibilities that include or exclude particular functions.
Basic Function Security
- Group the forms and functionality of an application into logical menu structures that will appear in the Navigator
- Assign a menu to one or more responsibilities
- Assign one or more responsibilities to one or more users
Advanced Function Security
- Oracle Applications GUI-based architecture aggregates several related business functions into a single form
- Not all users should have access to every business function in a form
- Oracle Applications provides the ability to identify pieces of application logic as functions
- Functions can be secured on a responsibility basis (that is, included or excluded from a responsibility)
A function is a part of an application's functionality that is registered under a unique name for the purpose of assigning it to, or excluding it from, a menu (and by extension, a responsibility).
There are several types of functions: form functions, subfunctions, and non-form functions. We often refer to a form function simply as a form.
Form (Form Function)
A form function (form) invokes an Oracle Forms Developer form. Form functions have the unique property that you may navigate to them using the Navigator window.
A subfunction is a securable subset of a form's functionality: in other words, a function executed from within a form.
A developer can write a form to test the availability of a particular subfunction, and then take some action based on whether the subfunction is available in the current responsibility.
Subfunctions are frequently associated with buttons or other graphical elements on forms. For example, when a subfunction is enabled, the corresponding button is enabled.
However, a subfunction may be tested and executed at any time during a form's operation, and it need not have an explicit user interface impact. For example, if a subfunction corresponds to a form procedure not associated with a graphical element, its availability is not obvious to the form's user.
Self-Service Function (Non-form Function)
Some functions provide a way to include other types of code, such as HTML pages or Java Server Pages (JSPs) on a menu and responsibility. These functions are typically used as part of the Oracle Self-Service Web Applications. These functions include other information such as URLs that point to the appropriate files or functionality.
A menu is a hierarchical arrangement of functions and menus of functions that appears in the Navigator. Each responsibility has a menu assigned to it.
The Oracle Applications default menu appears as the pulldown menu across the top of a window and is not generally controlled using Function Security.
A menu entry is a menu component that identifies a function or a menu of functions. In some cases, both a function and a menu of functions correspond to the same menu entry. For example, both a form and its menu of subfunctions can occupy the same menu entry.
A responsibility defines an application user's current privileges while working with Oracle Applications. When an application user signs on, they select a responsibility that grants certain privileges, specifically:
- The functions that the user may access. Functions are determined by the menu assigned to the responsibility.
- The concurrent programs, such as reports, that the user may run (request security group).
- The application database accounts that forms, concurrent programs, and reports connect to (data group).