Previous  Next          Contents  Index  Navigation  Glossary  Library

Function Security in Oracle Receivables

Use function security to control user access to Receivables functions. By default, access to Receivables functionality is not restricted. Your system administrator customizes each responsibility at your site by including or excluding functions and menus in the Responsibilities window.

The following examples are common results that enforcing function security may produce:

For example, your system administrator creates a Billing responsibility that lets users enter, update and delete all transactions except commitments. Depending on the type of restriction he wishes to impose, he could exclude one or more of the following functions:

Comm: View Comm: Enter Comm: Update Comm: Delete

If Comm: View is excluded from a responsibility, the user cannot perform any functions on commitments (for example, enter, update, delete, or view).

If Comm: Enter is excluded from a responsibility, the user cannot enter new commitments, but can query existing commitments to view, update, or delete them.

If Comm: Enter, Comm: Update, and Comm: Delete are excluded, the user can only query existing commitments for review, he cannot perform any other actions.

Function Security is used in several Set Up windows and in each of the following workbenches: Transactions Workbench, Receipts Workbench, Collections Workbench, and the Customers Workbench. If a workbench is completely removed from the menu, all functions associated with the workbench are automatically removed.

See Also

Receivables Functions

How Function Security Works

Customer Window Parameters (when function security definitions conflict with window parameters)

Defining a New Menu Structure

         Previous  Next          Contents  Index  Navigation  Glossary  Library