13.07.2015 Views

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SCT Banner Human Resources / Release Guide / 7.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Appendix B Example - Setting Up VBS in <strong>Human</strong> <strong>Resources</strong>OverviewAppendix BExample - Setting Up VBS in <strong>Human</strong> <strong>Resources</strong>OverviewThe following example illustrates how to set up Value Based Security (VBS) usingOracle Fine-Grained Access (FGAC) for a simplistic business case within <strong>Banner</strong><strong>Human</strong> <strong>Resources</strong>. This type of security is primarily to define row level access torecords in the database and is used in conjunction with the <strong>Banner</strong> HR applicationsecurity.This example is to provide details of securing employee job records based uponPosition Class, which resides on the Position record. This example is intended todefine classifications such as Administrative users and Faculty users, so that VBS willrestrict insert, update, and delete privileges on jobs data for specific userpopulations. As a component of defining FGAC rules, the user defines the tableswhich will be analyzed when records are accessed by an end user. In this example,the employee jobs tables are targeted, including, basic (base) job information, jobdetail, labor distributions, default earnings, and work schedules.Step 1 - Define a Domain and Plan the RulesVBS rules require that a domain be defined, which provides the primary driver tableto allow Oracle to begin the data analysis. In this case, we are identifying thePosition table (NBBPOSN), so that we can determine where to find the Position ClassCode that is ultimately associated with the employee's job assignment.In this step, we are determining what we will name our domain and the driver tablewithin the application. For example, we're using a user-defined domain name, forwhich we have chosen pb_position_class_vbs, and the Position table (NBBPOSN) willbe the driver to determine the specific Position Class.We will also define the tables in which the VBS restriction will execute, besides thedomain driver table NBBPOSN. This will ensure that the user that is attempting toinsert, update, or delete an employee job assignment, has authority over the record.The join conditions that will need to be defined for these tables are input later inthe process, on the FGAC VBS Table Rules Form (GORFDPL).DomainPB_POSITION_CLASS_VBSDriverNBBPOSNTableNBBPOSNClassJanuary 2005 <strong>Human</strong> <strong>Resources</strong>/Position Control <strong>Release</strong> <strong>7.0</strong>Confidential <strong>Release</strong> <strong>Guide</strong> 341

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!