EBS Security Architecture Overview

By Jag - September 10, 2012
Q21: What represents hierarchy of the function security in Oracle Applications?
Q22: What is responsibility?
Q23: What is function?
Q24: What is menu?
Q25: Is a menu item always attached to a function?
Q26: Give an example about the relationship of responsibility,function and menu?
Q27: Give an example about the difference between developing a screen and creating a menu?
Q28: What is request group?
——————————————————————————–
Q21: What represents hierarchy of the function security in Oracle Applications?
The hierarchy of the function security in Oracle Applications includes:
FND User
    |
Responsibility
    |          |
Request Group  Menu
               |
               Menu
               |   |
               |   Function
               |   Function
               |   Function
               Function
Q22: What is responsibility?
A responsibility is a collection of business functionalities, such as UI screens and reports, that is granted to Oracle Applications users for the purpose of access control to the screens and data that are related to the user’s role within the organization.
What a user can do in Oracle Applications is determined by assigned responsibilities.
Q23: What is function?
You can think of functions as units of an application’s functionality such as UI screens.
Q24: What is menu?
A menu is a reusable grouping of application functionality and consists of functions and other menus. Menus can have multiple functions attached to them.
Q25: Is a menu item always attached to a function?
No. Sometimes a menu item is attached to another menu. By doing so, you effectively create submenus within the menu, which creates a menu nesting. However, a function must be attached to a menu in order for it to be accessed by the end user.
Q26: Give an example about the relationship of responsibility,function and menu?
For example, every HTML and Forms-based screen is associated with a corresponding function, which can get attached to menus so that users can access it through an assigned responsibility. To recap, a responsibility is attached to a menu, and a menu can have several menu items. Each menu item can be attached to a function, and the function is attached to a screen. At the time of defining a function, you specify a screen name and optional parameters with their default values.
Q27: Give an example about the relationship between screen and menu?
a) Menus never pass parameters to the screens, but a function can.
b) A function does not always pass parameters and parameter values to a screen. If the screen has not been developed to be dependent on any parameter, then of course there is no need to pass any parameters.
c) Screen can be developed in a manner that its functionalities can differ depending upon the parameters that are passed into that screen.
d) When a given screen is attached to two different functions, each function can pass different parameters to the screen.
e) Even though the same screen is reachable via two different menus, the functionality exposed by the screen can vary, depending upon the parameters passed by the function to the screen.
f) The typical example is when a screen is developed to cater to both Data Entry and Read Only modes. For example, if the page flow requires this screen in Read Only mode, you can create a function for this screen and pass parameter to it so that the underlying code can pick it up at runtime and render the screen in Read Only mode
Q28: What is request group?
A request group is a grouping of reports and concurrent programs that is assigned to a responsibility. For example, custom reports have to be attached to a request group before the end users can access them through the responsibility.
  • Share:

You Might Also Like

0 comments