|Oracle Payables Implementation Guide|
Part Number E12795-04
Use function security to control access to Payables functionality.
Each Payables form performs one or more business functions. 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 an Payables responsibility.
Payables comes predefined with three responsibilities, each with its own set of preregistered functions assigned to it: Payables Manager, Payables Inquiry, Payables Purge. Your system administrator can register additional functions and can customize your responsibilities by assigning or not assigning new functions to existing responsibilities, or by creating new responsibilities.
There are two types of functions: form and subfunction.
Form. A form invokes an Oracle Forms form, for example, the Invoice Workbench. You can navigate to a form using the Navigator.
Subfunction. A subfunction is a subset of a form's functionality. In other words, a subfunction is a function executed from within a form.
Subfunctions are often associated with buttons or other graphical elements on forms. For example, in the Invoices window form, you may want to restrict access to the Invoice Actions window. In this case, for all users that do not have the associated subfunction name assigned to their responsibility, the Actions button would not appear.
You cannot navigate to a subfunction from the Navigator.
Your System Administrator can submit the Function Security Menu Reports request set. This request set includes the Function Security Functions report, which shows a complete list of Payables functions assigned to the preseeded responsibilities.
Overview of Function Security, Oracle Applications System Administrator's Guide
How Function Security Works, Oracle Applications System Administrator's Guide
Implementing Function Security, Oracle Applications System Administrator's Guide
Defining a New Menu Structure, Oracle Applications System Administrator's Guide
Copyright © 1988, 2010, Oracle and/or its affiliates. All rights reserved.