SCT Banner Human Resources/Position Control Release · PDF fileSCT Banner Human Resources/Position Control ... Browsing for Topics ... January 2005 Human Resources/Position Control

SCT Banner Human Resources/Position Control Release Guide

January 2005 Release 7.0

Confidential Business Information

This documentation is proprietary information of SunGard SCT and is not to be copied, reproduced, lent or disposed of, nor used for any purpose other than that for which it is specifically provided without the written permission of SunGard SCT.

Prepared By: SunGard SCT4 Country View RoadMalvern, Pennsylvania 19355United States of America

© SunGard 2004-2005. All rights reserved. The unauthorized possession, use, reproduction, distribution, display or disclosure of this material or the information contained herein is prohibited.

In preparing and providing this publication, SunGard SCT is not rendering legal, accounting, or other similar professional services. SunGard SCT makes no claims that an institution's use of this publication or the software for which it is provided will insure compliance with applicable federal or state laws, rules, or regulations. Each organization should seek legal, accounting and other similar professional services from competent providers of the organization's own choosing.

SunGard, the SunGard logo, SCT, the SCT logo, and Banner, Campus Pipeline, Luminis, PowerCAMPUS, SCT Matrix, SCT Plus, SCT OnSite and SCT PocketRecruiter are trademarks or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. All other trade names are trademarks or registered trademarks of their respective holders.

3

Release Guide

Human Resources/Position Control

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Section 1 New Banner Online Help . . . . . . . . . . . . . . . . . . . . . . . 17

Accessing Online Help from a Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Accessing the Help Center . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Features of Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Browsing for Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Searching for Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Using the Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Using the Field Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

How Does Online Help Affect Other Types of Help?. . . . . . . . . . . . . . . . . . 22

Section 2 New User Interface-Functional . . . . . . . . . . . . . . . . . . . 23

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Overall Changes to Form Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Tabbed Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

List of Tabbed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Forms with Other Window Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Code/Description Fields and List of Values . . . . . . . . . . . . . . . . . . . . . . . . 34

Standardization of Label Text . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Table of Contents

Human Resources/Positon Control Release 7.0 January 20054 Release Guide Confidential

Main Menu Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Main Menu Form (GUAGMNU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Enhanced User Preferences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

General User Preferences Maintenance Form (GUAUPRF) . . . . . . . . . . . . . . . . 36

Standardization of Identification Forms . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Accessibility Enhancements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Miscellaneous Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Section 3 Employee API - Functional . . . . . . . . . . . . . . . . . . . . . . 43

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Other Important API Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Section 4 Employee API - Technical . . . . . . . . . . . . . . . . . . . . . . . 47

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Employee API Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Section 5 Banner Support for Salary Planner - Functional . . . . . . . 51

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

Security Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Process Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Establishing Security for the Salary Planner . . . . . . . . . . . . . . . . . . . . . . . 54Setting Up Banner Forms for the Salary Planner . . . . . . . . . . . . . . . . . . . . . 55

New Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Budget Profile Validation Form (NTVBPRO) . . . . . . . . . . . . . . . . . . . . . . . 58Salary Planner Extract Rules Form (NTRSPEX) . . . . . . . . . . . . . . . . . . . . . . 59Salary Planner Security Form (NSASPSC). . . . . . . . . . . . . . . . . . . . . . . . . 67

Table of Contents

January 2005 Human Resources/Position Control Release 7.0Confidential Release Guide 5

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Organization Code Validation Form (PTVORGN) . . . . . . . . . . . . . . . . . . . . 71Position Control Installation Rules Form (NTRINST) . . . . . . . . . . . . . . . . . . . 75User Codes Rule Form (PTRUSER) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Position Budget Form (NBAPBUD). . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Job Change Reason Code Rule Form (PTRJCRE) . . . . . . . . . . . . . . . . . . . . . 81NOQLIBR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83NOQMENU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83

New Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Salary Planner Extract Process (NBPSPEX) 85Salary Planner Upload Process (NBPSPUP) 92

Error Resolution Matrix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Section 6 Banner Support for the Salary Planner - Technical . . . . . 109

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Changed Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

New Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

New Install Script. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

New Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Changed Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

Section 7 Support for 1099-R Changes - Functional . . . . . . . . . . . 135

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Changed Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

1099-R Form (PXA1099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

Changed Report and Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

1099-R Load Process (PXP1099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361099-R Print Report (PXR1099) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

1099-R Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

Table of Contents


Section 8 Support for 1042-S Changes - Functional . . . . . . . . . . . 141

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Changed Report and Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141

Foreign Person 1042-S Report (PXR1042) . . . . . . . . . . . . . . . . . . . . . . . . 1411042 Magnetic Tape Process (PXPMT42). . . . . . . . . . . . . . . . . . . . . . . . . 142

1042-S Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

Section 9 Support for US W-2 and MMREF-1 Processing - Functional . . . . . . . . . . . . . . . . . 153

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Changed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

United States W-2 (PXRW2US). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

Processing Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

US W-2 and MMREF-1 Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Address Hierarchy for W-2s, 1099-Rs, or 1042-Ss Available on GTVSDAX. . . . . . . . 158Adjusting Laser Print File if W-2s Need Realignment . . . . . . . . . . . . . . . . . . . 159U.S. Tax Form Vendors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

Section 10 Support for Puerto Rico W2 andMMREF-1 Processing - Functional . . . . . . . . . . . . . . . . 163

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

W-2 Puerto Rico Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

Address Hierarchy for W-2PRs Available on GTVSDAX . . . . . . . . . . . . . . . . . 166Puerto Rico Tax Form Vendor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

Section 11 Support for 1099-R Changes - Technical . . . . . . . . . . . 169

Changed Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

Table of Contents


Section 12 CA-MIS Reporting Enhancements For 2003 - Functional171

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

Earnings Code Rule Form (PTREARN) . . . . . . . . . . . . . . . . . . . . . . . . . . 172Job Location Rule Form (PTRJBLN). . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Employee Jobs Form (NBAJOBS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Employee Job Activity Form (PEAJACT) . . . . . . . . . . . . . . . . . . . . . . . . . 173Employee Assignment Extract Form (PDAASGN). . . . . . . . . . . . . . . . . . . . . 174

Changed Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

Calculate Statistics Salary Process (PEPCSAL) . . . . . . . . . . . . . . . . . . . . . . 179Employee Demographic Extract Process (PEPEDEX) . . . . . . . . . . . . . . . . . . . 182Employee Assignment Extract Process (PEPAEXT) . . . . . . . . . . . . . . . . . . . . 183

Section 13 CA-MIS Reporting Enhancements For 2003 - Technical 185

New Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

Changed Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

Section 14 OSHA Reports for 2003 - Functional . . . . . . . . . . . . . 189

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Changed Form . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

Health and Safety Incident Form (PEAHSIN) . . . . . . . . . . . . . . . . . . . . . . . 190

Changed Report. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

OSHA Form 300/300A (PEROSHA) . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

Obsolete Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

OSHA Form 101 (PERO101) and OSHA Form 200 (PERO200) . . . . . . . . . . . . . 199

Section 15 OSHA Reports for 2003 - Technical . . . . . . . . . . . . . . 201

New Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201

Table of Contents


Section 16 IPEDS Reports for 2003 - Functional . . . . . . . . . . . . . . 203

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

Changed Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

IPEDS Summary Report (PEREO61, -2) . . . . . . . . . . . . . . . . . . . . . . . . . . 206Web Upload File. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217IPEDS Detail Report (PEREO6D) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

IPEDS S1-Long Process Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

Impact of Faculty Tracking Method on IPEDS Reporting . . . . . . . . . . . . . . . . . 235Verifying IPEDS S1-Long Data on Banner HR Forms . . . . . . . . . . . . . . . . . . . 236Running IPEDS S1-Long Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Web Upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242

Section 17 IPEDS Reports for 2003 - Technical. . . . . . . . . . . . . . . 243

New Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

Section 18 VETS-100 Reporting for 2003 - Functional. . . . . . . . . . 245

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Changed Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

Identification Form (PPAIDEN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

Changed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

Veterans Employment Report (PERV100) 247

Section 19 VETS-100 Reporting for 2003 - Technical . . . . . . . . . . 251

Changed Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

Section 20 Canadian Regulatory Enhancement- Functional . . . . . . 253

Changed Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Canadian T4 Supplementary Report (PXRT4CN) . . . . . . . . . . . . . . . . . . . . . 253

Table of Contents


Section 21 Miscellaneous Enhancements - Functional. . . . . . . . . . 255

Common Matching in Human Resources . . . . . . . . . . . . . . . . . . . . . . . . 255

Access to Deferred Pay Information in the Employee Jobs Form (NBAJOBS) . . . . 256

Leave Roll Enhancement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Updateable Deferred Pay Adjustment List Form (PEADADJ) . . . . . . . . . . . . . 257

Expansion of the Discipline Code Field . . . . . . . . . . . . . . . . . . . . . . . . . 259

Reversal of Organization Transfer on the Position Budget Form (NBAPBUD) . . . 259

Labor Redistribution Form (PHAREDS) . . . . . . . . . . . . . . . . . . . . . . . . . . 261

Expansion of Benefit Plan Amount Fields For Percent Calculations . . . . . . . . . 262

Expansion of the Amount and Special Rate Fields . . . . . . . . . . . . . . . . . . . 262

NHRDIST Report Layout in E~Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Encumbrance Recasting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 264

Employee Jobs Form (NBAJOBS) Enhancements . . . . . . . . . . . . . . . . . . . . 269

New Rule Class Override in PTREARN and PHPFEXP . . . . . . . . . . . . . . . . . 270

Faculty Record Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

Enhancement to the Payroll Adjustment Form (PHAADJT) . . . . . . . . . . . . . . 275

Enhancements to the Employee Review Form (PEAREVW) . . . . . . . . . . . . . . 276

Section 22 Miscellaneous Enhancements - Technical . . . . . . . . . . 277

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Changed Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

Changed Utility Script . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

Table of Contents


New Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

Changed Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

Section 23 Problem Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . 291

Implementing Oracle Password Expiration Feature in Cobol Programs . . . . . . . 291

Human Resources Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

Validation Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Rule Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

Applicant Tracking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

Biographic & Demographic Information . . . . . . . . . . . . . . . . . . . . . . . . . 294

Benefits and Deductions Administration . . . . . . . . . . . . . . . . . . . . . . . . . 295

Employment Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 298

Position Budgeting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304

Health and Safety Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305

Time Entry and Payroll Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

Tax Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

Electronic Approvals . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 313

CA-MIS Reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 314

Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 315

Table of Contents


Section 24 Problem Resolutions- Technical . . . . . . . . . . . . . . . . . 331

Changed Scripts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 333

Changed Libraries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 334

Obsolete Objects in Human Resources Release 7.0 . . . . . . . . . . . . . . . . . . 335

Appendix A Example of Annual Salary Calculation for CA-MIS . . . 337

Appendix B Example - Setting Up VBS in Human Resources . . . . . 341

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341

Appendix C Using the Common Person API in Human Resources . 361

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Common Person API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

Table of Contents


This page intentionally left blank

Introduction


Introduction

This Release Guide documents Release 7.0 of the Banner Human Resources/Position Control Product.

Release 7.0 is a mandatory, cumulative release that includes enhancements, regulatory information, problem resolutions, and RPEs in Human Resources Releases 6.1 and 7.0, and Position Control releases 6.1 and 7.0.

The following table provides a quick reference guide to the releases included in this Release Guide, in addition to the 7.0 enhancements.

Brief descriptions of the enhancements included in this release guide are given below:

New Banner Online Help

Release 7.0 features a new online help system that contains information about forms and fields, as well as tasks you can perform with Banner. This help system runs in a web browser, and is available by choosing the Online Help button on the tool bar or the Online Help option from the Help pull-down menu. For more information refer to Section 1, “New Banner Online Help” in this release guide.

New User Interface of Banner

Release 7.0 features a new user interface that provides a new display format on forms for Banner. Refer to Section 2, “New User Interface” in this release guide for a description of the components of the Banner user interface.

Employee API

Section 3, “Employee API”, provides an overview of the Employee API, and a brief description of its usage and change in functionality in specific forms of Human Resources.

Release Contents Release Date

HR/Posn.Ctrl. 6.1 2003 Year-End US Regulatory Enhancements April 2004

CA-MIS Reporting Enhancements for 2003 April 2004

OSHA Reporting Enhancements for 2003 April 2004

IPEDS Reporting Enhancements for 2003 April 2004

VETS-100 Reporting Enhancements for 2003 April 2004

Introduction

Human Resources/Position Control Release 7.0 January 200514 Release Guide Confidential

Common Matching Enhancement in Human Resources

Refer to Section 21, “Miscellaneous Enhancements” of this release guide for a description of how the new Common Matching functionality of Banner General affects forms in Banner Human Resources.

Setting up VBS in Human Resources

Appendix B, “Setting up VBS in Human Resources”, of this release guide documents an example for setting up Value Based Security using Oracle’s Fine-Grained Access (FGAC) for forms in Banner Human Resources.

Using Common Person API in Banner Human Resources

Refer to Appendix C, “Using Common Person API in Banner Human Resources”, of this release guide for a brief description of the impact of the Common Person API on forms in Banner Human Resources.

2003 Year-End Regulatory Enhancements

The following enhancements were addressed with regard to changes in the 2003 Year-End Tax Reports:

• The Foreign Person 1042-S Form (PXR1042) and the United States W-2 Process (PXRW2US) have been modified to include the reporting of state-tax related information associated with two new Deduction Types, 21 and 22. This resolves RPE #30083.

• The Foreign Person 1042-S Report (PXR1042) has also been modified to print zero (0) in Box 7 US Federal Tax Withheld, when Federal Tax Withheld is zero dollars ($0). This resolves defect #90019.

• The 1099-R Load Process (PXP1099), the 1099-R Form (PXA1099) and the 1099-R Print Report (PXR1099) have been modified to display a new field, Payer Account Number for the payee.

CA-MIS Reporting Enhancements for 2003

Enhancements addressed include:

• Inclusion of Premium, Shift Differential and Additional earnings in the calculation of the annual salary by the Calculate Stats Salary Process (PEPCSAL).

• Eliminating the use of the Employee Job Activity Form (PEAJACT) for evaluating MIS element values by the PEPAEXT process.

• An updated Employee Assignment Extract (PEPAEXT) file layout

These enhancements also satisfy RPEs #34834 and #34836.

Introduction


OSHA Reporting Enhancements for 2003

The Occupational Safety and Health Administration (OSHA) Reports were revised for year 2003 with the following changes made in Banner:

• A new category was added to the Injury and Illness Type field on the Health and Safety Incident Form (PEAHSIN)

• The report formats of OSHA Form 300 and Form 300A have been updated to meet the requirements for 2003 tracking and 2004 reporting.

IPEDS Reporting Enhancements for 2003

To comply with the regulatory requirements, the following IPEDS reports have been modified in Banner Human Resources for the removal of the Other Administrative job category A0 (A zero):

• Formats of the Fall Staff Survey (S1-Long) Report and Web File Upload for S1-Long

• IPEDS Summary Report (PEREO61, -2)

• IPEDS Detail Report (PEREO6D)

VETS-100 Reporting Enhancements for 2003

The VETS-100 Report was revised for year 2003. The report now displays a Newly Separated Veterans column based on the Active Duty Separation Date field specified on the Identification Form (PPAIDEN) in the Human Resources System.

This release satisfies RPE# 26377 that requested the Newly Separated Veteran’s category be counted on the VETS-100 Report. In 2002 and 2003, this element was optional.

System Requirements

Install the following minimum required releases to use Payroll (Human Resources) Release 7.0:

• Minimum Required General Release: 7.0

• Minimum Required Position Control Release: 7.0 (see below)

• Minimum Required Payroll (Human Resources) Release: 6.0

Install the following minimum required releases for Position Control 7.0:

• Minimum Required General Release: 7.0

• Minimum Required Position Control Release: 6.0

Introduction



Section 1 New Banner Online HelpIntroduction


Section 1 New Banner Online Help

Release 7.0 features a new online help system that contains information about forms and fields, as well as tasks you can perform with Banner. This help system runs in a web browser, and is available by choosing the Online Help button on the toolbar or the Online Help option from the Help pull-down menu. Additionally, you can access online help by selecting the Help Center link on the main menu.

Online help will be updated to coincide with deliveries of the Banner Bookshelf (approximately twice a year). Information about installing and configuring online help is contained in the Oracle Developer for SCT Banner Implementation Guide.

Note: The Online Help button, Help Center link, and Online Help option from the Help pull-down menu are active upon installation of the 7.0 release, but do not lead to any online help content. Online help content will be available for download in Spring 2005 via the ActionWeb. In the meantime, your site administrator can download and install a placeholder online help system according to the instructions in the Banner General 7.0 Release Guide.

The new help system is not currently designed to be customized. Any changes made to help files will be overwritten by subsequent deliveries of online help. SunGard SCT recommends maintaining customized information in Local Dynamic Help within Banner.

Tip: For forms with no help, the Banner online help error page may not appear for Internet Explorer users who use IE’s “friendly” error messages by default. For optimal performance in IE, clear the Show friendly HTTP error messages check box that is located on the Advanced tab of your Internet Options.

Section 1 New Banner Online Help Accessing Online Help from a Form


Accessing Online Help from a Form

The Online Help button and Help menu option initially display information about the form on which you are working:

Accessing the Help Center

If you want information about forms and tasks for another Banner product, use the Help Center link, which is available from the main menu of Banner, or from anywhere within the help system.

From the Main Menu

From Within the Help System

Section 1 New Banner Online HelpFeatures of Online Help


The SCT Banner Help Center Page

From either the main menu or within the help system, the Help Center appears:

Note: Only products that are licensed at your site appear on the Help Center page.

Features of Online Help

You can browse, search, and use the index to locate topics in online help.

Browsing for Topics

The Contents tab and the bread crumb trail both enable you to browse for topics categorically. Form and field information is organized by Banner module. Task information is contained under the Procedures heading.

Section 1 New Banner Online Help Features of Online Help


Browsing with the Contents tab

Searching for Topics

The Search tab allows you to search for topics within the help system. You can also use your browser’s “search on page” feature to find specific text on a help page.

Searching with the Search tab

Section 1 New Banner Online HelpFeatures of Online Help


Using the Index

The Index tab provides an alphabetical listing of topics within the help system. When you enter the letters of a term, the index will scroll through the topics to the closest alphabetical match.

Searching with the Index tab

Using the Field Link

Many form descriptions are quite long, so sometimes you will find a link that goes to field descriptions on a separate page.

Section 1 New Banner Online Help How Does Online Help Affect Other Types of Help?


How Does Online Help Affect Other Types of Help?

The new online help replaces the WinHelp online help introduced in Release 4.0. All content from WinHelp has been incorporated in the new online help.

No changes are planned for the Banner Bookshelf as a result of the new online help. The PDF files that comprise the Bookshelf are the most efficient way to print Banner documentation for reference.

For 7.0, SCT-delivered Dynamic Help will not change, but eventually, SunGard SCT plans to phase it out. Local Dynamic Help and Item Properties (choices available from the Help pull-down menu in Banner) both display column information when it is available. There are no plans to phase out Local Dynamic Help.

Section 2 New User Interface-FunctionalOverview


Section 2 New User Interface-Functional

Overview

Release 7.0 features a new user interface for Banner. Components of the interface are described in this section.

Note: Information about how SunGard SCT implemented the 7.0 user interface changes is contained in the 7.0 UI Methodology Handbook.

Overall Changes to Form Layout

Many changes have been made to improve the usability of Banner forms. Improved alignment of screen elements, including the key block, Description fields, and field labels, enhances overall readability. More code is visible for all Code, ID, andSSN/SIN/TIN fields as a result of field expansion, and all elements are grouped logically on the form. Block headings are labeled consistently. Labels, check boxes, and radio buttons are now easier to read and select. Called forms have been positioned to display more of the calling form, when appropriate.

Buttons were enhanced as well. At the top of a column for fields that have both a label and a button, the label now always appears on top of the button. Additionally, buttons have “tool tips” that pop up when the mouse is on top of them.

Navigation between forms was also improved. When in the Go To field on the General Menu (GUAGMNU), the Up and Down arrow keys enable you to navigate to recently-accessed forms. Choose the Display Navigation Window key (F5) from any form to quickly navigate to any other form.

Note: The Display Navigation Window key does not work in query mode.

Section 2 New User Interface-Functional Tabbed Interface


Other changes to overall form layout are described below.

• Improved screen resolution-- 1025x768 screen resolution allows ample room for displaying user interface components. This enhancement eliminated many scrolling or stacked canvases.

• Consistency with Luminis--The new Banner user interface displays the colors and style of the Luminis UI.

• Consistent confidential and deceased messages—For most Banner products, these messages always appear on the top left of the first line of the form.

Note: Banner Advancement displays deceased spouse messages on the right side of the form. Banner Human Resources does not display messages on the top left of the form.

Tabbed Interface

Selected forms now have a tabbed interface rather than the traditional Banner window appearance. Tabs are used to arrange information in a meaningful way, and allow you to navigate easily between groups or blocks of information. You can click on the tab, use the Ctrl and Tab keys, or use the Next Block and Previous Block functions. Tab titles reflect the contents of a particular window or grouping of information.

For tabbed forms that contain windows of parent/child information, the Main tab appears in the top row. The dependent information appears on tabs lower on the window and below the top-level tab to which the information is related.

Use any of the following to navigate within tabbed forms:

• Control-Tab moves forward and Control-Shift-Tab moves backward through the tabs on a form.

• Control-Page Up moves forward and Control-Page Down moves backward through the tabs.

• The List Tab Pages key (F2) displays a list of other tabbed windows on the form. Use the mouse or the Up and Down arrow keys to select a different tab. For forms that have tabs within a tabbed window, navigation is based on the location of the cursor when List Tab Pages is selected.

Note: Some forms have only one tab because they call a window which is now a part of GOQCLIB. For information about these changes, refer to the “Standardization of Identification Forms” section of this document.

Section 2 New User Interface-FunctionalTabbed Interface


List of Tabbed Forms

The following Human Resources and Position Control forms have been changed in conformance to the new UI standards of the Banner 7.0 Release. A brief description of the changes in each form is provided below.

Form Tabs Other Window Changes

Identification Form (PPAIDEN)

The Identification form consists of the following tabs:

• Current Identification

• Alternate Identification

• Address

• Biographical

• Emergency Contact

• The Legal Name window and the ID/Name Maintenance Information window have been eliminated with the 7.0 version. This information is now included in the Current Identification window.

• The Delivery Information window has been removed and the fields in this window have been relocated to the Address Information window.



General Information Form (PPAGENL)

The General Information Form (PPAGENL) consists of the following tabs:

• General Education

• Examinations

• Publications

• Driver’s License

• Honors and Awards and

• Transcript

In the General Education window, the blocks have been renamed more accurately to represent the details:

• Institution

• Diploma or Degree

• Area of Concentration

Employee Form (PEAEMPL)

The Employee Form (PEAEMPL) now consists of three tabs:

• General Employee

• United States Regulatory

• Canadian Regulatory

The Hiring Location window, Leave of Absence window and the Termination window have been eliminated from PEAEMPL and the fields have been relocated to the General Employee window for easier accessibility.

The Regulatory window has been renamed as the United States Regulatory and the Other Regulatory window has been renamed as Canadian Regulatory.

Employee Relations Grievance Form (PEAGREV)

The tabs of the Employee Relations Grievance Form (PEAGREV) are as follows:

• General

• Participants

• Resulting Actions

• Resolution

None




Health and Safety Incident Form (PEAHSIN)

The windows of the Health and Safety Incident Form (PEAHSIN) can now be accessed via the following tabs:

• Incident

• Involved Persons or Parties

• Resolution and Follow Up

The scrolling canvas on the Involved Persons or Parties window has been modified to view more fields. The Cost Per Involved Party window has been eliminated and the fields have been added to the Involved Persons or Parties window.

Similarly, the Comments window has been eliminated and the fields are now included in the Incident window of the form.

Employee Benefit or Deduction Form (PDADEDN)

The tabs on the Employee Benefit or Deduction Form (PDADEDN) are as follows:

• Deduction

• Add or Replace and Arrears

• Excluded Payroll ID and

• Premium History

The One-Time Add/Replace Information window has been eliminated and the relevant fields are now included in the Add or Replace block of PDADEDN. Access this block by selecting the Add or Replace and Arrears tab.

Similarly, the Arrear Information window has been removed and the relevant fields have been relocated to the Arrears block of PDADEDN. Access the Arrears block by selecting the Add or Replace and Arrears tab.

Adjustment Processing Form (PHAADJT)

The tabs on the Adjustment Processing Form (PHAADJT) are as follows:

• Adjustment Detail

• Job Information

• Document Information and

• Comments

On the Document Information window, more fields are now available for view within the scrolling canvas, and the scrolling canvas was itself modified to allow you to view more fields. Additionally, the scrolling canvas has been removed from the Job Information window, allowing all fields to be seen in the window.




Applicant Information Form (PAAAPPL)

The tabs on the Applicant Information Form (PAAAPPL) are as follows:

• Applicant Information (default)

• Status Log and

• Interview Log

None

Applicant Entry by Requisition/Position Form (PAAAPOS)

The tabs on the Applicant Entry by Requisition/Position Form (PAAAPOS) are as follows:

• Applicant Information (default)

• Status Log

• Interview Log

None

Telephone Form (PPATELE)

The Telephone Form (PPATELE) consists of a single tab, the Telephone tab.

Since this information is now called from a General library, it assumes a tab structure.

None

Employee Jobs Form (NBAJOBS)

The tabs on the Employee Jobs Form (NBAJOBS) are as follows:

• General Job (default)

• Job Detail

• Payroll Default

• Deferred Pay

• Miscellaneous

• Excluded Deductions/Benefits

• Default Earnings

• Work Schedules

• Job Labor Distribution

The scrolling canvases on the Default Earnings window and the Job Labor Distribution have been removed allowing all fields to be seen in those windows.




Position Budget form (NBAPBUD)

The tabs on the Position Budget form (NBAPBUD) are as follows:

• Position Budget (Default)

• Salary Budgets

• Fringe Benefit

• Premium Earnings Totals

• Labor Distributions and

• Comments

The scrolling canvas in the Labor Distributions window has been removed, allowing all fields to be seen within this window.

Electronic Personnel Action Form (NOAEPAF)

The tabs of the Electronic Personnel Action Form (NOAEPAF) are as follows:

• Transaction (Default)

• Job Labor Distribution

• Default Earnings

• Routing

• Comments and Other Information

Additional rows have been added to the Transaction window and the Routing window.

The scrolling canvas has been removed from the Job Labor Distribution window, allowing all fields to be seen in this window.

The Comments and Other PAF Information windows have been combined into one window, the Comments and Other Information window.

Electronic Approval Summary Form (NOAAPSM)

The tabs on the Electronic Approval Summary Form (NOAAPSM) are as follows:

• Transaction Information and

• Transaction Comments

The scrolling canvas on the Transaction window has been modified to allow you to view more fields.


Section 2 New User Interface-Functional Forms with Other Window Changes


Forms with Other Window Changes

The following Human Resources/Position Control forms have been modified with other window changes:

Form Other Window Changes

Employee Search Form (POIIDEN)

The horizontal scroll bar in the Main window has been eliminated. All fields that were contained in the horizontal scroll bar area are now displayed in the Main window.

One-Time Payment Form (PEA1PAY)

• The blocks in the Main window have been renamed as:

• Biographic and Demographic

• Address and Telephone

• The Job Information block in the Job Information window has been renamed as the Jobs block.

Certification Information Form (PPACERT)

In the Main window, the following three fields have been relocated to outside of the horizontal scroll area:

• Certification Date

• Next Certification Date

• Expire Date

One-Time Payment Inquiry Form (PEI1PAY)

In the Main window, the following fields have been relocated to outside of the horizontal scroll area:

• Birth Month and Day

• Payroll Date

• Citizenship

Employee Accommodation Tracking Form (PEAEACC)

The two blocks in the Main window have been renamed as:

• Jobs

The Begin Date, End Date, Effective Date and Job Status fields have been relocated outside of the horizontal scroll area.

• Accommodation

In this block, the Request Status, Medical Condition and Verified? fields have been moved outside of the horizontal scroll area.

Section 2 New User Interface-FunctionalForms with Other Window Changes


EEO-1 Report Totals Form (PEAEEO1)

The horizontal scroll area has been eliminated. All fields within the horizontal scroll are now displayed in the Main block.

Employee Job Activity Form (PEAJACT)


Employee Review Form (PEAREVW)


Employee Termination Verification Process Form (PEATMVF)


Employee Position Class Seniority Form (PEIPCSN)


Faculty Action Tracking Form (PEAFACT)

The blocks within the Appt/Tenure Records Action window have been renamed as:

• Appointment

• Tenure

The blocks within the Rank Action window have been renamed as:

• Rank

• Decision

All fields in the Faculty Leaves Action window of PEAFACT are now grouped under the Leave Data block.

Faculty Action Inquiry Form (PEIFACT)

The blocks in the Main window have been renamed as:

• Appointment and Tenure

• Faculty Leave and

• Rank


Section 2 New User Interface-Functional Forms with Other Window Changes


Job Changes Detail Display Form (PEAJCDD)

The blocks in the Main window have been renamed as:

• Job

• Compensation

The horizontal scroll area in the Compensation block has been eliminated and all fields now reside within the block.

Employee History Form (PEIEHIS)

Two fields, Status and Home Organization, have been relocated outside of the horizontal scroll area.

Employee Year-to-Date Totals Form (PEIETOT)

The Main window has been organized into the following blocks:

• Quarterly Totals

• Yearly Totals

Job Year-To-Date Totals Form (PEIJTOT)

The Yearly Totals block and the Quarterly Totals block have been relocated on the Main window of the form.

Employee Seniority Adjustment History Form (PEISAHS)

The Adjustment Reason field has been relocated outside of the horizontal scroll area.

Employee/Job Labor Relations Form (PEABARG)

The horizontal scroll areas have been removed from the Main window.

Bargaining Unit Form (POABARG)

The Contract Text Available check box has been removed from the Contracts and Agreement Detail window.

Constituent Pledge Payroll Deduction Form (PEAFDED)

The blocks on the Main window of the form have been renamed as:

• Pledge and

• Deduction


Section 2 New User Interface-FunctionalForms with Other Window Changes


Employee FMLA Information Form (PEAFMLA)

The Other FMLA Leave Information window has been removed with this release, and the relevant fields have been relocated to the Main window of the form.

COBRA Person Form (PCAPERS)

The Coverage Notification window has been eliminated with this release. The relevant fields have been moved to the Main window of the form.

Record of Employment Generation Form (Pre-1997) (PEAROEC)

The Employment History window has been removed, and the relevant fields have been relocated to the Main window of the form.

Additionally, fields from the following windows have been consolidated and relocated to the new Holiday Pay, Other Monies and Comment window of PEAROEC. The following windows have been removed:

• Other Monies window

• Holiday Pay window and

• Comment window

Position Requisition (PAAREQU)

The Approver Information window and the Recruiter Information window have been removed. The relevant fields have been relocated to the Main window of the form.

Address List Inquiry Form (PPIADDR)

The Telephone Information window and the Delivery Information window have been removed and the relevant fields are now available in the Main window of the form.

Benefit or Deductions Grouping Rules Form (PTRBDPG)

The Secondary Group Associated Benefits Deductions Setup window has been removed. The fields of this window have been moved to the Main window of PTRBDPG.

Position Class History Form (NBICLSH)

Three fields, Accrue Seniority, Exempt and Employee Class have been relocated outside of the horizontal scroll bar.

Employee Job Inquiry Form (NBIJLST)



Section 2 New User Interface-Functional Options


Options

The available options can now be accessed by right-clicking on a form from anywhere on the blank canvas (not from a field).This list contains Rollback, Save, Exit, Print, and Add to Personal Menu as well as any form-specific options.

Tip: In order to see the form on the personal menu which has been added through the options window, you must first refresh the menu by either clicking the Menu link on GUAGMNU or entering refresh in the Go To field.

If the Search button opens an Option List window, you are now able to tab among the choices and use the Enter key or space bar to make your selection.

Code/Description Fields and List of Values

When you double-click in a Code/Description field, the list of values (LOV) for that field will open. When you double-click on a field other than Code/Description that has a LOV, the LOV will not open.

Note: This functionality existed in Banner 6.x, but the non-Code/Description fields had a Search button then, rather than the 7.0 icon. The fields looked different in version 6.x, but the double-click functionality was the same.

Tip: Changing the color of Code/Description fields with User Preferences can help you visually identify fields in which double-clicking will invoke an LOV.

Standardization of Label Text

Increased screen size allows for clearer labels. As a result, many field labels are now spelled out. When abbreviations are necessary, they have been standardized across Banner. Conversely, redundant labels have been eliminated.

Section 2 New User Interface-FunctionalMain Menu Changes


Main Menu Changes

Many changes have been made to the main menu, including toolbar changes, improved navigation with the Go To feature, and options to create links to favorite URLs or forms using My Links.

Main Menu Form (GUAGMNU)

Toolbar Changes

The entire toolbar is now accessible from the main menu.

Menu Navigation

The Go field is now the Go To field.

Note: In order for Banner to log security violations more effectively, you can no longer search for an object using the code/description search from this field. You can still search by using the List of Values button, and then performing your search on GUIOBJS.

You can now launch a QuickFlow directly from the Go To field, rather than first being directed to the Quick Flow Form (GUAQFLW).

The Products field is now a pull-down menu that expands the menu for the selected product. The Menu and Site Map buttons are now links.

The Help Center link accesses the SCT Banner Help Center. Refer to New Banner Online Help for information about the new help system.

My Links

The Change Banner Password link goes to the Oracle Password Change Form (GUAPSWD), where you can change your password.

The Check Banner Message link takes you to the Banner Message Form (GUAMESG), where you can view your messages. A green check mark appears next to the link when you initially log in and have pending messages, or whenever a new message arrives. The pop-up alert for new messages is no longer displayed.

Personal links enable you to create up to six links to favorite URLs or often-used Banner objects. Refer to the “Enhanced User Preferences” section of this document for information about creating personal links.

Section 2 New User Interface-Functional Enhanced User Preferences


The My Institution section is designed to reflect your institution’s web site and picture. Your DBA or site administrator can log in as the baseline user and set up the default web site link on GUAUPRF. Any user can change his/her link by accessing GUAUPRF and changing the value in the User Value field for the My Institution record.

Note: The default image can be changed by replacing the appropriate image in the banicons.jar file delivered with Banner. The image must be 163 x 141 pixels, or Banner will distort it to fit.

Broadcast Messages

The Broadcast Message button on the toolbar becomes enabled whenever you receive a broadcast message. You can view your message(s) in the Broadcast Messages section at the bottom of the screen.

Users with a security class of Broadcast can send broadcast messages to all users. To send a broadcast message, create it on GUAMESG as usual, and choose BASELINE as the recipient.

Enhanced User Preferences

Although Banner now features the colors and style of Luminis, you have the option of customizing the colors via the General User Preferences Maintenance Form (GUAUPRF). Custom colors can be specified at the site level, by logging in as the baseline user and changing the values in the Default Value fields, and also at the individual user level, by changing the values in the User Value fields.

Note: Most of the changes you make on this form appear immediately on all Banner forms; however, the General Menu Form (GUAGMNU) will not display changed title bar preferences for form name, release number, or database instance until you log out and log back in.

General User Preferences Maintenance Form (GUAUPRF)

Many changes have been made to this form for Release 7.0. Baseline users now have the option to cancel out of a change prior to saving it. Additionally, all changes made while logged in as the baseline user are saved in the GURTPRF table. Lastly, new users who are added to the database initially have the same user preferences as the baseline ID.

Note: Existing users’ records will no longer be removed from the GURTPRF table when the baseline user’s preferences are updated.

Section 2 New User Interface-FunctionalEnhanced User Preferences


Display Options Tab

The Form Name Display Option pull-down list has been changed to the Display Form Name on Menu check box.

Options related to the client/server environment have been removed:

• Display Bubble Help-- Bubble Help has been replaced with tool tips, which always display.

• Display Vertical Toolbar--Resized canvas has eliminated the need for this option.

• Display Horizontal Toolbar--Resized canvas has eliminated the need for this option.

New Alert Options enable you to customize how you are prompted by Banner for the following:

• Prompt Before Exiting Banner--Check this box if you want Banner to verify that you want to quit the Banner session before exiting.

• Display Additional Confidential Alert--Check this box if you want Banner to display an extra Confidential message for records that contain confidential information.

• Display Additional Deceased Alert--Check this box if you want Banner to display an extra Deceased message for records associated with a deceased person.

You can use the User Interface Color Settings to customize the color of the following items:

• Buttons, such as Cancel and OK (buttons in the toolbar are not included).

• Canvas of all forms

• Record highlighting

• Scroll and separator bars

• Code/Description prompts

• Canvases within the main menu, including the broadcast message, menu, and menu tree canvases

To change the color of an item at the user level:

1. Go to User Interface Color Settings on the Display Options tab.

2. In the User Value field for the item you want to change, choose a color.

Note: You can select a pre-defined color from the palette, or create your own shade by using HSB (Hue Saturation Brightness) or RGB (Red Green Blue) values.

3. Select OK.

4. Save.

Section 2 New User Interface-Functional Enhanced User Preferences


Note: SunGard SCT delivers the default values as seed data. If you change the default colors as the baseline user, all users who have not set colors at the individual user level will see the baseline colors you selected.

Directory Options Tab

The option for specifying the location of a client/server path to write the data extract file has been removed.

A directory option for specifying the location of your Banner ID images has been added. These are the images that appear on the Personal Image Form (GUAIMGE) for an ID when you select Help>>Display ID Image.

To specify a location:

1. Access GUAUPRF as the baseline user.

2. Select the Directory Options tab.

3. Find the Enter the location of your Banner ID images record.

4. Enter the location of your image directory in the User Value field.

5. Save your changes.

Creating a personal link

You can create a link from the main menu to a web site or Banner object using Personal Links. Make sure you do not have pop-ups blocked with any third-party software. Pop-up blockers can interfere with the performance of your personal links.

To create a link:

1. Go to the General User Preferences Maintenance Form (GUAUPRF).

2. Choose the My Links tab.

3. Enter a description of your link in the User Value field associated with the first personal link description.

4. Enter the URL or Banner object name in the User Value field associated with the first personal link URL or Banner object.

5. Save. You must exit Banner and log back in to see your changes.

Note: You can create up to six personal links. Each personal link is comprised of two records—the description and the URL/object. Make sure the description record matches the corresponding URL or Banner object record. The following example illustrates a personal link for a weather web site.

Section 2 New User Interface-FunctionalStandardization of Identification Forms


Standardization of Identification Forms

The new General Common Library (GOQCLIB) allows all identification forms in Banner to share the same code and basic layout, which includes a tabbed interface (refer to the “Tabbed Interface” section for details). The identification form for Human Resources is Identification Form (PPAIDEN).

The following windows are a part of GOQCLIB. Any changes you make to the windows included in this library will appear in all forms that use them.

• Current ID

Note: A name change on the Current ID window will not display in the key block until the user returns to the key block, or accesses another window within the form.

• Alternate ID

• Address

• Telephone

• Biographical

• E-mail


In Human Resources, the Telephone Form (PPATELE) uses these windows. Your insitution may use these windows on custom forms as well.

Note: If a form calls only one of the windows, then it may have only one tab.

Field Name Name of Your Link URL or Banner object

Description Enter the description for the “My Personal Link 1” link.

Enter the URL or Banner object for the “My Personal Link 1” link.

Default Value Your first personal link description

Your first personal link URL or Banner object

User Value My weather page www.weather.com

Section 2 New User Interface-Functional Accessibility Enhancements


Accessibility Enhancements

Several enhancements were made to improve the accessibility of Banner forms:

• When using keystrokes to access an Option list that is called from a button, you can now use Tab and Shift-Tab to navigate through the options. Use the Enter key to select the option.

• Whenever possible, the word "Information" has been removed from block headings.

Miscellaneous Enhancements

Toolbar Buttons

New buttons have been added to the toolbar:

• The Broadcast Message button becomes enabled when new system-wide message(s) are available.

• The Fine-Grained Access Control Security button becomes enabled if there are any FGAC rules active for the user in the database.

The Graph Information and Show Keys buttons have been removed from the toolbar.

Banner Bookshelf Button Removed

The Banner Bookshelf button has been removed from the toolbar. Enhancements to

the Adobe Reader® search feature only work when files are launched within the Reader application, and not when Reader is launched within a browser window. Maximum performance of search and index features is achieved by setting up a shortcut on your desktop to where the Bookshelf file is located at your institution.

To create a shortcut to the Banner Bookshelf on your desktop:

1. Open Windows Explorer.

2. Browse to the location where the Bookshelf directory is stored at your institution (bdoc5x, bdoc6x, or bdoc7x, depending upon the version of Banner you are using).

Section 2 New User Interface-FunctionalMiscellaneous Enhancements


3. Right click bkshlfXx.pdf and choose Create Shortcut.

4. Drag the shortcut to your desktop.

5. (Optional) Rename it.

Change to Keystroke Behavior of Pull-Down Item Lists

To expand a pull-down menu so that it displays all available list items at once, use the Alt and Down arrow keys simultaneously. Once the list is expanded, you can scroll through the list using the Up and Down arrow keys (in previous versions of Oracle Forms, the Down arrow key expanded the list).

Tip: You can use the arrow keys to scroll through the items one at a time regardless of whether the list is expanded.

Color of Disabled Text

As delivered, disabled text is black (the same as regular text), but you can change it to any color you'd like. For more information, please refer to the Oracle Developer for SCT Banner Implementation Guide.

Section 2 New User Interface-Functional Miscellaneous Enhancements



Section 3 Employee API - FunctionalOverview


Section 3 Employee API - Functional

Overview

This section provides an overview for the Employee API. This API is a database package that contains the business logic (validation rules and other related processing) surrounding the table associated with Employee data. The Employee API can be called by programs within Banner (like Forms, C processes, Web packages, etc.) as well as by external systems when there is a need to insert/update/delete information into the Employee table (PEBEMPL). The API provides for consistent processing and utilizes the same business logic whether a program in Banner calls it or an external system calls it. The table that contains Employee information is PEBEMPL.

The primary form associated with the Employee table is the Employee Form (PEAEMPL). This form retains a number of immediate edits over the data, such as the validations of Employee Class, against the Benefit Category and Leave Category codes. When inconsistent data is detected, the error messages will continue to be displayed at the bottom of the window on the Auto-help line. However, when you save the data and one or more error conditions continue to exist, a new window will open, detailing all error messages. Otherwise, you will not notice any other functional differences from prior versions of Banner Human Resources.

Other Human Resources forms and processes affect data associated with the employee table, and these have been modified to process through the Employee API. These include:

• New Hire Form (PEAHIRE) - This form creates Employee table data and validates using the Employee API;

• One-time Payment Form (PEA1PAY) - This form processes quick payments for employees and also impacts the Employee table (PEBEMPL);

• Employee Status Change Form (PEAESCH) - This form updates the Employee table with Leave or Termination data;

• Termination Verification Form (PEATMVF) - This form is designed to review employee records where there has been a Termination Date and Termination Reason established on PEAEMPL, but the Employee Status has not been set to 'Terminated'.

• Pay Period Update Process (PHPUPDT) - This process is the final payroll program that may affect employee records where the Employee Status is changed because Leave or Termination Dates have been future effective-dated consistent with the payroll.

Section 3 Employee API - Functional Other Important API Notes


• Electronic Approvals, EPAF package (NOKPLIB) - Since employee records can be created or updated through the use of EPAF, this package was modified to call the Employee API.

Please refer to the API Reference Guide for documentation related to all edits associated with the Employee API.

Other Important API Notes

Employee History Table Enhancement

The Employee History table (PEREHIS) has been expanded to include all data items associated with the Employee table (PEBEMPL). Therefore, any insert or change to any existing field on the Employee Form (PEAEMPL) will result in an audit record being posted to the Employee History table, on a going-forward basis. No changes were made to the Employee History Form (PEIEHIS) to display these new items. However, the audited elements are present on the table.

Payroll Processing Notes

An Employee table update function in the Pay Period Update Process (PHPUPDT) was modified to also utilize the Employee API. This API is called when the process determines that the Employee Status should be updated to reflect that the employee on Leave or Terminated. Through this evaluation, the Start and End Dates are evaluated against the job record in order to determine whether this update should occur.

For example, on December 1st, you indicate that the job is to go on Leave on December 31st and re-activates the job on March 1st. Next, in order to indicate the Leave information on the Employee record you enter that the Leave Start Date is January 1st and the Expected Return Date is February 28th. During the month-end payroll, since all records are in sync, the Pay Period Update Process (PHPUPDT) changes the Employee Status to 'Leave'.

There is a situation within Leave and Termination processing where the Pay Period Update Process (PHPUPDT) may error, the employee will not be updated and the process will stop. This will affect the finalization of the payroll. This situation involves records where you have further modified the job status and dates without reviewing the Employee record controls. Following the above example, if the job record has been reactivated on January 15th and is extracted and attempted to be paid, the Pay Period Update Process (PHPUPDT) will error out because the employee Leave dates are inconsistent with the job dates.

Section 3 Employee API - FunctionalOther Important API Notes


In order to ensure that the Pay Period Update Process (PHPUPDT) does not error and terminate, an edit has been placed in the Pay Period Proof Process (PHPPROF). If the job dates and status are not consistent with the employee record criteria, either on the Leave or Termination windows, the employee will receive an error in the payroll and the disposition will be set to '05'. The employee must be deleted in the payroll, their records must be corrected on the Employee Form (PEAEMPL), and they must be re-extracted through the Time Processing Report (PHPTIME) to be paid.

Security

It is important to note that Oracle and Banner HR security will continue to execute when data is processed through the API against the employee table, whether the processing source is within Banner or external to it.

Section 3 Employee API - Functional Other Important API Notes



Section 4 Employee API - TechnicalOverview


Section 4 Employee API - Technical

Overview

An SCT Banner API is essentially a database package that encapsulates the business logic surrounding an SCT Banner business entity.

An SCT Banner business entity is the fundamental unit of information that an SCT Banner application can modify. For example, a course, address, e-mail, and telephone number.

APIs leverage SCT Banner messaging support so that SCT Banner becomes "messaging enabled", i.e., be able to stimulate the production of messages based on changes to data they own.

Programs within SCT Banner as well as external systems can then manipulate a business entity or table by calling APIs.

The foundation of all SCT Banner APIs is the ability to perform CRUD (create, retrieve, update, and delete) actions on the database.

The APIs will contain the same validation logic and edits that are executed when performing these actions (CRUD) from an SCT Banner Internet-native form, self-service page, or batch process.

For example, calling the API for the "employee" business entity allows you to:

• Create employee information (insert rows into the Employee table).

• Retrieve data from the Employee table.

• Update employee information (modify rows in the Employee table).

• Delete employee information (physically remove data from the Employee table).

The advantage of using APIs include:

• APIs expose business objects that are useful to users of other applications comprising an institution's digital campus.

• APIs are bi-directional. That is, they support read and write functions.

• APIs ensure consistent edit and validation business logic (create, retrieve, update, and delete).

• APIs eliminate duplicate code that would need to be maintained in each application.

Section 4 Employee API - Technical Employee API Packages


Employee API Packages

The PB_EMPLOYEE package provides the Common Business interface for the EMPLOYEE. The Employee API establishes information about an employee's terms of employment.

Other Associated Packages:

• pb_employee_rules

This package provides messaging support and field validation for the Employee API.

• pb_employee_strings

This package contains the error messages and error message functions for the Employee API.

The following table provides a brief overview of the Employee API. For more details, refer to the HR API Reference Guide, Release 7.0.

API Object Name API Entity Name

Associated Files Associated Table

Affected Forms and Processes

PB_EMPLOYEE EMPLOYEE pokb_employee0.sqlpokb_employee1.sqlpokb_employee_r0.sqlpokb_employee_r1.sqpokb_employee_s0.sqlpokb_employee_s1.sql

PEBEMPL PEAEMPL

PEAESCH

PEAHIRE

PEA1PAY

PHPUPDT

NOKPLIB

Section 4 Employee API - TechnicalNew Scripts


New Scripts

PEBEMP10.SQL

This script adds columns PEBEMPL_USER_ID and PEBEMPL_DATA_ORIGIN.

PEBEMP11.SQL

This script adds comments for the PEBEMPL_USER_ID and PEBEMPL_DATA_ORIGIN columns.

PEBEMP12.SQL

This script updates null in the PEBEMPL_IPEDS_SOFT_MONEY_IND column with 'N'.

PEBEMP13.SQL

This script alters the PEBEMPL_IPEDS_SOFT_MONEY_IND column to NOT NULL.

PEBEMP14.SQL

This script rebuilds comments to match Employee API descriptions.

Section 4 Employee API - Technical New Scripts



Section 5 Banner Support for Salary Planner - FunctionalOverview


Section 5 Banner Support for Salary Planner - Functional

Overview

A new module, the Salary Planner, has been added to the Employee Self-Service product with Release 6.1 of Employee Self-Service. The Salary Planner is a Web application that enables you to define, edit and update position budgets and job salaries for select populations in accordance with the requirements of your enterprise.

To provide support for the Salary Planner, Banner Human Resources has been modified in the following aspects:

• Security for the Salary Planner

The Salary Planner can only be used in conjunction with Banner Human Resources. Accordingly, security for the Salary Planner will be established in the Banner Human Resources product installed at your enterprise.

As access to budget information is usually confined to a finite set of employees, security for the Salary Planner is defined at various levels; namely, at the Organization level, Employee Class level, Employer level and at the Salary Level. Consequently, this has resulted in modifications to the User Codes Rule Form (PTRUSER).

• Access and display of information in the Salary Planner

In addition to limiting access to budget information via security, a new Position Control form, the Salary Planner Security Form (NSASPSC) has been added that allows you to control the extent of information that can be updated by users of the Salary Planner.

This form allows you to set up organization security for a user by excluding or including access to a specific organization in the Salary Planner. The NSASPSC form only controls access within the Salary Planner and does not affect security within the Banner Human Resources module.

The NSASPSC form also allows you to copy the organization security of one user to another. For more details refer to the section New Forms on page 58.

Additionally, the Position Control Installation Rules Form (NTRINST) has been enhanced to provide viewing, calculation and approval level rules for the Salary Planner.

Section 5 Banner Support for Salary Planner - Functional Security Considerations


• Additional classification of Position Budgets

This has resulted in the creation of a new Budget Profile Validation Form (NTVBPRO). This form allows you to create budget profile codes which are associated with each budget. The budget profile codes are used in conjunction with Budget Extract IDs when data is extracted from Banner into Salary Planner. For more details, refer to the corresponding form in the section New Forms on page 58.

• Data extraction from Banner into the Salary Planner

To enable the transfer of position, budget and job information from Banner into the Salary Planner, a new rule form and a new process have been created in Banner Human Resources.

The Salary Planner Extract Process (NBPSPEX) downloads data from Banner into the Salary Planner based on certain criteria or rules established to identify the extract population in the new rule form, Salary Planner Extract Rules Form (NTRSPEX).

• Data upload from the Salary Planner to Banner

Similarly, to enable the transfer of updated position, budget, and job information from the Salary Planner into Banner, a new upload process - The Salary Planner Upload Process (NBPSPUP) has been created.

Security Considerations

Security access has been developed specifically for the Salary Planner product. This functionality will not affect any other security access within Banner HR, Employee Self Service, or Banner Finance.

All Oracle forms associated with this modification invoke the standard SCT Banner object level security, and SCT Banner Human Resource application level security is used.

Note: Timesheet Organization Security will not be utilized in the Salary Planner application of Employee Self-Service.

A new security model based on the Position Budget Organization Code on NBAPBUD has been developed for this modification and applies to all Web pages of the Salary Planner enhancement. SCT Banner Human Resource application level security will also be used for Employee Class, Salary Level and Employer Security. Salary Level security will be used when accessing job related data.

Web Tailor roles are used to determine Web page access within the Employee Self-Service - Salary Planner application. SCT Banner Human Resource application level security is used to determine data access within the Web pages.

Section 5 Banner Support for Salary Planner - FunctionalProcess Flows


Process Flows

The following process flows describe the workflow between Banner and Salary Planner. For further details, refer to the Employee Self-Service Release Guide, Release 6.1.

The following graphic presents a high-level process flow which outlines the key points at which Banner integrates with the Salary Planner in Employee Self-Service.

Set up security for theSalary Planner

and each of its users in Banner

Set up rules to extractdata from Banner

into the Salary Plannerwith NTRSPEX

Run the NBPSPEX processto extract data from

Banner into the Salary Planner

Modify the downloadeddata in the

Salary Planner

Run the NBPSPUP process toupload modified data from

the Salary Planner into Banner

Section 5 Banner Support for Salary Planner - Functional Process Flows


Establishing Security for the Salary Planner

The extent of access to budget information displayed for each user of the Salary Planner is determined by the security established in Banner at four levels, namely:

• Organization level security by setting the Organizational Security indicator in the new Salary Planner Rules window on the Position Control Installation Rules Form (NTRINST.)

For more details, refer to the NTRINST form in the Changed Forms topic in this section of the Release Guide.

• Employee Class level security using the existing functionality of Employee Class Security Form (PSAECLS) and the Installation Rules Form (PTRINST).

• Employer level security using the existing functionality of Employer Security Form (PSAEMPR) and the Installation Rules Form (PTRINST).

• Salary level security by specifying in the User Codes Rule Form (PTRUSER) and the Installation Rules Form (PTRINST).

In addition to specifying organization security, organization hierarchy also has to be established for the Salary Planner. Organization hierarchy can be implemented at enterprises having either Banner Human Resources or Banner Finance. Organization hierarchy is established in the Organization Code Validation Form (PTVORGN) at enterprises having only Banner Human Resources whereas Organization Code Maintenance Form (FTMORGN) is used at enterprises having Banner Finance. PTVORGN has been enhanced to enable the set up of an organization hierarchy when Banner Finance is not installed. For more details refer to the Changed Forms topic in this section of the Release Guide.

Note: Organization hierarchy in Finance takes precedence for enterprises that have Banner Human Resources as well as Banner Finance.

All other levels of security have to be implemented in Banner Human Resources regardless of where organization hierarchy is established - in Banner Finance or Banner Human Resources. Therefore, Banner Human Resources is a mandatory requirement for the Salary Planner.

At the user level, Salary Planner users can be set up with the following types of access: Update, Query, or None. These levels of access can be specified in the User Codes Rule Form (PTRUSER) for each user. Users who will be accessing the Salary Planner within Employee Self-Service need to be set up on this form.

Users with Update access can access, edit, and modify data in the Salary Planner.

Users with Query access can only access and review information in the Salary Planner. They cannot edit or modify data in the Salary Planner.

Users with None access cannot access or view information in the Salary Planner application in Employee Self-Service, unless set up with specific access on the new Salary Planner Security Form (NSASPSC). See Note below.



Note: Users with Query or None access in PTRUSER can be given access to view information for specific organizations in the Salary Planner. Access to these organizations can be established on the new Salary Planner Security Form (NSASPSC). In this case, NSASPSC overrides the security setup in PTRUSER for the specified organizations.

For a detailed description of NSASPSC, refer to the topic, New Forms on page 58, in this section of the Release Guide.

Setting Up Banner Forms for the Salary Planner

After setting up security, set up the following forms in Banner Human Resources for completion of a workflow between Banner and the Salary Planner, and vice-versa:

1. Run the script, NSPACAT.SQL to create Approval Types and assign Approval Categories. This script has been developed specifically to enable the Salary Planner Upload process (NBPSPUP) to create EPAFs when data is uploaded back into Banner from the Salary Planner.

The approval categories established here are used in the Installation Rule Form (NTRINST).

For more details, refer to the topic, New Install Script on page 132.

2. Assign mandatory approval levels on the Electronic Approval Category Rules Form (NTRACAT) for the approval categories defined from the NSPACAT.SQL script. For more information on Electronic Approvals, refer to Chapter 19 of the Human Resources User Guide, Release 6.0.

User Codes Rule Form(PTRUSER)

Set up user access tothe Salary Planner

Salary Planner Security Form(NSASPSC)

For users with Query or No access, setup access to specific organizations in

the Salary Planner

Section 5 Banner Support for Salary Planner - Functional Process Flows


3. Any user with security access to run the upload process (NBPSPUP) will be required to have Electronic Approval Routing Rules set up on NTRROUT for the Approval Categories defined on NTRINST for use with the Salary Planner. Based on the user running the process and the Approval Category associated with the EPAF, the approval level information set up on NTRROUT will default to the EPAFs created.

4. In the Salary Planner Rules window of the Installation Rules Form (NTRINST), define rules for the display of jobs in the Salary Planner application, and identify approval categories that will be responsible for reviewing or applying EPAFs when data has been uploaded into Banner.

5. Create Budget Profile codes in the Budget Profile Validation Form (NTVBPRO), if desired.

6. Associate Positions with a Budget Profile on the Position Budget Form (NBAPBUD), if desired. This provides a mechanism by which positions can be further defined for budgeting purposes.

Note: Each position can be associated with only one budget profile at any time.

7. On the Job Change Reason Rule Form (PTRJCRE), indicate the job change reasons that are to be displayed and included in totals in the Salary Planner application, such as Merit or COLA.

8. On the Salary Planner Extract Rules Form (NTRSPEX), create Budget Extract IDs and specify criteria by which data is to be extracted from Banner Human Resources.

9. A user runs the Salary Planner Extract Process (NBPSPEX) in Banner HR to download the budget extract into the Salary Planner for a specific Budget Extract ID.

Note: Any user of Banner HR can run this extract process. However, your Database Administrator can restrict it to only Salary Planner users through the Oracle Role Security set up.

10. In the Employee Self-Service, Salary Planner module, Master Salary Planners can now modify the Initial Scenario and create multiple budget scenarios from the Initial Scenario in the Salary Planner.

11. HR Managers can now modify budget scenarios (other than the Initial Scenario) in the Salary Planner and copy their final changes into a final scenario.

12. A user uploads the final version of the budget scenario back into Banner via the new Salary Planner Update Process (NBPSPUP).



Budget Profile Validation Form (NTVBPRO)Create budget profile codes

Position Budget Form (NBAPBUD)Associate positions with budget profile codes

Salary Planner Extract Rules Form (NTRSPEX)Create Budget Extract IDs and specify extract rules

Job Change Reason Rule Form (PTRJCRE)Indicate job change reasons that

are to be used in the Salary Planner

Salary Planner Extract Process (NBPSPEX)Download budget data into the Salary Planner

Create budget scenarios from the Initial Scenario ofthe extracted data in the Salary Planner

Upload locked and final scenarios into the SalaryPlanner via the Salary Planner Update Process

(NBPSPUP)

Installation Rules Form (NTRINST)Define rules, approval categories for EPAF

processing of uploaded budget data

Modify budget changes in the Salary Planner

Section 5 Banner Support for Salary Planner - Functional New Forms


New Forms

Budget Profile Validation Form (NTVBPRO)

The Budget Profile Validation form allows you to create budget profile codes and descriptions for use in the Salary Planner Application. A Budget Profile is a means for classifying different types of budgets that are used at an enterprise.

The budget profiles entered on this form help identify, describe, and associate positions with a specific type of budget on the Position Budget Form (NBAPBUD).

Section 5 Banner Support for Salary Planner - FunctionalNew Forms


Enter the following information to create new budget profile codes:

Salary Planner Extract Rules Form (NTRSPEX)

The Salary Planner Extract Rules Form (NTRSPEX) is a new rule form that allows you to identify the population that is to be extracted from Banner into the Salary Planner. The criteria you specify in this rule form is used as the input for the Salary Planner Extract Process (NBPSPEX). The extract population can be identified by specifying one or more of the following factors for inclusion in the extract process:

• Employee Classes

• Bargaining Units

• Budget Profiles

The NTRSPEX form consists of a Key block, a Main block and a window for each of the above. To specify any of the above, select the appropriate choice from the Options menu.

Key Block

The population criteria for an extract process is grouped and identified by a Budget Extract ID. Specify a new Budget Extract ID in the Key block of the form.

Note: To create a new Budget Extract ID without copying from an existing Budget Extract ID, specify the new Extract ID in the Current Budget Extract ID field and navigate to the next block.

To create a new Budget Extract ID using the Copy function, specify the new Extract ID in the New Budget Extract ID field and specify the following fields:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Budget Profile Code

Enter a 6-character alphanumeric budget profile code to categorize a specific type of budget.

Description Enter a description of the budget profile code.

Save the record.

User ID Displays the Banner ID of the employee who last updated the record.

Activity Date Displays the date on which the record was last updated.



. . . . . . . . . . . . . . . .Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Current Budget Extract ID

Enter a new Budget Extract ID to specify new criteria.

Alternatively, select an existing Budget Extract ID using the Search button if you wish to copy population criteria from an existing Budget Extract ID. The corresponding List of Values displays all Budget Extract IDs previously defined on this form.

(button) Search Budget Extract ID (NTRSPEX)

New Budget Extract ID

Enter a new Budget Extract ID if you have specified an existing Budget Extract ID in the previous field. The population criteria from the existing Budget Extract ID are copied into the new Budget Extract ID when you select the Copy Record function in the Options menu.



Main Block

Enter details regarding the new Budget Extract ID and specify preliminary selection criteria in this block.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Description Enter a short description of the new Budget Extract ID.

COA Enter or select a Chart of Accounts code by selecting the Search button.

(button) Search FTVCOAS if Banner Finance is installed.

This field is disabled if Banner Finance is not installed.

Fiscal Year Enter a fiscal year with which the Budget Extract ID is to be associated or select one using the Search button.

(button) Search Fiscal Year Form (NBAFISC)

Budget ID Associate a Budget ID with the Budget Extract ID. Enter or select one from the List of Values (LOV).

(lookup) List Operating Budget List (FTVOBUD)


Phase Associate a phase with the Budget Extract ID. Enter or select one from the corresponding List of Values (LOV).

(lookup) List Budget Phase List (FTVOBPH)


Budget Status Indicate the budget status for the selected budget ID and budget phase by choosing the appropriate radio button. Required field. Options include:

Approved

Working (default)

Enter the following preliminary criteria in the Selection Data block.

Include Secondary Jobs

Select this check box to include secondary jobs in the extract. Optional field.



Employee Classes Window

The Employee Classes window allows you to specify employee classes associated with positions on the Position Definition Form (NBAPOSN) that are to be considered by the Budget Extract ID. Access this window from the Options menu of NTRSPEX. Select employee classes using any of the following methods:

• Select the Include all Employee Classes in the Options menu to mass populate this window with all employee classes existing in Banner, and then selectively remove specific employee classes using the Record > Remove menu option or icon.

OR

• Individually select employee classes using the Search button in the Code field.

Include Overload Jobs

Select this check box to include overload jobs in the extract. Optional field.

Include Positions with No Bargaining Unit

Select this check box to include positions with no bargaining units defined in the Position Definition Form (NBAPOSN), in the extract. Optional field.

Include Positions with No Budget Profile.

Select this check box to include positions with no budget profile defined on NBAPBUD in the extract. Optional field.

User ID Displays the ID of the user who last updated this record.


. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Each employee class is displayed with the following information:

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Code Enter or select an Employee Class code using the Search button.

(button) Search Employee Class Query Form (PTQECLS)

Description The system displays a description of the selected Employee Class code.

Budget Factor Enter a budget factor for the specified employee class. This percent factor is used in the calculation of an Estimated Fiscal Year Budget amount in the Salary Planner. This factor indicates for what percent of the year the new Annual Salary would apply.

The Estimated Fiscal Year Budget is calculated as:

(Proposed Annual Salary x Factor) + [(1 - Factor) x Base Salary]

For example,

Fiscal year is July 1 to June 30. The employee's Base Salary (effective July 1) equals $50,000. His/her Proposed Salary (effective September 1) equals $60,000. The factor would be set to 83.33 (10/12). The Estimated Fiscal Year Budget for this job would be $58,333.



Bargaining Units Window

Similar to the Employee Classes window, specify bargaining units to be considered in the extract in this window. Bargaining units can be selected via any of the following methods:

• Select the Include all Bargaining Units from the Options menu to populate this window with all bargaining units existing in Banner, and then selectively remove bargaining units that you do not wish to include in the extract by using the Record --> Remove menu option or icon.

OR

• Individually select only those bargaining units that are to be included in the extract through the List of Values corresponding to the Bargaining Unit Code field. Access the LOV in the Bargaining Unit Code field

Job Effective Date

Enter a job effective date for each employee class.

This date is utilized to upload data to the job record from the Salary Planner. The first day of the new fiscal year is the default, based on the Chart of Accounts and Fiscal Year entered for the Budget Extract ID, but may be overridden.

Job Personnel Date

Enter an effective personnel date for each employee class.

This information is used to upload data to the job record in the Salary Planner. The first day of the new fiscal year is the default, based on the Chart of Accounts and Fiscal Year entered for the Budget Extract ID, but may be overridden.

. . . . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Include Positions with No Bargaining Units

Displays the check box indicator as marked for the corresponding field in the Main block of NTRSPEX.

A check indicates Yes.

Unchecked indicates No.

Bargaining Unit Code

Enter or select a bargaining unit code from a List of Values (LOV).

(lookup) List Bargaining Unit Validation Form (PTVBARG)

The system displays a short description of each bargaining unit code.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



The following table identifies the population that will be extracted based on the selection of the Include Positions with No Bargaining Unit indicator field in the Main block and the selections in the Bargaining Units window of NTRSPEX:

Include Positions with No Bargaining Unit Indicator

Bargaining Unit window Extract Population

Checked or Yes None Defined Null bargaining units only

Checked or Yes Defined Null bargaining units and defined bargaining units

Unchecked or No None Defined Error. Bargaining unit edit.

Unchecked or No Defined Defined bargaining units only



Budget Profiles Window

Specify budget profiles to be considered by the extract in the Budget Profiles window. Budget Profiles can be selected via any of the following methods:

• Select Include all Budget Profiles menu option from the Options menu to populate this window with all budget profiles existing in Banner, and then selectively remove budget profiles that you do not wish to include in the extract by using the Record --> Remove menu option or icon.

OR

• Individually select only those budget profiles that are to be included in the extract using the List of Values (LOV) corresponding to the Budget Profile Code field. Double-click to access the LOV in the Budget Profile Code field.

. . . . . . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Descriptions

Include Positions with No Budget Profiles

Displays the check box indicator as marked for the corresponding field in the Main block of NTRSPEX.





The following table identifies the population that will be extracted based on the selection of the Include Positions with No Budget Profile indicator field in the Main block and the selections in the Budget Profiles window of NTRSPEX:

Salary Planner Security Form (NSASPSC)

The Salary Planner Security Form (NSASPSC) is a new form developed to enforce organization security for the Salary Planner. This form should be set up for Salary Planner users who are not given Update access in the Salary Planner Master Organization field on the User Codes Rule Form (PTRUSER). In other words, organization security should be specified on this form for all Salary Planner users who have been given either Query or None access in Salary Planner Master Organization field in PTRUSER.

This form allows you to selectively include or exclude organization access for each user. You can also copy the organization security defined for one user to another within a single Chart of Accounts (COA).

The Salary Planner Security Form (NSASPSC) gives you greater control in determining access to data in the Salary Planner as you can not only specify access to a range of organizations, but now also restrict or include access to specific organizations within or outside the range, respectively.

Budget Profile Code Enter or select a budget profile code from a List of Values (LOV).

(lookup) List Budget Profile Validation Form (NTVBPRO)

The system displays a short description of each budget profile code.

Include Positions with No Budget Profile Indicator

Budget Profiles window Extract Population

Checked or Yes None Defined Null budget profiles only

Checked or Yes Defined Null budget profiles and defined budget profiles

Unchecked or No None Defined Error. Budget profile edit.

Unchecked or No Defined Defined budget profiles only

. . . . . . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Descriptions



Note: The Salary Planner Security Form (NSASPSC) only affects organization security within the Salary Planner enhancement, and does not affect other Banner HR security.

Key Block

Enter information in the following fields to define the organization security for a new user of the Salary Planner.

The Key block also allows you to copy organization security between two users or delete a user’s organization security for specific organizations.

You can copy the organization security from one user to another provided the organizations belong to the same Chart of Accounts code (COA). To copy the organization security from one user to another, specify the information below and then select Copy Record in the Options menu.

To delete a user’s organization security for specific organizations, specify the key block elements and choose Delete Organization by Group in the Options menu.



. . . . . . . . . . . . . .Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Current User Enter the name of the current user or choose the current user by selecting the Search button. Required field.

(button) Search User Codes Rule Form (PTRUSER)

New User Enter the name of the new user or choose a new user by selecting the Search button.

(button) Search User Codes Rule Form (PTRUSER)

Enter this field only if you wish to copy the organization security of the current user to the new user. Then select Copy Record from the Options menu. Optional field.

Include Organization

To include organizations for a new user, enter an organization code or select using the Search button.

(button) Search Organization Code Validation Form - Finance (FTVORGN) when Banner Finance is installed.

(button) Search Organization Code Validation Form (PTVORGN) when Banner Finance is not installed.

All organization codes will be copied for the new user, if this field is blank.

Exclude Organization

To exclude organizations for a new user, enter an organization code or select using the Search button.



Note: If this field is blank, it does not imply all organization codes are excluded for the new user.



Main Block

COA Code Enter or select a COA code using the Search button.

(button) Search Chart of Accounts Validation Form (FTVCOAS) when Banner Finance is installed. Required field.

This field is disabled when Banner Finance is not installed.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Organization Displays a list of organizations that match the include/exclude criteria, if specified in the Key block.

Alternatively, you can individually specify the organizations for which access is to be provided by selecting the Search button.



The system displays a short description of each selected organization code.

Access Specify the type of access for each organization from the drop-down list. Options include:

Update Enables the user to change and save the modified information in the corresponding Web pages of the Salary Planner.

Query Enables the user to only query on the information displayed in the Salary Planner.

. . . . . . . . . . . . . .Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Section 5 Banner Support for Salary Planner - FunctionalChanged Forms


Changed Forms

Validation Form

Rule Forms

Application Form

Other

Organization Code Validation Form (PTVORGN)

The Organization Code Validation Form (PTVORGN) has been enhanced to allow you to specify an organization hierarchy for use in the Salary Planner. This version of the form is available only when Banner Finance is not installed at your enterprise. Otherwise, the existing version of PTVORGN will be available when Banner Finance is installed.

PTVORGN Organization Code Validation Form

NTRINST Position Control Installation Rules FormPTRUSER User Codes Rule FormPTRJCRE Job Change Reason Code Rule Form

NBAPBUD Position Budget Form

NOQLIBRNOQMENU

Section 5 Banner Support for Salary Planner - Functional Changed Forms


To set up an organization hierarchy,

1. Ensure that you have entered all required organization codes. The entered codes will be used as predecessor codes.

2. Next, specify a predecessor code for an organization, select a code from the corresponding drop-down list. The LOV displays all existing organization codes.

3. Continue to specify a predecessor code for each subsequent organization code.

For example, to set up a 2-level organization hierarchy in the above window for organization codes 10, 100 and 1000 wherein 10 is the predecessor organization for 100, and 100 precedes 1000:

(a) Enter 10 in the Organization Code field

(b) Enter a short description of the organization in the Description field.

(c) Leave the Predecessor field blank

(d) Save the record.



(e) Now create a second record by entering 100 in the Organization Code field.

(f) Enter a short description of the organization in the Description field.

(g) Double-click in the Predecessor field to access a List of Values (LOV) that displays all previously saved organization codes - in this case, org. code 10. Select the organization code, 10 from the LOV.

The system displays the description of the predecessor organization 10, by default.

(h) Save the record.

(i) Now create a third record by entering 1000 in the Organization Code field.

(j) Enter a short description of the organization in the Description field.

(k) Double-click in the Predecessor field to access a List of Values (LOV) that displays all previously saved organization codes - namely 10, and 100. Select the organization code, 100 from the LOV.

The system displays the description of the predecessor organization, 100, by default.

(l) Save the record.

Proceeding in this manner, an organization hierarchy of up to 8 levels can be defined and viewed on this form. This functionality is similar to the corresponding Finance form, Organization Code Maintenance Form (FTMORGN).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Organization Code

Enter organization codes for the creation of a hierarchy.

Description Enter a short description for the new organization code.

Predecessor Enter or select from a List of Values (LOV) which displays previously saved organization codes. Select one that would precede an existing organization.

Description For predecessor organizations, the system displays the description of the corresponding organization by default, since the information has been previously saved.




Organization Hierarchy Window (PTQORGH)

The Organization Code Validation Form (PTVORGN) has been enhanced with the addition of a new Organization Hierarchy window (PTQORGH). This window will be available and accessible only when Banner Finance is not installed at your enterprise, giving you the ability to view the organization hierarchy for an organization code selected in the previous window.

This window displays all preceding organizations associated with an organization code with the highest preceding organization displayed first in the list. This form is display-only.

Continuing with the previous example, organizations 10 and 100 will be listed as the preceding organizations for organization code 1000, wherein the predecessor organization 10 is listed first, followed by the predecessor organization code 100.



Position Control Installation Rules Form (NTRINST)

The Position Control Installation Rule Form defines rules for general location, position control, and finance, as well as rules specific to the processing of Electronic Approvals.

Salary Planner Rules Window

A new Salary Planner Rules window has been added to NTRINST that allows you to establish control by setting rules at the enterprise level for the following features of the Salary Planner application in Employee Self-Service:

• Jobs displayed on the Employee Details page in the Salary Planner,

• Enable organizational security within the Salary Planner

• Define proration criteria for flat amounts and jobs-related data, and

• Identify electronic approval categories to process job and salary updates made in the Salary Planner. The updates will be incorporated into Banner via EPAF transactions that will refer to the categories set up in this window.

Access the Salary Planner Rules window from the Options menu of NTRINST

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Organization Displays the current organization code and its corresponding description for the record selected in the Organization Code Validation Form (PTVORGN).

Predecessor Displays the immediate predecessor of the organization code listed in the previous field, along with its corresponding description.

Below this field, all subsequent predecessors are listed along with their corresponding descriptions in a hierarchy.



. . . . . . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

View Whole Employee Detail

Select this check box to enable Salary Planner users to view an employee’s job(s) across all COAs and Organizations regardless of HR security. This indicator affects the display of data on the List by Employee page and the Employee Details page in the Salary Planner.

A check indicates Yes


This feature allows a user to view all jobs belonging to an employee that may be associated to organizations other than those to which the user is authorized. The system displays all jobs as long as the user has organizational access to at least one of them.

In essence this rule overrides the organization security set up for the Salary Planner when viewing records on the Employee Detail page. It will also enable the Employee Totals columns on the List by Employee page.

Organizational Security

Select this check box to enforce organization security at the system level in the Salary Planner. This rule causes the system to check the security set up on PTRUSER and NSASPSC for each Salary Planner user.





Prorate Flat Amount Based On

Select a method to automatically prorate flat amount mass changes based on any of the following factors:

FTE

Appointment percent or

None (No Proration)

The selected proration method will apply to mass changes on jobs and positions.

Note: If the Base FTE or Base Appointment percent is changed on a specific record in the Salary Planner after a mass change, it will not result in a corresponding proration change in the proposed amount.

This automated functionality affects the List by Position page, List by Job page, and the Employee Detail page in the Salary Planner, in Employee Self-Service.

Calculate Job Information Based On

Select a method to calculate job information from the following options:

FTE

Appointment percent or

None (No Proration)

Based on the selected method the Hours per Pay, Hours per Day, and the Default Hours are calculated for hourly jobs whereas the annual salary and a new hourly rate is calculated for salaried jobs.

For example, if the FTE method is selected to calculate job information for an hourly job, and the FTE is changed from 1 to 0.5, then the Hours per Pay, Hours per Day and the Default hours are also reduced proportionately.

This automated functionality affects the Job Details page and the Employee Details page in the Salary Planner.

Identify Approval Categories to incorporate job and salary updates made in the Salary Planner back into Banner via electronic approvals using the Salary Planner Upload Process (NBPSPUP).

. . . . . . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



Job Salary Approval Category

Access the LOV and select an Approval Category to use with any job salary updates made in the Salary Planner via EPAFs.

The system displays a short description of the selected Approval Category.

Default Hour Approval Category

Access the LOV and select an Approval Category to use with any changes made to the Default Hours in the Salary Planner via EPAFs.


Job Labor Distribution Approval Category

Access the LOV and select an Approval Category to use with any changes made to the Job Labor Distributions in the Salary Planner through EPAFs.


Combined Job Approval Category

Access the LOV and select an Approval Category to use if changes have been made to the job information in more than one aspect (i.e., default hours, job salary or job labor distribution) in the Salary Planner.

The Approval Category selected in this field will be used by default in the instance of multiple changes to job information.


Note: Approval Categories and their supporting rules are available through a script (NSPACAT.SQL) provided with this release. Refer to the topic, New Install Script on page 132 for further information for constructing the necessary Approval Categories.

. . . . . . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



User Codes Rule Form (PTRUSER)

The User Codes Rule Form establishes User IDs for security purposes. It enables you to define the maximum salary level that can be viewed by specified users and to assign access privileges for all organizations and/or employee classes.

A new field, Salary Planner Master Organization has been added to set up the organization security for each user with a specific type of access to the Salary Planner application in Employee Self-Service. Access types include:

• Update

• Query or

• No Access (None)

Users set up with Update access in the Salary Planner Master Organization field need not be set up on the Salary Planner Security Form (NSASPSC). But users set up with either query-only or no access to the Salary Planner on this form may need to be set up on NSASPSC if they are to be given update or query access to specific organizations in the Salary Planner.

Note: In addition to the above new field, also set the Master Employer, Master Employee Class and Salary Level security as required. You can specify unlimited salary level access by entering a limit of 999,999,999.99. This is existing Banner HR functionality.

It is important to note that in addition to the Salary Planner Master Organization security, the Employer, Employee Class, and Salary Level security features identified on PTRUSER apply to the Salary Planner as well as Banner Human Resources.

See a graphic of the User Codes Rule Form (PTRUSER) on the following page.



Position Budget Form (NBAPBUD)

The Position Budget Form (NBAPBUD) authorizes all positions. It enables you to define position budgets by fiscal year, regular earnings totals (budgeted, encumbered, expended, and remaining), premium earnings totals, fringe benefits, and position labor distributions.

A new field has been added that allows you to associate each position with a budget profile in the Main block of the Position Budget Form (NBAPBUD). Only one value may be associated with one position. However, the profile may be changed anytime.

. . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Descriptions

Budget Profile

Associate a position with a budget profile code from the List of Values. The entries displayed in the LOV correspond to the profile codes created in the Budget Profile Validation Form (NTVBPRO). Optional field.

(lookup) List Budget Profile Validation Form (NTVBPRO)

The system displays a description of the selected budget profile code.



Job Change Reason Code Rule Form (PTRJCRE)

Two new fields have been added to the Job Change Reason Code Rule Form that allow you to specify the priority given to change reason codes and also indicate if these reason codes are to be made available in the Salary Planner. These fields only relate to the Salary Planner application within Employee Self-Service.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Display priority on the Web

Prioritize the change reason codes by specifying a number in this field. The Salary Planner Web pages will sort and display the change reason codes in the same sequence order as specified on this form.

Note: The Change Reason code assigned a priority of 1 will be the default reason code displayed for an employee on the List by Employee page.



Include in Web Totals

Select this check box to indicate whether the amount or percent associated with the Change Reason code is to be included in the totals on the Employee Detail page of the Salary Planner.

For example, if the employee has the following changes:

Reason Percent AmountInclude in Totals

MERIT 2.00 1000.00Yes

COLA 3.00 2000.00Yes

Other 1.50 300.00No

Then, the Total Change Percent is 5.00 and the Total Change Amount is $3,000.00. The $300.00 will not be included in the total change.

Note: This indicator controls the computations for percentage and dollar increases reported in the Salary Planner. While a site may not consider some computation components as a part of their increase for the coming fiscal year (such as an FTE change for an employee), this control has no effect on the final Salary Budget loaded to a position or the salary associated with a employee’s job assignment.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions



NOQLIBR

Two new List of Values (LOVs) have been added for the Budget Profile code and Extract ID code used in the Position Budget Form (NBAPBUD) and the Salary Planner Extract Rules Form (NTRSPEX).

NOQMENU

This form has been modified to include a new global variable for the Extract ID code.




Section 5 Banner Support for Salary Planner - Functional New Processes

Human Resources/Position Control Release 7.0 January 2005 85 Release Guide Confidential

New Processes

Two new processes have been created to transfer data back and forth between Banner and the Salary Planner application in Employee Self-Service.

Salary Planner Extract Process (NBPSPEX)

Description The Salary Planner Extract Process (NBPSPEX) extracts data from Banner to the Salary Planner application in Employee Self-Service. The extracted data in the Salary Planner is transferred from Banner tables to a group of working budget tables in the Salary Planner. The extracted data is given the Scenario name as Initial, and can only be viewed or modified by a Master Salary Planner.

Note: All Master Salary Planners must have their Salary Planner Master Organization security enabled in the User Codes Rule Form (PTRUSER).

The NBPSPEX process can be run in three different modes: (I)nitial, (R)e-create, and (A)dd/Delete modes.

• Run the process in the (I)nitial mode when first extracting data from Banner for a new Budget Extract ID. The process checks for the existence of the Budget Extract ID in the working budget tables of the Salary Planner and if it exists, generates an error message in the Report Control section of the output.

• Run the process in the (R)e-create mode when you wish to remove all existing scenarios in the Salary Planner and re-create the Initial Scenario associated with an existing Budget Extract ID.

• Run the process in the (A)dd/Delete mode when you want to update extracted data that may have occurred in Banner forms. In this case, the process will add new position/job records that were created in Banner or remove position/job records that were terminated since the last extract associated with the Extract Effective Date.



Note: The process will not update existing scenario records with any changes that may have been made in Banner since the last extract. Only new and terminated records will be affected.

The extract process will only extract positions with a position status of Active or Frozen, and a budget status of Working or Approved. The maximum effective-dated record for a position working budget will be extracted based on the Fiscal Year, COA, Budget ID and Phase. The use of working position budget records with the same Fiscal Year, COA, Organization, Budget ID and Phase but different create dates may cause a problem and is strongly discouraged. Similarly, the use of position budget records with the same Fiscal Year, COA, Budget ID and Phase but different Organizations is strongly discouraged.

Parameters Name Description/Values Required? Default Validations

01 Process Mode Specify the mode to run the process. Options include:

• (I)nitial

• (R)e-create

• (A)dd/Delete

Yes (I)nitial None

02 Budget Extract ID Specify the Budget Extract ID that is to be used by the process. Data will be extracted based on the rules entered in NTRSPEX for the relevant Budget Extract ID.

Yes None NTRSPEX



03 Job Effective Date Specify the Job Effective Date to be used by the process when selecting employee records.

The process will extract only those job records whose Job Effective Date is prior to or identical to the date entered for this report parameter.

Yes None DD-MMM-YYYY

04 Proposed Salary Group Specify an existing salary group to update or change job salaries in the Salary Planner.

Yes None NTRSGRP

05 Copy Position Labor Distribution to Jobs

Indicate whether the position Budget Labor Distributions should be copied to the relevant Job Labor Distributions.

Yes N Y, N or y, n

06 Organization(s) to copy Specify the budget organization that will copy the Position Labor Distributions to the corresponding Job Labor Distributions

Yes, if the Copy Position Labor Distribution to Jobs parameter is set to Yes.

N Y, N or y, n

07 Include Subordinate Organizations

Indicate whether subordinate organizations associated with the selected organizations are to be included in the extract.

Yes, if the Copy Position Labor Distribution to Jobs parameter is set to Yes.

None FTVORGN or PTVORGN




Sort Order By Organization Code

Data Source NTRSPEX, NBAPOSN, NBAPBUD, NBAJOBS

Frequency On demand

Output Standard horizontal format

Fields Name Description

COA Displays the Chart of Accounts code associated with the Budget Extract ID

Fiscal Year Displays the Fiscal year associated with the extracted data.

Budget ID Displays the Budget ID associated with the extract rules specified on the Salary Planner Extract Rules Form (NTRSPEX).

Phase Displays the Phase associated with the Budget ID

Budget Status Displays the status of the budget as either Approved or Working as selected in NTRSPEX.

Include Secondary Jobs Indicates if data associated with secondary jobs have also been extracted by the process based on the rule specified in NTRSPEX.

Include Overload Jobs Indicates if data associated with overload jobs have also been extracted by the process based on the corresponding rule set up in NTRSPEX.



Include Positions with No Bargaining Units

Indicates if positions with no bargaining units have also been extracted by the process based on the corresponding rule set up in NTRSPEX.

Include Positions with No Budget Profiles

Indicates if positions with no budget profiles have also been extracted by the process based on the corresponding rule set up in NTRSPEX.

Employee Class Displays employee classes that have been included in the extract. This information is based on the employee classes selected for the Budget Extract ID in NTRSPEX.

Budget Factor Displays the budget factor associated with each employee class that has been included in the extract.

Job Effective Date Displays the Job Effective Dates that meet the criteria specified in the Job Effective Date parameter of NBPSPEX process.

Personnel Date Displays the Personnel Dates that meet the criteria specified in the Personnel Date parameter of the NBPSPEX process.

Bargaining Units Displays the Bargaining units that have been included in the extract process.

Budget Profiles Displays the Budget Profiles that have been included in the extract process.

Total Jobs, Positions, and Organizations

Displays the number of records in the entire extract population in the Salary Planner for this Extract ID. This does not represent the number of records processed.




Report Sample—Salary Planner Extract Process (NBPSPEX)

PAGE 1NBPSPEX Banner University RUN DATE 13-JAN-2004 Salary Planner Extract Process RUN TIME 09:04 AM

Budget Include Include Include Positions Include Positions COA Fiscal Year Budget ID Phase Status Secondary Jobs Overload Jobs No Bargining Units No Budget Profiles A 2005 FY05 ADMIN W N Y Y Y

Employee Class Budget Factor Job Effective Date Personnel Date U4 100.00 01-JUL-2004 01-JUL-2004 U5 100.00 01-JUL-2004 01-JUL-2004

Bargaining Units

Budget Profile GRNT GRNT02 GRNT03 GRANT6 NONREC RECUR GRNT04 GRNT2 GRNT3 GRNT4 GRNT5 GRNT05

Jobs in these Organizations were successfully updated:



PAGE 2NBPSPEX Banner University RUN DATE 13-JAN-2004 Salary Planner Extract Process RUN TIME 09:04 AM Process Parameters

* * * Report Control Information * * *Parameters have been entered via Job Submission.

Parameter Name Value______________________________ ________________________________________________________________________________Parameter Sequence No: 78003Process Mode R - Re-createBudget Extract ID FY05ADMIN - FY04-05 AdministrativeJob Effective Date 01-JUL-2004Proposed Salary Group 2005Copy Position Distribution to Jobs YInclude Subordinate Orgns N

SUCCESS* Recreated INITIAL extract from production data.

Total Jobs: 22Total Positions: 26Total Organizations: 12



Salary Planner Upload Process (NBPSPUP)

Description The Salary Planner Upload Process uploads position and job data from the Salary Planner application in Employee Self-Service to Banner. Position budget and position distributions will be uploaded into the related NBAPBUD Position Budget tables whereas job information will be uploaded by creating appropriate EPAFs in Banner. The relevant approval queues set up for the Approval Categories and Approval Types dictate how the job information and job labor distributions EPAFs get applied in Banner utilizing the NOPEAMA Mass Apply process or the Online Apply Process.

Run the upload process to upload position information or job EPAFs, or both. This provides you with the flexibility for using the Salary Planner exclusively for Position Budget updates as well as job salary updates.

Note: Only one Scenario and Extract ID combination can be uploaded at a time. However the upload process may be rerun to allow the Extract ID to be uploaded any number of times, making allowances for corrections to the extract that may arise after the initial upload. The relevant data will be updated only for the changed records in the Salary Planner. Accordingly, new EPAFs will be generated to update any corrected job information from the Salary Planner, thereby voiding the previous related EPAFs in a Waiting status.

Scenarios cannot be uploaded unless all organizations are locked. If the upload process finds unlocked organizations in the population, a list of the unlocked organizations along with an error message will be printed on the report and no data will be uploaded.

Additionally, the NBPSPUP process can be run in three different modes: Report, Process or Delete mode.

Run the process in the Report mode for verification purposes. The process prints a report of any upload type of process errors or warning encountered, without making any changes to the database.

Run NBPSPUP in the Process mode to update position data directly (budget and distribution on NBAPBUD) and/or job information (through the creation of EPAFs) in Banner. This mode makes permanent changes to the database.



Run the process in the Delete mode to delete combinations of Extract ID and Scenario from the Salary Planner application in Employee Self-Service. Multiple scenarios associated with a single Budget Extract ID can be deleted at a time. An Initial Scenario cannot be identified for deletion to prevent orphan scenarios from existing. Use a percent sign (%) to delete an Extract ID and all its associated scenarios.

Position Upload

The Salary Budget and Labor Distribution areas of the Position Budget record are updated by a position upload from the Salary Planner in Employee Self-Service to the NBAPBUD associated tables in Banner. Specifically, the following information is updated when position data is uploaded by NBPSPUP:

• The upload process updates data corresponding to only Active or Frozen positions.

• It also updates the Date Created field for a budget in the Position Salary Budgets window of the Position Budget Form (NBAPBUD), based on whether the fiscal year is Active or not. For an active fiscal year, the Create Date is the greater of the System Date or the Position Begin Date. For an inactive fiscal year, the Create Date is the greater of the Position Begin Date or the Fiscal Year Begin Date on NBAFISC.

• The upload process updates position data for a single COA, Fiscal Year, Budget ID and Phase, provided the associated position salary budget record exists in Banner. The data can be uploaded to either a Working or an Approved Budget ID and Phase. The upload process recalculates the distribution percentages for position labor distributions that were modified in the Salary Planner and prints any errors in the upload report.

Note: Ensure that you do not maintain multiple budget records for a position, each with a different Create Date for the same combination of Fiscal Year, COA, ID and Phase. This situation applies only for Working budgets. The Upload process will update the record that has the latest Effective Date.

For example, if two position budget records exist for a position with Create Dates of 07/01/2004 and 12/01/2004, respectively, the upload process will in this case, update the position budget record with the Create Date of 12/01/2004 when the intended update may have been meant for the record with the Create Date of 07/01/2004.



For the same reason, also ensure that you do not maintain multiple budget records for a position, each with a different organization for the same combination of Fiscal Year, COA, ID and Phase. In the absence of multiple budget records for a position, the upload process updates the position budget (NBRPTOT) record with the Maximum Effective Date for the combination of Fiscal Year, COA, ID, Phase and Organization.

• Comments associated with positions will be updated to the Comment window of the Position Budget Form (NBAPBUD).

• Position budget and distribution data will be uploaded to the Position Budget Form (NBAPBUD) if changes were made to any of the information relating to a position in the Salary Planner. Positions hidden in the Initial scenario will not be uploaded.

Once the data is uploaded into Banner, Position Control forms and other existing Banner processes can be used to make further modifications.

Job Upload

The Job upload process triggers the creation of EPAFs and their corresponding transaction numbers. The EPAF Transaction number is displayed in the process report and the corresponding Web pages in the Salary Planner.

The Job Detail, Default Hours and Labor Distribution areas of the Employee Job records are updated from the Salary Planner. Specifically, the following information is uploaded by NBPSPUP via EPAFs to update NBAJOBS records in Banner:

• New Job Effective Dates (i.e., Personnel Date and Effective Date) that were initially specified for each employee class in the Salary Planner Extract Rules Form (NTRSPEX) will be uploaded. The dates, if not entered, default to the first day of the new fiscal year based on the NBAFISC record for the specified COA and fiscal year corresponding to the Budget Extract ID.

• Job-related comments are uploaded to the Comments window in the Job Changes Detail Display Form (PEAJCDD).

• Job FTE and Salary records may be created on the Job FTE/Salary Calculations and Tracking Form (NBAJFTE) during the upload if the Create FTE/ Salary Records indicator is marked for the corresponding position.

• The upload process checks for the appropriate approval categories on the Installation Rule Form (NTRINST). It also determines which Approval Category to use based on the number and type of records to be updated.



Note: Look at the Electronic Approval Type Rules Form (NTRAPTY) for the Approval Types set up by the installation script NSPACAT.SQL to get a list of all the fields on NBAJOBS that may be uploaded.

When a Job is defined as Salaried (based on the Salary Table) only the Annual Salary is uploaded from Salary Planner. The EA Mass Apply Process (NPOEAMA) will calculate the Assign Salary and Hourly Rate. When a job is defined as Hourly only the Hourly Rate is uploaded from Salary Planner.

The following table provides a description of the EPAF status in the various records under specific conditions:

EPAF Condition Transaction Status NOBTRAN Table

Queue Status NORROUT Table

Apply Status NORTRAN Table

EPAF has errors Waiting (W) In the Queue (I) In the Queue (I)

EPAF has no Errors. It has been submitted and is awaiting approval.

The Routing Information window of NOAEPAF (NORROUT) has records with ACTION_IND set to A, (Approval)

Pending (P) Pending (P) Pending (P)

No Errors

EPAF has been submitted and automatically approved.

The User running the upload is the same User identified as the sole approver,

OR

The Routing Information window of NOAEPAF (NORROUT) does not have records with an ACTION_IND = A (Approval).

Approved (A) Approved (A) Pending (P)



Changed the original EPAF transaction from a Transaction Status of Waiting to Void, and the Queue status from In the Queue to Removed from the Queue.

This is only used when the upload process is re-run.

Void (V) Removed from Queue (Q)

Removed from Queue (Q)

Parameters Name Value/Description Required? Default Validation

01 Report Mode Specify the report mode for the process. Options include:

R Report Mode. Generates a report ofupload process errors without creatingEPAFs or updating the database.

P Process mode. Generates a report oferrors encountered, creates EPAFs andupdates the database.

D Delete mode. Deletes scenariosassociated with a Budget Extract ID inthe Salary Planner application ofEmployee Self-Service.

Yes Report None

EPAF Condition Transaction Status NOBTRAN Table

Queue Status NORROUT Table

Apply Status NORTRAN Table



02 Process Specify the information that is to be uploaded by the process from the Salary Planner. Options include:

P Position. Updates Position budget andPosition Distribution information only.

J Job. Updates job information and JobLabor Distribution information only.

B Both. Updates Position and Jobinformation from the Salary Planner.

Yes, if Report parameter is set to either R or P.

None None

03 Budget Extract ID Specify the Budget Extract ID that is to be uploaded from the Salary Planner or whose scenarios are to be deleted in the Salary Planner.

Yes None Budget Extract IDs defined in NTRSPEX

04 Extract Scenario(s) Specify the scenario that is to be uploaded into Banner from the Salary Planner, or deleted from the Salary Planner for the relevant Budget Extract ID.

Multiple scenarios can be specified only if the Report parameter is set to D. Enter % for all scenarios associated with a Budget Extract ID.

Yes None None




Sort Order First by Organization, then by Position and Suffix, followed by Employee IDs.

Data Source NTRSPEX, NBAFISC, FTVOBUD, FTVOBPH, PTVJCRE and the Salary Planner.

Frequency On demand

Output Standard horizontal format

05 Fiscal Year The fiscal year to be updated. Yes, if Banner Finance is Installed.

None NBAFISC

06 Budget ID The Budget ID to be updated by the process. This parameter is available only if Banner Finance is installed.

Yes if the Process parameter is set to P or B.

None FTVOBUD

07 Budget Phase The Budget Phase to be updated by the process. This parameter is available only if Banner Finance is installed.

Yes if the Process parameter is set to P or B.

None FTVOBPH

08 Job Change Reason Specify the job change reasons to be used when updating job records.

Yes if the Process parameter is set to J or B.

None PTVJCRE





The following fields are displayed when only Position Budget data is uploaded by the process from the Salary Planner.

COA The Chart of Accounts associated with the Position Budget being uploaded.

Budget ID The Budget ID associated with the position data being uploaded. This information is drawn from the corresponding parameter specified during the upload.

Budget Phase The Budget Phase associated with the budget ID. This information is drawn from the corresponding parameter specified during the upload.

Department The Department ID and name associated with the positions being uploaded into Banner.

Position The Position being uploaded by the process.

Title The Position Title corresponding to each Position.

FTE The FTE budgeted for each position.

Budget Amount The amount budgeted for each position.

The following fields display the elements of the labor distribution corresponding to each position.

Fund The fund associated with the Position Budget amount.

Organization The organization associated with the Position Budget amount.



Account The account associated with the Position Budget amount.

Program The program associated with the Position Budget amount.

Activity The activity associated with the Position Budget amount.

Location The location associated with the Position Budget amount.

Percent The percent of the Position Budget associated with this labor distribution. The total of all labor distribution records must equal 100%.

The following fields are displayed when job detail information is uploaded by the process, from the Salary Planner.

COA The Chart of Accounts associated with the Job information being uploaded.

Department The Department ID and name associated with the jobs being uploaded into Banner.

Position Suffix Position and Suffix of each job being uploaded.

ID Employee ID associated with the job.

Name Employee name whose job information is being uploaded.

EPAF Transaction # The EPAF Transaction # generated by the upload process.

Effective Date The effective date on which the job information becomes active.




Job FTE The FTE for each job.

Appt% The appointment percent corresponding to each job.

Hours per Day The number of hours per day on the job.

Hours per Pay The total number of hours per pay for each job.

Salary Group The salary group associated with each job.

Salary Table The salary table associated with each job.

Salary Grade The salary grade corresponding to each job.

Salary Step The salary step assigned for each job.

Hourly Rate The hourly rate of each job.

Salary The annual salary corresponding to each job.

The following fields are displayed when job default earnings information is uploaded by the process, from the Salary Planner.

Default Earnings The Regular pay default earnings code associated with each job.

Hours/Units The unit of measure, as hours or units, for the default earnings for each job.




The following fields display the elements of the labor distribution for each job.

Fund The fund associated with the job.

Organization The organization associated with the job.

Account The account associated with the job.

Program The program associated with the job.

Activity The activity associated with the job.

Location The location associated with the job.

Percent The percent of the salary associated with this labor distribution. The total of all labor distribution records must equal 100%.




Report Sample—Salary Planner Upload Process (NBPSPUP)

NBPSPUP (Release 6.1) Banner University RUN DATE 24-MAR-2004 Salary Planner Upload Process RUN TIME 02:24 PM

Employee Job Upload Chart Of Account: AORGN - 111 Dean Office Arts and Sciences

EFFECTIVE JOB APPT HOURS HOURS ---------SALARY--------- HOURLYID Name DATE FTE PCT /DAY /PAY GROUP TABLE GRADE STEP RATE SALARY

Position Suffix: U40002-02 Assoc Dean EPAF Trans No: 5572U27000066 Sjoegran, Therese 01-JUL-2006 1.0 100.00 8.00 173.33 2005 AD 01 0 5.77 12,000.00 DEFAULT EARNINGS HRS/UNITS FUND ORGN ACCT PROG ACTV LOCN PROJ CTYP PERCENT REG 173.33 1000 111 5120 100 100.00 W *WARNING* Annual Salary is outside the Table/Grade range. W *WARNING* Total FTE for this employee exceeds one as of the eff date.

Position Suffix: U20032-00 Professor Biology EPAF Trans No: 5579U27000030 Hucles, Angela 01-OCT-2006 1.0 100.00 8.00 173.33 2005 FE 05 0 35.36 55,167.21 DEFAULT EARNINGS HRS/UNITS FUND ORGN ACCT PROG ACTV LOCN PROJ CTYP PERCENT REG 173.33 1000 120 5120 100 25.00 1000 121 5120 100 75.00 E *ERROR* Missing one or more entries on PTRCALN for Defer Pay Schedule. W *WARNING* Annual Salary is outside the Table/Grade range.

Position Suffix: UA0005-00 Director Plant Research EPAF Trans No: 5609U27000010 Wildhom, Jack 01-JUL-2006 0.3 100.00 4.00 86.66 2005 AD 01 0 22.21 23,100.00 DEFAULT EARNINGS HRS/UNITS FUND ORGN ACCT PROG ACTV LOCN PROJ CTYP PERCENT 2211 215 5252 620 100.00 E *ERROR* Not a valid active position.

Position Suffix: U10039-00 Professor Electrical Eng EPAF Trans No: 5611U27000038 Bai, Jie 01-JUL-2006 1.0 100.00 8.00 173.33 2005 FA 05 0 28.85 60,000.00 DEFAULT EARNINGS HRS/UNITS FUND ORGN ACCT PROG ACTV LOCN PROJ CTYP PERCENT REG 173.33 1000 155 5120 100 100.00 E *ERROR* New Effective Date must be after 16-AUG-2006.



NBPSPUP (Release 6.1) Banner University RUN DATE 24-MAR-2004 Salary Planner Upload Process RUN TIME 02:24 PM

Employee Job Upload Chart Of Account: A * * * REPORT CONTROL INFORMATION * * *

Parameters have been entered via Job Submission.

Parameter Name Value Source Message____________________ ______________________________ ____________ __________________________________________________________________Parameter Seq No: 88175Report Mode P - Process Updates EnteredProcess Mode B - Both Posn and Jobs Update EnteredBudget Extract ID 2007FINAL Entered (2007 Final)Scenario UPLOAD EnteredFiscal Year 2007 EnteredBudget ID FY07 EnteredBudget Phase POSN EnteredJob Change Reason BUDGE EnteredInclude Wait Records N Entered

Successful Completion.

Posn/Jobs Posn Updated/ Posn/Jobs Posn/Jobs EPAFs EPAFs With Changes EPAFs Created With Warnings With Errors Submitted Waiting Positions: 22 22 N/A 0 Job EPAFs: 87 87 45 6 81 6

Total Positions: 133 Total Jobs: 134Total Organizations: 15

Section 5 Banner Support for Salary Planner - FunctionalError Resolution Matrix


Error Resolution Matrix

New error messages and warning messages have been added to the following forms and process for the Salary Planner Enhancement.

Form/Process Error/Warning Message Resolution

NTRSPEX *ERROR* This data has been saved to this Extract ID and may not be changed.

Extract data exists in the Salary Planner tables and may not be deleted. Use the Salary Planner Upload Process to delete Extract and all Scenarios. Return to NTRSPEX and delete rule record.

*ERROR* New Budget Extract ID already exists, please re-enter.

Extract ID entered for New ID already exists. Enter a new unique Extract ID.

*ERROR* Fiscal Year has not been defined; press LIST for valid codes.

Define Fiscal Year on the NBAFISC form.

*ERROR* Employee Class must be saved before continuing.

Enter at least one employee class on the Employee Classes window.

*ERROR* Date entered is outside of Fiscal Year.

Job Effective Date must fall within, and inclusive of, the begin and end date of the fiscal year defined on the main window.

*WARNING* Budget Extract ID not found, Add assumed.

Acknowledge message and enter extract data. If Extract ID was entered in error, acknowledge message and then Exit the form.

NBPSPEX *ERROR* Budget Extract ID already exists in the working budget table.

Extract ID has already been used for an Initial Extract. Error will print on.lis report and the totals associated with the records in the Salary Planner table for the original Extract will be displayed.



*ERROR* The following Salary Group/Table/Grade/Step combinations are invalid:

Review NBAJOBS and NTRSALA records for valid Salary Group combinations. Make corrections on NBAJOBS as needed.

*ERROR* No matching budgets for extract rule specified.

Review the NTRSPEX form for the Extract Rule based on valid position information for COA, Fiscal Year, Budget ID, Phase and Budget Status.

NBPSPUP Process Parameter Errors:

*ERROR* Report Mode must be R,P, or D.

Enter the correct Report Mode for Report, Process or Delete.

*ERROR* Process Mode must be P, J, or B when Report Mode is R or P.

Enter the correct Process Mode for Position, Job or Both

*ERROR* Invalid Budget Extract ID.

Review Budget Extract IDs in Salary Planner for valid values and enter here.

*ERROR* At least one scenario must be entered.

Enter a valid Scenario.

*ERROR* Single Scenario required when uploading data

Review Scenarios in Salary Planner for valid values and enter here.

*ERROR* Invalid Scenario Review Scenarios in Salary Planner for valid values and enter here

*ERROR* Invalid or Inactive Fiscal Year

Enter a valid Fiscal Year identified on NBAFISC.

*ERROR* Invalid Budget ID/Phase for this fiscal year

Verify Budget ID or Phase identified on NBAPBUD and enter a valid value.

*ERROR* Invalid Job Change Reason Code

Verify Job Change Reason Code and enter here.

NBPSPUP Process Errors:

*ERROR* Salary Planner not setup correctly on NTRINST.

Review NTRINST setup for identification of Approval Categories.




*ERROR* User Needs Exactly One NTRROUT Apply Record for:<lists acat_code>

Process User needs to set up NTRROUT records for each Approval Category identified on NTRINST for Salary Planner processing.

*ERROR* These organizations are unlocked, process aborted.

Review Organizations for locked status in Salary Planner. Rerun upload.

NBPSPUP Position Upload Errors:

*ERROR* Position begins after fiscal year ends

Correct the Begin Date of the position on NBAPBUD.

*ERROR* Position budget must not be negative.

Correct Position Budget in Salary Planner and rerun upload.

*ERROR* Position budget must be less than 999,999,999.99.

Correct Position Budget in Salary Planner and rerun upload.

*ERROR* Position status is not active.

Correct Position status on NBAPBUD

*ERROR* Labor Distribution Amounts do not total Position Budget.

Correct Position Budget records in Salary Planner and rerun upload.

*ERROR* Labor Distribution Percents do not add up to 100.00%.

Correct Position Budget records in Salary Planner and rerun upload.

Note: EPAF errors related to data will be printed on report identifying employee, position/suffix, EPAF Transaction Number and error.





Section 6 Banner Support for the Salary Planner - TechnicalNew Scripts


Section 6 Banner Support for the Salary Planner - Technical

This section documents the database changes made to provide Banner support for the Salary Planner. Database changes have been made to Position Control as well as Human Resources tables.

New Scripts

Note: The following scripts are run as a part of the upgrade process for the release.

NBREHDR1.SQL and NBREHDR2.SQL

NBREHDR1.SQL creates a new table, the Salary Planner Extract Header Table (NBREHDR).

NBREHDR2.SQL adds a primary key to the above table, namely, NBREHDR_SPEX_CODE, NBREHDR_SCENARIO.

NBREHDR3.SQL

NBREHDR3.SQL adds comments for the table and for each column.

NBREJLD1.SQL and NBREJLD2.SQL

NBREJLD1.SQL creates a new table, Extracted Job Labor Distribution Salary Planner Table (NBREJLD).

NBREJLD2.SQL creates a non-unique index NBREJLD_SPEX_INDEX on the NBREJLD table.

NBREJLD3.SQL

NBREJLD3.SQL adds a table comment and column comments.

NBREJOB1.SQL and NBREJOB2.SQL

The script, NBREJOB1.SQL creates a new table, Extracted Job Detail Salary Planner Table (NBREJOB).

Section 6 Banner Support for the Salary Planner - Technical New Scripts


NBREJOB2.SQL creates a unique index, NBREJOB_KEY_INDEX on the NBREJOB table.

NBREJOB3.SQL and NBREJOB4.SQL

NBREJOB3.SQL creates a non-unique index, NBREJOB_ECLS_INDEX on the NBREJOB table.

NBREJOB4.SQL creates a table comment and column comments for the NBREJOB table.

NBREJOB5.SQL

NBREJOB5.SQL creates a non-unique index NBREJOB_ORGN_INDEX on the NBREJOB table.

NBREPLD1.SQL and NBREPLD2.SQL

NBREPLD1.SQL creates a new table, Extracted Position Labor Distribution Salary Planner Table (NBREPLD).

NBREPLD2.SQL creates a non-unique index NBREPLD_SPEX_INDEX on the NBREPLD table.

NBREPLD3.SQL

This script creates a table comment and column comments for the NBREPLD table.

NBREPSA1.SQL and NBREPSA2.SQL

NBREPSA1.SQL creates a new table, Extracted Position Salary Planner Table (NBREPSA).

NBREPSA2.SQL adds a Primary Key, PK_NBREPSA to the NBREPSA table.

NBREPSA3.SQL and NBREPSA4.SQL

NBREPSA3.SQL adds a foreign key FK1_NBREPSA_INV_NBREHDR_KEY to the NBREPSA table.

NBREPSA4.SQL creates a non-unique index, NBREPSA_SPEX_INDEX on the NBREPSA table.



NBREPSA5.SQL

This script creates table comment and column comments for the NBREPSA table.

NBRERRN1.SQL and NBRERRN2.SQL

NBRERRN1.SQL creates a new table, Extracted Job Default Hours Salary Planner Table (NBRERRN).

NBRERRN2.SQL creates a unique index, NBRERRN_KEY_INDEX on the NBRERRN table.

NBRERRN3.SQL and NBRERRN4.SQL

NBRERRN3.SQL creates a table comment and column comments for the NBRERRN table.

NBRERRN4.SQL creates a non-unique index, NBRERRN_ORGN_INDEX on the NBRERRN table.

NBRLOCK1.SQL and NBRLOCK2.SQL

NBRLOCK1.SQL creates a new table, Salary Planner Organization Lock Table (NBRLOCK).

NBRLOCK2.SQL creates a unique index, NBRLOCK_KEY_INDEX on the NBRLOCK table.

NBRLOCK3.SQL

This script creates a table comment and column comments for the NBRLOCK table.

NBRPTOT1.SQL

NBRPTOT1.SQL creates a non-unique index, NBRPTOT_KEY3_INDEX on the NBRPTOT table.

NBRSALC1.SQL and NBRSALC2.SQL

NBRSALC1.SQL creates a new table, Salary Planner Salary Change Table (NBRSALC).

NBRSALC2.SQL creates a unique index, NBRSALC_KEY_INDEX on the NBRSALC table.

NBRSALC3.SQL

This script creates a table comment and column comments for the NBRSALC table.



NBRSPLC1.SQL and NBRSPLC2.SQL

NBRSPLC1.SQL creates a new table, Salary Planner Organization Lock Collector Table (NBRSPLC).

NBRSPLC2.SQL adds a Primary key, PK_NBRSPLC to the NBRSPLC table.

NBRSPLC3.SQL

This script creates a table comment and column comments for the NBRSPLC table.

NBTEMPF1.SQL and NBTEMPF2.SQL

NBTEMPF1.SQL creates a new temporary table, Salary Planner Extracted Employee Temporary Table (NBTEMPF).

NBTEMP2.SQL adds a Primary Key, PK_NBTEMPF to the NBTEMPF table.

NBTEMPF3.SQL and NBTEMPF4.SQL

NBTEMPF3.SQL adds an Index, NBTEMPF_SPEX_INDEX on the NBTEMPF table.

NBTEMPF4.SQL creates a table comment and column comments for the NBTEMPF table.

NBTFPRM1.SQL and NBTFPRM2.SQL

NBTFPRM1.SQL creates a new table, Salary Planner Filter Parameter Table (NBTFPRM)

NBTFPRM2.SQL adds a Primary Key, PK_NBTFPRM to the NBTFPRM table.

NBTFPRM3.SQL

This script creates a table comment and column comments for the NBTFPRM table.

NBTJERR1.SQL and NBTJERR2.SQL

NBTJERR1.SQL creates a new table, Salary Planner Upload Jobs Error Temporary Table (NBTJERR).

NBTJERR2.SQL adds a Primary Key, PK_NBTJERR to the new table, NBTJERR.



NBTJERR3.SQL

This script creates a table comment and corresponding column comments for the NBTJERR table.

NBTJOBF1.SQL and NBTJOBF2.SQL

NBTJOBF1.SQL creates a new table, Salary Planner Employee's Jobs Filter Temporary Table (NBTJOBF).

NBTJOBF2.SQL adds a Primary Key, PK_NBTJOBF to the NBTJOBF table.

NBTJOBF3.SQL and NBTJOBF4.SQL

NBTJOBF3.SQL creates an Index, NBTJOBF_SPEX_INDEX on the new table, NBTJOBF.

NBTJOBF4.SQL creates a table comment and corresponding column comments for the NBTJOBF table.

NBTORSF1.SQL and NBTORSF2.SQL

NBTORSF1.SQL creates a new table, Salary Planner Organization Summary Filter Temporary Table (NBTORSF).

NBTORSF2.SQL adds a Primary Key, PK_NBTORSF to the NBTORSF table.

NBTORSF3.SQL

This script creates a table comment and corresponding column comments for the NBTORSF table.

NBTPERR1.SQL and NBTPERR2.SQL

NBTPERR1.SQL creates a new temporary table, Salary Planner Upload Position Error Temporary Table (NBTPERR).

NBTPERR2.SQL adds a Primary Key, PK_NBTPERR to the NBTPERR table.

NBTPERR3.SQL

This script creates a table comment and corresponding column comments for the NBTPERR table.



NBTPOSF1.SQL and NBTPOSF2.SQL

NBTPOSF1.SQL creates a new table, Salary Planner Position Filter Temporary Table (NBTPOSF).

NBTPOSF2.SQL adds a Primary Key, PK_NBTPOSF to the NBTPOSF table.

NBTPOSF3.SQL and NBTPOSF4.SQL

NBTPOSF3.SQL creates an Index, NBTPOSF_SPEX_INDEX on the NBTPOSF table.

NBTPOSF4.SQL creates a table comment and corresponding column comments for the NBTPOSF table.

NSRSPSC1.SQL and NSRSPSC2.SQL

NSRSPSC1.SQL adds a new table, Salary Planner Security Table (NSRSPSC).

NSRSPSC2.SQL creates a unique Index, NSRSPSC_KEY_INDEX on the NSRSPSC table.

NSRSPSC3.SQL

This script creates a table comment and corresponding column comments for the NSRSPSC table.

NTRINST5.SQL and NTRINST6.SQL

NTRINST5.SQL adds the following columns, NTRINST_WEB_ALLOW_ALLJOBS_IND, NTRINST_FLAT_AMT_PRORATE_TYPE, NTRINST_JOB_INFO_PRORATE_TYPE, NTRINST_ACAT_CODE_JOB_SALARY, NTRINST_ACAT_CODE_DEFAULT_HRS, NTRINST_ACAT_CODE_JOB_LD, NTRINST_ACAT_CODE_JOB_COMBINED to the NTRINST table.

NTRINST6.SQL updates the following columns with seed data, NTRINST_WEB_ALLOW_ALLJOBS_IND, NTRINST_FLAT_AMT_PRORATE_TYPE, NTRINST_JOB_INFO_PRORATE_TYPE.


NTRINST7.SQL sets the following columns as NOT NULL columns: NTRINST_WEB_ALLOW_ALLJOBS_IND, NTRINST_FLAT_AMT_PRORATE_TYPE, NTRINST_JOB_INFO_PRORATE_TYPE.

NTRINST8.SQL adds comments for all new columns of NTRINST.




NTRINST9.SQL adds NTRINST_SP_ORGN_SECURITY_IND as a new column to the NTRINST table.

NTRINST10.SQL updates the NTRINST_SP_ORGN_SECURITY_IND column with seed data.


NTRINST11.SQL changes the NTRINST_SP_ORGN_SECURITY_IND column to a NOT NULL column.

NTRINST12.SQL adds a comment to the NTRINST_SP_ORGN_SECURITY_IND column.

NTRSPBU1.SQL and NTRSPBU2.SQL

NTRSPBU1.SQL adds a new table, Salary Planner Extract Bargaining Unit Rule Table (NTRSPBU).

NTRSPBU2.SQL adds a Primary Key, PK_NTRSPBU to the new table, NTRSPBU.

NTRSPBU3.SQL and NTRSPBU4.SQL

NTRSPBU3.SQL adds a Foreign Key, FK1_NTRSPBU_INV_NTRSPEX_CODE to the NTRSPBU table.

NTRSPBU4.SQL creates a table comment and corresponding column comments for the NBTPOSF table.

NTRSPEC1.SQL and NTRSPEC2.SQL

NTRSPEC1.SQL adds a new table, Salary Planner Extract Employee Class Rule Table (NTRSPEC)

NTRSPEC2.SQL adds a Primary Key, PK_NTRSPEC, to the NTRSPEC table.

NTRSPEC3.SQL and NTRSPEC4.SQL

NTRSPEC3.SQL adds a Foreign Key, FK1_NTRSPEC_INV_NTRSPEX_CODE to the NTRSPEC table.

NTRSPEC4.SQL creates a table comment and corresponding column comments for the NTRSPEC table.



NTRSPEX1.SQL and NTRSPEX2.SQL

NTRSPEX1.SQL adds a new table, Salary Planner Extract Rule Table (NTRSPEX).

NTRSPEX2.SQL adds a Primary Key, PK_NTRSPEX, to the NTRSPEX table.

NTRSPEX3.SQL

This script creates a table comment and corresponding column comments for the NTRSPEX table.

NTRSPPR1.SQL and NTRSPPR2.SQL

NTRSPPR1.SQL adds a new table, Salary Planner Extract Budget Profile Rule Table (NTRSPPR)

NTRSPPR2.SQL adds a Primary Key, PK_NTRSPPR to the NTRSPPR table.

NTRSPPR3.SQL and NTRSPPR4.SQL

NTRSPPR3.SQL adds a Foreign Key, FK1_NTRSPPR_INV_NTRSPEX_CODE to the NTRSPPR table.

NTRSPPR4.SQL adds a second Foreign Key, FK2_NTRSPPR_INV_NTVBPRO_CODE to the NTRSPPR table.

NTRSPPR5.SQL

This script creates a table comment and corresponding column comments for the NTRSPPR table.

NTVBPRO1.SQL and NTVBPRO2.SQL

NTVBPRO1.SQL adds a new table, Budget Profile Validation Table (NTVBPRO)

NTVBPRO2.SQL adds a Primary Key, PK_NTVBPRO, to the NTVBPRO table.

NTVBPRO3.SQL

This script creates a table comment and corresponding column comments for the NTVBPRO table.

Section 6 Banner Support for the Salary Planner - TechnicalChanged Scripts


Changed Scripts


NBBPOSN1.SQL and NBBPOSN2.SQL

NBBPOSN1.SQL adds a new column, NBBPOSN_BPRO_CODE to the table.

NBBPOSN2.SQL creates a non-unique index, NBBPOSN_BPRO_INDEX.

NBBPOSN3.SQL

NBBPOSN3.SQL adds a comment for the new column listed above.

PTRJCRE1.SQL and PTRJCRE2.SQL

PTRJCRE1.SQL adds two new columns, PTRJCRE_WEB_DISPLAY_PRIORITY, and PTRJCRE_WEB_INCL_TOTALS_IND to the PTRJCRE table.

PTRJCRE2.SQL updates the PTRJCRE table with seed data for the PTRJCRE_WEB_INCL_TOTALS_IND column.

PTRJCRE3.SQL and PTRJCRE4.SQL

PTRJCRE3.SQL sets the PTRJCRE_WEB_INCL_TOTALS_IND column as a NOT NULL column.

PTRJCRE4.SQL creates a unique index, PTRJCRE_KEY_INDEX on the PTRJCRE table.

PTRJCRE5.SQL

This script adds comments for the two new columns of PTRJCRE, PTRJCRE_WEB_DISPLAY_PRIORITY, and PTRJCRE_WEB_INCL_TOTALS_IND.

PTRUSER1.SQL and PTRUSER2.SQL

PTRUSER1.SQL adds a new column, PTRUSER_MASTER_SP_ORGN_IND to the PTRUSER table.

PTRUSER2.SQL updates the PTRUSER_MASTER_SP_ORGN_IND column with seed data.

Section 6 Banner Support for the Salary Planner - Technical New Tables


PTRUSER3.SQL and PTRUSER4.SQL

PTRUSER3.SQL sets the PTRUSER_MASTER_SP_ORGN_IND column as a NOT NULL column.

PTRUSER4.SQL adds a comment to the PTRUSER_MASTER_SP_ORGN_IND column.

PTVORGN1.SQL and PTVORGN2.SQL

PTVORGN1.SQL adds a new column, PTVORGN_ORGN_CODE_PRED, to the PTVORGN table.

PTVORGN2.SQL creates a non-unique index, PTVORGN_ORGN_CODE_INDEX on the PTVORGN table.

PTVORGN3.SQL

This script adds a comment to the PTVORGN_ORGN_CODE_PRED column.

New Tables

Salary Planner Extract Header Table (NBREHDR)

Database Column Null? Datatype

NBREHDR_SPEX_CODE NOT NULL VARCHAR2(12)

NBREHDR_SCENARIO NOT NULL VARCHAR2(30)

NBREHDR_FISC_CODE NOT NULL VARCHAR2(4)

NBREHDR_PTOT_STATUS NOT NULL VARCHAR2(1)

NBREHDR_JOBS_EFFECTIVE_DATE NOT NULL DATE

NBREHDR_LOCK_IND NOT NULL VARCHAR2(1)

NBREHDR_USER_ID NOT NULL VARCHAR2(30)

NBREHDR_ACTIVITY_DATE NOT NULL DATE

NBREHDR_COAS_CODE VARCHAR2(1)

NBREHDR_OBUD_CODE VARCHAR2(6)

NBREHDR_OBPH_CODE VARCHAR2(6)

Section 6 Banner Support for the Salary Planner - TechnicalNew Tables


Extracted Job Labor Distribution Salary Planner Table (NBREJLD)


NBREJLD_SPEX_CODE NOT NULL VARCHAR2(12)

NBREJLD_SCENARIO NOT NULL VARCHAR2(30)

NBREJLD_PIDM NOT NULL NUMBER(8)

NBREJLD_POSN NOT NULL VARCHAR2(6)

NBREJLD_SUFF NOT NULL VARCHAR2(2)

NBREJLD_EFFECTIVE_DATE NOT NULL DATE

NBREJLD_ORGN_CODE_POSN NOT NULL VARCHAR2(6)

NBREJLD_PERCENT_PROPOSED NOT NULL NUMBER(5,2)

NBREJLD_RECORD_STATUS NOT NULL VARCHAR2(1)

NBREJLD_USER_ID NOT NULL VARCHAR2(30)

NBREJLD_ACTIVITY_DATE NOT NULL DATE

NBREJLD_COAS_CODE VARCHAR2(1)

NBREJLD_ACCI_CODE VARCHAR2(6)

NBREJLD_FUND_CODE VARCHAR2(6)

NBREJLD_ORGN_CODE VARCHAR2(6)

NBREJLD_ACCT_CODE VARCHAR2(6)

NBREJLD_PROG_CODE VARCHAR2(6)

NBREJLD_ACTV_CODE VARCHAR2(6)

NBREJLD_LOCN_CODE VARCHAR2(6)

NBREJLD_PROJ_CODE VARCHAR2(8)

NBREJLD_CTYP_CODE VARCHAR2(2)

NBREJLD_ACCT_CODE_EXTERNAL VARCHAR2(60)

NBREJLD_TRANSACTION_NO NUMBER(15)



Extracted Job Detail Salary Planner Table (NBREJOB)


NBREJOB_SPEX_CODE NOT NULL VARCHAR2(12)

NBREJOB_SCENARIO NOT NULL VARCHAR2(30)

NBREJOB_PIDM NOT NULL NUMBER(8)

NBREJOB_POSN NOT NULL VARCHAR2(6)

NBREJOB_SUFF NOT NULL VARCHAR2(2)

NBREJOB_EFFECTIVE_DATE NOT NULL DATE

NBREJOB_EFF_DATE_PROPOSED NOT NULL DATE

NBREJOB_PERS_CHG_DATE NOT NULL DATE

NBREJOB_ORGN_CODE_POSN NOT NULL VARCHAR2(6)

NBREJOB_ECLS_CODE_POSN NOT NULL VARCHAR2(2)

NBREJOB_ECLS_CODE NOT NULL VARCHAR2(2)

NBREJOB_ANN_SALARY NOT NULL NUMBER(11,2)

NBREJOB_ANN_SALARY_PROPOSED NOT NULL NUMBER(11,2)

NBREJOB_APPT_PCT NOT NULL NUMBER(5,2)

NBREJOB_APPT_PCT_PROPOSED NOT NULL NUMBER(5,2)

NBREJOB_HRS_DAY NOT NULL NUMBER(6,2)

NBREJOB_HRS_DAY_PROPOSED NOT NULL NUMBER(6,2)

NBREJOB_HRS_PAY NOT NULL NUMBER(6,2)

NBREJOB_HRS_PAY_PROPOSED NOT NULL NUMBER(6,2)

NBREJOB_SGRP_CODE NOT NULL VARCHAR2(6)

NBREJOB_SGRP_CODE_PROPOSED NOT NULL VARCHAR2(6)

NBREJOB_BUDGET_FACTOR NOT NULL NUMBER(5,2)

NBREJOB_EST_FY_BUDGET NOT NULL NUMBER(11,2)

NBREJOB_EXCL_TOTALS_IND NOT NULL VARCHAR2(1)

NBREJOB_HIDE_IND NOT NULL VARCHAR2(1)

NBREJOB_EXTRACT_STATUS NOT NULL VARCHAR2(1)



Extracted Position Labor Distribution Salary Planner Table (NBREPLD)

NBREJOB_RECORD_STATUS NOT NULL VARCHAR2(1)

NBREJOB_USER_ID NOT NULL VARCHAR2(30)

NBREJOB_ACTIVITY_DATE NOT NULL DATE

NBREJOB_DESC VARCHAR2(30)

NBREJOB_DESC_PROPOSED VARCHAR2(30)

NBREJOB_REG_RATE NUMBER(11,6)

NBREJOB_REG_RATE_PROPOSED NUMBER(11,6)

NBREJOB_FTE NUMBER(6,3)

NBREJOB_FTE_PROPOSED NUMBER(6,3)

NBREJOB_SAL_TABLE VARCHAR2(2)

NBREJOB_SAL_TABLE_PROPOSED VARCHAR2(2)

NBREJOB_SAL_GRADE VARCHAR2(5)

NBREJOB_SAL_GRADE_PROPOSED VARCHAR2(5)

NBREJOB_SAL_STEP NUMBER(3)

NBREJOB_SAL_STEP_PROPOSED NUMBER(3)

NBREJOB_RANK_CODE VARCHAR2(2)

NBREJOB_COMMENTS VARCHAR2(13

NBREJOB_FACTOR NUMBER(4)

NBREJOB_PAYS NUMBER(4)

NBREJOB_EMPR_CODE VARCHAR2(4)

NBREJOB_ROUNDING_METHOD NUMBER(6,2)

NBREJOB_TRANSACTION_NO NUMBER(15)


NBREPLD_SPEX_CODE NOT NULL VARCHAR2(12)

NBREPLD_SCENARIO NOT NULL VARCHAR2(30)




Extracted Position Salary Planner Table (NBREPSA)

NBREPLD_POSN NOT NULL VARCHAR2(6)

NBREPLD_ORGN_CODE_POSN NOT NULL VARCHAR2(6)

NBREPLD_PERCENT_PROPOSED NOT NULL NUMBER(5,2)

NBREPLD_RECORD_STATUS NOT NULL VARCHAR2(1)

NBREPLD_USER_ID NOT NULL VARCHAR2(30)

NBREPLD_ACTIVITY_DATE NOT NULL DATE

NBREPLD_BUDGET_PROPOSED NUMBER(11,2)

NBREPLD_COAS_CODE VARCHAR2(1)

NBREPLD_ACCI_CODE VARCHAR2(6)

NBREPLD_FUND_CODE VARCHAR2(6)

NBREPLD_ORGN_CODE VARCHAR2(6)

NBREPLD_ACCT_CODE VARCHAR2(6)

NBREPLD_PROG_CODE VARCHAR2(6)

NBREPLD_ACTV_CODE VARCHAR2(6)

NBREPLD_LOCN_CODE VARCHAR2(6)

NBREPLD_PROJ_CODE VARCHAR2(8)

NBREPLD_CTYP_CODE VARCHAR2(2)

NBREPLD_ACCT_CODE_EXTERNAL VARCHAR2(60)


NBREPSA_SPEX_CODE NOT NULL VARCHAR2(12)

NBREPSA_SCENARIO NOT NULL VARCHAR2(30)

NBREPSA_POSN NOT NULL VARCHAR2(6)

NBREPSA_PTOT_EFFECTIVE_DATE NOT NULL DATE

NBREPSA_ORGN_CODE NOT NULL VARCHAR2(6)

NBREPSA_ECLS_CODE_POSN NOT NULL VARCHAR2(2)




Extracted Job Default Hours Salary Planner Table (NBRERRN)

NBREPSA_POSN_TYPE NOT NULL VARCHAR2(1)

NBREPSA_FTE NOT NULL NUMBER(7,4)

NBREPSA_FTE_PROPOSED NOT NULL NUMBER(7,4)

NBREPSA_APPT_PCT NOT NULL NUMBER(5,2)

NBREPSA_APPT_PCT_PROPOSED NOT NULL NUMBER(5,2)

NBREPSA_EXCL_TOTALS_IND NOT NULL VARCHAR2(1)

NBREPSA_HIDE_IND NOT NULL VARCHAR2(1)

NBREPSA_EXTRACT_STATUS NOT NULL VARCHAR2(1)

NBREPSA_RECORD_STATUS NOT NULL VARCHAR2(1)

NBREPSA_USER_ID NOT NULL VARCHAR2(30)

NBREPSA_ACTIVITY_DATE NOT NULL DATE

NBREPSA_BARG_CODE VARCHAR2(2)

NBREPSA_BUDGET NUMBER(11,2)

NBREPSA_BUDGET_PROPOSED NUMBER(11,2)

NBREPSA_CHANGE_PERCENT NUMBER(11,2)

NBREPSA_CHANGE_AMOUNT NUMBER(11,2)

NBREPSA_COMMENTS VARCHAR2(1300)


NBRERRN_SPEX_CODE NOT NULL VARCHAR2(12)

NBRERRN_SCENARIO NOT NULL VARCHAR2(30)

NBRERRN_PIDM NOT NULL NUMBER(8)

NBRERRN_POSN NOT NULL VARCHAR2(6)

NBRERRN_SUFF NOT NULL VARCHAR2(2)

NBRERRN_EFFECTIVE_DATE NOT NULL DATE

NBRERRN_EFF_DATE_PROPOSED NOT NULL DATE




Salary Planner Organization Lock Table (NBRLOCK)

Salary Planner Salary Change Table (NBRSALC)

NBRERRN_EARN_CODE NOT NULL VARCHAR2(3)

NBRERRN_ORGN_CODE_POSN NOT NULL VARCHAR2(6)

NBRERRN_SHIFT NOT NULL VARCHAR2(1)

NBRERRN_RECORD_STATUS NOT NULL VARCHAR2(1)

NBRERRN_USER_ID NOT NULL VARCHAR2(30)

NBRERRN_ACTIVITY_DATE NOT NULL DATE

NBRERRN_HRS NUMBER(6,2)

NBRERRN_HRS_PROPOSED NUMBER(6,2)

NBRERRN_CANCEL_DATE DATE

NBRERRN_SPECIAL_RATE NUMBER(12,6)

NBRERRN_TRANSACTION_NO NUMBER(15)


NBRLOCK_SPEX_CODE NOT NULL VARCHAR2(12)

NBRLOCK_SCENARIO NOT NULL VARCHAR2(30)

NBRLOCK_ORGN_CODE NOT NULL VARCHAR2(6)

NBRLOCK_LOCK_IND NOT NULL VARCHAR2(1)

NBRLOCK_USER_ID NOT NULL VARCHAR2(30)

NBRLOCK_ACTIVITY_DATE NOT NULL DATE


NBRSALC_SPEX_CODE NOT NULL VARCHAR2(12)

NBRSALC_SCENARIO NOT NULL VARCHAR2(30)

NBRSALC_PIDM NOT NULL NUMBER(8)




Salary Planner Organization Lock Collector Table (NBRSPLC)

NBRSALC_POSN NOT NULL VARCHAR2(6)

NBRSALC_SUFF NOT NULL VARCHAR2(2)

NBRSALC_EFFECTIVE_DATE NOT NULL DATE

NBRSALC_JCRE_CODE NOT NULL VARCHAR2(5)

NBRSALC_USER_ID NOT NULL VARCHAR2(30)

NBRSALC_ACTIVITY_DATE NOT NULL DATE

NBRSALC_CHANGE_PERCENT NUMBER(11,2)

NBRSALC_CHANGE_AMOUNT NUMBER(15,6)


NBRSPLC_PIDM NOT NULL NUMBER(8)

NBRSPLC_SPEX_CODE NOT NULL VARCHAR2(12)

NBRSPLC_SCENARIO NOT NULL VARCHAR2(30)

NBRSPLC_ORGN_CODE NOT NULL VARCHAR2(6)

NBRSPLC_ORGN_LOCK_STATUS NOT NULL VARCHAR2(1)

NBRSPLC_ORGN_LOCK_TYPE NOT NULL VARCHAR2(1)

NBRSPLC_ORGN_HIER_STATUS NOT NULL VARCHAR2(1)

NBRSPLC_ORGN_CHNG_STATUS NOT NULL VARCHAR2(1)

NBRSPLC_USER_ID NOT NULL VARCHAR2(30)

NBRSPLC_ACTIVITY_DATE NOT NULL DATE

NBRSPLC_ORGN_CODE_PRED VARCHAR2(6)

NBRSPLC_ORGN_TITLE VARCHAR2(35)




Salary Planner Extracted Employee Temporary Table (NBTEMPF)

Salary Planner Filter Parameter Table (NBTFPRM)

Salary Planner Upload Jobs Error Temporary Table (NBTJERR)


NBTEMPF_PIDM NOT NULL NUMBER(8)

NBTEMPF_SPEX_CODE NOT NULL VARCHAR2(12)

NBTEMPF_SCENARIO NOT NULL VARCHAR2(30)

NBTEMPF_SEQ_NO NOT NULL NUMBER(12)

NBTEMPF_EMPLOYEE_PIDM NOT NULL NUMBER(8)

NBTEMPF_ORGN_CODE NOT NULL VARCHAR2(6)

NBTEMPF_USER_ID NOT NULL VARCHAR2(30)

NBTEMPF_ACTIVITY_DATE NOT NULL DATE


NBTFPRM_PIDM NOT NULL VARCHAR2(8)

NBTFPRM_SPEX_CODE NOT NULL VARCHAR2(12)

NBTFPRM_SCENARIO NOT NULL VARCHAR2(30)

NBTFPRM_LABEL NOT NULL VARCHAR2(30)

NBTFPRM_VALUE NOT NULL VARCHAR2(30)

NBTFPRM_USER_ID NOT NULL VARCHAR2(30)

NBTFPRM_ACTIVITY_DATE NOT NULL DATE


NBTJERR_SESSION_ID NOT NULL VARCHAR2(30)

NBTJERR_PIDM NOT NULL NUMBER(8)

NBTJERR_POSN NOT NULL VARCHAR2(6)



Salary Planner Employee's Jobs Filter Temporary Table (NBTJOBF)

Salary Planner Organization Summary Filter Temporary Table (NBTORSF)

NBTJERR_SUFF NOT NULL VARCHAR2(2)

NBTJERR_EFFECTIVE_DATE NOT NULL DATE

NBTJERR_SEQ_NO NOT NULL NUMBER(6)

NBTJERR_MSG_TYPE NOT NULL VARCHAR2(1)

NBTJERR_ERROR_MSG NOT NULL VARCHAR2(80)

NBTJERR_USER_ID NOT NULL VARCHAR2(30)

NBTJERR_ACTIVITY_DATE NOT NULL DATE


NBTJOBF_PIDM NOT NULL NUMBER(8)

NBTJOBF_SPEX_CODE NOT NULL VARCHAR2(12)

NBTJOBF_SCENARIO NOT NULL VARCHAR2(30)

NBTJOBF_EMPF_SEQ_NO NOT NULL NUMBER(12)

NBTJOBF_SEQ_NO NOT NULL NUMBER(12)

NBTJOFB_EMPLOYEE_PIDM NOT NULL NUMBER(8)

NBTJOBF_POSN NOT NULL VARCHAR2(6)

NBTJOBF_SUFF NOT NULL VARCHAR2(2)

NBTJOBF_EFFECTIVE_DATE NOT NULL DATE

NBTJOBF_USER_ID NOT NULL VARCHAR2(30)

NBTJOBF_ACTIVITY_DATE NOT NULL DATE


NBTORSF_PIDM NOT NULL NUMBER(8)

NBTORSF_SPEX_CODE NOT NULL VARCHAR2(12)




Salary Planner Upload Position Error Temporary Table (NBTPERR)

Salary Planner Position Filter Temporary Table (NBTPOSF)

NBTORSF_SCENARIO NOT NULL VARCHAR2(30)

NBTORSF_ORGN_CODE NOT NULL VARCHAR2(6)

NBTORSF_USER_ID NOT NULL VARCHAR2(30)

NBTORSF_ACTIVITY_DATE NOT NULL DATE


NBTPERR_SESSION_ID NOT NULL VARCHAR2(30)

NBTPERR_POSN NOT NULL VARCHAR2(6)

NBTPERR_SEQ_NO NOT NULL NUMBER(6)

NBTPERR_MSG_TYPE NOT NULL VARCHAR2(1)

NBTPERR_ERROR_MSG NOT NULL VARCHAR2(80)

NBTPERR_USER_ID NOT NULL VARCHAR2(30)

NBTPERR_ACTIVITY_DATE NOT NULL DATE


NBTPOSF_PIDM NOT NULL NUMBER(8)

NBTPOSF_SPEX_CODE NOT NULL VARCHAR2(12)

NBTPOSF_SCENARIO NOT NULL VARCHAR2(30)

NBTPOSF_SEQ_NO NOT NULL NUMBER(12)

NBTPOSF_POSN NOT NULL VARCHAR2(6)

NBTPOSF_ORGN_CODE NOT NULL VARCHAR2(6)

NBTPOSF_PTOT_EFFECTIVE_DATE NOT NULL DATE

NBTPOSF_USER_ID NOT NULL VARCHAR2(30)

NBTPOSF_ACTIVITY_DATE NOT NULL DATE




Salary Planner Security Table (NSRSPSC)

Salary Planner Extract Bargaining Unit Rule Table (NTRSPBU)

Salary Planner Extract Employee Class Rule Table (NTRSPEC)


NSRSPSC_USER_CODE NOT NULL VARCHAR2(30)

NSRSPSC_ORGN_CODE NOT NULL VARCHAR2(6)

NSRSPSC_ACCESS_IND NOT NULL VARCHAR2(1)

NSRSPSC_USER_ID NOT NULL VARCHAR2(30)

NSRSPSC_ACTIVITY_DATE NOT NULL DATE

NSRSPSC_COAS_CODE VARCHAR2(1)


NTRSPBU_SPEX_CODE NOT NULL VARCHAR2(12)

NTRSPBU_BARG_CODE NOT NULL VARCHAR2(2)

NTRSPBU_USER_ID NOT NULL VARCHAR2(30)

NTRSPBU_ACTIVITY_DATE NOT NULL DATE


NTRSPEC_SPEX_CODE NOT NULL VARCHAR2(2)

NTRSPEC_ECLS_CODE NOT NULL VARCHAR2(2)

NTRSPEC_BUDGET_FACTOR NOT NULL NUMBER(5,2)

NTRSPEC_JOBS_EFFECTIVE_DATE NOT NULL DATE

NTRSPEC_JOBS_PERS_CHG_DATE NOT NULL DATE

NTRSPEC_USER_ID NOT NULL VARCHAR2(30)

NTRSPEC_ACTIVITY_DATE NOT NULL DATE



Salary Planner Extract Rule Table (NTRSPEX)

Salary Planner Extract Budget Profile Rule Table (NTRSPPR)

Budget Profile Validation Table (NTVBPRO)


NTRSPEX_CODE NOT NULL VARCHAR2(12)

NTRSPEX_DESC NOT NULL VARCHAR2(30)

NTRSPEX_FISC_CODE NOT NULL VARCHAR2(4)

NTRSPEX_PTOT_STATUS NOT NULL VARCHAR2(1)

NTRSPEX_INCL_SEC_JOB_IND NOT NULL VARCHAR2(1)

NTRSPEX_INCL_OVERLOAD_JOB_IND NOT NULL VARCHAR2(1)

NTRSPEX_INCL_NO_BARG_IND NOT NULL VARCHAR2(1)

NTRSPEX_INCL_NO_BPRO_IND NOT NULL VARCHAR2(1)

NTRSPEX_USER_ID NOT NULL VARCHAR2(30)

NTRSPEX_ACTIVITY_DATE NOT NULL DATE

NTRSPEX_COAS_CODE VARCHAR2(1)

NTRSPEX_OBUD_CODE VARCHAR2(6)

NTRSPEX_OBPH_CODE VARCHAR2(6)


NTRSPPR_SPEX_CODE NOT NULL VARCHAR2(12)

NTRSPPR_BPRO_CODE NOT NULL VARCHAR2(6)

NTRSPPR_USER_ID NOT NULL VARCHAR2(30)

NTRSPPR_ACTIVITY_DATE NOT NULL DATE


NTVBPRO_CODE NOT NULL VARCHAR2(6)

NTVBPRO_DESC NOT NULL VARCHAR2(30)

Section 6 Banner Support for the Salary Planner - TechnicalChanged Tables


Changed Tables

Position Base Table (NBBPOSN)

Position Control Installation Rule Table (NTRINST)

Job Change Reason Table (PTRJCRE)

NTVBPRO_USER_ID NOT NULL VARCHAR2(30)

NTVBPRO_ACTIVITY_DATE NOT NULL DATE



NBBPOSN_BPRO_CODE VARCHAR2(6)


NTRINST_WEB_ALLOW_ALLJOBS_IND NOT NULL VARCHAR2(1)

NTRINST_FLAT_AMT_PRORATE_TYPE NOT NULL VARCHAR2(1)

NTRINST_JOB_INFO_PRORATE_TYPE NOT NULL VARCHAR2(1)

NTRINST_ACAT_CODE_JOB_SALARY VARCHAR2(6)

NTRINST_ACAT_CODE_DEFAULT_HRS VARCHAR2(6)

NTRINST_ACAT_CODE_JOB_LD VARCHAR2(6)

NTRINST_ACAT_CODE_JOB_COMBINED VARCHAR2(6)

NTRINST_SP_ORGN_SECURITY_IND NOT NULL VARCHAR2(1)


PTRJCRE_WEB_DISPLAY_PRIORITY NUMBER(2)

PTRJCRE_WEB_INCL_TOTALS_IND NOT_NULL VARCHAR2(1)

Section 6 Banner Support for the Salary Planner - Technical New Install Script


User Code Rule Table (PTRUSER)

New Install Script

Note: This script will not be run as a part of the upgrade.

NSPACAT.SQL

Run this script to create Approval Types and assign Approval categories. This script has been developed specifically for use in the Salary Planner Upload process (NBPSPUP).

Note: SCT delivers this utility script to generate seed data in a given format. The order of the Approval Types in the Combined Approval Category must remain unaltered. This script will not be run as a part of the upgrade.

Each name can be up to six characters long. These named categories and types will be visible on the Electronic Approval Category Code Validation Form (NTVACAT) and Electronic Approval Types Rules (NTRAPTY). The appropriate blocks and fields for each Approval Type are also set up as a part of this script.

Upon successful completion of this script, the Salary Planner Upload Process (NBPSPUP) can be used.

This script sets up three approval types for use in the creation of Job EPAFs, namely:

1. Salary Information

2. Default Hours

3. Labor Distributions

Four approval categories are also created for Job EPAFs, namely:

1. Salary Information

2. Default Hours

3. Labor Distributions

4. Combined Job Information


PTRUSER_MASTER_SP_ORGN_IND NOT NULL VARCHAR2(1)

Section 6 Banner Support for the Salary Planner - TechnicalNew Packages


Each approval category is associated with an Approval Type:

The Approval Types have been created in Banner along with the Approval Categories. However, your institution may specify appropriate names as required when running the script.

New Packages

The following new packages have been added as a result of this enhancement.

NBKBUDG.SQL andNBKBUD1.SQL

This package contains common functions and procedures used in the Salary Planner Web pages, Salary Planner Extract process (NBPSPEX), and Salary Planner Upload process (NBPSPUP).

NOKEPAF.SQL and NOKEPA1.SQL

This package has been created to support EPAF edits and provide logic for EPAF transactions in the Salary Planner.

NBTEPSA0.SQL

The NBTEPSA0.SQL package contains a new trigger, NT_NBREPSA_UPDATE_NBREPLD for the Salary Planner Extracted Position Table (NBREPSA), to update its Labor Distribution in the NBREPLD table when changes are made to the proposed Position Budgets.

Changed Packages

The following packages have been modified in support of the Salary Planner application.

Approval Category Approval Type

Salary SalaryDefault Hrs Default HrsLabor Dist Labor DistCombined Includes Salary, Default Hours and Labor Distribution

Section 6 Banner Support for the Salary Planner - Technical Changed Packages


NOKSECR.SQL and NOKSEC1.SQL

These security packages have been modified to add a new organization security check for the Salary Planner.

NOKFLIB.SQL and NOKFLI1.SQL

This security package has been modified to recognize the organization hierarchy in PTVORGN when Banner Finance is not installed. New logic has been added that checks for the preceding and succeeding organization codes, similar to the functionality found in FOMUSOR

NBKD2S1.SQL

The p_build_ptot_select procedure has been modified to include the Budget Profile code and description for the Spreadsheet Budgeting download.

NOKP3LB.SQL and NOKP3L1.SQL

This package has been modified to include two new procedures, p_include_all_ecls and p_include_all_barg which populate all Employee Classes and Bargaining Units defined on the PTRECLS and PTVBARG forms, into the NTRSPEX form.

PSFECLS.SQL

This package has been modified to reduce the number of hits to the database by accessing the PTRINST table once.

NOKPVAL.SQL

This package has been modified to add two new edits to validate the Extract ID and Salary Group code parameters for the Salary Planner extract and upload processes, NBPSPEX and NBPSPUP, respectively.

Section 7 Support for 1099-R Changes - FunctionalOverview


Section 7 Support for 1099-R Changes - Functional

Overview

Note: This functionality was originally delivered with Human Resources Release 6.0.5.

For the year 2003, the 1099-R Form (PXA1099), 1099-R Load Process (PXP1099), and the 1099-R Print Report (PXR1099) have been modified to display a new field, Payer Account Number for the payee.

For your convenience, the 1099-R processing inclusive of the new modifications for 2003 have been included in this section. For more details refer to page 137.

Changed Form

The following Human Resources form has been modified for this enhancement:

Application Form

1099-R Form (PXA1099)

A new field, Payer Account Number has been added to the Main block of the 1099-R form. This field captures the payer’s account number for each employee.

PXA1099 1099-R Form

Section 7 Support for 1099-R Changes - Functional Changed Report and Process


Alternatively, if the 1099-R Load Process (PXP1099) is used, the account number is auto-generated and will be printed on the 1099-R form and the 1099-R magnetic tape file. For more details, see below.

Changed Report and Process

The following reports and processes have been modified for this enhancement.

1099-R Load Process (PXP1099)

This process has been modified to auto-generate a Payer Account Number to uniquely identify the record by distribution code for each employee. This is an alternative to entering the account number directly on the PXA1099 form.

1099-R Print Report (PXR1099)

Similar to the 1099-R Load Process (PXP1099), this report has also been modified to capture the Payer Account Number in the 1099 tape file, in positions 21- 40.

Section 7 Support for 1099-R Changes - Functional1099-R Processing


1099-R Processing

The Banner HR System utilizes information from several rule forms to produce 1099-R forms. The 1099-R forms will contain accurate data only if this information is complete and correct. Instructions for providing the required information follow:

1. Complete all fields on the Employer Rule Form (PTREMPR).

2. Complete the following fields on the Magnetic Tape Rule Form (PXAMTAP):

• 1099 Contact Name and 1099 Contact Phone Number fields on the main window of the form. These fields identify the 1099-R contact person at your enterprise.

• 1099-R Name Control field on the Employer Information window.

3. Select a value for the 1099-R Indicator field on the Tax Code Rule Form (PXATXCD). This indicator is only applicable to State Tax Codes (for example, GA). It specifies whether the identified state participates in the Combined/Federal State 1099 program. Valid values are Yes, No, and None. (None is used when the associated tax type is something other than State.) If you need to change the value for this indicator, follow the instructions for changing PXATXCD data in Chapter 17, Time Entry and Payroll Processing.

Note: Steps 4-7 are interrelated. Please read these four steps before performing Step 4.

4. Review the information on the 1099-R Distribution Code Validation Form (PTV1099). This form lists all of the distribution codes needed to report information for 1099-R forms. The codes in this form are delivered by SCT. Your enterprise should not change these codes unless it is directed to do so by SCT. The usage of these codes is described below.

5. Complete the following two fields on the Regulatory Information window of the Earn Code Rule Form (PTREARN):

• Enter a 1099-R distribution code in the 1099 Code field if the system should consider the earn code specified in the Key block of PTREARN when processing 1099-R forms. To view a list of valid values, double-click in the 1099 Code field.

• Check the Taxable Amount not Determined from Earn Code checkbox if the taxable amount of the earn code cannot be determined for 1099-R processing. When this field is checked, the 1099-R Load Process (PXP1099), will populate Box 2b on 1099-R.

6. Enter a 1099-R distribution code in the 1099 Code field on the Benefit/Deduction Rule Form (PTRBDCA) if the system should consider the benefit/deduction code specified in the Key block of PTRBDCA when processing 1099-R forms. (This field appears on the main window of the form.)To view a list of valid values, double-click in the 1099 Code field.

Section 7 Support for 1099-R Changes - Functional 1099-R Processing


7. Complete the following fields on the Tax Reporting Rule Form (PXAREPT):

• Enter 1099 in the Tax Report Code field in the Key block of the form.

• Complete the Box Identification, Benefit/Deduction Code, and Earnings Code blocks for each box on the 1099-R form. (Instructions for entering information on this form are given in Chapter 17, Time Entry and Payroll Processing.)

The rules for the earnings and benefit/deduction codes listed for box 1 determine what is loaded into the 1099-R form. The 1099-R forms will be completed according to the following rules:

• An employee will receive one 1099-R form for each distribution code associated with a deduction or earnings type listed for box 1. The distribution code is specified in box 7 of each 1099-R form.

• Only the deductions and earnings defined with the distribution code in box 7 of a 1099-R form are included in the calculations for the boxes of that form.

• A deduction or earning will be included in the calculations for a particular box for an employee's 1099-R only if the following conditions are true:

–The benefit or earnings has been defined for the employee.

–The benefit or earnings has been listed for the box.

–The benefit or earnings has been defined with the distribution code specified in box 7 of the 1099-R form.

For example, if REG is entered as an earn code for box 1 and the 1099 Code field in the PTREARN form for REG contains a distribution code of 1, each employee will receive a 1099-R form for distribution code 1. A 1 will appear in box 7 of each of these forms. As described below, the 1099-R Load Process (PXP1099) will populate the PXR1099 table. In calculating the entry for box 1 in the forms for distribution code 1, PXP1099 will consider each employee’s regular salary as well as each of the employee’s other earnings and deductions that has been listed for box 1 and defined with a distribution code of 1. In calculating the entries for each of the other boxes on the form for a particular employee, PXP1099 will consider each of the employee’s earnings and deductions that has been listed for that box and defined with a distribution code of 1.

If another distribution code has been specified for another deduction or earning listed for box 1, each employee will also receive a 1099-R form for that distribution code. For example, if FED is entered as a deduction code for box 1 and the 1099 Code field in the PTRBDCA form for FED contains a distribution code of 5, each employee will receive a 1099-R form for distribution code 5. A 5 will appear in box 7 of each of these forms. In calculating the entry for box 1 in these forms, PXP1099 will consider each employee’s federal tax as well as each of the employee’s other earnings and deductions that has been listed for box 1 and defined with a distribution code

Section 7 Support for 1099-R Changes - Functional1099-R Processing


of 5. In calculating the entries for each of the other boxes on the form for a particular employee, PXP1099 will consider each of the employee’s earnings and deductions that has been listed for that box and defined with a distribution code of 5.

The processing described in the above examples is performed for all distribution codes associated with box 1. As a result, multiple 1099-R forms can be produced for a particular employee. In each case, the distribution code appears in box 7 of the form.

8. Access the Crosswalk Validation Form (GTVSDAX) and enter the address type(s) in the External Code for the Internal Code 1099ADDR. See “Address Hierarchy for W-2s, 1099-Rs, or 1042-Ss Available on GTVSDAX” on page 158 of this Release Guide.

9. Run the 1099-R Load Process (PXP1099). This process will populate the PXR1099 table. All records created by this process can be viewed online on the 1099-R Form (PXA1099). Use the down arrow key to display all 1099-R forms for an employee, and note the change in distribution code (shown in box 7) if there are multiple 1099-R forms. If you find any errors, make any necessary changes on the PXA1099 form.

A sample PXA1099 record is shown below:

Section 7 Support for 1099-R Changes - Functional 1099-R Processing


You can also create 1099-R records directly on the PXA1099 form without running the PXP1099 Load Process. This functionality might be easier for enterprises who have relatively few 1099-R forms to send.

Note: For IRA, SIMPLE, and SEP accounts, it is possible that box 2a will contain a value and box 2b will be checked on the 1099-R form. When you save the record or when you scroll through previously created records, you will receive a warning message indicating that this scenario is unlikely. Ignore this message if you need both boxes populated.

Instructions for entering or changing a 1099-R record on the PXA1099 form are listed in Chapter 17, Time Entry and Payroll Processing.

10. Run the 1099-R Print Process (PXR1099). For more information, refer to Chapter 20, Reports and Processes, in the Human Resources User Guide.

Section 8 Support for 1042-S Changes - FunctionalOverview


Section 8 Support for 1042-S Changes - Functional

Overview


For 2003 reporting, the Foreign Person 1042-S Report (PXR1042) has been modified to include the reporting of state-tax related information associated with two new Deduction Types, 21 and 22. This resolves RPE #30083.

Additionally, this process has also been modified to print a zero (0)in Box 7 US Federal Tax Withheld, when Federal Tax Withheld is zero dollars ($0). This resolves defect #90019.

For your convenience, the 1042-S Processing notes have been included on page 142.

Note: To simplify the utilization of the new Deduction Types 21 and 22 for reporting of state tax withheld and exempt wages for states honoring tax treaties, SunGard SCT recommends implementing the new deduction types at the beginning of the payroll tax year. If a site makes the transition after the first payroll has been run, manual payroll adjustments will need to be made to transfer state deduction type 04 amounts to the new state Deduction Type 21 along with any applicable treaty allowance for Deduction Type 22.

Changed Report and Process

Foreign Person 1042-S Report (PXR1042)

The Foreign Person 1042-S Report (PXR1042) has been modified in the following respects:

• The process now prints a zero (0) in Box 7, US Federal Tax Withheld, when no Federal Tax is withheld. This resolves defect #90019.

• Deduction Type 21 - Foreign Persons State Tax-1042S Reportable, has been included to report an employee’s state tax withheld when associated with foreign treaty limits.

This completes RPE #30083.

Section 8 Support for 1042-S Changes - Functional 1042-S Processing


See the chart under Processing for the Benefit/Deduction Rule Form (PTRBDCA) for more information on implementation of the new Deduction Types 21 and 22.

Note: To report the new Deduction Type 21, verify the inclusion of all benefits/deductions with Deduction Types 04 and 21 in the Tax Reporting Rules Form (PXAREPT) for Tax Report codes W2, TDUG and 1042.

1042 Magnetic Tape Process (PXPMT42)

The 1042 Magnetic Tape Process (PXPMT42) generates a magnetic tape for the transmission of Form 1042-S (Foreign Person's U.S. Source Income Subject to Withholding). The Recipient ‘Q’ Record has been modified to print Unknown when Recipient Code 20 is used. Accordingly, the Recipient’s address also remains blank.

1042-S Processing

When United States resident and non-resident aliens receive income from U.S. sources, it is subject to U.S. taxation unless it is explicitly exempted by United States code or tax treaty agreements. The United States currently has tax treaty agreements with about forty nations. These treaties typically provide U.S. non-citizens with reduced tax rates or exemption from income taxes on certain types and levels of income received from U.S. sources. For citizens of countries with which there is no tax treaty, the U.S. tax code includes statutory requirements governing different income types.

The new Deduction Type 21- Foreign Persons State Tax-1042S Reportable, allows for the distinction of state tax withheld on nonresident alien income when the state honors Federal Treaties.

The new Deduction Type 22 - Foreign Persons State Treaty Exempted, allows for the accumulation and tracking of nonresident alien income within the Treaty Allowance.

When a Treaty Allowance is greater than zero, the association of Deduction Type 22 to Type 21 will allow for the accumulation of income within the Federal Treaty Allowance (Type 22) and then the state taxation of income over the Federal Treaty Allowance (Type 21). There should be no association on the Type 22 record.

Warning: The statutory regulations (for citizens of countries with which there is no tax treaty) and the tax treaty regulations are very complex and are subject to site interpretation. Before determining the tax liability of your non-citizen employees, give careful study to all applicable tax laws.

Section 8 Support for 1042-S Changes - Functional1042-S Processing


Compensation payments which are exempt from taxation under a tax treaty and non-compensation payments made to a non-resident alien must be reported on Form 1042-S, Foreign Person's U.S. Source Income Subject to Withholding. In addition, non-resident alien employees may be eligible to receive the standard Wage and Tax Statement (Form W-2) if their earnings are subject to FICA and FICA Medicare taxes.

The Banner Human Resources System supports 1042-S reporting requirements with the following batch report and process:

• The 1042-S Report (PXR1042) extracts relevant data, prints Form 1042-S, and inserts the data into the database table used in the generation of the magnetic tape.

• The 1042-S Magnetic Tape Process (PXPMT42) reads the database table and formats the data for magnetic media. This process also produces the 1042TAX file for magnetic media submission.

Refer to Chapter 20, Reports and Processes, of the Human Resources User Guide for additional information on the Foreign Person 1042-S Report (PXR1042) and the 1042 Magnetic Tape Process (PXPMT42).

The following forms and modules capture data for 1042-S processing and reporting:

• Tax Administration

• Benefits Administration

• Employment and Compensation (optional)

• Payroll

• Specified rule and validation forms

To set up 1042-S data, follow the steps listed in the next section.

Instructions

1. Access the Tax Code Rule Form (PXATXCD).

To view the Starting Point, Annualization Method, Supplemental Percent, and 1099-R Indicator fields, move the horizontal scroll bar below Tax Type or use the Next Field function.

Note: You must enter a password in order to make changes to information on this form. To gain update access to this form, follow the steps outlined in Chapter 17, Time Entry and Payroll Processing of the Human Resources User Guide.



2. Define the 1042-S tax codes applicable to your institution. You must use the following naming conventions when you establish your 1042-S tax codes.

It is not necessary to define all possible 1042-S codes. Define only the ones you expect to need at your site (but be sure they follow the naming conventions shown above).

3. Access the Tax Filing Status Form (PXAFSTA).

4. At Tax Code, enter a 1042-S tax code, e.g., FD15 or PA15. (You must complete this form for each 1042-S tax code established on PXATXCD in Step 2.) The system displays the description defined for this code.

5. At Filing Status, enter the country codes applicable to your site. A country code is a two-character code defined by the U.S. government. It identifies an employee's country for purposes of determining tax treaty benefits. The rate of tax withheld is determined by this code. The country code you enter at this prompt is used to set up tax exemptions and calculations on the Tax Setup Form (PXATAXS).

You must enter the codes applicable to your employees in the Filing Status field.

In this position … use this convention … for this designation

1 and 2 FD

<XY>

All Federal Treaties

Specific States that honor Federal Treaties.

For example, PA for Pennsylvania, NY for New York

3 and 4 15 Scholarship/Fellowship Grants

16 Independent Personal Services

17 Dependent Personal Services

18 Teaching

19 Compensation During Training

20 Earnings as an Artist or Athlete



Recognized country codes are published by the Internal Revenue Service in Instructions for 1042-S. Please review the codes applicable to the countries established on the Tax Filing Status Rules Form (PXAFSTA) for any changes.

6. In the Tax Filing Status Rules Form (PXAFSTA) Min YTD Gross field, enter the gross income amount an employee can earn during the year without being taxed represents the Federal Tax Treaty Allowance. Once an employee's year-to-date applicable gross (YTD plus applicable gross of payroll being processed) exceeds the amount entered at this prompt for his or her country code, any part of the current payroll's applicable gross that exceeds this amount will be taxed according to the tax rules established on the Tax Setup Form (PXATAXS).

Example

A non-resident alien employee has an applicable federal gross income of $2,000 per pay. He is a citizen of Austria, and the minimum applicable YTD gross for Austria has been defined on the Tax Filing Status Rules Form (PXAFSTA) as $3,000. The employee is taxed on half of his second paycheck and all of his third.

Warning: The value you enter at this prompt must comply with statutory and tax treaty regulations. To obtain the most recent requirements for the countries represented at your site, contact the Internal Revenue Service for Publication 515.

7. Access the Tax Setup Form (PXATAXS).

To view the Employer Percentage, Option Code, Multiply/Add indicator, Amount, Tax Code Indicator, Tax Type, and Tax Percent fields, move the horizontal scroll bar below Max Annual Tax or use the Next Field function.

For every combination of tax code (defined on PXATXCD) and country code (defined on PXAFSTA), enter the appropriate tax rate.

Payroll Number

YTD Appl Gross Current Appl Gross Current Gross Taxed

1 $0.00 $2,000.00 $0.00

2 $2,000.00 $2,000.00 $1,000.00

3 $4,000.00 $2,000.00 $2,000.00



Tax regulations may require that earnings be taxed based on any of the following:

• a fixed percentage (taking into account possible exemptions which, for most countries, total one). Note that a country code of OC (Country Unknown) requires a fixed rate of 30%.

• a special treaty rate

• the graduated tax tables that apply to U.S. citizens

These regulations determine which fields to complete and what values to enter on the Tax Setup Form (PXATAXS) for a given tax code/country code combination. For detailed instructions on the use of PXATAXS, refer to Setting Up Tax Exemptions and Calculations in Chapter 6, Processing of the Human Resources User Guide. Below are some supplementary instructions for using the Tax Setup Form (PXATAXS) during 1042-S setup.

• To establish a straight percentage without regard to personal exemptions, complete only the Main window of this form. Insert the appropriate rate in the Percentage field.

• To establish a percentage while acknowledging personal exemptions, complete the main window of this form. Enter the percentage rate at Tax Percent, the number 2 at Option Code, Multiply at Multiply/Add, and the appropriate exemption amount at Amount.

• To apply the graduated tax tables without regard to personal exemptions, leave the Tax Exemption block (that is, the block under the Key block) blank and go to the Graduated Tax Table window. Enter the appropriate graduated tax table. SCT's interpretation of the tax code suggests that the graduated table used for the Single filing status for federal withholding tax (tax code FD) should be repeated in this area.

• To apply the graduated tax tables while acknowledging personal exemptions, enter 2 at Option Code, Multiply at Multiply/Add, and the appropriate exemption amount at Amount. Then go to the Graduated Tax Table window and enter the appropriate graduated tax table. SCT's interpretation of the tax code suggests that the graduated table used for the Single filing status for federal withholding tax (tax code FD) should be repeated in this area.

Warning: The values you enter on the Tax Setup Form (PXATAXS) must comply with statutory and tax treaty regulations. To obtain the most recent requirements for the countries represented at your site, contact the Internal Revenue Service for Publication 515.

8. Access the Crosswalk Validation Form (GTVSDAX) and enter the address type(s) in the External Code for Internal Code 1042ADDR. See“Address Hierarchy for W-2s, 1099-Rs, or 1042-Ss Available on GTVSDAX” on page 158 of this Release Guide.



9. Access the Benefit/Deduction Type Validation Form (PTVBDTY).

10. At the Type Code prompt, enter 20 to establish a new benefit/deduction type code. At Description, enter Foreign Persons Tax - 1042S reportable.

If utilizing the new state treaty deduction types, also create:

11. Access the Benefit/Deduction Rule Form (PTRBDCA).

12. Define a deduction code for each federal income type your site expects to use. The deduction definition should match the definition of the Federal Withholding Tax deduction code, with the exception of the following fields:

Define a deduction code for each state that honors federal treaties your site expects to use. Deduction Type 21 is the equivalent of Deduction Type 04 for State Income Tax Withholding. Deduction Type 22 tracks the Treaty Allowance associated with the type 21 state. The deduction definition should match the definition of the State Tax deduction code, with the following exceptions:

Deduction Type code Description

21 Foreign Persons State Tax-1042S reportable22 Foreign Persons State Treaty Exempted

PTRBDCA Field Federal Withholding Tax Treaty

Short [Description]

Fed Tax FD Schlr (example for Income Type 15)

Long [Description]

Federal Withholding Tax

Fed Tax for NRA Tax--Inc Type 15 (example for Income Type 15)

Tax Code FD FD15, 16, 17, 18, 19 and/or 20

Deduction Type 01 20

(on the Definition of Options and Amounts window)

Title [of Option Code] 1

Filing Status Country Code


Exemptions Exemptions

Title [of Amount Code] 1

Additional Withholding




13. Examine the remaining windows of PTRBDCA to complete the calculation rules for these deduction codes. (Refer to Chapter 4, Rule Forms, of the Human Resources User Guide for detailed information on each PTRBDCA field.) Pay particular attention to the following windows:

• Associated Benefits/Deductions

• Precluded Benefits/Deductions

• Included Benefits/Deductions

• Excluded Deductions and Excluded Earnings

• Benefit/Deduction Labor Distribution Overrides

In most cases, the rules established for the standard Federal Withholding Tax can be duplicated for the Foreign Persons Federal Withholding Tax.

Note: When utilizing the new Benefit/Deduction Type 21 and Type 22, you must associate type 22 to type 21 for the specific state and income code. Make sure Deduction Type 21 is a lower priority than Type 22. There should be no association on the Type 22 record.

PTRBDCA Field State Withholding State Tax Treaty

Short [Description]

St Tax PA Schlr (example for Pennsylvania honoring Federal Tax Treaty for Income Type 15)

Long [Description]

State Withholding Tax

PA Treaty Tax - Income 15 (example for Income Type 15)

Tax Code PA PA15, 16, 17, etc. (example for Deduction Type 21)

PAT5, PAT6, PAT7, etc. (example for Deduction Type 22)

Deduction Type 04 21 (for all Non-Resident Aliens)

22 (if treaty allowance > 0)

(on the Definition of Options and Amounts window)


Filing Status Country Code


Exemptions Exemptions

Title [of Amount Code] 1





14. Access the Benefit Category Rule Form (PTRBCAT).

15. Add the newly defined deduction codes to the appropriate benefit categories (that is, the benefit categories to which your 1042-S employees are assigned) on PTRBCAT.

16. Access the Employee Benefit or Deduction Form (PDADEDN).

17. Use the Employee Benefit or Deduction Form (PDADEDN) to assign the newly defined deduction codes as appropriate. Keep in mind the following points:

• Assign the appropriate deduction code for each income type included in the tax treaty with the employee's country.

• Complete Option Code 1 with the appropriate country code (as established on the Tax Filing Status Rules Form (PXAFSTA)).

• Option Code 2 can reflect the number of exemptions claimed.

• To avoid payroll processing errors, employees who are subject to nonresident alien tax rules should have a status of E(xempt) for the Federal Withholding Tax deduction. (This is not necessary if the employee's benefit category does not include federal withholding tax in its PTRBCAT definition.) At payroll run, the system will acknowledge that the employee has the federal tax deduction (even though it is exempted) and will continue to process the employee through the payroll cycle.

18. Access the U.S. Regulatory Information window of the Employee Form (PEAEMPL).

19. At 1042S Recipient in the U.S. Regulatory Information window, enter a 1042 recipient code for each employee who must receive a 1042-S for the current calendar year. Valid values are listed below and are available from field-level Dynamic Help.

Code Recipient

01 Individual02 Corporation03 Partnership04 Fiduciary05 Nominee06 Government or international organization07 Tax-exempt organization08 Private foundation09 Artist or athlete19 Other20 Type of recipient unknown



Note: Take special precautions to update this field based on the 1042-S reporting year. For example, if an employee was eligible for 1042-S processing for the first but not the second half of the current calendar year, the 1042S Recipient field must be populated until the 1042-S statement for that calendar year has been produced. After you print the 1042-S report and generate the 1042-S Magnetic Tape, you should delete the value in the 1042S Recipient field of that employee's record.

20. If an employee has more than one job, and one job is subject to the tax treaty rule and the other is subject to the standard federal withholding tax, do the following:

• On the Employee Benefit or Deduction Form (PDADEDN), set up both the federal tax deduction and the appropriate deduction code(s) for the income and country codes applicable to this employee.

• In the Excluded Benefits/Deductions window of the Employee Jobs Form (NBAJOBS), exclude the Federal Withholding Deduction code from the job to be taxed only under nonresident alien tax rules. Standard federal tax will not be withheld from this job's earnings during the payroll process.

• For jobs to be taxed according to the standard federal graduated tax tables, enter the nonresident alien tax code(s) in the Excluded Deductions area of the Employee Job Form.

21. Run your payroll. (To review payroll procedures, see the Payroll Procedures section in Chapter 6, Processing of the Human Resources User Guide.) The Payroll Calculation process (PHPCALC) processes tax treaty deduction information in the 1042 database table, where it remains available for subsequent payrolls.

22. Access the Tax Report Setup Rule Form (PXAREPT).

Warning: This form is delivered to you with box identifications as established by SCT for your Banner Human Resources payroll module. Do not revise them unless you are advised to do so by SCT.

23. Use the Tax Report Setup Rule Form (PXAREPT) to associate 1042-S boxes by number with appropriate deductions and/or earnings. (For field-by-field instructions on using PXAREPT, refer to Chapter 17, Time Entry and Payroll Processing of the Human Resources User Guide.)

When utilizing the new Deduction Types 21 and 22, the site may control the reporting of income and tax by setting up only those Benefits/Deductions that apply to the applicable form, such as the 1042-S or W-2.

Warning: The statutory regulations (for citizens of countries with which there is no tax treaty) and the tax treaty regulations are very complex and are subject to site interpretation. Before determining the reporting requirements for non-citizen employees, give careful study to all applicable tax laws.



24. Run the 1042-S report (PXR1042) to produce Form 1042-S. Before proceeding to the next step, verify the results. Use the following parameters.

25. Run the 1042-S Magnetic Tape Process (PXPMT42).

Parameter What to Enter?

Tax Year The tax reporting year.

Employer Code The applicable employer code being reported.

Specific Employee IDs Ind

Y or N depending on the intended output.

Employee IDs If a Y was entered for the Specific Employee IDs Ind parameter, then enter the individual tax IDs.

Zero Out Negative Amounts

Y or N depending whether or not you want to reduce negative box amounts to zero.


Tax Year The tax reporting year. Required.

Is this run for TEST purposes?

Enter Y to label this run as a test run. This report then runs and populates positions 133-136 with the word TEST. Enter N if this run is the actual run. Required.

Number of Reels/Cartridges

Number of tape reels or cartridges being submitted. Required.




Section 9 Support for US W-2 and MMREF-1 Processing - FunctionalOverview


Section 9 Support for US W-2 and MMREF-1 Processing - Functional

Overview


For 2003 Tax Reporting, the United States W-2 Report (PXRW2US) has been modified to include the reporting of state-tax related information associated with two new Deduction Type 21 and Type 22. This resolves RPE #30083.

See Section 8 “Support for 1042-S Changes - Functional” on page 141 for more information on processing Deduction types 21 and 22.

For your convenience an updated version of US W2 and MMREF-1 processing notes have been included in the latter part of this section, on page 154.

Changed Report

United States W-2 (PXRW2US)

The United States W-2 Report (PXRW2US) has been modified in the following respects:

• Two new deduction types have been included to capture an employee’s state wages and state tax withheld when associated with foreign treaty limits:

• 21 - Foreign Persons State Tax-1042S reportable and

• 22 - Foreign Persons State Treaty Exempted

This completes RPE #30083.

Note: To use the new Deduction Type 21, set up all benefits/deductions with Deduction Types 04 and 21 in the Tax Reporting Rules Form (PXAREPT) for Tax Report codes W2, TDUG and 1042.

Section 9 Support for US W-2 and MMREF-1 Processing - Functional Processing Notes


Processing Notes

US W-2 and MMREF-1 Processing

To produce W-2 files, you must first set up required employer information and create the data for the W-2 forms. You can then create a magnetic tape or disk file containing all required W-2 information for submission to the government. Procedures for accomplishing these tasks are outlined below.

1. Access the Employer Rule Form (PTREMPR) and complete all fields. Make sure the federal ID number is correct. In the Employer State Information block, create records for all states that you withhold tax for and specify the correct account number for each state. This information prints in Box 15 of the United States W-2.

2. Access the Magnetic Tape Rule Form (PXAMTAP) and enter values in all necessary fields. Complete all three areas of the form (Transmitter Information, Organization Information, and Employer Information).

In most cases, the Transmitter Name and Address fields will be the same as the Organization Name and Address fields.

3. Access the MMREF-1 Electronic Filing Form (PXAMMEF) and enter values in all necessary fields. Complete all three areas of the form (Submitter Information, Company Information, and Employer Information). Complete the Third Party FIT Withheld field in the Employer Information area if applicable.

In most cases, the Submitter Name and Address fields will be the same as the Company Name and Address fields.

4. Access the Tax Reporting Rule Form (PXAREPT). In the Key block, enter W2.

Move to the Box Identification block. Each record in this area corresponds to a box on the W-2 form. All data in this block, except that for boxes 16 and 17, is supplied by SCT and should not be modified without consulting SCT.

Section 9 Support for US W-2 and MMREF-1 Processing - FunctionalProcessing Notes


You must set up a Box 16 and a Box 17 for each state for which you deduct state income tax. For each box, enter the box number followed by the two-character state code, as illustrated in the following example:

For each box record in the Box Identification block, you must list the benefit/deduction codes (from the PTRBDCA Benefit/Deduction Code field) and/or the earnings codes (from the PTREARN Earnings Code field) associated with the specified box. This selection is made in the Benefit/Deductions block and the Earnings block as described in the following page.

5. Choose a box and move to the Benefit/Deduction Code block. The vast majority of W-2 boxes will be specified in the Benefit/Deduction Code block. Very few, if any, will make use of the Earnings Code block.

List the Benefit/Deduction codes that pertain to the box chosen. Often this will be just one code. Also, a box is not usually associated with a benefit/deduction code and an earnings code.

For each Benefit/Deduction code listed, indicate which of the three amounts (Applicable Gross, Employee Amount, or Employer Amount) should be placed in the box. If necessary, you can list more than one.

Note: It is very important not only to list the correct benefit/deduction code(s), but also to specify the right amount indicator(s).

Boxes 15D and 15P no longer need to be defined on PXAREPT. It is recommended that the data for these boxes be deleted from the form to aid runtime performance

6. If the box is to contain earnings, move to the Earnings block and list the relevant earnings codes.

Box Description

16NJ New Jersey state wages16OH Ohio state wages16PA Pennsylvania state wages17NJ New Jersey state tax withheld17OH Ohio state tax withheld17PA Pennsylvania state tax withheld

Example 1 Box 1 Annual Federal Wages, Tips and Other Compensation

FED Federal Tax Applicable Gross

Example 2 Box 4 Social Security Tax withheld

FIO FICA—Old age portion Employee Amount



7. Access the Crosswalk Validation Form (GTVSDAX) and enter the address type(s) in the External Code for Internal Code W2ADDR. See “Address Hierarchy for W-2s, 1099-Rs, or 1042-Ss Available on GTVSDAX” on page 158 of this release guide.

8. When you run the United States W-2 (PXRW2US), you will be asked to enter a tax quarter. If you select quarters 1 through 4, the system will create data for the quarterly magnetic tape process. It will not create hard copy W-2s. If you select A (All quarters), the system will produce both hard copy W-2s and the data for year-end magnetic tape or diskette processing.

9. The W-2 process can be run multiple times. Each time, it will create a hard copy print file and populate a table used to create the magnetic tape(s) or diskette file. (There is no harm in just running it multiple times.)

Run the following in job submission:

Summary of PXRW2US Parameters:

For Quarterly Reporting establish the following parameters:

For Yearly Reporting (W-2 Forms printed) establish the following parameters:


Tax Year Tax reporting year.

Tax Quarter 1, 2, 3, or 4 to identify the quarter being reported.

Employer Code Applicable employer code being reported.

Specific Employee IDs Ind Y or N depending on the intended output.

Employee IDs If a Y was entered for the Specific Employee IDs Ind parameter, then enter individual tax IDs.


Y or N depending whether or not you want to replace negative box amounts with zero.



Tax Quarter A to report for the full year.






Running/Creating a Disk and/or Magnetic Tape File

Note: Run the W-2 MMREF-1 File (PXPW2MM) after the U.S. W-2 Report (PXRW2US) and before the W-2 MMREF-1 Tape File (PXPW2TP) to populate the formatted file (W2REPORT).

1. Run the U.S. W-2 Report (PXRW2US) typically used to create the hard copy W-2s.

This program produces two outputs, a print file (pxrw2us.lis) and an error report (pxrw2us.err). It also places information into the PXRMTW2 table.

2. Run the W-2 MMREF-1 File (PXPW2MM).

This process produces two outputs, a print file (pxpw2mm.lis) and an error report (pxpw2mm.err). It also places information into a formatted file (W2REPORT) from the data in the PXRMTW2 table.

3. Run the W-2 MMREF-1 Tape File (PXPW2TP).

This process produces a print file (pxpw2tp.lis) and converts data from the W2REPORT file to tape layout (W2TAPE).

For complete information the U.S. W-2 Report (PXRW2US) and the W-2 MMREF-1 File Process (PXPW2MM), see Chapter 20, Reports and Processes, of the Human Resources User Guide.


Y or N depending whether or not you want to reduce negative box amounts to zero.

W-2 Format Format to print W-2s:1—Standard IRS 1-up2—Laser 4-up3—Totals only—Choose to print only totals for the whole year. This does not print individual W-2s.4— Laser (pressure sealed) forms

W-2 Sort Order Order in which to sort the printed W-21—Last Name, First Name2—ZIP Code3—Check Distr Org—Check Distribution Organization




W-2 Employee Name

Note: Use of the Comment Form (PPACMNT) is not compatible with MMREF-1 reporting requirements.

If you want to use a name different than the one appearing on the Identification Form (PPAIDEN) for the W-2 Employee Name on the U.S. W-2 Report, and on the files produced by the W-2 MMREF-1 File (PXPW2MM) and the W-2 MMREF-1 Tape File (PXPW2TP), then complete the Social Security Name fields on the U.S. Regulatory Information window of the Employee Form (PEAEMPL).

Note: If a name is not specified in the Social Security Name fields on the Employee Form (PEAEMPL), the name that prints on the W-2 will be taken from the Identification Form (PPAIDEN).

Address Hierarchy for W-2s, 1099-Rs, or 1042-Ss Available on GTVSDAX

The method for creating the W-2, 1099-R, or 1042-S mailing addresses based on an address hierarchy appears below. Essentially, this method prioritizes the various address types for each recipient entered on the Identification Form (PPAIDEN) through the use of the Crosswalk Validation Form (GTVSDAX).

Once the hierarchy of address types are prioritized on GTVSDAX, the year-end processes use this information to determine the addresses of recipients. For example, if on GTVSDAX the PR (Permanent) address is given the first priority, a sequence of 1, and the BU (Business) address is given second priority, a sequence of 2, then the year-end processes (W-2, 1099-R, or 1042-S—whichever you select) prints (or produces on magnetic tape or diskette) all PR addresses on file for recipients. If a PR address is not available, then the system uses the BU address.

To establish an address hierarchy on the GTVSDAX form do the following:

1. Access the Crosswalk Validation Form (GTVSDAX).

2. Perform the Insert Record function.

3. Enter W2ADDR, 1042ADDR, or 1099ADDR in the Internal Code field. Make your choice based on the year-end process for which you want to create the hierarchy.

4. Enter the sequence number of the address type being used for the hierarchy. For example, if you want the W-2, 1042-S, or 1099-R process to select a MA (Mailing) address type as the secondary address, you would enter 2 in the Internal Seq field.

5. Enter ADDRESS in the Internal Group field.

6. Enter the address type in the External Code field, such as PR (Permanent).



7. Enter a description, to identify the type of address entered, in the Desc field. For example, W2 Permanent Address.

8. Save the record.

9. Repeat for all address types that are part of the hierarchy used when mailing W-2s, 1099-Rs or 1042-Ss.

10. Use the Query feature to display existing address information for specific codes. Enter W2ADDR, 1042ADDR, or 1099ADDR to query.

Adjusting Laser Print File if W-2s Need Realignment

The instructions below should be followed for making adjustments to the laser print file if your W-2s need some alignment. Modifications to the print file should be made by a person who is familiar with the PostScript language.

Note: SCT supports Moore Laser Printer 4-up forms. Comments made in this section impact these forms.

Default Font

The default font chosen for the W-2s is 10 point New Courier, which is a non-proportional typeface. This means that all letters and spaces use the same amount of print space on a horizontal line, regardless of the width of the letter. If a change to the font is required, it can be found at the beginning of the print file. Its form is:

/TextFontCN10 /Courier-New findfont 10 scalefont def TextFontCN10 setfont

Postscript Printing

In order for a laser printer to recognize a postscript file when running the W-2 Wage and Tax Statement (PXRW2US) Form, the first two characters of the first line must be %!. This automatically occurs.

Adjusting Horizontal Print Positions

The print may vary slightly on printers from different manufacturers. Consequently, if horizontal adjustment is required for the entire form, there is an easy way to make the adjustment. Increasing or decreasing the left margin will cause all printed data on the form to shift either left or right. Only very slight adjustments should be necessary. The applicable parameter can be found at the beginning of the print file and its form is:

/LeftMargin .75 inch def



Adjusting Vertical Print Positions

The vertical spacing is somewhat tighter and cannot be accommodated in the same manner as horizontal shifts. A vertical alignment problem will be most noticeable on the lower half of the form. The amount of space between lines is called “leading” and the default values are 9 for single spacing and 18 for double spacing.

If the data is printing over the description of each box on the form, the leading should be increased. If the data is printing over the bottom line of each box, the leading should be decreased. The double space value should always be twice that of the single space value.

When adjusting the leading, increment or decrement only one number at a time. For example, increment single and double spacing from 9 and 18 to 10 and 20. Moving up or down by one number should be the maximum adjustment necessary for the supported Moore forms. These parameters can be found at the beginning of the print file and their form is:

/LineSpace 9 def

/DoubleSpace 18 def

If all printed data must be shifted up or down, adjusting the top margin is the best method. The default value can be found in the /TopStart command. If an adjustment is required, it should be very slight. The parameter can be found at the beginning of the print file. Its form is:

/TopStart 10.125inch def (Laser 4-up)

/TopStart 12.325inch def (Laser – Pressure Sealed)

U.S. Tax Form Vendors

This section describes the form vendors that support U.S. year-end tax reporting for Banner.

General Information about Form Vendors

The software has been written so that the placement of each of the characters fits accurately in the lines and check boxes found on the forms supplied by Moore-Wallace (listed below). SCT has selected Moore-Wallace as a recognized and recommended business partner.

If your site elects to use a form vendor other than Moore-Wallace, the placement of the characters may vary since the form may be different. The existence of this restriction does not imply that you must use Moore forms. You may use any vendor that you choose. However, this may require modifications at your site to obtain the proper alignment.



Other forms vendors will probably require a sample output that can be obtained from running the tax reports PXR1042, PXR1099, and PXRW2US. The sample output appears at the beginning of the file and is generated when the tax data exists and the rule forms have been set up correctly in Banner. Three alignment forms appear at the beginning of each file generated when running the reports.

Note: The U.S. Government allows variations in the forms as long as the form is approved by the IRS. Forms supplied by Moore-Wallace are federally approved.




Section 10 Support for Puerto Rico W2 and MMREF-1 Processing - FunctionalOverview


Section 10 Support for Puerto Rico W2 andMMREF-1 Processing - Functional

Overview


There are no changes for Puerto Rico W-2 and MMREF-1 tax reports.

For your convenience the Puerto Rico W-2 and MMREF-1 processing notes have been included below.

W-2 Puerto Rico Processing

To produce W-2PR files, you must first set up required employer information and create the data for the W-2PR forms. You can then create a magnetic tape or diskette file containing all required W-2PR information for submission to the government. Procedures for accomplishing these tasks are outlined below.

1. Access the Employer Rule Form (PTREMPR) and complete all fields. Make sure the federal ID number is correct.

2. Access the Magnetic Tape Rule Form (PXAMTAP) and enter values in all necessary fields. Complete all three areas of the form (Transmitter Information, Organization Information, and Employer Information).

In most cases, the Transmitter Name and Address fields will be the same as the Organization Name and Address fields.

3. Access the MMREF-1 Electronic Filing Form, (PXAMMEF) and enter values in all necessary fields. Complete all three areas of the form (Submitter Information, Company Information, and Employer Information). Complete the Third Party FIT Withheld field in the Employer Information area if applicable.

In most cases, the Submitter Name and Address fields will be the same as the Company Name and Address fields.

Section 10 Support for Puerto Rico W2 and MMREF-1 Processing - Functional W-2 Puerto Rico Processing


4. Access the Tax Reporting Rule Form (PXAREPT). In the Key block, enter PRW2.

Move to the Box Identification block. Each record in this area corresponds to a box on your W-2PR form. All data in this block is supplied by SCT and should not be modified without consulting SCT.

For each box record in the Box Identification block, you must list the benefit/deduction codes (from the PTRBDCA Benefit/Deduction Code field) and/or the earnings codes (from the PTREARN Earnings Code field) associated with the specified box. This selection is made in the Benefit/Deductions block and the Earnings block as described below.

5. Choose a box and move to the Benefit/Deduction Code block. The vast majority of W-2PR boxes will be specified in the Benefit/Deduction Code block. Very few, if any, will make use of the Earnings Code block.

List the Benefit/Deduction codes that pertain to the box chosen. Often this will be just one code. Also, a box is not usually associated with a benefit/deduction code and an earnings code.

For each Benefit/Deduction code listed, indicate which of the three amounts (Applicable Gross, Employee Amount, or Employer Amount) should be placed in the box.

Note: It is very important not only to list the correct benefit/deduction code(s), but also to specify the right amount indicator(s).

6. If the box is to contain earnings, move to the Earnings block and list the relevant earnings codes.

7. Access the Crosswalk Validation Form (GTVSDAX) and enter the address type(s) in the External Code for Internal Code W2ADDR. See “Address Hierarchy for W-2PRs Available on GTVSDAX” on page 166 in this section of the Release Guide.

8. When you run the Puerto Rico W-2 Report (PXRW2PR), the system will produce both hard copy W-2PRs and the data for year-end magnetic tape processing.

Example 1 Box 8 Sueldos-Wages

FED Federal Tax Applicable Gross

Example 2 Box 18 Total Sueldos Seguro Social-SS Wages

FIO FICA—Old age portion Employee Amount

Section 10 Support for Puerto Rico W2 and MMREF-1 Processing - FunctionalW-2 Puerto Rico Processing


9. The W-2PR process can be run multiple times. Each time, it will create a hard copy print file and populate a table used to create the magnetic tape(s) and diskette file(s). (There is no harm in just running it multiple times.) Run the following in job submission:

Summary of PXRW2PR Parameters:

Running/Creating a Disk and/or Magnetic Tape File

Note: Run the Puerto Rico W-2 MMREF-1 File (PXPW2MP) after the Puerto Rico W-2 Report (PXRW2PR) and before the W-2 MMREF-1 Tape File (PXPW2TP) to populate the MMREF-1 format file (W2REPORT).

1. Run the Puerto Rico W-2 Report (PXRW2PR).

This process produces two outputs, a print file (pxrw2pr.lis) and an error report (pxrw2pr.err). It also places information into the PXRMTPR table.

2. Run the Puerto Rico W-2 MMREF-1 File (PXPW2MP).

This process produces two outputs, a print file (pxpw2mp.lis) and an error report (pxpw2mp.err) It also places information into a formatted file (W2REPORT) from the data in the PXRMTPR table.







Y or N depending whether or not you want to replace negative box amounts with zero.

W-2PR Format Format to print W-2PRs:1—Standard IRS 1-up2—Totals only—Choose to print only totals for the whole year. This does not print individual W-2PRs.

W-2PR Sort Order Order in which to sort the printed W-2PR1—Last Name, First Name2—ZIP Code3—Check Distr Org—Check Distribution Organization



3. Run the W-2 MMREF-1 Tape File (PXPW2TP).

This program produces a print file (pxpw2tp.lis) and converts data from the W2REPORT file to tape layout (W2TAPE).

Note: For complete information on the Puerto Rico W-2 Report (PXRW2PR) and the Puerto Rico W-2 MMREF-1 File process (PXPW2MP), see Chapter 20, Reports and Processes of the Human Resources User Guide.

Note: For complete information the PXRW2PR, PXPW2MP, and PXPW2TP processes, see Chapter 20, Reports and Processes of the Human Resources User Guide.

W-2PR Employee Name

Note: Use of the Comment From (PPACMNT) is not compatible with MMREF-1 reporting requirements.

If you want to use a name different than the one appearing on the Identification Form (PPAIDEN) for the W-2 Employee Name on the Puerto Rico W-2 Report (PXRW2PR) and on the files produced by the Puerto Rico W-2 MMREF-1 File (PXPW2MP) and the W-2 MMREF-1 Tape File (PXPW2TP), then complete the Social Security Name fields on the U.S. Regulatory Information window of the Employee Form (PEAEMPL).

Note: If a name is not specified in the Social Security Name fields on PEAEMPL, the name that prints on the W-2PR will be taken from PPAIDEN.

Address Hierarchy for W-2PRs Available on GTVSDAX

The method for creating the W-2PR mailing addresses based on an address hierarchy appears below. Essentially, this method prioritizes the various address types for each recipient entered on the Identification Form (PPAIDEN) through the use of the Crosswalk Validation Form (GTVSDAX).

Once the hierarchy of address types are prioritized on GTVSDAX, the W-2PR processes use this information to determine the addresses of recipients. For example, if on GTVSDAX the PR (Permanent) address is given the first priority, a sequence of 1, and the BU (Business) address is given second priority, a sequence of 2, then the W-2PR processes print (or produce on magnetic tape or diskette) all PR addresses on file for recipients. If a PR address is not available, then the system uses the BU address.

Section 10 Support for Puerto Rico W2 and MMREF-1 Processing - FunctionalW-2 Puerto Rico Processing


To establish an address hierarchy on the GTVSDAX form do the following:

1. Access the Crosswalk Validation Form (GTVSDAX).

2. Perform the Insert Record function or query for existing records.

3. Enter W2ADDR in the Internal Code field. Make your choice based on the year-end process for which you want to create the hierarchy.

4. Enter the sequence number of the address type being used for the hierarchy. For example, if you want the W-2PR process to select a MA (Mailing) address type as the secondary address, you would enter 2 in the Internal Seq field.

5. Enter ADDRESS in the Internal Group field.

6. Enter the address type in the External Code field, such as PR (Permanent).

7. Enter a description, to identify the type of address entered, in the Desc field. For example, W2PR Permanent Address.

8. Save the record.

9. Repeat for all address types that are part of the hierarchy used when mailing W-2PRs.

10. Use the Query feature to display existing address information for specific codes. Enter W2ADDR to query.

Puerto Rico Tax Form Vendor

All Puerto Rico tax processing produced by SCT prints on the forms generated from the Returns Processing Bureau located in Puerto Rico. They produce an Impact form for the Puerto Rico W-2PR. See the Returns Processing Bureau for more information regarding how to obtain these forms.




Section 11 Support for 1099-R Changes - TechnicalChanged Table


Section 11 Support for 1099-R Changes - Technical

This section documents the database changes made for 1099-R reporting in year 2003.

Note: This information was originally delivered with Human Resources Release 6.0.5.

Changed Table

(PXR1099)

The following column has been added to capture the Payer Account Number in the PXR1099 table.

New Scripts


PXR10991.SQL AND PXR10992.SQL

The PXR10991.sql script adds a new column to store the Payer’s Account Number in the PXR1099 table.

The PXR10992.sql script updates the new column PXR1099_ACCT_NO with a unique value.

PXR10993.SQL AND PXR10994.SQL

PXR10993.sql sets the PXR1099_ACCT_NO column as a NOT NULL column.

PXR10994.sql adds a comment to the PXR1099_ACCT_NO column.


PXR1099_ACCT_NO NOT NULL VARCHAR2(20)

Section 11 Support for 1099-R Changes - Technical New Scripts


PXR10995.SQL

PXR10995.sql adds a unique index to the PXR1099 table.

Section 12 CA-MIS Reporting Enhancements For 2003 - FunctionalOverview


Section 12 CA-MIS Reporting Enhancements For 2003 - Functional

Overview


California’s community colleges are required to submit Employee Demographic Information as well as the Employee Assignment Information to the California Community College Chancellor's Office. Two extract processes in Banner, Employee Demographic Extract Process (PEPEDEX) and the Employee Assignment Extract Process (PEPAEXT) generate data files that are required for compliance with this report.

Enhancements addressed in this release include:

• Inclusion of Premium, Shift Differential and Additional earnings in the calculation of the annual salary by the PEPCSAL process.

• Eliminating the use of the PEAJACT for evaluating MIS element values by the PEPAEXT process.

• An updated PEPAEXT file layout

These enhancements also satisfy RPE #34834 and RPE #34836.

Changed Forms

The following Human Resources forms have been modified for this enhancement:

Rule Forms

Application Form

PTREARN Earnings Code Rule FormPTRJBLN Job Location Rule Form

PDAASGN Employee Assignment Extract Form

Section 12 CA-MIS Reporting Enhancements For 2003 - Functional Changed Forms


Earnings Code Rule Form (PTREARN)

This rule form enables you to create earnings codes and associate them with rules. The earnings code identifies the nature of the pay (for example, regular or holiday) and establishes the rules governing the time entry validation and processing of earnings represented by this code.

A new California MIS Additional Earnings check box field has been added to the Regulatory Information window of PTREARN to identify the earn codes that are to be included in the calculation of the annual salary by the PEPCSAL process.

Longevity, shift differential and other earn codes that are not defined as stipends on PTREARN can also be included in the calculation of the annual salary.

Note: If shift differential is not set up as a premium pay it will not be added for the calculation of the annual salary. However, you can indicate this earn code as an additional earning by selecting this check box.

The PEPCSAL process has now been modified to calculate the annual salary by including any additional earnings for primary and secondary jobs. For more details, refer to page 179.

Job Location Rule Form (PTRJBLN)

The Job/Hiring Location Rule Form establishes job location codes for use on the Employee Jobs Form (NBAJOBS) and the Employee Form (PEAEMPL).

A new District Code field has been added to this form that allows you to specify the CA-MIS district code for each job location, where appropriate. You can override the job location at the position level via NBAPOSN or at the employee level via NBAJOBS. This enables the Job Assignment Extract Process (PEPAEXT) track the CA-MIS District codes for each job assignment for an employee from NBAJOBS.

Section 12 CA-MIS Reporting Enhancements For 2003 - FunctionalChanged Forms


Employee Jobs Form (NBAJOBS)

The CA-MIS District code originally specified on the Job/Hiring Location Rule Form (PTRJBLN) form is available in the List of Values (LOV) corresponding to the Job Location field on the Miscellaneous Job Information window of the NBAJOBS form. This enables tracking of CA-MIS District codes for each job assignment at the employee level.

Note: This form has not been changed and is not being delivered with this release. It has been documented in the Changed Forms section as a follow-up to PTRJBLN.

Employee Job Activity Form (PEAJACT)

The District Code, the Job Activity Code and the Assgn. Type fields will no longer be used as a source of reference for the MIS data elements in the PEPAEXT process.



Employee Assignment Extract Form (PDAASGN)

This application form allows you to review the job assignment data extracted by the PEPAEXT process prior to the creation of the data file. To uniquely identify the extracted records several new fields have been added to the report generated by this process. To accommodate the new fields, the extracted data will now be maintained in a new table, Employee Assignment Data Table (PERNASG). Data previously maintained in the PERASGN table will be retained for historical purposes only, and can be accessed by using client reporting tools.

Fields in the scrolling canvas are shown in the following page.





To uniquely identify each extracted record, the following fields have been added in the scrolling canvas:

. . . . . . . . . . . . . . . . .Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Source Displays the Banner form that is the source for the MIS data element.

Position Displays the employee’s position entered on NBAJOBS to uniquely identify the job assignment.

Suffix Displays the suffix associated with a position to uniquely identify a job assignment on NBAJOBS

Position Status Displays the status of the position.

Effective Date Displays the effective date specified for the position on NBAJOBS.

Course Reference Number (CRN)

Displays the Course Reference Number associated with the position/suffix combination entered on the Faculty Assignment Form (SIAASGN) or the Faculty Leave Assignment Form (SIALVAS).



Term Code Displays the Term Code associated with the Course Reference Number as specified on the Faculty Assignment Form (SIAASGN) or the Faculty Leave Assignment Form (SIALVAS).

Category Displays the session code associated with the Course Reference Number on the Faculty Assignment Form (SIAASGN) or the Faculty Leave Assignment Form (SIALVAS).

Non-Instructional Type Code

Displays the non-instructional type code associated with the employee. This information is drawn from the SIRNIST.

College Code Displays the college code associated with the employee’s job assignment.

Department Code Displays the Department code associated with the employee’s job assignment.

. . . . . . . . . . . . . . . . .Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions




Section 12 CA-MIS Reporting Enhancements for 2003 - FunctionalChanged Reports and Processes


Changed Reports and Processes

Calculate Statistics Salary Process (PEPCSAL)

The PEPCSAL extract process has been modified to calculate the employee’s annual salary for primary and secondary jobs by including premium earnings, shift differential earnings or any other additional earnings. From the earn codes listed for each employee in the Default Earnings window on NBAJOBS, the process includes only those that are marked as Additional Earnings and/or Premium Earnings on the Earnings Code Rule Form (PTREARN).

Note: Exercise caution if you include Premium earnings and Additional earnings in the calculation of the annual salary, as it is possible that earnings may get duplicated and result in an inflated annual salary.

Accordingly, three new report parameters have been added to specify the inputs for the annual salary calculation.


Include Premium Earnings Specify if premium earnings are to be considered in the calculation of the annual salary.

No N Y or N

Include Additional Earnings Specify if earn codes marked as Additional earnings on PTREARN are to be considered in the calculation of the annual salary.

No N Y or N

Include Shift Differential Specify if shift differential earn codes are to be included in the calculation of the annual salary.

No N Y or N



Report Sample—Calculate Statistics Salary Process (PEPCSAL)

27-OCT-2003 SCT Banner University PAGE 114:52:57 Calculate Statistics Salary PEPCSAL

* Indicates New Step Not Found or Out of Range for This ID. Annual Projected Pending ID Name Annual Salary Salary Date Projected Salary Salary Date Nego Ind123456987 Bernard Nevermind MH 80300.00 01-JAN-2002 80300.00 31-DEC-2002BB0000020 Adam Abner 135766.21 01-JAN-2002 135766.21 31-DEC-2002091000000 Abigail Abbey 60000.00 01-JAN-2002 63000.00 31-DEC-2002 Y131000001 Brian Abbey 34319.40 01-JAN-2002 34319.40 31-DEC-2002610009711 James Abbot 63000.00 01-JAN-2002 63000.00 31-DEC-2002511333333 Margaret Abercrombie 83250.00 01-JAN-2002 83250.00 31-DEC-2002109900001 Cathryn Able 74925.00 01-JAN-2002 77175.00 31-DEC-2002 N109900002 Fred Able 83250.00 01-JAN-2002 85750.00 31-DEC-2002 NJCCA99999 Ione Acar 60000.00 01-JAN-2002 60000.00 31-DEC-2002WE0000050 Amy Ace 63000.00 01-JAN-2002 63000.00 31-DEC-2002200000001 Linda Adam 85085.44 01-JAN-2002 87640.00 31-DEC-2002 NCD0000034 April Adams 101325.00 01-JAN-2002 101325.00 31-DEC-2002CD0000026 Ashley Adams 26543.76 01-JAN-2002 26543.76 31-DEC-2002JCCA22222 Bernard Adams 1247976.00 01-JAN-2002 1247976.00 31-DEC-2002121000001 Bill Adams 83250.00 01-JAN-2002 83250.00 31-DEC-2002BC000JOB2 James Adams 78750.00 01-JAN-2002 78750.00 31-DEC-2002WE0000011 James Adams 152762.50 01-JAN-2002 152762.50 31-DEC-2002CD0009557 Jamie Adams 11465.76 01-JAN-2002 11465.76 31-DEC-2002LAURA0035 Joey Adams 50000.00 01-JAN-2002 50000.00 31-DEC-2002CD0000031 Kayla Adams 86625.00 01-JAN-2002 86625.00 31-DEC-2002CD0000032 Kyle Adams 14248.00 01-JAN-2002 14248.00 31-DEC-2002CD0000000 Mary Adams 25115.52 01-JAN-2002 .00 31-DEC-2002AP0000006 Michael Adams 3288.00 01-JAN-2002 3288.00 31-DEC-2002CD0000115 Shane Adams 94350.00 01-JAN-2002 105010.00 31-DEC-2002 NCD0000027 Tony Adams 10919.76 01-JAN-2002 10919.76 31-DEC-2002CD0000033 Vaughn Adams 93450.00 01-JAN-2002 93450.00 31-DEC-2002529000001 William Adams 78750.00 01-JAN-2002 78750.00 31-DEC-2002



27-OCT-2003 SCT Banner University PAGE 2214:52:57 Calculate Statistics Salary PEPCSAL

* * * REPORT CONTROL INFORMATION * * *

Report Name: PEPCSAL

Calculate Stats Annual Salary As of: 01-JAN-2002Calculate Projected Stats Annual Salary: YCalculate Projected Stats Annual Salary As of: 31-DEC-2002Delete Projected Stats Annual Salaries: NCalculate Longevity Amount: YInclude Premium Earnings: NInclude Additional Earnings: NInclude Shift Differential Earnings: N



Employee Demographic Extract Process (PEPEDEX)

This process generates an employee’s demographic and salary information. This extract process also incorporates the salary information originally generated by the PEPCSAL process.

Fields MIS Element Element Name Description

EB12 Annual Salary This MIS element has been modified to capture the employee’s annual salary calculated by the PEPCSAL process by including all earn codes that have been classified as an Additional Earning on the PTREARN form.

Additional earnings also include shift differential, longevity, and earn codes not identified as stipends on PTREARN, and are listed as default earnings for a job assignment on NBAJOBS that has been paid up to the As of report date.

This resolves RPE #34836.



Employee Assignment Extract Process (PEPAEXT)

The derivation of the following MIS elements have been modified for non-faculty reporting as below:


Report Header District/Division The PEPAEXT process collects job assignment data of faculty and non-faculty. This information is sorted by District/Division code followed by an alphabetical listing of employees at each job location.

Previously, the district codes were being extracted from the PEAJACT. With this release this information will now be drawn from the NBAJOBS form.

EJ01 Assignment Type For non-faculty employees, the 2-character alphanumeric value of this MIS element is evaluated as follows:

The first character of the EJ01 element is derived from the value of the MIS Occ Code specified for a corresponding EEO Skill Code on the PTVESKL form.

The second character of this element represents the job status of the relevant position, and is derived from NBAJOBS as follows:

• If the job status is ‘Active’, an ‘N’ is printed in the second position.

• If the job status is ‘Leave’, (includes all leave combinations), the process prints an ‘L’ in the second position.

• If the job status is ‘Terminated’, the process prints an ‘N’ in the second position, and the following message is displayed in the log file: *WARNING*: Job status is terminated.




EJ03 Account Code For non-faculty employees, the account code is obtained for each position/suffix combination on NBAJOBS as follows:

When Banner Finance is installed, the process considers the value of the Program Code field in the FOAPAL distribution for each position/suffix combination on NBAJOBS.

When Banner Finance is not installed, this MIS element will not be reported.

EJ08 Assignment FTE For non-faculty staff, the value of this MIS element was originally being drawn from the PEAJACT. It is now derived from the Job FTE field on the Employee Jobs Form (NBAJOBS).



Section 13 CA-MIS Reporting Enhancements For 2003 - TechnicalNew Tables


Section 13 CA-MIS Reporting Enhancements For 2003 - Technical

This section documents the changes made to the database for the CA-MIS enhancements for 2003.


New Tables

Employee Assignment Data Table (PERNASG)

This table stores the job assignment data generated by the Employee Assignment Extract Process (PEPAEXT).

Database Column Null? Data Type

PERNASG_REPORT_NO NOT NULL VARCHAR2(5)

PERNASG_PIDM NOT NULL NUMBER(8)

PERNASG_POSN NOT NULL VARCHAR2(6)

PERNASG_SUFF NOT NULL VARCHAR2(2)

PERNASG_POSN_STATUS NOT NULL VARCHAR2(1)

PERNASG_EFFECTIVE_DATE NOT NULL DATE

PERNASG_SOURCE NOT NULL VARCHAR2(1)

PERNASG_REPORT_IND NOT NULL VARCHAR2(1)

PERNASG_USER_ID NOT NULL VARCHAR2(30)

PERNASG_ACTIVITY_DATE NOT NULL DATE

PERNASG_REPORT_DATE NOT NULL DATE

PERNASG_TERM_CODE VARCHAR2(6)

PERNASG_CRN VARCHAR2(5)

PERNASG_CATEGORY VARCHAR2(2)

PERNASG_NIST_CODE VARCHAR2(4)

Section 13 CA-MIS Reporting Enhancements For 2003 - Technical Changed Tables


Changed Tables

For this release, new columns have been added to the following tables:

Earnings Code Rule Table (PTREARN)

Job/Hiring Location Rule Table (PTRJBLN)

PERNASG_COLL_CODE VARCHAR2(2)

PERNASG_DEPT_CODE VARCHAR2(4)

PERNASG_DICD_CODE VARCHAR2(3)

PERNASG_TERM_IDENTIFIER VARCHAR2(3)

PERNASG_SSN VARCHAR2(9)

PERNASG_ASSIGN_TYPE VARCHAR2(2)

PERNASG_LEAVE_STATUS VARCHAR2(1)

PERNASG_ACCT_CODE VARCHAR2(6)

PERNASG_WEEKLY_HRS NUMBER(5, 2)

PERNASG_HOURLY_RATE NUMBER(11, 6)

PERNASG_FTE NUMBER(6, 3)



PTREARN_MIS_ADDL_EARN_IND NOT NULL VARCHAR2(1)


PTRJBLN_DICD_CODE VARCHAR2(3)

Section 13 CA-MIS Reporting Enhancements For 2003 - TechnicalChanged Scripts


Changed Scripts


PTREARN1.SQL and PTREARN2.SQL

PTREARN1.SQL adds the PTREARN_MIS_ADDL_EARN_IND column to the PTREARN table for the Additional Earnings indicator.

PTREARN2.SQL sets the default value of the above column to ‘N’.


PTREARN3.SQL sets the PTREARN_MIS_ADDL_EARN_IND column as a NOT NULL field.

PTREARN4.SQL adds a comment to this column.

PTRJBLN1.SQL and PTRJBLN2.SQL

PTRJBLN1.SQL adds the PTRJBLN_DICD_CODE column to the PTRJBLN table to store the CA-MIS District code.

PTRJBLN2.SQL adds a comment to the above column.

PERNASG1.SQL, PERNASG2.SQL and PERNASG3.SQL

PERNASG1.SQL adds the new table, PERNASG to hold job assignment data generated by the PEPAEXT process.

PERNASG2.SQL creates a unique index PERNASG_KEY_INDEX on the PERNASG table.

PERNASG3.SQL adds a comment for each column of PERNASG.

Section 13 CA-MIS Reporting Enhancements For 2003 - Technical Changed Scripts



Section 14 OSHA Reports for 2003 - FunctionalOverview


Section 14 OSHA Reports for 2003 - Functional

Overview


The US Department of Labor, Occupational Safety and Health Administration (OSHA) is the federal authority which oversees the standards of health and safety plans adopted by various industries in the United States of America. The health and safety plans implemented in each industrial sector within the USA must comply with the safety standards established by this agency.

All employers are required to document and record any work-related injuries and illnesses occurring at each job location on two OSHA forms:

• Form 300 - Log of Work-Related Injuries and Illnesses (replaces OSHA Form 101) and

• Form 300A - Summary of Work-related Injuries and Illnesses (replaces OSHA Form 200)

Employers must post Form 300A by February 1 following the year for which the incidents were recorded, for a duration of three (3) months.

The Occupational Safety and Health Administration (OSHA) Reports have been revised for year 2003 with the following changes made in Banner:

• A new category has been added to the Injury and Illness Type field on the Health and Safety Incident Form (PEAHSIN)

• The report formats of OSHA Form 300 and Form 300A have been updated to meet the requirements for 2003 tracking and 2004 reporting.

Changed Form

The following Human Resources Form has been modified.

Application Form

PEAHSIN Health and Safety Incident Form

Section 14 OSHA Reports for 2003 - Functional Changed Form


Health and Safety Incident Form (PEAHSIN)

This form maintains all information regarding health and safety incidents occurring at an enterprise. Data entered on this form is used to generate OSHA Reports.

Involved Persons and Parties Window

This window maintains information relating to medical conditions resulting from incidents at a work location. Access this window from the Options menu of the Health and Safety Incident Form (PEAHSIN).

Incidents of Hearing Loss are now categorized separately in the Injury and Illness Type field of the Involved Persons or Parties window of the Health and Safety Incident Form (PEAHSIN). This new category has been added to the corresponding drop-down list.

Section 14 OSHA Reports for 2003 - FunctionalChanged Report


Changed Report

OSHA Form 300/300A (PEROSHA)

The following changes have been made to the OSHA Reports - Form 300, Log of Work-related Injuries and Illnesses Section:

• Hearing loss incidents are now reported under the (M5)Hearing Loss field on the report

• Incidents of all other illnesses are now reported under a new (M6) All Other Illnesses field and

• Order of the existing columns (K) and (L) have been reversed, namely, Column (K) now corresponds to the Away from Work field, and Column (L) corresponds to the On Job Transfer or Restrictions field.

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Injury and Illness Type

Select the employee’s injury or illness type occurring from the drop-down list. Options now include:

None

Injuries

Skin Disorder

Respiratory Conditions

Poisonings

Hearing Loss

All Other Illnesses

SunGard SCT delivers the above list of predefined values as seed data.

Section 14 OSHA Reports for 2003 - Functional Changed Report


OSHA Form 300A - Summary Information Section displays a summary of the information reported in Form 300. This section of the report has been modified in the following aspects:

• The total count relating to incidents of Hearing Loss (Column M 5) is now reported under the Injury and Illness Types field.

• The order of the columns in the Number of Days block has been reversed.

The Total Number of Days Away from Work is reported first, followed by the Total Number of Days of Job Transfer or Restriction.

A sample of the modified OSHA reports, Form 300 and Form 300A have been provided in the following pages.


Human Resources/Position ControlRelease 7.0 January 2005 193 Release Guide Confidential

Report Sample—OSHA Form 300: See the following pages



REPORT: PEROSHA Banner University PAGE 1 of 1 4 Country View Road Malvern,PA,19355

OSHA Form 300

Incidents From 01-JAN-2003 to 31-DEC-2003___________________________________________________________________________________________________________________________________ Identify the Person Describe the Case Classify the Case No Of Days Injury and Illness Type___________________________________________________________________________________________________________________________________ (A) (B) (C) (D) (E) (F) (G) (H) (I) (J) (K) (L) (M1) (M2) (M3) (M4) (M5) (M6)Case No Employee Name/ Date of Injury/Illness/ Death Days Job Other Away On job Injury Skin Resp. Poison Hearing All Job Title Where the event away trans record- from trans Dis- Cond. Loss other occurred/ from or able work or Order ill Description/ Work restr cases restr___________________________________________________________________________________________________________________________________

931 25-AUG-2002 X Director Skin Disease

947 Peggy Olsen 03-FEB-2003 X 7 Assistant Direc Wrist - Carpal Tunnel Syn

951 Heidi A Meyer 22-MAR-2003 X X Skin Disease

953 Eileen Innis 06-APR-2003 X 4 X Deafness

970 Peggy Olsen 31-OCT-2003 X 61 X Assistant Direc Skin Disease

970 Privacy Case 31-OCT-2003 X Deafness

1017 Judi Croft 27-SEP-2002 X 98 X Receiving/Delivery Deafness ______________________________________________________________________________ Page totals : 1 2 2 105 65 1 1 4



Report Sample—OSHA Form 300A: See the following pages



REPORT: PEROSHA Banner University 4 Country View Road Malvern,PA,19355 Industrial Description: HIGHER EDUCATION SIC Code: 5461 OSHA Form 300A Incidents From 01-JAN-2003 to 31-DEC-2003________________________________________________________________________________________________________________________________Number of cases Total Number of Total Number of Total Number of Total number Cases with Days Cases with job other recordable of Deaths away from work transfer or restriction cases (G) (H) (I) (J) 1 2 2________________________________________________________________________________________________________________________________Number of Days Total Number of days Total Number of days of away from work job transfer or restriction (K) (L) 105 65________________________________________________________________________________________________________________________________Injury and Illness Types------------------------Total number of...(M1) Injuries 1(M2) Skin disorders 1(M3) Respiratory Conditions(M4) Poisonings(M5) Hearing Loss 4(M6) All other illnesses________________________________________________________________________________________________________________________________Employment Information----------------------Annual average number of employees: 15

Total hours worked by all employees last year: 10310

I certify that I have examined this document and that to the best of my knowledge, the entries are true, accurate, and complete.________________________________________________________________________________________________________________________________Company Executive Title

________________________________________________________________________________________________________________________________Phone Date



REPORT: PEROSHA Banner University 4 Country View Road Malvern,PA,19355

OSHA Form 300/300A

Incidents From 01-JAN-2003 to 31-DEC-2003 * * * REPORT CONTROL INFORMATION * * *

Parameter Name Value Source Message________________________ ______________________________ ________________________ _________________________________________Parameter Seq No: 1367779Start Date: 01-JAN-2003 TableStop Date 31-DEC-2003 TableIndustrial Description: HIGHER EDUCATION TableSIC Code: 5461 TableEmployer Code: OS TableExclude Employee ClassECLS Code: 02 Table

Total Number of Records Printed : 7




Section 14 OSHA Reports for 2003 - FunctionalObsolete Reports


Obsolete Reports

OSHA Form 101 (PERO101) and OSHA Form 200 (PERO200)

The previous version of the OSHA Reports, i.e., Form 101 (PERO101) and Form 200 (PERO200) have been removed with this release of Banner Human Resources.

Previously, the above reports had only been removed from the Banner Human Resources Menu, but could still be accessed from the Job Submissions window in Banner.

This release obsoletes PERO101 and PERO200 reports.

Section 14 OSHA Reports for 2003 - FunctionalObsolete Reports



Section 15 OSHA Reports for 2003 - TechnicalNew Script


Section 15 OSHA Reports for 2003 - Technical

This section documents the technical changes effected for the OSHA enhancement.


New Script

Note: The following script is run as a part of the upgrade process for the release.

PERHSIM1.SQL

This script adds a comment for the new Injury and Illness Type category in the Health and Safety Incident Medical Table (PERHSIM).

Section 15 OSHA Reports for 2003 - Technical New Script



Section 16 IPEDS Reports for 2003 - FunctionalOverview


Section 16 IPEDS Reports for 2003 - Functional

Overview


The Integrated Postsecondary Education Data System (IPEDS) is a survey conducted by the National Center for Education Statistics (NCES) to collect post-secondary education data. This survey which is conducted on a biennial basis, is a mandatory requirement for year 2003, and applies to all higher education institutions in the United States only.

To comply with the regulatory requirements, the following IPEDS reports have been modified in Banner Human Resources for the removal of the Other Administrative job category A0 (A zero):

• Formats of the Fall Staff Survey (S1-Long) Report and Web File Upload for S1-Long

• IPEDS Summary Report (PEREO61, -2)


For your convenience, the updated instructions for reporting IPEDS is provided on page 235.

Note: All client sites must review their data for any records using the A0 job category and manually change the EEO Skill Code to one of the currently accepted values of 10 through 90. Any records with the A0 Skill Code will not be included in the IPEDS reports.

Section 16 IPEDS Reports for 2003 - Functional Overview



Section 16 IPEDS Reports for 2003 - Functional Changed Reports


Changed Reports

The Other Administrative job category associated with the EEO skill code, A0 (A zero), has been removed from the following reports:

• IPEDS Summary Report (PEREO61, -2) and


Accordingly, the Web File Upload format for S1-Long has also been updated to reflect this change.

The following pages provide a sample of the modified report layouts.



IPEDS Summary Report (PEREO61, -2)

Report Sample—see the following pages



UNITID= 2 BBU Employer FICE= 23000 SECTOR= 200____________________________________________________________________________________________________________________________________ Fall Staff Survey, 2002 S1-Long Part A - Full-Time Faculty (Instruction/Research/Public Services) By Racial/ethnic Category, Gender, Contract Length and Salary Class Intervals Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Faculty by contract length alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. and salary class intervals Native Islander unknown ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Less than 9 month salary 1 contract 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ 9/10 month salary contract 2 Below $30,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 3 30,000 - 39,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 4 40,000 - 49,999 1 0 0 0 0 1 0 0 0 0 0 0 0 0 1 1 5 50,000 - 64,999 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 6 65,000 - 79,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 7 80,000 - 99,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 8 100,000 and above 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0____________________________________________________________________________________________________________________________________ Total 9/10 month salary 9 contracts (sum of lines 2-8) 1 0 1 0 0 1 0 0 0 0 0 1 0 0 2 2____________________________________________________________________________________________________________________________________ 11/12 month salary contract 10 Below $30,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 11 30,000 - 39,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 12 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 13 50,000 - 64,999 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 14 65,000 - 79,999 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 15 80,000 - 99,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 16 100,000 and above 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1____________________________________________________________________________________________________________________________________ Total 11/12 month salary 17 contracts (sum of lines 10-16) 0 0 1 1 0 0 0 0 0 0 0 1 1 0 2 2____________________________________________________________________________________________________________________________________ Part A total (sum of lines 1,9,17) 18 (must equal Part F, line 99) 1 0 2 1 0 1 0 0 0 0 0 2 1 0 4 4____________________________________________________________________________________________________________________________________



UNITID= 2 BBU Employer FICE= 23000 SECTOR= 200____________________________________________________________________________________________________________________________________

Fall Staff Survey, 2002 S1-Long Part B - All Other Full-Time Employees By Racial/ethnic Category, Gender, Primary Occupational Activity and Salary Class Intervals Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Employees by primary alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. occupational activity and Native Islander unknown salary class intervals ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Executive/administrative/ managerial 19 Below $30,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 20 30,000 - 39,999 0 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 21 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 22 50,000 - 64,999 0 0 0 0 0 0 1 0 0 0 1 2 0 0 2 2 23 65,000 - 79,999 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 24 80,000 - 99,999 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 25 100,000 and above 0 0 0 0 0 0 0 1 0 0 0 0 0 0 0 1____________________________________________________________________________________________________________________________________ Total Executive/administrative /managerial 26 (sum of lines 19-25) 0 1 0 0 0 0 1 1 0 1 1 3 0 0 2 6____________________________________________________________________________________________________________________________________ Other professionals (support/service) 35 Below $30,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 36 30,000 - 39,999 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 0 37 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 0 1 1 0 1 1 38 50,000 - 64,999 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 39 65,000 - 79,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 40 80,000 - 99,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 41 100,000 and above 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Total other professionals (support service) 42 (sum of lines 35-41) 0 0 0 0 1 0 0 0 0 0 1 1 1 0 3 1____________________________________________________________________________________________________________________________________




Fall Staff Survey, 2002 S1-Long Part B - All Other Full-Time Employees By Racial/ethnic Category, Gender, Primary Occupational Activity and Salary Class Intervals Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Employees by primary alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. occupational activity and Native Islander unknown salary class intervals ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Technical and paraprofessional 43 Below $20,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 44 20,000 - 29,999 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 45 30,000 - 39,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 46 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 47 50,000 and above 0 0 0 0 0 0 0 0 0 1 0 0 1 0 1 1____________________________________________________________________________________________________________________________________ Total technical and paraprofessionals 48 (sum of lines 43-47) 0 0 0 0 0 0 0 0 0 1 0 0 1 1 1 2____________________________________________________________________________________________________________________________________ Clerical and secretarial 49 Below $20,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 50 20,000 - 29,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 51 30,000 - 39,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 52 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 0 53 50,000 and above 0 0 0 0 0 0 0 0 0 0 2 1 0 0 2 1____________________________________________________________________________________________________________________________________ Total clerical and secretarial 54 (sum of lines 49-53) 0 0 0 0 0 0 0 0 0 0 3 1 0 0 3 1____________________________________________________________________________________________________________________________________ Skilled crafts 55 Below $20,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 56 20,000 - 29,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 57 30,000 - 39,999 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0 58 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 59 50,000 and above 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0____________________________________________________________________________________________________________________________________ Total skilled crafts 60 (sum of lines 55-59) 0 0 0 0 0 0 0 0 2 0 0 0 0 0 2 0____________________________________________________________________________________________________________________________________




Fall Staff Survey, 2002 S1-Long Part B - All Other Full-Time Employees By Racial/ethnic Category, Gender, Primary Occupational Activity and Salary Class Intervals Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Employees by primary alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. occupational activity and Native Islander unknown salary class intervals ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Service/Maintenance 61 Below $20,000 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 62 20,000 - 29,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 63 30,000 - 39,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 64 40,000 - 49,999 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 65 50,000 and above 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Total service/maintenance 66 (sum of lines 61-65) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Total all full-time employees (sum of lines 18,26,42,48,54 67 60 and 66) 1 1 2 1 1 1 1 1 2 2 5 7 3 1 15 14____________________________________________________________________________________________________________________________________




Fall Staff Survey, 2002 S1-Long Part D - Part-Time Employees By Racial/ethnic Category, Gender and Primary Occupational Activity Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Employees by primary alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. occupational activity and Native Islander unknown ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Part-Time Employees____________________________________________________________________________________________________________________________________ Faculty (Instruction/research/ 68 public service) 0 0 0 0 0 0 0 0 3 0 0 0 0 0 3 0____________________________________________________________________________________________________________________________________ Instruction/research 69 assistants 0 0 2 0 0 0 0 0 0 0 0 0 0 0 2 0____________________________________________________________________________________________________________________________________ Executive/administrative/ 70 managerial 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Other professionals 71 (support/service) 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Technical and 72 paraprofessionals 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ 73 Clerical and secretarial 0 0 0 0 0 0 0 0 1 1 0 0 0 0 1 1____________________________________________________________________________________________________________________________________ 74 Skilled crafts 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ 75 Service/Maintenence 0 0 0 0 0 0 0 0 0 0 2 0 0 0 2 0____________________________________________________________________________________________________________________________________ Total part-time employees 76 (sum of lines 68-75) 0 0 2 0 0 0 0 0 4 1 2 0 0 0 8 1____________________________________________________________________________________________________________________________________




Fall Staff Survey, 2002 S1-Long Part E - Summary of Full-Time and Part-Time Employees by Racial/ethnic Category and Gender Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Full-time and part-time alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. employees Native Islander unknown ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Total full-time and part time employees (sum of 77 Parts A, B, and D) 1 1 4 1 1 1 1 1 6 3 7 7 3 1 23 15____________________________________________________________________________________________________________________________________




Fall Staff Survey, 2002 S1-Long Part F - Tenure of Full-Time Faculty (Instruction/Research/Public Service) By Racial/ethnic Category, Gender and Academic Rank Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Faculty by tenure and alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. academic rank Native Islander unknown ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Faculty with tenure 78 Professors 0 0 1 1 0 0 0 0 0 0 0 0 0 0 1 1 79 Associate Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 80 Assistant Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 81 Instructors 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 1 82 Lecturers 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0 83 Other Faculty 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Total faculty with tenure 84 (sum of lines 78-83) 0 0 1 1 0 0 0 0 0 0 0 1 1 0 2 2____________________________________________________________________________________________________________________________________ Non-tenured faculty (Those on tenure track) 85 Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 86 Associate Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 87 Assistant Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 88 Instructors 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0 89 Lecturers 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 90 Other Faculty 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Total non-tenured faculty (Those on tenure track) 91 (sum of lines 85-90) 1 0 0 0 0 0 0 0 0 0 0 0 0 0 1 0____________________________________________________________________________________________________________________________________




Fall Staff Survey, 2002 S1-Long Part F - Tenure of Full-Time Faculty (Instruction/Research/Public Service) By Racial/ethnic Category, Gender and Academic Rank Employees on the payroll of the Institution as of November 1, 2002____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Faculty by tenure and alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. academic rank Native Islander unknown ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ Non-tenured faculty (Those not on tenure track) 92 Professors 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1 93 Associate Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 94 Assistant Professors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 95 Instructors 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 96 Lecturers 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 97 Other Faculty 0 0 1 0 0 0 0 0 0 0 0 1 0 0 1 1____________________________________________________________________________________________________________________________________ Total non-tenured faculty (Those not on tenure track) 98 (Sum of lines 92-97) 0 0 1 0 0 1 0 0 0 0 0 1 0 0 1 2____________________________________________________________________________________________________________________________________ Total Faculty (sum of lines 84,91, and 98) 99 (must equal Part A, line 18) 1 0 2 1 0 1 0 0 0 0 0 2 1 0 4 4____________________________________________________________________________________________________________________________________*Institutions without standard academic ranks should report full-time faculty here.




Fall Staff Survey, 2002 S1-Long Part G - New Hires By Racial/ethnic Category, Gender and Primary Occupational Activity____________________________________________________________________________________________________________________________________ American Nonresident Black Indian or Asian or Hispanic White Race/Line Employees by primary alien non-Hispanic Alaskan Pacific non-Hispanic ethnicity Grand TotalNo. occupational activity Native Islander unknown ________________________________________________________________________________________________ Men Women Men Women Men Women Men Women Men Women Men Women Men Women Men Women____________________________________________________________________________________________________________________________________ New Hires (Full-time between July 1 and October 31, 2002)____________________________________________________________________________________________________________________________________ Faculty____________________________________________________________________________________________________________________________________100 a. Tenured 0 0 1 0 0 0 0 0 0 0 0 1 1 0 2 1____________________________________________________________________________________________________________________________________101 b. Non-tenured on track 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________102 c. Non-tenured not on track 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 1____________________________________________________________________________________________________________________________________ Executive/administrative/103 managerial 0 0 0 0 0 0 1 0 0 0 0 1 0 0 1 1____________________________________________________________________________________________________________________________________ Other professionals105 (support/service) 0 0 0 0 0 0 0 0 0 0 0 0 1 0 1 0____________________________________________________________________________________________________________________________________ Technical and106 paraprofessionals 0 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1____________________________________________________________________________________________________________________________________107 Clerical and secretarial 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________108 Skilled crafts 0 0 0 0 0 0 0 0 1 0 0 0 0 0 1 0____________________________________________________________________________________________________________________________________109 Service/maintenance 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0____________________________________________________________________________________________________________________________________ Total (sum of lines 100-103110 and 105-109) 0 0 1 0 0 1 1 0 1 1 0 2 2 0 5 4____________________________________________________________________________________________________________________________________



PAGE 1REPORT : PEREO61 SCT Banner University RUN DATE 10-SEP-2003 IPEDS Summary Report RUN TIME 04:12 PM


Parameter Name Value Source Message_________________ ______________________________ _______ ____________________________________________________________Parameter Seq No: 1355479Year: 2002Employer Code: BB1



Web Upload File



Report SampletUNITID=2,SURVSECT=S1,PART=A,LINE=4,RACE=1,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=4,RACE=3,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=5,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=8,RACE=2,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=12,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=13,RACE=7,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=14,RACE=2,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=A,LINE=16,RACE=2,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=20,RACE=1,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=22,RACE=4,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=22,RACE=6,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=22,RACE=6,GENDER=2,COUNT=2UNITID=2,SURVSECT=S1,PART=B,LINE=23,RACE=5,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=24,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=25,RACE=4,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=36,RACE=3,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=37,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=37,RACE=7,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=38,RACE=6,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=44,RACE=7,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=47,RACE=5,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=47,RACE=7,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=52,RACE=6,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=53,RACE=6,GENDER=1,COUNT=2UNITID=2,SURVSECT=S1,PART=B,LINE=53,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=57,RACE=5,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=B,LINE=59,RACE=5,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=D,LINE=68,RACE=5,GENDER=1,COUNT=3UNITID=2,SURVSECT=S1,PART=D,LINE=69,RACE=2,GENDER=1,COUNT=2UNITID=2,SURVSECT=S1,PART=D,LINE=73,RACE=5,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=D,LINE=73,RACE=5,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=D,LINE=75,RACE=6,GENDER=1,COUNT=2UNITID=2,SURVSECT=S1,PART=F,LINE=78,RACE=2,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=78,RACE=2,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=81,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=82,RACE=7,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=88,RACE=1,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=92,RACE=3,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=97,RACE=2,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=F,LINE=97,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=100,RACE=2,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=100,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=100,RACE=7,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=102,RACE=3,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=103,RACE=4,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=103,RACE=6,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=105,RACE=7,GENDER=1,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=106,RACE=5,GENDER=2,COUNT=1UNITID=2,SURVSECT=S1,PART=G,LINE=108,RACE=5,GENDER=1,COUNT=1



IPEDS Detail Report (PEREO6D)

Report Sample—see the following pages



PAGE 1REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________NO RECORDS EXIST FOR CONTRACT GROUP <9-10 Month Faculty AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 1 : 9-10 Month Faculty____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 1 BEBG21-00 BEB21 BN 44,055 Erskin, David R 100420011 B 11001 N N 01-JUL-2001 Y

Total Annual Salary: 44,055 Tenure Code: 2 Salary Level: 3 Tenure Ind: O On-Track Report Column: 1 Rank: 4 Instructors____________________________________________________________________________________________________________________________________ Salary Level 3 Column 1 Non-Resident Alien Men COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 F 5 BEBG21-00 BEB21 B8 47,250 Moroney, Valerie 110110013 B 12201 Y Y 01-SEP-2002 N

Total Annual Salary: 47,250 Tenure Code: N Salary Level: 3 Tenure Ind: N Non-Tenured Report Column: 6 Rank: 1 Professors____________________________________________________________________________________________________________________________________ Salary Level 3 Column 6 American Indian or Alaskan Women COUNT: 1 Native____________________________________________________________________________________________________________________________________ Salary Level 3 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 F 1 BEBG21-00 BEB21 B8 55,000 Allen, Tracy 110110001 B 11101 Y Y 01-SEP-2002 Y

Total Annual Salary: 55,000 Tenure Code: 1 Salary Level: 4 Tenure Ind: T Tenured Report Column: 12 Rank: 4 Instructors



PAGE 2REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 1 : 9-10 Month Faculty____________________________________________________________________________________________________________________________________ Salary Level 4 Column 12 White (non-Hispanic) Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 4 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 2 BEBG23-00 BEB23 BN 110,055 West, Paul 100420030 B 11001 Y Y 01-JUL-2000 N

Total Annual Salary: 110,055 Tenure Code: Salary Level: 7 Tenure Ind: Report Column: 3 Rank:____________________________________________________________________________________________________________________________________ Salary Level 7 Column 3 Black (non-Hispanic) Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 7 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Employee Skill 20 : Faculty Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 2____________________________________________________________________________________________________________________________________Total Contract Group 1 : 9-10 Month Faculty Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 2____________________________________________________________________________________________________________________________________



PAGE 3REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 2 : 11-12 Month Faculty____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 F 1 BEBG20-00 BEB20 BM 46,255 Adams, April CD0000034 B 11001 Y Y 7962377 01-JAN-2001 N

Total Annual Salary: 46,255 Tenure Code: Salary Level: 3 Tenure Ind: Report Column: 12 Rank:____________________________________________________________________________________________________________________________________ Salary Level 3 Column 12 White (non-Hispanic) Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 3 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 6 BEBG20-00 BEB20 B7 63,000 Pentland, Bryan 110110014 B 12101 Y Y 01-SEP-2002 Y

Total Annual Salary: 63,000 Tenure Code: 1 Salary Level: 4 Tenure Ind: T Tenured Report Column: 13 Rank: 5 Lecturers____________________________________________________________________________________________________________________________________ Salary Level 4 Column 13 Race/Ethnicity Unknown Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 4 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 2 BEBG20-00 BEB20 B7 65,000 Bates, Martyn 110110002 B 11001 Y Y 01-SEP-2002 N

Total Annual Salary: 65,000 Tenure Code: 1 Salary Level: 5 Tenure Ind: T Tenured Report Column: 3 Rank: 1 Professors____________________________________________________________________________________________________________________________________ Salary Level 5 Column 3 Black (non-Hispanic) Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0



PAGE 4REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 2 : 11-12 Month Faculty____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 F 2 BEBG20-00 BEB20 BM 62,055 Havens, Teresa A 100420012 B 11001 Y Y 5923874 01-JUL-2000 N

Total Annual Salary: 62,055 Tenure Code: 1 Salary Level: 7 Tenure Ind: T Tenured Report Column: 4 Rank: 1 Professors____________________________________________________________________________________________________________________________________ Salary Level 7 Column 4 Black (non-Hispanic) Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 7 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Total Employee Skill 20 : Faculty Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 2________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________________Total Contract Group 2 : 11-12 Month Faculty Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 2____________________________________________________________________________________________________________________________________



PAGE 5REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002

____________________________________________________________________________________________________________________________________CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 F 3 BEBG01-00 BEB10 BG 30,055 Ross, Shawna CD0000012 B 11001 N N 01-JAN-2000 N

Total Annual Salary: 30,055 Tenure Code: Salary Level: 2 Tenure Ind: Report Column: 2 Rank:____________________________________________________________________________________________________________________________________ Salary Level 2 Column 2 Non-Resident Alien Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 2 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 M 4 BEBG10-00 BEB10 B1 63,000 Boice, Mathew 110110004 B 11101 Y Y 01-SEP-2002 Y

Total Annual Salary: 63,000 Tenure Code: Salary Level: 4 Tenure Ind: Report Column: 7 Rank:____________________________________________________________________________________________________________________________________ Salary Level 4 Column 7 Asian or Pacific Islander Men COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 M 1 BEBG01-00 BEB10 BG 52,500 Ames, Michael CD0000102 B 11002 Y Y 01-JAN-2002 N

Total Annual Salary: 52,500 Tenure Code: Salary Level: 4 Tenure Ind: Report Column: 11 Rank:____________________________________________________________________________________________________________________________________ Salary Level 4 Column 11 White (non-Hispanic) Men COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 F 1 BEBG01-00 BEB10 BG 52,500 Adams, A. C. P. CD0000007 B 11002 Y Y 01-JUL-2002 N

Total Annual Salary: 52,500 Tenure Code: Salary Level: 4 Tenure Ind: Report Column: 12 Rank:



PAGE 6REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 F 1 BEBG01-00 BEB10 BG 57,750 Adams, Mikayla DRC000003 B 11002 Y Y 01-JAN-2002 N

Total Annual Salary: 57,750 Tenure Code: Salary Level: 4 Tenure Ind: Report Column: 12 Rank:____________________________________________________________________________________________________________________________________ Salary Level 4 Column 12 White (non-Hispanic) Women COUNT: 2____________________________________________________________________________________________________________________________________ Salary Level 4 Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 2____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 F 3 BEBG10-00 BEB10 BG 75,055 Walter, Kelly A 100420014 B 11001 Y Y 01-JUL-2000 Y

Total Annual Salary: 75,055 Tenure Code: Salary Level: 5 Tenure Ind: Report Column: 10 Rank:____________________________________________________________________________________________________________________________________ Salary Level 5 Column 10 Hispanic Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 F 1 BEBG01-00 BEB10 BG 36,000 Adams, Anne DRC000000 B 11001 Y Y 01-JAN-2002 N BEBG01-TI BEB10 BG 47,250

Total Annual Salary: 83,250 Tenure Code: Salary Level: 6 Tenure Ind: Report Column: 12 Rank:____________________________________________________________________________________________________________________________________ Salary Level 6 Column 12 White (non-Hispanic) Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 6 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________



PAGE 7REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 10 F 4 BEBG01-00 BEB10 BG 115,555 Patterson, Stephanie J 100420022 B 11001 Y Y 7960980 01-JUL-2000 N

Total Annual Salary: 115,555 Tenure Code: Salary Level: 7 Tenure Ind: Report Column: 8 Rank:____________________________________________________________________________________________________________________________________ Salary Level 7 Column 8 Asian or Pacific Islander Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 7 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Total Employee Skill 10 : Executive/Admin and managerial Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 6____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 30 M 5 BEBG30-00 BEB30 BH 35,255 Schoen, Adam K 100420016 B 11001 Y Y 5913877 01-JUL-2000 Y

Total Annual Salary: 35,255 Salary Level: 2 Report Column: 5____________________________________________________________________________________________________________________________________ Salary Level 2 Column 5 American Indian or Alaskan Men COUNT: 1 Native____________________________________________________________________________________________________________________________________ Salary Level 2 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 30 F 1 BEBG30-00 BEB30 BH 46,255 Adams, Nicole CD0000035 B 11001 Y Y 01-SEP-2000 N

Total Annual Salary: 46,255 Salary Level: 3 Report Column: 12



PAGE 8REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM

AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________ Salary Level 3 Column 12 White (non-Hispanic) Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 30 M 6 BEBG30-00 BEB30 B2 47,250 De'ath, Tim 110110006 B 12201 NR N GM492380 01-SEP-2002 Y

Total Annual Salary: 47,250 Salary Level: 3 Report Column: 13____________________________________________________________________________________________________________________________________ Salary Level 3 Column 13 Race/Ethnicity Unknown Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 3 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 30 M 1 BEBG30-00 BEB30 BH 52,855 Adams, Vaughn CD0000033 B 11001 Y Y 01-JAN-2001 N

Total Annual Salary: 52,855 Salary Level: 4 Report Column: 11____________________________________________________________________________________________________________________________________ Salary Level 4 Column 11 White (non-Hispanic) Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 4 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Employee Skill 30 : Other professionals Column 15 Grand Total All Employees Men COUNT: 3 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 40 F 6 BEBG40-00 BEB40 BI 24,255 Starks, Wenda L 100420017 B 11001 Y Y 8675309 01-JUL-2000 Y

Total Annual Salary: 24,255 Salary Level: 2 Report Column: 14



PAGE 9REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________ Salary Level 2 Column 14 Race/Ethnicity Unknown Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 2 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 40 F 3 BEBG40-00 BEB40 B3 52,500 Griffin, Linda 110110007 B 12101 Y Y 01-SEP-2002 Y

Total Annual Salary: 52,500 Salary Level: 5 Report Column: 10____________________________________________________________________________________________________________________________________ Salary Level 5 Column 10 Hispanic Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 40 M 6 BEBG03-00 BEB40 BI 60,555 Tetsworth, Allen 100420024 B 11001 Y Y 8675310 01-JUL-2000 N

Total Annual Salary: 60,555 Salary Level: 5 Report Column: 13____________________________________________________________________________________________________________________________________ Salary Level 5 Column 13 Race/Ethnicity Unknown Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Total Employee Skill 40 : Technical and paraprofessional Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 2____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 50 M 1 MEA001-00 MEA01 03 44,400 Burroughs, Mark 001001002 B 11009 Y Y 4847566 01-JUL-2001 N

Total Annual Salary: 44,400 Salary Level: 4 Report Column: 11____________________________________________________________________________________________________________________________________ Salary Level 4 Column 11 White (non-Hispanic) Men COUNT: 1



PAGE 10REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM ____________________________________________________________________________________________________________________________________

CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________ Salary Level 4 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 50 M 1 MEA001-00 MEA01 03 65,000 Doral, Paul 001001004 B 11009 Y Y 9333561 01-AUG-2001 N

Total Annual Salary: 65,000 Salary Level: 5 Report Column: 11____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 50 M 1 MEA002-00 BEB50 03 83,250 Hines, Bill 001001008 B 11009 Y Y 258258 01-SEP-2001 N

Total Annual Salary: 83,250 Salary Level: 5 Report Column: 11____________________________________________________________________________________________________________________________________ Salary Level 5 Column 11 White (non-Hispanic) Men COUNT: 2____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 50 F 1 BEBG50-00 BEB50 BI 57,750 Adams, Shawna DRC000001 B 11001 Y Y 12-JUN-2002 N

Total Annual Salary: 57,750 Salary Level: 5 Report Column: 12____________________________________________________________________________________________________________________________________ Salary Level 5 Column 12 White (non-Hispanic) Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Total Employee Skill 50 : Clerical and secretarial Column 15 Grand Total All Employees Men COUNT: 3 Column 16 Grand Total All Employees Women COUNT: 1




____________________________________________________________________________________________________________________________________

CONTRACT GROUP 3 : Other Full Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 60 M 3 BEBG60-00 BEB60 BL 33,055 Hudson, Thomas W 100420019 B 11001 Y Y 01-JUL-2000 N

Total Annual Salary: 33,055 Salary Level: 3 Report Column: 9____________________________________________________________________________________________________________________________________ Salary Level 3 Column 9 Hispanic Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 3 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 60 M 3 BEBG60-00 BEB60 B6 57,750 Heyes, Alan 110110009 B 11101 Y Y 01-SEP-2002 N

Total Annual Salary: 57,750 Salary Level: 5 Report Column: 9____________________________________________________________________________________________________________________________________ Salary Level 5 Column 9 Hispanic Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Employee Skill 60 : Skilled crafts Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Contract Group 3 : Other Full Time Employees Column 15 Grand Total All Employees Men COUNT: 11 Column 16 Grand Total All Employees Women COUNT: 10



PAGE 12REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 4 : Part-Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 3 BEBG22-00 BEB22 B9 25,000 Bhama, Davinder 110110003 B 11001 Y Y 01-SEP-2002 N

Total Annual Salary: 25,000 Salary Level: 1 Report Column: 9____________________________________________________________________________________________________________________________________ Salary Level 1 Column 9 Hispanic Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 1 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 3 BEBG22-00 BEB22 BO 38,555 Hope, Allen M 100420013 B 11001 Y Y 2222222 01-JUL-2000 N

Total Annual Salary: 38,555 Salary Level: 2 Report Column: 9____________________________________________________________________________________________________________________________________ Salary Level 2 Column 9 Hispanic Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 2 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 20 M 3 BEBG22-00 BEB22 B9 42,000 Rodriguez, Carlos 110110015 B 11101 N N SV392804 01-SEP-2002 N

Total Annual Salary: 42,000 Salary Level: 3 Report Column: 9____________________________________________________________________________________________________________________________________ Salary Level 3 Column 9 Hispanic Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 3 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Employee Skill 20 : Faculty Column 15 Grand Total All Employees Men COUNT: 3 Column 16 Grand Total All Employees Women COUNT: 0



PAGE 13REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 4 : Part-Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 80 M 2 BEBG80-00 IRA01 BF 28,655 Davidson, Halbert T 100420020 B 11001 Y Y 5912150 01-JUL-2000 N

Total Annual Salary: 28,655 Salary Level: 1 Report Column: 3____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 80 M 2 BEBG80-00 IRA01 BB 47,250 Lau, Chris 110110011 B 11001 Y Y 01-SEP-2002 N

Total Annual Salary: 47,250 Salary Level: 1 Report Column: 3____________________________________________________________________________________________________________________________________ Salary Level 1 Column 3 Black (non-Hispanic) Men COUNT: 2____________________________________________________________________________________________________________________________________ Salary Level 1 Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Employee Skill 80 : Instruction/research assistant Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 50 F 3 BEBG50-00 BEB50 BJ 16,071 Tenbrink, Lea J 100420018 B 11001 Y Y 07041776 01-JUL-2000 N

Total Annual Salary: 16,071 Salary Level: 1 Report Column: 10____________________________________________________________________________________________________________________________________ Salary Level 1 Column 10 Hispanic Women COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 1 Column 15 Grand Total All Employees Men COUNT: 0 Column 16 Grand Total All Employees Women COUNT: 1



PAGE 14REPORT : PEREO6D SCT Banner University RUN DATE 10-SEP-2003 IPEDS Detail Listing RUN TIME 04:06 PM AS OF 01-NOV-2002____________________________________________________________________________________________________________________________________CONTRACT GROUP 4 : Part-Time Employees____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 50 M 3 BEBG50-00 BEB50 B4 80,000 Hardisty, Kevin 110110008 B 12201 Y Y 01-SEP-2002 N

Total Annual Salary: 80,000 Salary Level: 5 Report Column: 9____________________________________________________________________________________________________________________________________ Salary Level 5 Column 9 Hispanic Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Employee Skill 50 : Clerical and secretarial Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 70 M 1 BEBG70-00 BEB70 BK 24,255 Brown, James 100420010 B 11001 Y Y 01-JUL-2000 N BEBG70-01 BEB70 BK 9,055

Total Annual Salary: 33,310 Salary Level: 3 Report Column: 11____________________________________________________________________________________________________________________________________ Salary Level 3 Column 11 White (non-Hispanic) Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 3 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Empl Sex EEO Position PCLS ECLS Annual Employee name Employee Home Org Citizen Alien Reg Current SoftSkill Origin Salary ID Code Ind Number Hire Date $ 70 M 1 BEBG70-00 BEB70 B5 63,000 Keys, Robert 110110010 B 12101 Y Y 01-SEP-2002 N

Total Annual Salary: 63,000 Salary Level: 5 Report Column: 11____________________________________________________________________________________________________________________________________ Salary Level 5 Column 11 White (non-Hispanic) Men COUNT: 1____________________________________________________________________________________________________________________________________ Salary Level 5 Column 15 Grand Total All Employees Men COUNT: 1 Column 16 Grand Total All Employees Women COUNT: 0




____________________________________________________________________________________________________________________________________

CONTRACT GROUP 4 : Part-Time Employees____________________________________________________________________________________________________________________________________Total Employee Skill 70 : Service/Maintenance Column 15 Grand Total All Employees Men COUNT: 2 Column 16 Grand Total All Employees Women COUNT: 0____________________________________________________________________________________________________________________________________Total Contract Group 4 : Part-Time Employees Column 15 Grand Total All Employees Men COUNT: 8 Column 16 Grand Total All Employees Women COUNT: 1____________________________________________________________________________________________________________________________________GRAND TOTALS Column 15 Grand Total All Employees Men COUNT: 23 Column 16 Grand Total All Employees Women COUNT: 15____________________________________________________________________________________________________________________________________



Parameter Name Value Source Message_________________ ______________________________ _______ ____________________________________________________________Parameter Seq No: 1355449As of Date: 01-NOV-2002 DefaultEmployer Code: BB1 DefaultSoft Money Ind: N Default

Record Count 38

Line Count 55

Section 16 IPEDS Reports for 2003 - FunctionalIPEDS S1-Long Process Notes


IPEDS S1-Long Process Notes

Note: The information in these procedures applies only to United States installations and only to higher education institutions. When you use Banner for IPEDS reporting, the Installation field on the Installation Control Form (GUAINST) must be set to Higher Education; and the Location field on the Position Control Installation Rule Form (NTRINST) must be set to United States.

The Integrated Post Secondary Education Data System (IPEDS) S-1 Long Fall Staff Survey data is reported to the Bureau of the Census IPEDS/National Center for Education Statistics/IPEDS on a biennial basis. The reports are submitted in odd-numbered years (for example, in 1999, 2001, and 2003). The IPEDS S-1 Long reports must reflect your employee population as of a particular cutoff date and must be submitted by a specified date. The two dates may vary for each reporting year and are specified in the Release Guides that describe changes (if any) in IPEDS S-1 Long reporting for each of the reporting years.

The Fall Staff Survey (S1-Long) must be submitted to the National Center for Education Statistics (NCES) via the Web. The NCES Web site supplies forms on which you can enter data. Also, you can use an import file to upload the data to the NCES Web site. (See Running the IPEDS S-1 Long Reports and Web Upload below for further information.)

Impact of Faculty Tracking Method on IPEDS Reporting

Statistics for IPEDS-S1-Long reporting can come from either the Faculty Information Form (PEAFACD) or from the Faculty Action Tracking Form (PEAFACT) depending on how faculty information is tracked at your enterprise. When information is extracted from Banner to create the IPEDS S-1 Long reports, the processes determine whether the PEAFACD form is being used at the site or if the PEAFACT is being used.

PEAFACD

Faculty information for the IPEDS S1-Long reports is extracted from the Faculty Information Form (PEAFACD) when faculty data has not been entered into the PEAFACT form. This functionality existed prior to the Faculty enhancement.

PEAFACT

Faculty information from the IPEDS S1-Long reports is extracted from the Faculty Action Tracking Form (PEAFACT) once you have implemented this form at your site.



Faculty Enhancement

The Faculty enhancement associated with PEAFACT use impacts IPEDS S1-Long reporting in the following way. The tables that supply data change when reporting from the PEAFACT form. The tables associated with PEAFACT are the PERBFAC, PERAPPT, and the PERRANK tables. If any records exist on PEAFACT, use of the new faculty tracking information method is assumed.

When using PEAFACT, tenure and rank records can be effective dated. The PEREO61 and PEREO6D reports only use faculty data with an Approved Decision in Banner as of November 1, 2001. This means that PEREO61,-2, and PEREO6D select effective-dated records having the closest date equal to or less than November 1, 2001.

PEREO6D/PEREO61,2

Reporting for the IPEDS Detail Report (PEREO6D) and the IPEDS Summary Report (PEREO61,2) is impacted as described in previous sections. Information for Rank and Tenure may be reported from either the PEAFACD or the PEAFACT form.

Use of Banner HR for IPEDS S-1 Long Reporting

To produce the required IPEDS S1-Long reports, you must first ensure that all IPEDS S1-Long information on relevant Banner forms is correct. You can then execute the reports. Procedures for accomplishing these two functions are outlined below.

Verifying IPEDS S1-Long Data on Banner HR Forms

1. Ensure that the following forms display the codes listed below:

• The EEO Ethnic Code Validation Form (PTVEEOC) must contain the following ethnic codes:

Ethnic Code Description

1 White2 Black3 Hispanic4 Asian/Pacific Islander5 Alaskan Native/American Indian6 Race/Ethnicity Unknown



• The EEO Skill Code Validation Form (PTVESKL) must contain these EEO skill codes:

The value in the EEO Skill field in the Vacancy/Posting Information block of each employee’s Applicant Information Form (PAAAPPL) matches the appropriate skill code from the PTVESKL form.

The mandatory EEO skill codes can be broken down to a more detailed level. For example, the code 50 must be used to identify a clerical or secretarial employee. In addition, the code 5A could be used to identify a clerical or secretarial employee at the staff level and the code 5B could be used to identify an employee in the secretarial pool. The detailed skill breakdown can be used for a site specific purpose. It does not, however, have to be used for every installation.

• The EEO Contract Group Code Validation Form (PTVEEOG) establishes the contract group under which each employee will be reported. To ensure that the associated IPEDS S1-Long report data is correct, your codes must match the following codes:

These values are assigned to an employee class on the Regulatory Information window of the Employee Class Rule Form (PTRECLS).

• The EEO Salary Level Rule Form (PTREEOS) associates the EEO Contract Groups and the EEO Skill Codes established via the forms described above. It specifies the EEO Contract Group associated with each EEO Skill Code.

EEO Skill Code Description

10 Executive/Admin and managerial20 Faculty30 Other professionals40 Technical and paraprofessional50 Clerical and secretarial60 Skilled crafts70 Service/Maintenance80 Instruction/research assistant90 Other

EEOG Code Description

1 9-10 Month Full-Time Faculty2 11-12 Month Full-Time Faculty3 Other Full-Time Employees4 Part-Time Employees5 Less than 9 Month Full-Time Faculty6 Unreported



2. Check the Ethnicity Rule Form (PTRETHN). There are a few variations that can be used when establishing codes for this form. For example, only primary ethnic codes can be used, that is, only code 3 is used to identify employees in the Hispanic category. In another example, some of the codes are broken down to a more detailed level, that is, employees in category 3 are further identified as Cuban (code 3C), Mexican American (code 3M), etc.

If you have defined your ethnic codes to a more detailed level than 1, 2, 3, etc., the detailed codes will be consolidated to the primary code in both the IPEDS Detail Report and the IPEDS Summary Report.

3. If necessary, change the descriptions in the Rank Code Validation Form (PTVRANK) to match these codes.

The Rank Code Validation Form should contain only these values. It is strongly recommended that you do not change the above codes. Changing these values may cause the IPEDS S1-Long reports to contain incorrect data.

4. Review the Employer Rule Form (PTREMPR) to determine whether your State Sequence Number has been entered and is correct.To determine this number, look at the top of the second page of the survey document provided to you by the Department of Education.

The State Sequence Number field appears in the Report Information block on the IPEDS/EEO Required Fields window of PTREMPR.

5. Review your Citizenship Validation Form (STVCITZ) to ensure that the Citizen Indicator field has been checked for the group whose members are to be reported as U.S. citizens. When producing the IPEDS S1-Long reports, the system checks this form to determine which code identifies U.S. citizens.

6. Verify that the Citizenship field on each employee’s Identification Form (PPAIDEN) contains a value. The information in this field is required for all employees of U.S. Higher Education clients. You can use SQLPLUS to verify that none of your PPAIDEN records contains a Citizenship field with a null value.

Caution: If the Citizenship field is null for a particular employee, that employee will not be selected for the IPEDS S1-Long report.

Rank Code Description

1 Professor2 Associate Professors3 Assistant Professors4 Instructors5 Lecturers6 Other Faculty9 Non-Standard Academic Ranking



7. Enter a value in the Alien Registration Number field in the Passport Information block of the International Information Form (GOAINTL) for each non-citizen who is a resident alien. If you have a record of the registration number for an employee, enter that number. Otherwise, enter any value (for example, 999). If this field is left blank and the employee is identified as a non-citizen on the Identification Form (PPAIDEN), the employee will be reported in the Nonresident Alien column of the IPEDS S1-Long Report.

8. Ensure that the IPEDS Soft Money field on the Employee Form (PEAEMPL) has been set correctly for each employee so that employees can be identified for inclusion (or exclusion) from this category.

The IPEDS Soft Money field is on the Regulatory Information window of PEAEMPL. Check this field to include employees paid with “Soft Money” in IPEDS S1-Long reporting.

Note: When you run the IPEDS Detail Report (PEREO6D) with Y selected for the Soft Money Indicator parameter, the report will only include information on full-time staff paid with soft money. To produce a report containing information for all employees, including those paid with soft money, select N for the Soft Money Indicator parameter. (See Chapter 20, Reports and Processes, for more information on running the PEREO6D process.)

9. Ensure that the IPEDS Reporting Indicator field in the General Job Information block on the Employee Jobs Form (NBAJOBS) has been set correctly for each employee.

The IPEDS Reporting Indicator, when checked, means the job identified is IPEDS S1-Long reportable. This indicator allows more than one job to be reportable on the IPEDS Detail Report (PEREO6D) and the IPEDS Summary/Extract Report (PEREO61,-2). In order for this to work, the EEO contract group code must be 1-5 for all of the employee’s jobs that are checked as IPEDS S1-Long reportable; and each of these jobs must have the same employee skill code. (See the description of NBAJOBS in Chapter 10, Employee Administration, for further information on the use of the IPEDS Reporting Indicator field.)

10. Ensure that Rank and Tenure information is correct on either the Faculty Information Form (PEAFACD) or the Faculty Action Tracking Form (PEAFACT).

When entering records for a faculty employee, both a Rank and Tenure Appointment record must be entered. If a Tenure record is entered without a Rank record, the IPEDS PEREO61,-2 process may ignore the Tenure Code and count the employee in the Non-tenured (not on tenure track) section of Part F of the Fall Staff Survey.



Running IPEDS S1-Long Reports

When you have verified that all IPEDS S1-Long related material in the Banner forms is correct, you can run the IPEDS S1-Long reports using the procedure outlined below.

1. Run the IPEDS Detail Report (PEREO6D) through the Job Submission Process or the Host Process as described below.

Through the Job Submission Process:

Execute the PEREO6D report from the Job Submission Process Parameter Entry Form (GJAPCTL) using the following parameters:

Through the Host Process:

Through the host, enter the following parameters for the pereo6d report:

2. When the report has been printed, verify that employees are being reported in the expected categories by Skill, Sex, EEO Origin, and Salary Level.

Parameter Entry

As of Date 01-NOV-2003

Employer Code Valid employer code as defined on the Employer Rule Form (PTREMPR)

Soft Money Indicator N (This entry is used to select all employees.)orY (This entry selects only those employees having the Soft Money Indicator checked on PEAEMPL)

Parameter Entry

As of Date 01-NOV-2003


Soft Money Employees Only

N (This entry is used to select all employees.)orY (This entry selects only those employees having the Soft Money Indicator checked on PEAEMPL)



3. Run the IPEDS Summary Report extract process (PEREO61) and report process (PEREO62) through the Job Submission Process or the Host Process as instructed below.

Through the Job Submission Process:

Note: The PERE062 process will run automatically when PERE061 is run through job submission.

Execute the PEREO61 process from the Job Submission Process Parameter Entry Form (GJAPCTL) using the parameters outlined below.

If a printer is not selected when this process is run, output must be viewed from the host. The report file is named pereo62.lis and the Web file is named pereo62.txt.

Through the Host Process:

Through the host, execute pereo61.shl or (pereo61.com on VMS platforms).

• Enter the following parameter values for pereo61:

4. Record the Parameter Sequence Number generated by the PEREO61 process in the Control Report of the pere061.lis file.

5. Run the pereo62.shl process using the Parameter Sequence Number from the PEREO61 process above.This will produce the S1-Long report, pereo62.lis, as well as the Web file, pereo62.txt.

6. Verify your IPEDS Detail Report against the IPEDS Summary Report.

Parameter Entry

Year for Which Report is Run

2003


Parameter Entry

Year 2003




7. Once you are sure that the IPEDS Summary Report accurately reflects your employee population, you may either manually complete the institutional and certification information found on the NCES Web site or perform the Web file upload through the NCES Web site. Instructions for the upload/input of IPEDS information are given in the File Input/Update Tutorial on the following Web site:

http://nces.ed.gov/ipeds

Web Upload

The IPEDS Summary Report (PEREO61, -2) process creates a Web upload file in addition to the hard copy report. The Web upload file is in a comma-delimited format that conforms to the NCES requirements for the creation of the Key Pair Value file. (See Key Pair File Format immediately below for further information). Before the Web upload file is submitted to NCES, compare it with the IPEDS Summary Report data for accuracy.

When the IPEDS Summary Report is run through Job Submission or the Host Process, the file name is pereo62.txt.

For any additional information on the IPEDS Web-Based Data collection process refer to the following Web site:

http://nces.ed.gov/ipeds

or contact the IPEDS help desk at 1-877-225-2568.

Key Pair Value File Format

The key pair value file format is the standard from the National Center for Educational Statistics (NCES) that was used for the creation of the web upload option in the IPEDS reports. The following table lists the fields in the Web upload file and provides descriptions and valid values for each field.

Key ID Field Value Description/Values

UNITID Valid UnitID

SURVSECT Survey Section “S1”

PART Part of survey section “A,B,D,F,G”

LINE Primary occupation/salary category/academic rank

RACE Race/ethnicity code

GENDER Men “1” or Women “2”

COUNT Number of employees/staff

Section 17 IPEDS Reports for 2003 - TechnicalNew Script


Section 17 IPEDS Reports for 2003 - Technical

This section documents the technical changes made for the IPEDS release.


New Script

Run this utility script in preparation to run the IPEDS report.

PEEOSYNC.SQL

This SQL utility script identifies employees who have skill codes that are not valid for their EEO contract group. This is an exception report. So, when a blank report is generated, it implies that the EEO contract groups and skills codes are in sync for your employees.

Section 17 IPEDS Reports for 2003 - Technical New Script



Section 18 VETS-100 Reporting for 2003 - FunctionalOverview


Section 18 VETS-100 Reporting for 2003 - Functional

Overview


The VETS-100 Report has been revised for year 2003. The report now displays a Newly Separated Veterans column based on the Active Duty Separation Date field specified on the Identification Forms in the following Banner Systems:

• Identification Form (PPAIDEN) in the Human Resources System

• General Person Form (SPAPERS) in the Student System

• General Person Form (FOAPERS) in the Finance System

• Financial Aid General Person Form (ROAPERS) in the Financial Aid System

• General Person Form (APAPERS) in the Alumni System

Note: This section documents the changes that were made only to the HR forms. For more information on product-specific person forms, please refer to the relevant Release Guide.

This release satisfies RPE# 26377 that requests the Newly Separated Veteran’s category be counted on the VETS-100 Report. For the 2002 and 2003 reporting period, this element was optional.

Changed Form

The following Human Resources form has been modified.

Application Form

PPAIDEN Identification Form

Section 18 VETS-100 Reporting for 2003 - Functional Changed Form


Identification Form (PPAIDEN)

A new field, Active Duty Separation Date has been added to the Biographical window of the Identification Form (PPAIDEN).

. . . . . . . . . . . . . . Fields

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .Descriptions

Active Duty Separation Date

Enter the date on which the individual separated or was discharged from active military duty.

This date is used to classify veterans under the Newly Separated Veterans Category on the VETS-100 Report whose Active Duty Separation Date falls within the VETS reporting period.

Section 18 VETS-100 Reporting for 2003 - FunctionalChanged Report


Changed Report

Veterans Employment Report (PERV100)

A new category, Newly Separated Veterans, has been added to the columns in the New Hires Within Period section of the VETS-100 report. This category considers all newly hired employees whose Active Duty Separation Date falls within the current VETS-100 reporting period, and who qualify as a veteran in one or more of the following categories:

• Special Disabled Veterans

• Vietnam Era Veterans

• Newly Separated Veterans

• Other (Eligible) Veterans

A veteran can be classified in one or more of the above categories.



Report Sample—Veterans Employment Report (PERV100)

REPORT : PERV100 Banner University RUN DATE 16-JUL-2003 Veterans Employment Report RUN TIME 11:57 AM Charlottesville BETWEEN 01-OCT-2002 AND 30-SEP-2003--------------------------------------------------------------------------------------------------------------------------------- | | | | | NUMBER OF EMPLOYEES | NEW HIRES WITHIN PERIOD | | |---------------------------------|---------------------------------------------| | | | | | | | | | NEW HIRE | JOB | SPECIAL | VIETNAM | OTHER | SPECIAL | VIETNAM | NEWLY | OTHER | TOTAL, BOTH | CATEGORIES | DISABLED | ERA | PROTECTED | DISABLED | ERA | SEPARATED | PROTECTED | VETERANS AND | | VETERANS | VETERANS | VETERANS | VETERANS | VETERANS | VETERANS | VETERANS | NON-VETERANS | | | | | | | | | |----------------------------------------------------------------------------------------------------------------------------------Executive/Admin and managerial 1 1 0 1 1 1 0 1----------------------------------------------------------------------------------------------------------------------------------Faculty 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Other professionals 0 0 1 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Technical and paraprofessional 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Tech/para prof - Computer 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Tech/para Prof - Med Srv. Ctr 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Tech/para Prof - finance 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Clerical and secretarial 1 1 1 1 1 1 1 1----------------------------------------------------------------------------------------------------------------------------------Secy/Clerical - Staff 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Skilled crafts 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Service/Maintenance 0 0 1 0 0 1 1 1----------------------------------------------------------------------------------------------------------------------------------Instruction/research assistant 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------Other Administrative 0 0 0 0 0 0 0 0----------------------------------------------------------------------------------------------------------------------------------TOTAL 2 2 3 2 2 3 2 3---------------------------------------------------------------------------------------------------------------------------------- Minimum Maximum 1 3



PAGE 2REPORT : PERV100 Banner University RUN DATE 16-JUL-2003 Veterans Employment Report RUN TIME 11:57 AM BETWEEN 01-OCT-2002 AND 30-SEP-2003


Parameter Name Value Source Message_________________ ______________________________ _______ ____________________________________________________________Parameter Seq No: 1299140Start Date: 01-JAN-2001 DefaultStop Date: 31-DEC-2003 DefaultHiring Location: C-Campus Default




Section 19 VETS-100 Reporting for 2003 - TechnicalChanged Table


Section 19 VETS-100 Reporting for 2003 - Technical

This section describes the technical changes for the VETS-100 enhancement.


Changed Table

Basic Person Base Table (SPBPERS)

The following column has been added to capture the Active Duty Separation Date entered on the Person Form in the corresponding Banner products. This table is common to Human Resources, Student, Alumni, Finance, and Financial Aid products.

New Scripts


SPBPERS1.SQL

This script adds the SPBPERS_ACTIVE_DUTY_SEPR_DATE column to the SPBPERS table.

SPBPERS2.SQL

This script adds a corresponding comment to the SPBPERS_ACTIVE_DUTY_SEPR_DATE column.

Column Name Null? Data type

SPBPERS_ACTIVE_DUTY_SEPR_DATE DATE

Section 19 VETS-100 Reporting for 2003 - Technical New Scripts



Section 20 Canadian Regulatory Enhancement- FunctionalChanged Report


Section 20 Canadian Regulatory Enhancement- Functional

Note: This functionality was originally delivered with Employee Self-Service Release 6.0.1.

Changed Report

Canadian T4 Supplementary Report (PXRT4CN)

The T4 tax reporting capability for Box 71- Status Indian Employee has been added to this report.

Note: This was delivered as seed data. For more details, refer to Appendix B in the Employee Self-Service 6.1 Release Guide.

Section 20 Canadian Regulatory Enhancement- Functional Changed Report



Section 21 Miscellaneous Enhancements - FunctionalCommon Matching in Human Resources


Section 21 Miscellaneous Enhancements - Functional

Common Matching in Human Resources

Previously, when a new person or non-person record was added into Banner, it was possible to create more than one PIDM for that person or non-person under a variety of circumstances. Common Matching is a feature that checks for existing records before adding a new person or non-person record to the database. Common Matching can be turned on/off at the institutional level.

Common Matching is a process that will help your institution manage basic person records. Basic person records refer generically to person and non-person demographic records which can include Name, ID, address, telephone, e-mail and other biographical information.

For Human Resources specifically, if Common Matching is turned on at the institutional level, a data entry person that enters a new Banner ID via Employee Quick Hire Form (PEAHIRE), the One-Time Payment Form (PEA1PAY) or the Identification Form (PPAIDEN) will be taken to the Common Matching Entry form (GOAMTCH). A rules based algorithm is then used to potentially match the current existing basic person information in the Banner database. If no information entered on the form fulfills the matching rules, you may elect to create a new record. If there are potential matches, you can elect to utilize one of the matches found within the database.

Considerations specifically for Human Resources users include the development of specific Matching Source Rules on the Common Matching Source Rules Form (GORCMSC). These rules can be applied to specific users or specific users can be excluded from using Common Matching functionality altogether by setting the appropriate indicator on the Common Matching User Setup Form (GORCMUS).

Note: For more specific information about Common Matching refer to the General Release Guide for Banner Release 7.0.

Incorporated in Human Resources Release 7.0.

Section 21 Miscellaneous Enhancements - Functional Access to Deferred Pay Information in the Employee Jobs Form (NBAJOBS)


Access to Deferred Pay Information in the Employee Jobs Form (NBAJOBS)

Previously there was no visual cue for you to look for adjusted deferred pay amounts on the Deferred Pay Adjustment List Form (PEADADJ) when looking at an employee's deferred pay records on the Employee Jobs Form (NBAJOBS). In order to clarify and/or draw attention to the fact that there is data on the Deferred Pay Adjustment List Form (PEADADJ) for a particular employee, the Data icon is presented next to the Effective Date field on the Deferred Pay tab to indicate that a change exists. Selecting the icon takes you to the Deferred Pay Adjustment List Form (PEADADJ) to look at the adjustments made to that particular record.

This completes RPE #41293. Incorporated in Human Resources Release 7.0.

Leave Roll Enhancement

Previously, a leave roll would occur before the current pay period leave processing when it fell in the rolling period, as specified on PTRLCAT. This enhancement provides leave roll options to process the roll before the current pay period leave taken is applied (as in past releases) or after the current pay period leave taken has been applied.

With this enhancement, you will be able to define, at the installation level, the order in which leave rolls occur in relation to applying taken and accrued time for the current pay period. A new indicator, Leave Balance Roll Order, is provided on the Installation Rules (PTRINST), which allows the site to designate whether you prefer the system to apply leave taken and accrued before rolling the employee leave balance or, roll the leave balance before applying taken and accrued leave time.

Section 21 Miscellaneous Enhancements - FunctionalUpdateable Deferred Pay Adjustment List Form (PEADADJ)


The default setting is set to Roll Before Usage & Accrual. This rule matches the current system functionality. Under this setting, based upon when a particular Leave Category and Leave Code calls for the roll to occur (where the specified roll date falls within the current pay period), the Payroll Update Process (PHPUPDT) will first direct the employee's leave balances to be reset to the Maximum Roll Hours, or keep the employee's balance, whichever is less. Next, leave taken and accrued that is reported with the payroll will be applied to the balance available after the roll.

When this new field is flagged as Roll Balances After Usage & Accrual, PHPUPDT will first apply any leave taken and accrued against the current (unrolled) leave balance. The calculation will then be directed to reset the employee's balance and set it to the Maximum Roll Hours or keep the employee's balance, whichever is less.

This completes RPE #293. Resolved in Human Resources Release 6.1.

Updateable Deferred Pay Adjustment List Form (PEADADJ)

The Deferred Pay Adjustment List Form (PEADADJ) has been enhanced to allow users to update deferred pay amount overrides that have been generated due to salary adjustments or job additions that are made after the deferred pay cycle has begun.

Overrides cannot be created on this form, but those that are inserted from a Personnel Action Form (NOAEPAF), a job change on NBAJOBS or from running the Mass Salary Update (NBPMASS) are updateable. Those records are identified by a check in the System Calculated column. Once a user has modified the record on the Deferred Pay Adjustment List Form (PEADADJ), the check will disappear and the newly added User ID and Activity Date fields will be changed to that of the user making the change and the date the change was made.

Section 21 Miscellaneous Enhancements - Functional Updateable Deferred Pay Adjustment List Form (PEADADJ)


Comment functionality has also been added so that the user can view comments made when the calculation has been changed. Several edits have also been added to ensure that the deferred and Per Pay Salary amounts are valid, (i.e., not negative and salary is not less than deferral amount.)


Section 21 Miscellaneous Enhancements - FunctionalExpansion of the Discipline Code Field


Expansion of the Discipline Code Field

The Discipline Code field has been expanded from five characters to six characters in the Faculty Administration module. In the U.S., many national higher education surveys request information be submitted using the CIP (Classification of Instruction) Code Taxonomy which is 6 digits in length. This expansion also allows Banner HR to be consistent with the code stored in the Student module. The following items were modified to accommodate the expansion:

PEAFACT: The maximum length and the query length is set to 6 characters.

PEAFACD: The maximum length and the query length is set to 6 characters.

PEIFACT: Increased the size of Discipline Code field to 6 characters.

PTVDISP: Increased the length of the PTVDISP_CODE to 6 characters.

POQLIBR: Resulted in a technical fix to change the display width.


Reversal of Organization Transfer on the Position Budget Form (NBAPBUD)

The Position Budget Form (NBAPBUD) has been enhanced with this release to accommodate the reversal of a previously completed organization transfer. Prior to this release, once an organization transfer had been completed, you were unable to transfer budgetary responsibility back to the previous organization.

The Position Budget Form (NBAPBUD) required that every organization transfer executed have a unique organization number for the current fiscal year. With this release, the Position Budget Form (NBAPBUD) includes a new option known as Organization Untransfer. This option allows you to permit the user to select from a list of organization codes for the current fiscal year whose Status is Transferred. When a prior transferred organization code is selected, the form will aggregate the position total record amount fields between the prior active Position Total record (transferring from) and the previously transferred position total record (transferring to).

Section 21 Miscellaneous Enhancements - Functional Reversal of Organization Transfer on the Position Budget Form (NBAPBUD)


The following example describes the procedure to untransfer a budget:

Assume the following amounts exist on the position total record for the current fiscal year:

User processes an organization transfer to organization 11104

Continuing with this example, additional payrolls are processed in the current fiscal year and the employee in this position is paid an additional $5,000. Assuming the employee is paid with an earnings code that is set up on the Earnings Code Rules Form (PTREARN) and the earning code liquidates encumbrances, the position total record would now reflect:

Now, if the budgetary responsibility for this position needs to return to organization 11103, perform a budget untransfer by selecting the Organization Untransfer option.

In this case only one organization code will be listed, as this position has had only one transfer performed in the current fiscal year. On selecting the OK button for organization 11103, the system aggregates the position budget total records. Consistent with prior functionality, the Budget amount on the transfer record is set equal to any expense incurred for that organization. Any remaining budget is added back to the budget amount on the previously transferred position total record. In addition, any remaining encumbered amount is moved to the previously transferred position total record. Finally, the Status on the previously transferred record is set to Active. The Position Salary Budgets Window will now contain two Position Total records, which now reflect:

Status Org Budget Encumbered Expended Remaining

Active 11103 100,000 20,000 60,000 20,000


Transferred 11103 60,000 0 60,000 0Active 11104 40,000 20,000 0 20,000


Active 11104 40,000 15,000 5,000 20,000Transferred 11103 60,000 0 60,000 0


Active 11103 95,000 15,000 60,000 20,000Transferred 11104 5,000 0 5,000 0

Section 21 Miscellaneous Enhancements - FunctionalLabor Redistribution Form (PHAREDS)


Note: You may transfer to an organization code only once.

In the above example, a transfer back to organization 11104 would not be permitted in the current fiscal year. Instead, you could accomplish this action by doing an organization untransfer for organization 11104.


• When processing an organization transfer, any expended amount for a premium earning budget was being subtracted from an existing premium budget amount pending posting to Banner Finance. This was resulting in the understatement of budget amounts in Banner Finance. As organization transfers have no relevance to budget amounts pending posting, the subtraction of the expended amount from the To Be Posted amount on premium earnings has been removed. The amount to be posted for premium earnings will be unaffected by the processing of an organization transfer. Resolved in Human Resources Release 6.1.

Labor Redistribution Form (PHAREDS)

The following changes have been made to the Labor Redistribution Form (PHAREDS):

1. In the past, when one user was attempting to make payroll adjustments to an employee that was currently being processed by another user, the form indicated that records were in use by another user and gave no indication about who was reserving the records. Now, when you navigate to the next block from the Key block, and another user is processing an employee’s record, an error message is displayed with the user ID holding this record making it easier to determine who else is processing the employee.

2. Previously, when processing an adjustment for an employee and the Banner session ended abnormally, (i.e., a system crash), temporary records would be stored for that employee, but the user was unable to re-access those records. Consequently, the adjustment could not be completed. The form has been changed so that the original user can now access the temporary adjustment records and complete the transaction.

These enhancements complete RPE #4993. Incorporated in Human Resources Release 6.1.

Section 21 Miscellaneous Enhancements - Functional Expansion of Benefit Plan Amount Fields For Percent Calculations


Expansion of Benefit Plan Amount Fields For Percent Calculations

For benefit/deductions codes with calculation rules that accommodate percentage-based plans, the Amount 1 and Amount 2 fields, seen in many places in the system have been expanded to four decimal places from the current two.

Please note that the resulting deduction calculation will still be rounded to two decimal places.

This change has been made throughout the Benefits/Deductions module in both, Banner and Employee Self-Service, and includes flexible benefits, payroll, and mass change processing. Forms and processes impacted include the:

• Employee Benefits or Deduction Form (PDADEDN),

• Employee Flexible Benefits Form (PDAFLEX),

• Employee Benefits and Deductions Rule Form (PTRBDCA),

• Employee Benefit or Deduction Set Up Form (PDABDSU),

• Benefit/Deduction Mass Change Rules Form (PTRBDMC), and

• Payroll Calculation Report (PHPCALC).

Note: The expansion of Amount 1 and Amount 2 fields do not pertain to those benefit/deduction codes that use dollar amounts. If you try to enter too many decimal places you will receive an error message: *ERROR* {AMT1/AMT2} has to be in format 999,999,999.99. You will be required to change the number to the appropriate format prior to saving and leaving the record.


Expansion of the Amount and Special Rate Fields

In order to accommodate larger payments through the One Time Payment Form (PEA1PAY), the Special Rate and the Amount fields have been increased throughout the HR product. The Special Rate field was expanded to accommodate a maximum one-time payment amount of $999,999.99. Previously, the maximum payment that could be processed was $99,999.99. The Special Rate field is now defined in the database as 999,999.999999. Due to the increase in the size of the Special Rate field, the Amount field was also expanded to accommodate the potentially larger resultant calculation of Hours/Units times Special Rate.

Section 21 Miscellaneous Enhancements - FunctionalExpansion of the Amount and Special Rate Fields


Accordingly, the following forms have been modified:

• Online Time Entry Form (PHAHOUR)

• Electronic Approvals of Time Entry Form (PHATIME)

• Mass Time Entry Form (PHAMTIM)

• Check Detail Inquiry Form (PHICHEK)

• Pay History Display Errors Form (PHIDERR)

• Employee Jobs Form (NBAJOBS)

• Electronic Personnel Action Form (NOAEPAF)

The following C processes have been modified:

• Check/Direct Deposit Print Process (PHPCHEK/PHPCHKL)

• Retroactive Pay Calc Process (PHPRETO)

• Payroll Errors Display Report (PHRDERR)

• Report of Hours (PHRHOUR)

• Payroll Register Report (PHRPREG)

The following COBOL processes have been modified:

• Payroll Calculation Process (PHPCALC)

• Expenditures Finance Extract (PHPFEXP)

The following tables have been modified:

PEREARH PEREARI PEREARN PERELBD PERELBH

PERHOUH PERHOUR PERTITH PERTITO PETTIME

PHREARN PHRERRL PHRMTIM PTRSERN NBREARN

NORTERN

The following database packages have been modified:

BWPKTAP1.SQL, NOKMSGS.SQL, PEKTEE1.SQL, BWPKHST1.SQL


Section 21 Miscellaneous Enhancements - Functional NHRDIST Report Layout in E~Print


NHRDIST Report Layout in E~Print

The NHRDIST Report has been changed slightly in order to make it work correctly with e~Print’s page level security. Previously, a colon after the Organization string on a continuing page was missing, causing e~Print not being able to find the string to apply security. Now the colon has been supplied as well as six characters so that the organization code can be found in a standard place.

The way in which this report is constructed, e~Print must scan the header for a string value and extract the next 6 digits that occur after that string. For this report e~Print is scanning for 'Organization: ' For example, if the report has the two digit organization code '10' it prints as '10 Off'. Since '10 Off' is not a valid organization code this page will not open for a user who has access to organization 10. The shorter the Organization code the higher the organization is in the hierarchy. This means that the person with access to the Office of the President will not be able to access this page.

The report has been changed to include a ":" (colon) after Organization on the second and subsequent pages as well as moving the organization description 10 characters to the right of the code so as to enforce page security in e~Print.


Encumbrance Recasting

The purpose of this enhancement is to enable another way to manage encumbrances throughout the fiscal year. In the past, encumbrances could be generated through job assignments and the processing of the Budget Maintenance Process (NBPBUDM). However, these encumbrances could only be reduced through the payroll process and the reduction would be associated with actual payment, not the planned encumbered amount.

The Recast Method now allows the system to calculate encumbrance reductions based upon a date submitted to NBPBUDM, rather than having each payroll liquidate each encumbrance based upon the amount paid to the employee. The resulting encumbrance calculations will be posted to the employee's Labor Distribution History record that is associated with the affected job. This dollar amount, which is inserted into the To Be Posted field, would typically be a negative encumbrance adjustment, as it is computed against the original, or current job encumbrance.

Section 21 Miscellaneous Enhancements - FunctionalEncumbrance Recasting


To pass the encumbrance reductions to Finance, the Finance Extract Process (NHPFIN1) and the Finance Interface Report (NHPFIN2) have to be executed. Using the Recast Method, it is intended that the Expenditures Finance Extract (PHPFEXP) will no longer feed encumbrance adjustments, based upon the payroll expense. It is important to note that an adjustment to the Finance Setup Rules (NTRFINI) must be done prior to feeding the first payroll. This will be discussed in the setup information to follow. Otherwise, multiple encumbrance adjustments would be fed to Banner Finance which would overstate the liquidated encumbrance.

Note: Only the System Calculated encumbrance method type of jobs will process under the Recast guidelines described here. The other encumbrance methods: Value Input, Annual Salary, and Hours Input will process as they have in the past. These encumbrance controls are initially established on the Employee Class rules (PTRECLS), which are then associated with the employee's job assignment.

Enabling the Encumbrance Recasting Indicator

The first step to establishing Encumbrance Recast is to activate the system setting on the Position Control Installation Rules (NTRINST). The new control, Encumbrance Recasting Indicator, is being delivered in the 6.1 release as unchecked or not enabled. To turn on the Recast Logic system-wide, check the box next to this field. This indicator will control processing in NBPBUDM and PHPFEXP for all jobs that are affiliated with the system calculated encumbrance method.

Section 21 Miscellaneous Enhancements - Functional Encumbrance Recasting


Two processes are affected by the recast enhancement, the Budget Maintenance Process (NBPBUDM) and the Expenditures Finance Extract (PHPFEXP). Both processes contain new logic that will execute the recast methodology when two conditions are present:

1. When the (new) indicator Encumbrance Recasting Indicator, located on Position Control Installation Rules (NTRINST), is enabled, and

2. An employee's Encumbrance Method, as established on PTRECLS and associated with their job assignment, is System Calculated.

Section 21 Miscellaneous Enhancements - FunctionalEncumbrance Recasting


Changed NBPBUDM Process

The NBPBUDM process has two new parameters to run the Recast process. These items only affect encumbrance recast calculations and are not referenced in any other budget process:

1. Chart of Accounts Code - The COA that is to be computed for Encumbrance Recast purposes. The process can perform calculations for only one COA during a single run. So, if the site were processing multiple charts, the process has to be run multiple times.

2. Recast Date - A day within the active fiscal year for which encumbrances will be computed and compared to the current job encumbrance. This date can be a pay period end, a specific day within a month, a future date or past date. The program will calculate the amount required to fund the job from the Recast Date to the Job End Date (or the end of the fiscal year if the job End Date is null.) The difference between the current job encumbrance and the recast calculation will be posted to the employee's Job Labor Distribution History record for the affected FOAPAL.

When the process is executed, the Encumbrance Recasting Indicator setting on NTRINST determines if employees using the System Calculated Encumbrance Method will be processed through the recast logic. If the indicator is enabled, these employees will be selected for recast calculations and the process will require a Chart of Accounts and Recast Date as processing parameters. If these parameters are missing and encumbrances are being processed, the process will end and issue an error message.

The process then determines the value of each job assignment that qualifies by using the Recast Date as the starting point in the calculation and the Fiscal Year End Date as the end point (or the End Date of the job within the fiscal year.) The Fiscal Year End Date is determined from the Recast Chart of Accounts, submitted as a parameter, and the process locates the Active Fiscal Year on the Fiscal Year Form (NBAFISC). Once the dates have been established, the process will calculate the encumbrance based upon the workdays and where the Recast Date falls in the FY. This process can be run every pay period, once a month, or daily, based upon the financial posting needs of the site.

The calculation will determine the point-in-time encumbrance and compare the number with the current encumbrance amount, as stored on the Job Labor Distribution History record. There may be one or more of these records for the job based upon the Job Labor Distributions. The difference is then computed and inserted as adjustments to these records.

If the Fringe Chargeback method is being used, fringe encumbrances will also be computed and posted as part of this process, along with salary encumbrances.

Section 21 Miscellaneous Enhancements - Functional Encumbrance Recasting


Example

The fiscal year of the site is 7/1/2004 to 6/30/2005. An employee is appointed to a position as of 7/1/2004, paid on a monthly calendar, and the annual salary is $60,000, to one FOAPAL.

When the assignment is posted, the Job Labor Distribution History record will hold $60,000 as an encumbrance value and this amount is also inserted in the 'To Post' field so that it can be moved to Banner Finance through the NHPFIN1 and NHPFIN2 processes.

One month passes and the user wishes to post encumbrance adjustments. NBPBUDM is processed with the appropriate COA and a Recast Date of 7/31/2004. The calculation determines that, as of the Recast Date, the value of the job encumbrance is $55,000. Therefore, compared to the current encumbrance, -$5,000 needs to be inserted in the To Post field on the Job Labor Distribution History record. When NHPFIN1 and NHPFIN2 are processed, the system will generate an encumbrance adjustment of $5,000 to the appropriate FOAPAL.

The Encumbrance amount that is calculated and displayed on the base record of NBAJOBS is not updated with the recast calculated amount from the NBPBUDM process. Rather, the encumbrance amount displayed for the user continues to report the fiscal year funds required to pay the job assignment. As the job assignment is adjusted by future events, the NBAJOBS form will continue to recalculate the total fiscal encumbrance value. The prorated, or recast, amount of the encumbrance is recalculated and displayed on the Job Labor Distribution History record, distributed across the FOAPAL distributions associated with the job assignment.

Setup and Payroll Process

Through this methodology, the payroll expenditure feed process (PHPFEXP) should no longer generate encumbrance liquidations for the actual amount expended, as planned encumbrance adjustments, or liquidations are to be posted by NHPFIN1 and NHPFIN2. Therefore, PHPFEXP has been adjusted to determine whether recasting has been enabled and to use overrides when System Calculated employees are to be posted.

These overrides are established on the Finance Setup Rules form, NTRFINI, and are located in the Encumbrance Override navigation option. This area holds two new Finance Rule Class codes that will be used for recast employees. The first establishes the override that will be used to direct the Salary Expense posting. HGNL should be specified here, which will ensure that no encumbrance liquidation will be posted, along with the gross payroll expense.

The second Rule Class code establishes the override for Fringe Chargeback Expense posting. HFNL should be specified here in order to avoid the liquidation of Fringe Chargeback encumbrances generated through the course of the payroll posting.

Section 21 Miscellaneous Enhancements - FunctionalEmployee Jobs Form (NBAJOBS) Enhancements


Those sites that utilize the actual, or direct charge benefit method, where the Fringe Calculation Method on NTRFINI is None, will not utilize this Rule Class control, since benefit encumbrances are never generated under this charging method.

All other employee jobs where the encumbrance methods are Value Input, Hours Input, or Annual Salary, will continue to post in the traditional fashion. Encumbrance liquidations will occur on the actual payroll expense, utilizing the Salary Encumbrance Adjustment and Fringe Encumbrance Adjustment Rule Classes established on NTRFINI. These methods will not access the Encumbrance Override Rule Classes.

If recasting has not been enabled on NTRINST, the Encumbrance Overrides will not be accessed by PHPFEXP.

This enhancement completes RPE #34011. Resolved in Human Resources Release 6.1.

Employee Jobs Form (NBAJOBS) Enhancements

The following enhancements were made to the Employee Jobs Form (NBAJOBS):

• When an adjustment was made to the Job Detail Record on the Employee Jobs form (NBAJBOS), two records were being created on the PERJHIS table. The change to the detail record caused one record to be created and the encumbrance recalculation inserted on the Job Base Table (NBRBJOB), caused a second history record insert. The form has been modified and only one record is now written to job history. This completes RPE #34101. Resolved in Human Resources Release 6.1.

• The Error or Warning message regarding the job encumbrance value exceeding the available budget on the Position Budget Form (NBAPBUD) has been suppressed. When the position has a zero budget, the message is not relevant for positions that are not budgeted. This completes defect #31805 and RPE #34102. Resolved in Human Resources Release 6.0.0.1.

Section 21 Miscellaneous Enhancements - Functional New Rule Class Override in PTREARN and PHPFEXP


New Rule Class Override in PTREARN and PHPFEXP

This enhancement provides for the ability to override the Rule Class code at the Earnings level to avoid the generation of fringe chargeback encumbrance liquidation on certain earnings when the payroll is interfaced to accounting. In a past release, a similar capability was instituted, where an override Rule Class was made available at the earning code level to avoid salary encumbrance liquidations. In the case of salary items, a rule class can be overridden so that it could be changed from a normal liquidating earn code (e.g., HGRS) to a non-liquidating earn code (e.g., HGNL), during the payroll expense feed PHPFEXP.

With this RPE, a new fringe rule class override has been added to the earnings rule, and is called the Fringe Rule Class. It is located in the Main window of the Earnings Code Rule Form (PTREARN) along with the original rule class override which is used to override earnings.

In the case of Fringe Chargeback encumbrance liquidations, the Expenditures Finance Extract Process (PHPFEXP) will recognize the Fringe Rule Class, when it has been populated (typically with a non-liquidating earn code such as HFNL), to direct the payroll feed process not to liquidate the fringe encumbrance. This completes RPE #34233. Resolved in Human Resources Release 6.1.

Section 21 Miscellaneous Enhancements - FunctionalFaculty Record Enhancements


Faculty Record Enhancements

Several changes and enhancements have been made to the Faculty Tracking page (PEAFACT) in order to facilitate record keeping.

1. Automation of Approvals for Faculty Leave

As the automation of approval for Appointment/Tenure and Rank records has been delivered in a past release, this functionality has been extended to the Faculty Leave record. To activate this feature, a new Approval Level Code has to be entered on the Electronic Approval Level Rules Form (NTRALVL) to control the users for which an automated approval record would be generated once the Faculty Leave record has been created.

Section 21 Miscellaneous Enhancements - Functional Faculty Record Enhancements


Enter the new Approval Level Code on the Installation Rules Form (PTRINST) in the Faculty Action Rules window. Once this control is established, an automated approval record will be generated when a specified user saves the Faculty Leave record. When the Auto Approval Leave indicator is unchecked, the system waits for the manual insertion of the Approval Action, before the record can be set as Approved.

2. Option to uncouple Faculty Leave editing with Employee Jobs

Additional flexibility was requested for establishing Faculty Leave records when recording a leave, which was not necessarily tied to a payroll period, or the Faculty Leave information was not established until after the payroll period had occurred.

To ease the burden of attempting to synchronize employee job dates with Faculty Leave dates, a new field has been added to PTRINST. This new field is located on the Faculty Action Rules window (see previous page) and is called, Edit employee job records against Faculty Leave Records. When this indicator is set to Do Not Edit, and the employee's Faculty Leave record is approved, the job record will not be analyzed to ensure it is coded for the proper Job Status. Rather, the Faculty Leave record will be approved and will not be held in a Pending status waiting for the job record to synchronize.

If this new field is set to Edit, current functionality will be maintained where the Faculty Action will continue to be edited against the job status of the employee's job assignment.

Section 21 Miscellaneous Enhancements - FunctionalFaculty Record Enhancements


3. Overlapping Faculty Leave Dates

Flexibility was requested when a faculty member had multiple leave situations, and their leave dates overlapped. The Faculty Leave Action will now allow for multiple faculty leave records, regardless of the Leave Begin and Leave End dates. Editing of the leave periods that compared dates from one leave record to the next was dropped, allowing for the insertion of leave records that overlap.

4. Ability to record a new faculty title, without changing the rank record

When tracking faculty actions by Position/Suffix or by Organization Codes aligned with the employee job assignments, new effective-dated Rank records were required to initiate an Academic Title change. The maintenance of a new title tended to obscure the actual rank information, making a Years-in-Rank analysis difficult. To make the Academic Title easier to maintain, a new table has been added to allow for the creation of multiple Academic Titles, each based upon a date.

When establishing the rank record, under the Position/Suffix or Organization Code setting, the Academic Title could be installed by selecting the Note icon located to the right of the Academic Title field.

Section 21 Miscellaneous Enhancements - Functional Faculty Record Enhancements


A new Academic Title window is displayed that allows you to insert an Effective Date and an Academic Title. Upon returning to the Rank window, the Academic Title closest to the System Date will be displayed on the page.

Note: This window does not appear when faculty records are tracked by Faculty Members setup on PTRINST. In this case, the Academic Title field is unchanged, in that, only title will be stored and displayed on the Main block of PEAFACT.

5. Ability to see where comments are listed in Faculty Actions

Comments can be made on any of the three Faculty Action areas, Appointment/Tenure, Rank, and Faculty Leave. However, without querying into each record, it was difficult to determine where comments were previously submitted. To provide you with a visual aid to quickly determine where comments existed, a new display column has been added to the Employee List by Faculty Action page (PEIELFA).

The new Comments Exist field provides you with a check indicator, when comments are present on a given action record.

Section 21 Miscellaneous Enhancements - FunctionalEnhancement to the Payroll Adjustment Form (PHAADJT)



Enhancement to the Payroll Adjustment Form (PHAADJT)

The Payroll Adjustment Form has been enhanced to provide the ability to reissue a direct deposit portion of a payroll transaction comprised of a reconciled check. Prior to this release, you could not reissue the check component if it was already reconciled. You now have the ability to reissue the check, any portion of a direct deposit or the entire payroll transaction.


Section 21 Miscellaneous Enhancements - Functional Enhancements to the Employee Review Form (PEAREVW)


Enhancements to the Employee Review Form (PEAREVW)

The following RPEs have been completed for the Employee Review Form (PEAREVW):

• The Employee Review Form (PEAREVW) has been modified to include comments on the page with the review dates and other review data. This allows you to see all comments associated with each review date. This aids in the review of critical comments and may encourage more reviewers to add comments with their reviews. It also lessens the number of key strokes necessary to see all information about a review. With this change, the Comment window option has been removed from the Options menu.


• Prior to the modification mentioned in the previous paragraphs, there was a request to add a Comment Exists indicator on the PEAREVW form. Since the Comment field has been moved to the Main window of the PEAREVW form, there is no need for a separate indicator to indicate that a comment exists on a subsequent window.


Section 22 Miscellaneous Enhancements - TechnicalNew Scripts


Section 22 Miscellaneous Enhancements - Technical

This section documents the database changes in Banner for the Miscellaneous Enhancements made in Human Resources Release 6.1.

New Scripts


PERACTL1.SQL and PERACTL2.SQL

PERACTL1.SQL creates a new table, PERACTL.

PERACTL2.SQL creates a unique Index, PERACTL_KEY_INDEX on the PERACTL table.

PERACTL3.SQL and PERACTL4.SQL

PERACTL3.SQL populates the PERACTL table with values from the PERRANK table.

PERACTL4.SQL adds a table comment and corresponding column comments for PERACTL table.

Changed Scripts


NBREARN1.SQL

This script increases the field length of the SPECIAL_RATE field to NUMBER(12,6) in the NBREARN table.

NORTERN1.SQL

This script increases the length of the SPECIAL_RATE field to NUMBER(12,6) in the NORTERN table.

Section 22 Miscellaneous Enhancements - Technical Changed Scripts


NTRFINI1.SQL and NTRFINI2.SQL

NTRFINI1.SQL adds two new columns, NTRFINI_RUCL_CODE_EXP_NO_LIQ and NTRFINI_RUCL_CODE_FRN_NO_LIQ to the NTRFINI table,

NTRFINI2.SQL adds appropriate comments to the new columns of NTRFINI table.


NTRINST1.SQL adds a new column to capture the value of the Encumbrance Recast Indicator in the NTRINST table.

NTRINST2.SQL sets up a default value for the NTRINST_ENCUMBRANCE_RECAST_IND column.


NTRINST3.SQL sets the NTRINST_ENCUMBRANCE_RECAST_IND column as a NOT NULL column.

NTRINST4.SQL adds a column comment to the NTRINST_ENCUMBRANCE_RECAST_IND column.

PHRERRL1.SQL and PHRERRL2.SQL

PHRERRL1.SQL increases the length of the SPECIAL_RATE field to NUMBER(12, 6) and the AMOUNT field to NUMBER(12, 2)in the PHRERRL table.

PHRERRL2.SQL increases the length of the RATE field to NUMBER(12, 6)in the PHRERRL table.

PDRFLEX1.SQL

This script increases the length of the AMOUNT fields to accommodate for four decimal places in the PDRFLEX table.

PERAPPT1.SQL

This script expands the field length of the DISP_CODE field upto six (6) characters in the PERAPPT table.

PERBFAC1.SQL

This script expands the field length of the DISP_CODE field upto six (6) characters in the PERBFAC table.

Section 22 Miscellaneous Enhancements - TechnicalChanged Scripts


PERDADJ1.SQL and PERADADJ2.SQL

PERDADJ1.SQL adds three new fields, PERDADJ_SYSTEM_CALC_IND, PERDADJ_USER_ID, and PERDADJ_COMMENT, to the PERDADJ table.

PERDADJ2.SQL sets the PERDADJ_SYSTEM_CALC_IND value to Y for all existing PERDADJ records.

PERDADJ3.SQL and PERDADJ4.SQL

PERDADJ3.SQL adds comments to the new columns, PERDADJ_SYSTEM_CALC_IND, PERDADJ_USER_ID, and PERDADJ_COMMENT of the PERDADJ table.

PERDADJ4.SQL sets the PERDADJ_SYSTEM_CALC_IND column as a NOT NULL column.

PEREARH1.SQL

This script increases the SPECIAL_RATE field to accommodate NUMBER(12, 6) in the PEREARH table.

PEREARI1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PEREARI table.

PEREARN1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PEREARN table.

PERELBD1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PERELBD table.

PERELBH1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PERELBH table.

PERHOUH1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PERHOUH table.



PERHOUR1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PERHOUR table.

PERTITH1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PERTITH table.

PERTITO1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PERTITO table.

PETTIME1.SQL

This script increases the SPECIAL_RATE field to a NUMBER(12, 6) in the PETTIME table.

PHREARN1.SQL and PHREARN2.SQL

PHREARN1.SQL increases the length of the SPECIAL_RATE field to NUMBER(12, 6)and the AMOUNT field to NUMBER(12, 2) in the PHREARN table.

PHREARN2.SQL increases the length of the RATE field to NUMBER(12, 6) in the PHREARN table.

PHRHOUR1.SQL

This script increases the length of the AMOUNT field to NUMBER(12, 6) in the PHRHOUR table.

PHRMTIM1.SQL

This script increases the length of the SPECIAL_RATE field to NUMBER(12, 6) in the PHRMTIM table.

PTRBDPL1.SQL

This script increases the length of the AMOUNT fields to accommodate for four decimal places in the PTRBDPL table.

Section 22 Miscellaneous Enhancements - TechnicalChanged Scripts



PTREARN5.SQL adds a new column, PTREARN_RUCL_CODE_FRNG to the PTREARN table.

PTREARN6.SQL adds a comment to the above column in the PTREARN table.

PTRINST1.SQL and PTRINST2.SQL

PTRINST1.SQL adds a new column, PTRINST_LEAVE_ROLL_ORDER, to the PTRINST table.

PTRINST2.SQL sets the PTRINST_LEAVE_ROLL_ORDER column with a value B.


PTRINST3.SQL sets the PTRINST_LEAVE_ROLL_ORDER column as a NOT NULL column.

PTRINST4.SQL adds a comment for the new column, PTRINST_LEAVE_ROLL_ORDER.


PTRINST5.SQL adds three new columns to the PTRINST table, PTRINST_SABB_AUTO_APPR_IND, PTRINST_ALVL_CODE_SABB, and PTRINST_JOBS_LEAV_SYNC_IND.

PTRINST6.SQL initializes indicator values for the PTRINST_SABB_AUTO_APPR_IND and PTRINST_JOBS_LEAV_SYNC_IND columns in the PTRINST table.


PTRINST7.SQL sets the PTRINST_SABB_AUTO_APPR_IND and PTRINST_JOBS_LEAV_SYNC_IND columns as NOT NULL columns in the PTRINST table.

PTRINST8.SQL creates a Foreign Key, FK3_PTRINST_INV_NTRALVL_CODE for the PTRINST table.


PTRINST9.SQL adds comments for the three new columns of PTRINST, PTRINST_SABB_AUTO_APPR_IND, PTRINST_ALVL_CODE_SABB, and PTRINST_JOBS_LEAV_SYNC_IND.



PTRINST10.SQL adds a new column, PTRINST_DD_WEB_UPDATE_IND to the PTRINST table.


PTRINST11.SQL sets the PTRINST_DD_WEB_UPDATE_IND column value to N in the PTRINST table.

PTRINST12.SQL sets the PTRINST_DD_WEB_UPDATE_IND column as a NOT NULL column.

PTRINST13.SQL

This script adds a comment for the PTRINST_DD_WEB_UPDATE_IND column.

PTRSERN1.SQL

This script increases the field length of the SPECIAL_RATE field to NUMBER(12,6) in the PTRSERN table.

PTVDISP1.SQL

This script increases the field length of the PTVDISP_CODE column to six characters.

PDKDED1.SQL and PDKDEDN1.SQL

These scripts have been modified for RPE 25848.

PDKLIB1.SQL

This script has been modified for Tranman conversion in Release 7.0.

PDRFLEX1.SQL

This script alters the PDRFLEX table to expand Amount 1 and Amount 2 from 2 to 4 decimal digits for RPE 25848.

PDRPTAB2.SQL

This script drops two public synonyms for table that were dropped as a part of the 6.1 release of Human Resources. This script also drops 5 Payroll tables that used to support the Employee Self-Service Finance Product. Since Finance Self Service was separated from Employee Self Service, these tables are no longer needed.

Section 22 Miscellaneous Enhancements - TechnicalChanged Utility Script


PEK1PA1.SQL

This script has been modified for Tranman conversion in Human Resources Release 7.0.

PEKLIB1.SQL


PEKTEE1.SQL

This script has been modified for RPE #31570.

PHKLIB1.SQL


POKPVAL.SQL

This package has been modified for Tranman conversion in Human Resources Release 7.0.

POKWLI1.SQL

This package has been modified for Tranman conversion in Human Resources Release 7.0.

Changed Utility Script

Note: This script will not be run as a part of the upgrade.

PERBFACU.SQL

The PERBFACU.SQL utility script has been modified as a result of RPE #35097. This script is used to convert data from the Faculty Information Form (PEAFACD) to the Faculty Action Tracking Form (PEAFACT). During conversion, this script will now also populate the new Academic Title Table (PERACTL).

Section 22 Miscellaneous Enhancements - Technical New Table


New Table

Faculty Action Academic Title Table (PERACTL)

Changed Tables

Employee Default Earnings Code Table (NBREARN)

This column was added for the Expansion of Amount and Special Rate Fields Enhancement. (RPE #31570)

Transaction Approvals Default Earnings Table (NORTERN)

This column was added for Expansion of Amount and Special Rate Fields Enhancement. (RPE #31570)


PERACTL_PIDM NOT NULL NUMBER(8)

PERACTL_EFFECTIVE_DATE NOT NULL DATE

PERACTL_ACTIVITY_DATE NOT NULL DATE

PERACTL_ORGN VARCHAR2(6)

PERACTL_COAS_CODE VARCHAR2(1)

PERACTL_POSN VARCHAR2(6)

PERACTL_SUFF VARCHAR2(2)

PERACTL_ACADEMIC_TITLE VARCHAR2(80)

PERACTL_USER_ID VARCHAR2(30)


NBREARN_SPECIAL_RATE NUMBER(12,6)

Section 22 Miscellaneous Enhancements - TechnicalChanged Tables


HR/Finance Set Up Rule Table (NTRFINI)

These columns were added for the Encumbrance Recasting Enhancement. (RPE #34011)

Position Control Installation Rule Table (NTRINST)

This column was added for the Encumbrance Recasting Enhancement. (RPE #34011)

Pay History Error Log Repeating Table (PHRERRL)

These columns were added for the Expansion of Amount and Special Rate Fields Enhancement (RPE #31570)

Employee Flexible Benefits Table (PDRFLEX)

These columns were added for the Expansion of Benefit Plan Amount Fields Enhancement. (RPE #25848)


NORTERN_SPECIAL_RATE NUMBER(12,6)


NTRFINI_RUCL_CODE_EXP_NO_LIQ VARCHAR2(4)

NTRFINI_RUCL_CODE_FRN_NO_LIQ VARCHAR2(4)


NTRINST_ENCUMBRANCE_RECAST_IND NOT NULL VARCHAR2(1)


PHRERRL_RATE NUMBER(12,6)

PHRERRL_SPECIAL_RATE NUMBER(12,6)

PHRERRL_AMT NUMBER(12,2)


PDRFLEX_AMOUNT1 NUMBER(13,4)

Section 22 Miscellaneous Enhancements - Technical Changed Tables


Faculty Appointment/Tenure History Table (PERAPPT)

This column was modified for the Expansion of the Discipline Code Field Enhancement. (RPE #3638)

Faculty Information Base Table (PERBFAC)


Employee Defer Pay Adjustment Repeating Table (PERDADJ)

The following new columns were added for the Expansion of PERDADJ table Enhancement. (RPE #1072)

Time Entry Earnings History Table (PEREARH)

This column was modified for the Expansion of Amount and Special Rate Fields Enhancement. (RPE #31570)

PDRFLEX_AMOUNT2 NUMBER(13,4)


PERAPPT_DISP_CODE VARCHAR2(6)


PERBFAC_DISP_CODE VARCHAR2(6)


PERDADJ_SYSTEM_CALC_IND NOT NULL VARCHAR2(1)

PERDADJ_USER_ID VARCHAR2(30)

PERDADJ_COMMENT VARCHAR2(2000)


PEREARH_SPECIAL_RATE NOT NULL NUMBER(12,6)




One-Time Payments Earn Code Information Table (PEREARI)


Time Entry Earnings Repeating Table (PEREARN)


Time Entry Labor Distribution Repeating Table (PERELBD)


Time Entry Earnings Labor Distribution Repeating Table (PERELBH)


Time Entry Hours Breakdown History Table (PERHOUH)


Time Entry Hours Breakdown Table (PERHOUR)



PEREARI_SPECIAL_RATE NUMBER(12,6)


PEREARN_SPECIAL_RATE NOT NULL NUMBER(12,6)


PERELBD_SPECIAL_RATE NOT NULL NUMBER(12,6)


PERELBH_SPECIAL_RATE NOT NULL NUMBER(12,6)


PERHOUH_SPECIAL_RATE NOT NULL NUMBER(12,6)

Section 22 Miscellaneous Enhancements - Technical Changed Tables


Time In/Out History Table (PERTITH)


Time Entry Hours Breakdown Table (PERTITO)


Time Entry Hours Breakdown Temporary Table (PETTIME)


Pay History Earnings Repeating Table (PHREARN)

These columns were modified for the Expansion of Amount and Special Rate Fields Enhancement. (RPE #31570)

Hour Validation Table (PHRHOUR)



PERHOUR_SPECIAL_RATE NOT NULL NUMBER(12,6)


PERTITH_SPECIAL_RATE NUMBER(12,6)


PERTITO_SPECIAL_RATE NUMBER(12,6)


PETTIME_SPECIAL_RATE NOT NULL NUMBER(12,6)


PHREARN_RATE NUMBER(12,6)

PHREARN_SPECIAL_RATE NUMBER(12,6)

PHREARN_AMT NUMBER(12,2)



Mass Time Entry Table (PHRMTIM)


Benefit/Deduction Valid Plan Rule Table (PTRBDPL)

These columns were modified for the Expansion of Benefit Plan Amount Fields Enhancement. (RPE #25848)

Earnings Code Rule Table (PTREARN)

This column was added for the New Rule Class Override Enhancement.(RPE #34233)

Payroll Institution Rule Table (PTRINST)

These columns were added for RPEs #293, #15677, #21456 and #35097.


PHRHOUR_AMT NUMBER(12,2)


PHRMTIM_SPECIAL_RATE NUMBER(12,6)


PTRBDPL_AMT1 NUMBER(13,4)

PTRBDPL_AMT2 NUMBER(13,4)


PTREARN_RUCL_CODE_FRNG VARCHAR2(4)


PTRINST_LEAVE_ROLL_ORDER NOT NULL VARCHAR2(1)

PTRINST_SABB_AUTO_APPR_IND NOT NULL VARCHAR2(1)

PTRINST_ALVL_CODE_SABB VARCHAR2(6)

PTRINST_JOBS_LEAV_SYNC_IND NOT NULL VARCHAR2(1)

Section 22 Miscellaneous Enhancements - Technical Changed Libraries


Supplemental Payroll Earn Codes Rule Table (PTRSERN)


Discipline Code Validation Table (PTVDISP)


Changed Libraries

The following libraries have been changed for Release 6.1.

NOQPPLS.PLL

This library was modified to accommodate for RPE #25848, Expansion of Benefit Plan Amount Fields Enhancement. Two procedures, CREATE_EFF_DATE_RG and CREATE_DYN_RG2 were modified to enlarge the number variables.

NOQJPLS.PLL

This library was modified to accommodate for RPE #25848, Expansion of Benefit Plan Amount Fields Enhancement. Two procedures, CREATE_EFF_DATE_RG and CREATE_DYN_RG2 were modified to enlarge the number variables.

PTRINST_DD_WEB_UPDATE_IND NOT NULL VARCHAR2(1)


PTRSERN_SPECIAL_RATE NUMBER(12,6)


PTVDISP_CODE NOT NULL VARCHAR2(6)


Section 23 Problem ResolutionsImplementing Oracle Password Expiration Feature in Cobol Programs


Section 23 Problem Resolutions

This section lists the problem resolutions included in Human Resources Releases 6.1 and 7.0, and Position Control Release 6.1 and 7.0.

Implementing Oracle Password Expiration Feature in Cobol Programs

(#85938)If the database uses Oracle password expiration, changes have been made to COBOL programs in order to run properly. Previously, if the process encountered the warning message that the user was within the grace period of password expiration, the process would abort upon connection due to the Oracle ORA-28002 warning. Now, this has been changed so that when this warning is encountered, the process will run to completion as expected.

The process will not abort for ORA-28002 warning message. Resolved in Human Resources Release 6.1.0.2.

Human Resources Menu

(#88002)The following 5 Finance forms were delivered with the main menu *HRS. These have been removed:

• Invoice Credit Memo Query

• Invoice Credit Memo

• Document History

• Purchase Order

• Purchase Blanket Change Order Query

Resolved in Human Resources Release 6.1.

Section 23 Problem Resolutions Validation Forms


Validation Forms

PTVERGR (#90355)Previously the description on the Earnings Group Code Validation form allowed 60 characters to be entered and the user encountered an ORACLE error. The form has been corrected to allow only 30 characters, the same as the table length. The ORACLE error will no longer be encountered by the user. Resolved in Human Resources Release 6.1.

PTVORGN (# 98072)This occurs when Banner Finance is not installed. When you performed an Organization search from the Salary Budget window of the Position Budgets form (NBAPBUD), and tried to exit with value from the Organization Code Validation form (PTVORGN), the following error message was being displayed: FRM-41805: Ambiguous item name: PTVORGN_CODE. This has been corrected by modifying the KEY-NXTKEY form level trigger. Resolved in Human Resources Release 7.0.

Rule Forms

NTRJINC (#95095)An edit on the Mass Job Salary Increase Rules Form (NTRJINC) required position class records to be entered for the salary table processed. In addition, the Employee Jobs Salary table had to be the same as the Position Class Rules value. If the salary table value was overridden on the position or job assignment, the job would not be updated since the salary table was not associated with the position class.

The NTRJINC form will no longer require the entry of a position class for each salary table record. If no position classes have been identified on the NTRJINC Salary table record, all jobs will be processed that fit within the other identified criteria set up on NTRJINC. When the salary table on the job has been overridden, the process will still select the job if no position classes have been defined in the NTRJINC position class block.

The position class selection criteria in routines sel_mm_dd_step_incr, sel_step_incr_others, and sel_step_zero had been changed. Jobs will now be selected when the job's position class matches one of the position classes defined on NTRJINC or when no position classes are defined on NTRJINC. Resolved in Human Resources Release 6.1.0.1.

Section 23 Problem ResolutionsRule Forms


NTRPCLS (#90096)Previously the Activity Date field was not being updated on the Position Class Rule Form (NTRPCLS) when inserts and changes were made. This has been corrected. The Activity Date field now gets updated accordingly. Resolved in Human Resources Release 7.0.

PTRBDCA (#87159)Previously, if the inclusion was established prior to the exclusions, the form would display the error message *ERROR* Code must not exist in BENEFIT/DEDUCTIONS INCLUSIONS BLOCK. The Benefits and Deductions Rules Form (PTRBDCA) was not checking whether the Inclusion was directed at the Employee or the Employer portion. This problem was corrected so that the edit will further check the Employee/Employer Indicator. If it is set at Employer, no error will be generated. If it is set to Employee, then the error condition is an invalid condition and the record cannot be saved. Resolved in Human Resources Release 6.1.

PTRECLS The following defects have been resolved:

• (#9694)Previously, once a default earnings code had been deleted from an NBAJOBS default earning record for an employee, the code could not be deleted from the Employee Class Rules Form (PTRECLS) record unless the effective dates matched exactly. Now, as long as the default earning code in question has been ended on all job records for the employees in that particular employee class, the earn code can be removed from the list of eligible earning for the employee class without error. Resolved in Human Resources Release 6.1.

• (#88238)Previously, when the LOV flashlight was selected on the Time Entry Rules of the Employee Class Rules Form (PTRECLS), the following message: *ERROR* LOV button is outside current block, was being displayed. This has been corrected. Resolved in Human Resources Release 6.1.

• (#92638)Previously, when a new hours-based earnings code that was to accrue seniority was added to the Eligible Earnings window, you would get an incorrect error message. This has been corrected to display the error message when the earn code is unit-based and to properly save when the earn code is hours-based. Resolved in Human Resources Release 7.0.

PTRBCAT (#84463)Previously when the default values for a deduction were being changed from a four digit number (such as 1000.00) to another four digit number (such as 1500.00), the update did not occur correctly. This has been changed and the value can now be updated as needed. Resolved in Human Resources Release 6.1.

PTRINST (#85105)The LOV on CA Pension/MIS window for MIS District Code field would not work properly. This has been corrected by renaming the column so that the table behind the LOV can be properly queried. Resolved in Human Resources Release 6.1.

Section 23 Problem Resolutions Applicant Tracking


PTRLCAT (#86865)The Activity Date field was not being updated when changes were made in any of the windows of the Leave Category Rules Form (PTRLCAT). This has been corrected so that the appropriate Activity Date field will be updated when changes are made on the form. Resolved in Human Resources Release 6.1.

PTRPICT (#57535)Previously, you could not remove information from the Web and Departmental Time Entry Rules block of the Payroll Identification Form (PTRPICT), once entered and saved. An error message, *Error* Enter a valid cutoff time, would be displayed. Now, the form has been updated and you can update or remove data from this block. Resolved in Human Resources Release 6.1.

Applicant Tracking

PPACMNT (#83112)Previously, when you accessed the ID Search button to select a Key block value (and utilized the Exit with Value function), a number of form errors were encountered. This has been corrected. Now, you can use the ID Search button to choose the ID you want to work with and to view, modify, or create comments records as needed. Resolved in Human Resources Release 6.1.

Biographic & Demographic Information

PPAIDEN (#84478)When making changes to address information via the Identification Form (PPAIDEN) the User ID and Activity Date fields were not getting updated to reflect who made the change and when the change was made. This occurred only when a field was set to NULL and it previously had a value.

Also, the Rollback function could not be executed when no address records were available in the Address Information window of the Identification Form (PPAIDEN).

These defects have been corrected. Resolved in Human Resources Release 6.0.1.

Section 23 Problem ResolutionsBenefits and Deductions Administration


PPIADDR (#92317)Previously HR security was not invoked on the Address List Inquiry Form (PPIADDR) allowing all users to see potentially confidential employee address information. Now, the security routines have been modified to enforce the HR security rules as established by the user/administrator on the Organization Security Form (PSAORGN), the Employee Class Security Form (PSAECLS) and/or the User Code Rules Form (PTRUSER). The information is now secure based on the site's security policies and security set ups. Resolved in Human Resources Release 7.0.

Benefits and Deductions Administration

PDABCOV (#89765)Some changes to end dates on Beneficiary Coverage Form (PDABCOV) were not being recorded in the history table PDRBCHS, and as a result, the Audit Trail Report (PORAUDT) would not show an accurate audit trail. This problem has been corrected, and now the changes are recorded in the audit trail. Resolved in Human Resources Release 6.0.2.1.

PDABENE The following defects have been resolved:

• (#84057)Previously, the Beneficiary Form (PDABENE) allowed you to check or uncheck the College Indicator check box on the "S"elf relationship record. This functionality was inadvertently removed. This problem has been corrected. Now, you can now use the College Indicator check box on the "S"elf record. Resolved in Human Resources Release 6.1.

• (#88077)When adding a new beneficiary record on the Beneficiary Form (PDABENE) by selecting an existing ID from the LOV (flashlight) button, you would get an error indicating that the SSN could not be changed. This was an incorrect error as the user was not trying to change the SSN, they were only adding the PPAIDEN record as a dependent record on PDABENE where the SSN is not a required field. This problem has been corrected and now you can utilize the LOV to select the proper record to add to the Beneficiary Form (PDABENE). Resolved in Human Resources Release 6.1.

• (#93656)Previously, when updating information on the Beneficiary Form (PDABENE), the Activity Date and Time were not correctly being updated. This has been corrected. Resolved in Human Resources Release 6.1.0.1.

Section 23 Problem Resolutions Benefits and Deductions Administration


PDADEDNPTRBDCAPTRBDMCPDAFLEXPDABDSUPDCCOCE

(#94904)These forms displayed amounts incorrectly by truncating starting with the zero on the right side of the decimal. This did not cause incorrect data in the underlying tables, but it did affect the display.

For example, amounts of 5.23, 5.00, 5.10, & 5.03 were displayed as follows:

"5.23" was being displayed as "5.23" correctly."5.00" was being displayed as "5" - truncating the value at the zero."5.10" was being displayed as "5.1" - truncating the value at the zero."5.03" was being displayed as "5.03" correctly.

This has been corrected so that the forms in question now display the four decimal places if they have a plan associated with their calc rule; two decimal places if flat amount or percentage.

As a note, the LOV display will continue to truncate the trailing zero(s) on the right side of the decimal. Resolved in Human Resources Release 6.1.0.2.

PDADEDN The following defects have been resolved in the Employee Benefit or Deduction Form (PDADEDN):

• (#89197)Under certain conditions, the Employee Benefit or Deduction Form (PDADEDN) would allow an employee to have two precluded deductions active on the same day. This problem has been corrected. Now, two precluded deductions cannot be setup on the same day. Resolved in Human Resources Release 6.0.1.1.

• (#89668)The Employee Benefit or Deduction Form (PDADEDN) would erroneously delete the Self Beneficiary Coverage record (PDRBCOV) and the Excluded Pay ID record (PDRXPID - if one existed) when a deduction record was deleted, but the deduction still existed on a past Effective Date. This problem has been corrected. If there are more than one PDRDEDN effective-dated records existing, then beneficiary records will not be deleted. Resolved in Human Resources Release 6.0.1.1.

• (#92278)When a deduction code is being created for the first time and a plan or amount was required, using certain navigation options, it was possible to create records where the first deduction detail record effective date did not match the base deduction begin date. This caused processing problems. The form navigation has been corrected to now present an error message that the base record must be saved first before creating a future-dated deduction record. Resolved in Human Resources Release 6.1.0.1.

Section 23 Problem ResolutionsBenefits and Deductions Administration


PDAFCLM (#85297)Previously, when the Claim Amount entered was more than the available or deposited amount, you would receive an error message. The form has been changed to allow the entry of the claimed amount, but you will receive an error message if the Amount Paid is in excess of the Available or Deposited amounts (depending on whether the deduction is for a health or dependent care account). Resolved in Human Resources Release 6.1.

PEAFMLA The following defects have been resolved in the Employee FMLA Information Form (PEAFMLA):

• (#37356)A navigation and form display problem occurred when you moved from the Usage block to the Tracking block in the Employee FMLA Information Form (PEAFMLA), the dates did not correspond between the two blocks, when multiple tracking records existed. This problem has been corrected so that the dates for the record in Tracking block are same as the ones from the Usage block. Also, the Leave End Date on the usage block should never be allowed to be changed to a date less than what has been recorded as the Leave End Date in the Tracking block. This has been addressed by adding a new edit to compare the two dates and not allow this instance to recur. Resolved in Human Resources Release 6.1.

• (#93803)In previous releases, it was possible to skip the Base Record block of the Employee FMLA Information Form (PEAFMLA) and go right to the Usage and/or Leave Tracking windows without adding the parent record. This left orphaned records in the database that could not be matched up with the appropriate FMLA year. It can also caused problems in tracking since the database was unable to give the appropriate number of weeks/days left of FMLA eligible time. This has now been corrected to give an error anytime you try to navigate past the Base Record block without saving a Base Record first. This will eliminate the orphaned records possibility and keep all FMLA records in sync. Resolved in Human Resources Release 6.1.0.1.

PEIDTOT The following defects have been resolved in the Deduction Year To Date Totals Form (PEIDTOT):

• (#89549)The Deduction Year To Date Totals Form (PEIDTOT) was displaying wrong data when the Query Year Type field was set to Plan in the Key block and a Rollback and re-query had been performed. If you selected the Plan Query Year Type and viewed the data the totals based on plan year were displayed. If you then performed a Rollback function and re-queried without changing any values in the Key block, the Fiscal Year dates and data were displayed. This only occurred when selecting Plan for the Query Year Type. This problem has been corrected. Resolved in Human Resources Release 6.1.

Section 23 Problem Resolutions Employment Administration


• (#93420)A problem with the Deduction Year To Date Totals Form (PEIDTOT) was encountered when choosing the Plan radio button as the option in the Key block. Upon clearing the Key block after filling it out the first time, the dates were incorrect the second time resulting in incorrect query results in the form. This has been corrected so that the correct 12 month period is selected (as identified from the Benefits and Deductions Rules Form (PTRBDCA) Start Month Indicator) in combination with the year selected in the Key block. This insures correct and consistent query results. Resolved in Human Resources Release 6.1.

Employment Administration

NBAJOBS The following defects have been resolved in the Employee Jobs Form (NBAJOBS):

• (#13610)Occasionally when multiple users entered job labor distribution information or new jobs at the same time, duplicate encumbrance numbers would be assigned to different FOAPALS. This has been resolved by modifying the Employee Jobs Form (NBAJOBS) to utilize a new p_calc__num procedure. Resolved in Human Resources Release 7.0.

• (#31805)The form was not functioning according to how the Validate Position Budget indicator field on the Position Installation Rules Form (NTRINST) was set. When the indicator was set to ERROR, the form would commit a job record allowing it to go over budget and only issue a warning message. This problem has been corrected. Now, the form displays an error message and does not allow the record to be saved when the indicator is ERROR. Resolved in Human Resources Release 6.0.0.1.

• (#62951)The Employee Jobs Form (NBAJOBS) would not compile when Payroll was not installed. This problem has been corrected by removing the reference to PTRJCRE. Resolved in Human Resources Release 6.1.

• (#79606)The Employee Jobs form (NBAJOBS) could cause the Base Job End Date to be incorrect in some scenarios when the Position Control Installation Rule on NTRINST was set to allow the insertion of job detail records prior to existing job detail records.

If two future effective-dated records exist, with the latest effective date terminating the employee, and you deleted the effective-dated record prior to the termination record, the Base Job End Date was cleared. The result was an NBRJOBS record with a status of terminated and an NBRBJOB record with a null end date.

Section 23 Problem ResolutionsEmployment Administration


If an employee had a series of job effective dated records and you terminated the record prior to the last effective dated record, the End Date was set to be the Effective Date of the terminated record. The future change record was not considered when populating the End Date.

Both the problems have been corrected to reflect the correct End Date when the greatest effective dated record has a status of terminated, or a null End Date when the greatest effective dated record has a status other than Terminated. Resolved in Human Resources Release 6.1.

• (#85322)When entering a new effective dated record to terminate an employee with a terminated supervisor, the form looked at the employee termination date to determine if the invalid supervisor message should be displayed. The error should display only if the employee termination date is after (greater than) the supervisor termination date. This allows an employee and supervisor to be terminated on the same day without incorrect error messages. Resolved in Human Resources Release 7.0.

• (#88112)The NBAJOBS End Date was not being populated when creating a new effective-dated change as a termination. This problem has been corrected and you cannot exit the form when a termination exists without populating the End Date or changing the Job Detail status. Resolved in Human Resources Release 6.1.

• (#90898)When future changes were added in the Detail window of the Employee Jobs Form (NBAJOBS), where the effective date was in a fiscal year that was not checked as Active on NBAFISC, the PERJHIS record was not written out. This problem has been corrected. Now, a PERJHIS record is always written when a new job detail record is changed or inserted. Resolved in Human Resources Release 6.0.0.2.

• (#92337)This defect only affects those clients who allow for the insertion/deletion of NBAJOBS records between effective dates. This is accomplished by setting the Insert Job Detail Data Between Existing Records indicator on the Position Control Installation Rules Form (NTRINST) to Allowed.

Two scenarios using NBAJOBS have been disabled so as to remove the possibility of corrupted data records being saved to the database. One of the scenarios allowed you to delete the first effective dated record when future dated records exist. You are given the proper warning messages, but deleting the first effective dated record caused an orphaned record in the database. This has been corrected so that the first effective dated record cannot be removed. An error message has been added to this effect.

The second scenario included trying to insert a record with an effective date prior to the job begin date. This is no longer allowed. An error message is presented when you tried to insert this new record. Resolved in Human Resources Release 7.0.



• (#93718)The Employee Jobs Form (NBAJOBS) now allows job changes to invalid supervisor information after the effective date of the supervisor termination. Resolved in Human Resources Release 7.0.

• (#96282)The Employee Jobs Form (NBAJOBS) was allowing terminated records that were prior to the last paid date to be removed. This would happen if the termination date were some other date other than the last day of the pay period. This deletion should not happen because there are payroll records that exist. Now, the termination record cannot be removed once pay history exists for the pay period in which the termination date falls. Resolved in Position Control Release 6.1.0.3.

• (#96501)Previously, when a time sheet organization code was invalid, the Employee Jobs Form (NBAJOBS) did not allow future changes to be made via the Job Detail window. This has been corrected to allow the future change to be saved and viewed on NBAJOBS. Resolved in Human Resources Release 7.0.

NBIJLST (#88821)The sort order on the Employee Job Inquiry Form (NBIJLST) has been changed to sort by effective date rather than the original sort based on the employer code. Now, the earliest records are displayed at the top of the list with the most recent record at the bottom of the list. Resolved in Human Resources Release 6.1.

PEAEMPL (#89863)When processing Leave by Employee, the Employee Form (PEAEMPL) was not inserting new leave codes when an employee was changing from one Leave Category that did not grant specific leave, to a new one that included a new leave code. This problem has been corrected so that when you change an Employee Class or Leave Category, the appropriate leave records will be inserted into the employee's leave balances. Resolved in Human Resources Release 6.0.2.1.

PEAESCH (#98142)The Employee Status Change Form (PEAESCH) was not populating the Deduction End Date field with the correct value when a Terminate action was chosen, the All Records check box was checked, and the Personnel Change Date was less than the Last Paid Date.

When the Personnel Date value is less than the Last Paid Date, the form should terminate jobs and deductions as of the date in the Last Paid Date field. This was not happening for deductions. The form seemed to be using the pay period end date from the pay event (PTRCALN) in which the personnel date fell. This caused the error message: * ERROR* Deduction End Date cannot be prior to the Last Paid Date to display and you could not advance beyond the Key block.



Workaround: Do not check the All Records check box. After job termination information is entered, select the Employee Deduction Information option and manually enter the Last Paid Date value in the End Date field. Resolved in Human Resources Release 7.0.

PEAFACT The following defects have been resolved in the Faculty Action Tracking Form (PEAFACT):

• (#88329)A problem was detected when the approval information was being deleted from an appointment/tenure or rank record on the Faculty Action Tracking Form (PEAFACT). This situation was only occurring when a site used the auto-approval feature and the user deleting the approval record was the same as the auto-approver associated with Electronic Approval Level Rules Form (NTRALVL). The approval information on the main appointment/tenure and rank pages would still display Approved even when the approval records were removed. This problem has been corrected. Now, when an approval is removed, the affected main record is reset. The Decision and the Decision Date fields are set to N and Null respectively, for both Tenure and Rank Actions, when the approval action is deleted. Resolved in Human Resources Release 6.1.

• (#89937)When using auto-approval of faculty actions, you wanted to change the automated approval record to None, the Status was not being updated on the Main block of the Appointment or Rank records. Additionally, if a change was made to the main data, the item would get re-approved. This problem has been corrected. Now, when an automated approval decision is changed to None, the main record is updated properly and the form does not re-approve the faculty record if additional changes are made. Resolved in Human Resources Release 6.1.

• (#98925)When using the Appointment/Tenure window of the Faculty Action Tracking Form (PEAFACT), if you attempted to create a record where the Appointment Begin or End Date fell between the dates of another record, the page created an error. However, the wording of the error message received was confusing and did not truly indicate what the problem was. The error message stated: *Error* This Action previous or future dated actions. Review existing records. This has been corrected. Now the following error message is displayed: *Error* This Action OVERLAPS previous or future dated actions. Review existing records. Resolved in Human Resources Release 7.0.



PEAJCDD The following defects have been resolved in the Job Changes Detail Display Form (PEAJCDD):

• (#92321, #91217)An Oracle error was reported when the user performed an Effective or Personnel Date query for a date range in 2000. This problem was corrected so that when Effective Dates or Personnel Dates are queried with a user-entered date range in 2000, the Oracle error will no longer appear. Resolved in Human Resources Release 6.0.6.1.

• (#89682)

(a) When executing a query where Date Type is set to Effective in the Key block, in addition to returning job records with effective dates that fall within the Query Date From and Query Date To fields entered in the Key block, the form would return the maximum effective-dated job record that was less than the entered Query From Date. Based on the query dates entered in the Key block, a record was still being returned even in those instances where no record should be returned.

This problem has been corrected. Now, the form returns only those records with effective dates that truly fall within the Query Date From and Query Date To fields entered in the Key block. Resolved in Human Resources Release 6.0.5.1.

(b) When executing a query where Date Type was set to Personnel in the Key block, the form was using the query dates entered to determine whether the Job Effective Date fell within the query date range. This problem was resulting in the compensation change records PERJHIS not being displayed, even though the Personnel Date was within the entered query date range.

For example, if an employee had two job records:

Job1 Effective = 07/15/03 with Personnel Date = 07/16/03

Job2 Effective = 07/16/03 with Personnel Date = 07/16/03

If the query dates entered were from 07/16/03 to 07/16/03, only the record for job #2 was being returned, even though job #1 had a compensation change on 07/16/03. Job #1 was not being displayed because the Job Effective Date was not within the entered query date range. This problem has been corrected. Now, the query logic for the Job block has been modified to strictly return records associated with the compensation changes retrieved, PERJHIS, based on the entered query dates. That is, in the above example, a query on Personnel Date for07/16/03 - 07/16/03 should return two compensation change records dated 07/16/03 and two jobs records. The Effective date of the job record is not relevant when querying based on Personnel date. Resolved in Human Resources Release 6.0.5.1.



PEALEAV (#88900)On attempting to update leave balance information for an employee whose employee status was other than Active, the following error message was received: *ERROR*: Employee record is not established for this ID. This problem has been corrected so that leave balance information can be updated, regardless of the employee status. Resolved in Human Resources Release 6.0.0.1.

PEAREVW (#83516, #82956)The List of Values (LOV) button was erroneously removed from the Reviewer ID field, resulting in navigation errors. In addition, when toggling out of Banner and accessing Banner again, the error message, FRN-41014: Cannot set attribute of null canvas item BUTTON_CONTROL_BLOCK.REVIEWER_ID_LBT, was being displayed. The form would ask you to commit changes when no changes were submitted. These issues have been corrected. Resolved in Human Resources Release 6.1.

PEIJHIS (#90542)Previously, when looking at a history of changes on job related data, the Job Status field was not being populated. This has been corrected so that the appropriate status is now displayed in the Job Detail block area of the Employee Job History Form (PEIJHIS). Resolved in Human Resources Release 6.1.0.1.

PEILHIS (#88801)When using the Leave by Job processing method, the mouse could not be utilized to navigate to the Position/Suffix fields in order to establish the Key block items to perform the leave history query. However, Keystroke navigation to access these fields was working correctly. This navigation issue has been corrected. Resolved in Human Resources Release 6.1.

PEIPCSN #97561The Employee Position Class Seniority form (PEIPCSN) would lock up when trying to perform a query. After entering a Chart of Accounts, Time Sheet Organization, Position Class and navigating to the next block, the bar in the lower right-hand corner would keep moving back and forth, but no values were returned. This has been corrected by reorganizing the WHERE clause of the pevpcsn view. Unnecessary index searches on the NBRJOBS and NBBPOSN tables were also suppressed. Resolved in Human Resources Release 6.1.0.2.

Section 23 Problem Resolutions Position Budgeting


Position Budgeting

NBAPBUD The following defects have been resolved in the Position Budget form (NBAPBUD):

• (#90717)The Position Budget form (NBAPBUD) was not allowing access to certain Chart/Organizations if a site had multiple COAS codes and a chart defined on the Position Control Installation Rules Form (NTRINST), even if you had security access. When you first went into NBAPBUD to view a position within their Chart/Organization security access you would receive the message: ERROR Orgn - You do not have permission to see this Orgn. If you went to another form that contained the COA code in the Key block of the form and returned back to NBAPBUD you were able to view the position information. The NTRINST Chart field had to be set to Null. This problem has been corrected and the NBRPTOT Chart code is now selected along with the Organization code. Resolved in Human Resources Release 6.0.0.1.

• (#92235)The first page of the Position Budget form (NBAPBUD) contained various data fields that reside on the Position table NBBPOSN. When fields on the Position Budget form (NBAPBUD) were updated, the Activity Date on NBBPOSN was not being updated. This problem has been corrected so that changes to the fields on the Position Budget form (NBAPBUD) also change the Activity Date. Resolved in Human Resources Release 6.0.1.1.

• When processing an organization transfer, any expended amount for a premium earning budget was being subtracted from an existing premium budget amount pending posting to Banner Finance. This was resulting in the understatement of budget amounts in Finance. As organization transfers have no relevance to budget amounts pending posting, the subtraction of the expended amount from the to be posted amount on premium earnings has been removed. The amount to be posted for premium earnings will be unaffected by the processing of an organization transfer. Resolved in Human Resources Release 6.1.

NBAPOSN The following defects have been resolved in the Position Definition Form (NBAPOSN):

• (#91224)Selecting the icon next to the Salary Table field was resulting in the following error message: LOV button is outside of the current box. This occurred in internet-native as well as client-server Banner. This has been corrected. Now the List of Values operates correctly without displaying the error message. Resolved in Position Control Release 7.0.

Section 23 Problem ResolutionsHealth and Safety Administration


• (#92877)The Position Definition Form (NBAPOSN) was not compiling if Banner General 6.1.1 was installed. This has been corrected. Resolved in Human Resources Release 6.0.1.1.

NBQPOSN The following defects have been resolved in the Position List Form (NBQPOSN):

• (#92956)The Position List Form (NBQPOSN) was not displaying budget organization codes for all approved positions when multiple charts of accounts existed. This has been corrected. Now, regardless of the number of charts an organization may be set up under, the code and description will now be displayed on the NBQPOSN form appropriately for the specified position and chart. Resolved in Human Resources Release 6.1.0.1.

• (#95681)When searching for Positions using the Position List Form (NBQPOSN) and querying by Organization Code, the Position List Form (NBQPOSN) was not displaying budget organization codes for all approved positions when multiple charts of accounts exist. Only one COA would display if you used more than 2 characters with a wildcard, or entered the exact Organization code for the query. This has been corrected by modifying the pre-query of NBBPOSN by adding the following line:

AND B.FTVORGN_COAS_CODE = A.NBRPTOT_COAS_CODE))');

Resolved in Human Resources Release 6.1.0.2.

Health and Safety Administration

PEAHSIN (#89688)Previously, upon trying to change dates on the Health and Safety Incident Form (PEAHSIN), the cursor would get locked into a Date field. This situation would occur if the date entered in the Date of Incident field was changed and saved to a date greater than the Begin Date on the Medical Condition window. The Banner session had to be terminated in order to exit the form. This problem has been corrected by relaxing the edits from the field level to the save level and providing an edit on the Date of Incident field by comparing the Medical Condition dates. You may now change dates and receive errors, and be able to navigate to the other date fields for correction. Resolved in Human Resources Release 6.0.3.

Section 23 Problem Resolutions Time Entry and Payroll Processing


Time Entry and Payroll Processing

PHAADJT The following defects have been resolved:

• (#86028)The Adjustment Processing Form (PHAADJT) was setting the Reconciliation Indicator field and Reconciliation Date of an original event to null if an Erase adjustment was performed on an adjustment to that event. This problem has been corrected. Resolved in Human Resources Release 6.0.0.1.

• (#86371)Deduction records were not being extracted correctly when a deduction is terminated on the last day of pay period and the previous status was either Exempt or Waived. This has been corrected so that the extract logic matches the Time Processing Report (PHPTIME) and the Waived and Exempt records are now processed correctly when the deduction is terminated on the last day of the pay period. Resolved in Human Resources Release 6.1.0.2.

• (#87921)The Adjustment Processing form (PHAADJT) was allowing you to void a redistribution event. This was creating an out-of-balance condition since a redistribution transaction had already generated a reversal of money. The form has been changed to preclude you from creating a void from the reversal sequence of the redistribution transaction. Resolved in Human Resources Release 6.1.

• (#89059)When a site established the Leave Processing Method as Leave By Job, an error was encountered when using the Adjustment Processing Form (PHAADJT). On entering the pay adjustment information in the called On-Line Time Entry Form (PHAHOUR), an error was created when an Earn code that was tied to a Leave code was used. This situation has been corrected so that any eligible Earn code may be used on the adjustment transaction. Resolved in Human Resources Release 6.0.0.2.

• (#91635)When processing a manual transaction and the print indicator was manual, the Adjustment Processing Form (PHAADJT) was giving an incorrect message and was not allowing you to exit the form or complete the document history information. After entering document information and attempting to save, the cursor would go to the Bank Routing Number field. Once this error was encountered, all manual print transactions thereafter produced the same message forcing you to exit Banner and then go back in to continue without getting this message. This problem has been fixed. Now you will be able to enter the check data correctly. Resolved in Human Resources Release 6.1.0.1.

Section 23 Problem ResolutionsTime Entry and Payroll Processing


• (#91721)Multiple COAS codes were causing the Posting Override Date edit to fail in the Adjustment Processing Form (PHAADJT). If a site had multiple COAS codes then the NTRINST COAS code field must be null. So, when you first go into the Adjustment Processing Form (PHAADJT) to create an adjustment pay event you would receive the following error message: *ERROR* Posting Override Date does not fall within a defined accounting period. This has been corrected. Resolved in Human Resources Release 6.1.0.1.

• (#92021)The correction to defect #88881 disallowed you from being able to void 'Void' pay events. This has been corrected, and the Adjustment Action of Void may be applied to a record that had previously been voided. Resolved in Human Resources Release 6.0.6.1.

• (#92319)Previously, when an event was Redistributed, the Reconciliation Indicator and Reconciliation Date field values would get updated to reflect those for the event being redistributed. These fields should not get changed since a redistribution only adjusts the distribution of the accounting information and does not effect the indicator or the date of the event. The process has been fixed and these fields now do not change by a Transaction Type of Redistribution. Resolved in Human Resources Release 6.0.6.2.

• (#93807)This is a multi-part defect:

(a) The reconciliation indicator and the date value was being nulled when an Erase adjustment action was done. These fields were similarly being nulled when a Redistribution adjustment action was processed followed by a Re-issue. This has been corrected. Now, the Reconciliation indicator and the date are retained during erase and redistribution actions. Resolved in Human Resources Release 6.1.1.1.

(b) When a Void adjustment action is applied to a Void record, the void event must be able to set the Reconciliation Indicator back to R for direct deposit records and add the History Date as the Reconciliation Date. This has been corrected. Now, when a voided event is voided again, in the case of direct deposit, the Reconciliation Indicator is set back to R and the Reconciliation Date is set to the History Date. In the case of a check, R is set for the reconciled check and blank is set for unreconciled. Resolved in Human Resources Release 6.1.1.1.

• (#93979)Performance issues were identified, and the query was tuned to use the primary key of the table reducing the query elapsed time. Resolved in Human Resources Release 6.1.0.1.



PHAADJT/PHCDEDN

(#92360)The Adjustment Processing form (PHAADJT) was displaying an error message when re-issuing checks/direct deposits or performing redistributions for 1042 recipients when earnings being paid in the original event were excluded from the 1042 deduction in question. This error occurred when balancing the transaction, *ERROR* Nonresident alien 1042-S data missing.

The History Deductions Form (PHCDEDN) was displaying a warning message on 1042 employees when exiting the form. This warning occurred when the form was queried for a re-issue or redistribution, *WARNING* Nonresident alien 1042-S data missing.

These issues have been corrected to display the messages only when the PHRDEDN_APPLICABLE_GROSS for a deduction is not equal to zero. The History Deductions Form (PHCDEDN) was resolved in Human Resources Release 6.1.0.1, and the Adjustment Processing form (PHAADJT) was resolved in Human Resources Release 6.1.0.3.

PHADSUM • The following defects have been resolved in the Department Payroll Summary Form (PHADSUM):

• (#93262)If the time sheet approval queue included an 'FYI' person and the FYI person did not acknowledge the time sheet prior to all approvers approving the time sheet, then the 'FYI' person would receive an error message when they tried to acknowledge. This occurred only if the time sheet was in the Approved status. The time sheet would remain in their queue and would always appear as an outstanding item. This has been corrected. Now an FYI action is allowed in the pending, approved and completed statuses so as to clear the FYI person's queue. Resolved in Human Resources Release 6.1.0.1.

• (#93468)Performance problems were corrected when doing a Search look up in the Jobs block. Resolved in Human Resources Release 6.1.0.1.

PHAHOUR The following defects have been corrected in the On-Line Time Entry Form (PHAHOUR):

• (#78304)The On-Line Time Entry Form (PHAHOUR) had not been resetting the Change Indicator on the Mass Time Entry Form (PHAMTIM) properly when an individual employee’s payroll records were deleted. This problem has been corrected and the indicator now sets correctly. Resolved in Human Resources Release 6.1.



• (#85462)The On-Line Time Entry Form (PHAHOUR) was not resetting the dispositions correctly when an employee had multiple jobs and earnings were deleted from one of the jobs that changed the disposition for that job. This situation allowed the potential for the other jobs to be processed through the payroll causing incorrect hours and wages with the job record not getting processed. This problem has been resolved. The form now adjusts the disposition for all jobs held by the employee so that all jobs are processed at the same time. Resolved in Human Resources Release 6.0.01.

• (#93981)The On-line Time Entry form (PHAHOUR) allowed you to change hours for an earning when the employee was at Disposition 40 and would not reset the record back to Disposition 20. This allowed an employee to proceed through the payroll in an out of balance situation resulting in incorrect payroll records. Now, the form has been modified. When earnings are changed, the disposition is reset to 20 so that the record can properly be processed through the payroll cycle. Resolved in Human Resources Release 6.1.0.1.

PHARECN (#85842)In prior versions, the Bank Reconciliation Form (PHARECN) allowed you to change a document from reconciled to outstanding. Prior defect fixes changed the functionality and you were no longer able to change a document from reconciled to outstanding. This functionality has been corrected. Now when you remove the 'R' and save the record, the system will update the record to have a null value for the Reconciliation Indicator and the Reconciliation Date. Resolved in Human Resources Release 6.1.

PHAREDS The following defects have been corrected in the Labor Redistribution Form (PHAREDS):

• (#8227)The Labor Redistribution Form (PHAREDS) was not displaying defaults associated with the organization code entry. This has been corrected to allow the organization override and default logic, as well as Fund defaults in the Labor Redistribution Form (PHAREDS) to occur by modifying N$_EDIT_FUND and N$_EDIT_ORGN. When changing existing labor distribution records the existing field values must be removed to allow the new default logic to occur. Resolved in Human Resources Release 7.0.

• (#77736)When processing a fund redistribution, the form was not considering the Fund Expenditure End Date properly. If you attempted to post expenditures (by filling out a correct Posting Date) beyond the Fund Termination Date and before or on the Fund Expenditure End Date, the form would issue an error message indicating that the fund was terminated. This problem has been corrected so that a redistribution for expenses could be processed beyond the termination date of the fund as long as it was on or before the expenditure end date. Resolved in Human Resources Release 6.1.



• (#94818)The Labor Redistribution Form (PHAREDS) did not split the labor distribution when a payroll crossed fiscal years. The entire transaction was posted based on the Posting Date entered in the form, which was a required field. This has been corrected to allow for a Null override of the Posting Date when the pay event is split across fiscal years. New edits have been added to the form as follows:

(a) When a Posting Date is entered, an edit will validate that the Banner Finance accounting period is open (or in accrual). If not, an error message will be displayed, *ERROR* Accounting period closed. Re-enter a new Posting Date.

(b) When a Posting Date is not entered:

Validate that the pay event spans two fiscal years. If it doesn't span two fiscal years, an error message will display, *ERROR* Posting Date is required if pay period does NOT cross fiscal years.

Validate that the prior fiscal year accounting period is not closed. If the prior fiscal year accounting period is closed, an error message will display, *ERROR* Old fiscal year period for split pay event is closed. Posting Date is required.

A posting date is calculated based on the fiscal year (prior or new) in which the split part of the pay event falls. If the split is effective during the prior fiscal year, the calculated posting date is typically in the prior fiscal year. If the split is effective during the new fiscal year, the calculated posting date is typically in the new fiscal year.

When editing labor distributions, the scope of the changes is limited to the pay event being edited and will not affect any other pay events that may have been queried. This specifically applies when the Change All box is checked.

(c) If the Posting Date is changed the form will re-edit the labor distributions using the new Posting Date. This will happen during the OK Changes or save/commit.

(d) Changes to the labor distribution edits:

When a Posting Date is entered, during data entry the FOAPAL is edited against Banner Finance using the entered posting date. A re-edit is also performed during the save.

When a Posting Date is not entered, during data entry the FOAPAL is edited against Banner Finance using the calculated posting date. A re-edit is also performed during the save.



If the 'Change All' box was checked, the FOAPAL is edited against Banner Finance using the calculated posting date for each earnings labor distribution in the pay event. If a FOAPAL component is invalid, an error message is displayed similar to, *ERROR* Fund 1000 is terminated. See Job A10001-00, Effective Date 10-AUG-2004, Earn Code REG, Shift 1 of this pay event.

(e) New edits on the Search and Replace Posting Date.

The Search Posting Date remains a required field. An edit now validates that the Banner Finance accounting period is open (or in accrual). If not, an error message will be displayed: *ERROR* Accounting period closed. Re-enter a new Posting Date. Resolved in Human Resources Release 7.0.

PHATIME The following defects have been corrected in the Electronic Approvals of Time Entry Form (PHATIME):

• (#88918)When deleting a time transaction that was classified as a Leave Report, the following message was being displayed in error: *ERROR* Leave Code is not defined on PTVLCAT. The system displayed an additional message: Removing this record will delete the employee's time transaction. Do you want to delete this transaction? On responding Yes, the form then displayed: Delete Process is Complete. Following these messages, another error popup window was being displayed: *ERROR* Leave Code is not defined on PTVLCAT. This message had to be acknowledged twice, and then the form would close, even though additional employees existed in the Leave Report list. This problem has been corrected. The Electronic Approvals of Time Entry Form (PHATIME) no longer displays the error message regarding the Leave Category Validation Form (PTVLCAT) and you can now remove a Leave Report without the form terminating its process. Resolved in Human Resources Release 6.0.1.1.

• (#93396)Superusers can now submit any leave report or time sheet in a "in progress" status when the time/leave entry period is open. Previously, superusers could only submit when the time/leave entry period was closed.

A superuser can also extract any leave report/time sheet when the leave/time entry period is open or closed. If the entry period has not opened, then no one can extract a leave report/time sheet. Previously, superusers could only extract when the time/leave entry period was closed.

These extended capabilities were added so superusers have more flexibility in handling time sheets when an employee is unable to extract or submit their time sheet on time. If the superuser knows that the employee won't be able to extract or submit their time sheet before the entry period closes, he/she won't have to wait for the entry period to close to process a time sheet for the employee.

This change was delivered with the 6.0 release of Banner Human Resources and Employee Self-Service, but was not documented in the Release Guides. Documentation defect resolved in Human Resources Release 6.1.



• (#88427)A problem was discovered with regard to roles and actions that could be taken on Time sheet and/or Leave Records by individuals based on their role. Previously, the user would have to check the superuser box in order to make any changes to the Electronic Approvals of Time Entry Form (PHATIME) record regardless of whether or not they were a superuser. Approvers and/or originators had to do the same thing to get access to the record once again. This problem has been corrected and now the proper roles are enabled and given access as appropriate for the situation. Resolved in Human Resources Release 6.0.0.1.

• (#88837)During the extract of employee time sheets on this form (Transaction Status as Not Started), records were not immediately displayed after the extraction. In order for the form to display extracted employees, you had to manually change the Transaction Status in the Key block to In Progress and then perform a Next Block function to view the extracted employees. In the 5.x release of this form, the employees were automatically displayed after the extract and the Transaction Status in the Key block changed to In Progress.

To return functionality to the Electronic Approvals of Time Entry Form (PHATIME), the form has been corrected so that employees will now be displayed after the extraction process has been executed and Transaction Status will be set to In Progress. Resolved in Human Resources Release 6.0.5.2.

• (#89755)A problem was reported if you were the originator as well as the approver of the time sheet. If you wanted to submit the time sheet and immediately approve the time records, the appropriate options (Approve and Return for Correction) were not immediately available, as in past releases. You had to rollback to the Key block and then navigate back to the employee for the approval options to become available.

This problem has been corrected. Now, as soon as you submit the time sheet for approval, the Approve and Return for Correction options are enabled, You can enter time, submit time, and approve time without rolling back to the Key block or exiting the form. Resolved in Human Resources Release 6.0.5.2.

• (#91837)After extracting time, when you would select a valid employee and then go to the Time Entry block on the Electronic Approvals of Time Entry Form (PHATIME) using the Search button to select a valid earnings code, an error message would be displayed multiple times indicating that the reference could not be resolved. This problem has been corrected. The error message no longer appears. Resolved in Human Resources Release 6.0.5.1.

• (#93468)Performance problems were corrected when doing a search look up in the Jobs block. Resolved in Human Resources Release 6.1.0.1.

Section 23 Problem ResolutionsTax Administration


• (#94098)In previous versions of the Electronic Approvals of Time Entry Form (PHATIME), a warning message would appear to notify you that the employee may have an insufficient leave balance if the hours entered for leave earning codes exceeded the available balance. The message was not appearing in the 6.x version of the form. The insufficient leave balance message now appears for any departmental entry for Time Sheet, Leave Request, or Leave Report. Resolved in Human Resources Release 7.0.

PHIETIM • (#93468)Performance problems were corrected when doing a search look up in the Jobs block of the Web/Department Employee Time Inquiry Form (PHIETIM). Resolved in Human Resources Release 6.1.0.1.

Tax Administration

PXA1099 (#92478)The Auto Hint for the ID field in the Key block on the 1099-R Form (PXA1099), erroneously stated that you could leave the ID field blank in order to see all 1099s for the year that had been specified in Key block. This functionality is not available on the form and the message has been updated to state: ID Number; press LIST for Name/ID search. Resolved in Human Resources Release 7.0.

Electronic Approvals

NOAEPAF (#89280)Previously, when using one of the search options (POIIDEN, SOAIDEN or GUIALTI) on the Electronic Personnel Action Form (NOAEPAF) to change the ID from one that was used previously, the Key block information would not clear properly. This would cause the form to produce, Field must be entered, errors. This problem has been corrected and upon rollback, the Key block information is cleared so that the appropriate information associated with the ID and transaction number in the Key block is displayed. Resolved in Position Control Release 6.0.0.1.

Section 23 Problem Resolutions CA-MIS Reporting


NOFPBAL (#93502)When submitting an Electronic Personnel Action Form (NOAEPAF), certain combinations of factor, assignment salary and annual salary may result in a rounding error that causes the electronic approval application to error giving message: ERROR Annual salary divided by job factor does not equal assigned salary. This has been corrected. The error message will not be generated if the difference between the calculated assigned salary and the assigned salary is less than or equal to 0.01. Resolved in Position Control Release 6.1.0.1.

NOPEAMA The following defects have been resolved in the EA Mass Apply Process (NOPEAMA):

• (#86640)The EA Mass Apply Process (NOPEAMA) would abort when processing a new job whose Encumbrance Indicator was ‘V’alue input, and no salary encumbrance amount was entered. The ORA-01407 error message was received. The NOKMUP1.SQL package has been corrected so that the process automatically inserts a zero in the encumbrance amount. Resolved in Position Control Release 6.1.

• #94895 Technical Fix: In nokfoa1.sql, when p_edit_foapal was called with a null value it immediately exited. The cur_handle variable had already had a cursor assigned to it because it had been initialized in the declarative section. This caused an ORA-1000 MAX OPEN CURSORS EXCEEDED and ORA-1001 INVALID CURSOR error in programs that use this procedure such as the EA Mass Apply Process (NOPEAMA). Resolved in Position Control Release 7.0.

CA-MIS Reporting

PDAASGN (#89603)This defect has been resolved. For details, refer to the Employee Assignment Extract Form (PDAASGN) on page 174. Resolved in Human Resources Release 6.0.4.

PEPEDEX The following defects have been resolved in the Employee Demo Extract Process (PEPEDEX):

• (#87981)The Reporting Domain parameter of this process was ignoring non-faculty employees with secondary or overload jobs. This has been corrected. Resolved in Human Resources Release 6.0.4.

Section 23 Problem ResolutionsReports and Processes


• (#95615)The Report Date field on the process was displaying the year incorrectly; for example, 10-NOV-0003 rather than 10-NOV-2003. This has been corrected by updating the format of the Report Date field. The process now displays the year correctly. Resolved in Human Resources Release 7.0.

Reports and Processes

NBPBUDM The following defects have been resolved in the Budget Maintenance Process (NBPBUDM):

• (#13610)Occasionally when multiple users entered job labor distribution information or new jobs at the same time, duplicate encumbrance numbers would be assigned to different FOAPALS. The Budget Maintenance Process (NBPBUDM) was changed to use the new p_calc_num procedure in place of the assign_encd procedure, as well as modifying the load_encd procedure. The nopenum.sql was also modified to direct the p_calc_encd_num procedure to utilize the SOBSEQN table. Resolved in Human Resources Release 7.0.

• (#94102)On some processing platforms, the program produced a core dump and would never complete its execution when using the encumbrance recasting method. This has been corrected. Resolved in Human Resources Release 6.1.0.1.

• #96956Duplicate encumbrance sequence numbers could be generated when reactivating job records terminated in the previous fiscal year. When running the Budget Maintenance Process (NBPBUDM) with the budget parameter set to N and the encumbrance parameter set to Y, the fiscal year is not a required entry and was not being picked up as the Active fiscal year. This has been corrected by modifying the assign_encd procedure to get the fiscal year from the max_seq_encd. Resolved in Position Control Release 6.1.0.3.

Section 23 Problem Resolutions Reports and Processes


NBPMASS The following defects have been resolved in the Mass Salary Table Update Process (NBPMASS):

• (#88679)The parameter description field on the Parameter Value Validation Form (GJAPVAL) for parameter 01 of the Mass Salary Table Update Process (NBPMASS) does not provide an adequate description of the various parameter values that are valid. The descriptions have been updated to be consistent with other processes with this same parameter: Process Mode and Report Mode descriptions are used for the parameter 01. Resolved in Human Resources Release 6.1.

• (#94777)The following error message was encountered when running the Mass Salary Batch Update Process (NBPMASS) when the MM/DD fields were null on the Employee Jobs Form (NBAJOBS): ORA-01840: input value not long enough for date format. This has been corrected by modifying the sel_mm_dd_step_incr routine to add NVL to all occurrences of nbrbjob_step_incr_mon and nbrbjob_step_inc_day. Resolved in Human Resources Release 6.1.0.1.

NBPBROL The following defects have been resolved in the Budget Roll Process (NBPBROL):

• (#87664)Previously, the Budget Roll Process (NBPBROL) was allowing the approval of the new fiscal year when there were no existing working budgets in the new fiscal year. The old fiscal year was inactivated on the Fiscal Year Form (NBAFISC), and the HR/Finance Set Up Rules Form (NTRFINI) was set to the new year, and old position budget records were being set to Closed. This left the positions without approved budgets in the new year and caused problems when viewing job records for these positions. It was determined that the process would not produce the correct error condition when there were no working budgets for at least one qualified position in the new fiscal year.

This problem has been corrected so that the approval process will be executed when all qualified positions have the correct Working budget record. Any position that is qualified to roll into the new fiscal year, that does not have the target 'Working' budget record, will cause the Fiscal Year Approval process to error out. All on-going positions must have the appropriate working budget record for the new fiscal year to be approved. Resolved in Position Control Release 6.0.0.1.



• (#88797)The Budget Roll Process (NBPBROL) was deleting all working budget records from the NHRTBUD table when budgets were approved. When approving budgets, records are moved from the NHRTBUD table to the NHRDIST table by the Budget Roll Process (NBPBROL) process. Records being inserted and deleted in the NHRTBUD table were based on Fiscal Year, Budget ID and Phase. This could cause Working Budget records to be in NBRPTOT, and associated tables, with no corresponding NHRTBUD table record.

This has been corrected to look at the Fiscal Year, Chart of Accounts, Budget ID and Phase whenever inserting or deleting data from the NHRTBUD table. Resolved in Position Control Release 7.0.

• (#88106)The Budget Roll Process (NBPBROL), when run to approve budgets, was not populating the NHRDIST_INTERFACED_IND field when moving information from the Temporary Budget Table (NHRTBUD) to the NHRDIST table. This has been corrected to synchronize the NHRTBUD and NHRDIST interfaced indicators when records are copied from the NHRTBUD table. Thus, the NHRDIST_INTERFACED_IND would be a 'Y' if working budget records had been fed to Finance Budget Development. Resolved in Position Control Release 7.0.

• (#88015)The Budget Roll Process (NBPBROL) was not considering the Chart of Accounts value when rolling budgets into a working status. This problem only occurred for those clients using multiple chart of accounts on salary budget records. This happened when budgets had different chart of accounts values, but the same Budget ID and Phase. This defect had been corrected. Resolved in Position Control Release 7.0.

NBPSPUP #94895 Technical Fix: In nokfoa1.sql, when p_edit_foapal was called with a null value it immediately exited. The cur_handle variable had already had a cursor assigned to it because it had been initialized in the declarative section. This caused an ORA-1000 MAX OPEN CURSORS EXCEEDED and ORA-1001 INVALID CURSOR error in programs that use this procedure such as the Salary Planner Update Process (NBPSPUP). Resolved in Position Control Release 7.0.

NHRBDSTNHRDISTNHREDSTNHRSDST

(#85295)Previously, when trying to run processes Organization Payroll Distribution Process (NHRDIST), the Employee Distributions Report (NHREDST), the Employee Payroll Summary by Organization Report (NHRSDST) and the Budget Distribution Report (NHRBDST) without entering the Chart of Accounts in various parameters, the processes would abort with an Oracle error message, ORA-01400: cannot insert NULL into ("GENERAL"."GJBCOLR"."GJBCOLR_VALUE”). This error message was not very user-friendly and gave no indication of the actual error. The processes have now been modified to abort with an error message displayed in the log file as to where the process stopped. Resolved in Position Control Release 6.1.



NHPFIN1 (#86744)When Banner Finance is installed and the Finance Extract Process (NHPFINI) was run to interface COBRA transactions, the process would abort because the External Account Code field values were null. This problem has been corrected so that the process runs as expected and interfaces COBRA transactions appropriately. Resolved in Position Control Release 6.1.

NORAPTR The following defects have been resolved in the Electronic Approvals Report (NORAPTR):

• (#80153)This is a technical change that allows the Electronic Approvals Report (NORAPTR) process to compile without any warnings. The change is applicable only to NT environments. Resolved in Position Control Release 6.1.

• (#38422)In some instances, the Approval Type, the Position Number, the Effective Date and the Type Change fields were not being displayed on the Electronic Approvals Report (NORAPTR). This problem has been corrected so that if the information is available, the fields are populated with the correct information. Resolved in Position Control Release 6.1.

• (#51106)Previously when the Electronic Approvals Report (NORAPTR) was run, the transaction from and to date in the parameter had no effect on the records displayed on the report. This problem has been corrected so that only the records within the desired date range will show as well as any null valued records. Resolved in Position Control Release 6.1.

NOQLIBRNOQLPLS

(#62951)The Employee Jobs Form (NBAJOBS) form would not compile when Payroll was not installed. This problem has been corrected by removing the reference to Job Change Reason Code Rules Form (PTRJCRE). Resolved in Position Control Release 6.1.

PDPCFLX (#82366)Previously the Current Benefit Date parameter was not marked as required in job submission and the Flexible Benefits Create Process (PDPCFLX) would abort without the parameter entered. This problem has been corrected. The Current Benefit Date parameter is now a required parameter for the process. Resolved in Human Resources Release 6.1.

PDPF496 (#83604)Technical Fix: Previously, a couple of select routines in the Report of Payroll Activity Process (PDPF496) were rounding the pay rate amounts to 3 decimal places and inserting only 2 decimal places into the pension table PHRPENS. This intermittently caused doubling problems in the PDRF496 table and the resulting report produced by the Report of Payroll Activity Process (PDPF496). The routines have now been corrected to round to 2 decimal places. Resolved in Human Resources Release 6.1.



PDPPERS (#53921)The California PERS Monthly Report of Payroll Contributions (PDPPERS) will now accommodate the reporting of daily pay rates as well as monthly and hourly pay rates as determined by the pay codes set up on the Employee Jobs Form (NBAJOBS) Miscellaneous Information window. Resolved in Human Resources 6.1.

PEREEO4, PEREEO5, PHPCXPN, PXPW2TP, PHPCALC and PHPFEXP

(#88437)This is a technical change that removed an incorrect word that did not allow the processes in question to compile properly on a non-MicroFocus compiler. The following programs were effected: PEREEO4, PEREEO5, PHPCXPN, PXPW2TP, PHPCALC and PHPFEXP. This has been corrected. Resolved in Human Resources Release 6.0.0.1.

PEREO42 (#89598)The format of the EEO-4 Summary Report was corrected to remove leading zeros. Resolved in Human Resources Release 6.0.1.1.

PEREO61 (#79325)On a VMS platform, when the IPEDS Summary Report (PEREO61) was run through a .shl/.com/.pl script from job submission, it would not write the output into Saved Output Review Form (GJIREVO) when DATABASE was entered in the Printer field on the Process Submission Controls Form (GJAPCTL) nor would it go directly to a printer, when specified. This defect has been resolved, and now the report prints correctly. Resolved in Human Resources Release 6.0.2.

PEREO61, -2 The following defects have been resolved in the IPEDS Summary Report (PEREO61, -2):

• (#81498)The IPEDS Summary Report (PEREO61, -2) was matching the Faculty Action Tracking form (PEAFACT) 2-character Rank Code with the 1-character Rank Code on the Rank Code Validation form (PTVRANK). This problem caused incorrect reporting of Rank values when the Institution-created Rank codes did not coincide with the IPEDS Rank codes. This situation has been corrected to match the PEAFACT Rank code to the Institution created Rank code on the Faculty Rank Rule form (PTRRANK), and then match it to the IPEDS Rank Code from PTVRANK. Resolved in Human Resources Release 6.0.2.

• (#81904)The IPEDS Summary Report (PEREO61, -2) is generated by running the PEREO61 process from job submission. The PEREO62 process is included and dependent on running the PEREO61 process. Therefore, the PEREO62 process should not be available to be run via job submission. The PEREO62 process and related job submission data have been removed from the Banner HR product. Resolved in Human Resources Release 6.0.2.



PERLEAV (#87876)Some of the Grand Total fields for displaying the leave hours on the Leave Liability Report (PERLEAV) were not large enough. The Available Balance, YTD Accrued, and Begin Balance fields were increased by 2 characters to match the YTD Taken field size. When the field value exceeded the field size, the original issue caused # signs to be printed in these fields. This problem has been corrected. Resolved in Human Resources Release 6.1.

PERUTAN (#14168)The Percentage of Weighted Factor parameter in the Utilization Analysis Report (PERUTAN), which defaulted to 100%, was missing from job submission. This situation caused erroneous results in the Summary Report. This problem has been corrected and the parameter is available from job submission. Resolved in Human Resources Release 6.1.

PERV100 The following defects have been resolved in the Veterans Employment Report (PERV100):

• (#90681)The New Hires Within Period section of the VETS-100 report process, was not including employees that were terminated within the Start and End dates of the reporting period. The report was correctly counting employees in the Number of Employees section of the report, in that, employees that were terminated before the end date of the report were not included in the counts. With this update, the New Hires Within Period section of the report counts terminated employees as long as the termination (of the Employee record) falls within the reporting dates. Resolved in Human Resources Release 6.0.4.1.

• (#89562)In counting veterans to be reported, the process reported the same employee multiple times if the employee had multiple primary jobs that fell within the reporting period. An example might be that an employee had multiple adjunct contracts, that were designated as primary assignments within the reporting year. This problem has been corrected. Resolved in Human Resources Release 6.0.1.1.

• (#96702)The total number of employees reported in the 'Maximum' amount may be incorrect when running the report for the year (as opposed to running it for a month time frame). This can happen when differing pay ID's pay period start and end dates overlap each other, such as two biweekly payrolls with different Check Issue Dates and only one Check Issue Date falls within the reporting period.

The employee selection was modified so that the maximum count will include employees whose Pay Period Begin Date or Pay Period End Date fall within the report selection period. Resolved in Human Resources Release 6.1.



PHPCALC The following defects have been resolved in the Payroll Calculation Process (PHPCALC):

• (#87730)The Payroll Calculation Process (PHPCALC) was not compiling correctly on some platforms. A technical change was made to compile correctly. Resolved in Human Resources Release 6.0.0.1.

• (#94599)The FLSA "daily" overtime hours was not being calculated with time entry breakdown methods other than daily. This resulted in too many overtime hours being generated for each work period. This has been resolved. The daily overtime hours are now calculated correctly for FLSA, weekly, and pay period time entry breakdowns. Resolved in Human Resources Release 6.1.0.1.

• (#87044)The Payroll Calculation Process (PHPCALC) was not calculating the daily FLSA overtime correctly for employees with multiple jobs. This problem occurred when the total hours worked on a given day exceeded the maximum daily hours allowed as defined on the Work Period Rules Form (PTRWKPR), and the employee had hours entered for two or more days in the pay period. This problem has been fixed and overtime is now calculated correctly. Resolved in Human Resources Release 6.1.

• (#3188)Rounding problems occurred when creating Time Distribution records for FLSA generated earnings.

For example: An employee had a default labor distribution split 50/50 between two FOAPALS. In the current pay event, .75 hours of FLSA OT was generated. The hours calculated for each FOAPAL was .38 hours, for a total of .76 hours. When the user queried this pay event, he/she was trapped in the form since the earn hours did not equal the earnings labor distribution hours. This problem has been corrected and the hours will now be rounded so that they equal. Resolved in Human Resources Release 6.1.

• (#89437)The Payroll Calculation Process (PHPCALC) was not compiling on a non-MicroFocus compiler. This problem has been corrected. Resolved in Human Resources Release 6.0.0.2.

• (#92181)The Payroll Calculation Process (PHPCALC) has been modified to look to the State code rather than the Tax code to determine if the tax amount for the specific state should be rounded or not. The rounding process only applies to certain states, namely, ME, MN, MO, OK, SC, VA, CO, ID, NC, ND, and MT at this point. Resolved in Human Resources Release 6.1.

PHPCHKL (#90199)The Long Check/Direct Deposit Notice (PHPCHKL) was not printing the bank account information for the direct deposit. This printing problem also caused problems for other information on the form. The process has been corrected and now prints properly. Resolved in Human Resources Release 6.0.4.1.



PHPCXPN (#89437)This process was not compiling on a non-MicroFocus compiler. This has been corrected. Resolved in Human Resources Release 6.0.0.1.

PHPDIRD The following defects have been resolved in the Create Direct Deposit Tape Process (PHPDIRD):

• (#93739)The Create Direct Deposit Tape Process (PHPDIRD) was selecting Redistribution transactions when the process was run while the redistributions are being performed and if the disposition of the redistribution was between 42 and 50. This occurred when the PHPDIRD process was run with Type of Records, parameter 4, set to New Adjustment (3). Now, the process has been updated and will not select any Redistribution transaction regardless of the Type of Records that has been chosen. Resolved in Human Resources Release 6.1.0.1.

• (#82156)In the correction to defect 59482 (Release 5.2.1), the GXVBANK date field was truncated so that a timestamp would not be considered in date comparisons between HR and General. This defect applied the same change to the OFFSET_DEBIT_TRANS macro. The GXVBANK date field will no longer be truncated and a time stamp will be considered between HR and General. Resolved in Human Resources Release 6.1.

• (#92137)The Create Direct Deposit Tape Process (PHPDIRD) had been using the Check Date on the Calendar form as the effective date of the direct deposit. A new parameter, Direct Deposit Date has been provided that now allows you to enter a date to be used by the process. Resolved in Human Resources Release 6.0.6.1.

PHPDOCM (#95981)The Reconciliation Indicator was being set incorrectly in PHRDOCM to 'R', when the Adjustment Action was a Reissue of a direct deposit event and the tender was a computer generated check. The process was carrying the indicator forward and not realizing it was a check and no longer a direct deposit; thus, the indicator should not have been set to R or reconciled. This has been corrected. Now, the Calculate Check/Direct Deposit Amounts Process (PHPDOCM) sets the Reconciliation indicator and date to null when the checks are generated for reissues. Resolved in Human Resources Release 6.1.1.1.



PHPFEXP The following defects have been resolved in the Expenditures Finance Extract Process (PHPFEXP):

• (#89337)The Expenditures Finance Extract Process (PHPFEXP) was not using the correct employee class associated with an employee's job when determining the fringe rate from the Fringe Chargeback Rules Form (NTRFBLD). Fringe Chargeback expenses were not being recorded in the correct position on the Salary Budget record NBRPTOT. This would occur when an employee had more than one job with different employee classes, and both jobs incurred Fringe Chargeback expenses during the payroll. This problem has been corrected. Resolved in Human Resources Release 6.0.2.1.

• (#88437)This Expenditures Finance Extract Process (PHPFEXP) was not compiling on a non-MicroFocus compiler. This problem has been corrected. Resolved in Human Resources Release 6.0.0.1.

• ((#11659)When processing payroll adjustments that originated in a prior fiscal year, they would carry the original pay event's fiscal year encumbrance number. This can cause a problem when transactions are fed to Banner Finance and may generate a failed posting due to an invalid encumbrance number in the newly active fiscal year. As salary encumbrances are not normally rolled from year to year, the transaction should not affect current year encumbrances.

This has been corrected by modifying the Expenditures Finance Extract process (PHPFEXP). When payroll adjustments are processed for a prior fiscal year and the associated encumbrance does not exist for the current or future fiscal years, the rule class for transactions that liquidate gross and fringe encumbrances will be overridden with the encumbrance override rule classes identified on the HR/Finance Set Up Rules form (NTRFINI).

You must set up non-liquidating encumbrance rule classes on the Encumbrance Overrides block of the NTRFINI form to utilize this functionality, even if the site is not using the Recasting functionality. If a site is rolling labor encumbrances forward in Banner Finance, the original NTRFINI liquidating rule classes will be utilized since the original encumbrance is still open for liquidation, and the NTRFINI Non-liquidating rule classes will be ignored. Resolved in Human Resources Release 6.1.0.1.

• (#90798)The Expenditures Finance Extract process (PHPFEXP) was not populating the nhrdist_hist_type_ind from the PHRHIST table. The has been corrected by a modification to paragraphs 4600-xxx, 7000-xxx, 8988-xxx to retrieve the phrhist_type_ind and insert it into the NHRDIST table. Resolved in Human Resources Release 6.1.0.1.



• (#96119)The Expenditures Finance Extract process (PHPFEXP) was ignoring the Posting Override Date entered on the Labor Redistribution form (PHAREDS) or the Adjustment Processing form (PHAADJT) if the Payroll Calendar Rules form (PTRCALN) entry for the pay period had a fiscal year override. The Posting Override Date now supersedes all other dates. The process has been modified for the 8915-TRANS-DATE-AND-FISC-CODE and 8925-FIND-NBBFISC-ENTRY to ignore the PTRCALN_FISC_CODE when a posting override date has been entered. Resolved in Human Resources Release 6.1.0.1.

PHPLEAV The following defects have been resolved in the Leave Accrual/Taken Process (PHPLEAV):

• (#87100)Previously, when an institution utilized the Minimum Hours Method within Leave Category Rules, certain conditions would cause an employee to accrue excess leave. In the situation where an employee had a primary job that was processing under a deferred pay rule, and had a second job that was considered extra compensation but with no leave accrual, the process issued erroneous leave accruals during the payout period. Under this condition, the program was ignoring the Accrue Leave indicator from the second job and issuing the leave accrual for the period.

This problem has been corrected so that the second job does not generate an inappropriate accrual of hours. Resolved in Human Resources Release 6.0.1.1.

• (#95847)Previously, earnings were not properly created when exception time reported exceeded the leave balance available. An example of this issue would occur when there were multiple time sheets for an employee in the pay event for the same position (such as a pay raise) and exception time was entered for both time sheets.

In the first time sheet, the leave priority earnings were created properly. However, in the second time sheet, earnings were not created at all. The leave accrual information (PHIACCR/PHRACCR) was being captured correctly for the pay event. This situation has been corrected so that correct earnings, aligned with the appropriate job records, are posted correctly in the payroll. Resolved in Human Resources Release 6.1.0.1.

PHPMTIM The following defects have been resolved:

• (#94254)When the Mass Time Entry Process (PHPMTIM) is run, it looks at the Time Entry Type and if it is the pay period time sheet, it initializes the earnings that defaulted into the On-Line Time Entry Form (PHAHOUR) to zero and proceeds to replace those with the time entered on Electronic Approvals of Time Entry (PHATIME). The problem comes into play when you enter additional earnings on the Mass Time Entry Process (PHPMTIM) and rerun the process. It initializes the earnings on the On-Line Time Entry Form (PHAHOUR) again and then checks the change indicator on the PHRMTIM



table and sees that it has already processed the earns from the PHATIME process and consequently does not process them again. This leaves you with zero hours on the On-Line Time Entry Form (PHAHOUR) for the regular earnings which it must delete so that you're not left with earnings that have zero hours. The PHPMTIM process doesn't seem to work this way when the Time Entry Type on the Employee Jobs Form (NBAJOBS) is set to exception time only. To resolve this problem, touch each earning on the Mass Time Entry Process (PHPMTIM) for the employee for whom you enter additional earnings. Secondly, if earnings became zero by delete operation in PHAMTIM, the zero earnings would not get removed. These problems have been corrected.

Now, once the earnings get initialized and loaded for the pay period time entry employees, these earnings will not be re-initialized even if the Mass Time Entry Process (PHPMTIM) is run multiple times. Also, zero earnings are removed for non-payroll time entry employees regardless of the existence of PHRMTIM records. Resolved in Human Resources Release 7.0.

• (#87164)Previously, when FOAPAL information was not entered in the PHRMTIM table and the PTRPCLD or NBRJLBD tables contained an Index, the process would not correctly retrieve the account index. This problem has been fixed and the labor distribution is now retrieved correctly. Resolved in Human Resources Release 6.1.

• (#87051)The Mass Time Entry Process (PHPMTIM) had not been inserting the hours properly if an employee had FLSA as the Time Breakdown Method. The process has been updated and hours are now inserted correctly. Resolved in Human Resources Release 6.1.

• (#90196)The Mass Time Entry Process (PHPMTIM) would not report Oracle errors that occurred when loading information from the Web Time Entry tables into the mass Time Entry Table, PHRMTIM, but erroneously updated the status of the time transaction on the Web as Completed. Consequently no information was being loaded into PHRMTIM or pay history. This problem has been corrected. An errors is now reported without changing the status. Resolved in Human Resources Release 6.0.4.1.

• (#96939)This defect was created due to performance issues with the Mass Time Entry Process (PHPMTIM). The change was to wrap a TO_CHAR function around all occurrences of USERENV('SESSIONID') preventing a full table scan on the POTPARM table. Resolved in Human Resources Release 6.1.0.1.



PHPPROF The following defects have been resolved in the Pay Period Proof Process (PHPPROF):

• (#94159)The changes to Pay Period Proof Process (PHPPROF) previously posted for defect #92481 reduces performance in certain cases when running the process using the option to delete all time sheets that are at disposition 10. The performance improved by removing orphaned records individually using rowid instead of mass deletes. Modified routines have been applied for both Delete(A)ll Disp 10 TS and (D)elete Disp 10 TS if 20. Resolved in Human Resources Release 6.1.0.1.

• (#91978)Technical changes were made to the Pay Period Proof Process (PHPPROF) to enhance its performance. Resolved in Human Resources Release 6.0.5.1.

• (#92481)Some clients were experiencing problems with the Payroll Calculation Process (PHPCALC) generating zero checks for employees. The problem would occur when earning records (PHREARN) were orphaned from their corresponding job record (PHRJOBS) during the payroll process. Although this problem could not be recreated, it is suspected that the situation was the result of dispositions getting reset to 10 on the job record in error. This may be the result of custom modifications that reset dispositions, or some other internal Banner issue yet to be isolated. If a site runs the Pay Period Proof Process (PHPPROF) using the option to delete all time sheets at disposition 10, the job record (PHRJOBS) is deleted, while the earnings records (PHREARN) are not. To avoid problems with the Payroll Calculation Process (PHPCALC), a patch was created for the Pay Period Proof Process (PHPPROF) to delete earnings records (PHREARN) when the process is run using the Delete All Timesheets at 10 option. Now, orphaned earnings records get deleted when delete all 10 disposition time sheets are removed so that the Payroll Calculation Process (PHPCALC) performs its calculation properly. Resolved in Human Resources Release 6.0.6.1.

PHPTAXS The following defects have been resolved:

• (#95336)Delaware tax calculation was not rounding the withholding amount to the nearest whole dollar. The tax tables had to be updated to reflect the most current rates as stated by the DE Revenue web site. This has been corrected. Resolved in Human Resources Release 6.1.0.1.

• (#91936)Montana state tax withholding was not being rounded to the nearest dollar. This problem has been corrected. Resolved in Human Resources Release 6.0.5.2.

• (#91263)North Dakota state tax withholding was not being rounded to the nearest dollar. This problem has been corrected. Resolved in Human Resources Release 6.0.5.1.



• (#92181)The PHPTAXS routine has been updated to accommodate state tax rounding for state non-resident alien deductions. Now the NRA deductions are rounded appropriately and reported correctly. This applies to those states that require the state tax to be rounded to the nearest dollar including Maine, Minnesota, Missouri, Oklahoma, South Carolina, Virginia, Colorado, Idaho, North Carolina, North Dakota and Montana.

PHPTIME The following defects have been resolved in the Time Processing Report (PHPTIME):

• (#96221)Two problems have been addressed by this defect resolution. First, if an employee had a job termination detail record within the pay period and the job was then reactivated after the termination date but there was a break in time associated with the termination record and the activation record, the employee would have been paid for the full pay period. The process has been fixed and will prorate the hours or display the correct dates.

The second issue was that a holiday on the first day of the new fiscal year would not default. This issue has been fixed and the holiday will now default to the pay records. Resolved in Human Resources Release 6.1.0.2.

• (#86371)When a deduction is Terminated on the last day of the pay period, the process was not using the plan or amount information for the Terminated record. Rather, the payroll process picked up information from the previous, non-terminated deduction to process. This is incorrect, when changes are made to plans or amounts on the final day of the pay cycle. This has been corrected.

Now, effective dated changes made to a deduction record with a status of Active as of the last day of the pay period will be processed for the current pay event.

Deductions that have a terminated status within the current pay event dates and are reactivated beyond the payroll end date, will not be processed for the current payroll.

The Adjustment Processing Form (PHAADJT) has also been modified so that extraction and net-to-gross logic for deductions on manual checks is consistent with the above changes for the Time Processing Report (PHPTIME). These changes also resolve an existing defect (#89238) for this form (Deductions are not processed correctly for manual checks that are computer calculated when the deductions involved are terminated on the end date of the event being processed.) Resolved in Human Resources Release 6.1.0.1.

• (#88145)The process had not been prorating deemed hours for an employee correctly when there was a split time sheet (i.e., two time transactions for the same job assignment.) This problem has been fixed and deemed hours will be prorated properly. Resolved in Human Resources Release 6.0.1.1.



• (#52443)If an employee record was terminated in a pay period in which Holiday pay was to be received (meaning the holiday was entered on the Employee Holidays Rules Form (PTREHOL)), the employee was not receiving the holiday pay when the Time Processing Report (PHPTIME) was run, even if the termination date was after the holiday. This problem has been corrected. Now the Employee Holidays Rules Form (PTREHOL) holidays are paid on the appropriate time sheet, even for employees terminating on or after the holiday. Resolved in Human Resources Release 6.1.

• (#88587)Previously, the Time Processing Report (PHPTIME) was not splitting the payroll correctly for people who have job changes on the last day of a fiscal year or on the first day of a new fiscal year. This problem has been corrected so that the time sheets reflect the correct fiscal year dates. Resolved in Human Resources Release 6.1.

PHPUPDT The following defects have been resolved in the Pay Period Update Process (PHPUPDT):

• (#94036)When the system is set to process Leave by Job and you executed the period in which the leave period rolls, the Pay Period Update Process (PHPUPDT) process experienced slow performance. A section of this program was restructured to allow the process to run faster. There were no other functional changes other than the leave roll performance tuning. Resolved in Human Resources Release 6.1.0.1.

• (#90015)The Pay Period Update Process (PHPUPDT) was not updating the job totals table by employer code in addition to PIDM, Position, and Earn code. This only happened when the employer code changed on the Employee Jobs form (NBAJOBS) effective after the first pay of the month. This problem caused the old employer job total record to be updated with job information for the new employer code. This problem has been corrected, and the employer earnings can be verified appropriately on the Job Year To Date Totals Form (PEIJTOT). Resolved in Human Resources Release 6.0.5.1.

• (#93296)Performance issues were reported during the Pay Period Update Process (PHPUPDT). Some routines were restructured to execute more efficiently. Resolved in Human Resources Release 6.0.6.1.

PHVTIME (#93141)Technical Fix: Performance issues were reported when querying Web Time Entry data. A technical fix was applied to improve data retrieval performance. Resolved in Human Resources Release 6.0.6.1.



PHRLRAR (#89586)In the Labor Redistribution Audit Report (PHRLRAR), data and some field headings were not displaying correctly after upgrading to Oracle 9.2.0.1. This problem has been corrected so that the headings display properly and data is retrieved for display. Resolved in Human Resources Release 6.1.

PORAUDT The following defects have been resolved in the Audit Trail Report (PORAUDT):

• (#81297)Previously, when an employee had a one time add/replace on their deduction record, the Audit Trail Report (PORAUDT) would not correctly report the employer share of the add/replace. This problem has been corrected and the employee and employer amounts will be displayed on the Audit Trail Report (PORAUDT) in the correct columns. Resolved in Human Resources Release 6.1.

• (#58237)The Audit Trail Report (PORAUDT) was not executing through Job Submission. This problem has been corrected. Resolved in Human Resources Release 6.1.

PXPMT42 (#93150)The 1042 Magnetic Tape Process (PXPMT42) has been modified to convert all alpha characters to uppercase for all records and to make zip codes left justified and blank filled where necessary. As a note, in order to avoid hyphens in telephone numbers for the 1042-S process, the telephone number field on the Employer Rules Form (PTREMPR) and the Magnetic Tape Rules Form (PXAMTAP) should be entered without the hyphens. This will fulfill the regulatory requirement for the 'W' and 'T' records in the magnetic tape to not include hyphens. Resolved in Human Resources Release 6.0.6.1.

PXR1042 and PXRW2PR

(#87798)The Foreign Person 1042S Form (PXR1042) and the Form W2 Wage and Tax Statement for Puerto Rico (PXRW2PR) .err files could not be viewed on the Saved Output Review Form (GJIREVO) when run from Job Submission. Three new scripts .shl, .pl and .com have been created for these processes and the output for the .log, .lis and .err files may be viewed on the Saved Output Review Form (GJIREVO). Resolved in Human Resources Release 6.1.

PXR1042 (#90019)Box 7 - Federal Tax Withheld on the 1042-S Foreign Person's U.S. Source Income Subject to Withholding form was not printing a zero when no tax had been withheld. This problem has been corrected and a zero is now printed. Resolved in Human Resources Release 6.0.5.

PXRT4CN (#91347)Code 71 - Status Indian Employee was not being reported. This has been corrected. Resolved in Human Resources Release 6.0.5.1.



PXRW2US (#83835)For WinNT/2000 platforms only - A technical change was made to the process so that the process would not abort when choosing NOPRINT as the print option. Resolved in Human Resources Release 6.0.5.

PXPW2TP (#89437)This process was not compiling on a non-MicroFocus compiler. This problem has been corrected. Resolved in Human Resources Release 6.0.0.1.

PEKTEC1 The following defects have been resolved:

• (#88328)In the processing of Leave Reports, the enterprise has the option of establishing an alternate approval category for the building the approval routing queue for a leave report. The PEKTEC1 package was using the Time Entry Approval Category, rather than the Leave Report Approval Category when a Leave Report was being extracted. This was causing the extract to build an incorrect routing queue for the processing of the leave report. This problem has been corrected. The package now uses the correct approval category when the Leave Report extract is processed. Resolved in Human Resources Release 6.0.1.1.

• (#88642)When clients defined routing queues for time entry on the Position Definition Form (NBAPOSN) in the Reports To field, the extract process was not correctly establishing the approval queue. The employee on the Web or the administrative user on the Electronic Approvals of Time Entry Form (PHATIME) received an error message to contact Human Resources when they tried to extract a time sheet, stating that no routing queue had been established. The extract process has been corrected and routing queues will be correctly established when the set up is on the Position Definition Form (NBAPOSN). Resolved in Human Resources Release 6.0.0.1.

PEKTEC1 (#93141)Technical Fix: Performance issues were reported when querying Web Time Entry data. A technical fix was applied to improve data retrieval performance. Resolved in Human Resources Release 6.0.6.1.

PEKTEV1 The following defects have been resolved in this package:

• (#89686)The proxies for the originator of a time transaction could not update, restart, or submit time. This problem has been corrected. Now any proxy for the originator can perform all of the above actions. Resolved in Human Resources Release 6.0.1.1.

• (#89061)A Department user (as the originator) could not update the timesheet that was returned for correction. This problem has been corrected. Resolved in Human Resources Release 6.0.0.1.

Section 24 Problem Resolutions- TechnicalChanged Scripts


Section 24 Problem Resolutions- Technical

This section documents the technical changes made in Banner for problem resolutions in Human Resources Releases 6.1 and 7.0 as well as Position Control Releases 6.1 and 7.0.

Changed Scripts

PDKDED1.SQL

This script has been modified to resolve defect #89197.

PDTBCOV1.SQL


PEKLEA1.SQL

This script has been modified to correct defect #91978.

PEKTEA1.SQL

This script has been modified for defect #89061.

PEKTEC1.SQL

This script has been modified to resolve defects #88328, #88642, #93141, and #93468.

PEKTECM.SQL


PEKTEE1.SQL


Section 24 Problem Resolutions- Technical Changed Scripts


PEKTEV1.SQL

This script has been modified to resolve defects #89061, #89686, and #93262.

PEREHIS0.SQL and PEREHIS1.SQL

The script adds new columns to the PEREHIS table and PEREHIS1.SQL adds comments to each new column in Release 7.0.

PERREVW1.SQL

This script creates an index on the PERREVW table.

PEVJLEV.SQL


PEVPCSN.SQL

This script has been modified to resolve defects #96939 and #97561.

PHRREDS0.SQL and PHRREDS1.SQL

PHRREDS0.SQL adds a new column PHRREDS_POSTING_OVERRIDE_DATE to the PHRREDS table.

PHRREDS1.SQL adds a comment to the new column.

PHVTIME.SQL

This script has been modified to resolve defects #93141 and #93468.

POKLIB1.SQL


POKPAR1.SQL


Section 24 Problem Resolutions- TechnicalChanged Tables


POKREC1.SQL

The following new functions have been added to this package: f_ptrpict_rec, f_ptrbcat_rec, f_ptrecbc_rec, f_ptrjbln_rec, f_ptrlrea_rec, f_ptrtrea_rec, f_ptrwkpr_rec.

Changed Tables

Employee History Repeating Table (PEREHIS)

The following columns have been added to the PEREHIS table.


PEREHIS_COAS_CODE_HOME VARCHAR2(1)

PEREHIS_COAS_CODE_DIST VARCHAR2(1)

PEREHIS_ORGN_CODE_DIST VARCHAR2(6)

PEREHIS_FIRST_HIRE_DATE DATE

PEREHIS_SENIORITY_DATE DATE

PEREHIS_I9_FORM_IND VARCHAR2(1)

PEREHIS_I9_DATE DATE

PEREHIS_I9_EXPIRE_DATE DATE

PEREHIS_WKPR_CODE VARCHAR2(4)

PEREHIS_FLSA_IND VARCHAR2(1)

PEREHIS_STGR_CODE VARCHAR2(2)

PEREHIS_DAYS_IN_CANADA NUMBER(3)

PEREHIS_1042_RECIPIENT_CD VARCHAR2(2)

PEREHIS_INTERNAL_FT_PT_IND VARCHAR2(1)

PEREHIS_DICD_CODE VARCHAR2(3)

PEREHIS_EGRP_CODE VARCHAR2(4)

PEREHIS_IPEDS_SOFT_MONEY_IND VARCHAR2(1)

PEREHIS_FIRST_WORK_DATE DATE

Section 24 Problem Resolutions- Technical Changed Libraries


Payroll Labor Redistribution Work Table (PHRREDS)

The following column has been added to the PHRREDS table:

Changed Libraries

The following libraries have been changed for Release 6.1.

NOQRPLS.PLL

• (#62951)This library was modified to fix defect # 62951. A new procedure, POPULATE_JOBS_EFF_DATE_RG, was added to the library.

• (#77736)This library was modified to correct defect #77736. For more details, refer to “Problem Resolutions” on page 291.

PEREHIS_LAST_WORK_DATE DATE

PEREHIS_CALIF_PENSION_IND VARCHAR2(1)

PEREHIS_NRSI_CODE VARCHAR2(4)

PEREHIS_SSN_LAST_NAME VARCHAR2(20)

PEREHIS_SSN_FIRST_NAME VARCHAR2(15)

PEREHIS_SSN_MI VARCHAR2(15)

PEREHIS_SSN_SUFFIX VARCHAR2(4)

PEREHIS_JBLN_CODE VARCHAR2(6)

PEREHIS_COLL_CODE VARCHAR2(2)

PEREHIS_CAMP_CODE VARCHAR2(3)

PEREHIS_DATA_ORIGIN VARCHAR2(30)


PHRREDS_POSTING_OVERRIDE_DATE DATE


Section 24 Problem Resolutions- TechnicalObsolete Objects in Human Resources Release 7.0


NOQLPLS.PLL

(#62951)This library was modified for the CA-MIS enhancements in HR Release 6.0.4, and for Defect #62951. For more details regarding the defect resolution, refer to the “Problem Resolutions” on page 291.

Obsolete Objects in Human Resources Release 7.0

The following objects are obsolete with Human Resources Release 7.0.

PORPPFL.PC, PORPOFL.PC and PORPPFL.H

(#87515)No code change for this defect. Please use the LDIS-P extract, Process Name: ICGORLDI.PC, release numbers: Intcomp 5.3 and 6.1, which were delivered on March 29, 2004. The extract process works for both Luminis and WebCT integration. The XML is sent out in accordance with the LDIS protocol.

The three objects porppfl.h, porppfl.pc and porpofl.pc are obsolete with Release 7.0.

PEREEO1.PCO, PEREEO6.PCO, PXPMTW2.PCO and PXPMTPR.PCO

The following cobol programs are obsolete with Human Resources Release 7.0:

• pereeo1.pco

• pereeo6.pco,

• pxpmtw2.pco, and

• pxpmtpr.pco

PXPDSW2.PC

This C program is obsolete with Human Resources Release 7.0.

Section 24 Problem Resolutions- Technical Obsolete Objects in Human Resources Release 7.0



Appendix A Example of Annual Salary Calculation for CA-MIS




Consider the example of employee Sally Jones who has earn codes set up for Premium earnings, Additional earnings, shift differential and longevity with the following NBAJOBS information:

Original Hire Date 1/1/2000

Current Hire Date 1/1/2000

Adjusted Service Date 1/1/2000

Seniority Date 1/1/2000

Employee’s pay rate $20.00

Employee’s hours per pay 160

Employee’s pays per year 12

Employee’s base annual salary $38,400.00

Employee’s default earnings

*Transition payment

Today’s Date is 10/1/2003

Years of Service: 3 years 9 months

Earn Code Shift Hours Rate (if different from regular rate)

REG 1 80REG 2 80MIL 1 10 0.50NRP 1 20TTP* 1 10

Applicable Longevity Rule:

3 years 0 months to 5 years 0 months - 10% longevity



Longevity Earnings

The Annual Longevity Amount is calculated as follows:

In the above example,

Shift Differential Earnings

The annual shift differential amount is calculated as follows:

In the above example,

Applicable Shift Differential Rule:

Additional $.25/hour for shift 2

Applicable Premium Pay: Apply 1.00 per hour for REG 1 and REG 2 hours (asbestos removal)

Additional Earningsto be included:

Mileage rate (MIL), Non-resident payment (NRP)

Longevity per Hour

Annual Longevity Amount

=

=

[(Reg rate x % longevity) + flat amount longevity]

Longevity per hour x hours per pay x pay factor

Longevity per hour

Annual Longevity Amount

=

=

=

[(20.00 x 10)+ 0]

$2.00 x 160 x 12

$3840.00

Shift Amount per Hour

Annual Shift Amount

=

=

[(Reg rate x % shift) + flat amount shift]

Shift amount per hour x hours per pay x pay factor

Shift amount per hour

Annual Shift Amount

=

=

=

[(20.00 x 0)+ 0.25]

$0.25 x 80 x 12

$240.00



Premium Pay Earnings

The annual earnings from premium pay is calculated as follows:

In the above example, applicable premium earnings are REG1 and REG2 which are calculated as follows:

REG1

REG2

Total Annual Premium Earnings = ($960 + $960) = $1920.00

Annual Additional Earnings

The annual additional earnings for calculated as follows:

Annual additional earning amount = Default Rate x Hours per Pay x Pay Factor

In the above example, applicable earnings are MIL and NRP

MIL = .50 x 10 = 5 x 12 = $60

NRP = 20 x 20 = 400 x 12 = $4800

Therefore, Total annual additional earnings = $4860

Premium Amount per Hour

Annual Premium Amount

=

=

[(Reg rate x % premium) + flat amount prem.]

Shift premium per hour x hours per pay x pay factor



=

=

=

[(20.00 x 0)+ 1]

$1.00 x 80 x 12

$960.00



=

=

=

[(20.00 x 0)+ 1]

$1.00 x 80 x 12

$960.00



Annual Salary

The final annual salary determined from the above information and reported on PEPEDEX is calculated as:

Base annual salary = $ 38,400.00

Longevity + = $ 3840.00

Shift Differential + = $ 240.00

Premium Earnings + = $ 1920.00

Additional Earnings + = $ 4860.00

Total Annual Salary = $49260.00

Appendix B Example - Setting Up VBS in Human ResourcesOverview


Appendix B Example - Setting Up VBS in Human Resources

Overview

The following example illustrates how to set up Value Based Security (VBS) using Oracle Fine-Grained Access (FGAC) for a simplistic business case within Banner Human Resources. This type of security is primarily to define row level access to records in the database and is used in conjunction with the Banner HR application security.

This example is to provide details of securing employee job records based upon Position Class, which resides on the Position record. This example is intended to define classifications such as Administrative users and Faculty users, so that VBS will restrict insert, update, and delete privileges on jobs data for specific user populations. As a component of defining FGAC rules, the user defines the tables which 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, job detail, labor distributions, default earnings, and work schedules.

Step 1 - Define a Domain and Plan the Rules

VBS rules require that a domain be defined, which provides the primary driver table to allow Oracle to begin the data analysis. In this case, we are identifying the Position table (NBBPOSN), so that we can determine where to find the Position Class Code 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 table within the application. For example, we're using a user-defined domain name, for which we have chosen pb_position_class_vbs, and the Position table (NBBPOSN) will be the driver to determine the specific Position Class.

We will also define the tables in which the VBS restriction will execute, besides the domain driver table NBBPOSN. This will ensure that the user that is attempting to insert, 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 in the process, on the FGAC VBS Table Rules Form (GORFDPL).

Domain Driver

PB_POSITION_CLASS_VBS NBBPOSN

Table Class

NBBPOSN

Appendix B Example - Setting Up VBS in Human Resources Overview


Note: When defining the Join command on the FGAC VBS Table Rules Form (GORFDPL), the trailing parenthesis should be left out. It is handled by the FGAC package.

To further define the implementation of this scenario, we are documenting a set of Business Cases and are indicating how they will be enforced, on a user-by-user basis. The following chart helps to further define the premise for our example, as described above. The population, or user, for each business case is restricted to records associated with the Position, where the Position Class Code begins with the value listed in the SQL Predicate. SQL predicates are used to determine which conditions should be tested as each row of data is presented to the user. These are defined later on the FGAC Group Rules Form (GOAFGAC).

Establish the Domain as a Valid Value

Enter user-designed domain code on the FGAC Domain Validation Form (GTVFDMN) and provide a business-oriented description.

NBRBJOB EXISTS ( SELECT 'X' FROM NBBPOSN WHERE NBBPOSN_POSN = NBRBJOB_POSN

NBRJOBS EXISTS ( SELECT 'X' FROM NBBPOSN WHERE NBBPOSN_POSN = NBRJOBS_POSN

NBRJLBD EXISTS ( SELECT 'X' FROM NBBPOSN WHERE NBBPOSN_POSN = NBRJLBD_POSN

NBREARN EXISTS ( SELECT 'X' FROM NBBPOSN WHERE NBBPOSN_POSN = NBREARN_POSN

NBBWKSH EXISTS ( SELECT 'X' FROM NBBPOSN WHERE NBBPOSN_POSN = NBBWKSH_POSN

NBRWKSH EXISTS ( SELECT 'X' FROM NBBPOSN WHERE NBBPOSN_POSN = NBRWKSH_POSN

Business Case SQL Predicate

Administrative User Group may only insert, update, and delete job data belonging to administrative-type Position Class Codes. Jobs data includes basic job, job detail, labor distributions, default earnings, and work schedules.

(NBBPOSN_PCLS_CODE LIKE 'A%' , NBBPOSN_PCLS_CODE LIKE 'B%' , NBBPOSN_PCLS_CODE LIKE 'C%' , NBBPOSN_PCLS_CODE LIKE 'K%' , NBBPOSN_PCLS_CODE LIKE 'L%' , NBBPOSN_PCLS_CODE LIKE 'M%' , NBBPOSN_PCLS_CODE LIKE 'N%' , NBBPOSN_PCLS_CODE LIKE 'P%' , NBBPOSN_PCLS_CODE LIKE 'S%' , NBBPOSN_PCLS_CODE LIKE 'U%')

Faculty User Group may only insert, update, and delete job data belonging to faculty-type Position Class Codes. Jobs data includes basic job, job detail, labor distributions, default earnings, and work schedules.

NBBPOSN_PCLS_CODE LIKE 'F%'

Table Class





Step 2 - Enter Domain Driver on the FGAC Domain Driver Rules Form (GORFDMN)

Now that the Domain Code has been established as a valid value for our HR example, the primary Driver Table, NBBPOSN, must be established. This will identify where the Position Class Code can be found to further evaluate data for the VBS rules.

Step 3 - Enter All Domain Tables on the FGAC VBS Table Rules Form (GORFDPL)

This rule form ties the Domain driver to the tables where row-level security will be enforced. The driver table is established first, followed by the tables affiliated with the employee job tables.

• The Driver table is NBBPOSN. Restrictions are going to be based on values in this table.

• The rule is to be enforced for the following tables: NBRBJOB, NBRJOBS, NBRJLBD, NBREARN, NBBWKSH, and NBRWKSH. The join conditions are entered in the Driver SQL for these tables. These conditions join back to NBBPOSN.



• The user can select 'Validate SQL' to ensure that the Driver SQL that entered is valid.

Note: The trailing right paranthesis, ')' is omitted on the SQL statement because it is handled in the FGAC package.

• The active indicator needs to be on for the VBS rules to take effect,



Similarly, set up the NBREARN, NBRJLBD, and NBRJOBS tables on the FGAC VBS Table Rules Form (GORFDPL).



Also set up the NBRWKSH table on the FGAC VBS Table Rules Form (GORFDPL).



Step 4 - Set up the FGAC Business Profile Validation Codes (GTVFBPR)

Next, establish the Business Profile Codes for the business cases, or user groupings, as noted in the Business Case chart, above. This will initiate the code that is used to link specific Oracle User ID's to a specific Business Profile. In this example we'll use HR_STAFF_ADMIN, to associate 'Administrative' type users, and HR_ACADEMIC_ADMIN, to associate users to the 'Faculty' type jobs.



Step 5 - Associate Oracle User ID's to the Appropriate Business Profiles

Using the Business Profiles established in the last step, affiliate the User ID's to the FGAC Business Profile Assignments on the FGAC Business Profile Assignments Form (GOAFBPR). The first profile is to set up users that should have row-level security for employee jobs that are associated with staff-type Position Classes.

As the Business Profile Code is changed to associate Faculty, or Academic employee jobs with a set of users, several Oracle User ID's have been entered that should have row-level security for employee jobs that are associated with faculty-type Position Classes.





Step 6 - Add the VBS Group Validation Codes on GTVFGAC for the Business Cases.

This validation table establishes group codes that will ultimately allow the security logic to be affiliated with Administrative and Faculty users.



Step 7 - Establish the VBS Group Rule - GOAFGAC

This rule form connects the FGAC Group with the logic associated with processing the data for the user. First, we are setting up rules for the HR_ADMINISTRATIVE Group Code using the SQL Predicate that we have planned in our Business Cases. The Predicate information will test the Position Class Code, where the first character of the code indicates that these Positions are affiliated with staff employees.



On the same rule form, we then assign the VBS Group Rule to Business Profile and, in turn to the User ID's.

HR_STAFF_ADMIN users (Business Profile) within the HR_ADMINISTRATIVE group can insert, update, and delete jobs data only for jobs that have Non-Academic Staff Position Classifications.



We now establish the second set of Group Rules Set up rules for the HR_FACULTY_ADMIN group code. In this case, the predicate indicates that it will allow access to Position Class Codes that begin with the character 'F', which designates faculty positions.



Further define the rules for the HR_ACADEMIC_ADMIN users (Business Profile) within the HR_FACULTY_ADMIN group and indicate that they can insert, update, and delete jobs data only for jobs that have Faculty (Academic) Position Classifications.

Summary Results of User Rules:

User MFISHER has been restricted to inserting, updating, and deleting only job data that belong to Faculty Position Classifications (those position class codes starting with 'F').

User CSTACK has been restricted to inserting, updating, and deleting only job data that belong to a Non-Academic Position Classifications (those position class codes starting with 'A', 'B', 'C', 'K', 'L', 'M', 'N', 'P', 'S', 'U').

All other users are not restricted and can select, insert, update, and delete any job data.



Step 8 - Run the Delivered Policy Scripts

In order to create the Oracle policies for the appropriate tables, a script must be run against the database. This is a technical step and must be performed by the DBA for the site.

The following example describes this step.

• Connect as Baninst1 and run gfvbsaddpol.sql once for each of the seven tables that are defined in the PB_POSITION_CLASS_VBS domain (NBBPOSN, NBRBJOB, NBRJOBS, NBRJLBD, NBREARN, NBBWKSH, and NBRWKSH) to create the policies.

SQL> @gfvbsaddpol

The Table you wish to create policies for (partial name acceptable):nbbposnTable Policies for:NBBPOSN%Table selected from GORFDPL NBBPOSN

PL/SQL procedure successfully completed.

Elapsed: 00:00:00.32

NBBPOSN GOKFGAC_NBBPOSN_DELNBBPOSN GOKFGAC_NBBPOSN_INSNBBPOSN GOKFGAC_NBBPOSN_SELNBBPOSN GOKFGAC_NBBPOSN_UPD

Elapsed: 00:00:00.03SQL> select * from dba_policies where object_name = 'NBBPOSN';

POSNCTL NBBPOSNSYS_DEFAULT GOKFGAC_NBBPOSN_DELBANINST1 GOKFGACF_DELETE_FNC NO NO NO YES YES YES NO

POSNCTL NBBPOSNSYS_DEFAULT GOKFGAC_NBBPOSN_INSBANINST1 GOKFGACF_INSERT_FNC NO YES NO NO YES YES NO

POSNCTL NBBPOSNSYS_DEFAULT GOKFGAC_NBBPOSN_SELBANINST1 GOKFGAC

F_SELECT_FNC YES NO NO NO YES YES NO

POSNCTL NBBPOSNSYS_DEFAULT GOKFGAC_NBBPOSN_UPDBANINST1 GOKFGACF_UPDATE_FNC NO NO YES NO YES YES NO

Run gfvbsaddpol.sql for the remaining tables in the domain.



FGAC Predicate Inquiry - GOIFGAC

You can view what restrictions are in effect for each User ID and table on the FGAC Predicate Inquiry, GOIFGAC to test the access controls on a user-by-user basis. This query allows the user to have a direct tool to test the policies that have been established and to help diagnose access problems. It is executed against the specified table for a User ID.

Table: NBRJOBS

Results of the VBS Group Rule example that has been created and the policies that have been added to the tables: NBBPOSN and NBRBJOB

Example 1

Logging in as MFISHER (restricted to Faculty Position Classifications insert, update, and delete), MFISHER tries to insert a job that belongs to a non-academic position class. Position U60002 is defined as Position Class UFC01 - Clerical. This violates the policy because MFISHER should input only Position Classes that begin with the character 'F' (Faculty).



Select the OK button to receive the security violation message in the status bar.



Other Notes and Tips

Please refer to the Banner General Release Guide of Release 7.0 for additional, detailed information on the rules associated with Value Based Security. There are many considerations associated with using Value Based Security and could have unexpected results when establishing policies on the data. In addition, there can be cross-system implications with Banner Finance VBS policies in conflict with Banner HR policies and normal application level security.

For example, if a Finance VBS policy is established to restrict access to an Account, errors could be generated on forms such as the On-Line Time Entry Form (PHAHOUR), the Employee Jobs Form (NBAJOBS), the Position Budget Form (NBAPBUD), or any form that is attempting to balance FOAPAL distributions.

Thoroughly evaluate all policies in a test environment against any form or process that utilizes the data that is described in the policy restrictions, as they can have far-reaching implications.



Any Banner process or form can be excluded from VBS to avoid processing difficulties. As delivered with Banner 7.0, all current processes have been excluded from VBS. This will ensure that policies that are activated will not interfere with payroll, finance, and general reporting processes. It is also recommended that any custom form, report or process be evaluated for addition to the exclusions, to ensure that they continue to function properly.

Appendix C Using the Common Person API in Human ResourcesIntroduction


Appendix C Using the Common Person API in Human Resources

Introduction

With Banner 7.0, there are two sets of API's that are provided with the Human Resources application set. They are the Common Person API and the Employee API. This section will generally define the functionality and special notes associated with those processes. Further technical descriptions of API processing can be found in the API Reference Guide.

Common Person API

The processing of biographic and demographic data, associated with a person or employee record, has been revised so that it is consistent with other Banner applications and so that common processing can be executed. The API is executed whenever you select, insert, update, or delete data.

The focal point of this information resides on the Identification Form (PPAIDEN). All data blocks on this form execute the common business logic. These include:

• Current Identification

• Alternate Identification

• Address

• Biographical


Two other forms that allow the creation of a PIDM, within the Human Resources application include the New Hire Form (PEAHIRE) and the One-Time Payment Form (PEA1PAY). Both of these forms process core person data and therefore, have had the API logic applied.

Appendix C Using the Common Person API in Human Resources Common Person API


Additional forms in which the Common Person API is executed include:

• Address List Inquiry Form (PPIADDR)

• Telephone Form (PPATELE)

• International Information Form (GOAINTL)

• E-mail Address Form (GOAEMAL)

• General Medical Form (GOAMEDI)

All forms will process person data as in previous releases, with the exceptions noted below;

• As common tabs were added to all Identification pages, the Alternate Identification tab will follow the Current Identification tab, when executing the Next Block function;

• The Identification Form (PPAIDEN) will no longer edit for a missing address when a person record is created, which is consistent with all other Identification pages in Banner. However, you will receive an Error condition that an address is missing when the Employee Form (PEAEMPL) is accessed for entry.

• When Common Matching is enabled, the matching form will allow an address to be missing or incomplete, unless the matching rules specify otherwise. Ensure that a complete address is provided when creating an employee to ensure accuracy on checks and year end documents.

• Within the Common API logic, a Deceased Date is no longer required, when specifying that the person is deceased. Logic for deceased notification is activated when the Deceased Indicator is checked.

• When creating or updating a non-person record within the Identification Form (PPAIDEN), you can no longer supply an Emergency Contact record. This is consistent with the business logic associated with other Identification forms.

Documents

SCT Banner Human Resources/Position Control Release · PDF fileSCT Banner Human Resources/Position Control ... Browsing for Topics ... January 2005 Human Resources/Position Control