Defining Security Views

Use the Security View Names component (SECURITY_VIEWS) to define security views.

Page Name	Definition Name	Usage
Security Views Page	SECURITY_VIEWS	For each type of security, specify the security views for your system. The Apply Security Setups process changes the prompt edit tables based on the security view names that you specify here. Update this page only if you add new security views to your system.

Note: Defining new security views is optional.

Views are SQL statements that filter out data rows whose key values are not accessible by certain users. This allows users to access data horizontally across more than one table, seeing only appropriate subsets of values (SetIDs, business units, or ledgers) from the edit tables.

Business units, SetIDs, and ledgers are maintained and accessed on pages as primary keys throughout your system. Prompt edit tables give users a list of values from which to choose, and selection is limited to values for which access has been granted. PeopleSoft row-level application security enables you to specify through the edit tables that only certain values are available in a particular view.

PeopleSoft applications are delivered with no security views on the prompt tables of the key fields in your system. You can enable certain security options or even build your own views. Once you set up views, you can specify which users or permission lists can access certain secured field values.

Security view names have one of the following three file extensions to reflect the type of security views for prompting:

Extension	Description
NONVW	Indicates that no security is chosen for the field using this view as the prompt table.
OPRVW	Indicates that user ID security is chosen for the field using this view as the prompt table.
CLSVW	Indicates that permission list security is chosen for the field using this view as the prompt table.

Use the Security Views page (SECURITY_VIEWS) to for each type of security, specify the security views for your system.

The Apply Security Setups process changes the prompt edit tables based on the security view names that you specify here. Update this page only if you add new security views to your system.

Navigation:

Set Up Financials/Supply Chain > Security > Update Security View Names

Note: There is no need to access this page unless you have customized security views.

Field or Control	Description
Search Text	Displays the view name prefixes supplied by your applications. During the Apply Security Setups process, the system searches for prompt edit tables that begin with these prefixes. If an edit table name begins with a prefix from this list, the edit table from the appropriate column is accessed, which matches the security type that you selected when you specified security options (no security, user ID security or permission list security).
Type	Select the type of field secured by each view. Values are: Book, Ledger, Pay Cycle, Prob Inst, Project, SetID, and Unit. The system stores the list in the SEC_VIEW_NAMES table, where you can review or update the information.

Field or Control

Description

Search Text

Displays the view name prefixes supplied by your applications. During the Apply Security Setups process, the system searches for prompt edit tables that begin with these prefixes. If an edit table name begins with a prefix from this list, the edit table from the appropriate column is accessed, which matches the security type that you selected when you specified security options (no security, user ID security or permission list security).

Type

Select the type of field secured by each view. Values are: Book, Ledger, Pay Cycle, Prob Inst, Project, SetID, and Unit. The system stores the list in the SEC_VIEW_NAMES table, where you can review or update the information.

Defining Security Views

Page Used to Define Security Views

Understanding Security Views

Security Views Page