Banner Financial Aid / User Guide / 8.3

Banner Financial Aid / User Guide / 8.3
Banner Financial Aid
User Guide
Release 8.3
January 2009
What can we help you achieve?
SunGard Higher Education
4 Country View Road
Malvern, Pennsylvania 19355
United States of America
(800) 522 - 4827
Customer Support Center Website
http://connect.sungardhe.com
Documentation Feedback
http://education.sungardhe.com/survey/documentation.html
Distribution Services E-mail Address
[email protected]
Other Services
In preparing and providing this publication, SunGard Higher Education is not rendering legal, accounting, or other similar professional
services. SunGard Higher Education 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.
Trademark
Without limitation, SunGard, the SunGard logo, Banner, Campus Pipeline, Luminis, PowerCAMPUS, Matrix, and Plus are trademarks
or registered trademarks of SunGard Data Systems Inc. or its subsidiaries in the U.S. and other countries. Third-party names and marks
referenced herein are trademarks or registered trademarks of their respective owners.
Revision History Log
Publication Date
January 2009
Summary
New version that supports Banner Financial Aid 8.3 software.
Notice of Rights
Copyright © SunGard Higher Education 1991-2009. This document is proprietary and confidential information of SunGard Higher
Education Inc. and is not to be copied, reproduced, lent, displayed or distributed, nor used for any purpose other than that for which
it is specifically provided without the express written permission of SunGard Higher Education Inc.
Banner Financial Aid 8.3
User Guide
Contents
Chapter 1
System Overview
Application Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1
Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Module Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Financial Aid System Process Flow . . . . . . . . . . . . . . . . . . . . . . . 1-4
Chapter 2
Processing
Data Load Procedures. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Understanding Data Load. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
EDE ISIR Data Load Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . 2-2
CSS PROFILE Data Load Process Flow . . . . . . . . . . . . . . . . . . . . . . 2-4
Setting Up Rule and Validation forms for Data Load . . . . . . . . . . . . . . . . 2-5
Preparing the Data to Load into Banner . . . . . . . . . . . . . . . . . . . . . . 2-11
Default File Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11
File Concatenation Process (FILECAT) . . . . . . . . . . . . . . . . . . . . . . 2-11
Running the Data Load Process . . . . . . . . . . . . . . . . . . . . . . . . . . 2-13
Additional Data Load Topics . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-33
Loading and Storing of ISIR Records . . . . . . . . . . . . . . . . . . . . . . . 2-33
New Person Versus Existing Person . . . . . . . . . . . . . . . . . . . . . . . 2-35
Data Load Part 1 (RCBTPxx, RCBCTxx) Temporary Tables . . . . . . . . . . . . 2-36
Common Matching Algorithm . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-39
Rule Indicators . . . . . . . . . . . . . . . .
Field Length values . . . . . . . . . . . . . .
Primary Match logic . . . . . . . . . . . . . .
Secondary Match Logic . . . . . . . . . . . .
Examples of Matching Algorithm and Results.
January 2009
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Banner Financial Aid 8.3
User Guide
Contents
. 2-39
. 2-40
. 2-40
. 2-42
. 2-43
iii
Pell Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Pell Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Pell Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Pell Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Pell Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Fund Base Data form (RFRBASE) . . . . . . . . . . . . . . . . . . . . . . . . . 2-45
Detail Code Control form (TSADETC) . . . . . . . . . . . . . . . . . . . . . . . 2-46
Fund Management form (RFRMGMT) . . . . . . . . . . . . . . . . . . . . . . . 2-46
Aid Year Specific Data - Packaging Options window . . . . . . . . . . . . . . . 2-46
Aid Year Specific Data - Disbursement Options window . . . . . . . . . . . . . 2-47
Institution Financial Aid Options form (ROAINST) . . . . . . . . . . . . . . . . . 2-48
Main window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-48
Pell Grant Defaults - Defaults window. . . . . . . . . . . . . . . . . . . . . . . 2-48
Campus/EDE Defaults window . . . . . . . . . . . . . . . . . . . . . . . . . . 2-49
Budget Component Validation form (RTVCOMP). . . . . . . . . . . . . . . . . . 2-50
Packaging Options form (RPROPTS). . . . . . . . . . . . . . . . . . . . . . . . 2-50
Main Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Pell Options Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-50
Pell Options Window - Enrollment Options . . . . . . . . . . . . . . . . . . . . 2-51
Aid Period Validation form (RTVAPRD) . . . . . . . . . . . . . . . . . . . . . . . 2-52
Aid Period/Term Rules form (RORTPRD). . . . . . . . . . . . . . . . . . . . . . 2-52
Default Award & Disbursement Schedule Rules form (RFRDEFA) . . . . . . . . . 2-52
Fund Award and Disbursement Schedule Rules form (RFRASCH) . . . . . . . . 2-53
Federal Rules Inquiry form (RPIFEDR) . . . . . . . . . . . . . . . . . . . . . . . 2-53
Class Code Translation Rules form (RPRCLSS) . . . . . . . . . . . . . . . . . . 2-53
Pell Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Batch Pell Awards. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Override a Bachelors Degree . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Manual Adjustments to Pell Grants . . . . . . . . . . . . . . . . . . . . . . . . . 2-54
Why and How to Lock Pell Grants . . . . . . . . . . . . . . . . . . . . . . . . . 2-55
Lock Types . . . .
Fund Locks . . . .
Term Locks . . . .
Lock Functionality .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2-55
. 2-55
. 2-55
. 2-56
Updating Award Amounts to Agree with Actual Disbursement Amounts . . . . . . 2-56
Reducing an Award for Pell Paid at Another School in the Same Aid Year. . . . . 2-58
Handling Less-Than-Half Time for Pell More Efficiently . . . . . . . . . . . . . . 2-58
iv
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Controlling when the Pell Calculation Process is Run . . . . . . . . . . . . . . . 2-59
ROASTAT Student Level is Checked: . . . . . . . . . . . . . . . . . . . . . . . 2-60
ROAINST Campus Level is Checked: . . . . . . . . . . . . . . . . . . . . . . 2-60
ROAINST Institutional Level is Checked: . . . . . . . . . . . . . . . . . . . . . 2-60
Setup Procedure for Multiple Pell Fund Codes . . . . . . . . . . . . . . . . . . . 2-61
Pell Process (RPEPELL) for Pell Processing . . . . . . . . . . . . . . . . . . . . 2-61
Option to Delete Zero Pell Awards. . . . . . . . . . . . . . . . . . . . . . . .
Recognizing Co-Existence of Multiple Pells For Same Student Simultaneously.
Locked Records . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Rounding Option . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Offered or Auto Accepted . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Award Schedules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Award Change Letter Indicator . . . . . . . . . . . . . . . . . . . . . . . . .
. 2-61
. 2-62
. 2-63
. 2-63
. 2-63
. 2-63
. 2-63
Disbursement Process (RPEDISB) for Pell Processing . . . . . . . . . . . . . . 2-64
Recognizing Multiple Pell Funds . . . . . . . . . . . .
Back Out of Memo, Authorizations, and Disbursements
Use Disbursement Enrollment Edits for Memo Option .
RPEDISB Process Reports.. . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2-64
. 2-64
. 2-65
. 2-65
Pell Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-65
Pell Calculation Process (RPEPELL) . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Pell Grant Award Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-66
Pell Grant Award Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-67
Example #1 (continued) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-68
Pell Grant Disbursement Calculation . . . . . . . . . . . . . . . . . . . . . . . . 2-69
Disbursement Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-70
Need Analysis and EDE Correction Logging . . . . . . . . . . . . . . . . . . 2-71
Processing EDE Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-72
Methodology Specific Changes . . . . . . . . . . . . . . . . . . . . . . . . . 2-74
Setting a Student’s Dependency Codes . . . . . . . . . . . . . . . . . . . . . 2-74
Selecting a Student’s Dependency Status . . . . . . . . . . . . . . . . . . . . 2-75
EFC Proration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-75
Estimated vs Official Contributions . . . . . . . . . . . . . . . . . . . . . . . 2-76
Recalculate Need Analysis Indicator Functionality Updates . . . . . . . . . . 2-77
January 2009
Banner Financial Aid 8.3
User Guide
Contents
v
Requirements Tracking Procedures . . . . . . . . . . . . . . . . . . . . . . . 2-77
Requirements Tracking Implementation . . . . . . . . . . . . . . . . . . . . . . 2-77
Budgeting Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78
Budget Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-78
Satisfactory Academic Progress (SAP) Processing . . . . . . . . . . . . . . 2-81
SAP forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-81
Satisfactory Academic Progress Validation form (RTVSAPR) . . . .
Financial Aid Selection Rules form (RORRULE) . . . . . . . . . . .
Applicant Immediate Process form (ROAIMMP) . . . . . . . . . . .
Applicant Status form (ROASTAT) . . . . . . . . . . . . . . . . . .
Satisfactory Academic Progress Translation Rules form (RORSTRF)
Group Inquiry form (ROIGRPI) . . . . . . . . . . . . . . . . . . . .
Institution Financial Aid Option form (ROAINST) . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2-81
. 2-83
. 2-83
. 2-84
. 2-85
. 2-86
. 2-86
SAP Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-87
SAP Assignment Process (ROPSAPR) . . . . . . . . . . . . . . . . . . . . . . 2-87
Process Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-89
Sample Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-91
Funds Management Procedures . . . . . . . . . . . . . . . . . . . . . . . . . 2-93
Funds Management Implementation . . . . . . . . . . . . . . . . . . . . . . . . 2-93
Fund Balance Reconciliation . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-94
Calculating Fund Balances - Setting and Using
Overcommitment Levels in Packaging . . . . . . . . . . . . . . . . . . . . . . 2-95
Packaging and Disbursement Procedures. . . . . . . . . . . . . . . . . . . . 2-96
Packaging Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-96
Packaging/Simulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-98
Packaging Process Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99
Initialization Process (run as part of RPEPCKG) . . . . . . . . . . . . . . . . . . 2-99
Simulated Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-99
Actual Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Using NSLDS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Award Validation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-100
Award Validation Prior to Receipt of NSLDS Data . . . . . . . . . . . . . . . . 2-101
Award Validation After Receipt of NSLDS Data. . . . . . . . . . . . . . . . . . . 2-101
Original Awards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-101
Modifying Existing Stafford, Direct or Perkins Awards . . . . . . . . . . . . . . . 2-102
vi
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Stafford/Direct Loans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Perkins Loans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-102
Default/Refund Information and Financial Aid Eligibility . . . . . . . . . . . . . . 2-102
Validating Awards Against Defaults/Refunds . . . . . . . . . . . . . . . . . . . . 2-102
Validating Disbursements Against Defaults/Refunds . . . . . . . . . . . . . . . . 2-103
Using NSLDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-104
Student Loan Data System form (RNASLxx) . . . . . . . . . . . . . . . . . . . . 2-104
Applicant Student Loan Data Inquiry form (RNINSLD) . . . . . . . . . . . . . . . 2-104
Need Analysis form (RNARSxx) . . . . . . . . . . . . . . . . . . . . . . . . . . 2-105
Award forms (RPAAWRD)/(RPAAPMT)/(ROARMAN) . . . . . . . . . . . . . . . 2-105
Output Population Selection With Financial Aid Data Load, Part 3 . . . . . . . . . 2-106
Banner Financial Aid Fund Specific Packaging Options . . . . . . . . . . . . 2-107
Banner Financial Aid Global Packaging Options . . . . . . . . . . . . . . . . 2-113
Factors Determining Whether an Online/Batch Award is Packaged . . . . . . 2-115
Manually Scheduling Awards . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-119
Adding Terms to an Award Schedule . . . . . . . . . . . . . . . . . . . . . . 2-119
Award by Term Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-120
Identifying Students Needing New or Revised Award Letters . . . . . . . . . 2-121
Banner Financial Aid Global Disbursement Options . . . . . . . . . . . . . . 2-123
Banner Financial Aid Fund Specific Disbursement Options . . . . . . . . . . 2-126
Disbursement Validation Edits . . . . . . . . . . . . . . . . . . . . . . . . . . 2-134
Other Disbursement Considerations . . . . . . . . . . . . . . . . . . . . . . . 2-140
Regulatory Compliance for Stafford Disbursements . . . . . . . . . . . . . . . . 2-140
Disbursement Edits for Loans to Match Edits for other Funds . . . . . . . . . . . 2-141
Memo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-141
Loan Authorization to Net Returned Amounts . . . . . . . . . . . . . . . . . . . 2-141
Using Enrollment Disbursement Edits for Funds in Memo Status . . . . . . . . . 2-141
Recognition of Pell Payment Cell to Disbursement Process . . . . . . . . . . . . 2-142
Part-Time Proration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-142
January 2009
Banner Financial Aid 8.3
User Guide
Contents
vii
Memos Processed After Scheduled Disbursement Date . . . . . . . . . . . . . . 2-144
VA Chapter 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-144
Voiding Excess Payments for Students No Longer Eligible. . . . . . . . . . . . . 2-144
Disbursement Validation Reject Messages . . . . . . . . . . . . . . . . . . . . . 2-145
Disbursement Reports Generated by Disbursement Process . . . . . . . . . . . 2-145
Executing the Disbursement Process by an Oracle Pipe . . . . . . . . . . . . 2-146
Disbursement Pipe Terminology/Methodology . . . . . . . . . . . . . . . . . . . 2-147
Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-148
Disbursement Process Driver (RPEDISB) . . . . . . . . . . . . . . . . . . . . 2-148
Subprograms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-148
Disbursement Driver (RPEDISBS) . . . . . . . . . . . . . . . . . . . . . . . . 2-148
Log Print Subprogram (RNELOGW) . . . . . . . . . . . . . . . . . . . . . . . 2-148
Disbursement Output to Database Subprogram (RPEDISBO) . . . . . . . . . . 2-148
Running Disbursement the Traditional Way . . . . . . . . . . . . . . . . . . . . 2-148
Running Disbursement Using Pipes . . . . . . . . . . . . . . . . . . . . . . . . 2-149
Output Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-150
RPEDISB/Disbursement Using Pipes/Saving Output to Database . . . . . . . . . 2-151
Default/Refund Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-153
Levels of Default/Refund Administration . . . . . . . . . . . . . . . . . . . . . . 2-153
Sources of Default/Refund Information . . . . . . . . . . . . . . . . . . . . . . . 2-153
Title IV Refund/Repayment Process . . . . . . . . . . . . . . . . . . . . . . . . 2-155
Pell Grant Award and Disbursement Processing . . . . . . . . . . . . . . . . 2-155
State Grant Award Processing . . . . . . . . . . . . . . . . . . . . . . . . . . 2-157
Contracts and Exemptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-158
Contracts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-158
Exemptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-159
Excluding Contracts and Exemptions . . . . . . . . . . . . . . . . . . . . . . . . 2-159
Loan Processing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-161
Manual Loans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-161
Disbursing Manual Loan Checks through Banner . . . . . . . . . . . . . . . . . 2-161
Institutional Financial Aid Options form (ROAINST) . . . . . . . . . . . . . . . . 2-162
Aid Period/Term Rules form (RORTPRD). . . . . . . . . . . . . . . . . . . . . . 2-162
Default Award & Disbursement Schedule Rules form (RFRDEFA) . . . . . . . . . 2-163
viii
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Detail Code Control form (TSADETC) . . . . . . . . . . . . . . . . . . . . . . . 2-163
Fund Base Data form (RFRBASE) . . . . . . . . . . . . . . . . . . . . . . . . . 2-163
Funds Management form (RFRMGMT). . . . . . . . . . . . . . . . . . . . . . . 2-163
Packaging Options form (RPROPTS). . . . . . . . . . . . . . . . . . . . . . . . 2-164
Class Code Translation Rules form (RPRCLSS) . . . . . . . . . . . . . . . . . . 2-165
Certification Initials Validation form (RTVCINT) . . . . . . . . . . . . . . . . . . . 2-165
Loan Status Validation form (RTVLNST) . . . . . . . . . . . . . . . . . . . . . . 2-165
Lender Base Data Rules form (RPRLNDR). . . . . . . . . . . . . . . . . . . . . 2-165
Loan Period Base Data form (RPRLPRD) . . . . . . . . . . . . . . . . . . . . . 2-165
Loan Options form (RPRLOPT). . . . . . . . . . . . . . . . . . . . . . . . . . . 2-166
Lender/Disbursing Agents Rules form (RPRLNDA) . . . . . . . . . . . . . . . . 2-168
First-Year, First-Time Borrower Loan Rule . . . . . . . . . . . . . . . . . . . . . 2-168
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-168
Determination of a First-Year, First-Time Borrower . . . . . . . . . . . . . . . . 2-169
Crosswalk Validation form (GTVSDAX) . . . . . . . . . . . . . . . . . . . . . . . 2-170
Applicant Requirements form (RRAAREQ) . . . . . . . . . . . . . . . . . . . . . 2-170
Award forms (RPAAWRD)/(RPAAPMT)/(ROARMAN) . . . . . . . . . . . . . . . 2-171
Electronic Loan Application Process (RPRELAP) . . . . . . . . . . . . . . . . . 2-171
RPAELAP Fields Updated by RPRELAP Process . . . . . . . . . . . . . . . . . 2-173
Loan Parent Inquiry form (RPILPAR) . . . . . . . . . . . . . . . . . . . . . . . . 2-175
Electronic Loan Application Extract Process (RPRELAX) . . . . . . . . . . . . . 2-176
Batch Control form (RPIBATC) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-177
RPAELAP Fields Updated by the RPRELAX Process . . . . . . . . . . . . . . . 2-177
Electronic Loan Response Upload Process (RPRELRU). . . . . . . . . . . . . . 2-177
RPAELAP Fields Updated by the RPRELRU Process . . . . . . . . . . . . . . . 2-178
Disbursement/Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-179
Hold/Release Process (RPRHDRL) . . . . . . . . . . . . . . . . . . . . . . . . 2-180
Electronic Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-180
EFT Posting Process (RPREFTP) . . . . . . . . . . . . . . . . . . . . . . . . . 2-181
Disbursement form Field Population . . . . . . . . . . . . . . . . . . . . . . . . 2-183
Disburse to Student Account . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-184
Loan Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-185
Loan Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-186
CommonLine Loan Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-186
Electronic Loans as Certification Requests in Common Response File . . . . . . 2-188
Alternative Loans . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-189
Alternative Loan Processing Flow . . . . . . . . . . . . . . . . . . . . . . . . . 2-189
January 2009
Banner Financial Aid 8.3
User Guide
Contents
ix
Institutional Financial Aid Options form (ROAINST) . . . . . . . . . . . . . . . . 2-190
Fund Base Data form (RFRBASE) . . . . . . . . . . . . . . . . . . . . . . . . . 2-190
Fund Management form (RFRMGMT) . . . . . . . . . . . . . . . . . . . . . . . 2-190
Loan Options form (RPRLOPT). . . . . . . . . . . . . . . . . . . . . . . . . . . 2-190
Loan Period Base Data Rules form (RPRLPRD) . . . . . . . . . . . . . . . . . . 2-190
Electronic Loan Application Process (RPRELAP) . . . . . . . . . . . . . . . . . 2-191
Electronic Loan Application form (RPAELAP) . . . . . . . . . . . . . . . . . . . 2-191
Electronic Loan Application Extract Process (RPRELAX) . . . . . . . . . . . . . 2-192
Electronic Loan Response Update Process (RPRELRU). . . . . . . . . . . . . . 2-192
Electronic Loan Load/Post Processes (RPEFTL/RPREFTP) . . . . . . . . . . . . 2-192
Disbursement Process (RPEDISB) . . . . . . . . . . . . . . . . . . . . . . . . . 2-192
Disbursement/Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-192
Disbursement Process (RPEDISB) . . . . . . . . . . . . . . . . . . . . . . . . . 2-193
Hold/Release Process (RPRHDRL) . . . . . . . . . . . . . . . . . . . . . . . . 2-193
Electronic Transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-194
EFT/Disbursement Roster Upload Process (RPREFTL) . . . . . . . . . . . . . . 2-194
Electronic Payment Receipt form (RPAEPMT) . . . . . . . . . . . . . . . . . . . 2-194
EFT Posting Process (RPREFTP) . . . . . . . . . . . . . . . . . . . . . . . . . 2-195
RPAELAP Fields Populated by RPREFTP Process . . . . . . . . . . . . . . . . 2-195
Electronic Loan Disbursement form (RPAELDB) . . . . . . . . . . . . . . . . . . 2-195
Disbursement form Field Population . . . . . . . . . . . . . . . . . . . . . . . . 2-196
Disburse to Student Account . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-198
Disbursement Process (RPEDISB) . . . . . . . . . . . . . . . . . . . . . . . . . 2-198
Loan Adjustments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-198
Loan Reports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-199
Aging of Nondisbursed Loans Report (RPRLNAG) . . . . . . . . . . . . . . . . . 2-199
RPRLNEX Exceptions-Students Not Fully Funded Report . . . . . . . . . . . . . 2-200
Loan Summary Report (RPRLSUM) . . . . . . . . . . . . . . . . . . . . . . . . 2-200
CommonLine Loan Adjustment . . . . . . . . . . . . . . . . . . . . . . . . . . 2-200
Electronic Loans Received as Certification Requests in
Common Response File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-202
Direct Lending . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-203
Financial Aid Common Functions . . . . . . . . . . . . . . . . . . . . . . . . 2-203
Aid Year Default. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-203
x
Banner Financial Aid 8.3
User Guide
Contents
January 2009
User-Defined Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-204
Batch Posting Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-204
Displaying Student Enrollment . . . . . . . . . . . . . . . . . . . . . . . . . . 2-211
Building Rules (RORRULE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212
Using Parentheses in Selection Statements . . . . . . . . . . . . . . . . . . . . 2-212
Hints for RORRULE form Use . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-212
Student Employment Procedures . . . . . . . . . . . . . . . . . . . . . . . . 2-213
Student Employment Implementation . . . . . . . . . . . . . . . . . . . . . . . . 2-213
Algorithmic Packaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-215
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-215
Algorithmic Packaging Features . . . . . . . . . . . . . . . . . . . . . . . . . . 2-215
Algorithms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Packaging Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Awarding Based on Other Funds . . . . . . . . . . . . . . . . . . . . . .
Award a Fund Based on a Percentage of Another Fund . . . . . . . . . .
Simplification of Rules Creation and Maintenance . . . . . . . . . . . . .
Ability to Store and Reference Internal Interim Values in Packaging Rules .
Packaging Simulation Options . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 2-215
. 2-216
. 2-217
. 2-217
. 2-217
. 2-217
. 2-217
. 2-218
Related Fund Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-218
forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Group Fund Limits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ability to Apply a Percentage to All the Funds in the Package as a Group .
Rounding Options for Awards . . . . . . . . . . . . . . . . . . . . . . . .
Ability to Inactivate Fund Codes, Groups, and Rules . . . . . . . . . . . .
Ability to Override a Fund Rule for a Specific Student . . . . . . . . . . .
Fund Category and Fund Cross-Reference Fields for
Packaging and Reporting . . . . . . . . . . . . . . . . . . . . . . . . .
Fund Balance Roll Process (RFPFBRL) . . . . . . . . . . . . . . . . . .
Ability to Display All Recipients of a Particular Fund Code by
Aid Year or Term . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
. 2-218
. 2-218
. 2-219
. 2-219
. 2-219
. 2-219
. . . 2-219
. . . 2-220
. . . 2-220
Sample Algorithmic Packaging Rules. . . . . . . . . . . . . . . . . . . . . . . . 2-221
Example 1 - Institutional Grant with Amounts Based on
GPA and IM EFC Ranges . . . . . . . . . . . . . . . . . . . . . . . . . .
Example 2 - SEOG Award Calculation Based on
Pell Award Amounts for the Year . . . . . . . . . . . . . . . . . . . . . .
Example 3 - SEOG Award Calculation Based on
Pell Award Amounts for the Year while using Baseline Database Functions
Example 4 - SEOG Award Calculation Based on Pell Award Amounts for
the Year while using Multiple Pell Fund Codes . . . . . . . . . . . . . . .
January 2009
. . 2-221
. . 2-222
. . 2-224
. . 2-226
Banner Financial Aid 8.3
User Guide
Contents
xi
Example 5 - SEOG Award Calculation Based on
Pell Award Amounts for the Year while using Multiple Pell Fund Codes
and while using Baseline Database Functions . . . . . . . . . . . . . . . .
Example 6 - Calculating Perkins Loans as a Percentage of Pell . . . . . . . .
Example 7 - Calculation for a State Fund which has a Range of
Offer Amounts Based on a Percentage of Need and Various Ranges of
Cost of Attendance and EFC . . . . . . . . . . . . . . . . . . . . . . . . .
Example 8 - Calculation for a State Fund which has a Range of Offer Amounts
Based on EFC and Whether a Student is In-State or Out-of-State . . . . . .
Example 9 - Calculate an Equity Packaging Amount Based on
Both Gross Need and Budget . . . . . . . . . . . . . . . . . . . . . . . . .
. 2-230
. 2-232
. 2-235
. 2-239
. 2-240
Columns Defined on the Temporary Packaging Need Table (RPTNEED) . . . . . 2-242
New Functions Defined in the rpkalgr Package. . . . . . . . . . . . . . . . . . . 2-244
Scholarship and Athletics Processing by Term . . . . . . . . . . . . . . . . . 2-246
Potential Athletic Grant Defaults (RAAPAGD) . . . . . . . . . . . . . . . . . . . 2-246
Sport Aid by Term form(RAASPTM) . . . . . . . . . . . . . . . . . . . . . . . . 2-247
Team Sport Term Aid (RAITMTM) . . . . . . . . . . . . . . . . . . . . . . . . . 2-247
Donor/Scholarship Demographics (RFADSCD) . . . . . . . . . . . . . . . . . . 2-247
Scholarship Term Information (RPASTRM) . . . . . . . . . . . . . . . . . . . . . 2-247
Athletic Aid Type Validation (RTVAATP) . . . . . . . . . . . . . . . . . . . . . . 2-247
Financial Aid Sport Validation (RTVFASP) . . . . . . . . . . . . . . . . . . . . . 2-247
Grades to Donor Validation (RTVGRDD) . . . . . . . . . . . . . . . . . . . . . . 2-248
Scholarship Source Validation (RTVSSRC) . . . . . . . . . . . . . . . . . . . . 2-248
Reviewed Validation (RTVREVW) . . . . . . . . . . . . . . . . . . . . . . . . . 2-248
Thank You Letter Validation (RTVTYLT) . . . . . . . . . . . . . . . . . . . . . . 2-248
Contract Rules (RPRCONT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-248
Exemption Rules (RPREXPT) . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-248
Resource Code Validation (RTVARSC) . . . . . . . . . . . . . . . . . . . . . . . 2-248
Athletic Grant Term Roll Process (RAPAGRL) . . . . . . . . . . . . . . . . . . . 2-249
Athletic Aid Discrepancy Report (RARATAD) . . . . . . . . . . . . . . . . . . . . 2-249
Chapter 3
Applicant Processing
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Applicant Processing flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
xii
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Chapter 4
Need Analysis
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Need Analysis Online Recalculation Process Flow Narrative . . . . . . . . . 4-2
Chapter 5
Requirements Tracking
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Requirements Tracking Process Flow Narrative . . . . . . . . . . . . . . . . 5-2
Chapter 6
Budgeting
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1
Budgeting Process Flow Narrative . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Chapter 7
Packaging and Disbursement
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
Packaging Process Flow Narrative . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Chapter 8
Athletics
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Chapter 9
Funds Management
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
Funds Management Process Flow Narrative . . . . . . . . . . . . . . . . . . 9-2
Chapter 10 Electronic Data Exchange
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Electronic Data Exchange Process Flow Narrative . . . . . . . . . . . . . . . 10-2
January 2009
Banner Financial Aid 8.3
User Guide
Contents
xiii
Chapter 11 History and Transcripts
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1
History and Transcripts Process Flow . . . . . . . . . . . . . . . . . . . . . . 11-2
Chapter 12 Financial Aid Common Functions
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1
Common Functions Process Flow Narrative . . . . . . . . . . . . . . . . . . 12-3
Chapter 13 Student System Shared Data
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1
Student System Shared Data Process Flow Narrative . . . . . . . . . . . . . 13-2
Chapter 14 Short-Term Credit
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14-1
Short-Term Credit Process Flow Narrative . . . . . . . . . . . . . . . . . . . 14-1
Chapter 15 Student Employment
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15-1
Student Employment Process Flow Narrative . . . . . . . . . . . . . . . . . . 15-2
Chapter 16 Loan Processing
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-1
Manual Loan Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16-3
Chapter 17 Return of Title IV Funds
Forms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17-1
xiv
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Return of Title IV Funds Process Flow . . . . . . . . . . . . . . . . . . . . . . 17-2
Chapter 18 Reports and Processes
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-1
Naming Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-2
Athletic Grant Term Roll Process . . . . . . . . . . . . (RAPAGRL). . . . . . . 18-5
Athletic Grant Term Roll Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-6
Athletic Aid Discrepancy Report . . . . . . . . . . . . . (RARATAD) . . . . . . . 18-7
Athletic Aid Discrepancy Report Sample . . . . . . . . . . . . . . . . . . . . . 18-8
Applicant Budget Report . . . . . . . . . . . . . . . . . (RBRABUD) . . . . . . 18-9
Applicant Budget Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-12
Budget Component Report . . . . . . . . . . . . . . . . (RBRBCMP) . . . . . . 18-14
Budget Component Report Sample . . . . . . . . . . . . . . . . . . . . . . . . 18-15
Financial Aid CSS Data Load Part 1 Process . . . . . . (RCBCTxx) . . . . . . . 18-16
Financial Aid CSS Data Load Part 1 Process Sample . . . . . . . . . . . . . . 18-19
Financial Aid EDE Data Load Part 1 Process . . . . . . (RCBTPxx) . . . . . . . 18-20
Financial Aid EDE Data Load Part 1 Report Sample . . . . . . . . . . . . . . . 18-23
Financial Aid Data Load Table Deletes Process . . . . . (RCPDTMP) . . . . . . 18-24
Financial Aid Data Load Table Deletes Process Sample . . . . . . . . . . . . . 18-25
Copy IM Data to FM Process . . . . . . . . . . . . . . . (RCPIMFM). . . . . . . 18-27
Financial Aid Data Load Part 2 Process . . . . . . . . . (RCPMTCH) . . . . . . 18-28
Financial Aid Data Load Part 2 Process Sample . . . . . . . . . . . . . . . . . 18-29
Financial Aid Data Load Part 3 Process . . . . . . . . . (RCRTPxx) . . . . . . . 18-32
Financial Aid Data Load, Part 3 Report Sample (Student Listing) . . . . . . .
Financial Aid Data Load, Part 3 Report Sample (Discrepancy Report) . . . . .
Financial Aid Data Load, Part 3 Report Sample (NSLDS Discrepancy Report)
Financial Aid Data Load, Part 3 Report Sample (Errors Listing) . . . . . . . .
Financial Aid Data Load, Part 3 Report Sample (Report Control Listing) . . . .
. 18-36
. 18-37
. 18-39
. 18-39
. 18-40
ISIR Correction/Request Process . . . . . . . . . . . . (REBCDxx) . . . . . . . 18-41
ISIR Correction/Request Process Sample . . . . . . . . . . . . . . . . . . . . 18-45
CAL MIS Extract Process
. . . . . . . . . . . . . . . . (RERCALX). . . . . . . 18-46
2008-2009 COD Print Process . . . . . . . . . . . . . . (RERCD09). . . . . . . 18-51
Pell Origination Report - Sent Origination Records . . . . .
ACG Origination Report - Sent Origination Records . . . .
SMART Origination Report - Sent Origination Records . . .
Direct Loan Origination Report - Sent Origination Records .
Pell Origination Report - Unsent Origination Records. . . .
ACG Origination Report - Unsent Origination Records . . .
SMART Origination Report - Unsent Origination Records .
January 2009
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Banner Financial Aid 8.3
User Guide
Contents
. 18-53
. 18-54
. 18-54
. 18-55
. 18-55
. 18-56
. 18-56
xv
Direct Loan Origination Report - Unsent Origination Records
Pell Disbursement Report . . . . . . . . . . . . . . . . . . .
ACG Disbursement Report . . . . . . . . . . . . . . . . . .
SMART Disbursement Report. . . . . . . . . . . . . . . . .
Direct Loan Disbursement Report. . . . . . . . . . . . . . .
2008-2009 Correction Error Report
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 18-57
. 18-57
. 18-58
. 18-58
. 18-59
. . . . . . . . . . . (RERCE09) . . . . . . . 18-60
ISIR Corr/Request Control Report . . . . . . . . . . . . (RERCRCR) . . . . . . 18-61
ISIR Corr/Request Control Report Sample . . . . . . . . . . . . . . . . . . . . 18-62
2008-2009 COD Extract Process
. . . . . . . . . . . . (REREX09) . . . . . . . 18-77
2008-2009 COD Extract Process . . . . . . . . . . . . . . . . . . . . . . . . . 18-86
Grant File Import Process . . . . . . . . . . . . . . . . (RERFI09) . . . . . . . 18-87
Pell File Import (RERFIxx.lis) .
Pell File Import (RERFIxx.log).
Pell File Import (RERFIxx.ls1).
Pell File Import (RERFIxx.ls2).
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 18-89
. 18-89
. 18-90
. 18-90
Grant COD Miscellaneous Report . . . . . . . . . . . . (RERGRNT) . . . . . . 18-91
Pell Disbursement Locked for COD . . . . . . . . . . . . . . . . . . . .
ACG Disbursement Locked for COD . . . . . . . . . . . . . . . . . . .
SMART Disbursement Locked for COD. . . . . . . . . . . . . . . . . .
Multiple Reporting Records . . . . . . . . . . . . . . . . . . . . . . . .
Rejected Origination Records . . . . . . . . . . . . . . . . . . . . . . .
Rejected Disbursement Records . . . . . . . . . . . . . . . . . . . . .
Year To Date Records: Reconciliation Records without a
Matching Banner Origination Record . . . . . . . . . . . . . . . . . .
Year To Date Records: Banner Originations without a
Matching Reconciliation Record . . . . . . . . . . . . . . . . . . . . .
Year To Date Records: All Grant Recipients . . . . . . . . . . . . . . .
Year To Date Records: All Grant Recipients . . . . . . . . . . . . . . .
Year To Date Records: COD Accept Amount <> Banner Award Amount .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 18-97
. 18-98
. 18-98
. 18-99
. 18-99
. 18-99
. . . . 18-100
.
.
.
.
.
.
.
.
.
.
.
.
. 18-101
. 18-102
. 18-103
. 18-104
2008-2009 COD Import Process . . . . . . . . . . . . . (RERIM09) . . . . . . . 18-105
2008-2009 COD Import Process . . . . . . . . . . . . . . . . . . . . . . . . . 18-108
COD Import/Export Report . . . . . . . . . . . . . . . . (RERIMEX) . . . . . . . 18-111
Financial Aid COD Extract/Import Report Sample (Direct Loan Origination Records - Extract Report/Records in Sent Status) . . 18-116
Financial Aid COD Extract/Import Report Sample (Direct Loan Disbursement Records - Extract Report/Records in Sent Status) . 18-116
Financial Aid COD Extract/Import Report Sample (Direct Loan Origination Change Records Extract Report/Records in Sent Status) . . . . . . . . . . . . . . . . . . . . . 18-117
Financial Aid COD Extract/Import Report Sample (Pell Award Records - Extract Report/Records in Sent Status) . . . . . . . . . 18-117
Financial Aid COD Extract/Import Report Sample (Pell Disbursement Records - Extract Report/Records in Sent Status) . . . . . 18-118
Financial Aid COD Extract/Import Report Sample (ACG Award Records - Extract Report/Records in Sent Status) . . . . . . . . 18-118
xvi
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Financial Aid COD Extract/Import Report Sample (ACG Disbursement Records - Extract Report/Records in Sent Status) . .
Financial Aid COD Extract/Import Report Sample (SMART Award Records - Extract Report/Records in Sent Status) . . . . .
Financial Aid COD Extract/Import Report Sample (SMART Disbursement Records - Extract Report/Records in Sent Status) .
Financial Aid COD Extract/Import Report Sample (Pell Origination Records - Import Report) . . . . . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (Pell Disbursement Records - Import Report) . . . . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (Direct Loan Origination Records - Import Report) . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (Direct Loan Change Records - Import Report) . . . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (ACG Origination Records - Import Report) . . . . . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (ACG Disbursement Records - Import Report) . . . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (SMART Origination Records - Import Report) . . . . . . . . . . . . . . .
Financial Aid COD Extract/Import Report Sample (SMART Disbursement Records - Import Report). . . . . . . . . . . . . .
Financial Aid COD Import/Export Report — (Student Identifier Compare) . .
Financial Aid COD Import/Export Report —
(Identifier Change Records and Identifier Records with Edits/Rejects) . . .
. . 18-119
. . 18-119
. . 18-120
. . 18-120
. . 18-121
. . 18-122
. . 18-123
. . 18-123
. . 18-124
. . 18-124
. . 18-125
. . 18-125
. . 18-126
ISIR Print Process . . . . . . . . . . . . . . . . . . . . (RERISxx) . . . . . . . 18-127
ISIR Print Process Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-129
2008-2009 Grant Origination Creation Process . . . . . (REROR09). . . . . . . 18-134
2008-2009 Grant Origination Creation Process Report Sample . . . . . . . . . 18-138
2008-2009 Grant Origination Creation Process Report Sample . . . . . . . . . 18-139
Fund Balance Roll Process
. . . . . . . . . . . . . . . (RFPFBRL) . . . . . . . 18-140
Account Balance Report . . . . . . . . . . . . . . . . . (RFRABAL) . . . . . . . 18-144
Account Balance Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-146
Fund Budget Report . . . . . . . . . . . . . . . . . . . (RFRBUDG) . . . . . . 18-149
Fund Budget Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-150
Fund Description Report . . . . . . . . . . . . . . . . . (RFRFUND) . . . . . . 18-152
Fund Description Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-153
Simulation Fund Balance Report . . . . . . . . . . . . . (RFRSBAL) . . . . . . . 18-155
Simulation Fund Balance Report Sample . . . . . . . . . . . . . . . . . . . . . 18-156
Applicant Comments Report . . . . . . . . . . . . . . . (RHRCOMM) . . . . . . 18-158
Applicant Comments Report Sample . . . . . . . . . . . . . . . . . . . . . . . 18-160
Applicant Comments Purge Process . . . . . . . . . . . (RHRPCOM) . . . . . . 18-162
Applicant Comments Purge Report . . . . . . . . . . . . . . . . . . . . . . . . 18-164
Authorization Report . . . . . . . . . . . . . . . . . . . (RJRAUTH). . . . . . . 18-165
January 2009
Banner Financial Aid 8.3
User Guide
Contents
xvii
Authorization Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-166
Pay Period Report . . . . . . . . . . . . . . . . . . . . (RJRDPPR). . . . . . . 18-168
Pay Period Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-169
Payroll Load Process . . . . . . . . . . . . . . . . . . . (RJRLOAD). . . . . . . 18-171
Payroll Load Process Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-173
Payroll Exception Report . . . . . . . . . . . . . . . . . (RJRPAYE) . . . . . . . 18-174
Payroll Exception Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-175
Earnings Control Report . . . . . . . . . . . . . . . . . (RJRSEEC). . . . . . . 18-177
Earnings Control Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-179
Award/Tracking Letter Indicator Reset Process . . . . . (RLRLETR) . . . . . . . 18-182
Award/Tracking Letter Indicator Reset Process Sample . . . . . . . . . . . . . 18-183
Need Analysis Logging Report . . . . . . . . . . . . . . (RLRLOGG) . . . . . . 18-184
Need Analysis Calculation Process . . . . . . . . . . . (RNEINxx) . . . . . . . 18-185
Need Analysis Calculation Process Sample . . . . . . . . . . . . . . . . . . . 18-186
Transfer Monitoring Application Creation Process . . . . (RNRTMAC) . . . . . . 18-187
Transfer Monitoring Application Creation Process Sample . . . . . . . . . . . . 18-190
Transfer Monitoring Extract Process . . . . . . . . . . . (RNRTMNE) . . . . . . 18-192
Transfer Monitoring Inform/FAH Extract Report Sample . . . . . . . . . . . . . 18-195
Transfer Monitoring Import Process . . . . . . . . . . . (RNRTMNI) . . . . . . . 18-196
Transfer Monitoring Import Process Sample . . . . . . . . . . . . . . . . . . . 18-198
Verification Discrepancy Report . . . . . . . . . . . . . (RNRVRFY) . . . . . . 18-201
Verification Discrepancy Report Sample . . . . . . . . . . . . . . . . . . . . . 18-204
Automatic Rule Compilation Process
. . . . . . . . . . (ROOGSQL) . . . . . . 18-206
Financial Aid New Year Roll Process
. . . . . . . . . . (ROPROLL) . . . . . . 18-207
Financial Aid New Year Roll Process Sample. . . . . . . . . . . . . . . . . . . 18-208
SAP Assignment Process . . . . . . . . . . . . . . . . (ROPSAPR) . . . . . . 18-210
SAP Assignment Process Sample . . . . . . . . . . . . . . . . . . . . . . . . 18-211
Financial Aid Term Roll Process . . . . . . . . . . . . . (ROPTERM) . . . . . . 18-212
User-Defined Data Process . . . . . . . . . . . . . . . (ROPUSER) . . . . . . 18-213
Audit Log Report . . . . . . . . . . . . . . . . . . . . . (RORALOG) . . . . . . 18-214
Audit Log Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-216
Basic Applicant Report . . . . . . . . . . . . . . . . . . (RORAPLT) . . . . . . . 18-219
Basic Applicant Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 18-220
Batch Posting Process . . . . . . . . . . . . . . . . . . (RORBPST) . . . . . . 18-222
Batch Posting Process Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 18-224
Calculated Values Process . . . . . . . . . . . . . . . . (RORCALC) . . . . . . 18-230
Calculated Values Process Sample . . . . . . . . . . . . . . . . . . . . . . . . 18-232
Financial Aid E-mail Process . . . . . . . . . . . . . . . (ROREMAL) . . . . . . 18-234
FISAP Report
xviii
Banner Financial Aid 8.3
User Guide
Contents
. . . . . . . . . . . . . . . . . . . . . . (RORFSxx) . . . . . . . 18-237
January 2009
RORFSxx_yyyyy.lis File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-242
RORFSxx_yyyyy.log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-250
Grade Exception Report . . . . . . . . . . . . . . . . . (RORGRDE) . . . . . . 18-251
Grade Exception Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-252
Automatic Group Assignment Process . . . . . . . . . . (RORGRPS) . . . . . . 18-253
Financial Aid High School Data Posting Process
. . . . (RORHSDP) . . . . . . 18-256
Financial Aid High School Data Posting Sample . . . . . . . . . . . . . . . . . 18-258
Logging Activity Archive/Purge Process . . . . . . . . . (RORLOGA) . . . . . . 18-259
Purging RORLOGM and RORLOGD Data . . . . . . . . . . . . . . . . . . . . 18-259
Archiving RORLOGM and RORLOGD Data . . . . . . . . . . . . . . . . . . . 18-260
RORLOGA_xxxxx.lis File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-263
Financial Aid Registration Report
. . . . . . . . . . . . (RORREGS) . . . . . . 18-265
Financial Aid Registration Report Sample . . . . . . . . . . . . . . . . . . . . 18-267
Award Roll Process
. . . . . . . . . . . . . . . . . . . (RPRAROL) . . . . . . 18-268
Disbursement Print Process . . . . . . . . . . . . . . . (RPBDDRV) . . . . . . 18-272
Disbursement Print Process Sample . . . . . . . . . . . . . . . . . . . . . . . 18-272
LMS Interface Accounting Feed Program . . . . . . . . (RPBLMIA) . . . . . . . 18-273
LMS Interface Accounting Feed Program Sample . . . . . . . . . . . . . . . . 18-274
LMS Interface Disbursement Feed Program . . . . . . . (RPBLMID) . . . . . . . 18-275
LMS Interface Disbursement Feed Program Sample . . . . . . . . . . . . . . . 18-277
LMS Interface Enrollment Extract Program . . . . . . . . (RBPLMIE) . . . . . . . 18-279
LMS Interface Enrollment Extract Program Sample . . . . . . . . . . . . . . . 18-281
Packaging Print Process . . . . . . . . . . . . . . . . . (RPBPDRV) . . . . . . 18-283
Packaging Print Process Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-284
Disbursement Process . . . . . . . . . . . . . . . . . . (RPEDISB) . . . . . . . 18-285
Student Aid Disbursement Report - Sorted by Reject/Warning Message . . . . . 18-288
Student Aid Disbursement Report - Sorted by Fund . . . . . . . . . . . . . . . 18-289
Student Aid Disbursement Report - Sorted by Fund Type . . . . . . . . . . . . 18-290
Packaging Process . . . . . . . . . . . . . . . . . . . . (RPEPCKG) . . . . . . 18-291
Pell Calculation Process . . . . . . . . . . . . . . . . . (RPEPELL) . . . . . . . 18-297
Pell Calculation Process Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-298
Batch Initialization Process . . . . . . . . . . . . . . . . (RPEPINT) . . . . . . . 18-299
Batch Initialization Process Sample . . . . . . . . . . . . . . . . . . . . . . . . 18-300
Web Applicant Info Process . . . . . . . . . . . . . . . (RPPINFO) . . . . . . . 18-301
Web Applicant Info Purge Process . . . . . . . . . . . . (RPPPINF) . . . . . . . 18-303
Applicant Disbursement Report . . . . . . . . . . . . . (RPRADSB) . . . . . . 18-305
Applicant Disbursement Report Sample . . . . . . . . . . . . . . . . . . . . . 18-306
Award and Disbursement Report . . . . . . . . . . . . . (RPRAWDB) . . . . . . 18-308
Award and Disbursement Report Sample. . . . . . . . . . . . . . . . . . . . . 18-309
Applicant Award Report . . . . . . . . . . . . . . . . . (RPRAWRD) . . . . . . 18-312
January 2009
Banner Financial Aid 8.3
User Guide
Contents
xix
Applicant Award Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-314
Award Cancellation Process Report . . . . . . . . . . . (RPRCNCL) . . . . . . 18-324
Award Cancellation Process Report Sample . . . . . . . . . . . . . . . . . . . 18-325
Direct Loan Compare Extract Process . . . . . . . . . . (RPRCP09) . . . . . . . 18-327
Direct Loan Compare Extract Process Sample . . . . . . . . . . . . . . . . . . 18-329
Disbursement Schedule Date Update Process
. . . . . (RPRDDUP) . . . . . . 18-330
Disbursement Schedule Date Update Process Sample. . . . . . . . . . . . . . 18-331
Promissory Note Manifest . . . . . . . . . . . . . . . . (RPRDLPM) . . . . . . 18-332
Batch Promissory Note Manifest (RPRDLPM.lis) sample. . . . . . . . . . . . . 18-335
Disclosure Statement Print Process . . . . . . . . . . . (RPRDSPT) . . . . . . 18-339
Disclosure Statement (RPRDSPT) Sample . . . . . . . . . . . . . . . . . . . . 18-342
Disclosure Statement (RPRDSPT) Sample (continued) . . . . . . . . . . . . . 18-343
2008-2009 Direct Loan Flat-File Upload . . . . . . . . . (RPRDU09). . . . . . . 18-344
2008-2009 Flat-File Upload Process - DLSAS . . . .
2008-2009 Flat-File Upload Process - MPNDISOP . .
2008-2009 Flat-File Upload Process - MPNINAOP . .
2008-2009 Flat-File Upload Process - MPNEXPOP .
2008-2009 Flat-File Upload Process (RPRDU09.lis) .
2008-2009 Flat-File Upload Process (RPRDU09.log).
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 18-347
. 18-354
. 18-355
. 18-355
. 18-356
. 18-356
EFT/Disbursement Roster Upload Process . . . . . . . (RPREFTL) . . . . . . . 18-357
EFT Posting Process . . . . . . . . . . . . . . . . . . . (RPREFTP). . . . . . . 18-360
Electronic Loan Application Process . . . . . . . . . . . (RPRELAP). . . . . . . 18-362
Electronic Loan Application Extract Process . . . . . . . (RPRELAX). . . . . . . 18-374
Electronic Loan Application Extract Sample . . . . . . . . . . . . . . . . . . . 18-377
Electronic Loan Change Transaction Process . . . . . . (RPRELCT). . . . . . . 18-379
Electronic Loan Change Transaction Report Sample . . . . . . . . . . . . . . . 18-382
Electronic Loan Response Upload Process . . . . . . . (RPRELRU) . . . . . . 18-384
Electronic Loan Response Report Sample . . . . . . . . . . . . . . . . . . . . 18-385
Hold/Release Process . . . . . . . . . . . . . . . . . . (RPRHDRL) . . . . . . 18-387
Electronic Loan Hold/Release Extract Sample . . . . . . . . . . . . . . . . . . 18-389
Loan Proceeds Aging Report
. . . . . . . . . . . . . . (RPRLNAG) . . . . . . 18-390
Loan Process Aging Report Sample . . . . . . . . . . . . . . . . . . . . . . . 18-391
Loan Funding Exception Report . . . . . . . . . . . . . (RPRLNEX). . . . . . . 18-392
Loan Funding Exception Report Sample . . . . . . . . . . . . . . . . . . . . . 18-395
Direct Loan Record Creation . . . . . . . . . . . . . . . (RPRLORC) . . . . . . 18-397
Direct Loan Record Creation (RPRLORC.lis) . . . . . . . . . . . . . . . . . . . 18-402
Loan Summary Report . . . . . . . . . . . . . . . . . . (RPRLSUM) . . . . . . 18-404
Loan Summary Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . . 18-405
Promissory Note Print Process . . . . . . . . . . . . . . (RPRPNPT) . . . . . . 18-408
RPRPNPT.lis Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-414
xx
Banner Financial Aid 8.3
User Guide
Contents
January 2009
RPRPNPT.li4 Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-418
RPRPNPT.li5 Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-419
RPRPNPT.li6 Sample . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18-420
Simulation Award Report . . . . . . . . . . . . . . . . . (RPRSAWD) . . . . . . 18-421
Simulation Award Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 18-422
Financial Aid Student Billing Payment Report . . . . . . (RPRSBPR) . . . . . . 18-423
Financial Aid Student Billing Payment Report Sample . . . . . . . . . . . . . . 18-425
SMART Grant Eligibility Report
. . . . . . . . . . . . . (RPRSMRT) . . . . . . 18-428
Smart Grant Eligibility Report — Students to Report parameter set to A). . . . . 18-430
Smart Grant Eligibility Report — Students to Report parameter set to E . . . . . 18-431
Short-Term Credits Report . . . . . . . . . . . . . . . . (RPRSTCR) . . . . . . 18-432
Short-Term Credits Report Sample . . . . . . . . . . . . . . . . . . . . . . . . 18-433
Return of Title IV Calculation Process . . . . . . . . . . (RPRTIVC) . . . . . . . 18-434
Return of Title IV Funds Calculation Process Sample . . . . . . . . . . . . . . 18-437
Return of Title IV Funds Withdrawal Calculation Report . (RPRTIVI) . . . . . . . 18-441
Return of Title IV Funds Withdrawal Calculation Report Sample . . . . . . . . . 18-444
Return of Title IV Funds Recipient Withdrawn Status Report (RPRTIVR) . . . . . 18-447
Return of Title IV Funds Recipient Withdrawn Status Report Sample . . . . . . 18-450
VA Benefits on FAFSA Report . . . . . . . . . . . . . . (RPRVABN). . . . . . . 18-453
VA Benefits on FAFSA Report Sample . . . . . . . . . . . . . . . . . . . . . . 18-455
Validate Award Process . . . . . . . . . . . . . . . . . (RPRVAWD) . . . . . . 18-456
Disbursement Validation Report . . . . . . . . . . . . . (RPRVDIS) . . . . . . . 18-460
Applicant Requirements Report . . . . . . . . . . . . . (RRRAREQ) . . . . . . 18-464
Applicant Requirements Report Sample . . . . . . . . . . . . . . . . . . . . . 18-468
Exit Interview Requirements Process . . . . . . . . . . (RRREXIT) . . . . . . . 18-469
Exit Interview Requirements Process Sample . . . . . . . . . . . . . . . . . . 18-474
Adm. Transfer/Fin Aid Transcript Report . . . . . . . . . (RRRTRAN) . . . . . . 18-476
Adm. Transfer/Fin Aid Transcript Report Sample . . . . . . . . . . . . . . . . . 18-477
Data Discrepancies Report . . . . . . . . . . . . . . . . (RSRDSCP) . . . . . . 18-478
Data Discrepancies Report Sample . . . . . . . . . . . . . . . . . . . . . . . . 18-480
Financial Aid Enrollment Hours Process . . . . . . . . . (RSRENRL) . . . . . . 18-483
Financial Aid Enrollment Hours Process Sample . . . . . . . . . . . . . . . . . 18-486
Financial Aid Transcript Requirements Process . . . . . (RSRPCOL) . . . . . . 18-487
Financial Aid Transcript Requirements Process Sample . . . . . . . . . . . . . 18-488
Chapter 19 Interfaces
Student Employment Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-1
Banner Human Resources Requirements . . . . . . . . . . . . . . . . . . . . . 19-3
January 2009
Banner Financial Aid 8.3
User Guide
Contents
xxi
Banner Financial Aid Requirements . . . . . . . . . . . . . . . . . . . . . . . . 19-5
Setting Up Student Employment forms . . . . . . . . . . . . . . . . . . . . . . . 19-5
Setting Up Applicant forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-6
Awarding Work Study Funds . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Tracking Non-Work Study Awards . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Referring Students to Positions . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-7
Authorizing Students to Work . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-8
Example #1 – One Position for All Departments . . . . . . . . . . . . . . . . . . 19-8
Example #2 – One Position for Each Department . . . . . . . . . . . . . . . . . 19-8
Using Payroll Feed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-9
Entering Earnings Without Payroll Feed . . . . . . . . . . . . . . . . . . . . . . 19-10
Making Payroll Corrections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-11
Terminating a Student From a Position . . . . . . . . . . . . . . . . . . . . . . . 19-11
Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-12
Banner Human Resources Requirements . . . . . . . . . . . . . . . . . . . . . 19-12
Testing of Student Employment Payroll Feed . . . . . . . . . . . . . . . . . . . . 19-13
Accounts Receivable Module . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-14
Setting Up Detail Codes for Financial Aid Disbursement . . . . . . . . . . . . . . 19-15
Setting Up Aid Year, Term, Period for Financial Aid . . . . . . . . . . . . . . . . 19-15
Disbursing Financial Aid Funds . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-15
Running Financial Aid Disbursement Process (Online and Batch) . . . . . . . . . 19-18
Billing and Payments for Financial Aid . . . . . . . . . . . . . . . . . . . . . . . 19-19
Processing Disbursements, Authorizations, and Memos . . . . . . . . . . . . . . 19-20
Billing Parameters and Financial Aid . . . . . . . . . . . . . . . . . . . . . . . . 19-22
Financial Aid Disbursement Process and A/R . . . . . . . . . . . . . . . . . . . 19-23
Campus Loan Manager (CLM) Module . . . . . . . . . . . . . . . . . . . . . . 19-25
Section Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-25
Organization of Material . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Release Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Necessary Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Release Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
CLM components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-26
Banner components. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Functional Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
Banner to CLM Disbursement Feed. . . . . . . . . . . . . . . . . . . . . . . . 19-27
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-27
xxii
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Approach . . . . . . . . . . . . . .
Banner to CLM Enrollment Interface
Background . . . . . . . . . . . . .
Approach . . . . . . . . . . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19-27
. 19-28
. 19-28
. 19-28
CLM to Banner Accounting Feed . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-28
Approach . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Installation and Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-29
Non-OpenVMS Banner . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30
Procedural Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-30
Banner System -- Assign CLM Loan Fund Numbers . . . . . . . . . . . . . . . . 19-31
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31
Setup Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-31
Banner System -- Assign Coding Scheme Translations . . . . . . . . . . . . . . 19-32
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Setup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-32
Banner -- Setup General Ledger . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33
Setup Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-33
CLM System -- Assign Accounting Distribution Rules . . . . . . . . . . . . . . . 19-34
Background . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34
Setup Requirement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-34
General Procedure for the Banner to CLM Disbursement Feed . . . . . . . . . . 19-34
Frequency . .
Involvement .
Prerequisites
Banner . . .
CLM . . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19-34
. 19-34
. 19-34
. 19-35
. 19-35
Banner to CLM Enrollment Interface . . . . . . . . . . . . . . . . . . . . . . . . 19-35
Frequency . .
Involvement .
Prerequisites
Process . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19-35
. 19-36
. 19-36
. 19-36
CLM to Banner Accounting Feed . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37
Frequency . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37
Involvement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37
Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-37
CLM (SunGard Higher Education Plus) Operations . . . . . . . . . . . . . . . . 19-38
Online Operations and Screen formats . . . . . . . . . . . . . . . . . . . . . . 19-38
Banner Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19-39
Online Operations and Screen formats . . . . . . . . . . . . . . . . . . . . . . . 19-39
January 2009
Banner Financial Aid 8.3
User Guide
Contents
xxiii
Fund Management form (RFRMGMT) . .
Class Code Validation form (STVCLAS) .
Ethnic Code Validation form (STVETHN) .
Nation Code Validation form (STVNATN) .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
. 19-39
. 19-40
. 19-40
. 19-40
Banner Batch Operations and Reports . . . . . . . . . . . . . . . . . . . . . 19-43
Banner Enrolled Borrower Verification . . . . . . . . . . (NBA809) . . . . . . . . 19-43
Enrolled Borrower Verification Report Sample . . . . . . . . . . . . . . . . . . 19-44
Banner Finance Accrual Accounting Feed . . . . . . . . (NBB229) . . . . . . . . 19-46
Accrual Accounting Feed Report Sample . . . . . . . . . . . . . . . . . . . . . 19-47
Banner Finance Cash Accounting Feed . . . . . . . . . (NBD029) . . . . . . . . 19-48
Cash Accounting Feed Report Sample . . . . . . . . . . . . . . . . . . . . . . 19-48
LMS Interface Accounting Feed . . . . . . . . . . . . . (RPBLMIA) . . . . . . . 19-50
Accounting Feed Report Sample . . . . . . . . . . . . . . . . . . . . . . . . . 19-52
LMS Interface Disbursement Feed . . . . . . . . . . . . (RPBLMID) . . . . . . . 19-53
RPBLMID Comment Messages: . . . . . . . . . . . . . . . . . . . . . . . . . 19-54
Disbursement Feed Report Sample. . . . . . . . . . . . . . . . . . . . . . . . 19-55
LMS Interface Enrollment Extract . . . . . . . . . . . . (RPBLMIE) . . . . . . . 19-57
Enrollment Extract Report Sample . . . . . . . . . . . . . . . . . . . . . . . . 19-58
Appendix A 2009 - 2010 New Aid Year Checklist
Financial Aid New Year Roll Process (ROPROLL). . . . . . . . . . . . . . . . 4
Common Functions Module (*RESCOMN) . . . . . . . . . . . . . . . . . . . . 9
Data Management Module (*RESDATA) . . . . . . . . . . . . . . . . . . . . . 10
Need Analysis Module (*RESNEED) . . . . . . . . . . . . . . . . . . . . . . . 11
Requirements Tracking Module (*RESTRACK) . . . . . . . . . . . . . . . . . 13
Budgeting Module (*RESBUDG) . . . . . . . . . . . . . . . . . . . . . . . . . 14
Funds Management Module (*RESFUND) . . . . . . . . . . . . . . . . . . . . 16
Packaging And Disbursement Module (*RESPACK) . . . . . . . . . . . . . . 18
Loan Processing Module (*RESLOAN). . . . . . . . . . . . . . . . . . . . . . 23
Electronic Data Exchange (EDE) Module (*RESEDE) . . . . . . . . . . . . . . 24
xxiv
Banner Financial Aid 8.3
User Guide
Contents
January 2009
Student Employment Module (*RESEMPL) . . . . . . . . . . . . . . . . . . . 25
Athletic Module (*RESATHL) . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Schedule A — System Validation and Rules Form Reference . . . . . . . . . 27
Schedule B — Delivered System Required Data . . . . . . . . . . . . . . . . 29
Tables Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Index
January 2009
Banner Financial Aid 8.3
User Guide
Contents
xxv
xxvi
Banner Financial Aid 8.3
User Guide
Contents
January 2009
1
System Overview
This chapter introduces you to Banner Financial Aid. The following is a list of the sections
in this chapter and a brief description of their contents.
• The Application Summary section provides a description of the application and the
problems it resolves. It also describes the application’s place in Banner as well as
identifying database and hardware environments.
• The Functions section describes the key functions of Banner Financial Aid.
• The Module Integration section explains the interaction of Banner Financial Aid
functions.
• The Financial Aid System Process Flow section diagrams the Banner Financial Aid
process.
Application Summary
SunGard Higher Education’s software products assist with the task of resource
management by supporting the integrated flow of information throughout your institution.
The Banner series continues this tradition with Banner Financial Aid.
Handling the daily activities of the financial aid office, Banner performs tracking,
budgeting, need analysis and packaging. Meeting the demands for information, Banner
Financial Aid contains the following integrated components: applicant record creation,
requirements tracking, student budget assignment, need analysis, and packaging. Also
included are funds management, disbursement, award history/transcripts, direct lending,
electronic data exchange (EDE), reporting, loan processing, and return of Title IV fund
information.
Banner Financial Aid places your financial aid office at the forefront of technology
through its use of Oracle®—the advanced relational database management system from
Oracle Corporation and SQL—the standard for database access. By combining this
technology with rule-based architecture and the capability for distributed processing,
Banner creates an information environment that you can tailor to meet your unique
requirements without extensive technical support.
This combination gives you the advantages of an easy-to-use query language and report
writer, and direct access to strategic decision support information.
January 2009
Financial Aid 8.3
User Guide
System Overview
1-1
Functions
Banner Financial Aid performs the following functions via its integrated modules:
• Applicant Processing
• Need Analysis/Verification
• Requirements Tracking
• Budgeting
• Packaging and Disbursement
• Funds Management
• Electronic Data Exchange
• History and Transcripts
• Financial Aid Common Functions
• Student System Shared Data
• Short-Term Credit
• Student Employment
• Loan Processing
• Return of Title IV Funds
All modules can be tailored to your institution by using Banner’s rule-based architecture
to define validation codes and processing rules.
Module Integration
1. Applicant Processing accepts records created through several processes including
ISIR data loads, Pell Electronic Data Exchange, and manual creation through the
Record Creation/Need Analysis forms.
2. Need Analysis/Verification performs calculations that determine the contribution
applicants are expected to make towards their expenses. The verification process
validates certain information provided on an aid application against the same data
from other documents.
3. Requirements Tracking monitors the request for and receipt of certain documents
which are often required so that applications can be fully processed.
4. Budgeting maintains data on the applicant’s cost to attend the institution.
1-2
Financial Aid 8.3
User Guide
System Overview
January 2009
5. Packaging and Disbursements matches an applicant’s need with available funds to
determine an appropriate package for the applicant and records disbursement of the
funds.
6. Funds Management saves data related to financial aid funding sources.
7. Electronic Data Exchange allows institutions to share information electronically with
the central processor and COD.
8. History and Transcripts maintains historical data on the applicant and produces
financial aid transcripts.
9. Financial Aid Common Functions are general functions that support all of the other
financial aid processes.
10. Student System Shared Data shares information with the institution’s Student
Information System (that being the Banner Student or another student system).
11. Short-Term Credit creates and maintains short-term loans.
12. Student Employment establishes job referrals, authorizations, placements, and tracks
compensation limits for students employed by the institution.
13. Loan Processing allows for the creation and processing of loan applications for
Electronic Loans, Direct Loans, or Manual Loans.
14. Return of Title IV Funds assists you in complying with the Title IV regulations for
federal financial aid. Title IV features involve the Accounts Receivable, Student, and
Financial Aid products.
January 2009
Financial Aid 8.3
User Guide
System Overview
1-3
Financial Aid System Process Flow
1
Applicant
Record Creation
2
3
Need Analysis/
Verification
Requirements
Tracking
4
Student System
Shared Data
6
5
Electronic Data
Exchange (EDE)
Process
National Student
Loan Data System
(NSLDS)
9
8
1-4
Budgeting
Packaging/
Disbursements
10
11
Common
Functions
Reporting
Financial Aid 8.3
User Guide
System Overview
7
Funds
Management
12
Student
Employment
January 2009
2
Processing
This section discusses topics and procedures of interest in Financial Aid processing.
Concepts discussed in this chapter include:
• Data Load Procedures
• EDE Procedures
• CSS PROFILE Procedures
• Requirements Tracking Procedures
• Budget Procedures
• Satisfactory Academic Progress (SAP) Procedures
• Funds Management Procedures
• Packaging and Disbursement Procedures
Data Load Procedures
This section discusses the steps you must follow to run the Data Load process.
Understanding Data Load
The Data Load process loads financial aid applicant records into Banner Financial Aid
from external sources via electronic media. This information is stored in temporary Oracle
tables (loaded by the RCBCTxx or RCBTPxx processes), which are then used by the
RCPMTCH (Financial Aid Matching Process) and RCRTPxx (database load process)
programs to complete the Data Load process.
The xx in the last two positions of the program name indicates the aid year for which the
program is designed. The RCBTP09 program, for example, is written specifically for the
2008 - 2009 financial aid year. These programs are year-specific because financial aid
application record formats change annually. The names of the underlying financial aid
tables are not year-specific, however; columns are merely added to these tables as
necessary on a year-to-year basis.
January 2009
Financial Aid 8.3
User Guide
Processing
2-1
Data Load is divided into three mandatory steps:
1. Loading Data into Temporary Tables (through RCBCTxx or RCBTPxx)
2. Performing Match Process (RCPMTCH)
3. Loading Data into Production Database (RCRTPxx)
EDE ISIR Data Load Process Flow
1. Set Up Rule and Validation forms (Annually)
Enter requirement codes and statuses on the Data Source Code Validation form
(RTVINFC) for the EDE source to allow Banner to post documents indicating that a
federal application has been received. Use the Interface Data Translation Rules form
(RCRTPTR) to convert codes on incoming federal application records to valid Banner
values if your school will load all application records. Enter values and rules on
Banner General Common Matching forms used for matching incoming application
records to existing person records in Banner. Establish the matching source and
parameter set on Data Source Rules form (RCRDTSR) for the aid year and data
source used for the processing of individual records from the Financial Aid Suspended
Record Maintenance form (RCRSUSP). Set fields on the Institution Financial Aid
Options form (ROAINST) that control the dataload process or that act as default
values during the load.
2. Prepare Incoming files for Data Load
Use the File Concatenation Process (FILECAT) to combine multiple EDE files
downloaded via the EdConnect software into one file for uploading to Banner.
Note
You cannot use the FILECAT process with files in XML format.
„
Rename the file to the default name that is recognized by Banner processes.
3. Load Records to Temporary Tables (RCBTPxx)
The RCBTPxx process loads incoming EDE ISIR files to a set of temporary tables.
The temporary tables accommodate files for more than one aid year and for more than
one data source.
4. Match Incoming Records to Existing Banner Records (RCPMTCH)
The RCPMTCH process uses the matching rules established on the Banner General
Common Matching forms to compare incoming EDE records to existing General
Person records in the production database. The process identifies New records, those
that have an existing Match, and those that have potential matches or matching errors.
During this process, you may place unmatched New records in a Hold status to prevent
2-2
Financial Aid 8.3
User Guide
Processing
January 2009
them from loading to the production tables until a matching General Person record
exists in Banner.
5. Load Records to Production Database (RCRTPxx)
This step loads New and Matched status records from temporary tables to production
tables and deletes corresponding records from temporary tables. You may run
RCRTPxx in batch, or initiate the load for individual records as the records are
matched, on the Suspended Records Maintenance form (RCRSUSP) (See Step 7).
6. Resolve Records on the Suspended Records Maintenance form (RCRSUSP)
Review each Suspended, Duplicate, and Error record on the RCRSUSP form. Initiate
Common Matching rules to determine whether the record is New or Matched or if
potential matches exist. You may access selected Banner Student processing forms to
assist in suspense resolution. If a match is determined, use the Select ID button in the
Data Load Record Block to update the ID and determine the match status. Select the
Load button to load individual New and Match records to the production tables via the
RCRTPxx process. If applicable, use the online Delete Record feature on RCRSUSP
to remove individual records from the temporary tables.
7. Load Records to Production Database (RCRTPxx))
You must run RCRTPxx again if you did not load files individually after identifying
them as Matched or New on the RCRSUSP form. This loads the files you marked from
temporary tables to production tables and deletes the corresponding records from
temporary tables. This process is run as described in step 5 above.
Note
It is important to run steps 4, 5, 6, and 7 as close together as possible.
This decreases the chance of someone adding new students online,
which would make the New status, as determined by RCPMTCH,
incorrect. If the record is a duplicate, change only one entry to avoid
„
Oracle errors in RCRTPxx.
8. Delete Temporary Suspense Tables (RCRDTMP) (optional)
Use RCPDTMP to delete files from the temporary database tables at the end of a
completed aid year if you used the option to assign a status of Hold to records that did
not have a matching record in the production database. In addition, you can delete
temporary files individually during daily processing from the RCRSUSP form (see
Step 5). You may use the Delete Temporary Records option for immediate deletion, or
set the Delete Record indicator on RCRSUSP and run the RCPDTMP process to
batch delete the selected records.
January 2009
Financial Aid 8.3
User Guide
Processing
2-3
CSS PROFILE Data Load Process Flow
1. Set Up Rule and Validation forms (Annually)
Enter requirement codes and statuses on the Data Source Code Validation form
(RTVINFC) for the CSS source to allow Banner to post documents indicating that a
CSS PROFILE application has been received. Use the Interface Data Translation
Rules form (RCRTPTR) to convert codes on incoming applications to valid Banner
values if your school decides to load all incoming application records. Enter values
and rules on Banner General Common Matching forms used for matching incoming
application records to existing person records in Banner. Establish the matching
source and parameter set on the Data Source Rules form (RCRDTSR) for the aid year
and data source used for the processing of individual records from the Financial Aid
Suspended Record Maintenance form (RCRSUSP). Set fields on the Institution
Financial Aid Options form (ROAINST) that control the data load process or that act
as default values during the data load.
2. Combine Multiple CSS Files Using FILECAT (optional)
Use the File Concatenation Process (FILECAT) to combine multiple CSS files
downloaded from CSS into one file for uploading to Banner.
Note
You cannot use the FILECAT process with files in XML format.
„
Rename the file to the default name that is recognized by Banner processes.
3. Load Records to Temporary Tables (RCBCTxx)
The RCBCTxx process loads incoming CSS PROFILE files to a set of temporary
tables. The temporary tables accommodate files for more than one aid year and for
more than one data source.
4. Match Incoming Records to Existing Banner Records (RCPMTCH)
The RCPMTCH process uses the matching rules established on the Banner General
Common Matching forms to compare incoming CSS PROFILE records to existing
General Person records in the production database. The process identifies New
records, those that have an existing Match, and those that have potential matches or
matching errors. During this process, you may place unmatched New records in a
Hold status to prevent them from loading to the production tables until a matching
General Person record exists in Banner.
5. Load Records to Production Database (RCRTPxx)
This step loads New and Matched status records from temporary tables to production
tables and deletes corresponding records from temporary tables. You may run
RCRTPxx in batch, or initiate the load for individual records as the records are
matched, on the Suspended Records Maintenance form (RCRSUSP) (see Step 7).
2-4
Financial Aid 8.3
User Guide
Processing
January 2009
6. Resolve Records on the Suspended Records Maintenance form (RCRSUSP)
Review each Suspended, Duplicate, and Error record on the RCRSUSP form. Initiate
Common Matching rules to determine whether the record is New or Matched or if
potential matches exist. You may access selected Banner Student processing forms to
assist in suspense resolution. If a match is determined, use the Select ID button in the
Data Load Record Block to update the ID and determine the match status. Select the
Load button to load individual New and Match records to the production tables via the
RCRTPxx process. If applicable, use the online Delete Record feature on RCRSUSP
to remove individual records from the temporary tables.
7. Load Records to Production Database using RCRTPxx
You must run RCRTPxx again if you did not load files individually after identifying
them as Matched or New on the RCRSUSP form. This loads the files you marked from
temporary tables to production tables and deletes the corresponding records from
temporary tables. This process is run as described in step 5 above.
Note
It is important to run steps 4, 5, 6, and 7 as close together as possible.
This decreases the chance of someone adding new students online,
which would make the New status, as determined by RCPMTCH,
incorrect. If the record is a duplicate, change only one entry to avoid
„
Oracle errors in RCRTPxx.
8. Delete Temporary Suspense Tables (RCRDTMP) (optional)
Use RCPDTMP to delete files from the temporary database tables at the end of a
completed aid year if you used the option to assign a status of Hold to records that did
not have a matching record in the production database. In addition, you can delete
temporary files individually during daily processing from the RCRSUSP form (see
Step 5). You may use the Delete Temporary Records option for immediate deletion, or
set the Delete Record indicator on RCRSUSP and run the RCPDTMP process to
batch delete the selected records.
Setting Up Rule and Validation forms for Data Load
Step 1
Build the Interface Data Code Validation form (RTVINFC)
The Interface Data Block is not aid year-specific. Select the Source Code (such as EDE or
CSS) and enter a tracking requirement code in the Code Requirements field. Banner uses
this value to update the student’s tracking requirement record when the first application
record for that source is loaded into Banner. You can enter a second requirement (such as
an institutional application) in the Supplemental Requirements field. Enter the tracking
requirement status that you want to post with the tracking requirement in the Status
Requirements field.
January 2009
Financial Aid 8.3
User Guide
Processing
2-5
You must populate the Recruiting Source and Contact Type fields. This data is required
for Part 3 of Data Load (RCRTPxx) to complete successfully, even though you may not
create recruiting records. If you create recruiting records with RCRTPxx, the Recruit
Prospect form (SRARECR) is populated.
The Aid Year Specific Rules Block is optional. If your tracking requirement is different
each year, you may enter an Aid Year Code for each year and source combination you
want to define. Associate an aid-year-specific tracking requirement with each entry. If you
choose to enter aid-year specific requirements, the tracking entries on the Interface Data
Block are ignored.
Step 2
Build the Interface Data Translation Rules form (RCRTPTR).
This form allows you to convert specified data values in the temporary tables to
institutional values during Data Load. The four tables that are recognized by Banner are
MRTL (Marital), MAJR (Major), SBGI (prior schools attended), and CITZ (Citizenship). Data
Load processing requires MRTL, MAJR, and SBGI Table Name, Data Value, and Converted
Code field entries. CITZ is an optional entry. The form is completed for each application
Source Code (EDE, CSS) in use at your school.
Data Value is the value for the field that comes in from the Data Load file. The
Converted Code field contains the desired value you want the incoming data to be when
posted to Banner. The Converted Code must match values already defined in a
corresponding Banner validation table. Description automatically populates when you
enter the converted code.
When the incoming data field contains a blank value, enter an asterisk (*) in the Data
Value field with its associated Converted Code value. If a data value exists, but is not
listed in the corresponding validation form, or if you choose to convert all data to one
value, you must enter the word Default in the Data Value field for its associated
Converted Code value.
When building this form, there must be a minimum of two entries for each MAJR, and
SBGI. These two values are an asterisk (*) and the word Default in the Data Value field.
Even though students do not provide data for major or prior schools attended on the
FAFSA, or the CSS PROFILE, Banner Data Load still requires at least the default and (*)
entries for the MAJR and SBGI tables. A Default entry is not required for the MRTL or CITZ
tables.
Sample EDE record data values are as follows.
2-6
Table Name
Data Value
Converted Value
MAJR
*
Value for undeclared major - STVMAJR
MAJR
DEFAULT
Value for undeclared major - STVMAJR
Financial Aid 8.3
User Guide
Processing
January 2009
Table Name
Data Value
Converted Value
MRTL
*
Value for single - STVMRTL
MRTL
1
Value for single - STVMRTL
MRTL
2
Value for married - STVMRTL
MRTL
3
Value for single or separated - STVMRTL
SBGI
*
Institution’s School Code - STVSBGI
SBGI
DEFAULT
Institution’s School Code - STVSBGI
CITZ
*
Value for U.S. Citizen – STVCITZ
CITZ
1
Value for U.S. Citizen - STVCITZ
CITZ
2
Value for U.S. Citizen - STVCITZ
CITZ
3
Value for Non-Citizen - STVCITZ
Step 3
Build the Institution Financial Aid Options form (ROAINST).
Codes in various fields on this form serve as global controls for the dataload process, or
are used as defaults, as application records are loaded. You must define the following
fields in this step: Start Date and Year, End Date and Year, Primary Application
Source, Application Received Date Indicator, Tracking Established Status, Source
for Application Received Date (if you load both EDE ISIR and CSS Profile records)
Default Aid Period, Current Term Code, Initial SAP Code, Update Transaction
Number and EFC, Use EFC Proration, and the Application Source Codes on the
Defaults window (if you load CSS Profile records).
Step 4
Build the User Defined Variables Description form (RORUSER).
Note
This step is optional and is for CSS PROFILE only.
„
If you contract with CSS for students to complete optional questions on the PROFILE
application, you may load up to 30 responses to User Defined fields for the student. Select
a range of fields on the RORUSER form. Enter the CSS Profile question number and a
description for each question that students will complete. Once the data is loaded, you can
view the results on the Applicant User Defined Data form (ROAUSDF).
Step 5 Define the Common Matching Source Code Validation form
(GTVCMSC)
Enter a Matching Source code (name) and a Description on the Common Matching
Source Code Validation form (GTVCMSC) for the set of rules that you want to use when
January 2009
Financial Aid 8.3
User Guide
Processing
2-7
matching the records for an application data source during Data Load, Part 2 (RCPMTCH)
and during online matching when resolving suspended records. You may define a common
matching source code for each data source (EDE, CSS), or you may choose to define one
common matching source code for all data sources. Each data source code can have
multiple rules that determine if the record already exists in the database.
Step 6
Build the Common Matching Source Rules form (GORCMSC)
Set up default information for a Matching Source code on the Common Matching Source
Rules form (GORCMSC).
Select the Person value for the Match Type field to match against person records in
Banner.
Specify forms in the Option Display Rules Block to which the user can navigate using the
Details button on the Common Matching Entry form (GOAMTCH) in order to see more
detailed information about possible matched records.
Note
The Use for Online Common Matching, Default Address Type,
Default Telephone Type, and Default E-mail Type fields on the
GORCMSC form are applicable to a Common Matching Source Code that
will be used for creating records on the various %IDEN forms such as
SPAIDEN; they are NOT applicable to a Common Matching Source Code
that will be used to match records from the RCRSUSP form after a
Financial Aid Data Load. If you elect to create person records for new
applicants or to update existing person records during Data Load, Banner
will use only the Address, Telephone, and E-mail types defined in the
„
parameters of Data Load Part 1 (RCBTPxx or RCBCTxx).
Step 7
Build the Common Matching Rules form (GORCMRL)
Create rules for your Common Matching Source Codes on the Common Matching Rules
form (GORCMRL) and give each rule a priority. Banner accesses your rules in priority
order. If the Priority 1 rule finds a match, or finds no potential matches, the record is
matched or new respectively and processing stops. If the Priority 1 rule finds potential
matches, the procedure goes to the next priority and executes the rule to attempt to find
matched records. For this reason, the Priority 1 rule should have the most restrictive
criteria.
Select the Create Required Rules button to use default data elements (elements marked as
required for matching by checking the Required Element field on the Common Matching
Data Dictionary form (GORCMDD)). The GORCMDD form is populated and delivered
by SunGard Higher Education. The only data element delivered as a required element is
SPRIDEN_SEARCH_LAST_NAME.
Select additional data elements to use in matching by using the Column List of Values
from the GORCMDD data element listing that will make up each rule.
2-8
Financial Aid 8.3
User Guide
Processing
January 2009
In the Length field, indicate the number of characters to compare during the matching
process (for fields not defined as a code in Banner). If the Allow Negative Length field is
checked for a selected data element on the Common Matching Data Dictionary form
(GORCMDD), you may enter a negative number for comparison. For example, enter 10 to
read the first ten characters of the Last Name; enter –4 to read the last four characters of
the Social Security Number.
Indicate the value you want to apply to the data element during Common Matching in the
Data Required field. Select Required if the specified data must be present in both Banner
and the incoming record. If the data element is present in both locations and matches the
length requirement for that element, Banner perceives this as a match. Select Exists if the
data may be null in either the database or the incoming record. If you use Exists, and the
specified data field is null in either location, that data element is considered as a match
(i.e., the SSN is null in Banner and the SSN is not null in the data load tables).
The algorithm that controls Common Matching uses a combination of primary and
secondary matches (see the complete algorithm in the Additional Data Load Topics
section below). SunGard Higher Education suggests you use the Social Security Number
along with other criteria, such as birth day and an item from the address, in your rules to
achieve optimum matches. Also, you should test your choice of Required and Exists
statuses. A simple rule that uses only Last Name – Required (Required Element for the
rule) and SSN – Exists could find an incorrect student. The primary match on Last Name
would find the student, and SSN would be considered a match if the SSN is null in Banner
but not null in the incoming data load record.
This form allows you to copy previously created rules in the Copy Rules To window. You
also may add specific matching procedures for matching components that are not within
Banner General tables (i.e., matching on high school data for Banner Student) in the
Matching Procedures window.
Step 8
Build the Name Translation Rules form (GORNAME) — Optional
Use the GORNAME form to build common translations between the first and middle
names you receive in Data Load files and the first and middle names stored in the Banner
General Person record (SPRIDEN). The RCPMTCH routine uses entries on this form to
assist in the matching of the first and middles names on records in the temporary tables. If
the normal match routine comes up with a first name mismatch, the process goes to the
GORNAME rules to attempt a match. If there is an exact match between the primary
columns on this form, the match exists and this record passes the first name match
requirement. If there is no record present on this form that exactly matches the first name
in the temporary tables, there is no match and the record fails the first name match. The
listing also is used when the Common Matching process is started from the RCRSUSP
form.
Some first name translations are delivered with Banner. You may enter additional
translations. See the examples below.
January 2009
Financial Aid 8.3
User Guide
Processing
2-9
Bob
Robert
Harold
Hal
Rebecca
Becky
Note
The translations work both ways. You do not need to create one record
associating, for example, William with Will and a second record
associating Will with William. One record with the combination will suffice.„
Step 9
Create a Parameter Set for Online Data Load Part 3 (RCRTPxx)
Note
If you are processing both EDE and CSS records, you must define a
parameter set for each data source.
„
Build a default parameter set for each application data source (EDE, CSS) to control Data
Load Part 3 (RCRTPxx) when you run the process online from the Financial Aid
Suspended Records Maintenance form (RCRSUSP).
On the Job Parameter Set Rule form (GJRJPRM), enter RCRTPxx in the Process field.
Define a parameter set name that includes the application data source name (i.e.,
0506_EDE_RCRTPxx, 0506_CSS_RCRTPxx) in the Parameter Set field and enter a
Description.
Access the Default Parameter Value Validation form (GJAPDFT). Enter RCRTPxx in the
Process field and the saved parameter set name created on the Job Parameter Set Rules
form (GJRJPRM) in the Parameter field. Create user-defined values appropriate for the
data source for all required parameters. After the annual parameter set is created for a data
source, each user who has permission to load records to Banner from RCRSUSP must
copy the parameter set to his/her own user name. Use the copy feature on the GJAPDFT
form for this purpose. Banner validates the User ID, parameter set name, and job when
RCRTPxx is run from RCRSUSP.
Step 10
Build the Data Source Rules form (RCRDTSR)
Use this form to establish the Common Matching Source Code and RCRTPxx parameter
set to use when you process records from the Financial Aid Suspended Record
Maintenance form (RCRSUSP). You need to create an entry for each application Source
Code (EDE, CSS) at your school. Enter the Aid Year, application Source Code (EDE or
CSS), Common Matching Source Code, and the saved Parameter Set name for Data
Load Part 3 (RCRTPxx). You may use the same Common Matching Source Code rule
set for each entry, but you must have separate parameter sets saved if your schools loads
both EDE and CSS records.
2-10
Financial Aid 8.3
User Guide
Processing
January 2009
Preparing the Data to Load into Banner
Incoming application files from all sources must be loaded to the $DATA_HOME/finaid
directory for Unix or DATA$HOME for VMS, or BANNER_FINAID_DATA_HOME for NT.
The incoming file must be renamed to match what the processes are expecting. This
step must be completed every time there is a new input file to load to Banner.
Input names for the RCBTPxx (EDE ISIR) and RCBCTxx (CSS PROFILE) processes
are shown below. The xxyy in each filename represents the aid year for which the load
is performed.
Default File Names
For Financial Aid EDE Data Load, Part 1 (RCBTPxx), the default filename is:
Input File
Filename
EDE ISIR
xxyyesar.tap
For Financial Aid CSS DataLoad, Part 1 (RCBCTxx), the default filename is:
Input File
Filename
CSS PROFILE
xxyycssd.tap
Once you complete Data Load, you may want to save the input file under some other name
and archive it. This way, the next time a file is loaded, it will not overwrite your previous
input file.
File Concatenation Process (FILECAT)
You can use the File Concatenation Process (FILECAT) for Data Load files. You can view
the complete list of files that you concatenate with this process in the Reports and
Processes Chapter. You cannot use FILECAT with XML formatted files.
FILECAT combines multiple ISIR files downloaded via the federal software into one file
(per processing year) for uploading to the Banner environment. The following is an
overview of the installation and usage of FILECAT.
Copy the file filecat.exe from the filecat directory of the release CD to the directory
where files downloaded via the federal software reside. This may be any directory you
choose.
Warning
Do not rename the files that are downloaded via the federal software.
January 2009
„
Financial Aid 8.3
User Guide
Processing
2-11
Start the program by typing filecat at the DOS prompt in the directory where you installed
the utility. Enter the names of the ISIR files you want to add to the xxxxESAR.tap (for
example, where xxxx = 0809) file to be uploaded to Banner. You may process as many
ISIR files as you wish.Filecat syntax is:
filecat -i file1 [file2...fileN] [-e ext] [-o outfile] [-v] [-a]
where:
• -i list of input files (wildcards are allowed)
• -e extension of file to be output first
• -o output file name (default is filecat.out)
• -v enable verbose output mode
• -a append rows to output file instead of overwriting
You can type filecat without parameters to get detailed instructions for its use.
Warning
When using the -i parameter, the list of files to concatenate should be
separated by a space, not a comma.
If you double click the file from Windows Explorer or Run it from the
windows Start Menu, the text displays too briefly for it to be read. If the
program is not run from within a DOS window, you will not see the output
messages generated by the program.
If you run the program from the Windows Start Menu and include
command line parameters, it will probably run successfully. However, you
will not see any output messages, so you will not know if the run was
„
successful.
FILECAT permits any input filenames (including the * wildcard -- for example, Sara*).
You can create any output filename, though the output filename defaults to filecat.out if
not specified. Use the -a parameter to append new files to an existing file; otherwise, it
creates or overwrites the specified output filename.
If you use the -a parameter and the output file does not already exist, you receive an
appropriate error message. The process determines the record length of the output file
from the first input file it encounters, matching the input filename mask. If subsequent
files have a different record length, it displays an error message and quits.
For example, if you specify filecat -i 0001* as the input file(s), and 0001cssd.dat and
0001esar.dat both exist in the directory, an error message displays when you hit the
0001esar.dat file because its length differs from 0001cssd.dat. Conversely, if you use
filecat -i 0000e* and 0001esar.dat, 0001esar.001, 0001esar.002, 0001esar.003 all exist in
the directory, all four files concatenate into the output file.
2-12
Financial Aid 8.3
User Guide
Processing
January 2009
Each time you run the process, a new subdirectory is created and all processed files are
moved into it. This prevents you from accidently reloading the same file. The format of
the subdirectory name is \processed_cyymmddhh24miss. The output file remains in the
original tapedata directory.
For example:
1. filecat - i 0001esar*
Since the -o filename was not specified, it defaulted to filecat.out file. It moved
processed files to processed_19991220103501.
2. filecat -i ytdo01op.* -o filecat.out -a
Appended to current data in filecat.out.
3. filecat -i ytdo01op.* -a
Appended to current default file (filecat.out). If the data should be appended to
another file, you will need to specify with the -o filename.
4. filecat -i 0001cssd* -o csstape.tap
This creates a new output file of 001cssd.tap.
5. filecat -i ytdo010p* -o filecat.out.
This overwrites the existing data in filecat.out file.
Warning
You must exercise care in determining which ISIR files are to be added to
the output file (filecat.out) xxxxESAR.tap. Be sure that only files that have
„
not been previously uploaded to Banner are added to the file.
After the xxxxESAR.tap file is created, transfer this file to your Data Load directory in
Banner by using an option in your transfer utility (for example, FTP) that will not change
the original file structure.
Running the Data Load Process
This section covers each step of the dataload process. It includes explanations of process
parameters and a discussion of each operation.
Step 1
Run the Financial Aid EDE Data Load Part 1 Process (RCBTPxx).
The Financial Aid EDE Data Load Part 1 (RCBTPxx) process for Federal data (EDE)
records and the Financial Aid CSS Data Load Part 1 (RCBCTxx) process for CSS Profile
data records load incoming files to temporary tables. These temporary tables, which are
January 2009
Financial Aid 8.3
User Guide
Processing
2-13
duplicates of the Oracle tables where the production data is stored, contain fields that
convert data from the flat-file format to the Oracle format when discrepancies exist.
For example, a temporary person file name is ROTPERS, while the actual table name is
SPBPERS. The temporary table contains the exact fields of the actual table plus fields that
are needed to convert the birth date to the proper format.
The data in some of these temporary tables is then compared against the data in the
production database to ensure that the information can be loaded to the correct person if
they already exist in the database, or to create a new person if the student does not yet have
a record at the institution. This is Step 2, Performing the Match Process.
Note
A listing of the temporary tables is included in the Additional Data Load
„
Topics section below.
The RCBTPxx parameters are:
Parameter
Value
01
Aid Year Code
Appropriate Aid Year Code for RCBTPxx version
02
Data Source Code
EDE only
03
Data Delivery Method
E
Electronic or Diskette only
04
Generated ID/
Use SSN Indicator
G
Generated ID
S
Use SSN as ID (Default)
Recalculate Need
Indicator
Y
Recalculate Need (Default)
N
Don’t Recalculate Need
06
Address Type Code
Valid Address Type Code as listed on the STVATYP
form
07
Telephone Type Code
Valid Telephone Type Code as listed on the STVTELE
form
08
Starting Record
Number
Record number for the restart process (Default = 0)
09
Email Address
Type Code
Email Type Code as listed on the GTVEMAL form
05
Explanations of selected RCBTPxx parameters follow:
2-14
Financial Aid 8.3
User Guide
Processing
January 2009
04
Generated ID/
Use SSN Indicator
G
Generated ID
S
Use SSN as ID (Default)
The Generate ID/Use SSN Indicator enables Banner to generate an ID for a new person, or
use the SSN (social security number) as the ID. When this parameter is set to S, the
Student ID will be created using SSN; when this value is G, the RCBTPxx process will
assign a temporary generated ID to each record loaded to the temporary tables. The
temporary ID becomes permanent for students loaded as New. The temporary ID is
replaced with the generated ID in the Banner database if a match is achieved with an
existing record.
05
Recalculate Need
Indicator
Y
Recalculate Need (Default)
N
Don’t Recalculate Need
When this parameter is set to Y, all applicant records will be created with their Recalculate
Need Indicator set to Y, indicating that need will be recalculated the next time you run the
batch Need Analysis process after the records have been loaded.
Note
If a school chooses to set the Parameter 05 Recalculate Need Indicator to
N, the federal student Need Analysis record will reflect the information
imported on the ISIR with no changes. Schools that load federal ISIR and
CSS Profile records should set Parameter 05 to Y to flag the records for a
Needs Analysis calculation. This will produce a Need Analysis Report
with both the ISIR and PROFILE information listed for each student.
(Review set up of INAS Global Policy Options.) Schools that choose to
run the Needs Analysis calculation in batch should review CSS INAS
documentation carefully to understand differences in assumptions when a
„
recalculation is done.
To run the RCBTPxx process, access the Process Parameter Entry form (GJAPCTL) and
enter the required parameters. You can proceed in one of two ways:
1. Select the Submit radio button in the Submission Block and select the Save button to
submit the job, or
2. Select the Hold radio button in the Submission Block and press the Save button to
hold the job. Note the sequence number. If you select the Hold option, you must have
access to the job submission directory to complete job processing.
Note
As a general rule, you should confirm that each Data Load process is
complete before running the next process.
January 2009
„
Financial Aid 8.3
User Guide
Processing
2-15
Note
When inserting the name into the temporary table (ROTIDEN), the
following prefixes and suffixes are removed to assist with the matching
„
process.
• Specific prefixes are: Dr., Dr, Mr., Mr, Miss, Ms., Ms, Mrs., Mrs,
Prof., Prof.
• Specific suffixes are: Jr., Jr, Sr., Sr, III, IV, Ph.D, PhD, CPA, MD,
RN, Esq., Esq, DVM.
Step 2
Run Financial Aid CSS Data Load Part 1 (RCBCTxx)
The Financial Aid CSS Data Load Part 1 (RCBCTxx) process takes incoming CSS
PROFILE data and loads it to the temporary tables. This data is then available for use by
the remaining steps of the Data Load process.
RCBCTxx parameters (CSS PROFILE data only) include:
Parameter
Value
01
Aid Year Code
Appropriate Aid Year Code for RCBCTxx version
02
Data Source for CSS
CSS only
03
Data Delivery Method
D
Electronic or Diskette only
04
Generated ID/
Use SSN Indicator
G
Generated ID
S
Use SSN as ID (Default)
Recalculate Need
Indicator
Y
Recalculate Need (Default)
N
Don’t Recalculate Need
06
Address Type Code
Valid Address Type Code as listed on the STVATYP
form
07
Telephone Type Code
Valid Telephone Type Code as listed on the STVTELE
form
08
Starting Record
Number
Record number for the restart process (Default = 0)
09
Email Address
Type Code
Email Type Code as listed on the GTVEMAL form
05
Explanations of selected RCBCTxx parameters follow:
2-16
Financial Aid 8.3
User Guide
Processing
January 2009
04
Generated ID/
Use SSN Indicator
G
Generated ID
S
Use SSN as ID (Default)
The Generate ID/Use SSN Indicator enables Banner to generate an ID for a new person, or
use the SSN (social security number) as the ID. When this parameter is set to S, the
Student ID will be created using SSN; when this value is G, the RCBCTxx process will
assign a temporary generated ID to each record loaded to the temporary tables. The
temporary ID becomes permanent for students loaded as New. The temporary ID is
replaced with the generated ID in the Banner database if a match is achieved with an
existing record.
05
Recalculate Need
Indicator
Y
Recalculate Need (Default)
N
Don’t Recalculate Need
When this parameter is set to Y, all applicant records will be created with their Recalculate
Need Indicator set to Y, indicating that need will be recalculated the next time you run the
batch Need Analysis process after the records have been loaded.
Note
If a school chooses to set the Parameter 05 Recalculate Need Indicator to
N, the federal student Need Analysis record will reflect the information
imported on the ISIR with no changes. Schools that load federal ISIR and
CSS Profile records should set Parameter 05 to Y to flag the records for a
Needs Analysis calculation. This will produce a Need Analysis Report
with both the ISIR and PROFILE information listed for each student.
(Review set up of INAS Global Policy Options.) Schools that choose to
run the Needs Analysis calculation in batch should review INAS
documentation carefully to understand differences in assumptions when a
„
recalculation is done.
January 2009
Financial Aid 8.3
User Guide
Processing
2-17
To run the RCBCTxx process, access the Process Parameter Entry form (GJAPCTL) and
enter the required parameters. You can proceed in one of two ways:
1. Select the Submit radio button in the Submission Block and select the Save button to
submit the job, or
2. Select the Hold radio button in the Submission Block and press the Save button to
hold the job. Note the sequence number. If you select the Hold option, you must have
access to the job submission directory to complete job processing.
Note
As a general rule, you should confirm that each Data Load process is
complete before running the next process.
„
Note
When inserting the name into the temporary table (ROTIDEN), the
following prefixes and suffixes are removed to assist with the matching
„
process.
• Specific prefixes are: Dr., Dr, Mr., Mr, Miss, Ms., Ms, Mrs., Mrs,
Prof., Prof.
• Specific suffixes are: Jr., Jr, Sr., Sr, III, IV, Ph.D, PhD, CPA, MD,
RN, Esq., Esq, DVM.
Step 3
Run the Financial Aid Dataload Part 2 Process (RCPMTCH)
Note
Before running this step, verify that you have created matching rules on
„
the Common Matching Rules form (GORCMRL).
The RCPMTCH process is the matching step of Data Load. RCPMTCH performs a
comparison between the student data in the temporary tables (ROTIDEN, ROTPERS,
ROTADDR, ROTEMAL) and student person (General Person) data that already exists in the
database. RCPMTCH follows matching rules set up on the Common Matching Rules form
(GORCMRL) for the Data Source Code that you enter for the RCPMTCH Common
Matching Source Code (parameter 06).
As part of the matching process, all non-code fields used in matching are changed to upper
case, compressed to remove all spaces, and all special characters are removed. This occurs
with both the data in the Financial Aid temporary tables as well as the data in Banner.
You also can use the Name Translation Rules form (GORNAME) for matching situations
such as Bob – Robert. This process uses the name search fields to determine if a student is
new, or if the student truly exists on the database with the name entered in a slightly
different manner each time.
The result of this process is a status code that is posted to each student record in the
temporary tables. The status code assigned to a record determines whether this record is
2-18
Financial Aid 8.3
User Guide
Processing
January 2009
ready to be loaded directly to the database, needs manual review and intervention, or is in
a hold status.
Below is a listing of all status codes used and their definitions. Each record in the
temporary ID table (ROTIDEN) is updated with one of the following statuses:
Status
Comment
D
Duplicate. This name and/or ID has a match within the temporary file
indicating multiple records for the same person.
E
Error. This record encountered an error that would prohibit a determination
of a New or Matched status. See the Error listing below for information.
M
Matched. Based on the rules defined for the Common Matching Source
Code, this record matches a record on the production table database and has
a Need Analysis record for the aid year being processed.
N/H
New. No match was found for this record. It is a new person. If a school
chooses to define new students with a status of Hold, then the new student
will not be processed in step 3 (RCRTPxx) until the status is changed.
R
Matched student. Based on the rules defined for the Common Matching
Source Code, this record matches a record on the production table database
but no Financial Aid record (RORSTAT) exists for the current year.
A
Matched student. Based on the rules defined for the Common Matching
Source Code, this record matches a record on the production table database
with a Financial Aid record (RORSTAT) for the current year, but no Need
Analysis record (RCRAPP1) for the current year.
S
Suspend. This indicates at least one record where some of the fields match
the record being entered, but not all, or there is more than one record that
matches all the rules. A record will also be Suspended with an error code if
determined as new but the ID or SSN exists in the production database.
*
This is a database problem and must be corrected for the problem student
before attempting to process this student in Step 3 (RCRTPxx).
Warning
The RCRTPxx program that follows RCPMTCH only processes records
with a status of N, M, A, or R. Records with other statuses stay in the
temporary files until deleted using RCPDTMP, or until the statuses are
manually changed using the RCRSUSP form and you rerun the
RCRTPxx Process. Statuses that you have updated during RCRSUSP
record resolution can be changed if the RCPMTCH process is run again
before records resolved on RCRSUSP are loaded to the permanent
„
tables using RCRTPxx.
January 2009
Financial Aid 8.3
User Guide
Processing
2-19
The RCPMTCH parameters are:
Parameter
Value
01
Aid Year Code
Appropriate aid year
02
Data Source Code
Valid Source Code on the RTVINFC form
03
Generate ID/Use SSN
Indicator
G
Generate IDS Use SSN as ID (Default)
04
Value for New Students
N
New
H
Hold
I
Sort by IDN Sort by Name (Default)
T
Sort By Temporary PIDM
05
06
Sort Order Indicator
Common Matching Source
Code
Valid Source Code on the GTVCMSC form
Explanations of selected RCPMTCH parameters follow:
04
Value for New Students
N
New
H
Hold
This is the status code that is posted to all students who do not appear to match anyone in
the production database. Part 3 of the Data Load process loads all students with a status
code of N, but Data Load does not load students with a status code of H. This option is
available for those institutions that do not desire to have the Data Load process create new
students (person records) in the production database. Records with a status of H (Hold)
remain in the temporary tables until the records match a person record in the database and
their status is updated appropriately, or until the delete from temporary tables process is
run (RCPDTMP) in batch or for the individual record.
06
Common Matching Source
Code
Valid Source Code on the GTVCMSC form
Banner starts the Common Matching Application Programming Interface (API) using the
rules defined for the Common Matching Source Code entered for this parameter.
To run the RCPMTCH process, access the Process Submission Controls form (GJAPCTL)
and enter the required parameters.
2-20
Financial Aid 8.3
User Guide
Processing
January 2009
You can proceed in one of two ways:
1. Select the Submit radio button in the Submission Block and select the Save button to
submit the job, or
2. Select the Hold radio button in the Submission Block and press the Save button to
hold the job. Note the sequence number. If you select the Hold option, you must have
access to the job submission directory to complete job processing. Banner prompts
you for a User ID, a password, and the previously mentioned sequence number (the
job submission one-up number).
This job produces an rcpmtch_seqno.lis file. Print this file to capture the results of the
process. This file contains five reports:
• Financial Aid Data Load Matching Process - Parameters. This report lists the job
submission parameters used to run the job. The Common Matching Source Code
• Data Load Match Process – All Records. All records in the temporary tables for the
aid year and Data Source will be listed with the status returned from the matching
procedure (status E = Error, D = Duplicate, M = Match-M, A = Match-A, R =
Match-R, * = Dup PIDMs, S = Suspense, N = New, H = New-Hold), the rule
priority if matched, the error code if an error was encountered, and a message
regarding the status.
• Data Load Match Process - Duplicate Record. This report lists all people appearing
on the temporary tables two or more times. Note that this report is the only report
for all data source codes (see RTVINFC). Other reports are only for the data source
code (infc code) selected in parameter number two of this job.
• Data Load Match Process – Summary of Totals. This report lists Data Load
matching process totals by status and error code. Valid error messages that appear
on this report are listed below.
• Data Load Match Process - Control Summary.This report lists the parameters, job
number, report file name, and the number of pages.
Valid error messages that appear on the Data Load Match Process – Summary of Totals
report are:
January 2009
Error
Description
13
ID and SSN not equal
21
ID or SSN is null
22
Last name or First name is null and SSN is null
23
City is null
Financial Aid 8.3
User Guide
Processing
2-21
Error
Description
25
SSN exists on temporary tables 2 or more times
26
ID exists multiple times
27
ID exists in the database
28
SSN exists in the database
29
Missing Last Name
30
Missing First Name
The RCPMTCH process also creates an rcpmtch_seqno.log file.This log file contains
information that will be helpful to the technical staff if a problem running this process is
encountered.
Once the matching process is complete, the data for those students that the process has
determined are either a match, or new students, must be loaded to the production database.
This is Data Load, Part 3 (RCRTPxx).
Step 4
Run Data Load, Part 3 (RCRTPxx)
This step loads applicant information from temporary tables to permanent tables, creates
person records for New student records, and completes the necessary conversions using
the codes established in the RCRTPTR form.
Note
RCRTPxx loads all records designated as New or Matched by
RCPMTCH. The process also loads all records designated by you as
New or Matched on the RCRSUSP form.
It is important to run the RCPMTCH and RCRTPxx steps as close
together as possible. This decreases the chance of someone adding new
students online, which would make the New status, as determined by
„
RCPMTCH, incorrect.
2-22
Financial Aid 8.3
User Guide
Processing
January 2009
RCRTPxx process parameters include:
Parameter
Value
01
Aid Year Code
Appropriate Aid Year for RCRTPxx version.
02
Data Source Code
Valid Data Source Code on the RTVINFC form.
03
Load Option for Need
Analysis
1.
Load all as current.
2.
If first record from primary MDE, load as
current record, else load as non-current record
3.
If first record from primary MDE, load as
current, else do not load
4.
Load as non-current record
5.
Do not load records, but print discrepancy
report
6.
Replace existing CSS PROFILE record
7.
Do not replace existing CSS PROFILE record
Y
Print Discrepancy Report to report changes in
NSLDS summary data
N
Do not print the NSLDS Discrepancy Report
04
Not used at this time
05
NSLDS Print Option
06
07
Need Analysis Print Option Y
Print Need Analysis Discrepancy Report
N
Do not print Need Analysis Discrepancy
Report
Y
Create Banner Student Recruiting records
N
Do not create Banner Student Recruiting
records
Recruiting Option
Note: The Major field on the STVMAJR form must
be checked for the converted major code in the
Converted Value field on the RCRTPTR form in
order to be considered a valid major. A valid
major is necessary if you want to create
recruitment records using this parameter.
08
January 2009
Recalc Need Analysis
Option
Y
Set Recalc Need Analysis indicator to Y
N
Set Recalc Need Analysis indicator to N
Financial Aid 8.3
User Guide
Processing
2-23
Parameter
Value
09
NSLDS Output Application General area for which the Selection ID was
ID
defined for NSLDS output
10
NSLDS Output Selection
ID
Code that identifies the sub-population to be
updated by NSLDS
11
NSLDS Output Creator ID
ID of the person who created the sub-population
rules for NSLDS
12
ISIR Creation Option
Y
Create ISIR records
N
Do not create ISIR records
Load VA Data to Resource
Table
Y
Load VA Data to Resource Table
N
Don’t Load VA Data
Process Indicator
B
Process Batch
O
Process Online
13
14
15
Temporary PIDM
Blank when running in batch
16
Update Postal Address
Y
Update Postal Address
N
Don’t Update Postal Address
Y
Update Telephone Number
N
Don’t Update Telephone Number
Y
Update E-mail Address
N
Don’t Up-date E-mail Address
Y
Update Social Security Number
N
Don’t Update SS Number
17
18
19
Update Telephone Number
Update E-mail address
Update Social Security
Number
Explanations of selected RCRTPxx parameters follow:
2-24
Financial Aid 8.3
User Guide
Processing
January 2009
03
Load Option for Need
Analysis
1.
Load all as current.
2.
If first record from primary MDE, load as
current record, else load as non-current record
3.
If first record from primary MDE, load as
current, else do not load
4.
Load as non-current record
5.
Do not load records, but print discrepancy
report
6.
Replace existing CSS PROFILE record
7.
Do not replace existing CSS PROFILE record
Note
Data Load options 6 and 7 are the only valid options if you enter CSS
PROFILE for the Data Source Code parameter.
„
Students without current application records for this year - the status is N (New), R (match
found, but no RORSTAT record for the current year), or A (match found, but no RCRAPP1
record for the current year) - are loaded as current application records, regardless of the
load option.
Students with a locked Need Analysis record are loaded as non-current, regardless of the
load option that you select.
All new ISIR records with accompanying NSLDS data contain an NSLDS Transaction
Number. If the Transaction Number on the new NSLDS/ISIR record is greater than the
NSLDS Transaction Number of the Current NSLDS record in Banner, the process loads
the new NSLDS record as the Current NSLDS record and changes the Current record
indicator on the previous Current record to Non-current. No NSLDS records are ever
loaded as non-current. The records are either loaded as current or not at all.
You can print a Discrepancy Report for options 1 - 5, provided that you enter a Y value for
the subsequent Print Option parameter.
05
NSLDS Print Option
Y
Print Discrepancy Report to report changes in
NSLDS summary data
N
Do not print the NSLDS Discrepancy Report
The Sequence Number on the NSLDS records is independent of the Sequence Number on
the RCRAPPx records. The sequence number on the NSLDS record is not unique by
January 2009
Financial Aid 8.3
User Guide
Processing
2-25
source. For example, the second NSLDS record to be loaded for a student would be
sequence number 2 even if the first record was from a different source (that is, Manual).
• Since award validation must use current NSLDS data (if applicable) and you can
choose to not load the need analysis data from the ISIR, the NSLDS Data Match
Indicator is also stored as part of the NSLDS record. The Match Indicator is stored
in RCRLDS4_MATCH_IND for this purpose.
The value of this field is displayed in the Federal Match Indicators window of the
Need Analysis form (RNARSxx) in the NSLDS field, as well as in the NSLDS
Match field in the NSLDS Summary window of the Student Loan Data form
(RNASLxx). These fields display the match status for the current NSLDS record.
• A separate NSLDS Discrepancy Report is created to report changes in NSLDS
Summary Data.
Whenever a student is listed on the NSLDS Discrepancy Report, an NSLDS Override
Flag is printed if the student has any overrides for the aid year - either the NSLDS
Override or the Fund/Term Specific NSLDS Override. Review in a timely manner those
students with new NSLDS records and overrides to ensure that the overrides still apply.
If Parameter 03 Load Option (for Need Analysis) is set to a value of 5 (do not load
records, but print the discrepancy report), the Print Option parameter is automatically set
to Y, and the Recruiting and Recalc Need Analysis parameters are set to N.
09
NSLDS Output Application
ID
General area for which the Selection ID was
defined for NSLDS output
10
NSLDS Output Selection ID
Code that identifies the sub-population to be
updated by NSLDS
11
NSLDS Output Creator ID
ID of the person who created the sub-population
rules for NSLDS
The preceding NSLDS population selection parameters are optional.
NSLDS information entered via Data Load informs you as to whether a student is in
default. This information may affect the award process. If you use Early Decision, your
school may package awards before you receive NSLDS information. Creating an NSLDS
population selection allows you to re-validate previously processed awards based on
NSLDS information received after packaging.
When the first NSLDS record is loaded for a student for the year, or when a new NSLDS
record is loaded, Banner has the capability to capture the student’s PIDM in a population
selection ID so that you can run the Validate Award Process (RPRVAWD) to verify that the
previously packaged award is still valid.
2-26
Financial Aid 8.3
User Guide
Processing
January 2009
12
ISIR Creation Option
Y
Create ISIR records
N
Do not create ISIR records
A printed or electronic ISIR is only valid if the information matches the data at the CPS
for a given transaction number. To maintain a true ISIR database in a manner that
preserves the original content, Banner loads EDE records to the RCRAPP1 through
RCRAPP4 and RCRESAR tables with an INFC Code (source code) of ISIR and EDE. The
ISIR records are frozen as ISIR transactions. This option is controlled by the ISIR
Creation Option (Parameter 12).
15
Temporary PIDM
Blank when running in batch
16
Update Postal Address
Y
Update Postal Address
N
Don’t Update Postal Address
Y
Update Telephone Number
N
Don’t Update Telephone Number
Y
Update E-mail Address
N
Don’t Up-date E-mail Address
Y
Update Social Security Number
N
Don’t Update SS Number
17
18
19
Update Telephone Number
Update E-mail address
Update Social Security
Number
Parameter 15 - Temporary PIDM is used only when RCRTPxx is run from the RCRSUSP
form. Leave the parameter blank for batch processing.
If an incoming record is matched to an existing person record in the production database,
RCRTPxx loads all financial aid data from the incoming record. RCRTPxx does not
update populated fields on an existing person record. RCRTPxx updates the Postal
Address, Telephone Number, and/or E-mail Address if you answer Y to parameter 16,
17 or 18 and there is no record for the Address, Telephone, or E-mail type that you
specified in your Data Load Part 1 parameters. Social Security Numbers are updated on an
existing person record if it is blank and you enter Y for RCRTPxx parameter 19.
If no person record in the production database matches the incoming record, records exist,
RCRTPxx will create a person record for the student using data from the record in the
temporary tables, and will insert all financial aid data. (See section on New vs. Existing
Person below for additional discussion.)
Once RCRTPxx loads a record to the production database, all data for that record is
removed from the temporary tables.
January 2009
Financial Aid 8.3
User Guide
Processing
2-27
To run the RCRTPxx process, access the Process Parameter Entry form (GJAPCTL) and
enter the required parameters. You can proceed in one of two ways:
• Press the Submit radio button in the Submission Block and press the Save button
to submit the job
• Press the Hold radio button in the Submission Block and press the Save button to
hold the job. Note the sequence number. If you select the Hold option, you must
have access to the job submission directory to complete job processing. You are
prompted for a User ID, a password, and then the sequence number from above
(job submission one-up number).
RCRTPxx output includes the following reports:
Note
If there is no data for the reports, the file and output are suppressed.
„
• Report Control Information (rcrtpxx_jobseqno.lis). This report lists the parameters
used when Data Load Part 3 was run and the totals for the number of records
processed, the number of ISIR records added, the number of NSLDS records
added, duplicate transaction information, the number of Financial Aid records
(RORSTAT) created, the number of records not loaded as current, due to a locked
Need Analysis, the number of records not loaded when load option 3 was used, and
the number of Oracle and/or API errors encountered.
• Student listing (rcrtpxx_jobseqno_apps.lis). This report lists the records processed,
if the Need Analysis was load as the current record, if NSLDS data was loaded as
the current record, and identifies duplicate transactions.
• Discrepancy report (rcrtpxx_jobseqno_need.lis). If you selected the Need Analysis
Print option (parameter 06), this report displays discrepancies between the new
record being loaded and the existing current Federal record.
• NSLDS Discrepancy report (rcrtpxx_jobseqno_nslds.lis). If you selected the Need
Analysis Print option (parameter 06), this report displays discrepancies between
existing and new NSLDS information.
• Errors – Students Not loaded or errors encountered loading data
(rcrtpxx_jobseqno_errs.lis). If errors were encountered during Data Load part 3,
the name, ID, match status, and the error received are listed. If the record could not
be loaded, the Match status for the record is updated to Suspense with an error code
of 31 - Record not created. Failed Data Load Part 3. If the record was created but
not all data could be inserted, the error listing the data is provided; i.e., the process
was able to create the ID and biographical information for the record, but could not
insert the address due to missing data.
2-28
Financial Aid 8.3
User Guide
Processing
January 2009
Step 5 Review the Records on the Suspended Records Maintenance form
(RCRSUSP).
Records that are assigned a status of Suspend, Hold, Duplicate, *, or Error during Data
Load Part 2 (RCPMTCH) display on the Suspended Records Maintenance form
(RCRSUSP); records assigned a status of Match or New during the RCPMTCH process do
not appear on the form.
Only status codes of Duplicate, Error, Hold, and Suspense may be resolved from the
RCRSUSP form. If the status code is an asterisk (*), there is a data integrity problem with
this student that needs to be resolved prior to loading this student (a duplicate PIDM
exists). The status cannot be updated from an (*) on the RCRSUSP form. If the status code
is E, which means that a required field is null, you can correct the data in the temporary
table (top section) on this form and you can update the status.
SunGard Higher Education recommends working directly from the output report from the
RCPMTCH process as it lists all the students in the Suspense file and the status code of
each. To have this report you must print a copy of the Data Load Match Process – All
Records report.
The Data Load Record block of the RCRSUSP form displays data for a record in the
temporary tables, including a temporary ID assigned during Data Load Part 1 (RCBTPxx,
RCBCTxx). The ID may be the Social Security Number from the incoming record or a
temporary generated ID depending on your parameter choice during Data Load Part 1
(RCRTPxx, RCBCTxx). The RCPMTCH status and any associated error codes also
display. Error code descriptions are printed in the Data Load Match Process – All Records
report and display on RCRSUSP as part of the Error field. The Match Results Window on
RCRSUSP displays student data that exists in the production database once you have
selected a record as an actual match for the one displayed in the Data Load Record Block.
While on the RCRSUSP form, select the Match button to access the Common Matching
Entry form (GOAMTCH). From GOAMTCH, use the Common Matching functionality to
examine existing or potential matching records in the production database to resolve
suspended records. To utilize the Common Matching process, scroll to a record in the Data
Load Record Block on RCRSUSP, and press the Match icon or perform the Next Block
function. This will open the Common Matching Entry form (GOAMTCH). Information
from the record in the temporary table will display in the Data Entry Window. Press the
Duplicate Check icon to display a matching record (Match tab) or a listing of potential
matching records (Potential Matches) tab. If there are no records that match the rules that
you established on the Common Matching Rules form (GORCMRL), you will receive an
alert message.
If no match is found on GOAMTCH, and your school is loading New records, enter the
code of N in the Override field on the RCRSUSP form. The Status field is updated to New.
If you are using the status of Hold at your school, and you do not achieve a match on a
record with a Hold status, leave the status as H for matching later.
January 2009
Financial Aid 8.3
User Guide
Processing
2-29
If Banner displays a single matching record under the Match tab, information displays
according to the data elements present in your rules (i.e., If City is a data element in your
rule, and an address (of any address type) exists in the database that matches the one in the
temporary table, the matching address information displays. If no address data elements
are in your rule, no address information will display in the match fields.) If you are
presented with a list of potential matches, the same student may appear in the listing more
than once if you are using multiple priority rules and the student meets more than one of
your rules.
When reviewing a single matched record or multiple matching records, you may check
additional detail in the All Addresses field. You also may access selected Banner forms by
pressing the Details button on the GOAMTCH form. The Match Priority and Match
Results fields will indicate the rule used for matching and the portions of the rule that
were met, or not met. It is important to study the Common Matching algorithm to
understand what constitutes a match.
Once a matching record is confirmed, press the Select ID button on the GOAMTCH form
to return the data for the matching record to the Match Results Block of the RCRSUSP
form. Banner displays data items consistent with your rule. The address that displays on
RCRSUSP is for the address type that you specified in your Data Load Step 1 parameters,
or the most recent address in the Banner database, if no address exists for the type
specified during Data Load. Press the Select ID button on RCRSUSP, and Banner
automatically updates the match status and replaces the temporary ID in the Data Load
Record Block with the ID that exists in the production database. Save the record to finalize
the matching process.
A Duplicate status indicates that a student has two or more records in the temporary tables
at the same time. These may be from a single data source (EDE) or from multiple data
sources (EDE and CSS). Examine the records and select one for Common Matching. If
your school loads all records, select the duplicate with the earliest transaction number first.
After performing a Common Matching search, and achieving a match or entering a status
of New on the first record, you should load the record to Banner. If you have only one
more record for the student, you should achieve a match status the next time you run the
matching process in batch or online. If you have more than one duplicate remaining, you
must repeat the matching and loading processes until all records are loaded to the
production database.
If you make a mistake in changing a student’s status and wish to return to the original
status code, you have two options. Re-run the RCPMTCH process for all students, or prior
to committing the status, change the Override status code to ‘- ‘ for that student. When
you save the record, it will revert back to the original status code.
Note
Changing the status code on the form only works if you have not left the
RCRSUSP form (Exit or Clear form Rollback) since making the initial
change. Once you leave the form, the changes are saved and the Match
and New records no longer appear on the RCRSUSP form. Match and
New records continue to appear on the form until you perform an Exit or a
„
Clear form Rollback.
2-30
Financial Aid 8.3
User Guide
Processing
January 2009
Once a record is assigned a Match or New status, you must load the record to the Banner
database using the Data Load Part 3 (RCRTPxx) process. You may select the Load button
on the RCRSUSP form to run RCRTPxx immediately, which loads the record to the
permanent tables. You must have permission to run RCRTPxx and must have a parameter
set established in your user name to run the online process. Once you load the record, or
leave the record after assigning a New or Match status, the record no longer appears on the
RCRSUSP form. If you do not want to use the online load process, or if you forget to load
the record immediately after updating the status to Match or New, you may run Data Load
Part 3 (RCRTPxx) in batch (see Step 6 below).
Warning
If you elect to run Data Load Part 3 (RCRTPxx) in batch after resolving
records on the RCRSUSP form, do not run Data Load Part 2 RCPMTCH
again prior to running RCRTPxx. RCPMTCH returns your New and Match
„
status codes to those originally assigned to the temporary records.
The Suspended Records Maintenance form also includes functionality to delete selected
records from the temporary tables. You may check the Delete Record field on a selected
record to flag the record for deletion according to your institutional Data Load policy.
Once the flag is set, you may select Delete Temporary Records on the Options menu of the
RCRSUSP form. This removes all flagged records for the aid year and data source
displayed in the Key Block of RCRSUSP. If you do not use the online delete option, you
may run the Data Load Table Delete Process (RCPDTMP) in batch using parameter
choices to delete records flagged on the RCRSUSP form. Records flagged for deletion
continue to appear on RCRSUSP until the record is deleted or until the Delete Record
field is unchecked.
Note
The online Delete Temporary Records Process does not check for the
„
User ID before deleting flagged records.
Step 6
Run the RCRTPxx Process
This step is a repeat of Step 4. You should run batch RCRTPxx immediately after
resolving suspended records if you do not choose to load the records to the production
database individually from the RCRSUSP form. This moves those corrected records to the
production database for processing, and will reduce the chance of another user creating a
duplicate record in Banner for the same student.
It is critical that you repeat the RCPMTCH Process and the RCRTPxx Process until all
records in the temporary tables that can be resolved are resolved. These are iterative
processes and can be run over and over again until there are no longer any records in the
temporary tables that need to be moved.
Step 7
Run the Data Load Table Delete Process (RCPDTMP)
The Data Load Table Delete Process (RCPDTMP), which is used to delete records from
the temporary tables, may be run in batch, or the process may be run on-line from the
RCRSUSP form. The batch process can delete all records in the temporary tables for a
January 2009
Financial Aid 8.3
User Guide
Processing
2-31
selected Aid Year and INFC Source Code. The process also can delete all records where
the Delete Record field is checked on the RCRSUSP form. To delete records on-line from
RCRSUSP, you would check the Delete Record field to flag selected records. Then you
would select the Delete Temporary Records selection on the Options menu. This deletes
flagged records for the Aid Year and Source Code displayed in the RCRSUSP Key Block.
If you choose to delete selected records using either the on-line or the batch process, all
other records remain unchanged in the temporary tables.
Parameters for the RCRDTMP process are:
Parameter
Value
01
Aid Year Code
Appropriate Aid Year
02
Data Source Code
Valid Data Source Code
03
Delete Flagged Records
Only
Y
Delete Flagged Records Only
N
Delete All Records
Note
Parameter 01 and 02 are required if parameter 03 is set to N. However,
these parameters are not required if parameter 03 is set to Y.
If parameter 03 is set to Y and neither 01 or 02 is populated, the process
deletes all records where the ROTIDEN_DELETE_FLAG = Y, without regard
to the Aid Year code or INFC code. However, if either, or both, 01 and 02
are populated and 03 = Y, then the process use the combination of the
parameters to delete the correct flagged records. When parameter 03 is
set to Y, records that are not flagged for deletion on RCRSUSP remain in
the temporary tables.
On the Process Parameter Entry form (GJAPCTL), enter the required
parameter for RCPDTMP. You can proceed in one of two ways:
Select the Submit radio button in the Submission Block and select the
Save button to submit the job
Select the Hold radio button in the Submission Block and select the Save
button to hold the job. Note the sequence number. If you select the Hold
option, you must have access to the job submission directory to complete
job processing. You are prompted for a User ID, a password, and the
sequence number from above (job submission one-up number).
This process produces a rcpdtmp_seq.lis file. You should print or save
this file to capture the results of the process.
The RCPDTMP Process also creates an rcpdtmp_seqno.log file. This
2-32
Financial Aid 8.3
User Guide
Processing
January 2009
log file contains information that will be helpful to the technical staff if you
encounter a problem running this process. (As a general rule, you should
always review the output from any job prior to starting the next process.)„
Note
You must decide when you need to run the RCPDTMP process to delete
„
records from the temporary tables:
• If your school is diligent in the act of resolving all suspended records from
Data Load to Data Load, and you are loading all New student records to the
database, the RCRSUSP form should be empty after each Data Load. You
would not need to run the RCPDTMP Process.
• If you are using the RCPMTCH status of Hold to keep records in the
temporary tables until a matching person record exists in the production
database, you would run RCPDTMP only at the end of the financial aid
processing year. You would use the Aid Year and INFC Source Code
parameters for the batch process to remove records for the completed aid
year from the temporary tables.
• If you are loading only selected records into the production database (for
example, the latest transaction when two records with the same EFC exist in
the temporary tables), you may choose to flag records for deletion on
RCRSUSP and use the on-line Delete Temporary Tables option or the batch
process parameter to Delete Flagged Records Only.
Warning
Once data is deleted from the temporary tables, it is lost. If you
accidentally delete all data it could mean re-running the Data Load
Process for a particular file or for the particular aid year. This might
include records that already have been loaded to the production
database.
„
Additional Data Load Topics
The following sections discuss additional topics related to Data Load.
Loading and Storing of ISIR Records
The Institutional Student Information Record (ISIR) is the Department’s official
notification to your school about a student’s Expected Family Contribution (EFC) and
eligibility for Federal aid. This electronic ISIR record along with NSLDS information is
delivered to your school through EDE. You must maintain these original ISIRs along with
the NSLDS information for audit purposes and you may need to print them for internal or
student use.
To maintain these records, your school needs to support a database of ISIRs in a manner
that preserves the original content. A printed or electronic ISIR is only valid if the
information matches the data at the CPS for a given transaction number. However, a
January 2009
Financial Aid 8.3
User Guide
Processing
2-33
school may want to change information on the original ISIR, and to facilitate this Banner
provides an option during data load to create two records from the original ISIR data.
In order to maintain a true ISIR database, you have the option to load EDE ISIR records
with source codes (INFC Code) of ISIR and EDE. Those transactions with a source code
of ISIR are never updated, maintaining the original ISIR transaction information. Those
records with a source code of EDE may be changed. Parameter 12 of Data Load, Part 3
(RCRTPxx) determines whether or not an ISIR record is created. When this parameter is
set to Y (Yes), both an EDE and ISIR source record may be created at the time of data load.
The Current Record Indicator on records with a source code of ISIR is always N.
Occasionally, the processing center (CPS) sends duplicate transactions for students.
Historically, this has been because CPS sent the original ISIR transaction with incorrect
information as a result of a processing problem. Also, this occurs when a student submits a
correction to their name directly to CPS and a second transaction ‘01’ record with a new
SAR ID is received.
Banner may load these duplicate EDE and ISIR records depending on the parameter
options used for Data Load, Part 3 (RCRTPxx). For both sources of records, the sequence
number associated with the transaction is incremented by one each time a duplicate
transaction is loaded. The ISIR and EDE record with the highest transaction number (and
if a duplicate transaction, the highest sequence number) is the most recent sent by CPS. A
listing of all transactions from all sources for a student can be viewed on the Applicant
Need Analysis Application Inquiry window (RNIAPPL). Also, the Applicant Listing
produced by RCRTPxx will identify duplicate transactions with an asterisk (*) for the
source ISIR. A count of duplicate ISIRs is also included in the Control Totals for the
process.
Depending on parameter choices during Data Load, it is possible that an EDE record will
be created without a corresponding ISIR record. It is also possible that the ISIR record can
be created without the EDE record. For this reason, the sequence numbers for EDE
records and ISIR records may not correspond. However, whenever you are reviewing
records, either EDE or ISIR, the transaction with the highest transaction number and, if
there are duplicate transactions, the highest sequence number is the most recent.
Selections for the Load Option, Print Option, Recruiting Option, and Recalc Need
Analysis Option parameters in Data Load, Part 3 (RCRTPxx) are only applied to those
students who already have a financial aid application record for the current year.
For students without a current year record, EDE source records are always loaded to the
database. They are updated as the current EDE record and the Recalc Need Analysis flag
set according to the value selected for this parameter in EDE Data Load, Part 1
(RCBTPxx). The value for Parameter 03, Load Option for Need Analysis is disregarded
for these new application records. For example, if the option for Parameter 03 was to load
all records as non-current, the process only loads non-current records for students with
existing aid year information. Whether a record with a source code of ISIR is created
depends on the option for Parameter 12 in Data load Part 3(RCRTPxx). NSLDS
information is always loaded unless it is a duplicate transaction without any changes.
2-34
Financial Aid 8.3
User Guide
Processing
January 2009
NSLDS data is stored in non-updateable records in the RCRLDS4 – RCRLDS7 tables.
ISIRs and NSLDS records each have a unique Transaction Number and the two may be
different. Since NSLDS data is printed on the ISIR, Banner maintains a record of which
NSLDS transaction record came in on which ISIR transaction. The NSLDS transaction
number associated with the ISIR is stored in RCRAPP4_NSLDS_TRAN_NO.
NSLDS documentation indicates the transaction number will be incremented whenever
data changes exist. However, schools on occasion may receive updated information on an
NSLDS record without a new transaction number. Banner loads duplicate NSLDS
transaction numbers, incrementing the sequence number, if there is a change to any
information on the new NSLDS record. The current NSLDS record is the one with the
highest transaction and, if there are duplicate transactions, the highest sequence number.
NSLDS detail information is viewed on the Student Loan Data window (RNASLxx). A
listing of all NSLDS records for a student is accessible from this window as well as by
going directly to the Applicant Student Loan Data Inquiry form (RNINSLD).
Data Load, Part 3 (RCRTPxx) output reports duplicate NSLDS transactions in the Student
Summary listing with an asterisk (*) in the NSLDS-current column for the source EDE. A
count of people who had NSLDS data added with duplicate transactions is included in the
Report Control Totals (rcrtpxx_nn.lis). Also, there is an option to print an NSLDS
Discrepancy Report.
ISIR records may be printed using the ISIR Print Process (RERISxx). Using Parameter 7
(Banner ID Trans No), when you enter only a Banner ID then the process prints the ISIR
with the highest transaction number and sequence number. If an optional Transaction
Number is entered along with the Banner ID, then the ISIR with that transaction number
and highest sequence number is printed. Enter a Banner ID, Transaction Number and
Sequence Number to print specific ISIRs.
New Person Versus Existing Person
If a person record exists in Banner at the time of Data Load, Data Load Part 3 (RCRTPxx)
does not update fields on that person record except for fields specified in RCRTPxx
parameters 16, 17, 18, 19. If no person record exists, and you decide to load New records,
a new person record is created with data from the incoming record as shown below:
Any element with an asterisk (*) on the following tables must have a Banner Conversion
Value on the Interface Data Translation Rules form (RCRTPTR).
Identification Information (SPRIDEN, ROTIDEN Tables)
Identification Number
Last Name
First Name
Middle Initial
Person Information (SPBPERS, ROTPERS Tables)
January 2009
Financial Aid 8.3
User Guide
Processing
2-35
Gender Indicator
SSN
Marital Status*
Birth Date
Title
Citizenship
Address Information (SPRADDR, SPRTELE, ROTADDR Tables)
Address Type Code
State Code
Telephone Number
Street Line 1
ZIP/Postal Code
Start Date of Residence
City
Area Code
Recruiting Information (SRBRECR, RCTRECR Tables)
Desired Entry Term
Level Code
Department Code
Degree Code
Major Code*
Financial Aid Applicant Status Information (RORSTAT, ROTSTAT Tables)
Financial Aid Satisfactory Academic Progress Information (RORSAPR, ROTSAPR
Tables)
Financial Aid Application Information (RCRAPP1, RCRAPP2, RCRAPP3, RCRAPP4,
RCRTMP1, RCRTMP2, RCRTMP3, RCRTMP4, RCRESAR, RCTESAR Tables)
Financial Aid National Student Loan Data System (RCRLDS1, RCRLDS2, RCRLDS3
Tables)
Data Load Part 1 (RCBTPxx, RCBCTxx) Temporary
Tables
The RCBTPxx Process for Federal data (EDE) records and the RCBCTxx Process for CSS
Profile data records load incoming files to temporary tables. These temporary tables,
which are duplicates of the Oracle tables where the production data is stored, contain
fields that convert data from the flat-file format to the Oracle format when discrepancies
exist.
For example, a temporary person file name is ROTPERS, while the actual table name is
SPBPERS. The temporary table contains the exact fields of the actual table plus fields that
are needed to convert the birth date to the proper format.
Temporary tables and their matching production tables used during this Data Load step
include:
2-36
Financial Aid 8.3
User Guide
Processing
January 2009
January 2009
Temporary Table
Production Table
Name/ID Information Table (ROTIDEN)
Name/ID Information Table (SPRIDEN)
Basic Person Information Table
(ROTPERS)
Basic Person Information Table
(SPBPERS)
Address Information Table (ROTADDR)
Address Information Table (SPRADDR)
Telephone Table (SPRTELE)
Recruiting Data Table (RCTRECR)
Recruiting Data Table (SRBRECR)
Recruiting Source Table (RCTRSRC)
Recruiting Source Table (SRRRSRC)
Recruiting Contact Table (RPTCONT)
Recruiting Contact Table (SORCONT)
Application Table (RCRTMP1)
Application Table (RCRAPP1)
Application Table (RCRTMP2)
Application Table (RCRAPP2)
Application Table (RCRTMP3)
Application Table (RCRAPP3)
Application Table (RCRTMP4)
Application Table (RCRAPP4)
Application Table IM data (RCRTMP5)
Application Table IM data (RCRIMP1)
User-Defined IM Data Table (RCRTMP6)
User-Defined IM Data Table (ROBUSDF)
ISIR Table (RCTESAR)
ISIR Table (RCRESAR)
NSLDS Table (RCTLDS4)
NSLDS Table (RCRLDS4)
NSLDS Table (RCTLDS6)
NSLDS Table (RCRLDS6)
NSLDS Table (RCTLDS7)
NSLDS Table (RCRLDS7)
E-Mail Table (ROTEMAL)
E-Mail Table (GOREMAL)
Satisfactory Progress Table (ROTSAPR)
Satisfactory Progress Table (RORSAPR)
Student Status Table (ROTSTAT)
Student Status Table (RORSTAT)
NSLDS ACG Payment (RCTLDSA)
NSLDS ACG Payment (RCRLDSA)
NSLDS SMART Payment (RCTLDSS)
NSLDS SMART Payment (RCRLDSS)
Financial Aid 8.3
User Guide
Processing
2-37
The following permanent tables -- though used in this Data Load step - have no temporary
table equivalent:
2-38
Report/Process Definition Table
GJBJOBS
Process Run Parameter Table
GJBPRUN
Population Selection
GLBEXTR
Population Selection Base Table
GLBSLCT
Common Matching Rules
GORCMSR
Institutional Description Table
GUBINST
Code Conversion Table
RCRTPTR
Log Table (current record change)
ROBALOG
Institutional Options Table
ROBINST
Application User-Defined Data Table
ROBUSDF
Resource Table
RPRARSC
Tracking Requirement Table
RRRAREQ
Data Code Validation Table
RTVINFC
Tracking Requirement Code Table
RTVTREQ
Tracking Requirement Status Table
RTVTRST
User-Defined Variable Description Table
RORUSER
Interface Data Aid Year Rule Table
RCRINFC
Financial Aid 8.3
User Guide
Processing
January 2009
Common Matching Algorithm
• The Common Matching procedure allows for the processing of multiple rules.
Define priority numbers for each rule indicating the sequence in which to process
the rules. Assign your strictest rule as the first priority (i.e., #1).
• The Common Matching procedure processes each rule in order, separately and
completely.
• The first step is to perform primary matching for the rule. This step defines the
population on which the rest of the processing (secondary match) is performed. If
no match occurs during the primary match, the external record is considered new.
• The second step is to perform the secondary matching processing against the
results of the primary match. If the secondary match determines an exact match on
only one record, the external source record is considered a match. If more than one
record is matched to the criteria, the external source record is considered in
suspense. The external source record is considered in suspense if data matches part
of the criteria of the rules but does not match all the criteria.
• If the results of the rule are new or match, the results are returned to the calling
process. No other rules are processed.
• When all the rules have been processed, the Common Matching procedure
examines the results and returns the results to the calling process. The Match Status
(new, matched, or suspense) is returned as well as a results message providing the
elements that were matched, not matched, or missing as a result of processing the
rule.
• Online only. If a record is determined as a match using one rule, but as a suspense
using one or more additional rules, the record’s match status is set to match but you
can view the potential match records as well.
Rule Indicators
The Data Required field for the matching rules can be Exists or Required.
• A value of Required means the data field associated with the indicator is required
and must be present on the external source and in Banner. If the field on either the
external source or in Banner is null for a data element with the Data Required
indicator set to Required, the data element is considered not matched. If all data
elements are required, but all of the data elements in the secondary match are null
either in Banner or the external source, the record will be suspended for review.
• A value of Exists means either the external source or Banner value can be null. If
either or both values are null, the field is considered a match.
January 2009
Financial Aid 8.3
User Guide
Processing
2-39
Field Length values
Whenever a length is specified on a rule on the Common Matching Rules form
(GORCMRL), a comparison is made using the rule length of the fields. For example,
using the last name, the comparison is between the rule lengths of the last name on the
external source to the rule length of the last name in Banner. If the rule length is 5, the first
five characters of the external source last name are compared to the first five characters of
the Banner last name. You can enter a negative length for ID and SSN/SIN/TFN fields to
reverse the order to last to first; i.e., enter a –5 for the length of SSN/SIN/TIN, the last 5
characters of the external source are compared to the last 5 characters of the Banner SSN/
SIN/TIN.
Example:
Last Name length:4
First Name length:3
SSN/SIN/TFN length:-4
Patricia Longnecker, 555116789
The first 4 characters of the last name are used: LONG
The first 3 characters of the first name are used: PAT
The last 4 characters of the SSN/SIN/TFN are used: 6789
Primary Match logic
The primary match uses the Last Name/Non-person name
(SPRIDEN_SEARCH_LAST_NAME), which is a required data element for Common Matching.
If the First Name (SPRIDEN_SEARCH_FIRST_NAME) or Middle Name
(SPRIDEN_SEARCH_MI) are specified data elements in a rule, these elements are used as
part of the primary match for name as well. In addition, if ID (SPRIDEN_ID) and/or SSN/
SIN/TFN (SPBPERS_SSN) are specified data elements in a rule, these elements are used as
part of the primary match.
The Common Matching process uses the Entity indicator established for the Source on
the Common Matching Source Code Rules (GORCMSC) to determine the records to
select in Banner.
• A match type indicator of P selects person records: GORCMSC_ENTITY_CDE = P
selects records from SPRIDEN where the SPRIDEN_ENTITY_IND = P.
• A match type indicator of C selects non-person records: GORCMSC_ENTITY_CDE = C
selects records from SPRIDEN where the SPRIDEN_ENTITY_IND = C.
2-40
Financial Aid 8.3
User Guide
Processing
January 2009
• A match type indicator of B selects person and non-person records:
GORCMSC_ENTITY_CDE = B selects records from the SPRIDEN where
SPRIDEN_ENTITY_IND = P or C.
Either Step 1 or Step 2 below must be true for a record to pass the primary match. If the
External record fails the primary match, the match status is marked New.
Step 1 — If the SSN/SIN/TFN is defined for the Source and rule priority number,
retrieve all records from Banner with a matching SSN/SIN/TFN.
• SSN/SIN/TFN data element is defined as part of the rule and
SPBPERS_SSN = External source SSN/SIN/TFN.
Step 2 — If First name and/or Middle names are defined for the Source and rule
priority number, combine with Last name criteria and retrieve all records from
Banner with a matching Name.
Note
When matching non-person records, the First and Middle names should
„
not be included as part of the rule.
Step 2A —The following must be true:
• SPRIDEN_SEARCH_LAST_NAME must equal the last name on the
External source for the specified length.
Note
If the Source is defined to match non-person records and
SPRIDEN_SEARCH_LAST_NAME is not like the non-person name from the
External Source, the matching algorithm checks to see if a matching
„
record exists on the GORNPNM alias table.
Step 2B — One of the following must be true:
• First Name data element is not defined
or
• First Name data element is defined for the rule and
SPRIDEN_SEARCH_FIRST_NAME is equal to the External source First
Name for the specified length.
Note
If the SPRIDEN_SEARCH_FIRST_NAME is not like the First name from the
External Source, the matching algorithm checks to see if a matching
record exists on the GORNAME alias table if the Source is defined to
„
match person records.
Step 2C — One of the following must be true:
• Middle Name data element is not defined.
January 2009
Financial Aid 8.3
User Guide
Processing
2-41
• Middle Name data element is defined for the rule and
SPRIDEN_SEARCH_MI is equal to the External source Middle Name
for the specified length.
Note
If the SPRIDEN_SEARCH_MI is not like the Middle name from the External
Source, the matching algorithm will check to see if a matching record
exists on the GORNAME alias table if the Source is defined to match
„
person Records.
Step 3 — If ID is defined for the Source and rule priority number, retrieve all
records from Banner with a matching ID.
• ID data element is defined as part of the rule and SPRIDEN_ID =
External source ID.
Secondary Match Logic
The secondary match compares the data elements defined for the Source and rule priority
number for all records returned by the primary match process. The goal of this match is to
find an exact match between the External Source record and an Banner record.
When comparing a data field with the Data Required Indicator set to EXISTS, a null
value may exist either in Banner or in the External Source. If a null value exists either in
Banner or the External Source for the data element, the data element is considered as
matched.
When the Data Required Indicator is set to REQUIRED, if a null value exists either in
Banner or the External Source for the data element, the data element is considered not
matched.
For an External Source record to be considered a match, the following conditions must be
true:
This step is repeated for each of the data elements for the rule and one condition must be
true for each:
• Data element is not defined.
• Data element Data Required Indicator is Y or R and the Banner value is equal to
the External source value for the specified length.
or
• Data element Data Required Indicator is Y and Banner value is NULL.
or
• Data element Data Required Indicator is Y and External Source value is null.
2-42
Financial Aid 8.3
User Guide
Processing
January 2009
When the data being matched is part of a logical unit (an address), the logical unit is
matched separately and completely. For example, when matching on city and zip code, the
city and zip code must be associated with one address.
Exception: For an External Source record to be considered new when the record has
already passed the primary match, all non-name data elements must be determined as not a
match and none of the non-name elements may be null.
Examples of Matching Algorithm and Results
If all required data elements are missing, the record will be suspended.
Last name = Required
First Name = Required
DOB Day = Required
DOB Month = Required
DOB Year = Required
City = Required
Banner values: Mildred Jones, DOB = 08/17/1957, City = Topeka
External values: Mildred Jones
The external record passes the primary match because the first and last names match.
However, since all other data elements are missing (i.e., null) from the external source (not
matched, but are null), the record is suspended.
In this example, the external record passes the primary match as the first and last name
matches against 2 Banner records. These 2 records are then used in the secondary match.
Rule 1
Rule 2
Last name = R
Last Name = R
First name = Y
First Name = Y
SSN = Y
DOB = Y
DOB = Y
City = Y
City = Y
Zip code = Y
Zip code = Y
January 2009
Financial Aid 8.3
User Guide
Processing
2-43
Banner values:
1) Alberta Rockville, 330229101, Largesse, 06259, 05/01/1985
2) Alberta Rockville, no SSN, Pomfret, 19355, no DOB
External values:
Alberta Rockville, 330229101, Largesse, 06259, no DOB
The external record passes the primary match because the first and last name matches at
least one Banner record with the same first and last name. Using Rule 1 and the matching
algorithm, the external record matches against Banner record 1. It will suspend against
Banner record 2. Using Rule 2, the external record suspends against Banner record 1 as
well as Banner record 2. Since an exact match was found, the algorithm returns a match.
In this example, the external record passes the primary match, which usually means that
the match status will be ‘Suspense’ at a minimum. However, in this case, because none of
the non-name/SSN fields match, the external record is set as ‘New’.
Rule 1
Rule 2
Last Name = R
Last Name = R
First Name = R
First Name = R
SSN = Y
DOB = Y
DOB = Y
City = Y
City = Y
Zip = Y
Zip = Y
Banner values:
Tomasso Dalimonte, SSN = null, DOB = 06/02/78, City = Marikesh,
Zip = 11233
External values:
Tomasso Dalimonte, SSN = null, DOB = 09/07/59, City =
Woodstock, Zip = 06281
The external record passes the primary match because the first and last names match.
Normally, this would mean that the record would be suspended at a minimum. However,
because the DOB, City and Zip code fields specifically do not match (i.e., none of them
are null), the record’s match status is set to New. This is the only exception to the basic
matching algorithm.
2-44
Financial Aid 8.3
User Guide
Processing
January 2009
Pell Processing
Introduction
Pell Setup
The Pell Setup section provides information regarding fields that need to be populated,
how values in these fields affect Pell processing, the formula used to calculate Pell, and
how fields affect both the awarding and disbursement of Pell.
Pell Procedures
The Procedures section addresses topics such as multiple Pell processing, controlling
when the Pell Calculation Process is run, locking Pell, handling less than half-time Pell
more efficiently, updating award amounts to agree with actual disbursement amounts, and
automatically scheduling remaining Pell eligibility to future terms.
Pell Process
The Process section offers information on the Pell Calculation Process (RPEPELL) and
the Disbursement Process (RPEDISB) as it relates to Pell. This chapter also demonstrates
how Pell Grant awards and Pell Grant disbursements are calculated and includes examples
of calculations.
Pell Setup
Fund Base Data form (RFRBASE)
Establish a Pell fund code (or multiple codes) as a federal grant fund. The Pell fund code
requires the following settings for the Fund Source, Fund Type, and Federal Fund ID
fields. Multiple Pell codes are allowed for institutions with multiple campuses if
necessary.
• Set the Fund Source field to a federal fund source type.
• Set the Fund Type field to a grant fund type.
• Set the Federal Fund ID field to Pell.
For additional information about the RFRBASE form, refer to the Fund Base Data form
(RFRBASE) information in Banner Financial Aid Online Help.
January 2009
Financial Aid 8.3
User Guide
Processing
2-45
Detail Code Control form (TSADETC)
Ask Student Accounts personnel to establish grant fund detail codes for Pell funds. The
detail code created on this form is then assigned to the appropriate Pell fund code on the
RFRBASE form. If you use multiple Pell fund codes, you will need multiple detail codes,
as the fund codes and detail codes require a one-to-one relationship.
Fund Management form (RFRMGMT)
Enter fund data and options for the Pell fund code(s) that you established on the Fund Base
Data form (RFRBASE). This involves the entry of information in the Aid Year Specific
Information blocks on the first 3 windows of the form.
Aid Year Specific Data - Packaging Options window
Complete packaging option fields that are applicable to COD, as follows.
1. Award Max - Enter the maximum loan that could be made to any student during the
combined terms of the aid year (For example: The Pell limit for the 2004-2005 aid
year is $4,050).
2. Award Min – Schools generally enter $.00 as the minimum to allow small award
amounts in the event of a Return of Title IV calculation or in the event that the Pell
Award needs to be reduced to zero.
3. Auto Package – This field must be checked to automatically package Pell through
batch or online processing.
4. Auto Schedule – This box must be checked to enable the system to create a Pell
disbursement schedule when Pell is added to the student’s award package.
5. Auto Accept – Check this box if you want to ensure that Pell offers are automatically
placed into Accepted status. If this box is not checked the Pell will be accepted once a
SAR is received. Once a valid SAR Certified date is entered on ROAPELL, the
offered Pell grant will be accepted. Pell awards cannot be manually accepted.
6. Replace EFC - Do not check this box.
7. Reduce Need - Check this box. A check in this box reduces any remaining unmet
need automatically.
8. Override Need Check this box.
9. Loan Process - Do not check this box.
10. Need Analysis - Check this box to require a need analysis record before you package
the award.
2-46
Financial Aid 8.3
User Guide
Processing
January 2009
11. Award Letter Ind - Check this box if you want a change to the offered amount of a
Pell award to reset the award letter indicator in the student’s RORSTAT record. You
can use this indicator with population selection to identify those students that need
new or revised award letters.
12. Equity Fund - Check this field to reduce the student's equity level when you use
equity packaging. The system packages equity funds first to reduce the equity level
(the system packages non-equity funds after the equity funds regardless of the priority
assigned for the funds on the RPRGFND form).
13. Count for NCAA - Check this box to indicate you can count this fund for NCAA
regulations. The Fund Aid Year Specific Table (RFRASPC) contains the
RFRASPC_NCAA_IND field. Banner does not perform any processing of this data. It is
available for use in conjunction with your institutionally-defined rules and reports.
14. Round Award - Set this field to 001 so that the automatic packaging process
(RPEPCKG) rounds the award to the nearest dollar.
15. Round Schedule - Set this field to RD=Round Dollars to round the disbursement
schedule to the nearest dollar.
16. Memo Credit - Set this field to None if you do not want to apply disbursements as a
memo credit on the student’s account for the Pell fund. Otherwise, select Offered to
allow disbursements to memo when the award is in an offered status. Select Accepted
to allow disbursements to memo when the award is in an accepted status.
17. Disburse - Select the System option to allow the system to disburse the fund.
Aid Year Specific Data - Disbursement Options window
1. Use Disb Enroll Edits for Memo - Check this field to allow the application of the
disbursement enrollment edits to be applied to funds in memo status.
2. Recoup When Award Reduced - Check this field to recoup aid from the account
when the award amount is less than the amount which has already been paid. The
disbursement process places a negative payment amount on the student account for
the difference.
3. The If Ineligible Before Cut-off Date and If Ineligible After Cut-off Date fields
determine the course of action if the student receives a payment for an award in a
specific term and the student becomes ineligible for the award after it is paid. Set
these fields to the appropriate option for your institution. Cut-off dates are set on the
RPROPTS form.
4. Check the Use Attending Hours box if you wish to calculate the enrollment load for
disbursement based on hours that the student is attending and the course has begun.
January 2009
Financial Aid 8.3
User Guide
Processing
2-47
(See the Open Learning Handbook for more information on Open Learning and
Attending Hours)
Note
The Disbursement Load Options on the Disbursement Options window
are not applicable to Pell since Pell Grants pay based on the Pell Grant
„
Payment Schedule Grid.
Institution Financial Aid Options form (ROAINST)
Main window
Enter the routing number (formerly the Common School ID) for the school that sends and
receives data for the campuses or students it serves in the Routing No./Common School
ID field. The Routing Number is obtained from COD School Relations or the COD web
site. The Routing Number is the default Entity ID used when creating the extract file with
the COD Extract Process (REREXxx). This ID can be overridden through parameters for
the REREXxx process.
Pell Grant Defaults - Defaults window
Check the Prevent Automatic Pell Calculation box only if you want to prevent the Pell
Process (RPEPELL) from automatically running from forms that initiate the Pell Process
for all students at the institution. This may be appropriate if your institution is Graduate
level only or you do not wish for Pell awards to post until a later date.
Note
Even when the Prevent Automatic Pell Calculation box is checked, the
RPEPELL process will run when the student is in a Population Selection
used to run RPEPELL in batch from the job control form (GJAPCTL) or
„
when RPEPELL is run from the ROAIMMP form.
Enter the main campus entity ID, the main campus Pell ID, the name of the financial aid
director, the director's phone number, and the Title IV destination code assigned to your
institution in the appropriate fields. If you use an EDE Service Agent, enter the code in the
Service Agent Code field.
Enter the primary Pell Fund Code to be used if there is more than one Pell code listed on
RFRBASE and the applicant is not assigned to a campus that has a unique Pell fund
associated with it.
Check the Pell Reduced Eligibility Ind if you want to automatically create Pell
origination records when the Pell eligibility for a student is reduced (not required). Banner
will automatically create the origination records for any increase in eligibility, as this is
required.
2-48
Financial Aid 8.3
User Guide
Processing
January 2009
If your school is participating in the Department of Education’s Just in Time program for
Pell for this aid year, check the JIT/Adv Pay field. You can also check this field if your
school wishes to follow the JIT rules for Pell for the aid year as far as reporting the
expected Pell payment and requiring the receipt of an acknowledgement back prior to
allowing Banner to disburse the Pell funds.
If you check the JIT/Adv Pay field, enter the number of days prior to the scheduled
disbursement date in the # of Days for JIT field to allow the disbursement record to be
extracted. Based on the value in the # of Days for JIT field, the REREXxx Process allows
a JIT school’s Pell funds to be extracted. The REREXxx Process picks up these records to
submit for funding prior to payment. Valid values are 00 - 30.
The Alternate Pell Schedules Used field is used by the Pell process (RPEPELL) to
identify students who require the use of the Alternate Pell Schedules for determination of
their Pell award. Students who qualify for the Alternate Pell Schedules will receive a
lower maximum Pell Grant in some of the payment cells on the schedule. Because these
reductions are not consistent across the impacted cells, a different schedule is used. Check
this field to identify students who require the Alternate Pell Schedules for determination of
their Pell award. Also check this field if you wish to use both the Alternate Pell and the
Regular Pell schedules. When the field is unchecked, only the regular Pell Schedule will
be used to calculate Pell awards.
Note
The Alternate Pell Schedules Used field has been disabled - beginning
with the 2007-2008 and 2008-2009 aid years.
„
Check the Use New Pell Less than Half Time Calculation box if you wish to
automatically calculate a less than half time Pell Cost of Attendance using the RTVCOMP
budget components designated as eligible for Pell less than half time.
Campus/EDE Defaults window
Build all data related to each campus on the Campus/EDE Defaults window.
If you are a multi-campus based school, enter the routing number (formerly the Common
School ID) in the Routing No./Common School ID field.
If you are using multiple Pell fund codes, enter the Pell Fund Code associated with this
campus.
Check the Prevent Automatic Pell Calculation field only if you wish to prevent the Pell
calculation for the designated campus and you did not check this box on the Institutional
Defaults window.
For additional information about the ROAINST form, refer to the Institution Financial Aid
Options form (ROAINST) information in Banner Financial Aid Online Help.
January 2009
Financial Aid 8.3
User Guide
Processing
2-49
Budget Component Validation form (RTVCOMP)
Check the Used for Alt Pell field to select the value of this component for the calculation
of alternate Pell low tuition and fees. This amount is used in the determination of whether
the student is eligible for the Alternate Pell Schedules and, if so, the correct amount of the
Alternate Pell award.
Note
Alternate Pell Schedule functionality has been disabled - beginning with
„
the 2007-2008 and 2008-2009 aid years.
Check the Used for <½ Pell box to select the value of this component for the automatic
calculation of a less than half-time Pell cost of attendance. If you checked the Use New
Pell Less than Half Time Calculation box on ROAINST, the Banner disbursement
process (RPEDISB) uses these components and posts the calculated budget on the
ROAPELL form.
Packaging Options form (RPROPTS)
Main Window
Options on the first window affect all funds, but certain options are necessary for Pell
awarding. The Use Estimated Enrollment field and Default Estimated Enrollment
options, if checked, are used if the selected enrollment option in the Pell Options window
is not defined for a term.
The Enrollment Option for Disbursement field is used by other funds and is used by the
Pell process if the disbursement enrollment options are not populated on the Pell Options
Window for any term.
Pell Options Window
The Pell Options Window contains a Pay Pell if Disb Amt differs from Award Amt
option. Since the Pell calculation is done both at the time of awarding and at the time of
disbursement, it is possible that the award amount and the calculated disbursement amount
(the amount the RPEDISB process calculates for Pell) will not be equal. For example, if a
student was awarded with a Default Estimated Enrollment of Full Time and the student
enrolled Half Time, the award amount and calculated disbursement amount would be
different. When these two amounts differ you have the option to (N)ever disburse under
such circumstances, (A)lways disburse the calculated disbursement amount (RPEDISB
amount), or disburse the (L)esser of the award amount and calculated disbursement
amount.
If you choose to not use the New LTH Pell Calc you should populate the Default Less
Than Half Time Pell COA with the standard less-than-half time Pell COA used by the
majority of an institution’s less-than-half-time students. This amount should be a full year
2-50
Financial Aid 8.3
User Guide
Processing
January 2009
COA as the Pell Payment Schedule uses the full year COA. The RPEPELL process will
use this COA when referencing the Pell Payment Schedule Value for a student who has
been identified as less than half time. If this field is null, the Pell process will use the Fulltime Pell COA.
If the Pay Pell If System EFC and SAR EFC Are In Same Payment Cell field is not
checked, the disbursement process requires the SAR EFC and System EFC to be exactly
the same number in order for payment to occur. If you do check this field, the
disbursement process recognizes the payment cell, so that when these numbers vary
within the 100 point range of the cell, the disbursement process treats the EFC numbers as
equal values.
Check the Delete Pell Award if Zero box if you want Pell awards to be deleted from the
database if the award is reduced to 0 by the Pell calculation. The award will be deleted
only if no locks, origination, memo, authorization, or paid amounts exist. If the award has
disbursement activity on the student account it will not be deleted in order to preserve the
appropriate audit trail.
Check the Use NSLDS for Pell box if you wish to use current year Pell payments reported
on the NSLDS form (RNASLxx) from other schools. The Pell process will award Pell
based on the calculated remaining percentage of the scheduled annual award.
Pell Options Window - Enrollment Options
The Enrollment Options section contains an unlimited number of term records that you
enter in the Term Code field.
The Pell Award Enroll Option allows you to select which type of enrollment you would
like the Pell Calculation Process (RPEPELL) to use for the term code. This is a drop list
with the following values: A = Adjusted Hours, B = Billing Hours, E = Expected
Enrollment, I = Est. ISIR/FAFSA Enrl, 1=Full Time, 2=3/4 Time, 3=1/2 Time, 4=Less
Than 1/2 Time, (None).
• For the Adjusted Hours and Billing Hours the process searches for Financial Aid
Adjusted and Billing Hours (RORENRL_FINAID_ADJ_HR and
RORENRL_FINAID_BILL_HR) first. If the Financial Aid Adjusted and Billing Hours
do not exist, the process will use the adjusted or billing hours calculated from the
Student registration table (SFRSTCR).
• The Expected Enrollment for the year is the enrollment status value in the
Expected Enr Stat for Yr field on the RNANAxx form. This field is initially
populated during dataload with the value the student indicated on the FAFSA. You
can update the enrollment status directly on the Expected Enr Stat for Yr field on
the RNANAxx form.
• The “I” – Estimated ISIR/FAFSA Enrl option historically used the student
reported estimated enrollment for the term from the FAFSA. Since this information
is no longer collected on the FAFSA, institutions wishing to use this option must
populate these fields.
January 2009
Financial Aid 8.3
User Guide
Processing
2-51
The Pell Disburse Enroll Option allows you to select which type of enrollment you
would like the Disbursement Process (RPEDISB) to use for the term code. This is a drop
list with the following values: A = Adjusted Hours, B = Billing Hours, E = Expected
Enrollment, I = Est. ISIR/FAFSA Enrl, 1=Full Time, 2=3/4 Time, 3=1/2 Time, 4=Less
Than 1/2 Time, (None). (Refer to the preceding information concerning Adjusted Hours,
Billing Hours, and Expected Enrollment option.)
If you choose to use the estimated enrollment from the ISIR/FAFSA in column two or
three, use the Pell ISIR Term field to indicate which ISIR/FAFSA terms correspond with
the term. The drop list of ISIR/FAFSA terms include: Summer term (pre Fall), Fall
semester/quarter, Winter quarter, Spring semester/quarter, and Summer term (post
Spring). Since this information is no longer collected on the FAFSA, institutions wishing
to use this option must populate these fields.
For additional information about the RPROPTS form, refer to the Packaging Options form
(RPROPTS) information in Banner Financial Aid Online Help.
Aid Period Validation form (RTVAPRD)
Access this form to review the single and multiple term aid period combinations. In the
Pell Full Year Pct column enter the maximum percentage of the student’s scheduled Pell
award that a student could potentially receive if enrolled full time during each term of the
aid period. There may be more than one entry of 100%, but no entry can exceed 100%.
For additional information about this form, refer to the Aid Period Validation form
(RTVAPRD) information in Banner Financial Aid Online Help.
Aid Period/Term Rules form (RORTPRD)
This form enables you to specify the terms that you want to associate with an aid period. If
appropriate terms are not assigned to each aid period, assign the term codes to the correct
aid periods. The Pell Full Year Pct designation from RTVAPRD displays on this form.
For additional information about the RORTPRD form, refer to the Aid Period/Term Rules
form (RORTPRD) information in Banner Financial Aid Online Help.
Default Award & Disbursement Schedule Rules form
(RFRDEFA)
Enter a percentage in the Pell Award Percent column for each term in the aid period
displayed. Entry represents the portion of the Pell Full Year Pct designation from the
RTVAPRD form that a student could receive if enrolled in the term. The total of all
percentages must be at least 100% but may exceed 100%.
Example 1: A student enrolled for Fall/Spring/Summer – Fall 50%, Spring 50%,
Summer 50%. The student could get 50% of the 100% scheduled for this period on
2-52
Financial Aid 8.3
User Guide
Processing
January 2009
RTVAPRD in any of these terms if enrolled for an appropriate number of hours and
the total award has sufficient funds remaining from prior terms. The initial award will
be scheduled for 50% Fall and 50% spring. Up to 50% for Summer will be awarded
only if sufficient unused funds exist after Fall and Spring have been awarded.
Example 2: A student enrolled for Spring Only – Spring 100%. The student could get
100% of the 50% scheduled for this period on RTVAPRD.
Fund Award and Disbursement Schedule Rules form
(RFRASCH)
Use the RFRASCH form to enter award and disbursement schedules for a specific Pell
fund code.
Enter a percentage in the Pell Award Percent column for each term in the aid period
displayed. Entry represents the portion of the Pell Full Year Pct designation from the
RTVAPRD form that a student could receive if enrolled in the term. The total of all
percentages must be at least 100% but may exceed 100%.
Example 1: A student enrolled for Fall/Spring/Summer – Fall 50%, Spring 50%,
Summer 50%. The student could get 50% of the 100% scheduled for this period on
RTVAPRD in any of these terms if enrolled for an appropriate number of hours and
the total award has sufficient funds remaining from prior terms. The initial award will
be scheduled for 50% Fall and 50% spring. Up to 50% for Summer will be awarded
only if sufficient unused funds exist after Fall and Spring have been awarded.
Example 2: A student enrolled for Spring Only – Spring 100%. The student could get
100% of the 50% scheduled for this period on RTVAPRD.
Federal Rules Inquiry form (RPIFEDR)
Access this form to review the federal rules for Pell delivered by SunGard Higher
Education.
Class Code Translation Rules form (RPRCLSS)
The Class Code Translation Rules form is used to associate a student level code and class
code to a financial aid class code. The financial aid class code is the Banner Year in
College as a result of converted EDE values.
Equate Student System level and class codes with a Financial Aid class code that results in
an appropriate annual loan limit. First year student class levels can be equated with a
financial aid class code 1 (1st time freshman, no prior college) or 2 (Freshman, prior
college) to indicate freshman status.
January 2009
Financial Aid 8.3
User Guide
Processing
2-53
New students do not have a Student System class code if they have not had any courses
accumulated in academic history. Therefore, you must define a rule for the class code
translation in which the Student System class code is null (blank). To do this, create a rule
for the condition in which the Student System Level field is undergraduate and the
Student System Class field is blank; use a Financial Aid class code of 1 to indicate a
freshman. Create a similar rule for graduate students with a Financial class code of 7 to
indicate a 1st year graduate or professional.
For additional information about the RPRCLSS form, refer to the Class Code Translation
form (RPRCLSS) information in Banner Financial Aid Online Help.
Pell Procedures
Batch Pell Awards
The Pell award may be awarded online, or in batch, by the RPEPELL Process. See the Pell
Processing section for how the award is calculated.
Batch grouping to assign budget groups and components does not initiate the Pell award
process. The RPEPELL process must be run to assign Pell Awards to any students who
were assigned budgets using the batch process (RORGRPS). RPEPELL automatically
runs online to account for EFC recalculations, budget and aid period changes and after
changes are made to FAFSA data that would impact the Pell award. You can run
RPEPELL for all students or you can run the process using a population selection.
Override a Bachelors Degree
Check the Post BA Pell OVRD field in the Packaging Group Information window of the
award form (RPRAWRD, ROARMAN, or RPAAPMT) to award Pell Grants to Teacher
Certification and other students with a previous Bachelor's degree who may qualify for
Pell under federal regulations.
Manual Adjustments to Pell Grants
Once awarded, if you need to make any manual changes to the Pell award you will need to
access the Fund Awards By Term Window. You may only change the award amount, not
the distribution percent. Keep in mind the distribution percent takes into consideration the
aid period and the term award percents. Once you change an award manually you will get
a dialogue box requesting you confirm your changes. Once you have committed your
manual changes you must lock the award so that it is not recalculated if the RPEPELL
Process is run on this student again.
2-54
Financial Aid 8.3
User Guide
Processing
January 2009
Why and How to Lock Pell Grants
In the past schools manually adjusted Pell awards to account for Pell received at another
school. Once the manual change was complete, you would lock the record. Banner now
allows the use of NSLDS data to dynamically calculate the correct Pell award. So locking
the record is no longer necessary for this purpose.
Also schools used locks when manually awarding summer terms, but now the Pell
calculation correctly awards a summer session without manual modifications, or the need
for locks. Locks are still available in Banner Financial Aid for exception cases.
Lock Types
There are 2 types of locks in Banner — the Y lock and the E lock.
• A Y (always pay) value in the Lock field locks the award and pays what has been
awarded, without exception.
• An E (adjust for lower enrollment status) value in the Lock field pays the amount
awarded unless the student's enrollment drops at the time of disbursement; if
enrollment drops, the amount calculated at the time of disbursement is paid.
Warning
If you make a manual change to an award and place an E lock on the
award, make sure that you have also manually changed the enrollment
on the Funds Award By Term Window to correspond with the new award.
This is necessary because with an E lock, the Disbursement Process
checks the enrollment level at the time of disbursement and compares
this to the enrollment level at the time of awarding when determining if
enrollment has dropped and if it should pay the calculated disbursement
amount or the award amount. So if you make a manual change and use
an E lock, make sure that you manually adjust the enrollment level to
„
correspond with the manually adjusted award amount.
Fund Locks
A fund lock is placed on the first window of the award form (RPAAWRD, RPAAPMT, or
ROARMAN) in the Lock field. If you place a Y or an E lock in this field and will apply to
all term awards within the aid period. See the preceding text for information on using a Y
or E type lock.
Term Locks
A term lock is placed on the Fund Awards by Term window of the award form in the Term
Lock field. A Y or an E lock may be placed in this field and will apply to only the term for
which the lock has been placed. The term lock allows you to lock one term in the aid
period, but not another. For example, if you have a student who attends a Fall/Spring aid
period and is undergraduate Fall and graduate Spring, you can award the Fall as an
January 2009
Financial Aid 8.3
User Guide
Processing
2-55
undergraduate and lock the award, correctly update the spring grade level to graduate, and
allow the process to remove the Pell award for the Spring only.
Note
Both fund and term locks may be used for all funds, however the E type
lock works only for Pell funds. In addition, at this time, term locks on non„
Pell funds work the same as fund locks.
Lock Functionality
• Packaging (RPEPCKG) and Pell Awarding (RPEPELL) do not update awards with
a fund lock of Y or E for Pell and non-Pell funds.
• Packaging (RPEPCKG) and Pell Awarding (RPEPELL) do not update awards with
a term lock of Y or E for Pell and non-Pell funds.
• Disbursement (RPEDISB) for non-Pell Funds always pay the locked value for a
fund or term lock - whether the lock is Y or E.
• Disbursement (RPEDISB) for Pell with a fund or term lock of Y always pay the
locked value.
• Disbursement (RPEDISB) for Pell with a fund or term lock of E adjust downward
if the enrollment has dropped from the time the Pell was awarded.
Updating Award Amounts to Agree with Actual
Disbursement Amounts
Use the procedure that follows if your institution needs to update the Pell awards to more
accurately reflect the Pell disbursement amounts.
The Pell Calculation Process (RPEPELL) may be re-run with the same enrollment option
as disbursement to more accurately reflect what has been paid. This allows any unused
eligibility to be awarded to the student for the terms that follow.
1. Run the Pell Calculation Process (RPEPELL) with a set awarding enrollment option
on the Packaging Options form (RPROPTS). Set the Pell Award Enrollment Option
on the Pell Options window to default Full Time, use Est. ISIR/FAFSA, etc.
2. Run Disbursement (RPEDISB) with a set enrollment option for disbursement. Set the
Pell Disbursement Enrollment Option on the Pell Options window of the
Packaging Options form (RPROPTS) to Adjusted Hours, Billing Hours etc.
3. Institution’s Drop/Add period is over, enrollment is stable.
4. Institution changes the Pell Award Enrollment Option on the Packaging Options
form (RPROPTS) to match the Pell Disbursement Enrollment Option for a given
term.
2-56
Financial Aid 8.3
User Guide
Processing
January 2009
5. Institution runs RPEPELL. Now that enrollment is pulled from the same place for
both awarding and disbursement, this allows for any unused Pell to be awarded to the
student in a following term.
The above procedures allow for the following.
• A student is assigned a Fall/Spring/Summer aid period and the Pell award percent
is 50/50/50 on either the RFRDEFA or RFRASCH form for the Pell fund.
• The Pell Award Enrollment Option on the Packaging Options form is set to
Default Full Time. The Pell Awarding Process awards $2025 Fall, $2025 Spring
and $0 Summer.
• The student subsequently is enrolled half-time for Fall. The Disbursement
Enrollment Option for Pell on the Packaging Options form is set to Adjusted
Hours, so Disbursement uses Adjusted Hours. The Disbursement results are: Fall,
part time, $1013; Spring, full time, $2025; and Summer, full time, pays remaining
eligibility of $1012 (assuming the Pay Pell If Disbursement Amount Differs
From Award Amount field is set to Always or Lesser).
Note
Institutions that do not have a need to have award amounts match
disbursement amounts may stop here. Schools that would like awards to
more accurately reflect what is disbursed and show an award for summer
„
may proceed.
• Update the Pell Awarding Enrollment Option on RPROPTS to Adjusted Hours
(same as disbursement). Re-run RPEPELL, which awards Fall $1013, Spring
$2025, and Summer $1012.
Warning
Keep in mind that awarding and disbursement are snapshots of
information at a point in time. Institutions must decide the best time for
their institution to take these snapshots. For example an institution may
setup Fall, Spring and Summer awarding for Pell using estimated Full
Time enrollment. After drop/add for the Fall term, change the Fall Pell
enrollment option to Adjusted Hours and re-run Pell (RPEPELL). After
drop/add for the Spring term is over, adjust Pell awarding enrollment
option to Adjusted Hours and re-run Pell. The same changes could be
made for Summer. Also factor in if your institution freezes enrollment or
not. Note: Some institutions may opt to change both Fall and Spring
award options at the same time after drop/add for Spring and prior to the
„
start of the Summer awarding cycle.
The award amount and the disbursement amount should now match unless the EFC, COA,
or enrollment has changed between running the disbursement process and Pell. This is
why it is important to check your school’s enrollment freeze process.
The above process only changes the award amounts. The disbursement process will
disburse funds per prior term-actual disbursement amounts. In other words, this allows the
awarding process to allocate funds to the Summer term in the above example, but the
January 2009
Financial Aid 8.3
User Guide
Processing
2-57
disbursement process would pay the correct amount as long as RFRDEFA/RFRASCH is
set up correctly and the Pay Pell If Disbursement Amount Differs From Award
Amount field on the RPROPTS field is set to A - Always disburse or L - Lesser.
When identifying records, this Pell Awarding Process uses fund and term award locks. It
does not adjust awards with the lock set to Y or E, nor term awards set to a Y or E. These
were manual changes and the process will not overwrite such changes. Keep in mind
disbursement will still pay based on lower enrollment and reallocate funds to a Summer
term if the lock is set to E. This allows the correct amount to be disbursed while still
maintaining an audit trail of the manual changes you made to a Pell award.
Reducing an Award for Pell Paid at Another School in
the Same Aid Year
This functionality is similar to that used for Stafford loan funds. The only difference is that
Pell uses percentages to determine the current institution’s award amount.
For example, a student has Pell eligibility at their prior school of $900. The student was
paid $450 at the prior school (450 / 900 = 50%). The student used 50% of their Pell
eligibility for the year. The new school does a professional judgment and the student now
has Pell eligibility of $4050. At the new school the student would be eligible for the 50%
not used at the prior school (100% - 50% = 50%). The student could receive up to $2025
($4050 X 50%).
A check in the Use NSLDS for Pell field indicates that NSLDS Pell award information is
used in the calculation of Pell awards. The Pell award is reduced by any NSLDS Pell
Scheduled award percentages received at other schools in the Pell Calculation Process
(RPEPELL) and the Disbursement Process (RPEDISB).
Once the Use NSLDS for Pell field is checked, the RPEPELL Process checks to see if any
of the school codes listed in the in the School Code field of the Perkins Loan and Pell
Payment Data window of the RNASLxx form matches the Pell ID at either the institution
or campus level. If a match exists, the Pell award is calculated without factoring in the Pell
award percentage. If a match does not exist, the assumption is that another school has paid
a portion of the student Pell amount and the Pell calculation adjusts the Pell award
downward to account for the percentage received at the other school.
Handling Less-Than-Half Time for Pell More Efficiently
Previously, the Pell calculation used existing Default Less Than Half Time Pell COA on
the RPROPTS form and the Less Than Half Time COA field on the ROAPELL form
when calculating Pell awards for students who were enrolled for less-than-half-time status
in a term. These amounts were manually calculated and updated by the user on the
Packaging Options (RPROPTS) and Applicant Pell Grant (ROAPELL) forms,
respectively.
2-58
Financial Aid 8.3
User Guide
Processing
January 2009
The calculation of Pell less-than-half-time budgets has been automated through the
addition of a Use for < ½ Pell field on the Budget Components Validation form
(RTVCOMP). With this indicator, you can specify which budget components from a
student’s full time Pell budget should be included in the calculation of their less-than-halftime COA.
If no components are identified on the Budget Components Validation form (RTVCOMP),
and the Use New Pell Less than Half Time Calculation indicator is not checked on the
ROAINST form, the process continues to look at the values on the Applicant Pell Grant
form (ROAPELL), Less Than Half Time COA, and then Default Less Than Half Time
Pell COA on the Packaging Options form (RPROPTS).
Warning
The Pell Less than Half Time COA is not be updated if the student’s
Pell award is locked with a value of Y or E. The same applies to a term
„
lock of Y or E.
If you choose to have the system dynamically calculate the Less than Half Time COA
the system enters this value into the Less than Half Time COA) on ROAPELL. Any
manual updates to this field are overwritten by the RPEPELL process, once any
RTVCOMP component is checked. So once you decide to dynamically calculate the Less
than Half Time COA, remember no manual updates may be made on ROAPELL. If you
do not like the COA calculated you must update the budget on RBAABUD to allow for a
correct calculation.
The RTVCOMP components are not be used by the RPEPELL Process if the indicator for
Less Than Half Time Pell is not set on the ROAINST form.
Controlling when the Pell Calculation Process is Run
You can set an indicator to prevent the Pell Calculation Process (RPEPELL) from
executing automatically, either for an individual student, a group of students, a campus, or
an institution.
For example, you might want to run RPEPELL for continuing students, but delay running
the process for new students for a period of time. In this example, use a population
selection and the Batch Posting Process (RORBPST) to check/uncheck the Prevent
Automatic Pell Calculation indicator. For an individual student, you may check/uncheck
the Prevent Automatic Pell Calculation indicator on the Applicant Status form
(ROASTAT).
Additionally, Pell processing may be controlled at the campus level. Some schools may
have a campus that is strictly Graduate and therefore does not need Pell to run for that
campus. The Prevent Automatic Pell Calculation indicator is updated for individual
campuses through the Campus/EDE Defaults window on the Institutional Financial Aid
Options form (ROAINST).
January 2009
Financial Aid 8.3
User Guide
Processing
2-59
Finally, for a non-U.S. school you may choose to turn Pell off for the entire institution by
checking the indicator in the Institutional Defaults window on the Institutional Financial
Aid Options form (ROAINST).
The information that follows describes how the Prevent Automatic Pell Calculation
indicator will impact the running of the Pell process if checked.
ROASTAT Student Level is Checked:
• the student will not be picked up in a batch run for RPEPELL
• the forms will not automatically run RPEPELL for this student
• running a Needs Analysis calculation will not run RPEPELL for this student
• if the student is in a population selection used with a batch run of RPEPELL, the
process will calculate Pell for the student
• RPEPELL can be run directly from ROAIMMP for the student
ROAINST Campus Level is Checked:
• the students in this campus will not be picked up if RPEPELL is run in batch
without a population selection
• the forms will not automatically run RPEPELL for students in this campus
• running a Needs Analysis calculation will not run RPEPELL for students in this
campus
• if a student from this campus is in a population selection used with a batch run of
RPEPELL, the process will calculate Pell for the student
• RPEPELL can be run directly from ROAIMMP for students in this campus and the
process will calculate Pell for them.
ROAINST Institutional Level is Checked:
• all students will not be picked up if RPEPELL is run in batch without a population
selection
• the forms will not automatically run RPEPELL for any student
• running a Needs Analysis calculation for any student will not run RPEPELL
• if a student is in a population selection used with running RPEPELL in batch, the
process will calculate Pell for the student
• RPEPELL can be run directly from ROAIMMP for any student and the process
will calculate Pell for them.
2-60
Financial Aid 8.3
User Guide
Processing
January 2009
Setup Procedure for Multiple Pell Fund Codes
1. Set up separate Pell funds on RFRBASE.
2. Set up the default Pell code in the Pell Fund Code field on the Defaults window of
the Institution Financial Aid Options form (ROAINST).
3. Identify which campuses have a Pell fund code different from the default and
populate the correct campus with the corresponding Pell code in the Pell Fund Code
field on the Campus/EDE Defaults Window of the Institution Financial Aid Options
form (ROAINST).
4. Create and review carefully any special award schedules for Pell on RFRASCH.
Note
Keep in mind if a student is assigned multiple Pell fund codes within an
aid year, the default award schedule is used. Review RPEPELL and
„
RPEDISB documentation.
5. Once students are assigned to a specific campus and RPEPELL is re-run, the process
automatically awards the correct Pell fund code for each term for the student.
6. Disbursement does not determine which Pell fund code is assigned as this is done in
awarding (RPEPELL). Remember that if a student changes campuses, you must rerun RPEPELL to get the new campus Pell fund code to award.
Note
If you setup multiple Pell fund codes on RFRBASE you must go back to
prior years and populate the ROAINST form with the Pell Fund code used
for those years in the Institutional Defaults Window. This is necessary
because RFRBASE is not an aid year specific form. Otherwise if you
attempt to recalculate Pell for the prior years you will get the following
„
error message: Cannot Determine Default Pell Fund Code.
Pell Process (RPEPELL) for Pell Processing
The following functionality is included with Pell/Multiple Pell fund codes.
Option to Delete Zero Pell Awards.
Previously, once a Pell award existed for a student, the RPEPELL process would not
remove the award records from Banner, even if a recalculation resulted in a zero dollar
award amount.
The Delete Pell Award If Zero field in the Pell Options window of the RPROPTS form
now allows you to have RPEPELL delete awards if the awards are reduced to zero by
January 2009
Financial Aid 8.3
User Guide
Processing
2-61
RPEPELL. This option controls the deletion of award records when a Pell award is
reduced to zero -- whether a school uses a single Pell code or multiple Pell fund codes.
If the option is checked and the Pell award record is reduced to zero AND the following
are all true:
• the award memo amount is null,
• the authorized amount is null,
• the paid amounts are null,
• the award is not locked,
• the award has no term locks set,
• no Origination record was created for the award,
then the award records on the award forms (RPRAWRD, RPRATRM, RPRADSB) are
deleted for that award. Otherwise, the award records remain in Banner as previously.
Note
There is one exception to the Delete Pell Award If Zero checkbox. Even
when this new indicator is checked (delete $0 Pell awards), if a $0 Pell
award is created as a result of an NSLDS default, then the $0 Pell award
remains on the student’s award. This allows you to override on a term-by„
term basis the NSLDS default, if appropriate.
Recognizing Co-Existence of Multiple Pells For Same
Student Simultaneously.
The RPEPELL process recognizes the co-existence of multiple Pell funds on the same
student at the same time. The RPEPELL process combines the totals of any funds where
the Federal Fund ID is PELL. This means that if a student has two different Pell awards on
their account simultaneously, the RPEPELL process totals the awards together for
determining the correct amount for each term as well as for the entire year.
Multiple Pell award fund codes may exist for a student in an aid year. However, for any
term within that aid year, no more than one of those Pell awards will be allowed to have a
non-zero offer amount.
If multiple Pell Fund codes exist, the process to determine the appropriate Pell fund code
to be assigned follows the same hierarchy to be used when determining which Pell rules to
use when originating Pell records. This hierarchy is as follows:
1. Look to the General student record (SGBSTDN) to see in which campus the student
is enrolled.
2. If a Pell fund code has been added to the Campus/EDE Defaults window of
ROAINST for the student’s campus, use that Pell fund.
2-62
Financial Aid 8.3
User Guide
Processing
January 2009
3. If that campus does not have a Pell fund code defined on the Campus/EDE Defaults
window, use the default Pell fund.
4. If the school does not define a default Pell fund code on ROBINST, and there are
multiple Pell funds, do not award Pell. Instead, an error message prints to the log file
indicating that the Pell fund to be used cannot be determined.
5. However, if there is only one Pell fund defined on RFRBASE, award that fund to all
students who are eligible for Pell, as the process has always done in the past.
The above allows for students who have applied for admission but have not yet been
admitted to a campus to be awarded the default Pell. Once the student has been admitted to
a specific campus and RPEPELL is re-run, the Pell fund code for the assigned campus is
now awarded and the default Pell fund code is zeroed out. If the Delete Pell Award If
Zero is set to Y, the default fund is removed.
Locked Records
Fund or term locks still prevent changes to Pell award records. If a term lock exists, the
terms that are not locked may be awarded a different Pell fund code, which will result in a
$0 award amount for the locked term for the new Pell fund code. The non-zero award for
the locked term remains under the prior Pell fund code.
Rounding Option
If only one Pell fund code exists, the rounding option selected for that fund code on
RFRMGMT is utilized. If multiple Pell fund codes exist, the rounding option selected is
the rounding option on RFRMGMT for the default Pell fund code from ROAINST.
Offered or Auto Accepted
Offered or Auto Accept status is reviewed on a term-by-term basis per the fund code rules
setup on RFRMGMT for the Pell Fund Code awarded for that term.
Award Schedules
If only one Pell fund code exists, the RFRASCH schedule from that fund code is used if it
exists -- otherwise RFRDEFA. If multiple Pell fund codes exist for the aid period, the
RFRASCH schedule is used for the default Pell Fund Code on ROAINST -- otherwise
RFRDEFA.
Award Change Letter Indicator
If no Pell previously existed on the student award, but one or more is now being created
and any of the Pell fund codes for this student have award letter indicators set to Y, the
RORSTAT Award Letter flag is set to Y.
January 2009
Financial Aid 8.3
User Guide
Processing
2-63
If a Pell award previously existed for the student, and the new total award amount for all
Pell fund codes is different from the previous total award amount for all Pell funds, and if
any previous or new fund codes has the award letter indicator set to Y, the Award Letter
flag is set to Y.
Finally, if the Pell award previously existed for the student, but the Pell award now rejects,
and any of the fund code award letter indicators is set to Y, the student Award Letter flag is
updated to Y.
Disbursement Process (RPEDISB) for Pell Processing
Disbursement functionality for Pell / Multiple Pell fund codes is as follows.
Recognizing Multiple Pell Funds
The process combines the total of any funds with a Federal Fund ID of PELL. This means,
for example, if a student has two different Pell awards on their account simultaneously, the
process totals the awards for determining the correct amount for each term as well as for
the entire year.
Note
The Disbursement Process does not try to determine the correct Pell fund
to use for the student based on which campus he attends, but instead
pays whichever Pell fund code is awarded for the student for that term.
„
RPEPELL determines which Pell fund to use, not RPEDISB.
Back Out of Memo, Authorizations, and Disbursements
Support for multiple Pell funds requires that the same student cannot have two different
Pell funds in any state of payment (memo, authorization, or paid) in the same term
simultaneously. It is possible, however, that a student may be having aid reversed or
backed out at the same time the school wants to disburse a different Pell fund.
The disbursement process backs out memos, authorizations, and disbursements for Pell
awards whose term award has been reduced to zero, regardless of any Pell disbursement
option settings on RPROPTS. Pell awards with a zero term offer amount are processed
before Pell awards with non-zero term offer amounts. This ensures that disbursements
back out correctly, prior to attempting disbursement on the new Pell award.
In order for the disbursement process to work correctly, schools that disburse aid awards
by fund must include all Pell funds in the same run of the disbursement process. This
permits the back out of memo, authorization, and payment amounts for term awards that
have been reduced to zero, so that new, non-zero term award amounts can disburse.
2-64
Financial Aid 8.3
User Guide
Processing
January 2009
Use Disbursement Enrollment Edits for Memo Option
For Pell Processing -- regardless of how the Use Disbursement Enrollment Edits for
Memo field is set -- the RPEDISB process treats the Use Disbursement Enrollment
Edits for Memo as (checked) Y for Pell. This prevents Pell from overawarding when
memoing, authorizing, and disbursing. This is done for one Pell fund code as well as
multiple Pell fund codes. When no registration records exist for a student for a particular
term, the disbursement process will create a memo for Pell using the term's Pell Award
Enrollment options which are set up on the RPROPTS form.
RPEDISB Process Reports.
The Disbursement Reports use the Award Fund Code for all reports for all funds. This
allows each Pell fund code to be listed separately on the reports.
Pell Processes
This section provides you with a description of each process and report that is associated
with calculating Pell. It is important to remember that the Pell award is calculated both at
the time of awarding and at the time of disbursement. These two calculations are then
compared, and based on your option in the Pay Pell If Disbursement Amount Differs
From Award Amount field in the Pell Options window of the Packaging Options form
(RPROPTS), determines how much Pell to disburse to the student. The options for this
field are as follows.
Never — will not disburse any Pell Funds if the award amount and the calculated
disbursement amount differ.
Lesser Amount — will pay the lesser of the award amount or the calculated
disbursement amount.
Always Disburse — will always pay the calculated disbursement amount.
Essentially the calculation is the same at the time of awarding as it is at the time of
disbursement, but the process uses enrollment as a separate option for awarding and
disbursement. The process may or may not be calculating with different enrollment levels
since the calculation is dependent on your Pell Award Enrollment Option and Pell
Disbursement Enrollment Option in the Pell Options window of the Packaging Options
form (RPROPTS).
For example, many standard full-time schools may choose to award with a default of Full
Time, yet will only disburse with Billing or Adjusted Hours. Review the options for your
institution and review the preceding Updating Award Amounts to agree with Actual
Disbursement Amounts section. This section discusses how to change your enrollment
options at specific times of the year to ensure that both awarding and disbursement
ultimately utilize the same enrollment option.
January 2009
Financial Aid 8.3
User Guide
Processing
2-65
Pell Calculation Process (RPEPELL)
The Pell Calculation process performs the following functions:
• Calculates a Pell award based on the Pell Grant Payment Schedule table
(RORPELL) or the Pell Grant Alternate Payment Schedule table (RORAPEL). Pell
awards are calculated outside of the normal Packaging process, due to their special
requirements.
• This process uses the enrollment option for awarding on the RPROPTS form. The
Attending Hours will be calculated for the number of hours which the student is
attending if Use Attending hours has been indicated on the RFRMGMT form.
• Online, the Pell Awarding process is performed whenever the Pell EFC, the Pell
budget, the estimated enrollment level, or the aid period changes for an applicant
— unless the Prevent Pell Calc field is checked on the ROAINST or ROASTAT
form.
• In batch mode, all applicants with records on the Applicant Status table
(RORSTAT) will be processed.
• The Pell award may be auto-accepted on RFRMGMT, or may be accepted once a
SAR is received. Once a valid SAR Certified date is entered on ROAPELL, the
offered Pell grant will be accepted. A Pell award cannot be accepted manually.
Note
Parameters are automatically created by the forms that call this process
(RBAABUD, RNANAxx, RNAOVxx, RNARSxx, RNASUxx, RNAVRxx,
ROAIMMP, ROAPELL), or are created manually through the GJAPCTL
„
form.
Refer to the Reports and Processes Chapter of this User Guide for further information
regarding the Pell Calculation Process (RPEPELL).
Pell Grant Award Calculation
The Pell Grant Award Calculation section provides you with the Pell awarding
calculations and demonstrates the calculations with examples using Banner.
Pell Grant calculations are based on the Pell Grant Schedule published by the Department
of Education for determining scheduled awards for the award period. These payment
amounts change for each award year but are always determined by the full-time Cost of
Attendance and Expected Family Contribution grid. The contents of this grid are stored in
the Banner RORPELL table or Banner RORAPEL table for Alternate Pell Payments and
used in Pell Grant award and disbursement calculations.
Note
Alternate Pell Schedule functionality has been disabled - beginning with
„
the 2007-2008 and 2008-2009 aid years.
2-66
Financial Aid 8.3
User Guide
Processing
January 2009
Pell award enrollment is determined by the enrollment option for awarding on the
RPROPTS form. The enrollment is also determined based on the enrollment hours the
student is currently attending if the Use Attending hours indicator has been selected on the
RFRMGMT form.
Pell Grant Award Calculation
The Pell Grant award is calculated within Banner in the following manner.
1. Maximum Dollar Award for Aid Period
(Pell Full Year Pct field on the RTVAPRD form) x (Full-Time, Full Year
Scheduled Amount)
2. Term Amount
(Pell Award Percent field for the term on the RFRDEFA or RFRASCH form) x
(term enrollment full year amount x Pell Full Year Pct amount on the
RTVAPRD form)
3. Remaining Pell Dollars
Maximum Dollar Award for Aid Period - Prior Term Award(s)
4. Term Award
Lesser of Term Amount and Remaining Pell Dollars
Example
Aid Period: Fall/Spring/Summer. Pell Full Year Percent field on RTVAPRD = 100%
Pell Award Percent field on RFRDEFA = 50% Fall; 50% Spring; 50% Summer
Student Packaged using Full Time Estimate on RPROPTS
EFC = 0
Full Time Pell = 4050
¾ Pell = $3038
½ Pell = 2025
Maximum $award for aid period:
100% x 4050 = 4050 (a)
January 2009
Financial Aid 8.3
User Guide
Processing
2-67
Fall Term Award Calculation:
50% x 4050 = 2025 (b)
4050 (a) - 0 = 4050 (c)
lesser of 2025 (b) or 4050 (c) = (d)
d = term award 2025
Spring Term Award Calculation:
50% x 4050 = 2025 (b)
4050 (a) - 2025 = 2025 (c)
lesser of 2025 (b) or 2025 (c) = (d)
d = term award 2025
Summer Term Award Calculation:
50% x 4050 = 2025 (b)
4050 (a) - 4050 = 0 (c)
lesser of 2025 (b) or 0 (c) = (d)
d = term award 0
**Total Initial Award for the aid period is $4050 ($2025 for Fall, $2025 for Spring, and $0
for Summer)**
Example #1 (continued)
Student above actually registers for ¾ Time Fall, Full-Time Spring, & wants to register for
Summer next week. The student is paid Pell based on the adjusted hours and receives
$1519 for Fall & $2025 for Spring
School Changes Awarding Option for Pell on RPROPTS to Adjusted Hours for Fall &
Spring. This will allow any unused Pell from the Fall and Spring terms to be calculated
and awarded for the Summer term. When RPEPELL is performed the Pell Award for the
student is adjusted accordingly.
Maximum $award for aid period:
100% x 4050 = 4050 (a)
Fall Term Award Calculation:
50% x 3038 = 1519 (b)
2-68
Financial Aid 8.3
User Guide
Processing
January 2009
4050 (a) - 0 = 4050 (c)
lesser of 1519 (b) or 4050 (c) = (d)
d = adjusted term award 1519
Spring Term Award Calculation:
50% x 4050 = 2025 (b)
4050 (a) - 1519 = 2531 (c)
lesser of 2025 (b) or 2531 (c) = (d)
d = adjusted term award 2025
Summer Term Award Calculation:
50% x 4050 = 2025 (b)
4050 (a) - 3544 = 506 (c)
lesser of 2025 (b) or 506 (c) = (d)
d = adjusted term award 506
**Total Adjusted Award for the aid period is now $4050 ($1519 for Fall, $2025 for
Spring, and $506 for Summer)**
Pell Grant Disbursement Calculation
All normal Pell Grant calculations are based on the Pell Grant Schedule published by the
Department of Education for determining full-time scheduled awards for the award
period. These payment amounts change for each award year but are always determined by
the full-time Cost of Attendance and Expected Family Contribution grid. The contents of
this grid are stored in the Banner RORPELL table or Banner RORAPEL table for
Alternate Pell Payments and used in Pell Grant award and disbursement calculations.
Note
Alternate Pell Schedule functionality has been disabled - beginning with
„
the 2007-2008 and 2008-2009 aid years.
You will notice that the Pell Disbursement Calculation is very similar to the Pell Awarding
Calculation. The Pell Grant disbursement is calculated within Banner in the following
manner.
1. Full Year Maximum Dollar Amount
(Pell Full Year Percent field on the RTVAPRD form) x (Full-Time Full Year
Scheduled Amount)
January 2009
Financial Aid 8.3
User Guide
Processing
2-69
2. Term Amount
Pell Award Percent field on the RFRDEFA or RFRASCH form x Full Year
maximum dollar amount per enrollment level = A
3. B = Total paid amount for other terms in aid period (excluding term being disbursed)
4. Calculated Amount
If A + B > Full Time Full Year award:
Calculated term amount = FTFY award - B
Otherwise
Calculated term award = A
Disbursement Example
Aid Period: Fall/Spring/Summer Pell Full Year Percent field on RTVAPRD = 100%
Pell Award Percent field on RFRDEFA = Fall 50%; Spring 50%; Summer 50%
The sum of the Pell Award Percent fields on the RFRDEFA or RFRASCH form = 100%
Disbursement Option on RPROPTS set to ‘A’djusted Hours
Enrollment: ¾ Fall, FT Spring, FT Summer EFC = 0
Scheduled Pell: Full Time= 4050
¾ Time = 3038
½ Time = 2025
Fall Term:
1. 100% X 4050 = 4050
2. 50% x 3038 = 1519 = A
3. 0 = B
4. 1519 + 0 is not > 4050
Fall Term Disbursement: $1519.00
Spring Term:
1. 100% x $4050 = 4050
2. 50% x 4050 =2025 = A
2-70
Financial Aid 8.3
User Guide
Processing
January 2009
3. 1519 = B (prior disbursements)
4. 2525 + 1519 is not > 4050
Spring Term Disbursement: $2025.00
Summer Term:
1. 100% X 4050 = 4050
2. 50% x 4050 = 2025 = A
3. 3544 = B (prior disbursements)
4. 2025 + 3544 is > 4050
Therefore: Calculated term award = FTFY 4050 – (B) 3544 = 506
Summer Term Disbursement: $506
Need Analysis and EDE Correction
Logging
Banner stores changes to need analysis data in a special log table that can be used as an
audit trail. The same method of logging is used for storing changes for EDE correction
processing. To successfully log data changes for EDE, you must activate three levels of
control switches:
• The first level is the institutional level. EDE correction logging must be activated
by checking the appropriate option on the Institution Financial Aid Options form
(ROAINST) for the aid year.
• The ROAINST option controls the default value for the EDE Correction switch in
the Key Block section of the Need Analysis form (RNANAxx). This switch must
also be set to Yes in order to log changes for Pell EDE.
If you do not log the changes, this flag must be set to N each time upon entering the
RNANAxx form.
• The third level is the individual field level. This is the EDE correction indicator on
the Data Log Rules form (RORDATA) for the field that is being changed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-71
Warning
This is delivered data by SunGard Higher Education, and should not be
„
changed by the user.
Note
For example, if you set the default value on ROAINST = Y, and you do not
wish to log changes for a particular student, set the flag = N in the Key
Block of RNANAxx. However, if the value on ROAINST = N, no EDE
„
changes will be logged.
Under this method of logging Need Analysis or Pell corrections, the form stores the
changes in temporary tables (that is, RLRAPP1, RLRAPP2, RLRAPP3, RLRAPP4,
RLRSTAT). You must run another process to move the data from the temporary log tables
to the permanent log tables (ROBALOG). You must use the RLRLOGG process. Once
this process is completed, the changes can be viewed on either the Applicant Data Log
form (ROIALOG) or the Data Log Inquiry form (ROIILOG). Execute the REBCDxx
Process to create the EDE correction file after you move the data to the permanent log
tables.
The date/time stamp on the audit log record is the date and time that the information was
changed if it is data from the RCRAPP1 or RORSTAT tables. It is the date/time that the
RLBLOGG process was run if the changed data was from the RCRAPP2 table.
Warning
SunGard Higher Education delivers the settings on RORDATA each year
according to which fields can have changes reported and those that
cannot. It is recommended that users do not alter any settings on the
„
RORDATA form.
The Applicant Data Log Application form (ROAALOG) allows schools to resend EDE
corrections that were rejected simply by setting a checkbox. When this checkbox (Resend)
is set and saved, it triggers the nulling out of the ROBALOG_EDE_DATE_SENT field when you
commit.
You can only use this checkbox when PELL_CORRECTION has a value of Y.
Note
Batch Ind, Change Status, Rej Code and Description are not used in
conjunction with EDE Corrections processing.
This form can also be used for Direct Loans.
„
Processing EDE Corrections
To create correction records for EDE, you must activate Pell corrections on the
Institutional Options form (ROAINST). To complete the logging process for need analysis
changes you also must run the RLRLOGG process. Pell corrections pending submission to
2-72
Financial Aid 8.3
User Guide
Processing
January 2009
the Central Processing System (CPS) can be displayed on the ISIR Correction/Request
form (REACORR). Unnecessary corrections can be deleted here and missing or incorrect
Pell IDs can be changed. The actual data that you send to the CPS cannot be changed on
this form. The ISIR Request window of the REACORR form can be used to request
duplicate ISIRs for individual students and also to report Institution Changes. All three
types of changes - History Corrections, Institution Changes, and Duplicate Requests - are
handled by the REBCDxx process.
The ROAALOG form can also be used to flag EDE corrections that have been previously
extracted that for some reason must be resubmitted. By setting the Resend checkbox on
this form, this EDE data will again be logged as a correction and extracted to be sent the
next time the REBCDxx process is run.
REBCDxx will create an output file if necessary; CORRxxIN.DAT will contain the history
corrections, and duplicate ISIR requests, if any are ready to process. This filename
matches the default filename used by the Title IV WAN communications software
(EdConnect).
To run REBCDxx, you must use Job Submission to enter your parameters. They include:
January 2009
Parameter
Value
01
Aid Year Code
Current Aid Year
02
Resend Prev
Processed Records
Allows you to include previously transmitted
corrections
03
Resend for Prior Date
If previous parameter is Y, identifies which ones to
resend
04
Application ID
General area for which the selection ID was defined
05
Selection ID
Code identifying the sub-population being worked with
06
Creator ID
ID of the person creating sub-population rules
07
User ID
ID of the person using the sub-population rules
08
Resend for
Prior Date/Hour
Financial Aid 8.3
User Guide
Processing
2-73
Parameter
Value
09
Resend for
Prior Date/Minute
10
Send with
Discrepant Trans #’s
Send corrections when current ISIR Trans # differs
from number on Applicant status
11
Destination ID
The last five characters of the alternate TG# if different
than TG# listed on ROAINST.
After the program has completed you need to transfer the output file, corrxxin.dat, from
your mainframe to your PC by using a transfer utility that will not change the file's
contents. If you use Kermit, you typically use the binary file transfer option. If you use
FTP, you typically also use the binary option.
Methodology Specific Changes
Methodology-specific changes as handled on the Applicant Need Analysis Override
window of the Applicant Override form (RNAOVxx) are as follows. Regardless of your
preferred methodology (IM or FM), you can override the IM or FM formulas. Both
columns are always displayed and you can select any combination. If both methodologies
are selected, you will get the same results as if you had just made the change once on the
Applicant Need Analysis form (RNANAxx), which by default affects all formulas.
Setting a Student’s Dependency Codes
Most fields in the Applicant Override Information section of the Applicant Override form
are used as inputs to the INAS calculation. That is, the value of the field controls how
INAS performs some of its calculations. INAS must be run for the override to cause a
change in the results of the need analysis process.
The Dependency Override field will directly change the student's dependency status as
stored in the Banner database. There are two database fields that identify a student's
dependency status:
• RCRAPP2_C_DEPEND_STATUS field can contain a value from 1 to 8 where 1 =
Independent, 2 = Dependent, 3 = (Not used), 4 = Independent (documentation
needed), 5 = Independent due to professional judgement, 6 = Dependent due to
prior year data, 7 = Dependent rejected, and 8 = Independent rejected.
• RCRAPP2_MODEL_CDE field can contain a D for dependent or an I for independent.
2-74
Financial Aid 8.3
User Guide
Processing
January 2009
If you enter an I for the Change Dependency field on the Override form, Banner will set
RCRAPP2_C_DEPEND_STATUS to 1 and RCRAPP2_MODEL_CDE to I. If you enter a D on the
Override form, Banner will set RCRAPP2_C_DEPEND_STATUS to 2 and RCRAPP2_MODEL_CDE
to D.
The value will still be used as an override to INAS so the student's dependency status will
not change regardless of how the student answered the dependency questions on the
application. If there is no override present and the computed dependency status loaded in
from a CSS tape is not a 5 or 6, INAS will determine the student's dependency status based
on the applicant's responses to the dependency questions.
Selecting a Student’s Dependency Status
Most Financial Aid forms display a student's dependency status as either I for independent
or D for dependent. However, there are two database fields that contain a student's
dependency status. The value in RCRAPP2_C_DEPEND_STATUS is a number from 1 to 8 or
null. Financial Aid always converts the number to the more common I or D. The value
stored in the field RCRAPP2_MODEL_CDE is a D for dependent students and an I for
independent students. If you want to use the student's dependency status in a selection
statement to identify dependent students (which is done frequently), you could write a
statement such as:
RCRAPP2_C_DEPEND_STATUS
RCRAPP2_C_DEPEND_STATUS
is (2,6,7) OR
is null
Or you could use the following statement:
RCRAPP2_MODEL_CDE = D
The RCRAPP2_MODEL_CDE field is set to I when
RCRAPP2_C_DEPEND_STATUS
equals a 1, 4, 5, or 8. The RCRAPP2_MODEL_CDE is set
to D when
RCRAPP2_C_DEPEND_STATUS
equals a 2, 6, 7, or null.
This is performed at Data Load time, after INAS, and when dependency is changed on the
override form. These are the only ways to set or change a dependency status.
EFC Proration
There are two ways to perform an adjustment to the EFC for students not attending a
standard nine-month academic year. One method is to change the student's budget
duration on the Override form (RNAOVxx) and perform a new INAS calculation. INAS
will then calculate a new PC and SC using strict Federal Methodology rules for a student
attending more or less than the standard nine-month school year.
January 2009
Financial Aid 8.3
User Guide
Processing
2-75
Another method is to have Banner perform a proration based on the percent of year for the
student's aid period. This option is activated/deactivated on the Institutional Financial Aid
Options form (ROAINST). If this option is activated, Banner multiplies the student's PC
and SC by the percent of year for the student's aid period (displayed and updated on the
Applicant Budget form [RBAABUD]). For example, a student attending only 50% of the
year will have his PC and SC halved. Since this method of EFC proration may not meet
strict Federal Methodology rules, you should use your own interpretation of Department
of Education regulations when selecting a method for prorating EFC.
Warning
When selecting a method of EFC proration, you should use one method
or the other. For example, if you plan to adjust any student's budget
duration as an override, then your institutional option should be set to not
perform system EFC proration. You should never use both methods at the
same time. This would result in double proration which will always be
„
wrong.
When Banner performs an EFC proration, it takes the stored contributions in the
RCRAPP4 table, multiplies them by the percent of year for the student's aid period, and
stores the new values in fields in the RCRAPP2 table. Using this approach, the RCRAPP4
values always represent the full 100% results and the RCRAPP2 values always represent
the prorated results. The contributions displayed on the Need Analysis form (RNARSxx)
are the prorated values from the RCRAPP2 table. The contributions displayed on the
Calculated Need Analysis Detail Inquiry form (RNINAIQ) are the full 100% values from
the RCRAPP4 table.
If you use system EFC proration, you should always lock the SC and PC whenever you
manually adjust either contribution with professional judgement, even if you will never
perform a new INAS calculation. This is because changing the student's aid period can
also change the contributions. If the contributions are not locked and the student's aid
period changes, then Banner EFC proration will be applied to the old, unadjusted
contributions. If the contributions are locked, changing the student's aid period will not
prorate the contributions.
Values are placed in the RCRAPP4 table during Data Load and by INAS. Even if the
option to perform EFC proration is checked, it cannot be done unless there are RCRAPP4
values to prorate. In order to use system EFC proration with manually created records, you
must perform an INAS calculation after the need analysis information is entered.
Estimated vs Official Contributions
When the Need Analysis calculation encounters any of the federal reject conditions, the
corresponding contributions are labeled as Estimated rather than Official results. Federal
regulations prohibit the disbursement of Title IV funds to students until their need has
been computed based on official results. There is no such prohibition against packaging
with estimated results. Banner Financial Aid includes a user-defined option (RPROPTS)
2-76
Financial Aid 8.3
User Guide
Processing
January 2009
to control whether to permit students to be packaged when their contributions are
estimated rather than official. There is no similar option for disbursement. The following
rule could be used to prevent the disbursement of a non-Title IV fund to students with
estimated contributions:
((RCRAPP2_MODEL_CDE = I AND
RCRAPP2_C_1_CTRB_OFFL_EST = 1) OR
(RCRAPP2_MODEL_CDE = D AND
RCRAPP2_C_PAR_1_CTRB_OFFL_EST = 1 AND
RCRAPP2_C_1_CTRB_OFFL_EST = 1)) AND
RCRAPP1_CURR_REC_IND = Y
Recalculate Need Analysis Indicator
Functionality Updates
The Recalculate Need Analysis Indicator (Recalc) is set to Y when a current record has
been changed, or when the Date of Birth (DOB) has been changed. The Recalc field
displays in the Applicant Status Summary window of many forms throughout Banner. The
Need Analysis Calculation field on the Applicant Immediate Process form (ROAIMMP)
displays a Current Status value of Waiting if the Recalc field is set to Y for the ID and aid
year. The Current Status indicator for the Need Analysis Calculation field is blank if the
Recalc indicator is set to N.
Since you can change a record and then move this record to a non-current record without
running INAS, changing this same record back to a current record sets the Recalc
indicator to a Y since INAS has not been run since changes were committed to this record.
For this reason, Banner sets the Recalc indicator to Y every time a current record is
changed on the RNAOVxx form. A DOB change may impact the bottom line INAS
results in some cases. Therefore, a change to this field also sets the Recalc indicator to Y.
This field is also set depending on the parameters used during Data Load.
Requirements Tracking Procedures
Requirements Tracking Implementation
1. Define your tracking requirement codes on the Requirements Tracking Validation
form (RTVTREQ).
Think about the types of codes (that is, documents/requirements) that you would use
in your office. Examples might include: institutional applications, tax returns,
verification statements, loan applications, and so on.
January 2009
Financial Aid 8.3
User Guide
Processing
2-77
2. Define your tracking requirement status codes on the Requirements Tracking Status
Validation form (RTVTRST).
Think about different codes you would use to establish or satisfy a requirement, or to
track a document through a procedure. Examples might include: received, waived,
established, satisfied, cancelled, received incomplete.
3. Define your tracking groups on the Requirements Tracking Group Validation form
(RTVTGRP).
Think of all possible groups or combinations of students who may require a different
set of documents. Examples might include variations of graduate vs. undergraduate
documents, selected for verification documents, independent vs. dependent
verification groups, and so on.
4. Develop tracking group requirements for each group on the Requirements Tracking
Group/Requirements Rules form (RRRGREQ).
Indicate which documents are required for each specific tracking group. You can
change your defaults for a specific code from the defaults you indicated on the
RTVTREQ for the code. These defaults will only be used if Banner brings in the
requirements for the specific student. If the requirement is entered manually and the
manually entered code is not defined in the student's particular tracking group, the
default from the RTVTREQ table will appear.
5. Develop tracking group rules associated with each group on the Financial Aid
Selection Rules form (RORRULE).
Assign criteria for placing applicants into tracking groups. Use the standard Banner
data element dictionary table. Selection criteria may come from Banner Student,
Financial Aid, or any other installed Banner system.
6. Develop specific messages for each tracking code, if desired, on the Message Rules
form (RORMESG).
Budgeting Procedures
Budget Implementation
1. Access the Aid Year Inquiry form (ROIAIDY) to see all the valid aid years defined
on the ROAINST form.
2. Define valid aid periods on the Aid Period Validation form (RTVAPRD). Decide what
your 100% aid period will be: for example, a nine-month period, a twelve-month
period, or another. Define the percentage of EFC that will apply to the 100% full year.
2-78
Financial Aid 8.3
User Guide
Processing
January 2009
Add other aid periods with their appropriate full-year percents and percentages of
EFCs.
Note
The aid period code which represents the standard nine-month school
year should always be the one identified as the 100% of year code. Any
other aid period should use this one as its reference point.
For example, a semester-based school should use the aid period which
represents the Fall and Spring semesters as its 100% of year aid period
rather than one that represents Fall, Spring, and Summer. If the Fall,
Spring, and Summer aid period is used as the 100% period, and the Fall/
Spring period is 80% of a full year, then all students in the Fall/Spring aid
period will have their Pell grants multiplied by 80% even though these
students are eligible for a full grant.
In this example, the Fall, Spring, and Summer period could be defined as
120% of a full year. Students in this aid period will have their Pell grants
multiplied by 120%, but as the amount will be limited to the amount of the
„
grant in the payment schedule, the grant will never exceed 100%.
3. Define valid terms within aid periods on the Aid Period/Term Rules form
(RORTPRD).
For each aid period you defined in Step 1, you must now define the valid terms within
each aid period. Refer to the Term Validation form (STVTERM) for terms already set
up in Banner Student.
Note
The Term field of the RORTPRD will access a view of STVTERM through
„
the List function.
4. Define all valid budget components on the Budget Component Validation form
(RTVCOMP).
Review all of the possible budget components which you use in budget development.
The default indicator allows you to specify whether the component should be
automatically included in all budget groups when you define components within
groups on RBRCOMP.
If the budget component should be used to determine eligibility for the Alternate Pell
Schedule, check that box (that is, determine low tuition and fees).
Note
Alternate Pell Schedule functionality has been disabled - beginning with
„
the 2007-2008 and 2008-2009 aid years.
5. Define all valid budget types on the Budget Group Validation form (RTVBGRP).
January 2009
Financial Aid 8.3
User Guide
Processing
2-79
Review all of the valid budget types and indicate whether they are Campus,
Institutional, Pell, State, or some other budget. For example, for each budget type,
which Expected Family Contribution should be used, Federal or Institutional?
6. Define all valid budget groups on the Budget Group Validation form (RTVBGRP).
Think about all the combinations of budget groups you use. Assign a grouping priority
to each budget group.
Note
The lower the number, the higher the priority. You want to assign the
priorities so that the most populated budget group has the highest priority.
„
Doing so helps in the efficiency of the grouping process.
7. Define the valid budget types within groups on the Budget Group/Type Rules form
(RBRGTYP).
For each budget type, specify which budget types would be valid (for example, for a
graduate budget, Pell would not be a valid type). The default indicator defines which
of the valid types should be created for students in this group, in addition to the Pell
budget (if Pell is a valid budget type for the group).
8. Define budget components and the amounts associated with them for each budget
group on the Budget Component Rules form (RBRCOMP).
In this step you first need to define your 100% budgets for each combination of group,
type, and period. Then, if desired, use the Create Record function to default in
components based on varying percentages of full year.
Note
You can define the components here or the components can be defaulted
with the prorated amounts into the applicant's budget record based on the
„
aid period.
9. Use the Budget Inquiry form to view the combinations of budgets you have defined.
10. Define the group selection rules for each budget group on the Financial Aid Selection
Rules form (RORRULE).
11. Using elements from Banner, create selection rules based on the group definition. As
an example, for an undergraduate, in-state, on-campus student, your selection criteria
would look for these characteristics in order to group the student.
12. Use the Group Inquiry form (ROIGRPI) to view the budget groups which have group
selection rules associated with them and the number of students which have been
assigned to each group.
2-80
Financial Aid 8.3
User Guide
Processing
January 2009
13. Assign explanatory messages to respective budget group message codes that you
want to display on communications to the applicant on the Message Rules form
(RORMESG).
Satisfactory Academic Progress (SAP)
Processing
This process focuses on automation to meet the following objectives:
• Reduce the degree of end-user intervention in the SAP process
• Promote integration between student records and financial aid
• Provide functionality to accommodate user-defined SAP policies
This lets you use a group assignment-like process within Banner to assign SAP codes to
student records, along with the automatic posting of a letter code to the GURMAIL Table
for use in Letter Generation. There is also flexibility allowed in the definition for which
fund sources the user can restrict packaging and disbursement activity.
The functionality that is available with the RORRULE form to write both simple and
complex rules lends itself directly to the Satisfactory Academic Progress process. You can
write your own rules for as many different SAP codes as needed in either the expert or
simple mode on the RORRULE form. These rules are used by the SAP process to assign
SAP status codes automatically to the student record.
Satisfactory Academic Progress data is kept on a term-by-term basis and stored in the
RORSAPR table.
SAP forms
The following forms are used in SAP processing.
Satisfactory Academic Progress Validation form (RTVSAPR)
The primary sort order on this form is defined with the SAP Status Code Priority field.
This is the same basic format as that on the Group Assignment Validation forms and the
functionality is almost the same, with the lowest number (1- 999) representing the highest
priority. This means that the rules will be analyzed by Banner in the order of their priority
codes.
While this form operates much like the RTVTGRP, RTVBGRP, and RTVPGRP forms, the
output is not a group code, but rather an SAP status assigned to the student for a specific
term. The SAP process does not use the Group Assignment Process of RORGRPS, but
instead has its own unique process - the SAP Assignment Process (ROPSAPR).
January 2009
Financial Aid 8.3
User Guide
Processing
2-81
When you create a new SAP status code, a priority code with a value of 1 is created as the
default; you can update this field at that time. If you plan on using the ROPSAPR process,
you must assign a priority code to all SAP status codes.
Note
The primary sort on this form is priority code. If no priority code exists, it
will sort on the SAP status code. Those with priority codes will come
„
before those without.
The Letter Code field is validated against the Letter Code Validation form (GTVLETR).
This field allows for the association of a letter code to an SAP status and is optional. If the
student is assigned that SAP status, a pending letter is posted to the GURMAIL table
automatically. This only occurs if the SAP status was determined through the SAP
Assignment Process (ROPSAPR) or the SAP status is being updated through Batch
Posting. Pending letters will not be created automatically if a SAP status code is posted
manually, updated manually, or is posted through any other mechanism such as PL/SQL.
Note
Only one pending letter will be created for any specific letter. Until that
letter code has been printed, the same letter will not be posted as pending
for the same aid year. However, other pending letters can be created at
„
the same time for different letter codes.
The Message Number field for Web and Voice Response access is optional.
The SAP Status Code field, which is six positions in length, provides you with flexibility
in the definition of these codes and allows you to make the codes meaningful. For
example, a PROB1 value might represent the 1st Probation, while PROB2 might represent
the 2nd probation, or you could use P1 and P2. The objective is to provide flexibility to
define an SAP status with more meaning for the user. All related processes and all forms
that store an SAP status have been modified to accommodate this longer field length.
The RTVSAPR form contains an options list of Which Aid can be attached to each SAP
status to prevent packaging and/or disbursement activities. These options, which are
available via a drop-down list, include:
• None
• All Aid
• Title IV only
• All Federal Aid
Plus the additional options of (prevent packaging/prevent disbursement for):
• State only
• State and Federal
• State and Title IV
2-82
Financial Aid 8.3
User Guide
Processing
January 2009
• Institutional only
• Institutional and State
• Institutional and Federal
• Institutional and Title IV
• Institutional, State, and Title IV
• Institutional, State, and Federal (leaves Other Source code if any funds are defined)
Financial Aid Selection Rules form (RORRULE)
On the RORRULE form, the Group Code field becomes SAP Code when the Rule Type
field is assigned a value of S. The ROPROLL process allows for the rules to be rolled from
aid year to aid year. While it may be that a school's SAP rules do not change from year to
year, in some cases they will. As a result, to allow for those situations where these rules do
change, the aid year remains a part of the key for the rule, and the SAP rules will be treated
as all others in rolling from aid year to aid year. If there are no changes, you can just
continue processing, as the roll process now rolls the compiled versions of the rules from
RORRULE to the new aid year.
If your institution calculates SAP status on a specific term results rather than cumulative
results, the form will not automatically add the appropriate terminal variable of :TERM.
You will need to add this variable at the end of the rule by using the Substitution button
from the expert mode rules and selecting :TERM. This will then allow the Calculate From
term value to replace this in the rules when they are executed. This works the same as the
:PIDM and :AIDY values, except that you must manually add this to your rules when
initially creating them. By using this variable (:TERM) you will not be required to hard
code a term value into the rules and then make sure it is updated every time you want to
run SAP for a different term.
Applicant Immediate Process form (ROAIMMP)
This form allows the assignment of a SAP status online. The process involves the use of
two term codes. The first term code, Calc From, points the assignment process to the term
from which you want to calculate the newest SAP status. This Calc From term code is
required and automatically defaults the current term code as defined on the Institution
Financial Aid Options form (ROAINST) and can be changed. Although this value is
required, the field is only utilized by those rules which are term-specific and for those
schools that perform a term-specific SAP calculation. This Calc From term code must
belong to the aid year in the Key Block of the form. The validation on this term code will
restrict the options to only those terms which exist in the aid year.
The second term code, Effective, which is also required, directs the process to the term in
which to post the results (the New SAP Status on the ROASTAT form). The term for
which the new SAP code is being posted will not be validated against the aid year in the
Key Block of the form.
January 2009
Financial Aid 8.3
User Guide
Processing
2-83
For example, suppose that it is the end of the Spring term and you want to determine SAP,
and you want the result to be posted to the Fall term. The Spring term code (Calc From)
would need to belong to the aid year in the Key Block of the form, while the Fall term,
where the results will be posted (Effective term) would not need to belong to that year.
The Effective term must be later than the Calculate From term. The validation on this term
restricts the options to only those terms which are later than the Calc From term.
Logic within these terms prevents you from posting the results of the SAP calculation to
the term for which the calculation was just done, or any prior term. In this way, the process
ensures that you are posting the new SAP code to a term later than that from which the
calculation originated. In other words, the form will make sure that you do not calculate
the New SAP code from the spring term and then accidentally update the Spring SAP
code, when you meant to update the Fall SAP code. This same logic applies to the
parameters in job submission.
The SAP process on the ROAIMMP form differs from the other group assignments
process for tracking, budgeting, and packaging. The SAP process uses the same process
from online and from job submission to assign the SAP codes. The name of this process is
ROPSAPR, or the SAP Assignment Process. Also, the only option for the Action
Indicator is I (Immediate), therefore eliminating any need for the Current Status and
Completion Date columns. Check the SAP field option to perform this calculation.
Applicant Status form (ROASTAT)
The Satisfactory Academic Progress block on the ROASTAT form displays the SAP code
assignment process history and all related information for the student on a term-by-term
basis. This form captures the following information.
The Term is the effective term code that was used by the ROAIMMP form (using the
ROPSAPR Process) or as a parameter in job submission. The Calculated SAP Status is
the status that the SAP Assignment Process determined the student qualified for at this
point in time based on the rules from RORRULE.
However, the New SAP Status is the status that has gone through the additional
translation process from the Satisfactory Academic Progress Translation Rules form
(RORSTRF), if applicable. If the RORSTRF form is not used, the New SAP Status will
always be the same as the Calculated SAP Status. The Lock Indicator field allows you
to lock a new SAP status code from any further changes. You cannot update the calculated
SAP Status with this form. Only the SAP Assignment Process can update the calculated
SAP status.
The Lock Indicator, when set, prevents all manual and automated updates. You must
remove the lock before any further updates are allowed. If a SAP status is not locked and
there is another SAP calculation run for the same term, the old record is replaced with the
latest result. In all cases, the User ID and Activity Date default into the appropriate fields.
2-84
Financial Aid 8.3
User Guide
Processing
January 2009
The Term, Calculated SAP Status, and New SAP Status fields utilize the List of Values
function, which allows you to access to the full description for each of the codes
displayed. The description for each SAP status displays as the cursor moves to that field.
Note
The Calculated SAP Status field will be null for all terms where there is a
SAP status prior to utilizing the ROPSAPR process. This field is only
populated through the ROPSAPR process. Therefore any other means of
posting an SAP code, manual batch posting, or through an outside
process will not populate this field.
Batch posting a SAP code will automatically set the lock indicator.
„
Satisfactory Academic Progress Translation Rules form
(RORSTRF)
There is a need at many institutions to allow the SAP process to go through a final rule
process beyond just the calculation of the current SAP status. This process uses the
student's current (calculated) SAP status and their last SAP status to determine their real
SAP status at the current time.
An optional rules form can be used to support the additional process that defines the actual
SAP status code that you want to post to the RORSAPR record. The name of the form is
the Satisfactory Academic Progress Translation Rules form (RORSTRF). Banner takes the
calculated value from the SAP Assignment Process and compares the results to the
following rules form. The process then determines and posts the appropriate new SAP
status. In all cases, these are the same SAP statuses that were defined on the RTVSAPR
form.
This is a repeating rules form allowing for the definition of as many status combinations
desired. It also allows for the definition of the Letter Code to be posted to the GURMAIL
table as a pending letter for anyone with this combination. The SAP Letter Code is
validated against GTVLETR and the other three columns against RTVSAPR. The SAP
Letter Code field is optional if you use this form.
If the appropriate combination is defined on RORSTRF, the calculated status, which is
assigned as a result of the ROPSAPR process, is not the student's New SAP status, but
rather is just the status that has been determined from this recent calculation. It is the SAP
status that the student qualifies for - given the results of the rules. However, the calculated
SAP status will go through one more process to determine what is the correct SAP status
to post to the RORSAPR table and to be used by the packaging and disbursement
processes. The ROPSAPR process will see if the combination of Previous SAP status and
Calculated SAP status exist on RORSTRF. If they are present, the student will be assigned
whatever New SAP status the rules dictate.
If your school chooses not to use this rule form, the status code that is derived from the
ROPSAPR Process is the code that is posted to the New SAP status field and posted to the
RORSAPR table. However, if your school chooses to use this form and only wants to
January 2009
Financial Aid 8.3
User Guide
Processing
2-85
build certain combinations of SAP statuses on this form, rather than the complete
exhaustive list of all possible options, the process will support that also. This means that if
there is a combination of Previous SAP Status and Calculated Status present on this form
that matches a student, the appropriate New SAP status and Letter Code are posted
accordingly.
However, if the SAP Status combination is not present on the rule form, the Calculated
SAP Status will be the status posted to the New SAP Code and updated to the RORSAPR
table. For example, suppose the Previous Status is X and the Calculated Status is PROB1.
Given the above example, this combination is not present, therefore PROB1 becomes the
New SAP status and gets posted to RORSAPR.
The SAP Assignment Process will always look at the RORSTRF form first to see if the
student’s combination of Previous SAP status and Calculated SAP status exist. If they do
exist on the rule form, the ROPSAPR process will post the appropriate values to the
RORSAPR table (visible on the ROASTAT form) and the GURMAIL table (visible on the
RUAMAIL form). If the student’s combination does not exist on RORSTRF, the
Calculated SAP status will also be the new SAP status. If there is a letter code associated
with that status on the Satisfactory Academic Progress Validation form (RTVSAPR), it
will be posted to the GURMAIL table as a pending letter.
Note
Only one pending letter will be created for any specific letter. Until that
letter code has been printed, the same letter will not be posted as pending
for the same aid year. However, other pending letters can be created at
„
the same time for different letter codes.
Group Inquiry form (ROIGRPI)
This form is a tracking, budgeting, packaging, and SAP group assignment query form
used to view the results of the assignment process and to see if rules exist. When you enter
a value of SAP in the Group Type field and a term code in the Term field, the form
returns the count of how many applicants have a specific SAP code for that particular
term. The form also enables you to see if rules exist for that SAP code for the year in
which the term is associated. The sort order on the form is by Group Priority. Remember,
if you choose to assign SAP codes, regardless of the existence of a RORSTAT record,
these numbers reflect the counts in the RORSAPR table, not RORSTAT.
Institution Financial Aid Option form (ROAINST)
The Institution Financial Aid Options form (ROAINST) utilizes a six-character SAP code
field. The Initial SAP Status remains as the SAP code that is assigned to a student/
applicant when the initial RORSTAT record is created. The Exception SAP Status field is
used when the applicant falls through all of the SAP rules defined on RORRULE and does
not fit into any of the predefined rules. This is the SAP code of last resort, much like the
default group codes assigned in tracking, budgeting, and packaging. This field is also six
positions in length and is validated against the RTVSAPR values.
2-86
Financial Aid 8.3
User Guide
Processing
January 2009
SAP Processes
The applicant's SAP code is used throughout Banner. Banner looks at this value when
packaging and disbursing the aid for the student.
SAP Assignment Process (ROPSAPR)
This process utilizes the rules established on the RORRULE form with a Rule Type of S.
Unlike other Banner Financial Aid jobs, you must select which group of students to
process through rules using parameters 05, 06, or 07 through 10.
The process will not default to only those with RORSTAT records for the aid year as many
of the other Financial Aid processes do. In fact, this process will allow students to be used
who do not have RORSTAT records. This will allow those institutions who wish to
calculate and maintain SAP statuses on all students to do so, whether or not they are
currently receiving financial aid funds.
The parameters for this process include:
• 01 Aid Year Code (Required).
The aid year value is used to validate the Term Code for the calculation (must be
defined as belonging to that aid year).
• 02 Term Code For Calculation (Required).
This value is used for those schools who want to calculate SAP on a specific term
set of values rather than the cumulative statistics of an applicant. This parameter is
not used by schools that do not specify a term value in their rules. This value is
only utilized in the rules if there is a terminal value in the compiled rule :TERM. It
must be defined as a part of the aid year in Parameter 01.
• 03 SAP Effective Term Code (Required).
This is the term code that is associated with the results of the process. The process
requires this term to be later than that used for Parameter 02. This term also
identifies the aid year that all letters will be posted to in the GURMAIL Table
(RUAMAIL form).
• 04 Student ID.
This option cannot be used when running the process from job submission.
• 05 Use All with RORSTAT for Aid Year (Required - default of N).
This option allows for the process to run on only those applicants with RORSTAT
records for the aid year (as defined in Parameter 01).
• 06 Use All Enrolled for Term (Required - default of N). This option allows for the
process to run on only those students who have enrollment records for the Term
Code for Calculation (as defined in Parameter 02).
• 07 Application Code.
This parameter is utilized in population selection.
January 2009
Financial Aid 8.3
User Guide
Processing
2-87
• 08 Creator ID of Selection ID.
This parameter is utilized in population selection.
• 09 Selection Identifier.
This parameter is utilized in population selection.
• 10 User ID.
This parameter is utilized in population selection.
• 11 Create RORSTAT Record Y or N (Required).
If there were applicants who went through the process and did not already have
RORSTAT records, do you want RORSTAT records created?
The first term code parameter, Term Code for Calculation (Parameter 02), validates
against the Aid Year Code (Parameter 01) to ensure it is defined for that aid year code. The
second term code parameter used in the process, SAP Effective Term Code (Parameter
03), is the term to which the results of the SAP process are posted. This term code is not
validated against the aid year code parameter, as it may fall outside the range of the aid
year. For example, SAP is being calculated at the end of the Spring term for the Fall. The
Effective SAP Term Code would be the Fall term code, while the aid year parameter for
the process would be the prior year.
The goal in requiring you to define these separate terms as input to the process up front is
to minimize the need for you to hardcode specific term codes into the rules themselves.
This would require you to maintain this data every time you need to run the rules.
The part of this process that has always caused confusion has been deciding which term
the SAP has been calculated for and what term should be used in posting this SAP code.
For example, if the student status at the end of the Spring semester is being reviewed, the
code must be posted for the next term. Therefore, when running the SAP process, the term
that should be used as the Effective term is not the Spring term, but rather the Fall term
code (or possibly the Summer), as that is the term you want the results to affect. The
packaging and disbursement processes will look at the Fall term code and will apply any
and all logic for that SAP code to activity for the Fall; therefore, the Fall term code will be
the Effective Term.
The first step of the SAP Assignment Process is the determination of what is the student’s
Calculated SAP status from the logic defined by the rules on RORRULE. This result will
be posted to the RORSAPR table and displayed on the ROASTAT form. From here, the
ROPSAPR process must determine if there are rules present on the RORSTRF form. If
there are rules present and the combination of Previous SAP Status and Calculated SAP
Status is present and matches that combination with a student, the process will pick up the
New SAP Status as defined on RORSTRF and post that status as the New Status to the
RORSAPR table which will again display on ROASTAT. If there are no rules on the
RORSTRF form or the combination for Previous SAP Status and Calculated SAP Status is
not defined, the Calculated SAP Status will become the New SAP Status and be posted as
such.
2-88
Financial Aid 8.3
User Guide
Processing
January 2009
Finally, the process must determine if there is a letter code defined for the New SAP Status
anywhere. The processes will look at the RORSTRF rules form first. If there is a letter
code defined for the combination of Previous Status and Calculated Status, the process
will post that code to the GURMAIL table as a pending letter, using the aid year code
associated to the Effective term. If the combination is not present on RORSTRF, the
process will then look at the RTVSAPR rules form. If there is a letter code defined for the
student’s New SAP Status, that letter code will be posted to the GURMAIL form. If there
is not a letter code in either location, no letter code will be posted.
In the previous examples, the SAP status was being determined from the Spring term and
posted to the Fall term. In this case, the Calculate From term is the Spring and the
Effective term is the Fall. The letter code will be posted as a pending letter to the aid year
associated with the Effective term - or the Fall. Since this will impact the Fall term
eligibility, it was determined that this was the appropriate year in which to attach the letter.
The ROPSAPR output files, the .log and .lis files, will identify the number of students that
were processed through the SAP rules and if there are any locked records which could not
be processed. The output will itemize those students who were not processed due to
locked records.
SAP Status Codes View (ROVSAPR)
This view is intended to provide a method for selecting the maximum value SAP code for
any student at any point in time. This view can be used as a tool for writing population
selection rules, batch posting rules, or any other set of rules that is appropriate.
Process Flow
1. Set up all rules associated with this function (ROAINST, RTVSAPR, RORRULE,
RORSTRF).
2. When appropriate, run the ROPSAPR process from job submission for the desired
group of students.
3. On an individual basis, the SAP process can be run online from the ROAIMMP form
or the SAP code may be updated manually on the ROASTAT form. It is on this form
that results may also be locked. (The batch posting process can also be used).
4. Run letters that were posted to the GURMAIL table as pending. When you run the
GLBLSEL process, respond to the first question Print All Pending? with No. Select a
specific letter code. Then you will be asked again Print Pending Letters for this Letter
Code ?. Answer Yes and all letters with that letter code will be selected to be run.
Once you have run these letters through the GLRLETR process, the print date will
populate and they will no longer be pending.
January 2009
Financial Aid 8.3
User Guide
Processing
2-89
5. If there was a change to the SAP Status for the term and a pending letter has already
been created, but not yet printed, you will need to review the RUAMAIL form for
accuracy.
Note
For those institutions which use an aid year counter (or term counter) in
their rules, this data can be stored in a user-defined field and accessed in
your rules.
The same is true for those schools who require a specific number of
hours to be completed within an academic year. This data can be
collected and stored in a user-defined field. This data is then available for
„
use in your SAP rules.
Note
Those clients who plan to take advantage of the latest enhancements in
SAP processing will need to notify their Database Administrator to pay
particular attention to the rate of growth of the Satisfactory Academic
Progress Rules Table, RORSAPR. It it becomes too large, the table may
need to be resized. The General utility script gurrddl.sql (found in the
plus subdirectory of Banner General) can be useful in accomplishing this
task. This will particularly be true for those schools who choose to start
maintaining SAP data on all students who are enrolled, not just those with
RORSTAT records.
The batch posting process will not use the rules established on the
RORSTRF form since there will not be a calculated SAP status
determined. It will act the same way as a manual update to the SAP
status, and impact only the effective SAP status code. However, batch
posting will work differently than manually updating or posting an SAP
status, in that it will create a pending letter if the status code being posted
is defined with a letter code on the RTVSAPR form. It should also be
noted that SAP records will be locked through the batch posting process.
If you are writing term-specific rules and you wish to test the results while
still on the RORRULE form by pressing Execute, you must replace your
:TERM variable with a specific term code so the rule can know which term
to look for. However, remember to change this back to the :TERM variable
before leaving the form as the appropriate term code will pass into this
rule from the job parameters at run time.
For those institutions who wish to run the ROPSAPR process from the
„
command line, the following are the instructions to do so.
On the Process Parameter Entry form (GJAPCTL), enter the required parameters for
ROPSAPR. Select the Hold radio button of the Submission Block and press commit. Note
the sequence number that returns to the screen. Go to the command line and enter:
For Unix: ropsapr.shl <enter>
For VMS: ropsapr <enter>
2-90
Financial Aid 8.3
User Guide
Processing
January 2009
You will then be prompted for a User ID, a password, and the sequence number from
above.
Sample Rules
Below are some examples of rules that might be useful when trying to develop your own
rules. It is helpful to note that the SHRTGPA table stores term-specific data about
students, while the SHRLGPA table stores cumulative data. In the SHRTGPA table, there
are options of whether to choose all data for a term-related to Institution coursework (I) or
all data related to transfer work (T). In the SHRLGPA table there are three options.
Institution (I), Transfer (T), or Overall (O).
1. A term-specific rule that does not require a RORSTAT record. Would have to be
written in expert mode.
select DISTINCT(spriden_PIDM) from spriden, sgbstdn x, shrtgpa
where sgbstdn_degc_code_1 in ('BA','BBA','AS','AA') and
shrtgpa_levl_code = 'UG' and
sgbstdn_majr_code_1 in
('ACCT','ANTH','CHEM','BUSI','ENGL','PSYC','SOC','BIOL') and
(shrtgpa_gpa_type_ind = 'I' and
((.60*shrtgpa_hours_attempted) <= shrtgpa_hours_earned)) and
sgbstdn_term_code_eff =
(select max (y.sgbstdn_term_code_eff)
from sgbstdn y
where y.sgbstd_pidm
= x.sgbstdn_pidm and
y.sgbstdn_term_code_eff <= :TERM) and
sgbstdn_pidm = spriden_pidm and
shrtgpa_pidm = spriden_pidm and
spriden_pidm = :PIDM and
shrtgpa_term_code = :TERM
2. A cumulative rule which requires a RORSTAT record. Can be written in simple or
expert mode. This rule will also have to be updated every year as it uses the rovst99
view.
Simple rule:
shrlgpa_levl_code = ‘UG’ and
rovst99_degc_code_1 in (‘BA’,’BBA’,’AS’,’AA’) and
rovst99_majr_code_1 in (‘ACCT’,’ANT’,’CHEM’,’BUSI’,’ENGL’) and
(((shrlgpa_hours_attempted > 0 and
shrlgpa_hours attempted <= 44) and
shrlgpa_gpa >=1.60 and
shrlgpa_gpa_type_ind = ‘O’) or
((shrlgpa_hours_attempted >=45 and
shrlgpa_hours_attempted <=89) and
January 2009
Financial Aid 8.3
User Guide
Processing
2-91
shrlgpa_gpa >=1.75 and
shrlgpa_gpa_type_ind = ‘O’) or
((shrlgpa_hours_attempted >=90 and
shrlgpa_hours_attempted <=134) and
shrlgpa_gpa >=1.90 and
shrlgpa_gpa_type_ind = ‘O’) or
((shrlgpa_hours_attempted >=135 and
shrlgpa_hours_attempted <=275) and
shrlgpa_gpa >=2.00 and
shrlgpa_gpa_type_ind = ‘O’))
and
((.75*shrlgpa_hours_attempted) <= shrlgpa_hours_earned)
3. Example of the same rule as #2 without the rovst99 view. Would not require updating,
but will require expert mode rules. This rule contains the same logic within it that the
view does.
Select distinct(spriden_pidm) from spriden, sgbstdn x, shrlgpa where
sgbstdn_degc_code_1 in (‘BA’,’BBA’,’AS’,’AA’) and
shrlgpa_levl_code = ‘UG’ and
sgbstdn_majr_code_1 in (‘ACCT’,’ANT’,’CHEM’,’BUSI’,’ENGL’) and
(((shrlgpa_hours_attempted > 0 and
shrlgpa_hours attempted <= 44) and
shrlgpa_gpa >=1.60 and
shrlgpa_gpa_type_ind = ‘O’) or
((shrlgpa_hours_attempted >=45 and
shrlgpa_hours_attempted <=89) and
shrlgpa_gpa >=1.75 and
shrlgpa_gpa_type_ind = ‘O’) or
((shrlgpa_hours_attempted >=90 and
shrlgpa_hours_attempted <=134) and
shrlgpa_gpa >=1.90 and
shrlgpa_gpa_type_ind = ‘O’) or
((shrlgpa_hours_attempted >=135 and
shrlgpa_hours_attempted <=275) and
shrlgpa_gpa >=2.00 and
shrlgpa_gpa_type_ind = ‘O’))
and
((.75*shrlgpa_hours_attempted) <= shrlgpa_hours_earned) and
sgbstdn_term_code_eff =
(select max(sgbstdn_term_code_eff)
from sgbstdn y,
robinst
where y.sgbstdn_pidm = x.sgbstdn_pidm and
y.sgbstdn_term_code_eff <=robinst_current_term_code and
robinst_aidy_code = :AIDY) and
sgbstdn_pidm = spriden_pidm and
shrlgpa_pidm = spriden_pidm and
2-92
Financial Aid 8.3
User Guide
Processing
January 2009
Funds Management Procedures
Funds Management Implementation
1. Determine the various fund types your funds may have on the Fund Type Validation
form (RTVFTYP).
Fund types include: Loan, Work, Grant, or Scholarship.
2. Determine the various fund sources for your funds on the Fund Source Validation
form (RTVFSRC).
Fund sources include: Federal, State, Institutional, or Other.
3. Define all potential funds on the Fund Base Data form (RFRBASE).
If the fund is able to be disbursed to the student account, relate an A/R detail code to
the fund. From the Fund Type Validation form (RTVFTYP) and the Fund Source
Validation form (RTVFSRC), determine the type and source of each defined fund.
Relate a Federal Fund ID to those Federal funds to which Federal hard-coded rules
should apply. (Use the List function to determine valid values for these fields).
Determine the print order of the funds. Note that this print order only determines the
order of the funds for letter-generation printing purposes. This does not affect the
order of the funds on this form.
Note
You can use the GTIV (General Title IV Rules) code to subject the hardcoded federal rules to any non-Federal funds to which you wish them to
„
apply.
4. For each fund, define any awarding rules that may apply using Rule Type Fund
Awarding on the Financial Aid Selection Rules form (RORRULE).
These rules are interrogated during the packaging process when the fund is to be
packaged.
5. For each fund, define any disbursement rules that may apply on the Financial Aid
Selection Rules form (RORRULE).
These rules are interrogated during the packaging process when the fund is to be
disbursed.
6. Define the award and disbursement schedules by aid periods in the Default Award &
Disbursement Schedule Rules (RFRDEFA).
January 2009
Financial Aid 8.3
User Guide
Processing
2-93
Note that the default rules are not by fund, but only by aid period. You may use the
Insert Record function to bring in the valid terms for both the Award and the
Disbursement Schedule for the aid period identified in the Key Information section.
• In the Award Schedule section, the Award Percent for all terms must equal
100%. Define valid memo expiration dates for each term.
• In the Disbursement Schedule section, the disbursement date will default to
the cut-off date defined by term on the Packaging Options form (RPROPTS).
The disbursement percent for each term must equal 100%.
7. Access the Award & Disbursement Schedule Rules form (RFRASCH).
Use this form for any funds whose award and disbursement rules differ from the
defaults set up on the RFRDEFA in Step 6. If no rules are defined specifically for the
fund, the default rules will be used when the award and disbursement schedules are
created in the student's packages.
8. Access the Fund Management form (RFRMGMT).
Use this form to define aid-year specific budget information, packaging and
disbursement options budget and detail code rules, and tracking and message
assignment rules for each particular fund. Refer to Dynamic Help for specific
information on the use of the fields.
Fund Balance Reconciliation
The fund balances on the Fund Budget Inquiry form (RFIBUDG) are stored in the
RFRASPC Table. The balances in the RFRASPC Table are updated whenever a student's
award for the year changes, when the status of the award changes, or when the amount of
the memo, authorization, or payment changes. These balances are the summary of all
activity for the year for awards made to all students. Individual student award information
is stored in the RPRAWRD Table.
Note
If a fund is out of balance, Banner may stop awarding or disbursing funds
to students because it erroneously thinks that the fund is out of money.
Running this reconciliation process will restore the fund balances to their
„
proper level.
From time to time the totals that display in the RFIBUDG form and those stored in the
RPRAWRD table get out of sync. Therefore, it is recommended that the SQL* PLUS
scripts, rupfndbl.sql and rslfndbl.sql, are run regularly to keep them in sync. Note
that the same logic as rupfndbl.sql can be executed from the ROAMGMT form. You
can select to reconcile only one fund, or all funds for the Aid Year in the Key Block.
Warning
Original Offer totals are not updated by these scripts nor by the RECON
„
FUND/RECON ALL buttons on ROAMGMT.
2-94
Financial Aid 8.3
User Guide
Processing
January 2009
Calculating Fund Balances - Setting and Using
Overcommitment Levels in Packaging
You enter the number of real dollars available to award students from each fund on the
Fund Management form (RFRMGMT). You also use the RFRMGMT form to set an
overcommitment level. This overcommitment level is based on the expected number of
students who decline their awards, never enroll, become ineligible before payment, or in
the case of work programs - never appear for a job assignment or do not work the total
authorized hours.
Based on past experience, you can estimate the amount of specific awards that you can
safely overcommit during packaging because you know that all awards are not actually
paid; a percentage of awards are either canceled or declined before payment.
When Banner determines if available funds exist for new or additional awards to students,
Banner previously used the Available to Offer Amount (based on the overcommitment
level) minus the amount of current (active) offers already made to other students. If there
was no money left, the award was rejected by the award validation process.
However, as the financial aid office canceled and declined awards, the balance of funds
available to award to other students increased because the declined and canceled funds
were taken out of the current offers. These funds were available to be rewarded to other
students. Banner continued to allow awards to students until the amount of current offers
reached the Available to Offer amount. Unless you continuously monitored the amount of
canceled and declined awards and reduced the Available to Offer amount to eventually
match the real allocated dollars, you could begin the year with current offers exceeding the
number of real dollars available to pay.
To remedy this potential problem, Banner includes the amount of canceled and declined
awards in the formula that determines the fund balance for packaging. When testing to see
if the fund has enough money available to make new or additional awards, it now takes the
Available to Offer Amount (overcommitment level) and subtracts the current offers,
declined amounts, and canceled amounts.
When an award is canceled or declined, the Available to Offer amount does not change
because the canceled/declined amount is still being used to reduce the balance. The
numbers displayed on the Fund Budget Inquiry form (RFIBUDG) as the Amount
Remaining to Offer and the Percent Remaining to Offer now use this formula. All reports
that display the Amount Remaining to Offer also use this formula (RFRBUDG,
RFRSBAL).
In addition to this formula, an amount is displayed on the Fund Budget Inquiry form
(RFIBUDG). Next to the Percent Remaining to Offer field is the Actual Remaining
Amount. This is the Total Allocated (real dollars) minus the Current Offers.
This process works best when the aid office's procedure is to cancel or decline a student's
award if the student is no longer eligible, rather than by deleting the award from the
student's package. By canceling and declining awards you no longer need to continuously
January 2009
Financial Aid 8.3
User Guide
Processing
2-95
reduce the Available to Offer amount for each fund. If your overcommitment projection is
correct, the final current offers will eventually equal the total allocated. Banner still cannot
save you if you overcommit too much and your final current offers exceed your total
allocated. The total amount of canceled and declined awards in one year will be a good
measure of what the overcommitment level for the next year should be.
Packaging and Disbursement Procedures
Packaging Implementation
1. Set up your packaging groups and create a group priority on the Packaging Group
Validation form (RTVPGRP).
Remember that the lower the number, the higher the priority. You may want to leave a
range between groups for ease in adding groups at a later time. Create an award
priority. This priority is used in the awarding process to select the order in which
packaging groups will be awarded funds.
Note
Remember to add your default Packaging Group onto RTVPGRP before
„
entering it on ROAINST.
2. Define all possible award statuses in the Award Status Validation form (RTVAWST).
Check the appropriate values to the Offered, Accepted, Cancelled, and Declined
indicators for each status.
Note
Only one indicator may checked for each award status, but multiple award
statuses can have the same indicator checked. Remember to assign the
„
appropriate statuses built here to each fund on RFRMGMT.
3. Access the Packaging Options form (RPROPTS).
Use this form to select options that control the method in which certain functions
perform in the packaging module. Complete the Packaging Options, Exemptions/
Contracts Options, and Disbursement Options sections. Determine institutional policy
on enrollment cut-off dates for the terms within the aid year you are defining.
Note
If the Disburse If Charges Not Accepted box is not checked and the
student's charges have not been accepted, then the disbursement
process will not process any payments directly to the student's account.
However, process authorizations and memos can be processed.
If the Disburse If Charges Not Accepted box is checked, the
2-96
Financial Aid 8.3
User Guide
Processing
January 2009
disbursement process can post payments directly to the student's
account whether or not the student's charges have been accepted.
„
4. Open the Default Packaging Rules form (RPRDEFR).
Determine institutional policy on Gap, Equity, and Self-Help Packaging Rules.
Equity Packaging can use one of three methods:
(1)
(2)
(3)
Percentage of Gross Need,
Percentage of Budget, or
Equity Amount.
This form is used only as a default for those rules which may be used for individual
packaging groups. Gap Packaging can be accomplished by using either a Percentage
of Gross Need or a Gap Amount.
Self-Help Packaging can be accomplished through:
(1)
(2)
(3)
Percentage of Gross Need,
Percentage of Budget, or
Self-Help Amount
5. Access the Packaging Rules form (RPRPCKR).
Assign your Gap, Equity, and Self-Help rules to Packaging Groups to which they may
apply. To default in the rules from RPRDEFR, use the Create Record function. To
view the default rules on RPRDEFR, use the Count Query Hits function.
Note
If rules do not exist for a group, then no Gap, Equity, or Self-Help rules will
be used for that group. The packaging routine will not use the rules
„
defined on RPRDEFR.
6. Open the Financial Aid Selection Rules form (RORRULE).
Define your packaging group assignment rules for each packaging group in the aid
year you are defining. These rules are optional if you will not be performing automatic
packaging. The Packaging/Disbursement Rules types include:
• Packaging Group Assignment
• Fund Awarding
• Fund Disbursement
• Packaging Group Fund Awarding
January 2009
Financial Aid 8.3
User Guide
Processing
2-97
7. Categorize your funds into packaging groups in the Packaging Group Fund Rules
form (RPRGFND).
Define a minimum, maximum, and percentage of unmet need that the fund should
meet. Also identify the methodology to be used for the awarding of that fund within
the group (F - Federal or I - Institutional). Each fund code should be given a priority.
This controls the sequence by which the funds are interrogated during the packaging
process.
Note
Any fund with a Federal Fund ID of Pell cannot be associated with a
packaging group. The Pell awarding process is separate from the fund
awarding process.
Any fund with an unchecked Automatic Packaging indicator on
RFRMGMT cannot be associated with a packaging group.
The same fund can be included in the packaging group multiple times
with differing priorities.
„
Packaging/Simulation
In order for successful batch packaging, an applicant must:
1. Have a packaging complete date that is null (RPAAWRD, RPAAPMT, ROARMAN).
2. Not have any outstanding tracking requirements that prevent packaging.
(RPAAREQ).
3. Have a packaging group (RPAAWRD, RPAAPMT, ROARMAN).
4. Meet all hardcoded rules (Award Validation Rules). The fund must also meet any
locally developed notes on the RORRULE form such as a Fund Award Rule or
Packaging Group Fund Award Rule.
Packaging in actual or simulation mode should follow this procedure:
1. Run RPEPCKG.
The packaging process run will be based on the mode identified in GJAPCTL. The
action indicator should be set to S for Simulation mode or A for Actual mode. The
initialization (RPEPINT) and packaging (RPEPCKG) processes should not be run
separately. When packaging (RPEPCKG) is run, it will automatically call and run the
RPEPINT process.
Running these processes will produce the rpepckg.log file. Check this file for error
messages to ensure that the processes were completed successfully. Use the Print
Report parameter to select your report output prior to the process run.
2-98
Financial Aid 8.3
User Guide
Processing
January 2009
The possible packaging reports created by this process when the Action Indicator is
set to either A (Actual) or S (Simulated) includes the following:
rpbawrd.lis –
Packaging Award Report
rpbfund.lis –
Packaging Fund Report
Note
Although you are no longer required to use the Packaging Print Process
(RPBPDRV) during a normal run of the RPEPCKG Process, you can use
RPBPDRV to reprint existing extract files.
RPBPDRV requires that the rpepckg.ext file is present in your jobsub
directory. If you want to re-print an already extracted .ext file, you must
rename the rpepckg_job#.ext you want to report on to rpepckg.ext. You
can run RPBPDRV on any rpepckg_job#.ext you want as long as you
„
rename the file.
Packaging Process Definitions
Initialization Process (run as part of RPEPCKG)
The initialization process takes any pre-awarded funds that are on the student's award
record in an offered or accepted status and, if the award was system generated, refunds the
dollars to the appropriate fund management account.
Warning
This process will not delete and redeposit any funds or portion of funds if:
(1) the fund was manually added; (2) the award has been memoed,
authorized, or paid; or (3) the fund is locked. Following this process, the
new fund balances can be seen by running a Fund Report (RFRSBAL), or
„
by viewing the Fund Balance Inquiry form (RFIBUDG).
Simulated Packaging
First, the Action indicator on the GJAPCTL form for this process must be set to S
(Simulation). Then, in order to get a true picture of the funds available to be awarded, the
initialization process needs to be run. In simulated packaging, online results cannot be
viewed as the database is not being updated. Also in simulation, if the fund runs out of
money, the fund will continue to be packaged. The amount of insufficient funds will then
be indicated in a separate column on the fund report.
January 2009
Financial Aid 8.3
User Guide
Processing
2-99
Actual Packaging
In order to run actual packaging, the Action indicator on the GJAPCTL form for this
process must be set to Actual. The actual packaging mode will go through the initialization
process, then the packaging process, and then it will post the packaged awards to the
student's award record. Following the actual packaging routine, the applicant award report
can be run to show the packaged awards in order by student (rpbawrd.out).
Using NSLDS Data
The following sections explain how Banner provides the capability to utilize the NSLDS
source data in determining financial aid eligibility. The Financial Aid processes utilize the
cumulative loan-limit checking features.
Award Validation
Generally, a student is not eligible for U.S. Federal Student Aid funds if the student is in
default on a Federal student loan or owes an overpayment on a Federal grant or loan and
has not made a repayment arrangement for the default or overpayment. When the FAFSA
is processed, the CPS matches the student against the National Student Loan Data System
(NSLDS) to check for defaults, overpayments, and exceeded loan limits. Due to NSLDS
matching, the use of Financial Aid Transcripts (FAT) became redundant beginning with
the 2001-2002 aid year when the mandatory use of the NSLDS was required. Banner still
contained logic to examine the FAT table if the option was set to use Banner history. For
this reason, a change was made in Banner to exclude the old logic for default and
overpayment processing to only use NSLDS information when packaging U.S. Federal
funds, creating Federal loan applications, and disbursing Federal funds.
Often institutions award aid early in the processing year, but do not create loan
originations until a later time. During this time lapse, it is possible for default and/or
overpayment information to be received from NSLDS which then makes the student
ineligible. The creation of a loan origination, whether a Direct Loan or Electronic Loan,
will be prohibited if the student is now in default. An institution may override the status of
default and/or overpayment when sufficient documentation has been received, by
manually creating a current NSLDS record or using the NSLDS Override field on the
Need Analysis Result form (RNARSxx). When an override has been performed, a loan
origination may be created; however, the Loan Default field (RPRLAPP_IN_DEFAULT) is
updated to N (No) to reflect the current situation of the student.
When NSLDS data became available to schools in the EDE data load files many years
ago, Banner implemented a Source of Award History option on the Packaging Options
form (RPROPTS) to allow schools to select either N (NSLDS) data or B (Banner) data. All
schools must now use NSLDS data for this purpose. Starting with the 2006–2007 aid year,
N (NSLDS) is the only valid source of award history.
The Packaging and Disbursement processes will use NSLDS data for validation purposes.
The Electronic Loan Application (RPRELAP) and Direct Loan Record Creation
2-100
Financial Aid 8.3
User Guide
Processing
January 2009
(RPRLORC) processes will use the NSLDS Match indicator values to determine if a
student is in default or overpayment. Loan records are not created if the student is in
default and/or overpayment, unless the NSLDS Override field is set in the following
manner on the Federal Match Indicators window of the Need Analysis Result form
(RNARSxx).
NSLDS Match field (RNASLxx)
NSLDS Override Field Must Be (RNARSxx)
2=Default
D=Default tests or A=All tests
3=Overpayment
O=Overpayment tests or A=All tests
4=Default and Overpayment
A=All tests
Award Validation Prior to Receipt of NSLDS Data
It is possible that Stafford and/or Perkins awards could be made prior to the receipt of
NSLDS data for the year. In this event, cumulative limit or default/refund checking could
not be performed against current year data in packaging. Default/refund checking would
instead be performed at disbursement time. No federal aid would be disbursed until the
Official Source indicator was set to Official, but cumulative limit tests could not be done.
In this case, for Stafford Loans, Banner will use the Aggregate Outstanding Balances from
the most recent NSLDS record from the prior year. We should assume that no current year
loans are included in the prior year NSLDS data. The formula to use in validation would
be (NSLDS Aggregate Outstanding Balance + Prior Banner amount for the current year +
Award Difference) must be less than or equal to the aggregate limit for the federal fund ID
in RPRFEDR for the current year.
Perkins Loans (Cumulative Amount from NSLDS + Prior Banner amount for the current
year + Award difference) must be less than or equal to the aggregate limit for Perkins
loans in RPRFEDR. If the ELO Indicator on the NSLDS record = Y, use the rows in
RPRFEDR where the ELO Indicator = Y.
Award Validation After Receipt of NSLDS Data
Original Awards
When an original award is made for the year, it can be assumed that the NSLDS amounts
do not include any current year amounts. Stafford loans (NSLDS Total Loan Amount +
New Award for the year) must be less than or equal to the cumulative amount from
RPRFEDR. The Total Loan Amount differs from the Aggregate Outstanding Balance in
that the total already includes any pending disbursements whereas the Outstanding
Balance does not include pending disbursements. Any pending disbursements present at
this time would have to be for the prior year since the new award has not been made for
January 2009
Financial Aid 8.3
User Guide
Processing
2-101
the current year yet so NSLDS cannot know about it yet. Pending disbursements from a
prior year will be included in the aggregate test. Also, Outstanding Balances could include
capitalized interest on unsubsidized loans but Total Loan Amount would not. Capitalized
Interest does not reduce the remaining amount available to borrow so the total will be
used.
Modifying Existing Stafford, Direct or Perkins Awards
Stafford/Direct Loans
For Stafford/Direct Loans, Banner determines if a current year loan is included in the
current NSLDS record.
• The first check is of the recent loans table (RCRLDS6) where the NSLDS
Program Code matches the type of loan being validated (Direct Sub = D1, Unsub
Direct = D2, Sub Stafford = SF, Unsub Stafford = SU).
• If the Begin Date is between the Aid Year Start Date and the Aid Year End Date,
Banner assumes that the current year amounts are already included in the NSLDS
aggregate amounts. Otherwise, Banner assumes that the current year amounts are
not included.
If the assumption is Yes, Banner validates that (Total Amount from NSLDS + Award
Difference only) is less than the cumulative limit from RPRFEDR.
If the assumption is No, Banner validates that (Total Amount from NSLDS + Prior Banner
amount for the year + Award Difference) is less than the cumulative limit from
RPRFEDR.
Perkins Loans
For Perkins loans, Banner validates that ((NSLDS Cumulative Amount - NSLDS Current
Year Amount) + Prior Banner amount for the year + Award Difference) is less than the
cumulative limit from RPRFEDR.
Default/Refund Information and Financial Aid
Eligibility
Banner provides the capability for Banner to utilize NSLDS source data for default/
overpayment information in determining eligibility for financial aid.
Validating Awards Against Defaults/Refunds
Previously, the Award Validation routine (UVARTN) checked the NSLDS default/refund
statuses on the current RCRAPP4 record (RCRAPP4_NSLDS_MATCH). Banner now checks
2-102
Financial Aid 8.3
User Guide
Processing
January 2009
the current NSLDS record (RCRLDS4_MATCH_IND) for the information. The RCRAPP4
check is available to maintain prior year compatibility.
For students who resolve default/refund problems during the aid year: If a default or
refund problem is resolved by a student during the year, the student regains eligibility for
FFEL and Direct loans for the entire aid year (loan period). The student only regains
eligibility for other Title IV aid programs for the current payment period (term) and for
future payment periods in the same aid year, but not for prior payment periods in the same
aid year.
Since NSLDS only has one summary default/refund status field (NSLDS Match
Indicator), Banner cannot perform separate edits by payment period. Banner uses the
single indicator and assume that value for the entire year. This must be done since:
• There is no way to tell if the match indicator changed to correct an NSLDS data
problem or if the status actually changed,
• There is no way to tell the effective date of that change to determine which
payment period the change became effective, and
• It is possible that the first and only NSLDS record received by the school for the
year shows a satisfactory default/refund status; the school would never know that
the status for a previous payment period was unsatisfactory.
Validating Disbursements Against Defaults/Refunds
Disbursement validation also uses RCRLDS4_MATCH_IND for checking defaults and refunds
on overpayments.
For Perkins loans, the disbursement process works so that if NSLDS data indicates a
default or overpayment condition and a previous payment had been made to the student,
the previous payment of a Title IV fund will not be backed out - even if
RFRASPC_INEL_BEF_CUT_DATE_IND or RFRASPC_INEL_AFT_CUT_DATE_IND indicators are
set to B (Back Out).
This is necessary because if you received information about the default/repayment after
the payment was made, then your school is not responsible for recovering the money. No
new money will be paid but no money will be backed-out. You could still reduce the
amount of the award (even to zero) and the recoup feature will still return the funds.
(Recoup comes into play when no disbursement rejects are found.)
Since Stafford Loans are never backed-out, Banner prevents the payment of additional
loan proceeds. The processing of returned checks is still allowed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-103
Using NSLDS
forms related to the NSLDS process provide easy identification and query of data from the
various data sources (between manual entry and ISIR/NSLDS Data Load). The query
provides an overall picture of the applicant’s records in the aid year that supports both
daily inquiry and point in time audits.
Student Loan Data System form (RNASLxx)
The RNASLxx form allows the manual creation of records. Manual records can be
updated and other records (such as those with an INFC code of EDE or AFSA) cannot.
Manual records cannot be created unless the student already has a RORSTAT record and
at least one RCRAPPx record for the aid year.
All manually entered records become Current. Multiple manual records can exist per
student per year. The Sequence number would be one higher than the old current record.
The Processed Date field must be entered when creating manual records. The NSLDS
Transaction Number on a manual record will be set to the same transaction number as the
previous current record. The transaction number will display when you query the form.
When you create a manual record and an NSLDS record already exists, Banner copies all
the data from the previous NSLDS record into the new manual record. This includes
summary data, defaulted loan data, and recent loan data. This process allows you to easily
update the necessary fields without re-entering the entire record.
You cannot change the current record designation on records. If data in the current record
is incorrect, you can use overrides to negate the adverse consequences of the incorrect
data, or create a new manual current record with the appropriate data.
Applicant Student Loan Data Inquiry form (RNINSLD)
The Applicant Student Loan Data Inquiry form queries all NSLDS records. You can
access this form from the Need Analysis menu. You can also access this form if you select
Count Query Hits from the Source or Sequence No fields on the Student Loan Data
System form (RNASLxx). This form is similar in layout to the Applicant Need Analysis
Application form (RNIAPPL) and contains the following information:
• NSLDS Source
• NSLDS Sequence Number
• NSLDS Current Record Indicator
• NSLDS Transaction Number
• NSLDS Match Indicator
• NSLDS Results Flag
2-104
Financial Aid 8.3
User Guide
Processing
January 2009
• NSLDS Processed Date
• NSLDS Created Date
Need Analysis form (RNARSxx)
Banner provides an override capability to override NSLDS data that may be preventing
the awarding/disbursement of financial aid or the creation of Direct or FFEL loans. This is
important in cases where NSLDS data cannot be updated by the original data provider in a
timely manner for disbursement of funds. An example would be if the ISIR comes in
indicating that the student is in default, but the institution has documentation that the
student has made satisfactory arrangements to pay and is therefore eligible to receive Title
IV money.
Additional Override information includes:
• The Overrides that you enter will be used in both Award and Disbursement
Validation or the creation of Direct or FFEL loans.
• Two levels of Overrides are available: Overall for the student/year and by student/
year/term/fund.
• The Overall Override applies to all federal funds for all terms within the aid year.
• The term-specific overrides are specific to a fund/term combination and are used in
disbursement validation only.
• Each override is specific to each type of validation test:
• L
Limit tests (aggregate)
• D
Default tests
• O
Overpayment tests
• A
All tests
Annual limit overrides are not necessary because they already exist in the current
award validation process.
Award forms (RPAAWRD)/(RPAAPMT)/(ROARMAN)
Details on these forms include:
• A field, Override Indicator, is part of the RORSTAT table for the overall NSLDS
override. This field displays with the Federal Match Indicators on the Results form.
Valid values are L, D, O, and A. You can log changes to this field if Need Analysis
or Packaging Logging is activated.
• The award and disbursement validation processes checks the RORSTAT override
first, and if present, uses that value for all funds and terms for the year. Only
January 2009
Financial Aid 8.3
User Guide
Processing
2-105
disbursement validation utilizes a term code. Since Banner does not package by
term, the term code override option has no meaning for packaging.
• In disbursement processing, if no overall override exists, the validation processes
checks the term specific override on the RPRATRM table for the fund/term being
processed.
• Existing overrides (at either level) will not be automatically removed when a new
NSLDS record is loaded to Banner. The Data Load process will include an NSLDS
Discrepancy Report of Summary Data to show which NSLDS data elements have
changed. In this way, you can identify whose overrides might need to be reviewed.
• You should enter comments on the Applicant Comments form (RHACOMM)
whenever an override is entered or changed.
• As an alternative to using overrides, you can manually enter a complete new
NSLDS record on the RNASLxx form. This new record will become the current
NSLDS record and award/disbursement validation will use the data in this manual
record.
Output Population Selection With Financial Aid Data
Load, Part 3
NSLDS information entered via Data Load informs you as to whether a student is in
default. This information may affect the award process. If you use Early Decision
Processing, your school may package awards before you receive NSLDS information.
This process allows you to revalidate previously processed awards based on NSLDS
information received after packaging.
2-106
Financial Aid 8.3
User Guide
Processing
January 2009
Banner Financial Aid Fund Specific
Packaging Options
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
When you offer an award
to a student, what award
status code do you want
Banner to assign when
you package the award?
RFRMGMT
(Packaging
Options
Window)
Offer Status
Valid Award
Status Code
defined as
Offered
When the packaging program
offers the fund, Banner uses
this award status code for the
specific fund.
What award status code
do you want to use when
Banner accepts an award
for a student?
RFRMGMT
(Packaging
Options
Window)
Accept Status
Valid Award
Status Code
defined as
Accepted
Banner uses this defined
status when the fund is set to
auto-accept. It also uses this
status when you accept the
fund through the Award
Acceptance Mass Entry form
(RPAMACC).
What award status code
do you want to use when
Banner declines an
award for a student?
RFRMGMT
(Packaging
Options
Window)
Decline Status Valid Award
Status Code
defined as
Declined
Banner uses this decline
status when you decline the
award with the Award
Acceptance Mass Entry form
(RPAMACC).
Do you want to
automatically package
the fund through batch or
online auto packaging?
RFRMGMT
(Packaging
Options
Window)
Auto Package
a checked box
If you do not check this box,
you cannot use the fund on the
Packaging Group Fund Rules
form (RPRGFND) for the aid
year.
Once you award the
fund, do you want to
schedule it between the
terms in the student's aid
period?
RFRMGMT
(Packaging
Options
Window)
Auto Schedule a checked box
If you do not check this box,
the fund is not scheduled
between terms in the aid
period. There will be award
letter implications to consider
if you don't check this option.
There will also be
disbursement implications. It
is recommended this is
always checked.
January 2009
Financial Aid 8.3
User Guide
Processing
2-107
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
When you offer an award
as part of the student's
package, do you want
Banner to automatically
accept it?
RFRMGMT
(Packaging
Options
Window)
Auto Accept
a checked box
If you check this field and you
enter the fund with an Offered
status, the status
automatically changes to an
Accepted status as defined for
this fund and aid year. Do not
check the Auto Accept field
for any funds which you
require a student to accept
(that is, via an award letter).
Note that funds cannot be
disbursed until Accepted.
When the award is
packaged (whether in
batch or online), do you
want to package the
award even if it exceeds
the student's need?
RFRMGMT
(Packaging
Options
Window)
Override Need a checked box
Note that you cannot override
the overaward edit in Award
Validation regardless of how
this indicator is set if any Title
IV monies already exist in the
student's package.
Do you want to allow
Banner to disburse a fund
to a student without
regard to his/her
academic standing? If
you set this option to Y,
the award and
disbursement validation
routines skip the
academic progress
check.
RFRMGMT
(Packaging
Options
Window)
Override
SAPR
a checked box
For example, you may want to
package or disburse a
particular institutional
scholarship to a student not
making satisfactory academic
progress, despite the fact that
the student is not eligible for
any other institutional or
federal aid.
When the award is
packaged (whether in
batch or online), do you
want to package this
award regardless of
whether or not any
general unsatisfied
tracking requirements
which prevent packaging
exist?
RFRMGMT
(Packaging
Options
Window)
Override
Rqmt
a checked box
A general tracking
requirement is defined as a
requirement which is not fund
specific, that is a requirement
that gets assigned as part of
the group assignment process.
2-108
Financial Aid 8.3
User Guide
Processing
January 2009
Policy Question
If Yes, then
use form
Should the award be used
to replace the student's
EFC in the calculation of
Need?
Use Option
Set Option To
Comments
RFRMGMT
(Packaging
Options
Window)
Replace EFC
a checked box
Field will replace EFC first.
When it has replaced 100% of
EFC, it will start to reduce
need. Banner reduces need if
the EFC replacement award is
greater than the EFC.
Should the award be used
to reduce the student's
need in the calculation of
Need?
RFRMGMT
(Packaging
Options
Window)
Reduce Need
a checked box
Will reduce need by amount
of award. The Replace EFC
and Reduce Need fields are
mutually exclusive. You
cannot check both options.
Should the fund be
processed through the
Loan Module?
RFRMGMT
(Packaging
Options
Window)
Loan Process
a checked box
If you check this field, you
can create fund rules in the
loan module for the key aid
year. If this field is checked,
you must not check the
Disburse field since loan
disbursement occurs from
within the Loan Module.
In order for the fund to be
packaged, is a Need
Analysis record required
to be on file?
RFRMGMT
(Packaging
Options
Window)
Need Analysis a checked box
A warning message alerts you
during packaging if a student
does not have a need analysis
record for the aid year in
which the fund is packaged.
When you add or change
the award in the student's
package, do you want
Banner to automatically
set the award letter
indicator on the student's
record for award letter
selection?
RFRMGMT
(Packaging
Options
Window)
Award Letter
Ind
You can use this indicator
with population selection to
select those students who
need an award letter. Once
you generate the award letter
through the Letter Generation
Process, the RLRLETR
Process changes the award
letter indicator on the
RPAAPMT, RPAAWRD, and
ROARMAN forms back to N
for the selected students.
January 2009
a checked box
Financial Aid 8.3
User Guide
Processing
2-109
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
If you use the Equity
packaging philosophy,
do you want this fund to
count in the computation
of the student's equity
level?
RFRMGMT
(Packaging
Options
Window)
Equity Fund
a checked box
Note that you must set up the
Pell fund code as an Equity
fund. Any fund with this
indicator checked reduces the
student's calculated equity
level in the packaging
process.
Do you want to identify
this fund as a fund that
you to count for NCAA
regulations?
RFRMGMT
(Packaging
Options
Window)
Count for
NCAA
a checked box
Banner does not perform any
processing on this data. It is
available for use in
conjunction with your
institutionally defined rules.
The Fund Aid Year Specific
Table (RFRASPC) contains
the RFRASPC_NCAA_IND field.
Should applicants be
able to accept/decline
this fund via the Web?
RFRMGMT
(Packaging
Options
Window)
Web Accept
Flag
a checked box
This allows the applicants to
do self-service on their award
package. They can only
accept or decline the entire
amount of the fund. They
cannot accept a partial
amount.
Is this fund a Direct Loan RFRMGMT
fund with a Rebate Fee
(Packaging
Percent?
Options
Window)
Rebate Fee
Percent
Percentage
amount of the
rebate
This percentage will be used
when processing the loan to
determine the correct amount
to award to the student.
If you process the fund
through the loan module,
what is the total
percentage of origination
and agency fees that you
want to deduct from the
gross loan amount for
calculating net expected
check amounts?
Loan Fee
Percent
Percentage of
fees to be
deducted from
the gross loan
amounts.
This percentage defaults into
the Loan Application records
created for the fund, but you
can override the percentage
on an individual student basis
on the RPAELAP and
RPALAPP forms. You can
use the calculated net amount
to memo the net amounts of
the anticipated checks and to
anticipate the receivable
amount.
2-110
RFRMGMT
(Packaging
Options
Window)
Financial Aid 8.3
User Guide
Processing
January 2009
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
What is the interest rate if RFRMGMT
this is a Direct Loan?
(Packaging
Options
Window)
Interest Rate
The percentage
of the Direct
Loan interest
rate.
The amount of the interest
rate for the direct loan.
What type of loan is this
Direct Loan?
RFRMGMT
(Packaging
Options
Window)
Direct Loan
Indicator
Sub
Unsub
PLUS
Other
This field is used to determine
how to process the loan.
If the fund is a grant or
scholarship, and you use
self-help packaging, do
you want to use any
portion of the fund to
reduce the student's selfhelp level?
RFRMGMT
(Packaging
Options
Window)
Self - Help
Reduction %
Percentage of
the award which
should reduce
self-help level
If the student has a preawarded fund with a self-help
reduction %, Banner uses that
percentage of the student's
award to reduce the calculated
self-help level for the student
during packaging.
Is this an Alternate Loan
fund?
RFRMGMT
(Packaging
Options
Window)
Alt Loan
Prog Type
Three-character
code to indicate
if this fund is an
alternative loan
fund as defined
by NCHELP.
Used by Packaging and Loan
processes to determine correct
edits to use.
When you package the
fund, how do you want to
round the aid year
award?
RFRMGMT
(Packaging
Options
Window)
Round Award
001 = $1
010 = $10
025 = $25
050 = $50
100 = $100
Note that Banner rounds
down all awards to the nearest
specified dollar amount.
If the award is scheduled
between terms (if the
Auto Schedule field is set
to Y (Yes), how do you
want to round the term
award?
RFRMGMT
(Packaging
Options
Window)
Round
Schedule
RC Rd Cents
RD Round $
TC Trun Cts
TD Trun $
Round Cents
Round Dollars
Truncate Cents
Truncate Dollars
Does the fund have a
limit on how much
Banner can award to a
student based on
estimated tuition and
fees, etc.?
RFRMGMT
Budget
Component
Rules
Window
Valid Budget
Components
Banner only packages the
fund up to the sum of the
defined budget components,
or to the eligible packaged
amount - whichever is less.
January 2009
Financial Aid 8.3
User Guide
Processing
2-111
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
When you award a fund RFRMGMT
to a student, are there any
additional requirements
which the student must
satisfy before you memo
or disburse the fund?
Tracking
Requirements
Window
Valid Tracking
Codes
When you package the award,
Banner posts these tracking
codes to the student's tracking
record. You cannot enter
tracking codes that prevent
packaging here. Banner posts
these tracking requirements
with a system indicator of F
Fund. If you delete the award
that is associated with the
tracking requirement, Banner
also deletes the tracking
requirement provided the
requirement has not already
been satisfied.
When you award a fund RFRMGMT
to a student, are there any
specific messages you
would like to appear on
the award letter
regarding the specific
award?
Message
Assignment
window
Valid
Message
Codes
When you generate award
letters and the student has the
specific fund in their package,
the message prints on the
letter. A Letter Generation
variable for fund messages
must exist in the letter
definition in order for the
messages to print.
Do you have any
institutional specific
awarding rules for the
fund?
RORRULE
(using Rule
Type Fund
Awarding)
Define valid
conditions
The Award Validation process
checks to assure that the
student meets these defined
conditions for the fund.
Are any of the
institutionally specific
awarding rules for the
fund specific to a group
of students?
RORRULE
(using Rule
Type
Packaging
Group Fund
Awarding)
Define valid
conditions
The Award Validation process
checks to assure that the
student meets these defined
conditions for the fund based
on the student's specific
packaging group. Banner only
validates these rules when
you automatically package
the fund in batch or online
modes.
2-112
Financial Aid 8.3
User Guide
Processing
January 2009
Banner Financial Aid Global Packaging
Options
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
Do you want to use the
student's reported expected
enrollment for various
packaging functions if the
student reported an expected
enrollment?
RPROPTS
Use
Estimated
Enrollment
a checked box
If you do not check this box,
Banner uses the Default
Estimated Enrollment value.
Estimated enrollment is used
in packaging, exemptions &
contracts, Pell awarding, etc.
What default enrollment
would you use to package a
student if the student did not
report an expected
enrollment, or if you chose
not to use the student's
expected enrollment in the
preceding option?
RPROPTS
Default
Estimated
Enrollment
1 = Full-time
2 = ThreeQtr
3 = Halftime
4 = Less-half
This is a required field. You
must enter one of the
indicated values.
Do you wish to package a
student if the student's EFC
is an estimate?
RPROPTS
Package
Using
Estimated
EFC
a checked box
If you do not check this box,
the student will not be
packaged if the EFC is
estimated for the current Need
Analysis record.
RPROPTS
Package if
SAR C Flag
Exists
a checked box
Do you wish to default
RPROPTS
increased amount of Stafford
Loan?
Additional
Stafford
Elig
Default
a checked box
When this indicator is set (that
is, checked), independent
students will automatically be
eligible to receive the higher
amount of the unsubsidized
Stafford loan.
Where to get information for
packaging?
Source of
Award
History
B = Banner
N = NSLDS
This is a required field. When
determining award
cumulatives, where should
that come from.
January 2009
RPRPOTS
Only N is valid
for 0607 and
beyond
Financial Aid 8.3
User Guide
Processing
2-113
If Yes, then
use form
Policy Question
Use Option
Set Option To
Comments
By setting this indicator to
checked, the user can mass
accept awards for an applicant
from the RPAMACC form.
Do you wish to allow the
user to mass accept awards
for student?
RPROPTS
Allow Award
Mass Accept
a checked box
Do you wish to limit the
amount of time an applicant
has to respond to an offer of
aid?
RPROPTS
Offer
Expiration
Days
Number of Days Once the number of days
specified in this field has
expired, you have the
opportunity to automatically
cancel all unaccepted awards
or simply to get a report of
them by running the
RPRCNCL report.
Do you wish to assign any
tracking requirements
specific to a fund when it is
awarded?
RPROPTS
Tracking
Requirement
Status
The appropriate
Tracking
Requirement
Status
This is a required field. The
value will default when the
fund is awarded.
Do you want to interface
selected exemptions from
the Banner Student
Accounts Receivable
Module so that you can
count the exemptions as a
resource in the student's aid
package?
RPROPTS
Interface
Exemptions
a checked box
Exemptions will only be
interfaced for students who
are authorized for the
exemption on TSAEXPT. If
estimated amounts are desired
prior to actual A/R postings,
use the Exemption Rules form
(RPREXPT).
Do you want to interface a
selected third-party contract
from the Banner Student
Accounts Receivable
Module so that you can
count it as a resource in the
student's aid package?
RPROPTS
Interface 3rd
Party Cont
a checked box
Contracts will only be
interfaced for students who
are authorized for the contract
on TSACONT. If estimated
amounts are desired prior to
actual A/R postings, use the
Contract Rules form
(RPRCONT).
2-114
Financial Aid 8.3
User Guide
Processing
January 2009
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
If you choose to interface
RPROPTS
exemptions and/or contracts,
do you want to always use
the estimated amount of the
exemption or contract as a
resource in the student's aid
package?
Always Use
Estimated
a checked box
If this field is unchecked,
Banner uses the estimated
amount as a resource until the
actual amount is paid. When
paid, Banner uses the actual
amount
If you choose to interface
RPROPTS
exemptions and/or contracts,
do you want to assume that
the student is enrolled fulltime for the purposes of
estimating the amount of the
exemption or contract prior
to its payment?
Assume Full
Time
a checked box
If this field is unchecked,
Banner uses the proration
percentages based on the load
to calculate the estimated
amount. If this field is
checked, the estimated
amount comes from the rules
(RPREXPT or RPRCONT).
If you decided in the
RPROPTS
previous option not to
assume full-time for the
purposes of estimating the
amount of the exemption/
contract, how do you want to
prorate the estimated amount
based on the student's
expected load?
3/4 Time Pct Enter
1/2 Time Pct Percentages for
Less 1/2 Time each load option
Pct
Note that when you calculate
the estimated amount based
on the load, the student's load
comes from the reported data
first, (if you check the
Estimated Enrollment - Pell
field); it will then default to
the Default Estimated
Enrollment value.
Factors Determining Whether an Online/
Batch Award is Packaged
The list that follows itemizes the validation criteria used in the batch/online award
validation process with the reject messages which would appear online if the validation
condition failed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-115
2-116
Reject Message
Award Validation Condition
Award Not Packaged - Applicant
Has Holds
Holds cannot exist on the ROAHOLD form that prevent
packaging.
Award Not Packaged Outstanding Requirements
Check if there are any unsatisfied tracking requirements
that prevent packaging on the RRAAREQ form.
Award Not Packaged - Violates
Group Min or Max
If you are performing automated packaging, the award
must fall within the minimum and maximum award
levels set for the packaging group on the RPRGFND
form.
Award Not Packaged - Violates
Group Award Rules
If you are performing automated packaging, the
packaging group awarding rules cannot be violated by
the applicant or by the award on the RORRULE form
(Packaging Group Fund Award Rule Type).
Award Not Packaged - Must
Reduce Need
The award must reduce the calculated need if a federal
fund (except Pell) has been previously awarded.
Award Not Packaged -Cannot Be
a Federal Fund
The award cannot be a federal fund (except Pell) if an
award that does not reduce need has been previously
awarded.
Award Not Packaged -Exceeds
Unmet Need
If the award reduces need, the need must still be
available.
Award Not Packaged - Exceeds
EFC
If the award replaces EFC, EFC and/or unmet need must
still be available.
Award Not Packaged -Violates
Fund Matching Rules
The applicant or the award cannot violate the fund rules
on the RORRULE form using Fund Award Rule Type.
Award Not Packaged - Money Not
Available for Fund
The fund must have the amount of the award available
to offer. Use the RFIBUDG form to display fund
balances and the RFRMGMT form to update fund
balances.
Financial Aid 8.3
User Guide
Processing
January 2009
Reject Message
Award Validation Condition
Award Not Packaged - Violates
Fund Min or Max
The award must be within the minimum and maximum
fund award levels on the RFRMGMT form.
Award Not Packaged - Unsat Prog The student is not making satisfactory academic
(Institutional)
progress for an institutional program. Review the
student’s status in the Satisfactory Academic Progress
window of the Applicant Status form (ROASTAT).
Award Not Packaged -Unsat Prog
(State Aid)
The student is not making satisfactory academic
progress for at the state aid level. Review the student’s
status in the Satisfactory Academic Progress window of
the Applicant Status form (ROASTAT).
Note
All of the award validation conditions that follow are only checked if the
„
fund is associated with a federal Fund ID.
Reject Message
Award Validation Condition
Award Not Packaged -- Applicant
Not US Citizen
The RNANAxx form must indicate that the applicant is
a citizen or eligible non-citizen.
Award Not Packaged -Unsat
Progress (All Aid)
The ROASTAT form must indicate that the applicant is
making satisfactory academic progress with a code that
permits packaging.
Award Not Packaged Applicant in Default
The RNANAxx, RNARSxx, RHAPTRN, RNASLxx or
RHATINF form must indicate that the applicant is not in
default on a Title IV loan.
Award Not Packaged -- Applicant
Owes Refund
The RNANAxx, RNARSxx, RHAPTRN, RNASLxx1
or RHATINF form must indicate that the applicant does
not owe a refund on a Title IV grant.
Award Not Packaged -Exceeds
Allowable Maximum
The award amount cannot be greater than the calculated
budget minus the sum of the resources and other aid.
Award Not Packaged -- Exceeds
Cumulative Amount
The new awarded amount, plus the previously awarded
amounts, cannot exceed the hard-coded cumulative
maximum amounts on the Federal Rules Inquiry form
(RPIFEDR).
Award Not Packaged -- Load
Invalid For Fed Fund ID
The applicant's load and class cannot violate the Federal
rules on the RPIFEDR form.
Award Not Packaged - Class
Invalid for Fed Fund ID
January 2009
Financial Aid 8.3
User Guide
Processing
2-117
2-118
Reject Message
Award Validation Condition
Award Not Packaged - Violates
Fed Fund ID Limits
The award must fall within the minimum and maximum
award levels on the RPIFEDR form.
Award Not Packaged - - Prior
Bachelor Degree
If the fund has a Federal Fund ID of Pell, the applicant
cannot have a prior degree on the RNANAxx form.
Award Not Packaged - Pell EFC
Not Determined
If the fund has a Federal Fund ID of PERK, SEOG, or
STFD, the applicant must have a Pell EFC on the
RNARSxx form.
Award Not Packaged -- SAR CFlags Exist
The award is not packaged since SAR C Flags exist.
Award Not Packaged -- Ind.Stu
Ineligible For PLUS
The award is not packaged since the individual student
is ineligible for a PLUS loan.
Award Not Packaged - No Pell for
Profs or Grad
The award is not packaged since Pell is not available for
professional or graduate students.
Award Not Packaged - Est EFC/
Pell Ineligible
The award is not packaged since the estimated EFC for
Pell is ineligible.
Award Not Packaged -- No Pell
Budget
The award is not packaged since no Pell budget exists
for the student.
Award Not Packaged - Unsat.
Progress
(Title IV)
The student is not making satisfactory academic
progress for a Title IV program. Review the student’s
status in the Satisfactory Academic Progress window of
the Applicant Status form (ROASTAT).
Award Not Packaged - Unsat
Progress (Federal Aid)
The student is not making satisfactory academic
progress for Federal aid. Review the student’s status in
the Satisfactory Academic Progress window of the
Applicant Status form (ROASTAT).
Award Not Packaged - Override
Need Exceeds Budget
The award is not packaged since the need override
exceeds the budget.
Award Not Packaged - No Need
Analysis Record
The award is not packaged since a need analysis record
has not been established.
Financial Aid 8.3
User Guide
Processing
January 2009
Manually Scheduling Awards
Banner initially distributes awards by terms according to rules set on the Award and
Disbursement Schedule Rules form (RFRASCH) or the Default Award and Disbursement
Schedule Rules form (RFRDEFA) in the Funds Management Module. You can change the
award schedule for a specific student and fund on the second page of the Award form
(RPAAWRD), on the Package Maintenance form (RPAAPMT), or on the Financial Aid
Record Maintenance form (ROARMAN).
Award Amount Change - When you manually change the amount of an award, it is
scheduled according to the distribution percentages previously entered for the fund on
page two, rather than the schedule defined on one of the award schedule rules forms.
Therefore, if a student should receive an award with the unique pattern of 25% in the Fall
and 75% in the Spring and the amount of the award changes, the new amount will still be
scheduled at 25% in the Fall and 75% in the Spring.
Aid Period Change - If you change the student's aid period, both new awards and revised
awards will be scheduled according to the rules on the Award and Disbursement Schedule
Rules form (RFRASCH) or the Default Award and Disbursement Schedule Rules form
(RFRDEFA). A change in the student's aid period is determined by comparing the list of
terms in the fund's award schedule to the list of terms for the student's current aid period.
Note
An award status code change by itself does not cause the award to be
„
rescheduled.
Adding Terms to an Award Schedule
The only time you can manually add a new term to a student's award schedule is when that
new term is valid for the student's current aid period but it wasn't part of the student's aid
period when the award schedule was originally created. When you add a new term record
to the award schedule, Banner does not change the way the other terms were scheduled.
Instead, Banner sums up all the terms for the fund, puts the new total through the award
validation process and places the new total in the RPRAWRD table and then displays it in
the Fund Awards section of the Award form (RPAAWRD), the Package Maintenance form
(RPAAPMT), and the Financial Aid Record Maintenance form (ROARMAN). This is the
only situation which will cause the total award to change due to a change in one of the
term amounts. Normally, the total in the Fund Awards section needs to be changed and the
new total between terms in the award by term detail needs to be rescheduled.
The function to add a new term record is used, for example, when a student who was
originally in one aid period later decides to also attend a Summer term. If the Summer is
the last term for the aid year, the student's aid period can be changed to include that term.
To give the student an award for the new Summer term, insert a new term record into the
student's award schedule in the award by term detail section with the new Summer award
amount.
January 2009
Financial Aid 8.3
User Guide
Processing
2-119
This will not change the way other terms have been scheduled (and possibly already paid).
Banner will automatically add up all term amounts and calculate the new distribution
percents for each term based on the new total, and will package the new total. If the total in
the Fund Awards section is changed first, Banner might change the way other term
amounts have been scheduled.
The override indicators in the award by term detail of the Award form and Package
Maintenance form are used if the new total fails the award validation process for one of
the reasons that can be overridden. The override options available in the award by term
detail are the same as in the Fund Awards section; enter a Y to override the specific reason
for the validation failure or an A to override all possible reasons.
For the override to work, you must package the fund and save first. These overrides
include: Unmeet Need; Replace TFC; Trck Req; Fed Limit; and Fund Limit.
Warning
Entering an override prior to a commit will not yield the expected results.„
Award by Term Procedure
A quick award process exists which makes it easier to maintain awards which need to be
changed due to:
• a student's change in anticipated course load affecting only one term, or
• a student's change in enrollment plans so as not to be enrolled for all terms as
previously expected.
Consider the following two award maintenance scenarios and the current Banner Financial
Aid operational steps, either of which allow you to change the award to the desired
amount.
A student changes enrollment to half-time Fall and full-time Spring. The steps to change
the award were:
For Option 1
1. Change the student's budget on the Applicant Budget form (RBAABUD).
2. Change the total award in the Funds Award section of the Award form (RPAAWRD).
3. While still in the Funds Award section of the RPAAWRD form, save the change and
wait for award validation to accept the new award.
4. While on the RPAAWRD form, go to the Fund Awards by Term window and change
the award by term records to reflect a half-time Fall award and a full-time Spring
2-120
Financial Aid 8.3
User Guide
Processing
January 2009
award, ensuring that the sum of the term awards exactly equals the total that was
entered in the Funds Award section (or else the term changes will be rejected).
For Option 2
1. First enter the changed term award amounts on the Fund Awards by Term window of
the Award form or Package Maintenance form.
2. Save the changes and Banner proceeds as follows:
• The sum the term awards for the changed fund is compared to the existing total
award (that would initially have been displayed in the Funds Award section).
• If the sum of the term awards differs from the (existing) award total, a pop-up
window is displayed with a warning message requesting verification that the award
total is to be changed to the sum of the changed term awards.
To position your cursor on the proper choice you can use the Enter key or the Tab key.
Once you select your choice, press the Accept (Save) key.
• If you indicate that you want to change the award, the award is repackaged using
the new total which includes a validation against awarding rules, and all changes
are committed.
• If you do not want to change the award, the attempted term changes will be rolled
back.
• Banner recalculates the award percents for each term based on the new term
amount and updates those fields.
• The newly packaged amount can now be seen in the Funds Award section of the
Award form or the Package Maintenance form.
When you use the Award form (RPAAWRD), you can make changes to multiple terms and
multiple funds with a single Save. Since the Award by Term Block on the Package
Maintenance form (RPAAPMT) only deals with one fund at a time, multiple terms can be
done only for the selected fund.
Identifying Students Needing New or
Revised Award Letters
It is possible to identify students who may need a new or a revised award letter. The
Packaging Group Information section of the Award form (RPAAWRD), Packaging
Maintenance form, (RPAAPMT), and Financial Aid Record Maintenance form
(ROARMAN) display an Awrd Ltr field.
This field (RORSTAT_AWD_LTR_IND) is set to Y whenever the offered amount changes on
any fund in the student's package when you want changes to the fund to cause the award
January 2009
Financial Aid 8.3
User Guide
Processing
2-121
letter indicator to be set. If you want changes to a particular fund to cause the indicator for
the student to equal Y, you must check the Award Letter field on the Fund Management
form (RFRMGMT). Do not check this option if you do not want changes to a particular
fund to set the award letter indicator to Y.
You can use the Award Letter indicator (RORSTAT_AWD_LTR_IND) in population selection
to choose students who need a printed copy of an award letter. You could use the following
sample selection statement for this purpose: RORSTAT_AWD_LTR_IND = Y.
You can manually change the award letter indicator on the three packaging forms. For
example, you may not want to send a new award letter to a student if an award only
changes by a small amount. You could change the indicator back to N so that you do not
select the student for a new award letter. Or, if you want a particular student to receive a
duplicate copy of his latest award letter, change the indicator from N to Y. Banner now
selects the student for a new letter even though there were no changes to his award
package.
To create a population of students who should receive an award letter you should run the
GLBDATA process to find the students whose award letter indicator = Y. When you run
the letter extract process (GLBLSEL) for your award letter, you should use the population
just created. To reset the award letter indicator back to N you should run a report called
RLRLETR immediately following the letter print process (GLRLETR). The parameters
for this process must be the same as the population you just used to print the award letters.
It also asks for an aid year code so it knows which award letter indicator to reset. This
report will reset the award letter indicator back to N so the student will not be reselected
for another award letter unless there have been subsequent changes to the award package.
2-122
Financial Aid 8.3
User Guide
Processing
January 2009
Banner Financial Aid Global Disbursement
Options
Policy Question
If Yes, then
use form
Use Option
Set Option
To
Comments
If the student has not
accepted their
charges for the term
in which the
disbursement is run,
do you want to allow
the student to receive
the financial aid
credit on their
account?
RPROPTS
Disburse If
Charges Not
Accepted
a checked
box
If you do not check this box, the
fund is not paid if the student has not
accepted their charges for the term
in which you run disbursements. In
this case, the financial aid could be
authorized but not paid.
If the student has an
unresolved SAR C
flag, do you want to
pay the student?
RPROPTS
Disburse if
SAR C Flag
Exists
a checked
box
If you do not check this box, the
fund is not paid.
Do you want to allow
the fund that was
previously paid to
memo?
RPROPTS
Allow
Memos
When
Previously
Disbursed
a checked
box
If checked, it will allow a fund that
has previously paid for the term you
are trying to disburse, to memo.This
includes memoing amounts that
have paid or authorized then backed
out to zero. It also includes memo
amounts that are for future
scheduled disbursements when
earlier scheduled disbursements
have been paid or authorized and
not backed out.
When you disburse
an award, which
enrollment do you
want to use to
determine the
student's load at the
point of the
disbursement as the
default value?
See Below
See Below
See Below
The value entered in this field will
only be used if there is not a
disbursement enrollment option
entered for the term of disbursement
on the Enrollment Cut Off Dates
Rules Window.
January 2009
Financial Aid 8.3
User Guide
Processing
2-123
Policy Question
If Yes, then
use form
Use Option
Set Option
To
Comments
.... Expected
Enrollment?
RPROPTS
Enrollment
E xpected
Option for
Disbursement
Banner uses the student load from
the student reported expected
enrollment from the current Need
Analysis record, (if you check the
Estimated Enrollment - Pell field).
If this information does not exist, or
if you do not check the Estimated
Enrollment - Pell field, Banner uses
the Default Estimated Enrollment.
.... Adjusted
Enrollment?
RPROPTS
Enrollment
Adjusted
Option for
Disbursement
Banner calculates the student’s
adjusted enrollment as the student
billing hours for the term minus any
courses listed on the Audit Grading
Mode form (RPRAUDT), minus
any courses in the student’s
schedule where the course
registration status indicates that the
course should not count in
enrollment.
This means that dropped or
canceled courses for the term are not
counted in enrollment, but noncredit remedial courses are counted
even though these courses do not
carry real credit hours. Banner uses
adjusted financial aid hours if this
information exists, otherwise it uses
current adjusted hours. The adjusted
hours are converted to load based on
the credit hour rules specified on the
ROAINST form.
2-124
Financial Aid 8.3
User Guide
Processing
January 2009
Policy Question
If Yes, then
use form
Use Option
Set Option
To
Comments
.... Actual
Enrollment?
RPROPTS
Enrollment
Billing
Option for
Disbursement
Banner uses the student's financial
aid billing hours for the term of
disbursement if it exists, or else
Banner uses the current billing
hours. The billing hours are
converted to load based on the credit
hour rules found on the ROAINST
form.
Would you like to
setup different values
of enrollment to be
used when disbursing
funds on a term-byterm basis?
RPROPTS
(Enrollment
Cut Off
Dates Rules
Window)
Term Code
and
Disbursement
Enroll Option
If a rule exists on this window for a
term, it will override the Enrollment
Status window on the prior window
of the form.
Term code
for this
specific
enrollment
status and
the
enrollment
status you
wish to have:
Expected
Adjusted
Billing
At what date in the
term do you wish to
treat aid that has been
paid differently than
at the beginning of
the term?
January 2009
RPROPTS Cut Off Date
(Enrollment
Cut Off
Dates Rules
Window)
Date to be
used
This is a required field.
Financial Aid 8.3
User Guide
Processing
2-125
Banner Financial Aid Fund Specific
Disbursement Options
Policy Question
Do you want to give
the student anticipated
credit for the fund
prior to payment of the
fund?
If Yes, then
use form
RFRMGMT
(Packaging
Options
Window)
Use Option
Set Option To
Comments
Memo Credit
Accepted
or
Offered
If this field is set to
Accepted, the memo goes
out only if the student
accepts the award and all
memo validation criteria
have been met.
If this field is set to
Offered, the memo goes
out if the status of the
award is either Offered or
Accepted and the student
has met all memo
validation criteria.
How do you want to
disburse the fund to
the student's account?
RFRMGMT
(Packaging
Options
Window)
Disburse
System
or
Manual
If this field is set to
System, Banner
automatically creates the
disbursement (from either
RFRDEFA or RFRASCH)
schedule when the student
accepts the award.
If this field is set to
Manual, Banner does not
automatically create a
schedule, but does allow
you to manually create a
disbursement schedule for
the student and fund.
If the student is
enrolled, at the point
of disbursement, for
less hours than what
you anticipated when
you packaged, do you
still want to disburse
the fund?
2-126
See Below
Financial Aid 8.3
User Guide
Processing
See Below
See Below
January 2009
Policy Question
...No, do not disburse.
If Yes, then
use form
Use Option
RFRMGMT
If Disb Load
(Disbursements Code > Pckg
Option
Load Code
window)
Set Option To
Comments
N = No
Disbursement
If an amount has already
been paid, it may be
backed out based on the
back out options set in the
If Ineligible Before CutOff Date and Ineligible
After Cut-Off Date
fields.
By setting the option to No
Disbursements when the
Disb Load Code > Pckg
Load Code, a
Disbursement Error/
Reject is created and the If
Ineligible fields are then
...Yes, disburse the
amount of the award.
RFRMGMT
If Disb Load
(Disbursements Code > Pckg
Option
Load Code
window)
D = Disburse
100%
Disburse the amount of the
award in the student's
package despite the load.
...Yes, but prorate the
amount of the award
that you want to pay
based on the load.
RFRMGMT
If Disb Load
(Disbursements Code > Pckg
Option
Load Code
window)
P = Prorate
The amount of the award
in the student's package is
prorated based on the
payment percentages for
the student's load (load is
determined based on the
Enrollment Option for
Disbursement field).
If an amount greater than
the prorated amount has
already been paid, you
may back out the
difference based on your
back out options as set in
the Ineligible Before Cut-
January 2009
Financial Aid 8.3
User Guide
Processing
2-127
Policy Question
If Yes, then
use form
Use Option
Set Option To
Payment%
for 3/4 Load
Payment%
for 1/2 Load
Payment%
for Less 1/2
Load
Enter
When Banner calculates
percentages for the prorated amount based
each load option on the load, it determines
the student's load based on
the Enrollment option for
Disbursement option.
If you choose to
prorate the amount of
the award when the
student is enrolled at
less than the
anticipated amount
during packaging,
how do you want to
prorate the award?
RFRMGMT
(Disbursements
Option
window)
If an award is
scheduled for
disbursement in
multiple payments
within a term, and the
student's load changes
between scheduled
disbursements, how
do you want Banner to
calculate the amount
of the subsequent
disbursement?
RFRMGMT
Change Load
(Disbursements During Term
Option
window)
Based on the
A - (Award
Scheduled)
or on the
S - (Scheduled
Disbursement)
Comments
If the Disb Load Code >
Pckg Load Code field is
either D or P, this indicator
calculates the
disbursement amount. If it
is set to A, the scheduled
award for the term is
multiplied by the payment
percentages based on the
student's load and the
result is paid.
If it is set to S, the
scheduled disbursement is
multiplied by the payment
percentages based on the
Are there any
institutional specific
disbursement rules for
the fund?
RORRULE
(using Rule
Type Fund
Disbursement)
Do you want to apply
the same enrollment
edits that are used for
disbursement for
determination of what
can be memo’d?
RPROPTS
(Disbursement
Options
Window)
2-128
Financial Aid 8.3
User Guide
Processing
Use Disb
Enroll Edits
for Memo
a checked box
When this box is checked,
it will prevent aid from
memoing if this student is
not enrolled. It will use all
of the same edits for
enrollment as the
disbursement process,
including at least half time
for loans.
January 2009
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
If a student has
received a payment for
financial aid and
subsequently the aid
office reduces the
amount of the
student's award, do
you want to reverse
the difference between
the paid award and the
new award amount on
the student's account?
RFRMGMT
(Disbursement
Options
Window)
Recoup when a checked box
Award
Reduced
Use this option to recoup
aid from the account when
the award amount is less
than the amount which has
already been paid. The
disbursement process
places a negative payment
amount on the student
account for the difference.
If a student has
received payment and
their enrollment
changes, but the
student is still eligible
and you want to pay
that portion of
eligibility to the
student account?
RFRMGMT
(Disbursement
Options
Window)
Recoup
D = Disregard
Proration rules are used
when the student has no
disbursement errors.
If a student has
received payment but
now has disbursement
errors (for example,
Student Not Enrolled,
Outstanding Tracking
Requirement) and you
want to leave existing
disbursements?
RFRMGMT
(Disbursement
Options
Window)
Recoup
D = Disregard
Disregard will make no
adjustment to student
account.
If a student has
received payment but
now has disbursement
errors (for example,
Student Not Enrolled,
Outstanding Tracking
Requirement) and you
want to bring
disbursements for
term back to zero?
RFRMGMT
(Disbursement
Options
Window)
Recoup
B = Backout
Disbursement
Backout will reverse
credit to student account
January 2009
Financial Aid 8.3
User Guide
Processing
2-129
Policy Question
If Yes, then
use form
Use Option
Set Option To
If a student has
See Below
received a payment for
an award in a specific
term, and the student
becomes ineligible for
the award after it is
paid, do you want
Banner to back out the
payment which has
been made?
See Below
See Below
...No, do not back out
the payment that has
already been made.
RFRMGMT
(Disbursement
Options
Window)
If Ineligible
D = Disregard
Before CutOff Date
If Ineligible
After Cut-Off
Date
The disbursement process
does nothing if the student
becomes ineligible after a
payment has been made.
Ineligibility is defined as
failing any of the
disbursement validation
criteria. (You can set this
option differently based
on if it is on or before or
after your system defined
cut-off dates on the
RPROPTS form.)
...Yes, backout funds
RFRMGMT
(Disbursement
Options
Window)
If Ineligible
B = Backout
Before Cutdisbursements
Off Date
If Ineligible
After Cut-Off
Date
If the student is ineligible,
regardless of why, funds
will be backed out with the
B option.
...Yes, back-out the
entire amount of the
payment which has
been made for the
term.
RFRMGMT
(Disbursement
Options
Window)
If Ineligible
B = Backout
Before CutDisbursements
Off Date
If Ineligible
After Cut-Off
Date
The disbursement process
backs out the entire
amount of the payment for
the term. Ineligibility is
defined as failing any of
the disbursement
validation criteria. (You
can set this option
differently based on if it is
on or before or after your
system defined cut-off
dates on the RPROPTS
form.)
2-130
Financial Aid 8.3
User Guide
Processing
Comments
January 2009
Policy Question
...Yes, but back-out
only the amount of the
payment which has
not been applied to a
charge.
If Yes, then
use form
RFRMGMT
(Disbursement
Options
Window)
Use Option
Set Option To
If Ineligible
P = Payment not
Before CutApplied
Off Date
If Ineligible
After Cut-Off
Date
Comments
The disbursement process
backs out the amount of
the payment which has not
yet been applied to a
charge through the
application of payments
process. This option is
designed to reverse the
amount of the payment
that you could potentially
refund back to the student
without changing the
amount that you already
used to pay the charges.
If you run disbursements
online, this option puts out
a request to include the
student in the next run of
the application of
payments process. This
option only performs a
back out when it is run in
batch mode.
If the student’s
enrollment changes
and they are eligible
for additional funds
and you want to apply
Proration rules to
these funds
RFRMGMT
(Disbursement
Options
Window)
If a student has been
selected for
verification, and the
student's verification
has not yet been
completed, do you
want to disburse the
aid to the student
anyway?
RFRMGMT
(Disbursement
Options
Window)
January 2009
D = Disregard
If Ineligible
Before Cutchecked
Off Date
If Ineligible
After Cut-Off
Date.
If no disbursement errors
exist and disbursement
options are set to Recoup
and Disregard, proration is
applied for enrollment
changed.
Recoup when
award is
reduced.
If Selected
for
Verification
but
Verification
is not
complete
a checked box
You can check this option
for non-Federal funds so
the verification process
does not hold up these
funds. If unchecked,
Banner does not disburse
aid to the student.
Financial Aid 8.3
User Guide
Processing
2-131
Policy Question
If Yes, then
use form
Use Option
Set Option To
Comments
If a student has any
general unsatisfied
tracking requirements
on their tracking
record which prevent
disbursement, do you
want to pay the nonFederal fund anyway?
RFRMGMT
(Disbursement
Options
Window)
Override
General
Tracking
Requirements
a checked box
You can only use this
option for non-Federal
funds. (If the fund is a
Federal fund, you cannot
override general tracking
requirements which
prevent disbursement. A
general tracking
requirement is defined as
one which is not fund
specific.)
When you disburse the
award, is a promissory
note required for
disbursement?
RFRMGMT
(Disbursement
Options
Window)
Promissory
Note
Required
a checked box
If this field is checked, this
option creates promissory
note requirements for all
terms in which the student
receives the fund when the
award is accepted in the
student's package.
The disbursement process
assures that the student has
signed (satisfied) that
requirement prior to the
payment of the fund.
2-132
Financial Aid 8.3
User Guide
Processing
January 2009
If Yes, then
use form
Policy Question
Use Option
Set Option To
Comments
Term Code
a checked box
When this box is checked,
all disbursement activity
for that term will be
prevented.
Does the fund have a RFRMGMT
limit on how much
you can disburse to the
student based on the
actual tuition and fees,
etc.?
Detail Code
Rules
window
Valid Detail
When you disburse the
Codes defined as fund, Banner only pays an
charges
amount up to the sum of
the defined detail codes
for the term,. These rules
only specify the maximum
amount you can pay to the
account and in no way
determine how to apply
the payment to specific
charges. This function
occurs in the Accounts
Receivable Application of
Payments Process.
Are there any fundspecific tracking
requirements that
should be created
when the fund is
awarded that should
prevent the
disbursement of this
fund?
Tracking
Code
Appropriate
Tracking
Requirement
Code
Is there a term where
all disbursement
activity should be
prevented or stopped
for a period of time?
RPROPTS
Disbursement
Locks
RFRMGMT
Tracking
Requirements
If populated, a new
requirement will be
created when the fund is
awarded and will not
allow disbursement (setup
on RTVTREQ) of this
fund until satisfied.
Rules can be set on
RTVTREQ to prevent
memo or disbursement
until satisfied. Note: If the
fund is removed from the
student’s award and the
requirement has not been
satisfied, it will
Note
If an award is cancelled, declined, or reduced to a zero award amount,
the Disregard setting will be ignored and the previous payment will be
„
backed out.
Note
The Disregard setting will only affect awards which have been partially
„
disbursed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-133
Disbursement Validation Edits
The disbursement validation process checks user-defined rules, hardcoded rules, and
federal rules before Banner actually processes a payment or authorization. The following
list outlines the items that the disbursement validation process checks before processing a
payment or an authorization. The RPEDISB.log file lists the reject messages associated
with each factor if the disbursement is not paid or authorized.
2-134
Financial Aid 8.3
User Guide
Processing
January 2009
Reject Message
Disbursement Validation Condition
Applicant Has Holds
Determines whether there are active holds that prevent
disbursements on the ROAHOLD form.
Outstanding
Non-Fund Req
Checks for non-fund specific tracking requirements that prevent
disbursements on the RRAAREQ form. (Also checks to see if the
fund is supposed to override non-fund specific tracking
requirements.)
Outstanding Fund Req
Checks fund-specific tracking requirements that prevent
disbursements for that fund on the RRAAREQ form.
Applicant is Not
Enrolled
If the institutional option is set to disburse using actual enrollment
(Code A or B), Banner checks for the actual enrollment of the
student. If there is no actual enrollment, the Disbursement Load is
set to 5.
If the institutional option is set to use expected enrollment, then it
uses the expected enrollment from the RCRAPP1 table. If there is
no expected enrollment in RCRAPP1 then it uses the default
enrollment from the RPBOPTS table (Packaging Options formRPROPTS).
L/V Term Not in
ROAINST
L/V Term is not in ROAINST
Disbursement Amount
Greater than Loan
Amount
The disbursement amount is greater than the loan amount.
Charges Have Not
Been Accepted
Charges have not been accepted.
COD Rejected
Disbursement Record
The disbursement record was rejected by COD.
Disbursement Requires
Approval From COD
Disbursement requires approval from COD.
Disbursement
Reference No. 91-99 Or
MRR Block
Disbursement reference number 91-99 or MRR block.
A Previous DL
Disbursement Number
is Undisbursed
A previous Direct Loan disbursement number is undisbursed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-135
2-136
Reject Message
Disbursement Validation Condition
A Disbursement With
Earlier Date is
Undisbursed
A disbursement with an earlier date is undisbursed.
Prom Req Not Satisfied
Checks for the receipt of a promissory note for the term being
disbursed if the fund requires a promissory note. on page 2 of the
RRAAREQ form.
Award Not Accepted
Ensures that the award is in an accepted status. Use the
RPAAWRD, RPAAPMT, ROARMAN, or RPAMACC form to
update the award status.
Violates Fund Disb
Rules
Violates user-defined fund disbursement rules (Fund
Disbursement Rule Type) on the Financial Aid Selection Rules
form (RORRULE).
Verification Incomplete
Determines if verification is required/completed. If the fund
disbursement rule on the Fund Management form (RFRMGMT) is
set to not disburse with an incomplete verification and verification
is incomplete, then a disbursement will not take place. Otherwise,
the verification of the required/completed information is ignored
and the disbursement takes place.
Not Making Sat
Acad Prog
(All Aid)
Checks the satisfactory academic progress of the student. This is
determined with the satisfactory academic progress code for the
highest term code that is less than or equal to the term code for
which the disbursements are performed. Use the ROASTAT form
to view or update SAP codes.
Orig Rec Not
Acknowledged
Origination record not acknowledged.
Prom Note Not
Acknowledged
Promissory Note not acknowledged.
Loan Cancelled No Disb
Loan has been cancelled without disbursements.
Disb Cancelled- No
Disb
Disbursement cancelled without disbursements.
No Authorization for
EFT Disbursement
No authorization for EFT disbursement.
Loan Status is Held/
Inactive - No Disb
The loan status is on hold or inactive, no disbursements.
Financial Aid 8.3
User Guide
Processing
January 2009
Reject Message
Disbursement Validation Condition
Award Status for Loan is Award status for loan has been canceled or declined without
Cancel/Decline - No
disbursements.
Disb
Not Making Sat Acad
Prog (Institutional)
The student is not making satisfactory academic progress for an
institutional program. Review the student’s status in the
Satisfactory Academic Progress window of the Applicant Status
form (ROASTAT).
Not Making Sat Acad
Prog (State Aid)
The student is not making satisfactory academic progress for a
state program. Review the student’s status in the Satisfactory
Academic Progress window of the Applicant Status form
(ROASTAT).
No General Student
Record for Aid Period
Term(s)
A student record does not exist for the aid period/term.
If the institutional option is set to not disburse unless charges have
been accepted, Banner checks to see if the student's charges have
been accepted.
Checks that the fund being disbursed is not locked for the term.
You can verify locked funds on the Disbursement Locks window
of the Fund Management form (RFRMGMT).
The disbursement validation process checks that sufficient funds
are available to process the disbursement. If these funds are not
available, Banner places a lock on the fund for the term. You must
add more money to the fund and manually remove the lock on the
Disbursement Locks window of the Fund Management form
(RFRMGMT).
If the fund is associated with detail codes on the Detail Code Rules
window of the Fund Management form (RFRMGMT), Banner
determines whether or not the student has those detail codes on his
accounts receivable record for the term. The process may reduce
the amount of the authorization/disbursement so that it does not
exceed the sum of the detail codes on the student's account that are
associated with the fund.
Note
The rules that follow are only checked if the fund is associated with a
federal Fund ID.
January 2009
„
Financial Aid 8.3
User Guide
Processing
2-137
Reject Message
Disbursement Validation Condition
Not in Eligible Program Checks that the student is enrolled in an eligible program. The
Major, Minor, Concentration Code Validation form (STVMAJR)
defines the eligible programs for financial aid.
Not Citz
Validates citizenship from the RCRAPP1 table for the current
record. Use the RNANAxx form to view and update citizen
information.
Applicant in Default
Ensures that the student is not in default on a Federal title IV loan
or owes a refund on a Federal title IV grant. Banner uses the
RCRAPP1 table and the Financial Aid Transcripts for this
determination. Use the RNANAxx, RNARSxx, RNASLxx form
to view and update this information.
Applicant Owes Refund
Enroll Inval/
Fed Fund ID
Cannot Get Class Code
Verifies that the minimum required enrollment for the fund has
been reached (as defined on the Federal Rules Table (Federal
Rules Inquiry form - RPIFEDR)).
Cannot Get
Federal Rules
2-138
Violates Pell Req
If the fund is Pell, the disbursement validation process verifies the
non-receipt of a degree by 7/1/xx in the RCRAPP1 table. Use the
RNANAxx form to view this information.
SAR Recvd Date
Not Present
If the fund is Pell, Banner searches for the receipt of a SAR (SAR
certified date on the Applicant Pell Grant form - ROAPELL).
SAR EFC Not =
System EFC
If the fund is Pell, Banner checks that the Primary SAR-EFC
matches the Primary Sys-EFC OR (the Primary SAR-EFC
matches the Secondary Sys-EFC AND the Secondary SAR-EFC
matches the Primary Sys-EFC). Use the ROAPELL form to view
this information.
Pell Elig Not
Determined
If the fund is SEOG, Perkins, Stafford, the validation process
checks whether or not Pell Grant eligibility has been determined
(Sys-EFC is not null). Review Pell Grant eligibility information
on the RNARSxx form.
Student/Par
CTRB Is Est
If the fund is a Title IV Federal fund, Banner ensures that the
student and parent contributions are official. Review student and
parent contribution information on the RNARSxx form.
Financial Aid 8.3
User Guide
Processing
January 2009
Reject Message
Disbursement Validation Condition
Disb Load > Pckg Load The disbursement process compares a student's enrollment load at
the time of disbursement to the enrollment load assumed at the
time of packaging if the institutional option is set to disburse using
actual enrollment. If the code for the student's load at the time of
disbursement is greater than the code for the expected load at
packaging time, the disbursement process does not disburse the
fund if the If Disbursement Load Code greater than Package
Load Code field is set to N (No Disbursement) on the
RFRMGMT form.
Error - Basic
Student Data
During the validation of Title IV Federal funds, Banner requires
data from the General Student Table (SBGSTDN) such as the
Level Code, Major Code and Student Type Code. Banner displays
the ERROR - BASIC STUDENT DATA message when a general student
record does not exist for the student in the Student System.
Unofficial for Title IV
If the fund is a Title IV Federal fund, Banner ensures that the
Official Source Indicator on the RNARSxx form is set to 1 for
Official. Check the value of this field on the RNARSxx form.
Error Selecting
Load Rules
This error occurs when rules have not been established in the
Credit Hours Block on the ROAINST form for a particular Term/
Aid Year/Level Code combination. You can view the student's
current level code on the Student form (SGASTDN).
Plus Cred Check
Not Appr
PLUS credit check was not approved.
Award Not Disbursed SAR C-Flags Exist
Award was not disbursed; SAR C flags exist.
January 2009
Financial Aid 8.3
User Guide
Processing
2-139
Reject Message
Disbursement Validation Condition
Not Making Sat Acad
Prog (Title IV)
The student is not making satisfactory academic progress for a
Title IV funded program. Review the student’s status in the
Satisfactory Academic Progress window of the Applicant Status
form (ROASTAT).
NOT Making Sat Acad
Prog (Federal)
The student is not making satisfactory academic progress for a
Federal program. Review the student’s status in the Satisfactory
Academic Progress window of the Applicant Status form
(ROASTAT).
No Affirmation
Received for Direct
Loan
The DL Affirmation Pilot field on the Institution Options form
(ROAINST) indicates whether your school participates in the
Direct Loan Affirmation Pilot Program and chooses to prevent
disbursements of Direct Loans to borrowers who do not authorize
the disbursement of funds under the Master Promissory Note
process. The Affirm Flag for the student should be checked in the
Disbursement Detail window of the Direct Loan Origination form
(RPALORG) if the student has authorized the disbursement.
Other Disbursement Considerations
Regulatory Compliance for Stafford Disbursements
Banner disburses all financial aid based on the enrollment option selected on the
RPROPTS form. You decide whether to disburse aid based on expected enrollment, billing
hours, or adjusted hours. Along with this option is the decision of whether to freeze hours
at a specific point in time. The decision to capture hours at a specific time, most likely at
the census date, allows your institution the opportunity to set a constant enrollment load
for the determination of all aid disbursements, without continually recouping monies
every time a student drops a class.
• In the case of the Stafford loans, the actual enrollment of the student must be
checked at the time of disbursement — requiring the use of Student system hours.
However, the process must take into account the consortium students who will not
have these hours for the terms in which they are in a consortium agreement.
Banner Student enrollment hours are maintained as records in the SFBETRM table.
The student could be attending another institution and should still get paid by the
local school.
The Consortium Indicator field on the ROAENRL form allows your institution to
flag a student as a consortium student for any one term. By setting the consortium
indicator flag, the Disbursement Process always checks the RORENRL hours for
all funds, and does not check for the flag for Charges Accepted.
2-140
Financial Aid 8.3
User Guide
Processing
January 2009
Disbursement Edits for Loans to Match Edits for other
Funds
• The Stafford disbursement process ensures that the award amount is not less than
the disbursement amount. No other funds disburse more than the award amount.
However, since these are loans and it is possible to have loans without awards, the
edit checks the loan amount instead of the award amount.
In those cases where you review this loan disbursement and determine that you still
want to disburse this loan, an override can be added on a loan disbursement by
disbursement basis to allow this to occur.
• There is also an edit for allowing you to determine whether to disburse or not when
the Package Load is greater than the Disbursement Load.
One of the fields in the Aid Year Specific Data - Disbursement Options window on the
RFRMGMT form, If Disbursement Load Code greater than Package Load Code,
functions and description for option D D - Do not Prorate to D - Disburse 100%. The
option is effective for loan funds for the options of D - Disburse 100% and N - Do not
Disburse.
Memo
This allows those funds, which have been disbursed in a term, and then for some reason
the disbursement is completely recouped, to allow that fund to continue to be a memo as
long as it meets the conditions for a memo. This can be set based upon an option on the
RPROPTS form.
Loan Authorization to Net Returned Amounts
Banner lets you create a return check record (sequence 2) on the RPALDSB form, prior to
having disbursed the loan proceeds in the sequence 1 record. This was not a problem, as
many times it was known prior to the first disbursement that some of the monies would
need to be returned to the lender due to some change in eligibility.
However, when determining the amount of the loan to display as an authorization record,
the disbursement process only checked the sequence 1 transaction to determine the
amount to authorize. When, in fact it should have netted the amounts together from all
sequence records that met the conditions to allow authorization.
Using Enrollment Disbursement Edits for Funds in
Memo Status
There have been several requests to allow Banner to only post Memo funds in the amount
that would be paid. Previously, there were no edits checking for enrollment on the memo
process, and this resulted in aid passing as a memo in excess of what the student was
January 2009
Financial Aid 8.3
User Guide
Processing
2-141
reasonably expected to receive. In some cases, the fund would not be disbursed at all,
since the student was not enrolled. In other cases, the student should have received a
reduced memo amount, or no memo amount at all, due to a reduced enrollment from what
was anticipated when the fund was first awarded. Banner now allows disbursement edits
for enrollment to be used for funds in Memo status.
Recognition of Pell Payment Cell to Disbursement
Process
The disbursement process had required the SAR EFC and System EFC to be exactly the
same number in order for payment to occur. There was a request to allow the disbursement
process to recognize the Payment Cell, so that when these numbers vary within the 100
point range, the disbursement process would treat the EFC numbers as equal values. Since
some schools may want to retain the prior method used by the Banner system, this feature
is available as an option.
Part-Time Proration
The disbursement process compares a student's enrollment load at the time of
disbursement to the enrollment load assumed at the time of packaging if the institutional
option is set to disburse using actual enrollment.
• If the code for the student's load at disbursement time is less than or equal to the
code for the expected load at packaging time, the disbursement process will
process the amount packaged for the term without any adjustments.
• If the code for the student's load at disbursement time is greater than the code for
the expected load at packaging time, the disbursement process performs one of the
following options.
N
No Disbursement (do not process any disbursement for the fund for the
term),
D
Disburse 100% (process the amount packaged for the term and do not
prorate the amount), or
P
Prorate (prorate the amount packaged for the term by multiplying the
packaged amount by a user specified percentage).
The choice to use one of the preceding options is determined by your institution on a fundby-fund basis.
The enrollment code in this comparison is the code that means full-time (1), three-quartertime (2), half-time (3), less than half-time (4), and no enrollment at all (5). The code for a
student enrolled on a half-time basis (3) is greater than a student enrolled on a full-time
basis (1). This is an important distinction since it is the opposite of when you compare the
number of credit hours for which a student is enrolled.
2-142
Financial Aid 8.3
User Guide
Processing
January 2009
For example, if you package a student under the assumption of full-time enrollment (code
1) and that student is actually full-time at the time of the disbursement (code 1),
disbursements will process the amount of the award that was packaged for the term
without any proration because the two enrollment codes are equal. If you package the
student under the assumption of half-time enrollment (code 3) and that student actually
enrolls as a full-time student (code 1), disbursements processes the amount of the award
that was packaged for the term without any proration because the disbursement code (1) is
less than the packaged code (3).
However, if you package the student as a full-time student (code 1) and that student
actually enrolls as a half-time student (code 3), the disbursements process uses one of the
three options as stipulated by your institution for the fund because the disbursement code
is greater than the packaged code. The three options are N - do not disburse anything (and
possibly back out any previous disbursements for the fund and term), D - disburse 100%
the amount of the award and allow a disbursement, or P - prorate the amount of the
disbursement by multiplying the scheduled amount for the disbursement by the proration
percentage entered on the Fund Management form (RFRMGMT) based on the student's
actual enrollment load.
The Disbursement Load Code greater than Package Load Code field on the Fund
Management form (RFRMGMT) collects your option if the disbursement load is greater
than the packaged load. The Packaging Load field on the Award form (RPAAWRD), the
Package Maintenance form (RPAAPMT), and the Financial Aid Record Maintenance
form (ROARMAN) identifies how a particular fund was packaged for a specific term. The
packaged load field for each term in the student's schedule initially defaults to the load you
select for the calculation of Pell Grants. The Packaging Options form (RPROPTS)
establishes this rule. The defaulted load is derived from either the student's expected
enrollment load as reported on the need analysis application or the default estimated
enrollment on the Packaging Options form.
You must remember to manually change the packaged load indicator for the appropriate
term and fund whenever you change the student's award based on a different enrollment
status. For example, assume that John was originally packaged as a full-time student
(packaged load = 1). At the time of the disbursement, John is enrolled as a half-time
student (disbursement load = 3). If the option set on RFRMGMT was set to N (Do not
disburse), John would not receive a disbursement from the fund since the disbursement
load is greater than the packaged load. Assume that you now access the Budget form and
recalculate John's budget as a half-time student, and later access the Award form to
repackage John with half-time awards based on a half-time need. If you fail to also change
the packaged load to a code 3, John will still not get the half-time awards just packaged
since the disbursement load is still greater than the packaged load. The half-time awards
will be paid when you change the packaged load to a code 3 since the disbursement load is
now equal to the packaged load.
January 2009
Financial Aid 8.3
User Guide
Processing
2-143
Memos Processed After Scheduled Disbursement
Date
If the calendar date is past the scheduled disbursement date and the student was not
eligible for a real payment to the account because the payment fails one or more of the
disbursement validation rules, the student can receive a memo. If you do not want to
process memos after the scheduled disbursement date, you can set the memo expiration
date to be the same as the scheduled disbursement date
VA Chapter 30
A provision of the 1998 reauthorization of Title IV financial aid is the treatment of VA
Chapter 30 and AmeriCorps Educational Benefits in determining subsidized student loan
eligibility. This provision requires that Chapter 30 and AmeriCorps benefits be excluded
as resources when determining eligibility for subsidized loans.
The maximum exclusion is equal to the amount of the subsidized loan, but the budget can
never be exceeded. Although these benefits must be excluded in the determination of a
subsidized loan, they must still be used as resources when determining other federal needbased aid, such as SEOG, FWS, and Perkins Loans. If they so choose, schools may award
other federal aid first utilizing 100% of the above benefits as resources.
The award validation for a Stafford Subsidized loan checks the amount entered in the
Subsidized Loan Exclusion Amount field and uses the amount to automatically calculate
the amount of Subsidized Stafford loan for the student. Enter the exact amount of VA
Chapter 30 or Americorps benefits in the Subsidized Loan Exclusion Amount field on
the Packaging Group tab of the RPAAWRD form at any time prior to awarding the
Stafford Subsidized loan to ensure the correct calculation.
Note
This provision does not affect unsubsidized or PLUS loans.
„
If other federal aid is awarded, the order of the awards will affect the amount that can be
considered as a subsidized loan.
Voiding Excess Payments for Students No Longer
Eligible
Banner has a fund disbursement option to void a financial aid payment previously paid to
a student who is now ineligible for the fund. The options on the Fund Management form
(RFRMGMT) are to:
• Back out the full amount of the payment.
• Disregard the fact that the student is now ineligible (do nothing).
2-144
Financial Aid 8.3
User Guide
Processing
January 2009
• Void the amount of the payment that has not yet been applied to a charge through
the application of payments process.
The last option is designed to cancel the amount of the award that is to be paid back
directly to the student without changing the amount that has already been used to pay the
student's bill.
The Payment Not Applied option can only be used when the disbursement process is run
in the batch mode. If disbursements are run online (from the Immediate Process form or
the Student Payment form), the process puts out a request for the student to be included in
the next run of the application of payments process. If the fund disbursement option is set
to B or D on RFRMGMT, the requested function works as usual when disbursements are
run online or in batch.
Disbursement Validation Reject Messages
You can run online disbursements from the Immediate Process form (ROAIMMP) in the
Financial Aid System, or from the Student Payment form (TSASPAY) in the Accounts
Receivable module of the Student System. Whenever you run the disbursement process,
the program creates a log file with information about the execution of the program. The
online disbursement process places messages in the log file (RPEDISB.log) for funds that
could not be disbursed or to see the reject messages online, using the Disbursement
Results form (ROIDISB).
Disbursement Reports Generated by Disbursement
Process
The Disbursement Report (RPBDISB) is created if you enter Y for the Print Report
parameter. No report is created when you enter N for the Print Report parameter. You can
sort this report either by student name or ID. The sort option is selected via the Disb
Report Sort parameter. You enter N for name sorting or I for ID sorting. That report prints
the term code in the heading of all pages and includes a special message in the comment
column to indicate if the amount disbursed was different from the amount awarded.
Other disbursement reports include the Student Award and Disbursement Report
(RPRAWDB) which prints the summary by fund of the accepted amount, memo’d
amount, authorized amount, and disbursement amount, as well as the Applicant
Disbursement Report (RPRADSB), which provides detailed information on applicant
disbursements.
January 2009
Financial Aid 8.3
User Guide
Processing
2-145
Executing the Disbursement Process by
an Oracle Pipe
The Disbursement Process (RPEDISB) can now be executed by an Oracle Pipe. The main
benefit of executing the Disbursement process via an Oracle Pipe is improved
performance of the process when it is executed online from Banner via the Applicant
Immediate Process form (ROAIMMP). Online Disbursement is normally launched
through the General Interface form (GUQINTF), which calls the Job Submission process
to start a platform-specific script which then loads and executes the RPEDISB program.
The Disbursement Pipe method improves the performance time of Disbursement when
executed online by using listener programs and accepting all requests for Disbursement
via an ORACLE “pipe.” This achieves performance time savings since Job Submission
does not need to load and execute the RPEDISB program with each disbursement request.
The Disbursement Pipe method is optional. That is, online execution of the Disbursement
Process from ROAIMMP may still be launched through the General Interface form
(GUQINTF), and requires no special setup. Everything will run in the traditional way,
except an additional output file (.clg) will be produced for each execution of RPEDISB.
The output will exist in the same file and directory structure, and will follow the same
naming conventions.
Note
The Disbursement Process with an Oracle Pipe is not designed to
function in a Windows NT or Linux environment.
„
Note
When the RPEDISB Disbursement Process is initiated from the Process
Submission Control form (GJAPCTL), the Job Submission process starts
a platform-specific script which loads and executes the desired program.
This is the method in which RPEDISB has always executed. The
„
Disbursement Pipe alternative does not change this methodology.
Note
A small change has been made in the way disbursement date updates
are made by the Disbursement Process. Prior to Release 7.4, the
Disbursement Date Update Process (RPRDDUP) executed each time the
RPEDISB Disbursement Process executed, both in online and batch
execution. If the Rescheduled Disbursement Date option was selected on
the Institution Financial Aid Options form (ROAINST), the process would
reschedule disbursement dates for Financial Aid awards based on the
student attending hours at the time of disbursement. If the option was not
selected, the RPRDDUP Process ended without performing any updates.
When executing through a pipe, the platform-specific script which loads
and executes both the RPRDDUP and RPEDISB program only executes
once when the pipe is started. Therefore, the RPRDDUP Process would
only run once. Depending on how frequently the pipe is started and
stopped, this could have an impact on how frequently the disbursement
date updates take place. To prevent any impact on the disbursement date
updates, the RPRDDUP Process has been removed from the platform-
2-146
Financial Aid 8.3
User Guide
Processing
January 2009
specific scripts which execute RPEDISB. Instead, a call to the
rokmisc.p_resched_fund_term_disburse packaged procedure is
directly made within the Disbursement Process for each student and fund
that is processed.
The only difference you see is that the rprddup.lis and rprddup.log files
are no longer created when the Disbursement Process is executed. The
logging information is visible on the GJIREVO form, and when
Disbursement is run from the ROAIMMP form, the detailed disbursement
reject messages are displayed on the GJIREVO form. The disbursement
date updates continue to take place at the appropriate time if you
„
request.
Disbursement Pipe Terminology/Methodology
This section explains some special terminology and methodology to assist you in
understanding and working with the Disbursement Pipe enhancement.
A database “pipe” is similar to a UNIX “pipe.” Different sessions connected to the same
Oracle instance can send and receive messages over a pipe. Pipes can have multiple
listeners (sessions that receive messages) and writers (sessions that send messages).
The writer packs a series of data items into a local message buffer. This buffer is sent over
the pipe into the message buffer of the listener, who then unpacks its buffer.
When the listener is started via the RNRPINI Process, it sleeps until a message is received
along the pipe to wake it up. The message (that is, a request for Disbursement) is
processed, and the listener either goes back to sleep or processes the next message.
Each listener receives messages from one and only one pipe. The pipe and process share
the same name. For example, the pipe and the Disbursement process are both named
RPEDISB.
You can start multiple listeners for each process, but only one pipe for the process can
exist. If two listeners (RPEDISB) are started for the Disbursement process, there will only
be one pipe named RPEDISB.
Currently, only the ROAIMMP Immediate Process form is a writer. When a request for
Disbursement is made, a message is sent over the RPEDISB pipe to the listener. The form
waits until a message is returned via a pipe named for the Oracle session from the listener
specifying the outcome of the Disbursement Process.
January 2009
Financial Aid 8.3
User Guide
Processing
2-147
Drivers
Disbursement Process Driver (RPEDISB)
This is a new process which can be executed as a one-time process, or as the listener, when
pipes are in use.
Subprograms
Disbursement Driver (RPEDISBS)
This is the old RPEDISB program which is now a subprogram to the new Disbursement
Process driver. All displays have been changed to call the RNELOGW subprogram which
writes the messages to a file.
Log Print Subprogram (RNELOGW)
This subprogram writes messages produced by the RPEDISBS program to a file. It was
originally delivered with the INAS Performance Enhancement in Banner Financial Aid
release 5.1. It is also used to write messages produced by the RPEPELLS and RNEINXXS
programs.
Disbursement Output to Database Subprogram (RPEDISBO)
If you are running the Disbursement process using pipes and have chosen to move the
output to the database, this subprogram moves the output from an actual operating system
files to the database GUBOUTP and GUROUTP tables, where you can review it with the
Saved Output Review form GJIREVO.
Running Disbursement the Traditional Way
You do not need to do any special setup to continue running Disbursements through the
General Interface form (GUQINTF).
Note
A log file (.clg) is produced for Disbursement. The output exists in the
same file structure and has the same naming convention as the existing
„
.lis and .log files.
Warning
If the GTVSDAX entry specifies that pipes are not being utilized, the forms
will initiate the GUQINTF process to perform the disbursement process
„
even if listeners have been started for the disbursement process.
2-148
Financial Aid 8.3
User Guide
Processing
January 2009
Running Disbursement Using Pipes
1. Indicate the number of listeners to start for RPEDISB.
Use the GTVSDAX form to indicate the number of listeners to run for Disbursement.
Code/Group
Direction
Internal Code
Enter RPEDISB.
Internal Group
Enter PIPE PROCESS. This entry must be exact.
External Code
Enter the number of listeners to start the process. For
example, if the external code is 2, 2 listeners will be
started for RPEDISB. If the external code is 0, no listeners
will be started for RPEDISB.
2. Start the listeners by running RNRPINI with a parameter of START.
Example: rnrpini user/password START.
(For UNIX) rnrpini.shl userid START - when prompted, enter the password.
Note
A single run of RNRPINI will start listeners for each of the RPEDISB,
RPEPELL, and RNEINxx (RNEIN01, RNEIN02, etc.) pipes specified on
„
GTVSDAX with an External Code > 0.
Note
The userid can be any user id that currently executes RPEPELL,
RNEINXX, or RPEDISB. The userid also needs select, insert, and update
permission to table GUBOUTP, and insert permission to table GUROUTP.
„
The userid does not need to be a DBA or system level login.
3. Process Disbursement online using the ROAIMMP form.
4. Stop the listeners by running RNRPINI with a parameter of STOP.
Example: rnrpini user/password STOP.
(For UNIX) rnrpini.shl userid STOP - when prompted, enter the password.
January 2009
Financial Aid 8.3
User Guide
Processing
2-149
Note
This stops all RPEDISB, RPEPELL, RNEINXX listeners.
„
Warning
The listeners remain running until they are stopped via the RNRPINI
program or until the Oracle instance is brought down. Each listener will
wait four days for a message, meaning that the output file can be huge. „
Note
If the pipe process GTVSDAX entry for Disbursement is set to a number
greater than zero, the forms will send messages via the pipes to the
listeners. If the listeners are not running, the Disbursement process will
not be performed via ROAIMMP. The form will wait 7.5 minutes for a reply
from the listener before supplying an error message. (This value is
global.max_wait_time and is the same value used to determine how
long an online process will wait for a response from job submission when
running processes online with the Immediate Process form (ROAIMMP).
„
It is a hard-coded value in form guainit.fmb, but you can modify it.)
Output Differences
Because the Disbursement process does not end until the listeners are stopped, the
resulting output is affected in the following ways:
• The output exists in the directory associated with the user who initiated the rnrpini
process, not the directory of the user who initiated the process through the Banner
form. For example, if User A runs the rnrpini process to initiate the listeners, all
output generated by the RPEDISB and Disbursement processes exist in the home
directory of User A. If User B initiates the process using the ROAIMMP form, the
generated output exists in the directory associated with User A.
• All the output generated by a listener is concatenated into one set of files. If
RPEDISB is run the traditional way with a one-up number of 111111, the following
files are created in the users directory:
rpedisb_111111.clg
rpedisb_111111.log
If RPEDISB is run again the traditional way with a one-up number of 111112, the
following files are created in the user’s directory:
rpedisb_111112.clg
rpedisb_111112.log
2-150
Financial Aid 8.3
User Guide
Processing
January 2009
If RPEDISB is run using pipes with a one-up number of 111113 and the first
listener processes the request, the following files are created in the directory of the
user who initiated the rnrpini process:
rpedisb_1.clg
rpedisb_1.log
If RPEDISB is run using pipes with a one-up number of 111114 and the first
listener processes the request, the output is concatenated to the existing data in the
following files.
rpedisb_1.clg
rpedisb_1.log
If RPEDISB is run using pipes with a one-up number of 111115 and the second
listener processes the request, the following files are created in the directory of the
user who initiated the rnrpini process:
rpedisb_2.clg
rpedisb_2.log
Note
If the Disbursement process fails, a message including the one-up
number is displayed on the ROAIMMP form message line.
„
RPEDISB/Disbursement Using Pipes/Saving Output to
Database
1. Indicate the number of listeners to start for RPEDISB.
Using the GTVSDAX form, indicate the number of listeners to run for RPEDISB.
Code/Group
Direction
Internal Code
Enter RPEDISB.
Internal Group
Enter PIPE PROCESS. This entry must be exact.
External Code
Enter the number of listeners to start the process. For
example, if the external code is 2, 2 listeners will be started
for RPEDISB. If the external code is 0, no listeners will be
started for RPEDISB.
2. Indicate if you want to move the output for RPEDISB to the database.
January 2009
Financial Aid 8.3
User Guide
Processing
2-151
Code/Group
Direction
Internal Code
Enter RPEDISB.
Internal Group
Enter FINAID LOG TO DB. This entry must be exact.
External Code
Y (Yes) or N (No).
3. Start the listeners by running RNRPINI with a parameter of START.
Example: rnrpini user/password START.
(For UNIX) rnrpini.shl userid START - when prompted, enter the password.
4. Process Disbursement online using the ROAIMMP form.
5. Stop the listeners by running RNRPINI with a parameter of STOP.
Example: rnrpini user/password STOP.
(For UNIX) rnrpini.shl userid STOP - when prompted, enter the password.
A log file (.clg) is produced for RPEDISB. The file and the file location are the same as
the .log files when running pipes. When the RPEDISB pipe is started with Finaid Log to
DB set to Y, a rpedisb_xxxxx.log file is created and will be viewable on form GJIREVO.
The xxxxx is the job number of the individual disbursement process executed by the
Immediate Process form (ROAIMMP). There will be an individual rpedisb_xxxxx.log
file created in the database for each execution of RPEDISB from the ROAIMMP form.
When Finaid Log to DB is Y, the rpedisb.log file created in the home directory of the user
starting the pipe will always be empty.
If the pipe is started with Finaid Log to DB set to N, the output will not be viewable on
the GJIREVO form. Instead, when the pipe is stopped, the rpedisb_1.log file (or the
RPEDISB_PIPES.LOG file for VMS) in the home directory of the user who started the pipe
will contain the concatenated output of all of the log files generated by RPEDISB while
the pipe was running.
Once the Disbursement Process is complete, the write to the database subroutine reads the
output and copies it to the database in the existing GUROUTP and GUBOUTP tables.
These database tables may contain many records. You may want to purge old entries from
these tables regularly.
Note
If the Disbursement Process has a fatal error and Finaid Log to DB is Y,
GJIREVO is queried and automatically displays the resulting log file. You
„
can also use this form to delete, save, or print existing output files.
2-152
Financial Aid 8.3
User Guide
Processing
January 2009
Default/Refund Processing
Levels of Default/Refund Administration
1. Award Packaging
When you execute the Award Validation process either through automatic packaging
(online or batch), or manual online packaging, Banner checks to ensure that when you
package Federal monies, or non-Federal funds which have a Federal Fund ID of GTIV
(General Title IV) associated with them, that the student is not in default on a Federal
Title IV Loan, or owes a refund on a Federal grant.
If a student is in default, or owes a refund from any of the default/refund sources
stored in Banner, the award validation process fails and any funds in which the default
criteria is invoked is not packaged.
2. Award Disbursement
When you execute the disbursement validation process in either online or batch
mode, Banner checks to ensure that when you disburse Federal funds, or non-Federal
funds which have a Federal Fund ID of GTIV (General Title IV) associated with
them, that the student is not in default on a Federal Title IV Loan, or owes a refund on
a Federal grant.
If a student is in default, or owes a refund from any of the default/refund sources
stored in Banner, the disbursement validation process fails and any funds in which the
default criteria is invoked is not packaged.
Sources of Default/Refund Information
1. Incoming Financial Aid Transcripts from a Student's Prior Institutions
Data Storage: You can enter incoming FAT data into Banner in the History and
Transcripts module through the Prior Institution Transcript form (RHAPTRN). Use
the Section C window of this form to maintain default/refund information as reported
by another institution. (Banner stores these indicators in the RHBTRNS Table.)
Data Maintenance: You can update this data on the RHAPTRN form.
System Use of Data: Banner uses default/refund information from this source in the
award validation and disbursement validation processes when Banner awards and
disburses Federal funds, or when it awards and disburses non-Federal funds in which
Federal rules apply (the Federal Fund ID equals GTIV).
2. Default as Reported by the Government
This data is reported to the institution through the ISIR. It is maintained in the Banner
database and is accessed using the Need Analysis form (RNARSxx), the Federal
January 2009
Financial Aid 8.3
User Guide
Processing
2-153
Match Indicators window, in the Title IV Match Indicator drop-down list and on the
Student Loan Data System form (RNASLxx)
Data Storage: Banner stores this data on the student's aid year need analysis record
(stored in RCRAPP1_TITLE_IV_DEFAULT).
Data Maintenance: You can view and maintain this information in the Federal Match
Indicators window of the Need Analysis form (RNARSxx). The allowable values for
this field are: 1 = Default /Not Eligible, 2 = Default,/Eligible, 3 = Cannot Determine, 4
= Not on Database., 5 = Dflt and rcvd overpayment/NE, 6 = Received overpayment/
NE, None.
System Use of Data: Both the award validation and disbursement validation
processes use this data when Banner awards and disburses Federal funds, or when it
awards and disburses non-Federal funds in which Federal rules apply (the Federal
Fund ID equals GTIV).
3. Federal Default/Refund from Own Institution
You can enter institutionally determined default/refund information to record students
who are in default or owe a refund from loans acquired at, or grants received at, your
own institution.
Data Storage: Institutions can load data and store this information with the Transcript
Information form (RHATINF). This information is stored in the RHBTINF table. You
can store and maintain the following data.
• Student owes a refund on a Pell or SEOG.
• Student is in default on a Perkins, NDSL, ICL.
• Student owes a refund on a SSIG.
• Student is in default on a GSL, FISL, SLS, PLUS (ALAS), or consolidation
loan.
Data Maintenance: You can maintain the preceding data elements. You can load this
information and maintain it either manually or electronically (i.e., if a third party
agency performs loan management activities) for Perkins, NDSL, or ICL. You can
also maintain this information if the student owes a refund on a Pell, SEOG, or SSIG
at the institution. If a student is in default on a GSL, FISL, SLS, or PLUS loan,
guarantee agencies/lenders generally provide this information for students in default
at their institution via hard copy printout, or electronically.
System Use of Data: Banner uses this institutional data in the following processes:
• Award Validation
• Disbursement Validation
• Outgoing Financial Aid Transcripts.
2-154
Financial Aid 8.3
User Guide
Processing
January 2009
Title IV Refund/Repayment Process
Please see the Title IV Handbook for information on this process.
Pell Grant Award and Disbursement
Processing
• Pell Grant calculation is not performed within the packaging process. You
determine in the Packaging Options section on the Packaging Options form
(RPROPTS) whether to package with the estimated enrollment reported by the
applicant or to package an estimated Pell with the default enrollment for all
applicants.
• You can run the Pell Grant Calculation Process (RPEPELL) either online or in a
batch. When you initially package Pell Grants for the year, run the batch Pell Grant
Calculation Process after you perform Batch INAS calculations and budget
assignments since the creation of the Pell Expected Family Contribution (EFC) and
Pell Budget in batch does not automatically trigger a Pell Grant Calculation.
• There are many fields in the database which impact a student's eligibility for a Pell
Grant. Therefore, when the information in one of those fields changes, Banner
performs the routine to calculate the amount and validate the student's eligibility
for a Pell Grant. When any of the following database fields change, Banner
performs RPEPELL, the Pell calculation and award validation routine.
Fields that trigger a Pell calculation when changed include:
January 2009
form
Field/Column Name
Need Analysis form
(RNARSxx)
Primary Calculation Sys EFC
Applicant Budget form
(RBAABUD)
Aid Period
Need Analysis Supplemental
form (RNASUxx)
Expected Enrollment Status for the Yr
Need Analysis form
(RNANAxx)
Prior Bachelor's Degree
Class Code
Citiz. Status
Applicant Pell Grant form
(ROAPELL)
SAR Certified Date
Financial Aid 8.3
User Guide
Processing
2-155
• You cannot add or accept a Pell award manually in the student's aid package. If you
need to delete the Pell award from the student's aid package, you must first set the
dollar amount to zero.
• During the disbursement process, the Pell Grant is recalculated based on the option
to disburse using an actual enrollment. If the award is calculated differently at that
time, the award amount is not updated. The new Pell award will only be used
during the disbursement process.
Note
If the Pell award is locked in the student's package, it is not recalculated
„
during disbursement.
• A Pell award will never be disbursed if the student is picked for verification, a SAR
EFC has not been received, and verification is not performed.
• Set the Equity Fund field to Y on the Funds Management form (RFRMGMT) for
the Pell fund code.
• If the Pell fund code is already included in the student's package and is recalculated
to a zero (0) amount, it will remain in the package with a 0 dollar amount; this
amount is also included in the student's award letter. If the Pell Grant is initially
calculated as a zero amount, it is not added to the student's package at all.
• Fund Management form (RFRMGMT) considerations include:
• If you check the Auto Accept indicator for an award, Banner automatically
changes an offered status for a fund to an accepted status.
• The Change Load During Term, Payment Percent for Three Quarter
Load, Payment Percent for Half Load, and Payment Percent for less
than Half Load Disbursement Option indicators do not apply to Pell Grant
processing.
• The Pell Grant Disbursement Process does use the If Ineligible Before Cut
off Date, If Ineligible After Cut off Date, If Selected for Verification but
is Not Complete, and Recoup When Award Reduced indicators.
• If you need to manually change a Pell grant amount for the year:
• Change the total award amount on the Fund Award by term section of the
Award form (RPAAWRD), on the Package Maintenance form (RPAAPMT),
or on the Financial Aid Record Maintenance (ROARMAN)
• Reschedule the award on the Fund Award by Term window of the
RPAAWRD, RPAAPMT, or the ROARMAN form (if necessary), and
2-156
Financial Aid 8.3
User Guide
Processing
January 2009
• Lock the fund in the Fund Award section of the RPAAWRD, RPAAPMT, or
the ROARMAN form.
Note
The award amount is never changed by the disbursement process.
„
Note
The Pell fund is the only fund in which the disbursement process can
disburse more than the scheduled amount.
„
• Applicant Pell Grant form (ROAPELL) considerations include:
• The Scheduled Award is based on the student's Pell budget and the full year,
full time Pell Grant Payment Schedule that the RPEPELL process uses.
• The Expected Disbursement prorates the amount in the Scheduled Award
field if the student is a part-time or part-year student based on the student's
enrollment load.
• The Amount Paid to Date field indicates the Pell payments that have
already been disbursed for the student.
State Grant Award Processing
In many states, the state grant program is handled by a state financial aid agency. This
agency processes state grant applications, calculates award amounts, and disburses the
funds directly to students or to schools for payment to students. Though the amount of the
grant is calculated by the state agency, financial aid offices may need to estimate the award
amount prior to the actual awarding by the state grant agency. Since this award can affect
the student's need for other aid, aid officers typically try to estimate the amount of the state
grant prior to its official calculation by the state grant agency.
Although it is disbursable, schools would not want to disburse an estimated award. They
need to make sure that only the official amount calculated by the state grant agency for the
term is disbursed.
These concerns can be handled by Banner in the following manner:
1. On the Fund Management form (RFRMGMT), set up the fund accepted award status
code to be something such as ESTD (Estimated). The Disburse indicator should be
set to System. The Memo Credit indicator can be set either way, and the Automatic
Acceptance indicator can be either checked or unchecked.
2. On the Financial Aid Selection Rules form (RORRULE), create a disbursement rule
that says:
RPRAWRD_AWST_CODE = CERT (Award Status Code = CERT)
January 2009
Financial Aid 8.3
User Guide
Processing
2-157
This will prevent the fund from being paid or authorized unless the award status code
is intentionally changed to CERT (a code meaning accepted on RTVAWST). The
normal processes of awarding or accepting the award would post different status codes
so the fund could be packaged and memoed, but not disbursed.
3. When the official award is known, then the actual amount is posted, replacing the
estimated award, and the status code is changed to CERT. The award is then eligible
for disbursement and only the actual/official amount will be paid.
If actual/official state grant award data is received on magnetic tape, a customized
process to post the tape data to the student's award record (RPRAWRD) and award by
term record (RPRATRM) can be developed. A customized process should also change
the award status code to identify the amount as the official amount and make it
disbursable.
Contracts and Exemptions
Contracts
Note
In order to interface third-party payments from Banner Student to Banner
Financial Aid, the Interface Third Party Cont indicator must be checked
on the Packaging Options form (RPROPTS) for those aid year you wish
„
to interface.
1. TSACONT – Contract Authorization form.
In order to interface contracts, the contract must first exist on SPRIDEN as a NonPerson record and on TSACONT for authorization. The Person Authorization
window of TSACONT provides for the authorization of contracts for specific
students.
2. RPRCONT – Third Party Contract Rules form.
Define the valid third party contracts which will be in effect for the specified terms.
Estimate a standard amount for each contract within the defined terms.
Note
On RPROPTS, if the Always Use Estimated field is checked, then the
estimated amount will always be used as a resource for students
authorized for the contract. If the Always Use Estimated field is not
checked, the estimated amount will be used until the actual amount is
available from Banner Accounts Receivable.
If the Assume Full Time field is checked, the full estimated amount will
always be used regardless of estimated enrollment. If Assume Full-Time
is set to N, then the percentage specified will be used to prorate the
estimated contract amount.
2-158
Financial Aid 8.3
User Guide
Processing
January 2009
RPIARPY – The Resource Payment form allows you to view Third Party
Contracts that have been applied to the student's account.
RPAARSC – The Exemptions and Contracts window of the Resource
form enables you to view a student's exemptions and third party contracts
„
for an aid year.
Exemptions
Note
In order to interface Exemptions from Banner Student to Banner Financial
Aid, the Interface Exemptions indicator must be checked on the
Packaging Options form (RPROPTS) for the Aid Year in which you want
„
to interface.
1. TSAEXPT – Exemption Authorization form.
In order to interface exemptions, the exemption must be set up on TSAEXPT in
Banner Student. The Person Authorization window of this form provides for the
authorization of exemptions to specific students.
2. RPREXPT – Exemption Rules form.
Define the valid exemption codes which will be interfaced for specified terms.
Estimate a standard amount for that exemption within the defined terms.
• On RPROPTS, if the Always Use Estimated field is checked, the estimated
amount of exemption will always be used as a resource for students
authorized for exemptions. If the Always Use Estimated field is not
checked, then the estimated amounts will be used as a resource until the
actual amount is available from Banner Accounts Receivable.
• The estimated amount can be prorated based on estimated enrollment. If the
Assume Full Time field is checked, the full estimated amount will be used.
If the Assume Full Time field is unchecked, then the percentage specified
will be used to prorate the estimated amount of the exemption.
• RPIARPY – The Resource Payment form allows you to view exemptions
that have been paid to the student's account.
• RPAARSC – The Exemptions and Contracts window of the Resource form
enables you to view a student's exemptions and third party contracts for an
aid year.
Excluding Contracts and Exemptions
The Higher Education Reconciliation Act of 2005, HERA, changed the way Coverdell
education savings accounts, prepaid tuition plans offered by a State, and qualified tuition
programs (known as 529 prepaid tuition plans and 529 savings plans) were treated in the
determination of a student's financial aid package.
January 2009
Financial Aid 8.3
User Guide
Processing
2-159
Previously, prepaid tuition plans were treated as an adjustment to the student's cost of
education, estimated financial aid, or as a resource. Many institutions used Third Party
Contract processing in the Accounts Receivable system of Banner to process students who
benefited from these plans. By using the Third Party Contract process, the benefits
received by the student were then reported as a resource for financial aid and properly
reduced the student's need.
The changes made by HERA require that prepaid tuition plans no longer be treated as
adjustments to the cost of education, estimated financial aid, or resources. All qualified
educational benefits or education savings accounts are now treated as assets of the owner
of the plan in the calculation of the student's EFC, unless the plan is owned by a dependent
student.
• Even if the beneficiary of the plan is someone other than the student (for example,
a sibling) it is counted as an asset belonging to the plan’s owner.
• The value (refund value for 529 prepaid tuition accounts) of all plans owned by the
parent of a dependent applicant must be reported as an asset of the parent.
• The value (refund value for 529 prepaid tuition accounts) of all plans owned by the
independent student applicant or spouse must be reported as an asset of the student.
• If the dependent student owns the plan, it is not included on the FAFSA nor is it
included as an adjustment to the COA or considered as a resource or estimated
financial assistance.
Specific resources identified as a qualified tuition program must be excluded from being
considered as resources when they have been processed using Third Party Contracts in the
Accounts Receivable system.
Previously, if you opted to interface Contracts and/or Exemptions on the Packaging
Options form (RPROPTS), when a student was authorized and received payment from a
Third Party Contract or Exemption, the amount paid on the student's account was included
in the determination of actual resources for financial aid.
The resource amount was interfaced into the Resource Maintenance form (RPAARSC)
and included in the calculation of need for financial aid in the following award forms:
Award Maintenance (RPAAWRD), Packaging Maintenance (RPAAPMT), and Financial
Aid Record Maintenance (ROARMAN) with the resource amount displaying in the
Resource field.
In response to the changes required by HERA, Banner Financial Aid allows you to
exclude specific contracts and/or exemptions from being counted as a Financial Aid
Resource. In addition, you can roll contracts and exemptions from one term to a new term.
In order to properly process contracts and exemptions from being excluded as resources,
you must:
• establish a contract record on the Third Party Contract Rules form (RPRCONT),
for a contract.
2-160
Financial Aid 8.3
User Guide
Processing
January 2009
• establish an exemption record on the Exemptions Rules form (RPREXPT), for an
exemption.
• select the new Exclude as Resource checkbox on RPRCONT or RPREXPT.
• set the estimated amount, or, if you choose not to use estimates, leave the amount
blank.
Note
If a Third Party Contract or Exemption is excluded as a resource, it will not
be visible on the Applicant Resource form (RPAARSC). However, all
Third Party Contracts and Exemptions which have been paid to a student,
including those that have been excluded, may be viewed on the Contracts
and Exemptions Payment Inquiry form (RPIARPY) which uses the
RPVARPY view. You can view Third Party Contracts or Exemptions paid
„
on the student's account.
The calculation of estimated resources for both contracts and exemptions uses the
maximum amount established on the student authorization for the contract and/or
exemption if it exists in Accounts Receivable (TSACONT/TSAEXPT). If no maximum
amount has been established, the calculation for estimated resources will continue to use
the estimated amount defined on RPRCONT for contracts and RPREXPT for exemptions.
Loan Processing
Manual Loans
Disbursing Manual Loan Checks through Banner
Occasionally a student's eligibility for a Subsidized Stafford or Unsubsidized Loan
changes after the loan has been certified but before the check is disbursed. If the student is
no longer eligible for any of the loan, you simply return the entire check to the lender. If
the student remains eligible for an amount that is less than the amount of the check, then
the excess can be returned to the lender and only the proper amount disbursed to the
student.
1. On the Loan Disbursement form (RPALDSB), enter:
the full amount of the check into Check/Net Amount.
the amount the student does not qualify into Returned Amount
2. After the check has been endorsed by the student, set the Feed indicator to Y
3. Run the disbursement process.
January 2009
Financial Aid 8.3
User Guide
Processing
2-161
The process will disburse the difference between the full check amount and the returned
check amount to the student's account.
For example, if a full loan check is for $500, but the student is only eligible for $400, enter
$500 into Check/Net Amount and $100 into Returned Amount. Only the difference of
$400 will be paid.
In order to recover a partial or full loan amount after the full amount of the check has been
paid to the student account, use the Returned Amount field and change the feed indicator
from F to Y (the feed indicator previously read F to indicate that the loan check had
already been fed to the student's account). When the disbursement process is run again for
the student, the process will put out an adjusting entry on the student's account for the
amount returned.
Once a loan check has been fed to a student's account, it will not be backed out
automatically if the student becomes ineligible for the fund. Other non-loan funds may be
“backed out” automatically as per rules on the Fund Management form (RFRMGMT).
The only way to cancel a payment for a loan check that has been fed to the student's
account is to use this Check Returned feature.
Institutional Financial Aid Options form (ROAINST)
Set the Loan Process Type drop-down box on the Institution Financial Aid Options II
window of this form to Electronic for Electronic only or Both if processing Electronic and
Direct loans. This box is accessed during online and batch processing.
Note
If your institution has a EL School code which is different than the Pell ID
and your school is not processing for multiple campuses, enter the
Electronic School Code and Electronic Branch ID in the Institution
Financial Aid Options II window. Loan applications will then be created
correctly with these values.
Conversely, if your institution will be processing Electronic loans for
multiple campuses, establish the Electronic School Code and Branch
ID for each campus on the Campus/EDE Defaults window. The loan
application records will then be created with the correct Electronic
School Code and Branch ID for the Campus code on the student’s
General Student record. Loan applications can then be extracted based
„
on individual Electronic School Codes and/or Electronic Branch IDs.
Aid Period/Term Rules form (RORTPRD)
Associate terms with aid periods on this form.
2-162
Financial Aid 8.3
User Guide
Processing
January 2009
Default Award & Disbursement Schedule Rules form
(RFRDEFA)
Establish award distributions for each aid period. Memo expiration dates must be
established here for loan memos to work correctly. Dates entered here are used for loan
periods associated with an aid period.
Detail Code Control form (TSADETC)
Ask Student Accounts personnel to establish loan fund detail codes as well as detail codes
to use in the refund process on this form.
Fund Base Data form (RFRBASE)
Establish loan fund(s) and associate them with Federal loan identifiers.
Separate loan funds MAY be established if the school knows which individual loans will
be received via EFT versus paper checks, or if EFT and paper check funds will have a
different general ledger accounting structure. If a different type of fund is received, the
original loan application must be cancelled, and a new one must be generated for the other
fund.
Banner loan applications can be created and sent for all funds using electronic processes.
Codes for subsidized funds should precede unsubsidized funds in the RFRBASE listing,
since batch processes select funds in alphabetical order.
Funds Management form (RFRMGMT)
1. Create a separate RFRMGMT form for each loan fund.
2. Allocate dollars to the fund on the first window.
3. Complete the following Packaging Options fields applicable to Electronic loans in the
Aid Year Specific Data - Packaging Options window:
• Enter the maximum loan that could be made to any student during the
combined terms of the aid year.
• Check Replace EFC for unsubsidized and PLUS Loans.
• Check Reduce Need for subsidized loans.
• Check Need Analysis Indicator. The Need Analysis indicator may be left
unchecked for PLUS Loans.
• Check Loan Process for all Electronic loans.
• Complete Loan Fee Percentage.
January 2009
Financial Aid 8.3
User Guide
Processing
2-163
• The Direct Loan Indicator must indicate ‘None’ for electronic loans to
process.
• Memo Credit block (optional). (1) To memo gross: RFRMGMT memo =
Offered, RTVLNST code = Approved, RPRLOPT Memo Actual Amount =
blank; (2)To memo net: RFRMGMT memo = Accept, RTVLNST code =
Approved, RPRLOPT Memo Actual Amount = checked.
• Set Disburse block to None if using the Loan Process as loans are disbursed
from RPALDSB.
4. Complete disbursement option fields applicable to Electronic loans in the Aid Year
Specific Data - Disbursement Options window.
For If Disbursement Loan Code greater than Package Load Code, choose
Disburse 100% (disburses total amount available for the current disbursement) or No
Disbursement (no disbursement if the disbursement load code is greater than
packaging load code indicating that student has dropped hours). Proration is not
applicable to Electronic loan disbursement.
5. Set Use Disbursement Enrollment Edits for Memo field option. The checked field
works in conjunction with the Disbursement Load Code field option to create/not
create memos under the same condition as the Disbursement Load option. If
unchecked, this field results in memos at gross prior to creation of the loan
application and at net after the application is created.
6. Other required fields must be filled to exit the form, including those not used in loan
processing.
7. Optionally, enter any tracking documents or messages applicable to each fund.
Packaging Options form (RPROPTS)
The expected annual enrollment on RNANAxx is used for loan awarding.
Check the Additional Unsubsidized box to control awarding of unsubsidized amounts
above the grade-level maximum to independent students.
Note
The override field for dependent unsubsidized professional judgment is
„
on the three award forms: RPAAWRD, RPAAPMT, and ROARMAN.
2-164
Financial Aid 8.3
User Guide
Processing
January 2009
Class Code Translation Rules form (RPRCLSS)
Equate Student System Class codes with Financial Aid class Codes as defined on
RNANAxx for Banner Year in College. A default Student Level code with a null Student
Class code should be established with a Financial Aid Class Code.
Note
Electronic certification and disbursement processes use the Student
System’s class information.
„
Certification Initials Validation form (RTVCINT)
This is an optional form used also in short-term credit processing.
Enter the initials of staff members authorized to certify loans on this form. Entering and
saving initials in the Loan Certification section of a loan application locks the form and
prevents additional editing.
Loan Status Validation form (RTVLNST)
Enter status codes for loans here. An Initial status defaults when a loan application is
created. An Approved status may be posted during the response file upload. An Inactive
code prevents disbursement memos. A Hold code stops processing until resolved and
replaced with an Active code. Institutions may wish to create loans in an Inactive status
until an approval is received from the processor.
Lender Base Data Rules form (RPRLNDR)
This form is used to create a lender listing and to associate a Lender ID with a Guarantor
ID. Use official lender/guarantor identification codes.
Loan Period Base Data form (RPRLPRD)
Year-specific loan period names help you to distinguish loans on the RPALDSB
disbursement form. Memo expiration dates used for term-based loans should match those
used for the same term on RFRDEFA.
1. Create loan periods associated with regular aid periods in Loan Period.
2. Enter disbursement dates in Start Date and End Date.
For Loan Periods that Match Aid Periods:
January 2009
Financial Aid 8.3
User Guide
Processing
2-165
• Enter the Aid Period to be used for certification.
Note
A term schedule for each aid period must exist on RFRDEFA. Loan
applications will create automatically based on the student’s aid period.
The loan period may be changed to a term-based period once the
„
application is generated.
For Loan Periods that Do Not Match Aid Periods:
• Create additional loan periods associated with a term to be used for students in
multi-term aid periods who want one-term loans (for example, Fall/Spring aid
period; wants loan for Fall only).
• Enter disbursement dates. Costs for term-based loans must be established manually.
Note
If Summer is counted in two different aid years, you must have two
Summer terms with one attached to each aid year to process Summer„
only loans.
3. Create a disbursement schedule for each loan period. Up to four disbursements may
be entered per loan period; the total must equal 100 percent. Date(s) entered here will
be transmitted to the lender as the dates that funds are released to the school.
Note
The Number of Days for Memos field is used in the manual loan
process if the application is created prior to the award to indicate the
length of time from the scheduled disbursement date that memos should
„
expire.
Loan Options form (RPRLOPT)
Values established on this form are used as defaults when applications are created.
1. Establish a null value for both Create Application options by checking each box,
saving, unchecking each box and saving. These options are used only for paper
applications.
2. Enter an Initial Loan Status.
3. Enter a Default Return ID (for refund checks), Default Lender ID (to receive loan
applications), and Default Guarantor ID (associated with Lender IDs) to be used as
defaults for new borrowers. For the guarantee only and guarantee/print options, a
lender/guarantor must be specified. When the print/guarantee is used, these fields
may be left blank or may be populated with the default Lender(s) ID information
from the school’s lender list. Some schools rotate preferred Lender IDs here.
2-166
Financial Aid 8.3
User Guide
Processing
January 2009
For continuing students, Banner defaults the most recent lender/guarantor information
to the application. These fields may be left blank if the school has multiple lenders and
wishes to enter them manually after applications are created online or in batch.
Guarantors who require students to continue with the same lender may change the
Banner-supplied data, or new students may change it. The Lender ID will be loaded
during the response file update process.
4. Enter Y in the Satisfy Loan Application Requirement field and the specific
requirement and status codes if you wish to use this option.
5. Enter Y to memo the net loan amount (calculated as Disbursement Amount on
RPALDSB disbursement form) when the application is created. Packaged amount
will be memoed if box is set to N.
6. Enter Y to create loan authorizations for this year. For loans, authorization indicates
that a check or EFT funds have been received, but the check has not been endorsed
and /or the disbursement date has not arrived.
7. Check the Disbursement Amount greater than Loan Amount checkbox if you
wish to prevent disbursement if a loan amount is greater than the award amount. the
process uses net of all term disbursements up to and including term in which
disbursement is being made.
8. Check the Request Amount Required for Certification checkbox, if necessary. This
prevents entry of certification initials on the RPALAPP form unless a requested
amount is present. Not applicable for use with RPAELAP.
9. Refund detail codes may be established for automatic generation of return checks to
lenders through Banner Accounts Receivable as described below.
10. Complete the Student Charge or Payment code. A negative payment detail code
should be used to net down the payment to the student. A negative charge detail code
appears like a refund to the student.
11. Enter a Return Payment code to be used by RPEDISB that represents a payment to
the return lender’s account.
12. Enter the Return Refund code that represents the charge to the Refund account for
the return to the lender. This code must be set up as a Charge, and the Refund code
must be set to Y on TSADETC.
January 2009
Financial Aid 8.3
User Guide
Processing
2-167
Lender/Disbursing Agents Rules form (RPRLNDA)
This optional form links a lender code with service provider code to expedite transmission
of hold/release records directly to the service provider rather than to the lender or
guarantor.
1. Enter the Lender ID.
2. Enter the Guarantor ID (optional)
3. Enter the Disbursing Agent ID.
First-Year, First-Time Borrower Loan Rule
Overview
Stafford loan processing was changed in the 7.2 release in order to implement a Federal
requirement for a 30-day delay in disbursement for certain loans. This requirement is
called the first-year, first-time borrower loan rule. It specifies that the disbursement of
Stafford loan proceeds to a student in their first year of an undergraduate program of study
who has not previously received a Federal Subsidized, Unsubsidized, or SLS loan must be
delayed 30 calendar days from the date the student begins his/her program of study.
Previously, Banner used student reported data from the FAFSA, the Campus
Undergraduate Level Code Rules form (RPRCLVL), and the existence of academic
history to determine if the 30-day delay should be used when scheduling the
disbursements for Federal Stafford loans.
As an example, if the student is enrolled in the first semester (running from September 1,
2005 to December 14, 2005) of a program that is made up of three 5-week modules, but
the student is not enrolled in the first two modules of that semester, the school has to wait
to disburse the funds until 30 days after classes from the third module begin.
To implement this rule, Banner must determine whether the student is in a first year
undergraduate program of study and whether the student has previously been disbursed
Federal Stafford or SLS loan funds. In order to determine if a student has previously been
disbursed Federal Stafford or SLS loan proceeds, NSLDS records from the ISIR record
and Transfer Student Monitoring Alert files are queried. A check for Federal Stafford
loans paid in Banner is also performed.
To determine if a student is in the first year of an undergraduate program, the financial aid
class translation rules are used to identify first year students using the financial aid class
for Banner year in college of 1 (first-time freshman, no prior college) or 2 (freshman, prior
college).
An option to turn off the function to determine a first-year, first-time borrower is provided
at the campus level (on the Campus/EDE Defaults window of the ROAINST form) and as
2-168
Financial Aid 8.3
User Guide
Processing
January 2009
a default for the institution (on the Loan Options window of the ROAINST form). After
the install of release 7.2, the rule to apply the first-year, first-time borrower check is used.
If your institution does not want to apply the first-year, first-time borrower rule, you must
uncheck the appropriate campus and institution Apply First-Year, First-Time Borrower
Rule indicators on the Institution Financial Aid Options form (ROAINST).
Note
First-year, first-time borrower rule processing is not supported for manual
loans. When processing a loan manually, you must determine if the firstyear, first-time borrower rule applies and set the disbursement date
„
accordingly.
First-Year, First-Time Borrower Function
With the 7.2 Banner Financial Aid release, functionality to determine first-year, first-time
borrowers using FAFSA reported data and the Campus Undergraduate Level Code Rules
form (RPRCLVL) is no longer used.
The F_FIRST_TIME_BORROWER function supports the determination of a first-year, firstyear borrower for Stafford loans. The Electronic Loan Application form (RPAELAP) and
the Direct Loan Origination form (RPALORG) use this function to determine if the 30-day
delay is applied when the loan period is changed.
The Electronic Loan Application Creation Process (RPRELAP) and the Direct Loan
Record Creation Process use the F_FIRST_TIME_BORROWER function to determine if the
student is a first-year, first-time borrower and the 30-day delay is applied.
Determination of a First-Year, First-Time Borrower
The F_FIRST_TIME_BORROWER function determines if the Apply First-Year, First-Time
Borrower Rule indicator is checked (Yes) for the campus on the most recent student
record where the effective term is less than or equal to the first term of the loan period
being processed. If no corresponding campus has been defined or there is no General
Student or Admissions record, the institution default for Apply First-Year, First-Time
Borrower Rule is used.
If the option to turn off the function has not been indicated, the following steps to
determine a first-year, first-time borrower are used:
1. Determine if the student has been disbursed a prior Stafford, SLS, Direct Subsidized,
or Direct Unsubsidized loan using:
Current NSLDS record
Banner award record
If the student has received a Stafford, SLS, Direct Subsidized, or Direct Unsubsidized
loan, no 30-day delay will be processed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-169
If the student has not received a prior Stafford, SLS, Direct Subsidized, or Direct
Unsubsidized loan, go to the next step.
2. Determine if the student is an undergraduate first-year student using the class
calculation and class translation rules.
If the student's financial aid class is calculated as 1 (1st time freshman, no prior
college) or 2 (freshman, prior college), the 30-day delay will be applied.
If no student record exists, the 30-day delay will be applied.
Crosswalk Validation form (GTVSDAX)
Electronic loan processing requires that foreign country addresses contain the State code
of FC and zip code of 99999. To correctly identify which addresses are foreign when
addresses are not created with a country code of US, you must establish the crosswalk
validation of GTVSDAX. Without GTVSDAX being populated, the null nation code on
RPAELAP will be converted to FC for foreign country and transmitted in the datafile.
GTVSDAX should be populated with 157 for the US Nation code or the appropriate value
as established by your institution.
Application Creation, Extract, and Response Processing
The annual Spring Banner Financial Aid release contains updates for federal loan
processing. It is best to process loans for the coming year after this release is installed.
This section discusses each process followed by a section showing fields that update on
RPAELAP as a result of each process.
(A) Creating and Certifying Electronic Loan Applications)
forms involved in creating and certifying Electronic loan applications include:
Applicant Requirements form (RRAAREQ)
This form lists tracking requirements that could prevent disbursement packaging if not
satisfied.
2-170
Financial Aid 8.3
User Guide
Processing
January 2009
Award forms (RPAAWRD)/(RPAAPMT)/(ROARMAN)
This form is used to award loan(s) to a student. Loans must be in an accepted state to
create an electronic application. Banner awards based on expected enrollment level from
RNANAxx.
Note
Parameters for the online RPRELAP process must be created for each
„
user authorized to create loan application records.
Electronic Loan Application Process (RPRELAP)
Electronic loan applications must be created online (through the Create App button on
RPAAWRD, RPAAPMT, ROARMAN) or in batch mode.
Note
Parameters for the online RPRELAP process must be created for each
„
user authorized to create loan application records.
1. Access the GJAPDFT form and enter parameters for the process.
Warning
Leave the Parameter Set field in the Key block blank. The online
process may not be run with a parameter set.
„
2. Once the parameters have been established for one user, use the Copy function on
GJAPDFT to establish the default parameters for all users who will be using the
online process.
3. The following parameters for batch RPRELAP should be established and saved by
each user as a parameter set:
• Aid Year Code.
• Fund Code. Applications for multiple funds may be created simultaneously.
Use the Insert Record function to enter additional 02 Fund Code parameter
lines.
• Default Process Type. This parameter varies by school (for example, GP Guar/Print; GO - Guarantee only, and so on). If a school has paper
applications on hand for some students, then award the loan, generate the
application, change this option to guarantee only, and mail the certified paper
form to the lender.
• Application Code, Report Selection Query ID, and Creator ID of Selection
ID. These parameters may be used in batch mode.
• Process Indicator. Enter Batch. The online process will ignore this
parameter.
January 2009
Financial Aid 8.3
User Guide
Processing
2-171
• Permanent Address Type Default and Local Address Type Default. These are
Student-system addresses. Use the address hierarchy as in letters (for
example, 1PR, 2MA, and so on).
• Loan Status Default. Enter a default initial loan status.
• EL (Electronic) Application Status Default. Enter Ready to send or N if
applications must be reviewed prior to transmission to the lender.
Note
PLUS Loans are not ready to send until parent data has been entered on
the resulting RPAELAP form. This status must be changed from R to N to
„
use the Delete/Replace function.
• EFT (Electronic Funds Transfer) Authorization Default. Enter Y if the
majority of students choose this option. Can be changed for individual
students before records are sent.
• Lock Indicator Default. This parameter can be set if you wish to stop the
Delete/Replace function so that manually entered data is not lost. If award
amounts are changed on the award form, Banner will delete/replace amounts
on an application unless it is locked or has a status of Sent. The application is
recreated during this process and previous data is removed.
• References Default. Enter N for the Reference parameter if your lender/
guarantor will mail notes to the student. Enter Y if you have collected the
references.
• Deferment Request Default and Capitalize Interest Default. Enter Y if the
majority of your students use these options. May be changed individually on
RPAELAP form.
• Default Lender ID, Default Guarantor ID, Default Return ID. Defaults may
be specified here.
• Default Loan Period. Leave this blank to use the loan period associated with
the student’s aid period. This parameter is only valid for Batch processing.
• Default PN (Promissory Note) Delivery Code. Specify an Email, Paper, or
Web PN Delivery code as guarantor method of promissory note delivery to
the student.
• Default Federal Application form Code. Enter B Old PN, MPN (all
applications processed as combined, request amount set to 99999),or Plus.
• Default Serial Loan Code. Enter New note for each loan or Serial MPN.
PLUS loans will be created with a value of None.
• Default Hold/Release Status. Initial status may be HR (Hold Request) or RR
(Release Request). Status may be updated individually on RPAELAP.
• Source of Lender ID. Use NSLDS or prior Banner as source for student’s
lender.
2-172
Financial Aid 8.3
User Guide
Processing
January 2009
• User ID. The ID of the person using the sub-population rule.
Note
Regarding the Delete/Replace function, applications that are not locked
or sent may be deleted or replaced as awards are adjusted or canceled.
Change the Application Status to N (Not Ready to Send), adjust the
award, and recreate the application by clicking the Create Application
button.
New applications will be created for additional award amount(s) after an
application is sent.
Parent Loan demographic data from a prior application is transferred to
the new application during the replace function. The application number is
updated with each replacement and is not to be used as a counter. The
batch RPRELAP process will delete applications where awards have
„
been cancelled.
RPAELAP Fields Updated by RPRELAP Process
RPAELAP displays the latest loan application first. Arrow down to see additional
applications. Windows updated on this form include:
Application Window
• Loan ID. RPRELAP generates a temporary Loan ID for each subsidized,
unsubsidized, and PLUS loan in the batch being run. It has a B (for Banner) in the
Loan Type field within the number and S, U, or P following the B to indicate the
type of loan.
The S is replaced with O in the combined subsidized Loan ID during the
RPRELAX process.
• Fee Percent.
• Lock (if selected). This locks the application from getting deleted and replaced
when an award is changed or canceled.
• Fund Code/Name.
• Process Type.
• Aid Year.
• Lender/Return/Guarantor ID. Official federal Lender ID is used and is left
justified. Do not fill in remaining spaces.
• Record Type. A indicates a new application.
• Loan Period Start/End Dates. This can be changed manually.
• Loan Status.
January 2009
Financial Aid 8.3
User Guide
Processing
2-173
• System Indicator. It is set to B for online and batch processes.
• Recommended and Requested Amounts. These come from the RPAAWRD,
RPAAPMT, and ROARMAN award amounts. The recommended amount stays the
same, but the requested amount will update.
• Maximum Eligibility Amount. This is calculated from certification data (that is,
Cost - EFC = Estimated Aid) but not sent to the guarantor.
• Expected Amount. This is the amount the student is eligible to receive based on
amount awarded and student’s grade level.
Promissory Note/Miscellaneous Information Window
• Promissory Note Delivery. Choices are: Email, Paper, Web
• Federal Application form. Choices are: B Old PN, Master PN, PLUS note.
• Serial Loan. Choices are: New MPN, Serial Note.
• Electronic Funds Transfer Authorization.
• References.
• Deferment Request.
• Capitalize Interest.
Certification Data Window
Note
The RPQLELG form may be accessed from this window to check
certification data.
„
• Budget.
• Estimated Financial Aid. This includes all aid except this fund.
• Expected Family Contribution. This is derived from the RNARSxx form.
Budget, Estimated Aid, and EFC for term-based loans must be entered manually.
• Maximum Eligible Amount.
• Adjusted Gross Income.
• Expected Amount. This is the amount the student will receive. Use the lesser of
maximum eligibility from delivered rules table, calculated maximum amount, or
requested amount.
• Grade Level. Uses Student System class level (translated on RPRCLSS).
• Expected Grad Date. Accesses Student system data first. If there is no data,
Banner adds years to FAFSA class level and uses hardcoded date of 5/31; for
example, 2000-01 FAFSA class 1 + 3 years = 5/31/2004 graduation date.
• Enrollment Status. From the annual expected enrollment on RNANAxx.
2-174
Financial Aid 8.3
User Guide
Processing
January 2009
• Dependency status. From the RCRAPP record.
Student Data Window
• Social Security Number.
• Address.
• Local Address.
• Date of Birth.
• Citizenship.
• Driver’s License Number.
• Loan Default.
• Dependency
Parent Data Window
Enter parent data in this window. Banner will carry forward parent data to revised
applications.
Term Schedule Window
Data defaults into this window. The Memo Amount displayed is for the term.
Note
The optional Certified Hours field may be populated manually with the
number of hours used as a basis for loan certification. Hours entered here
„
will appear on the RPALDSB form.
Disbursement Schedule Window
The net amount will display if Memo Actual was chosen. Adjustments will result in
additional disbursement transactions. Initial HR (Hold Request) or RR Release Request)
status in the Hold/Release Status field.
Loan Parent Inquiry form (RPILPAR)
Use this form to view parent names associated with a student. This form may be accessed
from the ROASMRY or RPALDSB forms.
Extracting Loan Applications from Banner
The following forms are used for extracting loan applications:
January 2009
Financial Aid 8.3
User Guide
Processing
2-175
Electronic Loan Application Extract Process
(RPRELAX)
1. Check loan applications prior to transmission. Applications will extract if:
• The loan is not canceled.
• The loan status is Ready to Send.
• The Batch ID is null.
• The Loan ID is not null.
• The student is in the population selection (if used).
2. Select the printer on the GJAPCTL form. Output can be viewed on GJIREVO when
saved to a database. Funds may be entered individually or as a multiple entries
3. Establish parameters on GJAPCTL form as below:
• Aid Year Code.
• Fund Code. Funds may be entered individually or as multiple entries.
• Enter the File Identifier parameter as Production or Test.
• Spell out the school name in the School Name parameter.
• Recipient Name and Recipient ID. These identifiers are placed in the Header
record of the file to direct the electronic file to the proper guarantee/lending
agency for processing. Check with the provider of your vender software to
see if it will insert this information after the FTP process.
• Select Media type. It usually is PC.
• Select population selection identifiers.
• Combine Sub/Unsub Stafford. All loans with Application Code of M process
as combined loans.
• Version Number. Extract changes supported with Version 4.
• EL (Electronic) School Code. Enter the code for the loan applications to be
extracted if you are multi-campus and want each campus extracted correctly.
• EL (Electronic) Branch ID. Enter the corresponding Branch ID for the EL
School Code to be extracted.
Review Output Window
This window displays:
• RPRELAX.log, when the process is completed.
2-176
Financial Aid 8.3
User Guide
Processing
January 2009
• RPRELAX.lis includes student ID, name, and loan fund(s) extracted.
Parameters used and a summary of total applications are included. Report
shows loans selected for transmission as well as missing data.
Note
ELAPxxIN_xxxxx.DAT data file is produced to be transmitted to the
guarantor/lender.
„
Batch Control form (RPIBATC)
This form is used to view a record of Electronic loan batches created.
RPAELAP Fields Updated by the RPRELAX Process
Application Window
• Loan Status changes to Sent.
• Version Number checkbox.
• Submission Date.
• Cross Reference Loan ID. The subsidized Loan ID is used on combined loan
applications. The cross-reference loan ID links the unsubsidized loan to the
subsidized loan and is the Loan ID assigned to the subsidized loan. The cross
reference ID of the subsidized loan will be updated with the Loan ID of the
unsubsidized loan. The Loan ID is given a unique one-up number when RPRELAX
extracts the loan application.
Electronic Loan Response Upload Process (RPRELRU)
1. Run the RPRELRU process after setting the single parameter to the desired Approved
loan status.
2. Review output in the Review Output window:
• RPRELRU.log will show process completion.
• RPRELRU.lis shows all records loaded with adjustment indicators if the
amount certified or requested was changed along with error messages. Error
code descriptors are found in the Electronic Loan Manual.
Note
Uploading loan response files is not required for disbursement. Schools
that wish to memo loans based on an Active status may wish to upload
response files to identify approved loans and response files containing
records with special status notifications.
Responses are received at the individual loan level (subsidized and
January 2009
Financial Aid 8.3
User Guide
Processing
2-177
unsubsidized) for combined loans.
More than one response record may be received for the same loan
application (one per batch). The Application Status field is updated.
To upload data to Banner, the files received electronically must be moved
to the same directory used for all other data uploads (DATAHOME).
The incoming file name expected by the RPRELRU process is
elupdtop.dat. Once processed by Banner, the first nine characters of the
Header records are changed to Processed to prevent accidentally
„
reloading the same data again.
RPAELAP Fields Updated by the RPRELRU Process
Application Window
• Loan Status. This field updates with the loan status defined in the parameter of
RPRELRU.
• Application Status. This field shows latest guarantor statuses including:
• Submitted
• Guaranteed
• PN received/approved
• Pending
• Denied/Rejected
• Modified
• Cert. Request.
• Terminated
• Not Ready
• Ready
• Sent
• Application Accepted.
Note
Certification requests and modification records are not loaded into
Banner. These records will appear in the output with a message of the
„
type of record received.
• Application Phase Code.
• Approved Amount.
• Approval Date. Approval amount and date can be updated manually if school does
not load response files.
2-178
Financial Aid 8.3
User Guide
Processing
January 2009
• Lender ID. If no non-person record exists for lender, error message appears in .lis
file.
Promissory Note/Miscellaneous Information Window
• Master Promissory Note Confirmation Code. This indicates the MPN existed at
the time of certification.
• Borrower Confirmation Code. This indicates borrower confirmation of loan was
received.
Disbursement Schedule window
• Hold/Release Status updates to HA (Hold Accepted), RA (Release Accepted).
Parent Data Window
• Parent data will be returned including Social Security Number, name, and date of
birth (check Electronic Loan Manual for additional information).
Note
The RPRELRU process does NOT update the RPAAWRD, RPAAPMT,
and ROARMAN award amounts or change the requested amount or
„
certification record.
Disbursement/Adjustment
Banner CommonLine Electronic processing includes EFT, Master Check, and individual
check record upload capability. An EFT file may contain any or all of these types of
disbursements. Banner Hold/Release may be used to update the initial Hold/Release status
to permit or prevent the receipt of scheduled loan disbursements depending upon the
option of the school.
Disbursement Process (RPEDISB)
1. Run the disbursement process online or in batch to generate memos, authorizations,
and disbursement error messages if the disbursement edit optional parameter is being
used for the RPRHDRL process.
For Revised Disbursement amount processing:
1. Enter changes to disbursement amounts on RPAELAP as net amounts. Banner will
convert it to the gross amount if the revision is included with the RPRHDRL record.
Loan memos will use Revised Disbursement amounts if present in RPAELAP
Disbursement window.
2. Review disbursement error messages on the disbursement report or on ROIDISB.
January 2009
Financial Aid 8.3
User Guide
Processing
2-179
Hold/Release Process (RPRHDRL)
This process captures changes to the initial Hold/Release status and creates a data file for
transmission to the service provider or lender.
1. Run the process after receiving the response file. The Guarantor sequence number is
needed.
2. Batch update of status by fund/term updates all available undisbursed records or use
Disbursement Edit.
Note
The Disbursement edit (which is optional) requires at least one
disbursement reject in the Disbursement Results Table to hold a loan, and
that no rejects be found to release a loan. Revised Disbursement dates
and /or revised Disbursement amounts will be included in Hold/Release
„
transmissions if present.
3. Update the Hold/Release Status field on RPAELAP to HS Hold Sent or RS Release
Sent.
4. Output files include the RPRHDRL.xxxxx.DAT data file and .lis file with the Control
Report and records not processed (with reasons).
Electronic Transfer
EFT/Disbursement Roster Upload Process (RPREFTL)
This process should be run to load student detail data to the temporary RPREFTD table
and cash data to the RPREPMT table.
To transferring file(s) to the Banner dataload directory:
Note
Multiple files may be placed in the directory, but will be processed one at
„
a time.
1. Rename each file to eftxxx.dat where xxx is a school-maintained sequence number.
After the file is processed, the first nine characters of the Header are changed to
Processed to prevent a duplicate upload.
2. Enter the single parameter file name and run the process.
Electronic Payment Receipt form (RPAEPMT)
1. Review summary cash information.
• Single record for all EFT payments in the file.
2-180
Financial Aid 8.3
User Guide
Processing
January 2009
• Single record for all Netted EFT payments in the file. If netting is used, the
school retains and recycles funds recovered from loan adjustments. Student
records in the file which represent the netted fund total will have a file code
of A.
• Single record for all Master Check payments in the file.
• Individual records for each Individual Check payment in the file. If the check
number field is blank on the incoming file, Banner will generate a Reference
ID number. Banner Reference IDs will have the @ sign.
2. Contact the Accounting Office to confirm that EFT funds have been received in the
bank account.
3. Confirm receipt of checks/master checks.
4. Enter a checkmark by the summary EFT, master check, or netted amount to indicate
receipt of funds so that records will upload during the posting process.
Note
Be certain to mark the receipt flag on $0 payment rosters if netting so that
„
funds will post to student(s).
5. Enter a checkmark by each individual check received so that the amounts will post.
EFT Posting Process (RPREFTP)
This process matches student records using the unique loan identifier and uploads the data
to the RPRLDSB table. If the record loads successfully, it is deleted from the temporary
table.
1. Enter parameters and run the RPREFTP process.
2. Select a Distribution Method (that is, E, I, M, N) or leave blank to post all types of
student detail records at once.
3. Enter a specific Reference ID or leave blank to process all records.
4. Review output. Verify the process completed by viewing the .log file. The .lis file will
show all students processed in the run including error messages for thosethat did not
load to the permanent tables.
5. Re-run RPREFTP to generate a report listing the names of only those students whose
records did not match. Resolve on RPAELDB suspense form.
Note
If there are multiple records for the same student in the file, additional
record(s) will be inserted on RPALDSB.
January 2009
„
Financial Aid 8.3
User Guide
Processing
2-181
RPAELAP Fields Populated by RPREFTP Process
In the Disbursement Schedule window, the Confirmation Flag indicates the service
provider has borrower confirmation of loan request (for Loan Pilot Program schools). The
Confirmation Flag will be used during the RPEDISB process for non-PLUS loans when
the Direct Loan indicator is not null.
Electronic Loan Disbursement form (RPAELDB)
To resolve suspended loan records, blank out the ID in the Key block to enter a query. You
can sort on the record types shown on RPAEPMT (that is, E, M, I, N).
We recommend performing a Print Screen for each suspended record and comparing it to
the loan application.
• If the Loan ID is incorrect, change the Loan ID on the RPAELDB record and rerun RPREFTP.
• If there is a Social Security Number mismatch, manually enter data on RPALDSB
and delete the loan record from the temporary tables.
• If there is a Birthdate error (most common), correct the Birthdate and re-run
RPREFTP.
• If the EFT authorization block is not checked on RPAELAP, for funds received via
EFT, obtain authorization from the student, check the RPRELAP block, and re-run
RPREFTP.
• If the EFT block is checked on RPAELAP and funds were received as a paper
check, remove the EFT indicator on RPAELAP and re-run RPREFTP. If you have
separate funds for paper checks, you must cancel the EFT fund application and
award, reaward/recreate the application from the paper check fund, and re-run the
posting process.
• If the record is not your student, use the Print Screen of RPAELDB as authorization
for the Finance Office to cut a check from the EFT account back to the lender.
Delete the record on RPAELDB.
1. Rerun RPREFTP after data correction or deletes.
Note
Multiple records for the same student in the same batch will result in
multiple disbursement records on RPALDSB.
„
To determine fees subsidized by the guarantor/lender, you must verify that:
• Response files include fees to be subsidized by the guarantor/lender for each loan
disbursement.
• Fee subsidies are loaded to the Loan Disbursement (RPRLABD) table and are
visible in the Fees Paid field on RPAELDB only while the Response records are in
2-182
Financial Aid 8.3
User Guide
Processing
January 2009
the temporary tables. Schools may wish to write a program to capture the fees and
calculate a new net amount for memos.
Disbursement form Field Population
Loan Disbursement form (RPALDSB)
This form displays the historical loan record for a student. Disbursement data populated
by the Electronic Loan Application Process (RPRELAP) include:
• Fund
• Term Code
• Schedule Date
• Sequence Number
Disbursement data populated by the EFT Posting Process (RPREFTP) include:
EFT Records
• Reference ID (from the roster)
• EFT (Electronic Funds Transfer) Amount/Date
• Electronic Funds Transfer Indicator checked
• Feed Indicator set to Y
• Individual Checks
• Reference ID (check number)
• Check Amount/Date
• Feed Indicator IS NULL (must sign check)
Master Check
• Reference ID (master check number)
• Amount/Date
• Feed Indicator IS NULL (must sign for proceeds)
When checks/master check forms are signed:
• Feed Indicator (manual)
• Feed Date
By the RPEDISB disbursement process:
January 2009
Financial Aid 8.3
User Guide
Processing
2-183
• Transaction Number from the Student Account posting.
• Disbursement Load (load code) and Option (type of hours used for calculation)
Due to non-enrollment/withdrawal adjustments:
• Returned Amount for refund amounts calculated after the check is fed.
• Returned to Lender for return of unclaimed checks that have not been fed.
• Returned Date. (Date returned to lender).
Note
Create a separate disbursement record on RPALDSB using the Insert
Record function to post refunds/returns to the lender. Amounts to be
returned can be posted prior to receipt of funds.
„
Other:
• Certified Hours. This is the credit hours used for eligibility on the loan application
(entered manually on RPAELAP term schedule window)
• Student Received. An optional field populated manually to show date student
received balance of loan proceeds.
• Disbursement Bypass. Used with adjusting entries to correct data entry errors.
• Disbursement Override.Permits disbursement when the loan amount is greater
than the award amount. Edit uses total of all term disbursement amounts up to and
including the term in which the disbursement process is being run.
Disburse to Student Account
Disbursement Process (RPEDISB)
1. Run the disbursement process online or in batch to release memos, authorizations,
and/or payment information to the student account. Disbursement may also be run in
the Student Accounting Office if loan checks or Master Check forms are signed there.
2. Check error messages on report or on the ROIDISB form.
Note
This process uses the Financial Aid Consortium enrollment first if the
Consortium Indicator is checked. It uses the actual Student System
enrollment (billable or adjusted per RPROPTS option) as of date of
disbursement run.
RPEDISB/RPALDSB Disbursement/Authorization calculates from the net
of all loan disbursement records for term on the RPALDSB disbursement
form and allows Payment and Authorization in the same term when two
„
disbursements are scheduled.
2-184
Financial Aid 8.3
User Guide
Processing
January 2009
3. Process checks for EFT code or MPN Federal Application code of M.
4. Fees paid by the lender captured during the RPREFTL process are used to calculate
loan memos.
Note
Loan disbursements for students who have not accepted charges when
the Accept Charges field on RPROPTS is checked will be rejected. New
„
error message will appear.
Loan Adjustments
Returning Individual Checks Prior to the Accounting Feed
1. Access the appropriate term record on RPALDSB.
If the student is NOT ENROLLED, enter the check amount on the Retn’d Lndr line on
the Original disbursement term record.
If the student is ENROLLED, use the Insert Record function to create a new term
record for the adjusting entry. Enter the check amount on the Retn’d Lndr line and
save.
Entry on the Retn’d Lndr line prevents any further disbursement. Previous memos
will be backed out.
2. Cancel the award on RPAAWRD.
3. Return check to lender.
Returning Calculated Refund Amounts to Lender
1. Access the appropriate term record on RPALDSB.
2. Use the Insert Record function to create a new term record for the adjusting entry.
3. Enter adjustment amount in Returned Amount field. If you are netting
disbursements, check the Disbursement Bypass field to prevent generation of a
refund check to the lender. Save the data.
4. Reduce the award amount on RPAAWRD so that future transcripts will be correct.
5. Run the RPEDISB process to back out excess loan funds.
Note
Banner does not support the return of refund amounts to lenders via EFT.
The posting to Finance for a refund check happens immediately when an
entry is made on RPALDSB and RPEDISB is run.The student ID is NOT
„
passed to Finance as part of the refund check process.
January 2009
Financial Aid 8.3
User Guide
Processing
2-185
Correcting Loans - Received Amount Less than Awarded Amount
Reduce the awarded offer and accepted amounts on RPAAWRD or RPAAPMT to the
Approved amount so that the financial aid transcripts will be correct.
Loan Reports
Aging of Nondisbursed Loans Report (RPRLNAG)
This report displays the number of days between receipt of the loan funds and the date of
the report as well as basic loan information.
RPRLNEX Exceptions-Students Not Fully Funded Report
The Loan Funding Exception Report lists those students whose received amounts are less
than the amount on the loan by term table.
Parameters include:
• Tolerance Amount ($1.00 is used if no tolerance is entered).
• Process Type compares Pending, Actual, or Both disbursements.
• Process EFT Only allows you to disregard paper checks.
• Reference ID allows you to restrict report by batch.
Setting the Exclude Flag on the individual RPAELAP form will prevent the line from
displaying for a student who has appeared on an earlier report even if a discrepancy
between award/disbursement amount exists.
Review and adjust award form as needed so that transcripts will be correct or so that future
loans for the year will generate correctly.
Loan Summary Report (RPRLSUM)
The Loan Summary Report lists loans for students and can be categorized in several ways
through report parameters.
CommonLine Loan Adjustment
• If the Approved loan amount is less than the recommended amount for adjustment
of RPAAWRD, create and run a population selection based on:
RPRLAPP_APPROVE_AMT < RPRLAPP_RECOMMENDED_AMT
RPRLAPP_APPROVE_DATE > & APPROVE_DATE
RPRLAPP_EL_STATUS = B
RPRLAPP_AIDY_CODE
2-186
Financial Aid 8.3
User Guide
Processing
January 2009
• When canceling the Spring disbursement of a full-year loan (also may be used for
other funds on RPAAWRD):
1. Cancel the full amount to move award to the Cancelled column on RPAAWRD.
2. Change the status to ACPT and enter the Fall portion of the loan in the Offered and
Accept columns.
3. Adjust the Dollar Amount on RPAAWRD to the full amount Fall, $0 Spring.
4. Inactivate Spring loan disbursement (student not enrolled, no disbursement)
5. Access the term disbursement record on RPALDSB.
6. Enter the full, anticipated disbursement amount in the Returned to Lender field,
Save.
7. Recoup the Spring disbursement (loan disbursed).
8. Access the term disbursement record on RPALDSB.
9. Click Insert Record to duplicate the term record.
10. Enter the return amount in Returned Amount field, enter date, and set Feed
Indicator.
11. Run the disbursement to create a negative entry on the student account.
12. Cancel the disbursement with the guarantor.
• Delete/Replace Functions
Unsent Loan Application (create replacement application)
• Awarded loan and created original application.
• Increased award on RPAAWRD
• Changed Loan Status to Not Ready to send
• Clicked Create App button. Original application
Unsent Loan Application (create second application)
• Awarded loan and created original application.
• Increased award on RPAAWRD
• Left status at Ready to Send
• Clicked Create App button. Created second application with Ready status.
Sent Loan Application (create second application)
• Awarded loan and created original application.
January 2009
Financial Aid 8.3
User Guide
Processing
2-187
• Extracted Loan. Status Sent on original loan application.
• Increased award on RPAAWRD
• Clicked Create App button. Created second application with Ready status.
• Decline/Cancel Loan
Loan Not Disbursed
1. Enter CNCL or DECL status to move award to Cancel/Decline column.
2. Access RPAELAP form and enter CNCL status in left-hand status field to inactive.
3. Report cancellation to guarantor.
4. Watch for guarantor status on right hand side of RPAELAP to change to Terminate
Loan Disbursed
1. Reduce RPAAWRD Offer and Accept amounts to $0.
2. Recoup disbursement.
3. Access term disbursement record on RPALDSB
4. Click Insert Record to duplicate the term record.
5. Enter return amount in Returned Amt field, enter date, and set Feed Indicator.
6. Run disbursement to create a negative entry on the student account.
7. Cancel the disbursement with the guarantor.
Electronic Loans as Certification Requests in
Common Response File
When a Loan application has been initiated by the student/parent with a Lender or
Guarantee Agency, the loan certification request is sent to the school in the CommonLine
Response file prior to the Electronic Loan application being created in Banner.
1. If possible, identify the loan from the third-party software report prior to running
RPRELRU. If no report is available, the loan will be identified on the report
generated by RPRELRU and will include the unique Loan ID assigned by the
Guarantee Agency.
2. After the loan has been identified and the student’s eligibility determined, award the
student the appropriate fund and create the loan application in Banner using either the
online process or batch RPRELAP process.
2-188
Financial Aid 8.3
User Guide
Processing
January 2009
3. From RPAELAP, change the process type to C - (Certification Request) and the
record type to CR - (Correct the Submission). This will then allow you to access the
Loan ID field on RPAELAP.
4. Change the Loan ID to match exactly the Loan ID that has been assigned by the
Guarantee Agency/Lender.
5. Commit the change.
6. If the loan is a certification request, change the Loan Status to R - (Ready), for the
RPRELAX process to extract the loan to send in the Application Send File. The Loan
ID will not be changed as long as the first six positions are not the School Code as
entered on ROAINST as the Main Campus Pell ID.
If the Certification Request is for a Combined Sub/Unsub, the Loan ID of the
subsidized loan should be updated to match the Unique Loan ID assigned by the
Guarantee Agency/Lender. For the unsubsidized loan, the Cross-reference Loan ID
will need to be updated using SQL* Plus to match the Unique Loan ID assigned by the
Guarantee Agency/Lender and the non-unique Loan ID can remain.
Future Response, Change Transaction, and EFT Roster files will recognize the Loan ID
and will correctly process without further manual intervention.
Note
Parent and student data contained in the Response file will not be loaded
„
into Banner. This information must be manually entered.
Alternative Loans
This section addresses Banner’s Electronic loan processing that allow clients to create
applications and receive response and disbursement files for Alternative Loans.
Alternative Loan Processing Flow
The basic steps to process a Electronic Alternative Loan in Banner include:
1. Receive the loan application from the student or receive Certification Request for the
loan via the RPRELRU Electronic Response Upload file.
2. Award the loan on one of the Banner award forms (RPAAWRD, RPAAPMT, and
ROARMAN).
3. Create the RPAELAP Electronic loan application. If the loan involves a Certification
Request, then you must update certain fields on the RPAELAP form and replace the
January 2009
Financial Aid 8.3
User Guide
Processing
2-189
Banner-generated unique loan ID to the unique ID created initially by the lender (sent
in the Response file).
4. Extract the loan application via the RPRELAX Electronic Loan Extract Process.
5. Receive a Response file via the RPRELRU Response Upload Process (this is optional
unless utilizing Certification Requests for Alternative Loans).
6. Receive EFT/individual check/Master Check payments via the RPREFTL/RPREFTP
processes.
Institutional Financial Aid Options form (ROAINST)
See the “Banner Electronic Loan Processing - Preliminary forms Setup” section for details
on setting up this form.
Fund Base Data form (RFRBASE)
Establish a separate loan fund for any lender for whom you will process Alternative loans
using Electronic loan methodology.
Fund Management form (RFRMGMT)
In the Aid Year Specific Data - Packaging Options window, enter the appropriate
Alternative Loan Program Type code for each Alternative loan fund. This code defaults
into the Electronic Loan Application form (RPAELAP).
Note
The Needs Analysis checkbox may be selected or deselected, depending
on the requirement for each lender. A checkbox in this field causes the
calculated Expected Amount on the RPAELAP Loan Application form to
„
be affected by EFC and prior aid received.
Loan Options form (RPRLOPT)
Establish additional forms as needed for new Alternative loan funds. A separate form for
each federal and Alternative electronic loan fund is required. The Guarantor is known as
the Insurer for Alternative loans.
Loan Period Base Data Rules form (RPRLPRD)
Create additional loan periods as needed to accommodate Alternative loans.
2-190
Financial Aid 8.3
User Guide
Processing
January 2009
Electronic Loan Application Process (RPRELAP)
Enter Parameter 02 to include Alternative loan funds. If no needs analysis record is
present, the Social Security Number and Date of Birth are pulled from the SPBPERS
General Person table.
This process allows the creation of application with a negative or zero amount and prints
the message App created with an expected amount of zero or less in the .log file. These
will not extract.
The process also populates null values in the Fed App form and Serial Loan fields, since
an MPN is not required. It will not replace data in the Parent Alternative Loan Data
window during delete/replace.
Electronic Loan Application form (RPAELAP)
The unique Loan ID includes the institutional EL School Code/Branch code or Pell code
after extraction.
If a Certification Request record is received, the Loan ID field should be updated to the
Loan ID established by the lender/servicer. To manually update the Loan ID field, change
the process type to CR and the record type to C. You can then manually update the Loan
ID field.
Note
The RPRELAX process will not convert the Loan ID if positions 1-6
(agency code) do not match the School ID.
„
In the Alternative Loan Data window (which is accessible only if the Alternative Loan
Program Type code is populated on RFRMGMT form), the data incorporated as the
CommonLine @4 record is sent with the @1 record which includes basic CommonLine
loan information.
The Program Type code defaults from RFRMGMT according to the fund awarded. The
Total Student Debt is required if the Loan Process Type = GO, GP, PG. The remaining
fields must be entered manually if applicable to student.
In the Cosigner Information section, cosigner data may be blank. If it is required, you must
manually enter it.
Note
If the lender requires this data, be sure to enter all of it. Partial data entry
„
may cause the loan to reject.
In the Parent Loan Demographic Data window, populate the parent fields with third-party
borrower data if the parent is not actual alternative loan borrower.
January 2009
Financial Aid 8.3
User Guide
Processing
2-191
Electronic Loan Application Extract Process
(RPRELAX)
Uses the Student/Bor Ind to extract either student or parent/third-party demographic data.
This process extracts @4 Alternative loan record data, and incorporates Campus and EL
School code data into unique loan ID. The process also ignores Hold/Release codes for
Alternative Loan funds.
Electronic Loan Response Update Process (RPRELRU)
Certification Request records are identified via the message Cert Request, not processed.
The Load Alternative Loan Approved Amount and Date If Guarantee fields are not
populated.
This process also processes @4 record data and loads data to relevant list fields on
RPAELAP the Loan Application form (RPAELAP).
Electronic Loan Load/Post Processes (RPEFTL/
RPREFTP)
This process posts EFT, individual check, or Master Check data received in an electronic
file. Data is visible on the Loan Disbursement (RPALDSB) form. Checks received that
are not part of the roster must be entered on RPALDSB by you.
Disbursement Process (RPEDISB)
This process disregards Hold/Release codes.
Disbursement/Adjustment
Banner Commonline Electronic processing includes EFT, Master Check, and individual
check record upload capability. An EFT file may contain any or all of these types of
disbursements. Banner Hold/Release may be used to update the initial Hold/Release status
to permit or prevent the receipt of scheduled loan disbursements depending upon the
option of the school.
2-192
Financial Aid 8.3
User Guide
Processing
January 2009
Disbursement Process (RPEDISB)
1. Run the disbursement process online or in batch to generate memos, authorizations,
and disbursement error messages if the disbursement edit optional parameter is being
used for the RPRHDRL process.
For Revised Disbursement amount processing:
1. Enter changes to disbursement amounts on RPAELAP as net amounts. Banner will
convert it to the gross amount if the revision is included with the RPRHDRL record.
Loan memos will use Revised Disbursement amounts if present in RPAELAP
Disbursement window.
2. Review disbursement error messages on the disbursement report or on ROIDISB.
Hold/Release Process (RPRHDRL)
This process captures changes to the initial Hold/Release status and creates a data file for
transmission to the service provider or lender.
1. Run the process after receiving the response file. The Guarantor sequence number is
needed.
2. Batch update of status by fund/term updates all available undisbursed records or use
Disbursement Edit.
Note
The Disbursement edit (which is optional) requires at least one
disbursement reject in the Disbursement Results Table to hold a loan, and
that no rejects be found to release a loan. Revised Disbursement dates
and /or revised Disbursement amounts will be included in Hold/Release
„
transmissions if present.
3. Update the Hold/Release Status field on RPAELAP to HS Hold Sent or RS Release
Sent.
4. Output files include the RPRHDRL.xxxxx.DAT data file and .lis file with the Control
Report and records not processed (with reasons).
January 2009
Financial Aid 8.3
User Guide
Processing
2-193
Electronic Transfer
EFT/Disbursement Roster Upload Process (RPREFTL)
This process should be run to load student detail data to the temporary RPREFTD table
and cash data to the RPREPMT table.
To transferring file(s) to the Banner dataload directory:
Note
Multiple files may be placed in the directory, but will be processed one at
„
a time.
1. Rename each file to eftxxx.dat where xxx is a school-maintained sequence number.
After the file is processed, the first nine characters of the Header are changed to
Processed to prevent a duplicate upload.
2. Enter the single parameter file name and run the process.
Electronic Payment Receipt form (RPAEPMT)
1. Review summary cash information.
• Single record for all EFT payments in the file.
• Single record for all Netted EFT payments in the file. If netting is used, the
school retains and recycles funds recovered from loan adjustments. Student
records in the file which represent the netted fund total will have a file code
of A.
• Single record for all Master Check payments in the file.
• Individual records for each Individual Check payment in the file. If the check
number field is blank on the incoming file, Banner will generate a Reference
ID number. Banner Reference IDs will have the @ sign.
2. Contact the Accounting Office to confirm that EFT funds have been received in the
bank account.
3. Confirm receipt of checks/master checks.
4. Enter a checkmark by the summary EFT, master check, or netted amount to indicate
receipt of funds so that records will upload during the posting process.
Note
Be certain to mark the receipt flag on $0 payment rosters if netting so that
„
funds will post to student(s).
2-194
Financial Aid 8.3
User Guide
Processing
January 2009
5. Enter a checkmark by each individual check received so that the amounts will post.
EFT Posting Process (RPREFTP)
This process matches student records using the unique loan identifier and uploads the data
to the RPRLDSB table. If the record loads successfully, it is deleted from the temporary
table.
1. Enter parameters and run the RPREFTP process.
2. Select a Distribution Method (that is, E, I, M, N) or leave blank to post all types of
student detail records at once.
3. Enter a specific Reference ID or leave blank to process all records.
4. Review output. Verify the process completed by viewing the .log file. The .lis file will
show all students processed in the run including error messages for thosethat did not
load to the permanent tables.
5. Re-run RPREFTP to generate a report listing the names of only those students whose
records did not match. Resolve on RPAELDB suspense form.
Note
If there are multiple records for the same student in the file, additional
record(s) will be inserted on RPALDSB.
„
RPAELAP Fields Populated by RPREFTP Process
In the Disbursement Schedule window, the Confirmation Flag indicates the service
provider has borrower confirmation of loan request (for Loan Pilot Program schools). The
Confirmation Flag will be used during the RPEDISB process for non-PLUS loans when
the Direct Loan indicator is not null.
Electronic Loan Disbursement form (RPAELDB)
To resolve suspended loan records, blank out the ID in the Key block to enter a query. You
can sort on the record types shown on RPAEPMT (that is, E, M, I, N).
We recommend performing a Print Screen for each suspended record and comparing it to
the loan application.
• If the Loan ID is incorrect, change the Loan ID on the RPAELDB record and rerun RPREFTP.
• If there is a Social Security Number mismatch, manually enter data on RPALDSB
and delete the loan record from the temporary tables.
January 2009
Financial Aid 8.3
User Guide
Processing
2-195
• If there is a Birthdate error (most common), correct the Birthdate and re-run
RPREFTP.
• If the EFT authorization block is not checked on RPAELAP, for funds received via
EFT, obtain authorization from the student, check the RPRELAP block, and re-run
RPREFTP.
• If the EFT block is checked on RPAELAP and funds were received as a paper
check, remove the EFT indicator on RPAELAP and re-run RPREFTP. If you have
separate funds for paper checks, you must cancel the EFT fund application and
award, reaward/recreate the application from the paper check fund, and re-run the
posting process.
• If the record is not your student, use the Print Screen of RPAELDB as authorization
for the Finance Office to cut a check from the EFT account back to the lender.
Delete the record on RPAELDB.
1. Rerun RPREFTP after data correction or deletes.
Note
Multiple records for the same student in the same batch will result in
multiple disbursement records on RPALDSB.
„
To determine fees subsidized by the guarantor/lender, you must verify that:
• Response files include fees to be subsidized by the guarantor/lender for each loan
disbursement.
• Fee subsidies are loaded to the Loan Disbursement (RPRLABD) table and are
visible in the Fees Paid field on RPAELDB only while the Response records are in
the temporary tables. Schools may wish to write a program to capture the fees and
calculate a new net amount for memos.
Disbursement form Field Population
Loan Disbursement form (RPALDSB)
This form displays the historical loan record for a student. Disbursement data populated
by the Electronic Loan Application Process (RPRELAP) include:
• Fund
• Term Code
• Schedule Date
• Sequence Number
Disbursement data populated by the EFT Posting Process (RPREFTP) include:
• EFT Records
2-196
Financial Aid 8.3
User Guide
Processing
January 2009
• Reference ID (from the roster)
• EFT Amount/Date
• EFT Indicator checked
• Feed Indicator set to Y
• Individual Checks
• Reference ID (check number)
• Check Amount/Date
• Feed Indicator IS NULL (must sign check)
Master Check
• Reference ID (master check number)
• Amount/Date
• Feed Indicator IS NULL (must sign for proceeds)
When checks/master check forms are signed:
• Feed Indicator (manual)
• Feed Date
By the RPEDISB disbursement process:
• Transaction Number from the Student Account posting.
• Disbursement Load (load code) and Option (type of hours used for calculation)
Due to non-enrollment/withdrawal adjustments:
• Returned Amount for refund amounts calculated after the check is fed.
• Returned to Lender for return of unclaimed checks that have not been fed.
• Returned Date. (Date returned to lender).
Note
Create a separate disbursement record on RPALDSB using the Insert
Record function to post refunds/returns to the lender. Amounts to be
returned can be posted prior to receipt of funds.
„
Other:
• Certified Hours. This is the credit hours used for eligibility on the loan application
(entered manually on RPAELAP term schedule window)
• Student Received. An optional field populated manually to show date student
received balance of loan proceeds.
January 2009
Financial Aid 8.3
User Guide
Processing
2-197
• Disbursement Bypass. Used with adjusting entries to correct data entry errors.
• Disbursement Override.Permits disbursement when the loan amount is greater
than the award amount. Edit uses total of all term disbursement amounts up to and
including the term in which the disbursement process is being run.
Disburse to Student Account
Disbursement Process (RPEDISB)
1. Run the disbursement process online or in batch to release memos, authorizations,
and/or payment information to the student account. Disbursement may also be run in
the Student Accounting Office if loan checks or Master Check forms are signed there.
2. Check error messages on report or on the ROIDISB form.
Note
This process uses the Financial Aid Consortium enrollment first if the
Consortium Indicator is checked. It uses the actual Student System
enrollment (billable or adjusted per RPROPTS option) as of date of
disbursement run.
RPEDISB/RPALDSB Disbursement/Authorization calculates from the net
of all loan disbursement records for term on the RPALDSB disbursement
form and allows Payment and Authorization in the same term when two
„
disbursements are scheduled.
3. Process checks for EFT code or MPN Federal Application code of M.
4. Fees paid by the lender captured during the RPREFTL process are used to calculate
loan memos.
Note
Loan disbursements for students who have not accepted charges when
the Accept Charges field on RPROPTS is checked will be rejected. New
„
error message will appear.
Loan Adjustments
Returning Individual Checks Prior to the Accounting Feed
1. Access the appropriate term record on RPALDSB.
If the student is NOT ENROLLED, enter the check amount on the Retn’d Lndr line on
the Original disbursement term record.
2-198
Financial Aid 8.3
User Guide
Processing
January 2009
If the student is ENROLLED, use the Insert Record function to create a new term
record for the adjusting entry. Enter the check amount on the Retn’d Lndr line and
save.
Entry on the Retn’d Lndr line prevents any further disbursement. Previous memos
will be backed out.
2. Cancel the award on RPAAWRD.
3. Return check to lender.
Returning Calculated Refund Amounts to Lender
1. Access the appropriate term record on RPALDSB.
2. Use the Insert Record function to create a new term record for the adjusting entry.
3. Enter adjustment amount in Returned Amount field. If you are netting
disbursements, check the Disbursement Bypass field to prevent generation of a
refund check to the lender. Save the data.
4. Reduce the award amount on RPAAWRD so that future transcripts will be correct.
5. Run the RPEDISB process to back out excess loan funds.
Note
Banner does not support the return of refund amounts to lenders via EFT.
The posting to Finance for a refund check happens immediately when an
entry is made on RPALDSB and RPEDISB is run. The student ID is NOT
„
passed to Finance as part of the refund check process.
Correcting Loans - Received Amount Less than Awarded Amount
Reduce the awarded offer and accepted amounts on RPAAWRD or RPAAPMT to the
Approved amount so that the financial aid transcripts will be correct.
Loan Reports
Aging of Nondisbursed Loans Report (RPRLNAG)
This report displays the number of days between receipt of the loan funds and the date of
the report as well as basic loan information.
January 2009
Financial Aid 8.3
User Guide
Processing
2-199
RPRLNEX Exceptions-Students Not Fully Funded
Report
The Loan Funding Exception Report lists those students whose received amounts are less
than the amount on the loan by term table.
Parameters include:
• Tolerance Amount ($1.00 is used if no tolerance is entered).
• Process Type compares Pending, Actual, or Both disbursements.
• Process EFT Only allows you to disregard paper checks.
• Reference ID allows you to restrict report by batch.
Setting the Exclude Flag on the individual RPAELAP form will prevent the line from
displaying for a student who has appeared on an earlier report even if a discrepancy
between award/disbursement amount exists.
Review and adjust award form as needed so that transcripts will be correct or so that future
loans for the year will generate correctly.
Loan Summary Report (RPRLSUM)
The Loan Summary Report lists loans for students and can be categorized in several ways
through report parameters.
CommonLine Loan Adjustment
• If the Approved loan amount is less than the recommended amount for adjustment
of RPAAWRD, create and run a population selection based on:
RPRLAPP_APPROVE_AMT < RPRLAPP_RECOMMENDED_AMT
RPRLAPP_APPROVE_DATE > &APPROVE_DATE
RPRLAPP_EL_STATUS = B
RPRLAPP_AIDY_CODE
• When canceling the Spring disbursement of a full-year loan (also may be used for
other funds on RPAAWRD):
1. Cancel the full amount to move award to the Cancelled column on RPAAWRD.
2. Change the status to ACPT and enter the Fall portion of the loan in the Offered and
Accept columns.
3. Adjust the Dollar Amount on RPAAWRD to the full amount Fall, $0 Spring.
4. Inactivate Spring loan disbursement (student not enrolled, no disbursement)
2-200
Financial Aid 8.3
User Guide
Processing
January 2009
5. Access the term disbursement record on RPALDSB.
6. Enter the full, anticipated disbursement amount in the Returned to Lender field,
Save.
7. Recoup the Spring disbursement (loan disbursed).
8. Access the term disbursement record on RPALDSB.
9. Click Insert Record to duplicate the term record.
10. Enter the return amount in Returned Amount field, enter date, and set Feed
Indicator.
11. Run the disbursement to create a negative entry on the student account.
12. Cancel the disbursement with the guarantor.
• Delete/Replace Functions
Unsent Loan Application (create replacement application)
• Awarded loan and created original application.
• Increased award on RPAAWRD
• Changed Loan Status to Not Ready to send
• Clicked Create App button. Original application
Unsent Loan Application (create second application)
• Awarded loan and created original application.
• Increased award on RPAAWRD
• Left status at Ready to Send
• Clicked Create App button. Created second application with Ready status.
Sent Loan Application (create second application)
• Awarded loan and created original application.
• Extracted Loan. Status Sent on original loan application.
• Increased award on RPAAWRD
• Clicked Create App button. Created second application with Ready status.
• Decline/Cancel Loan
Loan Not Disbursed
1. Enter CNCL or DECL status to move award to Cancel/Decline column.
2. Access RPAELAP form and enter CNCL status in left-hand status field to inactive.
January 2009
Financial Aid 8.3
User Guide
Processing
2-201
3. Report cancellation to guarantor.
4. Watch for guarantor status on right hand side of RPAELAP to change to Terminate
Loan Disbursed
1. Reduce RPAAWRD Offer and Accept amounts to $0.
2. Recoup disbursement.
3. Access term disbursement record on RPALDSB
4. Click Insert Record to duplicate the term record.
5. Enter return amount in Returned Amt field, enter date, and set Feed Indicator.
6. Run disbursement to create a negative entry on the student account.
7. Cancel the disbursement with the guarantor.
Electronic Loans Received as Certification Requests in
Common Response File
When a Loan application has been initiated by the student/parent with a Lender or
Guarantee Agency, the loan certification request is sent to the school in the CommonLine
Response file prior to the Electronic Loan application being created in Banner.
1. If possible, identify the loan from the third-party software report prior to running
RPRELRU. If no report is available, the loan will be identified on the report
generated by RPRELRU and will include the unique Loan ID assigned by the
Guarantee Agency.
2. After the loan has been identified and the student’s eligibility determined, award the
student the appropriate fund and create the loan application in Banner using either the
online process or batch RPRELAP process.
3. From RPAELAP, change the process type to C - (Certification Request) and the
record type to CR - (Correct the Submission). This will then allow you to access the
Loan ID field on RPAELAP.
4. Change the Loan ID to match exactly the Loan ID that has been assigned by the
Guarantee Agency/Lender.
5. Commit the change.
6. If the loan is a certification request, change the Loan Status to R - (Ready), for the
RPRELAX process to extract the loan to send in the Application Send File. The Loan
2-202
Financial Aid 8.3
User Guide
Processing
January 2009
ID will not be changed as long as the first six positions are not the School Code as
entered on ROAINST as the Main Campus Pell ID.
If the Certification Request is for a Combined Sub/Unsub, the Loan ID of the
subsidized loan should be updated to match the Unique Loan ID assigned by the
Guarantee Agency/Lender. For the unsubsidized loan, the Cross-reference Loan ID
will need to be updated using SQL* Plus to match the Unique Loan ID assigned by the
Guarantee Agency/Lender and the non-unique Loan ID can remain.
Future Response, Change Transaction, and EFT Roster files will recognize the Loan ID
and will correctly process without further manual intervention.
Note
Parent and student data contained in the Response file will not be loaded
„
into Banner. This information must be manually entered.
Direct Lending
Please see the COD Handbook for detailed instructions for working with Direct Loans.
Financial Aid Common Functions
Aid Year Default
Banner uses the current calendar year to try to default the global aid year code to be used
when you first start a Banner session. The first time you call a financial aid form (a form
starting with the letter R), Banner runs a form called ROQMENU in the background. One
of the things that this form does is to look at the current calendar year (based on Banner
date) and looks at the ROBINST table for an aid year code where the aid year start year is
the same as the current calendar year and the aid year end year is the same as the current
calendar year plus 1. So, if you are in 2004 it looks for an aid year code that was defined as
starting in 2004 and ends in 2005. After the start of the new year (2005) it looks for an aid
year code that was defined as starting in 2005 and ends in 2006. If it doesn't find one
(because you haven't defined the 0405 aid year code yet) then you will get the message
*ERROR* Could not calculate aid year code from today's date.
This error is not a serious one and will not prevent you from continuing your normal
activities. It just means that Banner could not determine a global aid year code. You would
have to manually set the global aid year code by entering it on a form that has aid year as a
key field or by calling any aid year specific form (like RNANAxx).
If you have defined your 0405 aid year code, Banner will use that aid year as the global aid
year code at start-up. If you wish to keep your global aid year code as 0405 you can
change the pivot date on the ROAINST form.
January 2009
Financial Aid 8.3
User Guide
Processing
2-203
User-Defined Data
User-defined data is stored in a table called ROBUSDF. This table has 360 data fields
named ROBUSDF_VALUE_1 through ROBUSDF_VALUE_360 in addition to a field for aid year,
PIDM, and activity date.
Each data field is 20 positions long and is defined as a character field. Values entered may
be character, integer, numeric, or date according to how each field is being used, however
editing for the proper format of integer, numeric, or date fields will not occur.
The Applicant User-Defined Data form (ROAUSDF) allows you to view, enter, and
update each of the 360 fields for an individual student for a particular aid year.
Descriptions to define how the institution uses each field are maintained on a form and
table called RORUSER. The descriptions for each field entered on RORUSER are
displayed next to the field number on the applicant form to aid the user. Field descriptions
are maintained separately for each aid year so you do not need to use the same descriptions
for the same field numbers each year. Even though descriptions are associated with each
field, the data stored in the field for a student is still referred to by its field number when
used in selection statements.
This design permits multiple user-defined fields to be used in a selection statement by
making it simpler to reference the data being stored. You are not required to use the same
fields in the same order each year.
In order to use these values in your rules, it is suggested that you run the RORUSER
Process on a regular basis such as weekly and after each Data Load. This will create a
record in the ROBUSDF table for every applicant with a RORSTAT record for the aid
year.
Batch Posting Process
The purpose of the Batch Posting Process is to allow you to post the same data to all
students who meet a common set of criteria at one time. For example, you can post a
tracking requirement for proof of citizenship status for all students who are permanent
resident aliens. Use of Batch Posting can greatly reduce the number of budget or tracking
groups that need to be defined.
The generic population selection process is used to identify the students to receive batch
posted data. The Batch Posting Process requires three steps.
1. Create a Population Selection ID to identify the sub-population of students to receive
the batch posted data. This is done on the Population Selection Definition Rules form
(GLRSLCT). The process to extract the IDs of the students who meet the Population
Selection ID criteria is called the Batch Report Selection Extract Process
2-204
Financial Aid 8.3
User Guide
Processing
January 2009
(GLBDATA). Individual student IDs can be inserted into or deleted from the list of
students generated by using the Extract Application form (GLAEXTR).
2. Identify the type of data to be posted, the codes to be posted, and the information
showing where the IDs of the extracted students are being stored. This is done on the
Batch Posting Rules form (RORPOST). The Batch Posting Type Indicator Validation
form (RTVPTYP) is used as a List form for the posting type code, but you cannot
update anything on this form. Multiple types of data can be set up to be posted during
the same run of the process.
For example, you can post tracking requirements, budget adjustments, and award
amounts all in the same run of the program. The Use Indicator field tells the batch
posting process which rules to execute during the next run of the program. You cannot
set the order in which multiple batch posting rules are executed. Therefore, if batch
posting of one type of data depends on the results of another type of batch posting, you
should run each batch posting rule by itself. This way you can control the order in
which they are processed.
3. Run the batch posting process itself. This is done with a standard process called the
Batch Posting Process (RORBPST). The process uses the batch posting rules
established on RORPOST. The batch posting process creates RORSTAT records
when posting awards for students who don't already have RORSTAT records for the
aid year. The only parameters for the process are for Aid Year to process and Print
Report (Y/N). The optional printed report shows a listing of students who received
each type of batch posted data with comments about anything unusual.
Many types of student data can be batch posted, each one identified by a unique type code.
The codes are listed on the Batch Posting Type Indicator Validation form (RTVPTYP) and
are discussed below:.
A - Aid Period
To batch post an Aid Period you enter A under the Type Indicator column and a valid aid
period code under the Code to Post column on the Batch Posting Rules form
(RORPOST). EFC Proration is performed if institutional rules call for it. Students will be
rebudgeted if necessary, however, components with a system/manual indicator of Manual
or Batch will not have that component's value changed. Awards in the student's package
will not be rescheduled so batch posting of aid periods should be done before students are
packaged. Since changing a student's aid period can change the amount of a Pell Grant,
users should perform a batch Pell Grant recalculation (RPEPELL) after batch posting a
new aid period. If you choose to batch post a new aid period, it is recommended that you
run that rule by itself before running other batch posting rules.
AA - Award Level Info Access Indicator
You may set the Award Level Info Access indicator to display (Yes) or to not display (No)
a specific fund on the Web for the population selection. Enter the fund code in the Code to
Post column. An update to the award table will not be made if the fund does not exist for a
student; an error message, Fund does not exist for student, info access indicator not
updated will be written on the output.
January 2009
Financial Aid 8.3
User Guide
Processing
2-205
AS - Student Info Access Indicator
You may batch post the Student Info Access Indicator to display (Yes) or to not display
(No) all award information for the population selection. The Student Info Access Indicator
is displayed on the Packaging Group Information tab on the award forms.
B - Budget Component/Amount
The batch posted component amount replaces the existing amount in the student's budget,
with the exception of manually assigned amounts. If the requested component does not
exist in the student's budget, it is created. The student's non-Pell budget type is updated
(unless the Pell type is the only budget type). The student's gross and unmet need will be
updated. If the student has not been budgeted yet, then the process will not post the new
component/amount.
BB - Borrower Based Indicator
This allows you to post a code to link students with the same Borrower-based loan periods
together. Can be seen on the Award forms.
BF - Budget Duration - FM
This allows the user to batch post a change to the student, number of months of attendance
for the Federal Methodology by calculation. Can be seen on RNAOVxx.
BI - Budget Duration - IM
This allows you to batch post a change to the student’s number of months of attendance for
the Institutional Methodology calculation. Can be seen on RNAOVxx.
C - Current Record Lock
This locks the need analysis record flagged as the Current Record from updates or
replacement until unlocked.
D - Packaging Completed Date
This process sets the existing date to null. A null packaging completed date allows
previously packaged students to be repackaged by the batch packaging process.
DD - Scheduled Disbursement Date
This allows you to post a disbursement date for a specific non-loan fund and term code.
E - Enrollment Status for Year
This allows you to post the enrollment status for the year used by the Packaging Process.
F - Fund Code/Amount/Status
All students will be packaged with the same amount and award status code. If a student
already has an award from the requested fund, its amount and status will be replaced with
the new amount and status. The information will not be posted if the student's package is
locked or the fund is locked in the student's package. The appropriate fund balances will
be updated. Award validation is performed on funds being packaged through batch
posting, so you should only batch post funds where all selected students are known to be
eligible. For example, it would be appropriate to batch post a scholarship for a student
regardless of the impact it might have on the rest of the awards in the package. Batch
2-206
Financial Aid 8.3
User Guide
Processing
January 2009
posting funds may create overawards. The student's unmet need will be updated. The
award will be scheduled into its term by term distribution and a disbursement schedule
will be created if called for. If the fund being posted is an auto accept fund then the fund
will be posted as accepted. You can use the batch posting process to cancel an award by
entering the amount as $0.00.
FH - HPPA Indicator
Identifies students who qualify for the increased Health Profession Programs Amount
(HPPA) loan amounts for Stafford loans.
FL - Fund Lock
Use this batch type to batch post a fund lock value to the Lock field on the Award
Maintenance - Locks/Indicators window of the RPAAWRD and RPAAPMT form. When
the Type Indicator is FL, valid values for Code to Post are:
Y - Always pay the locked amount
E - Adjust for enrollment decreases only (Pell only)
N - Award is not locked
FN - Fund/Amt/Status no validation
The FN batch type allows the batch posting of a fund code, amount, and status for a
population selection without going through the award validation process. The following
fields are required for the FN posting type:
• Code to Post (RORPOST_POST_CODE) is the Fund Code to be posted.
• Amount to Post (RORPOST_AMT) is the amount to be posted.
• Status or Term Code (RORPOST_STATUS_CODE) is the award status to be posted.
FS - Fund Code Status
The FS batch posting type lets you cancel, decline, or accept a specific fund award in its
entirety. When you select the FS type indicator, do not enter an amount for the rule. You
can only enter an award status which has been designated as accepted, cancelled, or
declined on RTVAWST for the FS posting type. For rules of type FS:
• The Code to Post is the fund code of the award. The list of values for the code is
drawn from the Fund Code Validation Table (RFRBASE).
• The Status or Term Code is the award status. The list of values for the code is
drawn from the Award Status Validation Table (RTVAWST).
The Status or Term Code is invalid for specified Post Type Code error message displays if
you enter an offered award status.
GL - Group Code Lock
The Group Code Lock allows you to post a lock to the any of the three group locks:
tracking, budgeting, or packaging. When the Type Indicator is GL, the Code to Post field
indicates whether to add (Y) or remove (N) a tracking, budgeting, or packaging group lock.
January 2009
Financial Aid 8.3
User Guide
Processing
2-207
For example, when Type Indicator is GL and the Code to Post field is Y, a lock is posted
to whatever group type (T (Tracking), B (Budgeting), or P (Packaging)) is indicated in the
Miscellaneous Code field. If the Code to Post field is N, the lock is removed from
whatever group type is indicated in the Miscellaneous Code field.
H - Hold Code
A financial aid hold can be placed or removed for a student. Holds are removed by making
them inactive. To remove the indicated hold code, you must enter an R in the Status field
on RORPOST. If the requested hold code currently exists for the student and it is locked
by another user, then batch posting will not update it.
I - Institutional Housing Code
You can batch post codes of 1-4. The codes are defined each year on the FAFSA
application. Only Current Records are updated. The institutional housing code can be used
in budget group selection and budget construction.
L - Letter Code
You can assign a student a letter to be sent the next time letters are run.
M - Applicant Message
This allows the user to specify a user-defined message to print on letters along with the
expiration date of that message.
MD - Memo Expiration Date
This allows the user to post an expiration date for a specific fund code and term code.
P - Package Lock
If a student's package is locked, the student cannot be repackaged, either manually or in a
batch.
PB - Post BA Pell Override
This flags students who are eligible to receive Post BA Pell.
PI - Pell Process Indicator
Use this batch type to enable/disable the Prevent Automatic Pell Calculation field on the
Applicant Status form (ROASTAT). This field prevents the automatic execution of the Pell
process from forms for a student.
PO - Pell Origination Indicator
This allows you to post an indicator on the student to automatically create an updated Pell
Origination record.
PT - Prep or Teacher Cert Ind
Once you have identified a population of students who are undergraduates taking
preparatory coursework, graduates taking preparatory coursework, or students enrolled in
teacher certification, you may use the Batch Posting Process to update the Preparatory or
Teacher Certification indicator on the RPAAWRD or RPAAPMT forms. Once the
indicator has been updated, the award and disbursement validation process use the
2-208
Financial Aid 8.3
User Guide
Processing
January 2009
appropriate annual limits for the student. Also, the Stafford loan records will contain the
indicator value once created.
R - Requirement Code/Status
A tracking requirement can be created or updated. If this type is to be posted, you must
also identify a tracking requirement code and a status code. You cannot batch post a
requirement that needs a Source Background Institution Code (SBGI code) such as a
financial aid transcript. If the requested requirement code already exists in the student's
tracking record, the status of that requirement will be updated to the new status. If the
posted requirement is a Once Only requirement, previous aid years are checked for prior
satisfaction. If the once only requirement was satisfied in a previous year, the status in the
current aid year will be updated. The packaging requirements, disbursement requirements,
and all requirements completed dates will be updated if necessary. If the student who is to
receive the batch posted requirement code/status does not have a RORSTAT record for the
specified aid year, the batch posting process will create one prior to posting the tracking
requirement.
RF - Fund Specific Requirements
This allows you to post a fund-specific tracking requirement.
S - Satisfactory Academic Progress
If you batch post an SAP code you must also enter a term code under the Status/Term
field on the RORPOST form. Satisfactory Academic Progress codes must first be defined
on the Satisfactory Academic Progress Validation form (RTVSAPR)
SL - SAP Code Lock/Unlock
This allows you to lock or unlock a SAP code for a term.
TE - Term Enrollment Status
This allows the user the ability to batch post a term enrollment status to update the FAFSA
data.
TL - Term Lock
Use this batch type to batch post a term lock value to the Term Lock field on the Fund
Awards by Term - Options window of the RPAAWRD and RPAAPMT form. When the
Type Indicator is TL, valid values for Code to Post are:
Y - Always pay the locked amount
E - Adjust for enrollment decreases only (Pell only)
N - Award is not locked
U - User Defined Variable/Value
You can batch post to any of the 360 user-defined data fields. The field being posted to
must be referred to by its field number, not by its description. To identify which field is to
receive the batch posted data, enter a number from 1 to 360 without any leading zeros
under the Code to Post field on RORPOST. The information to post for that field is
entered in the Status or Term Code field.
January 2009
Financial Aid 8.3
User Guide
Processing
2-209
UN - Non Year User-Defined Data
You can batch post to any of the 360 non year user-defined data fields. The field being
posted to must be referred to by its field number, not by its description. To identify which
field is to receive the batch posted data, enter a number from 1 to 360 without any leading
zeros under the Code to Post field on RORPOST. The information to post for that field is
entered in the Status or Term Code field.
V - Verification Selection Message
You can use this posting type to institutionally select a student for Title IV verification.
You can also use this option to deselect a student for verification. The verification message
will be posted to the student's current record only.
VS - Verification Status
You can post the student’s verification status code; the current values for the aid year are
available in the LOV. This value can be seen on ROAPELL.
Y - Banner Year in College
This option updates the Banner year in college which is used by all the processes. Only the
current record is updated. The values for Banner year in college are:
1
2
3
4
5
6
7
0
1st time freshman, no prior college
Freshman, prior college
Sophomore, (2nd year undergrad)
Junior, (3rd year undergrad)
Senior, (4th year undergrad)
5th Year/Other undergrad
1st Year Graduate/Professional
Continuing Grad/Prof or beyond
1 - Federal Methodology Student Contribution Lock
This locks the FM-SC displayed on the Need Analysis form (RNARSxx) from being
updated or replaced. Only the field in the current record is locked.
2 - Federal Methodology Parent Contribution Lock
This locks the FM-PC displayed on the Need Analysis form (RNARSxx) from being
updated or replaced. Only the field in the current record is locked.
3 - Federal Methodology EFC Lock
This locks the Pell EFC displayed on the Need Analysis form (RNARSxx) from being
updated or replaced. Only the field in the current record is locked. This is the single field
loaded from EDE or AFSA tape where the SC and PC are not present. In order to lock the
Total where a SC and PC are both present, you must lock the SC and PC separately.
4 - System Pell EFC Lock
This locks the SYS-PGI displayed on the Need Analysis form (RNARSxx) from being
updated or replaced. Only the field in the current record is locked.
2-210
Financial Aid 8.3
User Guide
Processing
January 2009
5 - Institutional Methodology Student Contribution Lock
This locks the IM-SC displayed on the Need Analysis form (RNARSxx) from being
updated or replaced. Only the field in the current record is locked.
6 - Institutional Methodology Parent Contribution Lock
This locks the IM-PC displayed on the Need Analysis form (RNARSxx) from being
updated or replaced. Only the field in the current record is locked.
Note
Batch posting allows you to specify that when a student has a specific
Reject or Comment code, you can batch post a requirement or message,
etc., to that group of students. This process requires a population
selection, but one that will be used in conjunction with the Comment code
or Reject code. You do not need to write and support different population
selections for each possible combination of Reject or Comment codes
that may exist for a student. For example, if the goal is to attach a new
tracking requirement to all students with a Reject code of 04, then the
population selection used could be for all students with a RORSTAT
record for the year, define the Type code as R for Reject, and the Code as
„
04, and the tracking requirement and status code to be posted.
Displaying Student Enrollment
The Financial Aid Enrollment form (ROAENRL) maintains Banner Financial Aid hours
and displays Banner Student hours.
This form maintains Attending Hours by date for the student both for Financial Aid hours
and Current Hours from registration. You can view the student's registration for the term.
When an Aid Year has been entered in the Key Block, only the terms associated with the
aid year are displayed. You may only insert manual Financial Aid hours when an Aid Year
has been provided.
The Aid Year in the Key Block may be left blank to view all enrollment hours for a
student. When the Aid Year in the Key Block is left blank, the form acts as a query form to
display the enrollment terms in descending order for the student.
If necessary, you can select the ID button or List to search for existing applicants with the
Person Search form (SOAIDEN) or the Alternate ID Search form (GUIALTI).
When the Consortium indicator is checked, the previous functionality of using the
Financial Aid hours for the student is used.
If logging for packaging has been indicated on the Institutional Options form (ROAINST),
and Audit logging is yes for the data elements (RORDATA), updates and deletions of
Financial Aid hours, Financial Aid Attending hours, and the Consortium indicator will
occur.
January 2009
Financial Aid 8.3
User Guide
Processing
2-211
Building Rules (RORRULE)
Using Parentheses in Selection Statements
When constructing selection statements on the RORRULE form or when defining a
population selection ID, it's always a good idea to surround selection statements connected
with an OR with an open parenthesis and a closed parenthesis. This is recommended even
if it appears to be unnecessary. Without the parenthesis, Banner may be forced to make
assumptions on how to process the data. Be sure to enter the data in a way that Banner will
know for sure how you wanted it to be processed.
Hints for RORRULE form Use
The following are suggestions for improving RORRULE performance:
• If you use RCRAPP2, 3, 4 or RCRESAR, the first rule on the simple mode form
should use one of these tables to ensure that the correct join will be done behind the
scenes.
• If you use RCRAPP1, 2, 3, 4 or RCRESAR, you should include the rule:
AND RCRAPP1_CURR_REC_IND = Y
It does not have to be last, but should not be first. This is done so that the rule will use the
unique index on the RCRAPP1table and not a non-unique index.
• Do not use a view as the first rule on the simple rule form. The table or view of the
first rule is used to join all of the other tables. This may cause performance issues.
• If you only want to use a view as part of your rule, use one of the following as the
first rule to improve performance:
RORSTAT_AIDY_CODE= &AIDY_CODE or RORSTAT_PIDM IS NOT NULL
• Before using Expert mode, create as much of the rule as possible in Simple mode
and compile it. Then go to Expert mode and modify it. This will show the joins
which Banner generally expects and the format of them.
• In Expert mode, use UPPER CASE.
• In Expert mode, make sure that you have at lease one space following :AIDY,
:PIDM and :TERM. If you just hit carriage return at the end of the line, the rule
will not work correctly in the COBOL program although it will appear to be fine
when the <EXECUTE> button is pressed.
• The execute button will give you an idea about syntax errors, but does not execute
exactly the way that the COBOL program will. To test grouping rules and see what
is really being executed, the technical person can get the test student's PIDM, set
2-212
Financial Aid 8.3
User Guide
Processing
January 2009
the priority on the group to 1 on RTVPGRP and then put RORGRPS on hold on
GJAPCTL.
The full rule (the grouping process selection statement plus the compiled rule) will appear
in the log.
This can also be done by putting the student in a single person population selection and
running RORGRPS in debug mode. Please note, however, that RORGRPS will currently
hang if it hits any group without rules, so the user will need to either press Y <ENTER>
several times until they get back to a prompt or <N> ENTER to exit the job at that first
error.
• There are many factors when it comes to tuning. Unless you are using one of our
views which uses the RORVIEW table, views must populate for the entire database
before returning a single row. This is why it is inadvisable to use a view as the first
rule because all joins will be performed against it. Also, to determine which index
to use, Oracle reads from the bottom up. The first index which it completes is the
one which it will use whether it is the desired one or not. There are many other
factors as well including size of table, extents, etc. Factors related to tuning are
documented in Oracle's documentation.
Student Employment Procedures
Student Employment Implementation
1. RTVRFST – Referral Status Validation form
This form maintains the various statuses of job referrals. Define all possible statuses
which referral records may have.
2. RTVAUST – Authorization Status Validation form
This form maintains various statuses of work authorizations. Generally, work
authorizations are used to define those students who are authorized to be paid for a
specific time period and pay period. Define all possible statuses for work
authorizations; indicate whether or not the status means the authorization is Active or
Inactive. Examples may include statuses such as Authorized, Terminated, Resigned,
etc.
3. RJAPLBD – Placement Basic Data form
This form stores name and address information for all locations (both on- and offcampus) that employ students. The supervisor is the name of the person responsible
for supervising the student employees at that job location. This is also the form that
you use to define the placement codes.
January 2009
Financial Aid 8.3
User Guide
Processing
2-213
4. RJRPLRL – Placement Rules form
This form maintains placement information regarding allocation, employee class,
position, chart of account code, and organization code.
Note
If you use Banner Human Resources, then the List function is available
for indicating valid values for these fields. If you do not use Banner
Human Resources, these fields are free-format and have no validation. It
will be necessary to meet with your HR and GL colleagues to determine
„
appropriate coding for accounting purposes.
5. RJRSEDR – Student Employment Default Rules form.
This form maintains information which is defaulted into student authorization
records. Define the common start and end dates of authorizations, common start and
end pay dates, and default authorization status.
6. RJRPAYL – Payroll Load Control form.
Note
This form is necessary only when Banner Human Resources is used.
„
Identify those payrolls which are to be interfaced to the Student Employment Module.
The Payroll Year, ID, and No. can be brought forward from the Calendar Rules form
via List. Once the payroll identifiers are brought in, the only necessary field to
complete is the Term Code. The Term Code is necessary so the payroll load process
knows which term to post earnings to in the student's award record and in Funds
Management.
7. RJRJOBT - Job Title Base Data form.
This form defines the individual job titles that you use when you refer or authorize a
student for a particular job. The Job Title Code controls the default pay rate and
eligible range of pay rates for the job title.
8. RJRJREQ - Job Title Requirements form.
Use this form to identify the job skills/levels that are required for a Job Title Code.
9. RJASERF - Student Employment Referral form
Complete this form for a student when he or she is referred to a job location for
possible employment. (The use of this form is optional.)
10. RJASEAR - Student Employment Authorization form.
Complete this form for students that you have determined to be eligible to work at a
particular job. You can automatically create this data from the Student Employment
Referral form (if you completed this optional form).
11. RJASEME - Student Employment Mass Entry form.Use this form to enter payroll
data if your institution does not utilize Banner Human Resources, or if you do not
choose to run the process that automatically loads payroll data from the Human
Resources System to Banner Financial Aid.
2-214
Financial Aid 8.3
User Guide
Processing
January 2009
12. RJRLOAD - Payroll Load Process.
Use this process to interface payroll data from Banner Human Resources to Banner
Financial Aid.
Note
You can use the Student Employment Work History form (RJISEWH) to
„
verify a student's work history.
Algorithmic Packaging
Overview
Packaging is a fundamental activity for all Financial Aid offices in the administration of
financial aid. Key to leveraging scarce financial resources to attract the targeted incoming
class each year, as well as successfully supporting the enrollment management retention
goals, is the ability to systematically package students according to an institution’s
awarding philosophy. A cornerstone of Enrollment Management, packaging should
provide the ability to match the institution’s awarding philosophy directly to the actual
awards offered to the prospective students in order to successfully harvest the ideal class
and award returning students accordingly. If an institution cannot package according to
their awarding philosophy, they are forced to sacrifice their philosophy and yield rates
based on the limitations of software functionality or perhaps continue to package students
manually. Manual packaging is not reasonable for most institutions since it is a
cumbersome process and lends itself to errors.
Algorithmic packaging allows clients to use a business rules engine to automatically
package students in accordance with the institution’s awarding philosophy. In addition to
the algorithmic packaging business rules solution, many other changes have been made to
enhance the packaging process.
Algorithmic Packaging Features
This feature is designed to facilitate the use of algorithmic packaging with the Banner
Financial Aid baseline product. forms and processes have been added or modified to
provide a more complete means of automatically packaging students through the use of
algorithmic packaging forms in conjunction with pre-existing Banner Financial Aid rules
forms. The information that follows summarizes these features.
Algorithms
Banner Financial Aid includes an algorithmic packaging solution in the baseline product.
Algorithms can be performed at the fund level in addition to the packaging group level.
January 2009
Financial Aid 8.3
User Guide
Processing
2-215
Algorithmic Packaging
• Enables predictive modeling to support an institution’s enrollment.
• Provides a management strategy to help an institution manage complex
calculations to award the right funds to the right students.
• Allows an institution to package multiple financial aid awards based upon
configurable rules and calculations that support an institution’s awarding
philosophies.
• Includes the functionality to allow the use of algorithms as part of the fund
awarding sequence within the current packaging process.
Algorithmic Packaging Definition
End user creation of a set of ordered rules or steps for the automatic packaging of financial
aid funds. The rules or steps allow the use of mathematical expressions as part of the
awarding rules and logic for a particular fund within a packaging group based upon data
elements within the student and/or financial aid system.
Example
Award Fund 1 with a maximum of $1,000 and minimum of $200 not to exceed unmet need
Award Fund 2 up to 50% of Fund 1, not to exceed unmet need
Award Fund 3 up to 25% of Fund 1 total + 25% of Fund 2 total, not to exceed unmet need
Award Fund 4 up to 70% of remaining unmet need, not to exceed the total of Fund 1
Award Fund 5 up to 100% of remaining unmet need
Note
All the rules and steps utilize the fund award rules as the overall master
„
rule for fund eligibility.
forms
Algorithmic Packaging Rules form (RPRALGR)
The RPRALGR form enables you to use algorithmic packaging rules to award funds. On
this form, you write SQL statements to define algorithmic packaging rules, which are
arranged by rule code and sequence number.
Once you’ve validated the rule, you can test the rule by entering values for any
substitution parameters used in the rule and execute the rule in test mode. The system uses
your need analysis data in the testing of your algorithmic rules and temporarily stores the
simulated results in the Temporary Packaging Need Table (RPTNEED). The results
display in the Calculated Amount field. This allows you to verify that the rule will return
the expected results when used by the Packaging Process.
2-216
Financial Aid 8.3
User Guide
Processing
January 2009
Algorithmic Packaging Rule Code Validation form (RTVALGR)
The RTVALGR form enables you to define algorithmic packaging rule codes for use on
the Algorithmic Packaging Rules form (RPRALGR), Packaging Rules form (RPRPCKR)
and Packaging Group Fund Rules form (RPRGFND).
Packaging Functions
Using algorithms and parameters, functions include calculations based upon:
• a percentage of a fund award,
• a fixed dollar amount of a fund award
• a data value housed in the Banner system (less than, equal, greater than, not equal),
and
• a value that falls within a range of values housed in the Banner system (Between).
Awarding Based on Other Funds
Using algorithms and parameters, you can limit funds to specific amounts based upon
other funds, fund sources, or fund groups. Refer to the Sample Algorithmic Packaging
Rules section for examples.
Award a Fund Based on a Percentage of Another Fund
You can award a fund based on a percentage of other funds within a packaging group.
Simplification of Rules Creation and Maintenance
Algorithms can be performed at the packaging group level, in addition to the fund level.
Ability to Store and Reference Internal Interim Values in
Packaging Rules
The Algorithmic Packaging Rules form (RPRALGR) allows you to reference internal
interim values in SQL statements. These internal interim values are created and referenced
in the Temporary Packaging Need Table (RPTNEED) table. The RPTNEED table is a
temporary table which temporarily stores need analysis data for use in algorithmic
packaging rules. A row is inserted into the table for each student that is processed prior to
packaging the student and is deleted after the student is processed.
January 2009
Financial Aid 8.3
User Guide
Processing
2-217
Packaging Simulation Options
The Packaging Process (RPEPCKG) includes parameters that allow the process to:
• bypass tracking requirements during Simulated Packaging only,
• to award Pell in both Simulated and Actual mode, and
• to stop the awarding of an individual fund during simulated packaging, when that
fund's available amount has been exhausted.
Related Fund Features
forms
Packaging Group Fund Category Maximums Rules form (RPRFCAT)
The Packaging Group Fund Category Maximums Rules form allows you to place fund
category maximums on packaging groups.
Fund Category Validation form (RTVFCAT)
This form enables you to define fund categories for use on the Fund Base Data form
(RFRBASE).
Fund Award Inquiry form (RPIFAWD)
The Fund Award Inquiry form enables you to view all students who have a particular fund
for a particular aid year.
Fund Award Term Inquiry (RPIFTRM)
The Fund Award Term Inquiry form enables you to view all students with a particular fund
for a particular term.
Group Fund Limits
You can use group fund limits which supersede individual fund limits.
For example, suppose a student has total need of $10,000 and tuition of $7,000. Fund #1
has an individual award cap of $5,000 and Fund #2 also has a cap of $5,000. However,
Funds #1 and #2 are defined in a group, and the group rule is that total aid from all funds
in the group cannot exceed tuition.Therefore, the award from Fund #1 would be $5,000
but Fund #2 is limited to $2,000 because of the group cap. The remaining $3,000 of unmet
need must be met from funds outside the group.
2-218
Financial Aid 8.3
User Guide
Processing
January 2009
Ability to Apply a Percentage to All the Funds in the
Package as a Group
If the original unmet need or gross need is not being used throughout the packaging
process, you can take a defined percentage of remaining need or gross need and award the
funds so the original percentage is not exceeded. For example, if remaining need is 5,375
and the percentage of remaining need to award is 85%. The sum of the funds packaged
should not exceed 4,568.
Rounding Options for Awards
The Round Award field on the Fund Management form (RFRMGMT) enables you to
specify how you want to round the award.The RPEPCKG process rounds the award down
to a multiple of this amount to prevent an overaward. This field had fixed rounding
amounts of 10, 25, 50, or 100. The valid values for this field are 1 – 99999.
Ability to Inactivate Fund Codes, Groups, and Rules
The Fund Active field on the Fund Base Data form (RFRBASE) and Create and Maintain
Funds form (ROAMGMT) allows you to inactivate a fund code.
You can globally inactivate a budgeting group (RTVBGRP), packaging group
(RTVPGRP), requirements tracking group (RTVTGRP), or satisfactory academic progress
group (RTVSAPR).
The Rule Active field on the Financial Aid Selection Rule (RORRULE) form allows you
to inactivate fund awarding, budget group assignment, fund disbursement, packaging
group fund awarding, packaging group assignment, satisfactory academic progress and
requirements tracking group rules.
Ability to Override a Fund Rule for a Specific Student
The Fund Award Rule Override feature on RPAAWRD and RPAAPMT allows you to
override a Fund Award Rule, if one exists, for the aid year.
The Fund Disbursement Rule Override feature on RPAAWRD and RPAAPMT allows
you to override a Fund Disbursement Rule, if one exists, for the term.
Fund Category and Fund Cross-Reference Fields for
Packaging and Reporting
The Fund Cross Reference field enables you to cross reference IDs used for funds by
another office.This field is a user-defined field with no validation.
The Fund Category field allows you to group fund codes by a user-defined category.
January 2009
Financial Aid 8.3
User Guide
Processing
2-219
Fund Balance Roll Process (RFPFBRL)
The RFPFBRL process provides the ability to optionally roll fund balances from one aid
year to the next aid year.
Ability to Display All Recipients of a Particular Fund Code by
Aid Year or Term
The Fund Award Inquiry form (RPIFAWD) enables you to view all students who have a
particular fund for a particular aid year.
The Fund Award Term Inquiry form (RPIFTRM) enables you to view all students with a
particular fund for a particular term.
2-220
Financial Aid 8.3
User Guide
Processing
January 2009
Sample Algorithmic Packaging Rules
The examples that follow demonstrate how you might use the Algorithmic Packaging
Rules form (RPRALGR) to set up business rules for your institution.
Refer to Banner Online Help for detailed form and field information.
Example 1 - Institutional Grant with Amounts Based on GPA
and IM EFC Ranges
The following information provides an example of the calculation of an institutional grant
with amounts based on GPA and IM EFC ranges.
The rule uses three mutually exclusive sequences to award $5000 to the student if their
EFC is <10,000 and their GPA is at least 4.0, $2500 if their EFC is <10,000 and GPA is at
least 3.5, and $1500 if their EFC is <10,000 and their GPA is at least 3.0. Subsequent
sequences are evaluated only if the prior sequences fail.
This example uses the Temporary Packaging Table (RPTNEED). The RPTNEED table is
populated for a financial aid recipient by the Packaging Process (RPEPCKG) prior to
packaging the student. Any row created on this table is inserted for a student, used, and
then deleted. The table is also populated when you use the Test Rule button on the
Algorithmic Packaging Rules form (RPRALGR).
The f_get_gpa function is for illustrative purposes only. This function is not a SunGard
Higher Education-delivered function; the f_get_gpa function illustrates the use of a
client-created function within the rules.
Field
Value
Rule
GPA_EFC_RULE
Sequence
1
SQL Statement
SELECT 5000 FROM DUAL
WHERE EXISTS
(SELECT ‘X’ FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_IM_EFC < 10,000)
AND f_get_gpa(:AIDY, :PIDM) >= 4.0
January 2009
Financial Aid 8.3
User Guide
Processing
2-221
Field
Value
Rule
GPA_EFC_RULE
Sequence
2
SQL Statement
SELECT 2500 FROM DUAL
WHERE EXISTS
(SELECT ‘X’ FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_IM_EFC < 10,000)
AND f_get_gpa(:AIDY, :PIDM) >= 3.5
Field
Value
Rule
GPA_EFC_RULE
Sequence
3
SQL Statement
SELECT 1500 FROM DUAL
WHERE EXISTS
(SELECT ‘X’ FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_IM_EFC < 10,000)
AND f_get_gpa(:AIDY, :PIDM) >= 3.0
Example 2 - SEOG Award Calculation Based on Pell Award
Amounts for the Year
This case illustrates how you can create a rule for a fund which is based on another fund
award for the year. For example, you can base the calculation of an SEOG award on Pell
award amounts for the year. This example assumes you use a single fund code for all Pell
awards.
In this example, $2000 is awarded for SEOG when the student's Pell award is less than or
equal to $4300 but more than $3000; $1500 SEOG is awarded when the Pell award is less
than or equal to $3000 but more than $1500; and $1000 SEOG is awarded when the Pell
award is less than or equal to $1500 but greater than 0.
2-222
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
SEOG_CALC_1
Sequence
1
SQL Statement
SELECT 2000 FROM DUAL
WHERE EXISTS
(SELECT ‘X’
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_OFFER_AMT <= 4310
AND RPRAWRD_OFFER_AMT > 3000
AND RPRAWRD_FUND_CODE = ‘PELL’)
Field
Value
Rule
SEOG_CALC_1
Sequence
2
SQL Statement
SELECT 1500 FROM DUAL
WHERE EXISTS
(SELECT ‘X’
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_OFFER_AMT <= 3000
AND RPRAWRD_OFFER_AMT > 1500
AND RPRAWRD_FUND_CODE = ‘PELL’)
January 2009
Financial Aid 8.3
User Guide
Processing
2-223
Field
Value
Rule
SEOG_CALC_1
Sequence
3
SQL Statement
SELECT 1000 FROM DUAL
WHERE EXISTS
(SELECT ‘X’
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_OFFER_AMT <= 1500
AND RPRAWRD_OFFER_AMT > 0
AND RPRAWRD_FUND_CODE = ‘PELL’)
Example 3 - SEOG Award Calculation Based on Pell Award
Amounts for the Year while using Baseline Database
Functions
This case illustrates how you can create a rule for a fund which is based on another fund
award for the year. For example, you can base the calculation of an SEOG award on Pell
award amounts for the year.
This example is similar to Example 2 but uses baseline database functions delivered with
Banner Financial Aid. This example uses the Temporary Packaging Table (RPTNEED).
Inserts to the RPTNEED table are done automatically by the RPEPCKG process during
packaging. During that insert, the Simulate Switch (RPTNEED_SIMULATE_SW) is set depending on whether you are performing Actual or Simulated packaging. The Simulate
Switch indicates whether or not this row was created during simulated packaging.
This allows you to write an algorithmic rule that is based on the RPRAWRD Award table
during Actual packaging, and based on the RPTAWRD Temporary Award table during
Simulated packaging. The f_get_fund_offer function uses the RPTNEED_SIMULATE_SW to
determine which table to use for the calculation.
2-224
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
SEOG_CALC_2
Sequence
1
SQL Statement
SELECT 2000 FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_fund_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 4310
AND rpkalgr.f_get_fund_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 3000
Field
Value
Rule
SEOG_CALC_2
Sequence
2
SQL Statement
SELECT 2000 FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_fund_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 3000
AND rpkalgr.f_get_fund_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 1500
January 2009
Financial Aid 8.3
User Guide
Processing
2-225
Field
Value
Rule
SEOG_CALC_2
Sequence
3
SQL Statement
SELECT 1000 FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_fund_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 1500
AND rpkalgr.f_get_fund_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 0
Example 4 - SEOG Award Calculation Based on Pell Award
Amounts for the Year while using Multiple Pell Fund Codes
This example creates a rule for a fund which is based on the total award for a federal fund
ID for the year. For example, you can base the calculation of an SEOG award on Pell
award amounts for the year. This example assumes the institution uses multiple Pell fund
codes.
In this example, $2000 is awarded for SEOG when the student has funds awarded with
federal fund IDs of PELL whose total amount is between $3001 and $4310; $1500 is
awarded for SEOG when the student has funds awarded with federal fund IDs of PELL
whose total amount is between $1501 and $3000; $1000 is awarded for SEOG when the
student has funds awarded with federal fund IDs of PELL whose total amount is between
$1 and $1500.
2-226
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
SEOG_CALC_3
Sequence
1
SQL Statement
SELECT 2000 FROM DUAL
WHERE
(SELECT SUM(NVL(RPRAWRD_OFFER_AMT,0)
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_FUND_CODE IN
(SELECT RFRBASE_FUND_CODE
FROM RFRBASE
WHERE RFRBASE_FED_FUND_ID = ‘PELL’))
<= 4310
AND
(SELECT SUM(NVL(RPRAWRD_OFFER_AMT,0)
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_FUND_CODE IN
(SELECT RFRBASE_FUND_CODE
FROM RFRBASE
WHERE RFRBASE_FED_FUND_ID = ‘PELL’))
> 3000
January 2009
Financial Aid 8.3
User Guide
Processing
2-227
Field
Value
Rule
SEOG_CALC_3
Sequence
2
SQL Statement
SELECT 1500 FROM DUAL
WHERE
(SELECT SUM(NVL(RPRAWRD_OFFER_AMT,0)
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_FUND_CODE IN
(SELECT RFRBASE_FUND_CODE
FROM RFRBASE
WHERE RFRBASE_FED_FUND_ID = ‘PELL’))
<= 3000
AND
(SELECT SUM(NVL(RPRAWRD_OFFER_AMT,0)
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_FUND_CODE IN
(SELECT RFRBASE_FUND_CODE
FROM RFRBASE
WHERE RFRBASE_FED_FUND_ID = ‘PELL’))
> 1500
2-228
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
SEOG_CALC_3
Sequence
3
SQL Statement
SELECT 1000 FROM DUAL
WHERE
(SELECT SUM(NVL(RPRAWRD_OFFER_AMT,0)
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_FUND_CODE IN
(SELECT RFRBASE_FUND_CODE
FROM RFRBASE
WHERE RFRBASE_FED_FUND_ID = ‘PELL’))
<= 1500
AND
(SELECT SUM(NVL(RPRAWRD_OFFER_AMT,0)
FROM RPRAWRD
WHERE RPAWRD_AIDY_CODE = :AIDY
AND RPRAWRD_PIDM = :PIDM
AND RPRAWRD_FUND_CODE IN
(SELECT RFRBASE_FUND_CODE
FROM RFRBASE
WHERE RFRBASE_FED_FUND_ID = ‘PELL’))
> 0
January 2009
Financial Aid 8.3
User Guide
Processing
2-229
Example 5 - SEOG Award Calculation Based on Pell Award
Amounts for the Year while using Multiple Pell Fund Codes
and while using Baseline Database Functions
This case illustrates how you can create a rule for a fund which is based on another fund
award for the year. For example, you can base the calculation of an SEOG award on Pell
award amounts for the year. This example assumes you use multiple Pell fund codes.
This example is similar to Example 4 but uses baseline database functions delivered with
Banner Financial Aid. This example uses the Temporary Packaging Table (RPTNEED).
Inserts to the RPTNEED table are done automatically by the RPEPCKG process during
packaging. During that insert, the Simulate Switch (RPTNEED_SIMULATE_SW) is set depending on whether you are performing Actual or Simulated packaging. The Simulate
Switch indicates whether or not this row was created during simulated packaging.
This allows you to write an algorithmic rule that is based on the RPRAWRD Award table
during Actual packaging, and based on the RPTAWRD Temporary Award table during
Simulated packaging. The f_get_ffid_offer function uses the RPTNEED_SIMULATE_SW to
determine which table to use for the calculation.
Field
Value
Rule
SEOG_CALC_4
Sequence
1
SQL Statement
SELECT 2000 FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 4310
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 3000
2-230
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
SEOG_CALC_4
Sequence
2
SQL Statement
SELECT 1500 FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 3000
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 1500
Field
Value
Rule
SEOG_CALC_4
Sequence
3
SQL Statement
SELECT 1000 FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 1500
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 0
January 2009
Financial Aid 8.3
User Guide
Processing
2-231
Example 6 - Calculating Perkins Loans as a Percentage of
Pell
This case illustrates how you can create a rule for a fund which is based on another fund
award for the year. For example, this rule calculates a Perkins Loan as a percentage of
Pell.
In this example, Perkins would be awarded for 75% of the student's Pell award if the
student's Pell award was between $3001 and $4310; 50% of the student's Pell award if the
student's Pell award was between $1501 and $3000; 25% of the student's Pell award if the
student's Pell award was between $1 and $1500.
Field
Value
Rule
PERK_CALC
Sequence
1
SQL Statement
SELECT .75 *
rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW)
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 4310
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 3000
2-232
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
PERK_CALC
Sequence
2
SQL Statement
SELECT .50 *
rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW)
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 3000
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 1500
January 2009
Financial Aid 8.3
User Guide
Processing
2-233
Field
Value
Rule
PERK_CALC
Sequence
3
SQL Statement
SELECT .25 *
rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW)
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) <= 1500
AND rpkalgr.f_get_ffid_offer
(:AIDY,
:PIDM,
‘PELL’,
RPTNEED_SIMULATE_SW) > 0
2-234
Financial Aid 8.3
User Guide
Processing
January 2009
Example 7 - Calculation for a State Fund which has a Range
of Offer Amounts Based on a Percentage of Need and
Various Ranges of Cost of Attendance and EFC
This case illustrates how you create a rule for a fund which has a range of offer amounts
based on a percentage of need and various ranges of Cost of Attendance and EFC. In this
example, the rule also has defined minimum and maximum amounts. If the calculated
award falls below the minimum amount defined for the rule, no award is made. If the
calculated award is greater than the maximum amount defined for the rule, the maximum
amount is awarded, rather than the calculated amount.
In this example, the student would receive a State grant of 47% of their unmet need at the
time the packaging process begins (minimum of $500 and maximum of $4300) if the EFC
is between $1 and $4000 and their Budget is between $18001 and $24000; 37% of their
unmet need at the time the packaging process begins (minimum of $500 and maximum of
$4300) if the EFC is between $4001 and $6000 and their Budget is between $18001 and
$24000; 27% of their unmet need at the time the packaging process begins (minimum of
$500 and maximum of $4300) if the EFC is greater than $6000 and their Budget is
between $18001 and $24000; 47% of their unmet need at the time the packaging process
begins (minimum of $500 and maximum of $4700) if the EFC is between $1 and $4000
and their Budget is between $24001 and $26000; 37% of their unmet need at the time the
packaging process begins (minimum of $500 and maximum of $4700) if the EFC is
between $4001 and $6000 and their Budget is between $24001 and $26000; 27% of their
unmet need at the time the packaging process begins (minimum of $500 and maximum of
$4700) if the EFC is greater than $6000 and their Budget is between $24001 and $26000.
Also note in this example that the RPTNEED table has several Unmet Need Amount
columns. This example uses the RPTNEED_BEG_UNMET_NEED_AMT column. (The beginning
value of the student's FM unmet need when the packaging process is run.) This number is
calculated when the packaging process starts processing a student, and remains fixed. So
the resulting calculated amount will be the same regardless of what priority the
STATE_CALC_1 fund has in the packaging group. If the rule had used
RPTNEED_UNMET_NEED_AMT, the resulting calculated amount would differ, depending on
which funds and amounts were awarded to the student during the packaging process
before the STATE_CALC_1 rule was executed.
Note
To keep algorithmic rules as simple as possible, only conditions which
determine the actual amount of an award should be included in
algorithmic rules. Conditions which determine the overall eligibility of the
student for an award should continue to be defined on the Financial Aid
Selection Rules form (RORRULE).
For example, suppose an institution has a state grant which requires that
the student actually reside in the state. The residency condition could be
defined as a Fund Awarding rule on the RORRULE form, since it isn’t
actually required to determine the amount of the award. (See state grant
Example 7 below).
Another institution may have a grant program which awards larger
January 2009
Financial Aid 8.3
User Guide
Processing
2-235
amounts for in-state students. The residency condition would need to be
included in the algorithmic rule which calculates the amount of the grant.
„
(See state grant Example 8 below).
Field
Value
Rule
STATE_CALC_1
Sequence
1
SQL Statement
SELECT .47 * RPTNEED_BEG_UNMET_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT > 0
AND RPTNEED_FM_EFC_AMT <= 4000
AND RPTNEED_BUDGET_AMOUNT >= 18001
AND RPTNEED_BUDGET_AMOUNT <= 24000
Award Minimum
500
Award Maximum
4300
Field
Value
Rule
STATE_CALC_1
Sequence
2
SQL Statement
SELECT .37 * RPTNEED_BEG_UNMET_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT > 4000
AND RPTNEED_FM_EFC_AMT <= 6000
AND RPTNEED_BUDGET_AMOUNT >= 18001
AND RPTNEED_BUDGET_AMOUNT <= 24000
2-236
Award Minimum
500
Award Maximum
4300
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
STATE_CALC_1
Sequence
3
SQL Statement
SELECT .27 * RPTNEED_BEG_UNMET_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT > 6000
AND RPTNEED_BUDGET_AMOUNT >= 18001
AND RPTNEED_BUDGET_AMOUNT <= 24000
Award Minimum
500
Award Maximum
4300
Field
Value
Rule
STATE_CALC_1
Sequence
4
SQL Statement
SELECT .47 * RPTNEED_BEG_UNMET_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT > 0
AND RPTNEED_FM_EFC_AMT <= 4000
AND RPTNEED_BUDGET_AMOUNT > 24000
AND RPTNEED_BUDGET_AMOUNT <= 26000
January 2009
Award Minimum
500
Award Maximum
4700
Financial Aid 8.3
User Guide
Processing
2-237
Field
Value
Rule
STATE_CALC_1
Sequence
5
SQL Statement
SELECT .37 * RPTNEED_BEG_UNMET_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT > 4000
AND RPTNEED_FM_EFC_AMT <= 6000
AND RPTNEED_BUDGET_AMOUNT > 24000
AND RPTNEED_BUDGET_AMOUNT <= 26000
Award Minimum
500
Award Maximum
4700
Field
Value
Rule
STATE_CALC_1
Sequence
6
SQL Statement
SELECT .27 * RPTNEED_BEG_UNMET_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT > 6000
AND RPTNEED_BUDGET_AMOUNT > 24000
AND RPTNEED_BUDGET_AMOUNT <= 26000
2-238
Award Minimum
500
Award Maximum
4700
Financial Aid 8.3
User Guide
Processing
January 2009
Example 8 - Calculation for a State Fund which has a Range
of Offer Amounts Based on EFC and Whether a Student is InState or Out-of-State
This case illustrates how you create a rule for a fund which has a range of offer amounts
based on EFC and whether a student is in-state or out-of-state. (Assume the institution is
in Illinois.)
In this example, the student would be awarded a State grant for $2000 if their FM EFC
amount was $5000 or less and their state of residence was Illinois; $1000 if their FM EFC
amount was $5000 or less and their state of residence was not Illinois.
Field
Value
Rule
STATE_CALC_2
Sequence
1
SQL Statement
SELECT 2000
FROM RPTNEED, RCRAPP1
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT <= 5000
AND RCRAPP1_STAT_CODE = ‘IL’
AND RCRAPP1_AIDY_CODE = RPTNEED_AIDY_CODE
AND RCRAPP1_PIDM = RPTNEED_PIDM
AND RCRAPP1_CURR_REC_IND = ‘Y’
January 2009
Financial Aid 8.3
User Guide
Processing
2-239
Field
Value
Rule
STATE_CALC_2
Sequence
2
SQL Statement
SELECT 1000
FROM RPTNEED, RCRAPP1
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_FM_EFC_AMT <= 5000
AND RCRAPP1_STAT_CODE <> ‘IL’
AND RCRAPP1_AIDY_CODE = RPTNEED_AIDY_CODE
AND RCRAPP1_PIDM = RPTNEED_PIDM
AND RCRAPP1_CURR_REC_IND = ‘Y’
Example 9 - Calculate an Equity Packaging Amount Based
on Both Gross Need and Budget
The preceding examples are all rules that might be defined for use on the Packaging Group
Fund Rules form (RPRGFND) to calculate award amounts for individual funds.You can
also define rules which you can use on the Default Packaging Rules form (RPRDEFR) and
the Packaging Rules form (RPRPCKR) to give additional flexibility in defining GAP,
Equity, and Self-Service amounts. In the past, you could only define fixed Amounts,
Percent of Budget, or Percent of Gross Need on those forms. You can now use an
algorithmic rule for more complex calculations as in the following example.
If this rule was used on RPRPCKR, the equity level for the packaging group would be as
follows: 50% of FM gross need if FM gross need was greater than $5000 and the budget
$10000 or greater; 40% of FM gross need if FM gross need was greater than $5000 and
the budget was less $10000; 30% of FM gross need if FM gross need was $5000 or less
and the budget was greater than $10000; 20% of FM gross need if FM gross need was
$5000 or less and the budget was $10000 or less. This would set the overall equity level
for the student in a particular packaging group so any equity funds defined on RPRGFND
would not exceed these totals. Also, in this example, if the institution has used an
algorithmic rule on RPRGFND for one of the equity funds, the rule on RPRPCKR is
processed first then any rules on RPRGFND are processed.
2-240
Financial Aid 8.3
User Guide
Processing
January 2009
Field
Value
Rule
EQUITY_CALC
Sequence
1
SQL Statement
SELECT .50 * RPTNEED_GROSS_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_GROSS_NEED_AMT > 5000
AND RPTNEED_BUDGET_AMOUNT > 10000
Field
Value
Rule
EQUITY_CALC
Sequence
2
SQL Statement
SELECT .40 * RPTNEED_GROSS_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_GROSS_NEED_AMT > 5000
AND RPTNEED_BUDGET_AMOUNT <= 10000
Field
Value
Rule
EQUITY_CALC
Sequence
3
SQL Statement
SELECT .30 * RPTNEED_GROSS_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_GROSS_NEED_AMT <= 5000
AND RPTNEED_BUDGET_AMOUNT > 10000
January 2009
Financial Aid 8.3
User Guide
Processing
2-241
Field
Value
Rule
EQUITY_CALC
Sequence
4
SQL Statement
SELECT .20 * RPTNEED_GROSS_NEED_AMT
FROM RPTNEED
WHERE RPTNEED_AIDY_CODE = :AIDY
AND RPTNEED_PIDM = :PIDM
AND RPTNEED_GROSS_NEED_AMT <= 5000
AND RPTNEED_BUDGET_AMOUNT <= 10000
Columns Defined on the Temporary Packaging Need
Table (RPTNEED)
The Temporary Packaging Table (RPTNEED) is populated for a financial aid recipient by
the Packaging Process (RPEPCKG) prior to packaging the student. Any row created on
this table is inserted for a student, used, and then deleted. The table is also populated when
you use the Test Rule button on the Algorithmic Packaging Rules form (RPRALGR).
Column Name
Comment
RPTNEED_AIDY_CODE
AID YEAR CODE: The aid year associated with the need
data.
RPTNEED_PIDM
PIDM: The internal system generated student
identification number.
RPTNEED_SIMULATE_SW
SIMULATE SWITCH: Indicates whether or not this row
was created during simulated packaging.
(See note below regarding
this column)
2-242
RPTNEED_BUDGET_AMOUNT
BUDGET AMOUNT: The amount of the student’s cost of
attendance.
RPTNEED_RESOURCE_AMOUNT
RESOURCE AMOUNT: The total amount of outside
resources used in the applicant’s need calculation.
RPTNEED_REPLACE_EFC_AMT
REPLACE EFC AMOUNT: The total amount of the
student’s awards used to replace the expected family
contribution.
RPTNEED_REDUCE_NEED_AMT
REDUCE NEED AMOUNT: The total amount of the
student’s awards used towards gross need.
Financial Aid 8.3
User Guide
Processing
January 2009
Column Name
Comment
RPTNEED_EFC_IND
EFC INDICATOR: The expected family contribution
(EFC) to be used in the calculation of need. An “F”
indicates FM EFC will be used. An “I” indicates IM EFC
will be used.
RPTNEED_EFC_AMT
EXPECTED FAMILY CONTRIBUTION: The student’s
most recently calculated expected family contribution
(EFC).
RPTNEED_FM_EFC_AMT
FM EXPECTED FAMILY CONTRIBUTION: The
student’s most recently calculated expected family
contribution (EFC) using federal methodology (FM).
RPTNEED_GROSS_NEED_AMT
GROSS NEED: The gross need of the applicant defined
as budget minus expected family contribution (EFC),
minus resources.
RPTNEED_EXCESS_EFC_AMT
EXCESS EFC: The total amount of the student’s awards
which are designated as replacing EFC but instead are
used to reduce need.
RPTNEED_UNMET_NEED_AMT
UNMET NEED: The student's unmet need which is the
gross need minus any awards.
RPTNEED_IM_EFC_AMT
IM EXPECTED FAMILY CONTRIBUTION: The
student’s most recently calculated expected family
contribution (EFC) using institutional methodology (IM).
RPTNEED_IM_GROSS_NEED_AMT
IM GROSS NEED: The gross need of the applicant
defined as budget minus IM expected family contribution
(EFC), minus resources.
RPTNEED_IM_UNMET_NEED_AMT
IM UNMET NEED: The student's unmet need which is
the IM gross need minus any awards.
RPTNEED_BEG_UNMET_NEED_AMT
UNMET NEED: The beginning value of the student's FM
unmet need when the packaging process is run.
RPTNEED_BEG_IM_UNMET_NEED_
AMT
IM UNMET NEED: The beginning value of the student's
IM unmet need when the packaging process is run.
January 2009
Financial Aid 8.3
User Guide
Processing
2-243
RPTNEED_SIMULATE_SW Column
The RPTNEED_SIMULATE_SW column is populated dynamically based on whether
RPEPCKG is run in A (Actual) or S (Simulated) mode. If run in A (Actual), the value is N.
If run in S (Simulated), the value is Y. When using functions, you can use the
RPTNEED_SIMULATE_SW so the packaging process can look at the RPRAWRD (permanent)
or RPTAWRD (temporary) tables.
The example below demonstrates how to utilize this column in a rule.
Select 1500 from RPTNEED
Where RPTNEED_AIDY_CODE = :aidy
and RPTNEED_PIDM = :pidm
and RPKALGR.F_GET_FUND_OFFER
(:AIDY,:PIDM,'PELL',RPTNEED_SIMULATE_SW) <4310
When RPEPCKG is run in A (Actual), the packaging process examines the permanent
tables to obtain the Pell value (this assumes that the Calculate Pell Award parameter is set
to Y or Pell has already been awarded).
When RPEPCKG is run in S (Simulated), the packaging process looks at the temporary
tables to obtain the Pell value (this also assumes that the Calculate Pell Award parameter is
set to Y).
Examples 3, 5 and 6 in the Sample Algorithmic Packaging Rules section also demonstrate
how this switch can be utilized in rules.
Warning
SunGard Higher Education recommends that you do not use
RPTNEED_SIMULATE_SW = 'Y' as a hard-coded value in a rule since
inaccurate results could occur if you are packaging in Actual Mode and
the temporary tables are not available, or have different values than that
„
which is in the permanent tables.
New Functions Defined in the rpkalgr Package
The following section lists the new functions defined in the rpkalgr package that you can
use in algorithmic packaging rules.
F_GET_FUND_OFFER
Function to calculate award offer amounts for an aid year, student, and fund code.
f_get_fund_offer
( p_aidy_code,
p_pidm,
p_fund_code,
p_simulate_sw)
2-244
Financial Aid 8.3
User Guide
Processing
January 2009
F_GET_FFID_OFFER
Function to calculate award offer amounts total for an aid year, student, and federal fund
ID.
f_get_ffid_offer
( p_aidy_code,
p_pidm,
p_fed_fund_id,
p_simulate_sw)
F_GET_PRIOR_YEAR_FUND_OFFER
Function to calculate prior year award offer amounts for an aid year, student, and fund
code. (The p_aidy_code value is the current year.)
f_get_prior_year_fund_offer
( p_aidy_code,
p_pidm,
p_fund_code)
F_GET_PRIOR_YEAR_FFID_OFFER
Function to calculate prior year award offer amounts total for an aid year, student, and
federal fund id.
f_get_prior_year_ffid_offer
( p_aidy_code,
p_pidm,
p_fed_fund_id)
January 2009
Financial Aid 8.3
User Guide
Processing
2-245
Scholarship and Athletics Processing by
Term
You can count scholarships by term and define how many terms a student can receive a
scholarship. Use the Scholarship Term Information form (RPASTRM) to view the
maximum terms, amount paid, loss of eligibility, and remaining terms of eligibility. This
form displays all terms for which the student received the scholarship.
Use the Donor/Scholarship Demographics form (RFADSCD) to provide you with a place
to capture the following donor and scholarship information.
Donor Information
• Donor ID and Name
• Reception Invite
• Anonymous
• Thank you letter
• Primary Donor
• Deceased
• Grades to donor
• Donor selects recipient
• Link to address, telephone, and
e-mail information
Scholarship Information
• Minimum enrollment
• Tuition waiver
• Multiple donors
• Scholarship source
• Restricted
• Maximum number of terms
You can auto-populate or manually enter specific student athlete data by term on the Sport
Aid by Term form (RAASPTM). In addition, use the Team Sport Term Aid form
(RAITMTM) to provide you with the ability to identify specific team sport information by
term.
Potential Athletic Grant Defaults (RAAPAGD)
Use this form to enter default award year values for potential athletic grant amounts. The
form is split up into two blocks. The first block allows you to enter potential athletic grant
default amounts for in-state and out-of-state athletes. The second block allows you to enter
sport-specific default amounts for in-state and out-of-state athletes. If a sport is defined in
the second block, then the appropriate default amount is used for the student on the Sport
Aid by Term (RAASPTM) form otherwise, the appropriate default amount from the first
block gets populated.
2-246
Financial Aid 8.3
User Guide
Processing
January 2009
Sport Aid by Term form(RAASPTM)
Use this form to view and enter student athletic aid information for a specific term.
Information on the Aid for Sport tab is a combination of manually entered and systempopulated data. Institutional award, outside award, resource and contract/exemption
information is populated when the Default Aid Values button is clicked.
Team Sport Term Aid (RAITMTM)
This form displays and totals, within sport and term, the Potential Athletic Grant - Year
amount, Athlete's Actual Grant - Term amount and percentage of the potential and
actual amount based on data from RAASPTM.
Donor/Scholarship Demographics (RFADSCD)
Use this form to view and enter donor and scholarship demographic information. The
Scholarship Demographics block allows you to identify specific information related to the
Scholarship and the Donor Demographics block allow you to identify specific Donor
information.
Scholarship Term Information (RPASTRM)
The Scholarship Term Information form (RPASTRM) form enables you to view
scholarship information for a student. The information on this form is obtained from
various sources. The Maximum comes from RFADSCD (Maximum Number of Terms),
the Paid amount comes from RPRATRM, the Loss of Eligibility number is manually
entered, and the Remaining number is a calculation of Maximum - Paid - Loss of
Eligibility.
Athletic Aid Type Validation (RTVAATP)
This validation form allows you to set up the Athletic Aid Types to be used on
RAASPTM, for example: Medical Release, Injured Reserve, Redshirt.
Financial Aid Sport Validation (RTVFASP)
This validation form allows you to designate Financial Aid sport codes to be used on
RAASPTM, as they may differ from what is used in Banner Student.
January 2009
Financial Aid 8.3
User Guide
Processing
2-247
Grades to Donor Validation (RTVGRDD)
This validation form allows you to designate specific categories of grades that a donor
wishes to receive, if any. For example, a donor may wish to receive grades only for the
freshmen students or only for students in a specific program.
Scholarship Source Validation (RTVSSRC)
This validation form allows you to designate the source of a scholarship, for example:
donor, gift, or institution.
Reviewed Validation (RTVREVW)
This validation form allows you to designate the review status of an athlete's institutional
award, outside award, resource, and/or contract or exemption. For example, you might use
this form to designate that the information for the fund, resource, and contract/exemption
has been reviewed and is complete.
Thank You Letter Validation (RTVTYLT)
This validation form allows you to designate specific categories of a thank you letter that a
donor wishes to receive, if any. For example, a donor may wish to receive a thank you
letter only from the freshmen students or only from students in a specific program.
Contract Rules (RPRCONT)
Use the Count for Athletics field on RPRCONT to indicate if a contract should be counted
for Athletic reporting purposes.
Exemption Rules (RPREXPT)
Use the Count for Athletics field on RPREXPT to indicate if the exemption should be
counted for Athletic reporting purposes.
Resource Code Validation (RTVARSC)
Use the Count for Athletics field on RTVARSC to indicate if the resource should be
counted for Athletic reporting purposes.
2-248
Financial Aid 8.3
User Guide
Processing
January 2009
Athletic Grant Term Roll Process (RAPAGRL)
Use this process to roll athletic grant term information on RAASPTM from one term to the
next.
Athletic Aid Discrepancy Report (RARATAD)
Use this report to display the discrepant information between the actual fund/resource
amounts and the reported amounts on RAASPTM. This report should be used to determine
if a student’s award information has been updated since this information was originally
reported to Athletics.
January 2009
Financial Aid 8.3
User Guide
Processing
2-249
2-250
Financial Aid 8.3
User Guide
Processing
January 2009
3
Applicant Processing
The Applicant Processing module contains the forms that you use on a regular basis for
the day-to-day processing of student financial aid information. All of the forms in this
module also exist in other modules in Banner Financial Aid.
Forms
The following forms can be found within the Applicant Processing module:
January 2009
Applicant Status
ROASTAT
Financial Aid Record Maintenance
ROARMAN
Need Analysis
RNANAxx
Need Analysis Processing
RNAPRxx
Need Analysis Document Verification
RNAVRxx
Student Loan Data System
RNASLxx
NSLDS Transfer Monitoring Application
RNATMNT
Need Analysis Result
RNARSxx
Applicant Requirements
RRAAREQ
Applicant Budget
RBAABUD
Award Maintenance
RPAAWRD
Applicant User Defined Data
ROAUSDF
Financial Aid Enrollment
ROAENRL
Applicant High School and Admission Data
ROAHSDT
Summary Academic History Inquiry
RSIHIST
Basic Student Information Inquiry
RSISTDN
Admissions Application Inquiry
RSIAPPL
Financial Aid 8.3
User Guide
Applicant Processing
3-1
Account Detail Review Inquiry
RSIAREV
Degrees and Other Formal Awards Inquiry
RSIDEGR
Housing Information Inquiry
RSIHOUS
Prior College Inquiry
RSIPCOL
High School Inquiry
RSIHSCH
Test Score Inquiry
RSITEST
Veteran Certification Inquiry
RSIVETN
Third Party Contract Inquiry
RSICONT
Billing Exemption Inquiry
RSIEXPT
Applicant Processing flow
• Applicant Status form (ROASTAT)
The Applicant Status form displays applicant information such as general financial
aid status information, satisfactory academic progress data, admissions status
information, financial need data, and award data.
• Financial Aid Record Maintenance form (ROARMAN)
The Financial Aid Record Maintenance form enables you to review and change
most of the important aspects of a student’s financial aid record from one central
form. Specifically, it displays and updates the following parts of a student’s record:
• award detail
• applicant processing status
• enrollment
status
• satisfactory academic progress
• admissions
status detail
• budget components
• other resources
• coded and non-coded tracking requirements
• Pell Grant status • need analysis information.
• Need Analysis form (RNANAxx)
You can view, enter, and maintain all core financial aid application information on
the Need Analysis form. The information on this form is specific to the aid year
and applicant. It is presented and stored in MDE independent format.
3-2
Financial Aid 8.3
User Guide
Applicant Processing
January 2009
• Need Analysis Processing form (RNAPRxx)
Use the Need Analysis Processing form to view and process both (Federal
Methodology) FM and (Institutional Methodology) IM calculations for a specified
aid year. The form allows you to view the data and process data changes for both
calculations, side-by-side. Once data is loaded and modified (if required), this form
can be used to calculate INAS and receive new need analysis results. RNAPRxx
maintains many of the characteristics of the Need Analysis form (RNANAxx),
including the ability to run INAS, add a need analysis record manually, and utilize
Pell Corrections functionality.
• Need Analysis Document Verification form (RNAVRxx)
Use the Need Analysis Document Verification form to verify the data that exists in
the student's application record with physical tax forms and other documents
submitted by the student. This form includes student application and verification
records, as well as parent application and verification data.
• Student Loan Data form (RNASLxx)
You can view and maintain National Student Loan Data System (NSLDS)
information on the Student Loan Data System form. Load the NSLDS data from
files received through the Electronic Data Exchange (EDE) process or from the
Applicant Data Reporting Service from the Department of Education.
• NSLDS Transfer Monitoring Application form (RNATMNT)
Use RNATMNT to enter the names of students who need to be added to or
removed from the NSLDS Monitoring List. Data entered on this form is used by
the Transfer Monitoring Extract Process (RNRTMNE) to create the Transfer
Monitoring School Inform File, which is sent to NSLDS.
• Need Analysis Result form (RNARSxx)
Use the Need Analysis Result form to view, enter, and edit the results of the
calculations of a student’s Federal Methodology (FM), Pell EFC, and Institutional
Methodology (IM) contributions. You can load the results from electronic
applications or you can manually enter the results. You can also change the results
to reflect professional judgement where permitted.
• Applicant Requirements form (RRAAREQ)
Use the Applicant Requirements form to assign tracking requirements to a financial
aid applicant for a specified aid year. A tracking group can be used to assign the
applicant to a general group of tracking requirements. You can also assign a set of
non-standard requirements to the applicant. The Promissory Notes section enables
you to prevent the disbursement of student loan funds to students who have not yet
signed their promissory note for the term.
• Applicant Budget form (RBAABUD)
Use the Applicant Budget form to assign a set of budget components to a financial
aid applicant for a specified aid year. You can also use RBAABUD to assign a
January 2009
Financial Aid 8.3
User Guide
Applicant Processing
3-3
budget group to a student and an aid period. The aid period defines the portion of
the aid year that the student will be in attendance.
• Award Maintenance form (RPAAWRD)
Refer to the Award Maintenance form to maintain packaging information for an
applicant.
• Applicant User Defined form (ROAUSDF)
Refer to the Applicant User Defined form to view the user-defined fields for an
applicant.
• Financial Aid Enrollment form (ROAENRL)
Use ROAENRL to maintain Banner Financial Aid hours and display Banner
Student hours.
• Applicant High School and Admission Data form (ROAHSDT)
Use ROAHSDT to enter the information necessary to establish high school
eligibility for the Academic Competitiveness Grant (ACG) and to record if the
student meets TEACH Grant eligibility requirements.
• Student System Shared Data menu
The Student System Shared Data module allows you to integrate Banner Student
with Financial Aid. This option permits you to view forms that contain information
concerning recruiting, admissions, registration, housing, accounts receivable, and
academic history.
3-4
Financial Aid 8.3
User Guide
Applicant Processing
January 2009
4
Need Analysis
In the Need Analysis module, the student’s financial need is calculated based on the
difference between the packaging budget and the Federal Methodology (FM) or the
Institutional Methodology (IM) budget calculations. You can define the methodology used
in the need analysis calculation. A transaction log maintains an online log of all changes.
Forms
The following forms are included within the Need Analysis module. For more information
about a specific form, select Help > Online Help from that form in Banner.
January 2009
Need Analysis
RNANAxx
Need Analysis Processing
RNAPRxx
Supplemental Need Analysis
RNASUxx
Need Analysis Result
RNARSxx
Applicant Override
RNAOVxx
Applicant Need Analysis Application Inquiry
RNIAPPL
Applicant Student Loan Data Inquiry
RNINSLD
Calculated Need Analysis Detail Inquiry
RNINAIQ
Miscellaneous Results Inquiry
RNIMSxx
Need Analysis Global Policy Options Rules
RNRGLxx
Applicant Status
ROASTAT
Applicant Pell Grant
ROAPELL
Need Analysis Document Verification
RNAVRxx
Financial Aid 8.3
User Guide
Need Analysis
4-1
Application Purge
RNAPURG
Student Loan Data System
RNASLxx
NSLDS Transfer Monitoring Application
RNATMNT
Need Analysis Online Recalculation
Process Flow Narrative
• Financial Aid Application Current Record
Each financial aid applicant may have multiple application records from different
sources, one of which will always be marked current. The current record is always
used for Need Analysis calculations, which are performed by the College
Scholarship Service (CSS) Institutional Need Analysis System (INAS).
• INAS Options
The CSS INAS default values are delivered from SunGard Higher Education. If
you would like to change these values, you can do so for all students on the INAS
Global Policy Options Rules form (RNRGLxx). In addition, overrides can be set
for individual students using the Applicant Override form (RNAOVxx).
• INAS Calculation
The calculation default mode setting is the long option, which initiates a complete
recalculation of all Need Analysis results, including interim results.
• Pell Calculation
A Pell Award calculation can be run after the INAS calculation is completed. The
Pell calculation determines the amount of the student's Pell award, checks the
validity of the award, and packages the award in the student's award package.
When running the Need Analysis Calculation (INAS) online from a form, the Pell
calculation will be called automatically under certain conditions. When running
INAS from Job Submission, the Pell calculation is not automatically run. Pell batch
calculations can be done by running the Pell Calculation Process (RPEPELL).
• INAS Results
INAS Results can be seen online on both the Need Analysis Result form
(RNARSxx) and the Calculated Need Analysis Detail Inquiry form (RNINAIQ). In
addition, the calculation produces a printed report.
4-2
Financial Aid 8.3
User Guide
Need Analysis
January 2009
5
Requirements Tracking
The Requirements Tracking module permits you to define an unlimited number of
documents or statuses that students need to submit or complete. These requirements
control whether a student is eligible to be packaged or receive a payment of aid. This
module provides you with the following features:
• Requirement Definition – defines an unlimited number of application requirements
• Grouping of Students – places students with similar characteristics into groups and
assigns the same requirements to all students in the same group
• Mass Entry – allows entry of information about multiple documents/requirements
for multiple students on one screen
• Letter Generation – provides the ability to print letters to students informing them
of the documents/requirements they need to submit or satisfy
Forms
The following forms are included within the Requirements Tracking module. For more
information about a specific form, select Help > Online Help from that form in Banner.
January 2009
Applicant Requirements
RRAAREQ
Financial Aid Record Maintenance
ROARMAN
Applicant Requirements Mass Entry
RRAMASS
Applicant Comments
RHACOMM
Applicant Immediate Process
ROAIMMP
Financial Aid Selection Rules
RORRULE
Requirements Tracking Group/Requirements Rules
RRRGREQ
Message Rules
RORMESG
Group Inquiry
ROIGRPI
Financial Aid 8.3
User Guide
Requirements Tracking
5-1
Requirements Tracking Validation
RTVTREQ
Requirements Tracking Group Validation
RTVTGRP
Requirements Tracking Status Validation
RTVTRST
Requirements Tracking Process Flow
Narrative
• Financial Aid Application Current Record
Each financial aid applicant may have multiple application records from different
sources, one of which will always be marked current. Data in the current record is
used to determine whether additional documents need to be supplied by the
applicant.
• Create Applicant Requirement Records
Applicant requirement records can be established in several ways. When applicants
are loaded into Banner Financial Aid through data load, they are usually also run
through the Requirements Tracking Batch Group Assignment Process.
This process places the applicants into Requirements Tracking groups according to
user-defined criteria. Each group has a set of requirements associated with it, which
are then assigned to each applicant that falls into the group. Applicants can also be
individually assigned to Requirements Tracking groups online, either manually or
automatically. Individual requirements can be manually assigned to applicants
online as well.
• Requirement Tracking Group Codes and Rules
The Financial Aid Office establishes the Requirement Tracking Group codes and
rules that associate specific groups with specific sets of tracking components.
• Applicant Requirement Records
Applicant Requirement Records contain information about outstanding and
satisfied requirements, including the date the requirement was established, the last
date and action taken against the requirement, whether the requirement is required
by the Packaging, Disbursement and/or Memo processes, and the fund code of a
specific fund to which the requirement is linked.
• Additional Documents Required
The Financial Aid office establishes policies regarding which additional documents
are required from certain applicants. The rules governing which applicants are
assigned requirements are set up online, and users can monitor an applicant's
progress toward fulfilling these requirements at any time.
5-2
Financial Aid 8.3
User Guide
Requirements Tracking
January 2009
• Other Processes Can Proceed
Requirements are categorized as necessary for certain processing in three specific
functional areas: Packaging, Memoing, and Disbursement. When all requirements
that are mandatory in one of the functional areas have been met, processing in that
area can proceed.
• Send Requirements Tracking Letters to Applicants
After applicants have been assigned requirements, the Financial Aid office sends
letters to each applicant with unsatisfied requirements, advising them that certain
documents need to be supplied. These letters can be created through the Letter
Generation portion of Banner.
• Applicant Documents
After being notified of the request for documents, applicants send those documents
to the Financial Aid office.
• Post Satisfied Requirements
Receipt of the documents from applicants is entered online. The status of the
requirement is changed to satisfied, if the requirement has been properly met.
January 2009
Financial Aid 8.3
User Guide
Requirements Tracking
5-3
5-4
Financial Aid 8.3
User Guide
Requirements Tracking
January 2009
6
Budgeting
The Budgeting module calculates and assigns cost of attendance values to each applicant
based on budget types established by the institution (for example, tuition, fees, room and
board, etc.). This module provides you with the following features:
• Budget Component Assignment – assigns a pre-defined set of budget categories
(components) and values to students according to their budget group
• Budget Averaging – creates a budget which is a weighted average of two or more
budgets
• Multiple Budgets – assigns a Pell Budget plus one additional budget
• Transaction Log – maintains an online log of all budget changes
Forms
The following forms can be found within the Budgeting module. For more information
about a specific form, select Help > Online Help from that form in Banner.
January 2009
Applicant Budget
RBAABUD
Financial Aid Record Maintenance
ROARMAN
Applicant Comments
RHACOMM
Applicant Immediate Process
ROAIMMP
Budget Component Rules
RBRCOMP
Financial Aid Selection Rules
RORRULE
Budget Group/Type Rules
RBRGTYP
Message Rules
RORMESG
Budget Inquiry
RBIBUDG
Group Inquiry
ROIGRPI
Budget Group Validation
RTVBGRP
Financial Aid 8.3
User Guide
Budgeting
6-1
Budget Type Validation
RTVBTYP
Budget Component Validation
RTVCOMP
Aid Period/Term Rules
RORTPRD
Aid Period Validation
RTVAPRD
Budgeting Process Flow Narrative
• Financial Aid Application Current Record
Each financial aid applicant may have multiple application records from different
sources, one of which will always be marked current. Data in the current record is
used to determine the budget that is assigned to an applicant.
• Create Applicant Budget Records
Applicant Budget records can be established in several ways. When applicants are
loaded into Banner Financial Aid through data load, they are usually also run
through the Budgeting Batch Group Assignment Process.
This process places the applicants into Budgeting groups according to user-defined
criteria. Each group has a set of budget components associated with it, which are
then assigned to each applicant that falls into the group. Applicants can also be
individually assigned to Budgeting groups online, either manually or automatically.
Individual budget components can be manually assigned to applicants online as
well.
• Budget Components
Budget Components are the individual line items for which the Financial Aid office
establishes costs. Examples of budget components are tuition, books and supplies,
and commuting costs.
• Budgeting Group Codes and Rules
The Financial Aid Office establishes the Budgeting Group codes and rules that
associate specific groups with specific sets of budget components.
• Applicant Budgets
Applicant Budgets reflect the approximate costs that an applicant will incur by
attending the institution. These costs are different for different categories of
students - on-campus vs. off-campus, graduate vs. undergraduate, and so on. An
individual applicant can have at most two different budgets – one for Pell Grants
and a second for non-Pell programs.
6-2
Financial Aid 8.3
User Guide
Budgeting
January 2009
• Other Financial Aid Processes
Other functional areas within Banner use the applicant budgets developed within
the Budgeting module to determine the financial need that an applicant has, and the
appropriate aid that will meet that need.
• Budget Information Can be Included in Award Letters to Applicants
Letters that are sent to applicants detailing their financial aid awards can optionally
include a section dealing with the applicants' budgets, which are drawn from this
module. These letters can be created through the Letter Generation portion of
Banner.
January 2009
Financial Aid 8.3
User Guide
Budgeting
6-3
6-4
Financial Aid 8.3
User Guide
Budgeting
January 2009
7
Packaging and
Disbursement
The Packaging and Disbursement module provides a flexible automatic packaging
function that allows an unlimited number of ways individual or groups of applicants may
be packaged. The following processes are included in the Packaging and Disbursement
module:
• User-Defined Packaging – permits applicants to be assigned into an unlimited
number of packaging groups, which have a unique set of user-defined packaging
formulas
• Simulated Packaging – permits you to design and run what-if packaging analysis
• Letter Generation – allows you to produce an unlimited number of different types
of award letters
• Transaction Log – maintains an online log of all packaging changes
Forms
The following forms are included within the Packaging and Disbursement module. For
more information about a specific form, select Help > Online Help from that form in
Banner.
January 2009
Packaging Maintenance
RPAAPMT
Award Maintenance
RPAAWRD
Scholarship Term Information
RPASTRM
Financial Aid Record Maintenance
ROARMAN
Fund Award Inquiry
RPIFAWD
Fund Award Term Inquiry
RPIFTERM
Award Acceptance Mass Entry
RPAMACC
Award Offer Mass Entry
RPAMOFF
Resource Maintenance
RPAARSC
Financial Aid 8.3
User Guide
Packaging and Disbursement
7-1
7-2
Applicant High School and Admission Data
ROAHSDT
Applicant Comments
RHACOMM
Applicant Immediate Process
ROAIMMP
Contracts and Exemptions Payment Inquiry
RPIARPY
Applicant Award by Term
RPIATRM
Disbursement Results
ROIDISB
Financial Aid Selection Rules
RORRULE
Algorithmic Packaging Rules
RPRALGR
Financial Aid CIP Code Rules
RPICIPC
State Advanced/Honors Program Codes
RPISAHP
Packaging Group Fund Rules
RPRGFND
Default Packaging Rules
RPRDEFR
Packaging Rules
RPRPCKR
Exemption Rules
RPREXPT
Third Party Contract Rules
RPRCONT
Packaging Options
RPROPTS
Audit Grading Mode
RPRAUDT
Packaging Group Fund Source Maximums Rules
RPRFSRC
Packaging Group Fund Category Maximums Rules
RPRFCAT
Group Inquiry
ROIGRPI
Financial Aid Degree Rules
RPRDEGR
Financial Aid Major Rules
RPRMAJR
Algorithmic Packaging Rule Code Validation
RTVALGR
Award Status Validation
RTVAWST
Financial Aid 8.3
User Guide
Packaging and Disbursement
January 2009
Fund Category Validation
RTVFCAT
Packaging Group Validation
RTVPGRP
Resource Code Validation
RTVARSC
Packaging Process Flow Narrative
• Financial Aid Application Current Record
Each financial aid applicant may have multiple application records from different
sources, one of which will always be marked current. Data in the current Record
can be used to determine the budget that is assigned to an applicant.
• Assign Applicants to Packaging Groups (required if using automated
packaging)
Applicants can be assigned to Packaging groups in several ways. When applicants
are loaded into Banner through data load, they are usually also run through the
Packaging Batch Group Assignment Process. This process places the applicants
into Packaging groups according to user-defined criteria. Applicants can also be
individually assigned to Packaging groups online, either manually or automatically.
• Packaging Group Codes and Rules
The Financial Aid Office establishes the Packaging group codes and rules that
associate specific groups with specific sets of packaging components.
• Packaging and Fund Rules
Packaging and Fund rules define how and when awards to applicants will be made.
These rules include awarding rules, funds management rules, gap equity and selfhelp packaging rules, and exemption and third-party contract rules.
• Applicant Budgets
The Packaging process uses the applicant budgets, in conjunction with the Need
Analysis results, to determine the financial need that an applicant has and the
appropriate aid that will meet that need.
• Need Analysis Results Record
Packaging uses the Expected Family Contribution, in conjunction with the
applicant’s budget, to determine the contribution an applicant and family can make
toward meeting financial need.
• Packaging Process
The Packaging process determines an award package for each applicant based on
rules within the Packaging module, data from other modules within Financial Aid
(unsatisfied requirements, packaging holds, and so on), and federal financial aid
rules.
January 2009
Financial Aid 8.3
User Guide
Packaging and Disbursement
7-3
• Applicant Award Package
The Applicant Award Package consists of award amounts from various funds and a
schedule of when the amounts will be disbursed.
• Additional Need
If, after the automatic Packaging process is performed, additional need remains for
an applicant, manual packaging can be performed to attempt to meet the need.
• Manual Packaging
Manual packaging can be performed online at any time for an applicant (that is,
before or after automatic packaging).
• Send Award Letters
Send Award Letters to applicants after determination of partial or final awards. In
addition to financial aid awards, Award Letters can optionally contain other
messages related to the budget or awards.
• Post Applicant Acceptance/Rejection
Applicant responses to award letters can be updated manually online.
7-4
Financial Aid 8.3
User Guide
Packaging and Disbursement
January 2009
8
Athletics
Use the Athletics module to maintain scholarship and donor information. Through this
module, you have the ability to
• Set up and track scholarship information by term.
• Enter default potential values for grants by Sport Code.
• Maintain donor and scholarship demographic information.
• Select specific types of thank you notes donors will receive.
• Select specific groups whose grades will be reported to donors.
Forms
The following forms can be found within the Athletics module. For more information
about a specific form, select Help > Online Help from that form in Banner.
Potential Athletic Grant Defaults
(RAAPAGD)
Use RAAPAGD to enter the default athletic grant
award amounts for the aid year. Through
RAAPAGD, you can enter general default amounts
for athletic grants for both in-state and out-of-state
athletes, and you can also enter default amounts for
in-state and out-of-state athletes by Sport Code.
Sport Aid by Term (RAASPTM)
Use RAASPTM to view and enter student athletic
aid information for a specific term. You can use the
Default Aid Values button to populate the data
under the following tabs: Institutional Award,
Outside Award, Resources, and Contracts and
Exemptions.
Team Sport Term Aid
(RAITMTM)
Use RAITMTM to view by sport the total amount of
a grant that has been awarded in a term. RAITMTM
also displays the detail of how the grant was
awarded. This information is based upon the data on
RAASPTM.
Donor/Scholarship Demographics
(RFADSCD)
Use RFADSCD to enter donor and scholarship
demographic information.
January 2009
Financial Aid 8.3
User Guide
Athletics
8-1
Scholarship Term Information
(RPASTRM)
Use RPASTRM to view scholarship information for
a student by term.
Athletic Aid Type Validation
(RTVAATP)
Use RTVAATP to set up the Athletic Aid Types to be
used on RAASPTM.
Financial Aid Sport Validation
(RTVFASP)
Use RTVFASP to designate the Financial Aid Sport
Codes to be used on RAASPTM. This is necessary,
because Financial Aid Sport Codes may differ from
what is used in Banner Student.
Grades to Donor Validation
(RTVGRDD)
If a donor wishes to receive grade reports on specific
groups, use RTVGRDD to designate those groups.
Scholarship Source Validation
(RTVSSRC)
This validation form allows you to designate the
source of a scholarship, for example: donor, gift, or
institution.
Reviewed Validation (RTVREVW)
Thank You Letter Validation
(RTVTYLT)
This validation form allows you to designate
the review status of an athlete's institutional
award, outside award, resource, and/or contract
or exemption. For example, you might use this
form to designate that the information for the
fund, resource, and contract/exemption has
been reviewed and is complete.
If a donor only wishes to receive certain types of
thank you letters, use RTVTYLT to designate the
thank you letter types.
Athletic Grant Term Roll Process (RAPAGRL)
Use this process to roll athletic grant term information on RAASPTM from one term to the
next.
Athletic Aid Discrepancy Report (RARATAD)
Use this report to display the discrepant information between the actual fund/resource
amounts and the reported amounts on RAASPTM. This report should be used to determine
if a student’s award information has been updated since this information was originally
reported to Athletics.
Contract Rules (RPRCONT)
8-2
Financial Aid 8.3
User Guide
Athletics
January 2009
Use the Count for Athletics field on RPRCONT to indicate if a contract should be counted
for Athletic reporting purposes.
Exemption Rules (RPREXPT)
Use the Count for Athletics field on RPREXPT to indicate if the exemption should be
counted for Athletic reporting purposes.
Resource Code Validation (RTVARSC)
Use the Count for Athletics field on RTVARSC to indicate if the resource should be
counted for Athletic reporting purposes.
January 2009
Financial Aid 8.3
User Guide
Athletics
8-3
8-4
Financial Aid 8.3
User Guide
Athletics
January 2009
9
Funds Management
The Funds Management module defines and monitors an unlimited number of funds, fund
types, and fund associated eligibility rules for purposes of awarding and disbursing
financial aid. This module provides you with the following features:
• Applicant Requirements – allows application requirements to be associated with
individual funds assigned to the student’s tracking record when the fund is
packaged
• Fund Messages – permits messages that are unique to a specific fund to be printed
in the award letter
Forms
The following forms are included within the Funds Management module. For more
information about a specific form, select Help > Online Help from that form in Banner.
January 2009
Fund Management
RFRMGMT
Funds Management
ROAMGMT
Fund Budget Inquiry
RFIBUDG
Federal Fund ID Inquiry
RFIFFID
Federal Rules Inquiry
RPIFEDR
Default Award and Disbursement Schedule Rules
RFRDEFA
Fund Award and Disbursement Schedule Rules
RFRASCH
Financial Aid Selection Rules
RORRULE
Fund Base Data
RFRBASE
Donor and Scholarship Demographics
RFADSCD
Fund Source Code Validation
RTVFSRC
Financial Aid Fund Type Validation
RTVFTYP
Financial Aid 8.3
User Guide
Funds Management
9-1
Grades to Donor Validation
RTVFTYP
Reviewed Validation
RTVREVW
Scholarship Source Validation
RTVSSRC
Thank You Letter Validation
RTVTYLT
Funds Management Process Flow
Narrative
• Define Basic Fund Data
Basic fund data includes fund type, funding source, and other fund information
which is established by the Financial Aid Office on the Financial Aid Fund Type
Validation form (RTVFTYP), the Fund Source Code Validation form (RTVFSRC),
and the Fund Source Data form (RFRBASE).
• Standard Award & Disbursement Schedules
Standard awarding and disbursement schedules for each aid period are set up on the
Default Award and Disbursement Schedule Rules form (RFRDEFA).
• Create Fund Aid Year-Specific Data
Aid Year-specific fund records contain information about monies available to be
awarded, packaging options, disbursement options, messages, and comments. This
is defined on the Fund Base Data form (RFRBASE).
• Standard Award Schedule
The Financial Aid Office ascertains whether the standard award schedule is
applicable to the fund for any aid period.
• Create Fund-Specific Award Schedule
If the standard award schedule is not applicable to the fund for any specific aid
period, a customized fund award schedule is created on the Fund Award and
Disbursement Schedule Rules form (RFRASCH).
• Standard Disbursement Schedule
The Financial Aid Office ascertains whether the standard disbursement schedule is
applicable to the fund and aid period.
• Create Fund-Specific Disbursement Schedule
If the standard disbursement schedule is not applicable to the fund for any specific
aid period, a customized fund disbursement schedule is created on the Fund Award
and Disbursement Schedule Rules form (RFRASCH).
9-2
Financial Aid 8.3
User Guide
Funds Management
January 2009
• Create Fund Awarding Rules (optional)
Awarding rules specific to the fund are created on the Financial Aid Selection
Rules form (RORRULE).
• Packaging Process
The rules established in the Funds Management are used extensively in the
Packaging process.
• (Optional) Create Fund Disbursement Rules
Disbursement rules specific to the fund are created on the Financial Aid Selection
Rules form (RORRULE).
January 2009
Financial Aid 8.3
User Guide
Funds Management
9-3
9-4
Financial Aid 8.3
User Guide
Funds Management
January 2009
10
Electronic Data Exchange
The Electronic Data Exchange module enables you to perform the following functions:
• Applicant Record Creation – Load ISIRs into the Banner Financial Aid System
• Online Need Analysis – Use online need analysis verification forms to log data
changes to an applicant's record.
• ISIR Correction/Request Processing – Create data files for transfer to the Central
Processor.
• COD Processing – Creates data files for transfer to COD using information from
the Banner Financial Aid database.
• Data File Generation – Send data files generated by Banner Financial Aid to the
EDE Central Processor.
Forms
The following forms can be found within the Electronic Data Exchange module. For more
information about a specific form, select Help > Online Help from that form in Banner.
January 2009
ISIR Correction/Request
REACORR
Batch Control
RPIBATC
COD Document Control
REICODD
Miscellaneous Results Inquiry
RNIMSxx
Rejection Code Validation
RTVRJCT
Summary Statement of Account Inquiry
REISSOA
Detail Statement of Account Inquiry
REIDSOA
Data Request Record
RERRDRQ
Multiple Reporting Record Inquiry
REIRMRR
COD Year to Date Grant Summary
REIYTDS
NSLDS Transfer Monitoring Application
RNATMNT
Financial Aid 8.3
User Guide
Electronic Data Exchange
10-1
COD Identifier
REASTID
Financial Aid CIP Code Rules
RPICIPC
State Advanced/Honors Program Codes
RPISAHP
Electronic Data Exchange Process Flow
Narrative
• Student Signs ISIR or Initiates Corrections
The student signs the electronic SAR (ISIR) and returns it to the school. Or, the
student initiates the corrections and sends the information directly to the Central
Processor.
• Process the ISIR through Banner and Create a Corrections Batch
• Ensure that rules for EDE Correction logging are established.
• Make the necessary data changes on the RNANAxx form.
• Run the Need Analysis Logging Process (RLRLOGG) to move the data from
the temporary log tables to the permanent log tables.
• Run the EDE Correction/ISIR Request File Creation Process (REBCDxx) to
extract the corrections and to create the data file. The flat file consists of
EDE corrections and requests for ISIRs.
• Transfer the data file from Banner to your PC. You must download the data
file to a PC in order to transmit the information electronically to the CPS
through EdConnect.
• School using Federal SAIG Network
The school uses the SAIG Network to load revised ISIRs.
• Central Processor
The Central Processor responds to ISIR requests and transmits corrected ISIRs for
the students after successfully processing your corrections. If the CPS rejects an
ISIR Request, it will return the transaction to you, along with codes indicating the
reason for the rejection.
• Create EDE Files
Change the name of the ISIR file to xxxxesar.tap and load the ISIR file to the
correct Banner directory so that it can be processed by the programs that will load
the data in the Financial Aid database.
10-2
Financial Aid 8.3
User Guide
Electronic Data Exchange
January 2009
• FILECAT on PC (optional)
Use the File Concatenation Process (FILECAT) to combine multiple ISIR files into
one file for uploading to Banner.
• Banner Data Load Process
Run the Data Load process to load financial aid applicant records into Banner from
external sources.
• Create FAFSA/NSLDS Record
An NSLDS record is created for each student for whom a record is received on the
ISIR. In addition, a selected group of students can be selected using the NSLDS
population selection option in the dataload process.
• Create Revised ISIR Record
In addition to the current EDE record, an ISIR record, which cannot be changed, is
created in the database. The ISIR record is the official notification, delivered by
EDE, to the school about students’ Expected Family Contribution (EFC) and
eligibility for Federal Aid.
• Print Revised ISIR (optional)
You can print valid ISIR records directly from Banner.
January 2009
Financial Aid 8.3
User Guide
Electronic Data Exchange
10-3
10-4
Financial Aid 8.3
User Guide
Electronic Data Exchange
January 2009
11
History and Transcripts
The History and Transcripts module maintains student financial aid records online for use
in packaging, financial aid transcript generation, and audit functions. This module
provides you with the following features:
• Online Transcript Request – produces Federally-required transcripts for students in
NASFAA standard format
• Prior College & Institutional History – allows unlimited entry of transcript data
received from other institutions
Forms
The following forms are included within the History and Transcripts module. For more
information about a specific form, select Help > Online Help from that form in Banner.
NSLDS Transfer Monitoring Application
RNATMNT
Transcript Rules
RHRTRNS
Pre-Banner Award Summary
RHAPBAW
Prior Institution Transcript
RHAPTRN
Fund Sequence History Inquiry
RHIAFSH
Applicant Comments
RHACOMM
Transcript Information
RHATINF
Financial Aid Transcript Request
RHARQST
Tip
Student Financial Aid history may also be viewed on the Student Loan
„
Data System form (RNASLxx).
January 2009
Financial Aid 8.3
User Guide
History and Transcripts
11-1
History and Transcripts Process Flow
• Create Transcript Rules
Transcript rules define which of the institution's funds appears on financial aid
transcripts.
• Enter Transcript Information
Non-loan and non-award information that will be printed on financial aid
transcripts is entered online.
• Enter/Convert Pre-Banner Award Summary Data
Historical data that exists in any pre-Banner Financial Aid that is needed for
printing on financial aid transcripts should either be run through a conversion
process, or entered manually online.
• Request Transcript from Prior Institution
For applicants who have attended prior post-secondary institutions, financial aid
transcripts must be requested to ascertain their continuing eligibility for certain
awards.
• Prior Institution Transcript Data
Data from prior institution's transcripts is entered online and should also be updated
in the Requirements Tracking module, if financial aid transcripts are tracked as
requirements.
• Enter Applicant Comments
Free-form applicant comments are maintained in the History module.
11-2
Financial Aid 8.3
User Guide
History and Transcripts
January 2009
12
Financial Aid Common
Functions
The Financial Aid Common Functions module maintains frequently used financial aid
functions. This module provides you with the following features:
• Data Management – allows the entry of rules to control the loading of student and
financial aid records into the database from external sources
• Common Function Controls – includes features such as: processing additional Pell
Grants, establishing and maintaining financial aid record holds, displaying student
summary information, creating and maintaining user-defined fields, displaying the
management audit log, setting institutional options
• Form Call Sequencing – Allows the definition and execution of a series of
functions in a predefined order
Forms
The following forms are included within the Financial Aid Common Functions module.
For more information about a specific form, select Help > Online Help from that form in
Banner.
January 2009
General Person Identification
SPAIDEN
Person Name/ID Search
ROAIDEN
FISAP Person Maintenance
ROAFSAP
Aid Year Inquiry
ROIAIDY
Group Inquiry
ROIGRPI
Data Log Inquiry
ROIILOG
Logging Activity Inquiry
ROILOGA
Message Code Inquiry
ROIMESG
SAR ID Inquiry
ROISARI
Financial Aid Term Code Inquiry
ROITERM
Financial Aid 8.3
User Guide
Financial Aid Common Functions
12-1
12-2
Financial Aid Record Maintenance
ROARMAN
Applicant Status
ROASTAT
Applicant Pell Grant
ROAPELL
Applicant Non Year User-Defined Data
ROANYUD
Applicant User-Defined Data
ROAUSDF
Applicant Holds
ROAHOLD
Applicant Data Log Inquiry
ROIALOG
Applicant Data Log Application
ROAALOG
Applicant Immediate Process
ROAIMMP
Applicant Comments
RHACOMM
Applicant Summary
ROASMRY
Applicant Messages
ROAMESG
Applicant High School and Admission Data
ROAHSDT
Financial Aid Enrollment
ROAENRL
Applicant Status Inquiry
ROIASIQ
Applicant Mail
RUAMAIL
Global Institution Financial Aid Options
ROAINST
U.S. Specific Institution Financial Aid Options
ROAUSIO
Section Unavailable for Aid
ROASECT
Logging Control
ROALOGC
Miscellaneous Validation Rules Inquiry
ROIMVAL
Data Log Rules
RORDATA
Supplemental Log Data Rules
RORDSUP
Message Rules
RORMESG
Batch Posting Rules
RORPOST
SAP Translation Rules
RORSTRF
Financial Aid 8.3
User Guide
Financial Aid Common Functions
January 2009
Aid Period/Term Rules
RORTPRD
Aid Period Validation
RTVAPRD
Comment Category Code Validation
RTVCCOM
Hold Type Validation
RTVHOLD
ISIR Comment Code Validation
RTVICMT
Message Code Validation
RTVMESG
Batch Posting Type Indicator Validation
RTVPTYP
Rejection Code Validation
RTVRJCT
Satisfactory Academic Progress Validation
RTVSAPR
Non Year User-Defined Variables Description
RORNYVD
User-Defined Variables Description
RORUSER
E-Mail Letter Rules
RORELTR
E-Mail Letter Format Rules
RORELTF
E-Mail Letter Module Validation
RTVELTM
Financial Aid Suspended Records Maintenance
RCRSUSP
Data Source Rules
RCRDTSR
Interface Data Translation Rules
RCRTPTR
Data Source Code Validation
RTVINFC
Common Functions Process Flow
Narrative
Common Functions tables, forms, reports and batch processes are utilized by all other
Financial Aid modules. Common Functions support other modules' processes, but don't
clearly fit into any one other module.
Examples of Common Functions tables are the Applicant Status Table (RORSTAT), which
is the base table in which applicant data is stored; the Regular Pell Grant Schedule Table
(RORPELL), which contains a matrix of values used in Pell Grant award and
January 2009
Financial Aid 8.3
User Guide
Financial Aid Common Functions
12-3
disbursement calculations; and the Applicant Satisfactory Academic Progress Table
(RORSAPR), which details applicants' academic progress.
12-4
Financial Aid 8.3
User Guide
Financial Aid Common Functions
January 2009
13
Student System Shared
Data
The Student System Shared Data module integrates Banner Student with Financial Aid.
This option permits you to view information in the following modules:
• Recruiting
• Admissions
• Registration
• Housing
• Accounts Receivable
• Academic History
Forms
The following forms are included within the Student System Shared Data module. For
more information about a specific form, select Help > Online Help from that form in
Banner.
January 2009
Summary Academic History Inquiry
RSIHIST
Basic Student Information Inquiry
RSISTDN
Admissions Application Inquiry
RSIAPPL
Account Detail Review Inquiry
RSIAREV
Degrees and Other Formal Awards Inquiry
RSIDEGR
Housing Information Inquiry
RSIHOUS
Prior College Inquiry
RSIPCOL
High School Inquiry
RSIHSCH
Test Score Inquiry
RSITEST
Financial Aid 8.3
User Guide
Student System Shared Data
13-1
Veteran Certification Inquiry
RSIVETN
Third Party Contract Inquiry
RSICONT
Billing Exemption Inquiry
RSIEXPT
Student System Shared Data Process
Flow Narrative
Through the Student System Shared Data module, Banner Student data is shared with the
Financial Aid system. This module consists of inquiry-only forms that contain information
that the Financial Aid system requires for processing.
This data is available through these shared views, instead of through direct access in order
to enable institutions that use Banner Financial Aid as a standalone product to access the
data from their Student Systems.
13-2
Financial Aid 8.3
User Guide
Student System Shared Data
January 2009
14
Short-Term Credit
The Short-Term Credit module allows you to build history files on a student’s short period
loans.
Forms
The following forms are included within the Short-Term Credit module. For more
information about a specific form, select Help > Online Help from that form in Banner.
Short-Term Credit Detail
RPASTCD
Short-Term Account Maintenance
RPRSTAM
Short-Term Credit Inquiry
RPISTCI
Certification Initials Validation
RTVCINT
Repayment Source Validation
RTVRPSR
Short-Term Credit Process Flow Narrative
• Short-Term Credit Account
Short-Term Credit Accounts are established online, and include such data as
budgeted loan amounts, amounts requested, approved and repaid, and account
comments.
• Short-Term Credit Request
Short-Term Credit Requests are recorded by student ID, and include such data as
amounts requested, approved and repaid, repayment source, and comments.
• Determine Loan Eligibility
After Short-Term Credit has been requested, the Financial Aid Office must
determine whether the applicant is eligible for the loan.
• Student Receives Short-Term Credit
Once the Financial Aid Office has determined the eligibility of the applicant and
the loan amount, this information is recorded online.
January 2009
Financial Aid 8.3
User Guide
Short-Term CreditFinancial Aid
14-1
• Student Repays Short-Term Credit
Data is maintained regarding how and when the student repays the short-term loan.
14-2
Financial Aid 8.3
User Guide
Short-Term CreditFinancial Aid
January 2009
15
Student Employment
The Student Employment module performs the referral, placement, hours submission, and
tracking functions for student employees. This module provides you with the following
features:
• Work Authorization - allows processing of the student’s work location,
employment dates, rate of pay, and authorized hours and earnings
• Departmental Time Reports - permits submission and monitoring of the student’s
hours worked
Forms
The following forms are included within the Student Employment module. For more
information about a specific form, select Help > Online Help from that form in Banner.
January 2009
Student Employment Default Rules
RJRSEDR
Payroll Load Control
RJRPAYL
Placement Rules
RJRPLRL
Placement Base Data
RJAPLBD
Job Title Base Data
RJRJOBT
Job Title Requirements
RJRJREQ
Referral Status Validation
RTVRFST
Employment Authorization Status Validation
RTVAUST
Financial Aid 8.3
User Guide
Student Employment
15-1
Student Employment Process Flow
Narrative
• Placement Rules
Placement rules define the Position, Allocation, Employee Class, Chart of
Accounts code, and Organization code with which a Placement code is
associated.
• Payroll Employee Class and Payroll Position
The Employee Class code and Position code associated with a Placement code
are either obtained from Banner Human Resources, or are free-format, unvalidated
data elements.
• Finance Chart of Accounts
The Chart of Accounts code associated with a Placement code is either obtained
from Banner Finance, or is a non-enterable data element.
• Finance or Payroll Organization
The organization code associated with a Placement code is either obtained from
Banner Finance, Banner Human Resources, or is a free-format unvalidated data
element.
• Create Referrals
Position referrals are created for each employed student by Placement code.
• Create Employment Authorizations
Student Employment Authorizations are created for each employed student by
Fund and Placement code. The authorizations obtain data from multiple tables
(see diagram) and update the Student Employment Work History table.
• Employment Default Rules
These rules are used in the creation of position referrals and contain starting and
ending dates for Authorizations and Payments, Pay Rate, and Authorization
Status.
• Applicant Awards, Work History, and Payroll Earnings
These data elements are used in the creation of position referrals.
• Payroll Load Process
This process updates Financial Aid student employment data with actual payroll
earnings and produces the Payroll Load Result Report.
• Payroll Load Rules
These rules are used during the Payroll Load Process and identify the payroll(s)
that should be interfaced to the Financial Aid student employment module.
15-2
Financial Aid 8.3
User Guide
Student Employment
January 2009
• Payroll Calendar Rules and Payroll Base History
These rules are used to create the Payroll Load rules. The Calendar rules define
beginning and ending Pay Dates and Check Date, and valid combinations of
Payroll Year, Payroll ID, and Payroll Number. The Base History table defines
the Payroll Disposition indicator.
January 2009
Financial Aid 8.3
User Guide
Student Employment
15-3
15-4
Financial Aid 8.3
User Guide
Student Employment
January 2009
16
Loan Processing
This module enables you to process Direct Loans, CommonLine Loans, and Manual
Loans.
Banner Financial Aid clients who process Pell, ACG, SMART, and TEACH grants, and
Direct Loans must process the files as Common Origination and Disbursement (COD).
Refer to the Banner Financial Aid COD Handbook for information on the entire COD
Process.
Refer to the Banner Financial Aid Electronic Loan Handbook for complete information
on CommonLine Loan processing.
Forms
The following forms are included within the Loan Processing module. For more
information about a specific form, select Help > Online Help from that form in Banner.
Direct Loan Processing
Direct Loan Origination
RPALORG
Batch Control
RPIBATC
COD Document Control
REICODD
Direct Loan Corrections
RPADLCR
Promissory Note
RPAPROM
Loan Electronic Counseling Status
RPILECS
Direct Loan Cash Drawdown
RPACASH
Direct Loan Account Summary
RPIDLAS
COD State Codes Rules
RTVCDST
COD Nation Codes Rules
RTVCDNT
Loan Parent Inquiry
RPILPAR
Electronic Loan Processing
January 2009
Financial Aid 8.3
User Guide
Loan Processing
16-1
Electronic Loan Application
RPAELAP
Student Lender History Data
RPASLND
Loan Disbursement
RPALDSB
Change Transaction Record Request
RPACTRR
Electronic Payment Receipt
RPAEPMT
Electronic Loan Disbursement
RPAELDB
Loan Parent Inquiry
RPILPAR
Batch Control
RPIBATC
Loan Electronic Counseling Status
RPILECS
Manual Loan Processing
Loan Application
RPALAPP
Loan Disbursement
RPALDSB
Loan Parent Inquiry
RPILPAR
Loan Control
16-2
Loan Period Base Data
RPRLPRD
Lender Base Data
RPRLNDR
Lenders/Disbursing Agents Rules
RPRLNDA
Loan Options
RPRLOPT
Class Code Translation
RPRCLSS
Federal Rules Inquiry
RPIFEDR
Loan Status Validation
RTVLNST
Certification Initials Validation
RTVCINT
COD State Code Rules
RTVCDST
COD Nation Codes Rules
RTVCDNT
Financial Aid 8.3
User Guide
Loan Processing
January 2009
Manual Loan Process
• Student Returns Completed Application
• Determine Award Amount
The loan amount is determined based on need.
• Create/Update Loan Information
The loan information is created and maintained on the Loan Application form
(RPALAPP). This form is used to create a loan application, review eligibility and
admissions data, establish references for the applicant, view the application
information, modify the loan term and disbursement schedules, and certify the
loan.
• Manually Record Check
When received from the lender, the loan check is manually recorded and a
summary of all loan activity for the student is reviewed using the Loan
Disbursement form (RPALDSB).
• Generate Memos, Authorizations, Payment Records
Run the Disbursement Process (RPEDISB) to generate memos, authorizations, and
payment records pertaining to amount of deferred financial aid available, amount
of financial aid available to be disbursed, and the schedule for disbursement.
January 2009
Financial Aid 8.3
User Guide
Loan Processing
16-3
16-4
Financial Aid 8.3
User Guide
Loan Processing
January 2009
17
Return of Title IV Funds
The Return of Title IV Funds module assists you in complying with the Title IV
regulations for federal financial aid. The Title IV module the Accounts Receivable,
Student, and Financial Aid products and enable you to do the following.
• Identify Title IV institutional change, such as aid year, and manual refund detail
codes.
• Record authorizations from students to authorize the use of Title IV aid to pay off
non-allowable charges, prior year minor institutional charges, and/or hold excess
Title IV aid for future use.
• Allow application of payments to pay off only allowable charges, or to pay off all
charges based on user authorization. You can also choose to apply payments so that
they will only pay off charges for terms within an aid year, with parameter to
control future terms within the aid year.
• Identify original charges as required for the return calculation.
• Define break periods within the period of enrollment.
• Identify Title IV recipients who have fully withdrawn, or are no longer in
attendance.
• Determine the enrollment period and the point in the period that enrollment
terminated.
• Determine a student’s institutional charges, Title IV aid, and percentage of
enrollment period completed in order to calculate the Title IV repayment.
• Determine the amount of Title IV aid that should be returned to the Title IV
programs by the institution and/or student, or post-withdrawal disbursed to the
student.
• Refund Title IV credits.
Forms
The following forms are included within the Return of Title IV Funds module. For more
information about a specific form, select Help > Online Help from that form in Banner.
January 2009
Financial Aid 8.3
User Guide
Return of Title IV Funds
17-1
Return of Title IV Funds Calculation
RPATIVC
Return of Title IV Funds Calculation Inquiry
RPITIVC
Return of Title IV Funds Process Flow
• Run the Title IV Recipients Withdrawn Process.
Determine students who have withdrawal records by running the Title IV
Recipients Withdrawn Process (RPRTIVR).
• Calculate the Title IV fund amount to be returned to students.
• Batch Process: Calculate the Title IV fund amount to be returned to students
by running the Title IV Fund Returns Calculation Process (RPRTIVC).
• Online Process: Calculate the Title IV fund amount to be returned to an
individual student by using the Return of Title IV Funds Calculation form
(RPATIVC).
Both the batch and online process use a Simulation and Calculate and Save mode.
Use the Simulation mode to review the results. Use the Calculate and Save mode to
create a Return of Title IV Funds record.
• (Optional) Review calculations for all students by running Return of Title IV
Funds With Process (RPRTIVI)
• (Optional) Review individual student records using the Return of Title IV
Funds Calculation Inquiry form (RPITIVC).
• Update the student’s award based on the results of the Return of Title IV
Calculation.
• Run the Disbursement Process to update the paid amounts for affected funds.
• The business office returns the money to the appropriate Title IV funds.
17-2
Financial Aid 8.3
User Guide
Return of Title IV Funds
January 2009
18
Reports and Processes
Introduction
This chapter contains information about reports generated by Banner Financial Aid. It
includes the following sections:
Naming
Conventions
An explanation of Banner report seven-character code naming
conventions.
Reports
For most report, two sections are provided: a description page
and a report sample.
The description page provides the report’s seven-character
name and identifier, and contains the following headings:
Description
A brief explanation of the report’s contents
Parameters
For each parameter, lists the parameter
number, name, valid values or the source
form for valid values, and comments
regarding the parameter
The report sample provides you with a picture of the report.
Most reports include the following pages:
Data page(s)
Detailed, itemized report data
Summary page
Grand totals of all data categories
Report Control
Information
Includes a list of the parameters established
when the report was requested and a total
record count for the report
The sample reports are presented in alphabetical order by the report’s seven-character
name.
For information on how to run a report, see the Job Submission chapter of the General
User Guide.
January 2009
Financial Aid 8.3
User Guide
Reports and Processes
18-1
Naming Conventions
The names of all Banner reports and processes are seven characters in length and use the
following convention.
Position Locations:
R
1
B
2
R
3
B
4
C
5
M
6
P
7
Note
SunGard Higher Education has reserved the letters W, Y, and Z for the
first two characters of all client-developed forms and reports.
For client-developed new applications built to co-exist with Banner
applications, W, Y, and Z is used as the first character.
For client-developed forms, reports, tables, or modules used within an
Banner application, the SunGard Higher Education system identifier is
used as the first character (i.e., R = Financial Aid, etc.), and W, Y, and Z is
„
used as the second character.
Position 1: Identifies the primary system owning the report as:
A
F
G
N
P
R
S
T
=
=
=
=
=
=
=
=
Advancement
Finance
General
Position Control
Human Resources
Financial Aid
Student
Accounts Receivable
If W, Y, or Z appears as the first character of the report name, refer to Note (above).
Position 2: Identifies the primary module owning the report as:
B
C
E
F
H
J
L
N
O
P
18-2
Financial Aid 8.3
User Guide
Reports and Processes
=
=
=
=
=
=
=
=
=
=
Budgeting
Record Creation
Electronic Data Exchange (EDE)
Funds Management
History and Transcripts
Student Employment
Logging
Need Analysis
Common Functions
Packaging and Disbursements
January 2009
R
S
=
=
Requirements Tracking
Student System Shared Data
If W, Y, or Z appears as the second character of the report name, refer to Note (above).
Position 3: Identifies the type of report or process as:
B
E
O
R
=
=
=
=
Batch Mode only
Either Batch or Online Mode
Online Mode only
Report
Positions 4 - 7: Identifies the unique four-character abbreviation of the report name.
For example, the derivation of RBRBCMP (Budget Component Report) is:
R
B
R
BCMP
January 2009
=
=
=
=
Financial Aid
Budgeting
Report
Budget Component listing
Financial Aid 8.3
User Guide
Reports and Processes
18-3
18-4
Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Athletic Grant Term Roll Process (RAPAGRL)
Use this new process to roll athletic grant term information on RAASPTM from one term to the next. The
following are the process parameters. When the Term parameter (Parameter 04) is R, then the Number of Terms
field on RAASPTM is incremented by 1. When it is equal to S, then the Summer Terms field is incremented by 1.
Description
Note
When this process is run in Audit mode, the output will indicate the potential number of rollable
records and non-rollable records. When run in Update mode, the actual number of rolled or
„
non-rolled records will be indicated.
Parameters
18-5
Name
Required?
Description
Values
From Term
Yes
To Term
Yes
Sport Code
No
Term Code from which athletic grant information is
to be rolled.
Term Code to which athletic grant information is to
be rolled.
Financial Aid sport code
Term
Yes
Term type to be created
Athlete’s Actual
Grant – Term
No
Roll Athlete’s Actual Grant – Term Amount;
Run Mode
Yes
Run in (A)udit or [U]pdate mode.
Sort Option
No
Sort report by [N]ame or (I)d.
Application ID
No
Selection ID
No
General area for which the selection ID was
defined.
Code that identifies the sub-population to work
with.
LOV: STVTERM
Default = blank
LOV: STVTERM
Default = blank
LOV: RTVFASP
Default = blank
R = Regular Term
S = Summer
Default = R
Y = Yes
N = No
Default = N
A = Audit
U = Update
Default = U
N = Name
I = ID
Default = N
LOV: GLIAPPL
Default = blank
LOV: GLISLCT
Default = blank
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont
Name
Required?
Description
Values
Creator ID
No
User ID
No
The ID of the person creating the sub-population
Default = blank
rules.
The ID of the person using the sub-population rules. Default = blank
Athletic Grant Term Roll Sample
09-SEP-2008 12:25:34 PM
SUNGARDHE University
ATHLETIC GRANT TERM ROLL PROCESS REPORT
NAME
ID
FA Sport
Description
Status
KichlineKichli?e, Test65 1
999656565
MF-TRACK
Men's Fall Track
Athletic Data rolled.
09-SEP-2008 12:25:34 PM
SUNGARDHE University
ATHLETIC GRANT TERM ROLL PROCESS REPORT
PAGE
RAPAGRL
1
PAGE
RAPAGRL
2
* * * REPORT CONTROL INFORMATION * * *
Program Name.................................: RAPAGRL
Version......................................: 8.2
Report Sequence Number.......................: 200407
From Term....................................: 200910
To Term......................................: 200930
Sport Code...................................: MF-TRACK
Term.........................................: R
Athlete’s Actual Grant - Term Amount........: Y
Run Mode.....................................: U
Sort Option..................................: N
Application Id...............................:
Selection Id.................................:
Creator Id...................................:
User Id......................................:
FINAID
MANUAL
MKICHLIN
MKICHLIN
Line Count...................................: 55
Number of records rolled.....................: 1
Number of records not rolled.................: 0
Total pages Printed..........................: 2
****** END OF REPORT ******
18-6
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Athletic Aid Discrepancy Report (RARATAD)
Use this report to display the discrepant information between the actual fund/resource amounts and the reported
amounts on RAASPTM. This report should be used to determine if a student’s award information has been updated
since this information was originally reported to Athletics.
Description
Parameters
18-7
Name
Required?
Description
Values
Term
Yes
Sport Code
No
Term Code from which athletic grant discrepancy
information is to be reported.
Financial Aid sport code
Sort Option
No
Sort report by [N]ame or (I)d.
Application ID
No
General area for which the selection ID was defined.
Selection ID
No
Code that identifies the sub-population to work with.
Creator ID
User ID
No
No
The ID of the person creating the sub-population rules.
The ID of the person using the sub-population rules.
LOV: STVTERM
Default = blank
LOV: RTVFASP
Default = blank
N = Name
I = ID
Default = N
LOV: GLIAPPL
Default = blank
LOV: GLISLCT
Default = blank
Default = blank
Default = blank
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Athletic Aid Discrepancy Report Sample
09-SEP-2008 12:41:48 PM
SUNGARDHE University
ATHLETIC AID DISCREPANCY REPORT
NAME
ID
Term
FA Sport
Type
Code
KichlineKichli?e, Test65 1
999656565
200910
MF-TRAC
Inst. Award
Resource
MKGRNT
VA30
09-SEP-2008 12:41:48 PM
SUNGARDHE University
ATHLETIC AID DISCREPANCY REPORT
PAGE
RARATAD
1
Actual
Reported
4,000.00
2,000.00
5,000.00
1,000.00
PAGE
RARATAD
2
* * * REPORT CONTROL INFORMATION * * *
Program Name.................................: RARATAD
Version......................................: 8.2
Report Sequence Number.......................: 200416
Term.........................................: 200910
Sport Code...................................:
Sort Option..................................: N
Application Id...............................:
Selection Id.................................:
Creator Id...................................:
User Id......................................:
FINAID
MANUAL
MKICHLIN
MKICHLIN
Line Count...................................: 55
Number of students with discrepant records...: 1
Number of discrepant records.................: 2
Total pages Printed..........................: 2
****** END OF REPORT ******
18-8
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Applicant Budget Report (RBRABUD)
The Applicant Budget Report prints applicant budget information based on specified parameters.
Description
Parameters
18-9
Name
Required?
Description
Values
Selection Identifier
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application Code and Creator ID of
Selection ID parameters.
Population Selection Inquiry form
(GLISLCT)
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection Identifier and Creator ID of
Selection ID parameters.
Application Inquiry form (GLIAPPL)
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Aid Period Code
No
You can optionally enter an aid period code. If you
enter an aid period code, you can restrict the
information on this report to only include
information relevant to this aid period.
Aid Period Validation form
(RTVAPRD)
Budget Group Code
No
You can optionally enter a budget group code. If you
enter a budget group code, you can restrict the
information on this report to only include
information relevant to this group code.
Budget Group Validation form
(RTVBGRP)
Budget Type Code
No
You can optionally enter a budget type code. If you
enter a budget type code, you can restrict the
information on this report to only include
information relevant to this budget type.
Budget Type Validation form
(RTVBTYP)
Campus Based
Type Indicator
No
If this optional parameter is used, enter a Y for the
value.
Y
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont)
18-10
Name
Required?
Description
Values
Pell Type Indicator
No
You define each budget on the RTVBTYP form as
Campus Based, Pell, Institutional, State, or Other
when you enter a Y in the respective indicator. If you
optionally enter a Y for this parameter and do not
enter a Budget Type Code parameter, the report will
only include those budget types with a Y in the Pell
field on the RTVBTYP form.
Budget Type Validation form
(RTVBTYP)
Institutional Type
Indicator
No
You define each budget on the RTVBTYP form as
Campus Based, Pell, Institutional, State, or Other
when you enter a Y in the respective indicator. If you
optionally enter a Y for this parameter and do not
enter a Budget Type Code parameter, the report will
only include those budget types with a Y in the Pell
field on the RTVBTYP form.
Budget Type Validation form
(RTVBTYP)
State Type Indicator
No
You define each budget on the RTVBTYP form as
Campus Based, Pell, Institutional, State, or Other
when you enter a Y in the respective indicator. If you
optionally enter a Y for this parameter and do not
enter a Budget Type Code parameter, the report will
only include those budget types with a Y in the Pell
field on the RTVBTYP form.
Budget Type Validation form
(RTVBTYP)
Other Type Indicator
No
You define each budget on the RTVBTYP form as
Campus Based, Pell, Institutional, State, or Other
when you enter a Y in the respective indicator. If you
optionally enter a Y for this parameter and do not
enter a Budget Type Code parameter, the report will
only include those budget types with a Y in the Pell
field on the RTVBTYP form
Budget Type Validation form
(RTVBTYP)
Year in College
No
If this optional parameter is used, enter a number
from 0 - 9.
0-9
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont)
18-11
Name
Required?
Description
Values
Creator ID
of Selection ID
No
The ID of the person creating the sub-population
rules.
User Identification Control form
(GUAIDEN)
User ID
of Selection ID
No
The ID of the person using the sub-population rules.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Applicant Budget Report Sample
17-MAY-2002 01:33 PM
1
AID YEAR: 0203 Award Year 2002-2003
STUDENT'S NAME
SunGard Higher Education Development
PAGE
Applicant Budget Report
ID
AID
PERIOD
% OF
YEAR
RBRABUD
BUDGET
GROUP
YR IN SCH
LOAD
Magrone, Aaron C.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030505 FA/SPR
TOT BUD: $10,775.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$10,775.00
Magrone, Anand R.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030521 FA/SPR
TOT BUD: $11,025.00
100.000
UGINOF
6
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$11,025.00
Magrone, Brian A.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030503 FA/SPR
TOT BUD: $10,400.00
100.000
UGINOF
5
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$10,400.00
Magrone, Caroline M.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030514 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Christian R.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030508 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
0
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Collin C.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030510 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Daniel B.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030504 FA/SPR
TOT BUD: $10,500.00
100.000
UGINOF
5
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$10,500.00
Magrone, Jason M.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030513 FA/SPR
TOT BUD: $16,330.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Jenell M.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030507 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
0
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Jodi L.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030502 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$19,950.00
Magrone, Kyle D.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030515 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Lea C.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030524 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
0
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$6,830.00
Magrone, Melanie N.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030501 FA/SPR
TOT BUD: $29,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Michael J.
18-12
Banner Financial Aid 8.3
User Guide
Reports and Processes
181030511
FA/SPR
100.000
UGINOF
1
January 2009
17-MAY-2002 01:33 PM
2
AID YEAR: 0203 Award Year 2002-2003
STUDENT'S NAME
SunGard Higher Education Development
PAGE
Applicant Budget Report
ID
AID
PERIOD
% OF
YEAR
RBRABUD
BUDGET
GROUP
YR IN SCH
LOAD
Magrone, Nathaniel M.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030516 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Neggy
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030509 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Magrone, Onkar
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030520 FA/SPR
TOT BUD: $11,025.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$11,025.00
Magrone, Peter N.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030522 FA/SPR
TOT BUD: $11,025.00
100.000
UGINOF
0
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$11,025.00
Magrone, Shannon M.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030512 FA/SPR
TOT BUD: $19,950.00
100.000
UGINOF
7
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$16,330.00
Silvaint, Kevin Y.
BUD TYPE CD: CAMP
TYPE IND: CAMP
181030506 FA/SPR
TOT BUD: $11,025.00
100.000
UGINOF
5
BUD TYPE CD: PELL TYPE IND: PELL
TOT BUD:
$11,025.00
17-MAY-2002 01:33 PM
4
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Applicant Budget Report
PAGE
RBRABUD
* * * REPORT CONTROL INFORMATION * * *
RPTNAME: RBRABUD
VERSION#: (5.3)
REPORT SEQUENCE NUMBER: 786760
AID YEAR: 0203
SELECTION IDENTIFIER: 0203_APPS
APPLICATION CODE: FINAID
CREATOR ID: SMAGRONE
AID PERIOD: FA/SPR
BUDGET GROUP:
BUDGET TYPE:
CAMPUS INDICATOR (Y/N):
PELL INDICATOR (Y/N): Y
INSTITUTION INDICATOR (Y/N):
STATE_INDICATOR (Y/N):
OTHER_INDICATOR (Y/N):
YEAR IN COLLEGE:
LINE COUNT: 55
RECORD COUNT - PART ONE: 21
RECORD COUNT - PART TWO:
18-13
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Budget Component Report (RBRBCMP)
The Budget Component Report lists budget component amounts by budget group, budget type, and aid period.
Description
Parameters
18-14
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Budget Group Code
No
You can optionally enter a budget group code. If you
enter a budget group code, you can restrict the
information on this report to only include
information relevant to this group code.
Budget Group Validation form
(RTVBGRP)
Budget Type Code
No
You can optionally enter a budget type code. If you
enter a budget type code, you can restrict the
information on this report to only include
information relevant to this budget type.
Budget Type Validation form
(RTVBTYP)
Aid Period Code
No
You can optionally enter an aid period code. If you
enter an aid period code, you can restrict the
information on this report to only include
information relevant to this aid period.
Aid Period Validation form
(RTVAPRD)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Budget Component Report Sample
17-MAY-2002 01:38 PM
1
AID YEAR: 0203 Award Year 2002-2003
GROUP
CODE
DESCRIPTION
SunGard Higher Education Development
Budget Component Report
TYPE
CODE
DESCRIPTION
UGINOF Undergrad Resident Off Campus CAMP
Campus based
PRINT ORDER COMPONENT CD DESCRIPTION
10
T+F
Tuition and Fees
20
R+B
Room and Board
30
B+S
Books and Supplies
50
PERS
Personal Expenses
60
TRAN
Transportation
120
COMP
Computer Fees
RBRBCMP
AID
PERIOD
DESCRIPTION
% OF
YEAR
FA/SPR
Fall-Spring Semesters
100.000
VALUE
TOTAL:
UGINOF Undergrad Resident Off Campus PELL
Pell Based
PRINT ORDER COMPONENT CD DESCRIPTION
10
T+F
Tuition and Fees
20
R+B
Room and Board
30
B+S
Books and Supplies
50
PERS
Personal Expenses
60
TRAN
Transportation
$9,500.00
$5,550.00
$800.00
$950.00
$650.00
$2,500.00
-------------$19,950.00
FA/SPR
Fall-Spring Semesters
100.000
VALUE
TOTAL:
17-MAY-2002 01:38 PM
2
AID YEAR: 0203 Award Year 2002-2003
PAGE
$9,500.00
$5,000.00
$800.00
$950.00
$80.00
-------------$16,330.00
SunGard Higher Education Development
Budget Component Report
PAGE
RBRBCMP
* * * REPORT CONTROL INFORMATION * * *
RPTNAME: RBRBCMP
REPORT SEQUENCE NUMBER: 786764
AID YEAR: 0203
BUDGET GROUP: UGINOF
BUDGET TYPE:
AID PERIOD: FA/SPR
LINE COUNT: 55
RECORD COUNT: 2
18-15
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid CSS Data Load Part 1 Process (RCBCTxx)
Description
The parameters for the CSS Data Load - Part 1 are similar to the Financial Aid EDE Data Load - Part 1 process.
The RCBCTxx process substitutes for the RCBTPxx process as step 1 in the data load procedure when you load
CSS PROFILE records. Like the RCBTPxx process, the RCBCTxx process stores this information in temporary
Oracle tables, which are then used by the RCPMTCH (Financial Aid Matching Process) and RCRTPxx (database
load process) programs to complete the data load process.
The xx in the last two positions of the program name indicates the aid year for which the program is designed. The
program is year-specific because financial aid processor application record formats change annually. Note that the
names of the underlying Banner Financial Aid tables are not year-specific; columns are merely added to these
tables as necessary on a year-to-year basis.
Note
Refer to the Data Load Procedures section of the Processing chapter for more information
concerning the entire data load process.
18-16
Banner Financial Aid 8.3
User Guide
Reports and Processes
„
January 2009
Parameters
18-17
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Data Source
for CSS
Yes
The only valid value for this parameter is CSS.
Interface Data Code Validation form
(RTVINFC)
Data Delivery Method
Yes
Identifies delivery method.
D
Electronic Data Delivery
Generate ID/
Use SSN Indicator
Yes
When this parameter value is set to S, the student ID
will be created using the social security number
(SSN); when this value is G, a new ID will be
generated. The Generate ID/Use SSN parameter
option enables Banner to generate an ID for a new
person, or use the SSN as the ID. If SSNs are used as
IDs and duplicate IDs are found, the SSN will be
used on the first person and generated IDs will be
used for the duplicates.
G
Generate
S
Use SSN (default)
Recalculate Need
Indicator
Yes
Address Type Code
Yes
Banner Financial Aid 8.3
User Guide
Reports and Processes
When this parameter value is set to Y, all new
Y
applicant records will be created with their
Recalculate Need indicator set to Y, indicating that N
their need will be recalculated the next time the Need
Analysis process is performed.
This parameter determines the address type that you
want to use for a student.
Recalc (default)
No Recalc
Address Type Validation form
(STVATYP)
January 2009
Parameters (cont)
Name
Required?
Description
Telephone Type Code
Yes
If the STVATYP table has a Telephone Type code
associated with the requested Address Type code,
Banner uses that Telephone Type code to create the
telephone record. The Address Type code and
address sequence number are populated with the
values used when creating the associated address
record and the telephone number is flagged as
primary. This is necessary since the address type is
linked to this telephone type. In this case, the value
for the new telephone type parameter is ignored.
Values
If the STVATYP table has no Telephone Type code
associated with the requested Address Type code,
Banner uses the Telephone Type code defined as the
input parameter. The Telephone Type code is
validated against the STVTELE table. The
telephone record is created with this validated
Telephone Type code. The Address Type code and
Address Sequence Number are populated with the
values used when creating the associated address
record and the telephone number is flagged as
primary. This is necessary since the address type is
linked to this telephone type.
Starting Record Number
Yes
This parameter contains the record number for the
restart process.
0 - 99,999
Email Address
Type Code
No
The email address type you want to use for a
student.
E-mail Address Type Validation form
(GTVEMAL)
Note
Banner adds address and telephone records on new students (not currently in the database).
Also, parameters for Financial Aid Dataload, Part 3 (RCRTPxx) determine whether to update
address, telephone, and email for existing student records if the Type does not already exist.„
18-18
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid CSS Data Load Part 1 Process Sample
Log file for program RCBCT03
============================
Program Version = 6.2
Command Line Parameters:
User Id
= smagrone
Password = ????????
ONE-UP-NO = 978335
Jobname
= RCBCT03
CONNECTED TO ORACLE RDBMS
on 26-OCT-2001 at 01:40:36
Job Submission
Parm 1 =
Parm 2 =
Parm 3 =
Parm 4 =
Parm 5 =
Parm 6 =
Parm 7 =
Parm 8 =
Parm 9 =
Parameters:
0203
CSS
D
S
N
BI
PR
00000001
WARNING STVATYP Phone Type for Address Type was used
Phone Type entered was ignored
Address Type/Phone Type = BI
Number of records read from input data: 00000010
Number of data records skipped/dropped: 00000000
Number of applicants loaded to tables: 00000010
HALT 999, NORMAL EOJ
Connected.
Job Summary
----------Job Name...:
Number.....:
Submit Date:
Submit Time:
Database...:
Userid.....:
Printer....:
Directory..:
18-19
rcbct03.shl
978335
26-Oct-2003
01:40:33 PM
B40
smagrone
DATABASE
/u/designer/smagrone/jobsub
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid EDE Data Load Part 1 Process (RCBTPxx)
Description
The data load process loads financial aid applicant records into Banner Financial Aid from external sources via
electronic media. This information is stored in temporary Oracle tables (loaded by the RCBCTxx or RCBTPxx
processes), which is then used by the RCPMTCH (Financial Aid Matching Process) and RCRTPxx (database load
process) programs to complete the data load process.
The xx in the last two positions of the program name indicates the aid year for which the program is designed. The
program is year-specific because financial aid processor application record formats change annually. Note that the
names of the underlying Banner Financial Aid tables are not year-specific; columns are merely added to these
tables as necessary on a year-to-year basis.
Note
Refer to the Data Load Procedures section of the Processing chapter for more information
concerning the entire data load process.
18-20
Banner Financial Aid 8.3
User Guide
Reports and Processes
„
January 2009
Parameters
18-21
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Data Source Code
Yes
Enter a valid data source code.
Interface Data Code Validation form
Data Delivery Method
Yes
Identifies delivery media
D
Electronic or Diskette
Generate ID/
Use SSN Indicator
Yes
When this parameter value is set to S, the student ID
will be created using the social security number
(SSN); when this value is G, a new ID will be
generated. The Generate ID/Use SSN Indicator
parameter option enables Banner to generate an ID
for a new person, or use the SSN as the ID. If SSNs
are used as IDs and duplicate IDs are found, the SSN
will be used on the first person and generated IDs
will be used for the duplicates.
G
Generated ID
S
Use SSN as ID (default)
Recalculate Need
Indicator
Yes
Address Type Code
Yes
Banner Financial Aid 8.3
User Guide
Reports and Processes
When this parameter value is set to Y, all new
Y
applicant records will be created with their
Recalculate Need Indicator set to Y, indicating that N
their need will be recalculated the next time the Need
Analysis process is performed.
This parameter determines the address type that you
want to use for a student.
Recalculate Need (default)
Do Not Recalculate Need
Address Type Validation form
(STVATYP)
January 2009
Parameters (cont)
Name
Required?
Description
Values
Telephone Type Code
Yes
If the STVATYP table has a Telephone Type code
associated with the requested Address Type code,
Banner uses that Telephone Type code to create the
telephone record. The Address Type code and
address sequence number are populated with the
values used when creating the associated address
record and the telephone number is flagged as
primary. This is necessary since the address type is
linked to this telephone type. In this case, the value
for the new telephone type parameter is ignored.
Telephone Type Validation form
(STVTELE)
If the STVATYP table has no Telephone Type code
associated with the requested Address Type code,
Banner uses the Telephone Type code defined as the
input parameter. The Telephone Type code is
validated against the STVTELE table. The
telephone record is created with this validated
Telephone Type code. The Address Type code and
Address Sequence Number are populated with the
values used when creating the associated address
record and the telephone number is flagged as
primary. This is necessary since the address type is
linked to this telephone type.
Starting Record Number
Yes
This parameter contains the record number for the
restart process.
0 - 99,999
Email Address
Type Code
No
The email address type that should be created if it is
a new student.
E-mail Address Type Validation form
(GTVEMAL)
Note
Banner adds address and telephone records on new students (not currently in the database).
Also, parameters for Financial Aid Dataload, Part 3 (RCRTPxx) determine whether to update
address, telephone, and email for existing student records if the Type does not already exist.„
18-22
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid EDE Data Load Part 1 Report Sample
If the EDE records you are loading are the result of an ISIR Datamart Query, the title of that Query is displayed.
Log file for program RCBTP03
============================
Program Version = 5.3
Command Line Parameters:
User Id
= faisusr
Password = ????????
ONE-UP-NO = 7392
Jobname
= RCBTP03
CONNECTED TO ORACLE RDBMS
on 04-MAR-2002 at 01:39:00
Job Submission
Parm 1 =
Parm 2 =
Parm 3 =
Parm 4 =
Parm 5 =
Parm 6 =
Parm 7 =
Parm 8 =
Parm 9 =
Parameters:
0203
EDE
D
S
N
PR
PR
00000001
HOME
The address for this person contains a
Pidm = 00001762 SSN = 165294202
Name = ISAAC
DRUM
Addr = 259790 HWY 101 #44
The address for this person contains a
Pidm = 00001763 SSN = 165390880
Name = BERTHA
AVILA
Addr = 1816 #B 16TH ST.
The address for this person contains a # . , & ^ or *.
Pidm = 00001765 SSN = 165568697
Name = ALON
TRAUT
Addr = 3330 NORTHWEST AVE #D5
18-23
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Data Load Table Deletes Process (RCPDTMP)
This process allows multi-year and multi-source processing by deleting everything in the temporary tables used in
the data load process whenever the RCPDTMP process was executed.
Description
Parameters
18-24
Name
Required?
Description
Values
Aid Year Code
No
Enter a valid and active aid year. FThis parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Data Source Code
No
Enter a valid data source code.
Interface Data Code Validation form
(RTVINFC)
Delete Flagged
Records Only?
Yes
Delete flagged records only?
Y
Yes
N
No (default)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Data Load Table Deletes Process Sample
04-MAR-2002 01:38:06 PM
BANNER University
1
Aid Year: 0203
Data Load Table Delete Process
RCPDTMP
-----------------------------------------------------------------------------------------------------------------------------------Rows deleted from RCRTMP1 : 6
Rows deleted from RCRTMP2 : 6
Rows deleted from RCRTMP3 : 6
Rows deleted from RCRTMP4 : 6
Rows deleted from RCRTMP5 : 0
Rows deleted from RCRTMP6 : 0
Rows deleted from RCTLDS1 : 0
Rows deleted from RCTLDS2 : 0
Rows deleted from RCTLDS3 : 0
Rows deleted from RCTLDS4 : 6
Rows deleted from RCTLDS5 : 0
Rows deleted from RCTLDS6 : 36
Rows deleted from RCTLDS7 : 0
Rows deleted from RCTESAR : 6
Rows deleted from ROTPERS : 6
Rows deleted from ROTADDR : 6
Rows deleted from RCTRECR : 6
Rows deleted from RPTCONT : 6
Rows deleted from RCTRSRC : 6
Rows deleted from ROTSTAT : 6
Rows deleted from ROTSAPR : 6
Rows deleted from ROTEMAL : 6
18-25
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Rows deleted from ROTIDEN : 6
04-MAR-2002 01:38:06 PM
BANNER University
2
Aid Year: 0203
Data Load Table Delete Process
RCPDTMP
-----------------------------------------------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name
One up Number
Aid Year Code
Data Source Code
Delete Flagged Records Only
Number of lines per page
Report file name
:RCPDTMP(5.1)
:7391
:0203
:EDE
:N
:55
:c:\temp\jobsub\fatest_faisusr_rcpdtmp_7391.lis
Total pages Printed
:2
****** END OF REPORT ******
18-26
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Copy IM Data to FM Process (RCPIMFM)
This process copies all unique IM fields to the current FM record so they may be used in rules processing. Once
an FM record is loaded into the system, it automatically becomes the current record while the IM record becomes
the noncurrent record.
Description
Rules look only at the current record when being applied to a population and therefore, if unique IM data is to be
used in rules, this data must be copied to thecurrent FM record. The RCIMTOFM process is run as part of data load
Step 3.However, this process also may need running if a manual FM or IM record is created, the current record is
changed, and you want the unique IM fields copied to the current FM record.
Parameters
18-27
Name
Required?
Description
Values
Aid Year Cod
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Applicant ID
No
You can optionally enter an applicant ID. Enter an
Person Search form (SOAIDEN)
ID for this parameter if you want to restrict the report
to only a single applicant.
Application ID
No
General area for which the selection ID was defined. Application Inquiry form (GLIAPPL)
Selection ID
No
Code that identifies the sub-population to work with.
Creator ID
No
ID of the person creating the sub-population rules.
User ID
No
ID of the person using the sub-population rules.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Data Load Part 2 Process (RCPMTCH)
The RCPMTCH process compares data in temporary tables is against the data in the production database to ensure
that the information can be loaded to the correct person if they already exist in the database, or to create a new
person if the student does not yet have a record at the institution.
Description
Parameters
18-28
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Data Source Code
Yes
Enter a valid data source code.
Interface Data Code Validation form
(RTVINFC)
Generated ID/
Use SSN
Yes
Use SSN or Generated IDs.
G
Use Generated ID
S
Use SSN (default)
Value for New Students
Yes
H
Hold
N
New (default)
Banner Financial Aid 8.3
User Guide
Reports and Processes
Status for new students. This is the status code that
is posted to all students who do not appear to match
anyone in the production database. Part 3 of the Data
Load process loads all students with a status code of
N, but Data Load does not load students with a status
code of H. This option is available for those
institutions that do not desire to have the Data Load
process create new students (person records) in the
production database. Records with a status of H
(Hold) remain in the temporary tables until the
records match a person record in the database and
their status is updated appropriately, or until the
delete from temporary tables process is run
(RCPDTMP) in batch or for the individual record.
January 2009
Parameters (cont)
Name
Required?
Sort Order Indicator
No
Common Matching
Source code
Yes
Description
Common Matching Source Code defined on the
Common Matching Source Code Validation form
(GTVCMSC). Banner starts the Common Matching
Application Programming Interface (API) using the
rules defined for the Common Matching Source
Code entered for this parameter.
Values
I
Sort by ID
N
Sort by Name (default)
T
Sort by Temporary PIDM
Common Matching Source Code
Validation form (GTVCMSC)
Financial Aid Data Load Part 2 Process Sample
25-APR-2002 08:02:09 AM
Aid Year: 0203
BANNER University
1
Data Load Match Process
RCPMTCH
Parameters
-----------------------------------------------------------------------------------------------------------------------------------Financial Aid Data Load Matching Process - Parameters
Aid Year Code = 0203
Data Source Code = EDE
ID Type SSN/Generated = S
Status for New Students = N
Sort Order Indicator = I
SSN
Last Name
First Name
Middle Initial
Birthday Month
Birthday Day
Birthday Year
Gender
Address
City
State
Zip
Area Code
Phone
18-29
0
R 0
0
R 0
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
25-APR-2002 08:02:09 AM
Aid Year: 0203
BANNER University
2
Data Load Match Process
RCPMTCH
All Records
-----------------------------------------------------------------------------------------------------------------------------------INFC
PIDM
------- -------EDE
1777
1778
1779
1780
1781
1782
1783
1784
1785
1786
1787
1788
1789
1790
1791
1792
1793
1794
1795
1796
1797
1798
1799
1800
1801
1802
1809
1810
1805
1806
1807
1803
1804
1808
18-30
ID
--------181030501
181030502
181030503
181030504
181030505
181030506
181030507
181030508
181030509
181030510
181030511
181030512
181030513
181030514
181030515
181030516
181030517
181030518
181030519
181030520
181030521
181030522
181030523
181030524
181030525
181030526
181030527
181030528
181030701
181030702
181030703
181030704
181030705
181030706
SSN
--------181030501
181030502
181030503
181030504
181030505
181030506
181030507
181030508
181030509
181030510
181030511
181030512
181030513
181030514
181030515
181030516
181030517
181030518
181030519
181030520
181030521
181030522
181030523
181030524
181030525
181030526
181030527
181030528
181030701
181030702
181030703
181030704
181030705
181030706
Banner Financial Aid 8.3
User Guide
Reports and Processes
NAME
---------------------------Magrone, Melanie N
Magrone, Jodi L
Magrone, Brian A
Magrone, Daniel B
Magrone, Aaron C
Magrone, Kevin Y
Magrone, Jenell M
Magrone, Christian R
Magrone, Neggy
Magrone, Collin C
Magrone, Michael J
Magrone, Shannon M
Magrone, Jason M
Magrone, Caroline M
Magrone, Kyle D
Magrone, Nathaniel M
Magrone, Jyoti R
Magrone, William L
Magrone, Julie M
Magrone, Onkar
Magrone, Anand R
Magrone, Peter N
Magrone, Ella A
Magrone, Lea C
Magrone, Michael
Magrone, Chinaemerem B
Magrone, Kirsten
Magrone, Virginia C
Magrone, Andrea R
Magrone, Alon A
Magrone, Johnni E
Magrone, Isaac J
Magrone, Bertha L
Magrone, Kil B
STATUS
CODE MESSAGE
--------- ---- --------------------------------------------------New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
New
Ready for processing
January 2009
25-APR-2002 08:02:09 AM
Aid Year: 0203
BANNER University
3
Data Load Match Process
RCPMTCH
Summary of Totals
-----------------------------------------------------------------------------------------------------------------------------------COUNT STATUS DESCRIPTION CODE MESSAGE
---------- ------ ----------- ---- -----------------------------------------------------------34
N
New
25-APR-2002 08:02:09 AM
Aid Year: 0203
Ready for processing
BANNER University
4
Data Load Match Process
RCPMTCH
Control Summary
-----------------------------------------------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name
One up Number
Aid Year Code
Data Source Code
ID Type SSN/Generated
Status for New Students
Sort Order Indicator
Number of lines per page
Report file name
:RCPMTCH(5.1)
:7515
:0203
:EDE
:S
:N
:I
:55
:c:\temp\jobsub\fatest_faisusr_rcpmtch_7515.lis
Total pages Printed
:4
****** END OF REPORT ******
18-31
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Data Load Part 3 Process (RCRTPxx)
Description
This process (Financial Aid Data Load, Part 3) loads new and matching applicant records to the permanent tables
with an option to print a discrepancy report if a financial aid record already exists.
With this process, certain values are updated on new records based on what is entered on the Interface Data
Translation Rules form (RCRTPTR). These values include Citizenship, Marital Status, and Major. Citizenship
does not require values on RCRTPTR, as with the other fields. Citizenship is not updated if no values are entered
on RCRTPTR.
18-32
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Data Source Code
Yes
Enter a valid data source code.
Interface Data Code Validation form
(RTVINFC)
Load Option
for Need Analysis
Yes
The Load Option for Need Analysis only applies to
students with current application records for this
year - that is, the status is M (Matched).
1
Load all as current
2
If first record from primary MDE,
load as current record, else load as
non-current record
3
If first record from primary MDE,
load as current, else do not load
4
Load as non-current record
5
Do not load records, but print
discrepancy report
6
Tape load options 6 and 7 are the only valid options
if you enter CSS for the Data Source Code.
Replace existing CSS PROFILE
record
7
Do not replace existing CSS
PROFILE record
Prints NSLDS Discrepancy Report.
Y
Print NSLDS Disc Report
N
Do Not Print NSLDS Disc Report
Y
Print Need Analysis Disc Rpt
N
Do Not Print Need Analysis Disc
Students without current application records for this
year - the status is N (New), R (match found, but no
RORSTAT record for the current year), or A (match
found, but no RCRAPP1 record for the current year)
- will be loaded as current application records,
regardless of the load option that you select.
You can print a Discrepancy Report for load options
1 through 5, provided that you enter a Y value for the
subsequent Print Option parameter.
Not used at this time.
NSLDS Print Option
Need Analysis
Print Option
18-33
Banner Financial Aid 8.3
User Guide
Reports and Processes
Yes
Yes
Prints Need Analysis Discrepancy Report.
January 2009
Parameters (cont)
18-34
Name
Required?
Description
Values
Recruiting Option
Yes
Create recruiting records.
Y
Create Recruiting Recs
N
Do Not Create Recruiting Rec
Y
Recalc Need Analysis
N
Do Not Recalc Need Analysis
Recalc Need
Analysis Option
Yes
Sets Need Analysis Recalculation Flag.
NSLDS Output
Application ID
No
General area for which the selection ID was defined
for NSLDS output.
NSLDS Output
Selection ID
No
Code that identifies the sub-population to be updated
by NSLDS.
NSLDS Output
Creator ID
No
ID of the person who created the sub-population for
NSLDS.
ISIR Creation
Option
Yes
Option to create ISIR records.
Load VA Data to
Resource Table
Yes
Process Indicator
Yes
Application Inquiry form (GLIAPPL)
Y
Create ISIR Records (default)
N
Do Not Create ISIR Records
Option to load VA Educational Benefits into the
RPRARSC table.
Y
Load to Resource Table (default)
N
Do Not Load to Resource Table
Indicates batch or online processing
B
Batch (default)
O
Online
Temporary PIDM
No
Used in online processing
Update Postal Address
Yes
If an incoming record is matched to an existing
Y
person record in the production database, RCRTPxx
loads all financial aid data from the incoming record. N
RCRTPxx does not update populated fields on an
existing person record. RCRTPxx updates the Postal
Address if you enter Y and there is no record for the
Address type that you specified in your Data Load
Part 1 parameters.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Blank when running in batch
Update Postal Address
Don’t Update Postal Address
January 2009
Parameters (cont)
Name
Required?
Description
Update Telephone
Number
Yes
If an incoming record is matched to an existing
Y
person record in the production database, RCRTPxx
loads all financial aid data from the incoming record. N
RCRTPxx does not update populated fields on an
existing person record. RCRTPxx updates the
Telephone Number if you enter Y and there is no
record for the Telephone type that you specified in
your Data Load Part 1 parameters.
Update Telephone Number
Update E-mail address
Yes
If an incoming record is matched to an existing
Y
person record in the production database, RCRTPxx
loads all financial aid data from the incoming record. N
RCRTPxx does not update populated fields on an
existing person record.RCRTPxx updates the Email Address if you enter Y and there is no record
for the E-mail type that you specified in your Data
Load Part 1 parameters.
Update E-mail Address
If an incoming record is matched to an existing
Y
person record in the production database, RCRTPxx
loads all financial aid data from the incoming record. N
RCRTPxx does not update populated fields on an
existing person record. Social Security Numbers are
updated on an existing person record if it is blank
and you enter Y for this field.
Update Social Security Number
Update Social Security
Number
Yes
Values
Don’t Update Telephone Number
Don’t Up-date E-mail Address
Don’t Update SS Number
Note
Separate files are create for the output and output is only produced as required except for the
.lis and .log files. This means, for example, if you did not request the Need Analysis
Discrepancy or NSLDS Discrepancy Report, there would be no rcrtpxx_nnnnn_need.lis or
„
rcrtpxx_nnnnn_nslds.lis output.
18-35
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
The following describes the possible output from this process.
Rcrtpxx_nnnnn.lis
Rcrtpxx_nnnnn.log
Rcrtpxx_nnnnn_apps.lis
Rcrtpxx_nnnnn_need.lis
Rcrtpxx_nnnnn_nslds.lis
Rcrtpxx_nnnnn_errs.lis
Report Control Listing
Log file
Student Listing
Discrepancy Report (Need Analysis)
NSLDS Discrepancy Report
Errors Listing
Financial Aid Data Load, Part 3 Report Sample (Student Listing)
Aid Year: 0506
Data Source Code: EDE
Load Opt:
ONLY for matched students with
(for Need
current application records for
Analysis)
this year.
Load as current records
NAME
----------------------------------Blattner, Studentoo L.
Blattner, Studentoo L.
Blattner, Studentpp D.
Blattner, Studentpp D.
Blattner, Studentqq A.
Blattner, Studentqq A.
Blattner, Studentrr M.
Blattner, Studentrr M.
Blattner, Studentss M.
Blattner, Studentss M.
Blattner, Studenttt D.
Blattner, Studenttt D.
Blattner, Studentuu L.
Blattner, Studentuu L.
Blattner, Studentvv G.
Blattner, Studentvv G.
Blattner, Studentnn A.
Blattner, Studentnn A.
ID NUMBER
--------200506318
200506318
200506319
200506319
200506320
200506320
200506321
200506321
200506322
200506322
200506323
200506323
200506324
200506324
200506325
200506325
200506317
200506317
BANNER University
2005-2006 FA Dataload Part 3
Student Listing
SOURCE
------EDE
ISIR
EDE
ISIR
EDE
ISIR
EDE
ISIR
EDE
ISIR
EDE
ISIR
EDE
ISIR
EDE
ISIR
EDE
ISIR
RCRAPP-CURRENT
-------------Y
N
Y
N
Y
N
Y
N
Y
N
Y
N*
Y
N
Y
N
Y
N*
Run Date: 16-MAR-2005 16:36:30
RPT name: RCRTP06
Page:
1
NSLDS-CURRENT
------------Y
Y
Y
Y
Y
Y
Y
Y
Y
* = Duplicate transaction number
End of Applications Report
18-36
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Data Load, Part 3 Report Sample (Discrepancy Report)
Aid Year: 0506
Data Source Code: EDE
Load Opt:
ONLY for matched students with
(for Need
current application records for
Analysis)
this year.
Load as current records
BANNER University
2005-2006 FA Dataload Part 3
Discrepancy Report
Run Date: 16-MAR-2005 16:36:30
RPT name: RCRTP06
Page:
1
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentoo L.
200506318
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------PARENTS' CONTRIBUTION:
0
SAR TRAN NO:
01
02
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentpp D.
200506319
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------PARENTS' CONTRIBUTION:
0
SAR TRAN NO:
01
02
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentqq A.
200506320
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------SAR TRAN NO:
01
02
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentrr M.
200506321
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------SAR TRAN NO:
01
02
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentss M.
200506322
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------PELL EFC:
32521
STUDENT'S CONTRIBUTION:
35
PARENTS' CONTRIBUTION:
32486
SAR TRAN NO:
01
02
18-37
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Aid Year: 0506
Data Source Code: EDE
Load Opt:
ONLY for matched students with
(for Need
current application records for
Analysis)
this year.
Load as current records
BANNER University
2005-2006 FA Dataload Part 3
Discrepancy Report
Run Date: 16-MAR-2005 16:36:30
RPT name: RCRTP06
Page:
2
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentvv G.
200506325
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------SAR TRAN NO:
01
02
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studenttt D.
200506323
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------PARENTS' CONTRIBUTION:
0
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentuu L.
200506324
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------SAR TRAN NO:
01
02
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Blattner, Studentnn A.
200506317
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------PELL EFC:
0
STUDENT'S CONTRIBUTION:
0
PARENTS' CONTRIBUTION:
0
LAST NAME:
BLATTNER
SMYTHE
End of Discrepancy Report
18-38
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Data Load, Part 3 Report Sample (NSLDS Discrepancy Report)
Aid Year: 0506
Data Source Code: EDE
Load Opt:
ONLY for matched students with
(for Need
current application records for
Analysis)
this year.
Load as non-current records
BANNER University
2005-2006 FA Dataload Part 3
NSLDS Discrepancy Report
Run Date: 31-MAY-2005 11:51:21
RPT name: RCRTP06
Page:
1
NAME
ID NUMBER
-------------------------------------------------------------------------------------------------- --------Rucker, Test4002 R.
517004002
CURRENT RECORD
NEW DATA RECORD
----------------------------------------------------------AGGREGATE SUB OUT PRIN BAL:
1000
2000
End of NSLDS Discrepancy Report
Financial Aid Data Load, Part 3 Report Sample (Errors Listing)
Aid Year: 0506
Data Source Code: CSS
Load Opt:
ONLY for matched students with
(for Need
current application records for
Analysis)
this year.
NAME
ID NUMBER
----------------------------------- --------Blattner, Maxine F.
A00034039
SPBPERS API - Citizen Code is invalid.
18-39
Banner Financial Aid 8.3
User Guide
Reports and Processes
BANNER University
2005-2006 FA Dataload Part 3
Errors Listing
SOURCE
------CSS
STATUS
-----N
ROTIDEN PIDM
-----------14711
Run Date: 26-MAY-2005 15:40:49
RPT name: RCRTP06
Page:
1
*** Student not loaded ***
January 2009
Financial Aid Data Load, Part 3 Report Sample (Report Control Listing)
Aid Year: 0506
BANNER University
Data Source Code: EDE
2005-2006 FA Dataload Part 3
Load Opt:
ONLY for matched students with
(for Need
current application records for
Analysis)
this year. Load as current records
* * * REPORT CONTROL INFORMATION * * *
REPORT NAME..................................................: RCRTP06
VERSION......................................................: 7.2
REPORT SEQUENCE NUMBER.......................................: 36019
AID YEAR.....................................................: 0506
DATA SOURCE CODE.............................................: EDE
LOAD OPTION for Need Analysis................................: 1
PRINT NSLDS DISCREPANCY REPORT...............................: Y
PRINT NEED ANALYSIS DISCREPANCY REPORT.......................: Y
LOAD RECRUITING RECORDS......................................: Y
RECALCULATE NEED.............................................: N
NSLDS OUTPUT APPLICATION ID..................................:
NSLDS OUTPUT SELECTION ID....................................:
NSLDS OUTPUT CREATOR ID......................................:
RUN USER ID for NSLDS OUTPUT USER ID.........................: KBLATTNE
LOAD ISIR RECORDS............................................: Y
LOAD VA DATA.................................................: Y
BATCH OR ONLINE..............................................: B
ONLINE PIDM PARAMETER........................................:
UPDATE POSTAL ADDRESS........................................: Y
UPDATE TELEPHONE NUMBER......................................: Y
UPDATE EMAIL ADDRESS.........................................: Y
UPDATE SOCIAL SECURITY NUMBER................................: Y
LINE COUNT...................................................: 55
Primary MDE..................................................: EDE
The following totals are for Need Analysis Data ONLY
Number of NEW people processed...............................: 0
Number of RENEWED (1st record for this year) people processed: 0
Number of MATCHED (subsequent record) people processed.......: 9
Total number of people processed.............................: 9
Number of ISIRs added........................................: 9
Number of ISIRs added for existing transactions..............: 2
Number of people who had NSLDS data 'Tran 01' Dropped........: 9
Number of people who had NSLDS data added....................: 9
RORSTAT records added........................................: 0
Application records locked...................................: 0
Application records skipped because LOAD OPTION 3 selected...: 0
Application records skipped because of Oracle/API errors.....: 0
Completion time..............................................: 16:36:37
18-40
Banner Financial Aid 8.3
User Guide
Reports and Processes
Run Date: 16-MAR-2005 16:36:30
RPT name: RCRTP06
Page:
1
January 2009
ISIR Correction/Request Process (REBCDxx)
This process creates a flat file of EDE corrections and requests for ISIRs for transmission to the central processor.
Description
To create correction records for EDE, you must activate Pell corrections on the Institutional Options form
(ROAINST) and set the Pell Corrections Field in the Key Block on the Need Analysis form (RNANAxx) to Y. To
complete the logging process for need analysis changes, you also still need to run RLRLOGG or submit the
RLBLOGG job through Job Submission. Pell corrections pending submission to the Central Processing System
(CPS) can be displayed on the ISIR Correction/Request form (REACORR). Unnecessary corrections can be
deleted here and missing or incorrect Pell IDs can be changed. The actual data that you send to the CPS cannot be
changed on this form. Page two of the REACORR form can be used to request duplicate ISIRs for individual
students and also to report Institution Changes. All three types of changes (that is, History Corrections, Institution
Changes, and Duplicate Requests) are handled by the REBCDxx program.
REBCDxx will create two output files if necessary: (1) CORRxxIN.DAT will contain the history corrections, if any
are ready to process; (2) and DUPRxxIN.DAT will contain the duplicate ISIR requests, if any are ready to process.
The correction records are stored in the ROBALOG table as are all logged records. After the records are extracted
to create the data file, a flag is set on the ROBALOG record to indicate that the correction has already been
transmitted. This prevents corrections from being retransmitted each time you run the process. The ROBALOG
records are not physically deleted from the table. The flag that is used is actually the EDE Date Sent. This allows
the process to recreate correction batches at a later date if necessary. For example, if you lost the file created by
REBCDxx before actually transmitting the batch to the CPS, you can run the REBCDxx program again but with
different parameters. This time, set the Resend Previous Processed Records parameter to Y and the Resend for Date
parameter to the date you originally created the batch. The process will still find the corrections in ROBALOG for
that date and recreate the batch.
Parameters
18-41
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Resend Prev.
Processed Records
Yes
This parameter enables you to indicate whether or
not you want to include previously transmitted
corrections in the file.
Y
Resend Prev. Processed Records
N
Do Not Resend (default)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
18-42
Required?
Description
Values
Resend for Prior Date
No
If you entered a Y for the Resend Prev. Processed
Records parameter, this parameter identifies which
records to send when you enter the send date of the
previously processed records.
DD-MMM-YYYY
Application ID
No
General area for which the selection ID was defined. Application Inquiry form (GLIAPPL)
Selection ID
No
Code that identifies the sub-population to work with.
Creator ID
No
ID of the person creating the sub-population rules.
User ID
No
ID of the person using the sub-population rules.
Resend for
Prior Date/Hour
No
If the Resend Prev. Processed Records parameter is
set to Y and there are two or more batches for that
day, enter a value to represent the hour for this
parameter. Otherwise, all batches are selected.
Resend for
Prior Date/Minute
No
If the Resend Prev. Processed Records parameter is 00 - 59
set to Y and there are two or more batches for that
day, enter a value to represent the minute. Otherwise,
all batches are selected.
Send with Discrepant
Trans. #’s
Yes
Send corrections when the current ISIR transaction Y
number differs from the number on Applicant Status.
N
Banner Financial Aid 8.3
User Guide
Reports and Processes
00 - 23
Send with Discrepant Trans #’s
Do Not Send
January 2009
Parameters (cont) Name
Processing Type
Required?
Description
Values
Yes
This parameter works with the Send Indicator field
on the REACORR form and enables you to extract
corrections by the type of correction, that is,
Correction, Institution Change, and Housing Code
Change. You can use this parameter with or without
a population selection.
A
All correction transactions,
including Institution and Housing
Code changes (Default)
B
Institution and Housing Code
changes only, no other correction
transactions
C
All corrections except Institution
and Housing Code changes
D
All corrections including
Institution Changes, no Housing
Code changes
Always extract Institution changes for financial aid
applicants with a check in the Send Indicator field
on the REACORR form regardless of whether or not
a population selection is used or if the student is
included in a population selection when the
Processing Type parameter is A, B, D, or I.
18-43
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Federal School Code
Required?
Description
No
This parameter limits the corrections extracted to the
Federal School Code and validates the school code
to the student transaction being corrected.
Values
REBCD09 checks the Federal School Codes on the
EDE record being corrected and compares them to
the values that exist for the Federal School Codes
(on the Defaults window and Campus/EDE window)
when selecting the Federal School Code for the EDE
correction record.
This does not pertain to institutional code changes
and housing code changes entered directly on the
REACORR form. When using this parameter, it is
suggested that you set the Processing Type to C for
Corrections Only so that you don't also extract
institutional code or housing code changes with a
different Federal School Code.
Processing Type
(continued)
Always extract Housing Code changes for financial
aid applicants with a check in the Send Indicator
field on the REACORR form regardless of whether
or not a population selection is used or if the student
is included in a population selection when the
Processing Type parameter is A, B, E, or H.
E
All corrections including Housing
Code changes, no Institution
changes
H
Housing Code Changes only, no
other corrections nor Institution
changes
Never extract Institution changes for financial aid
applicants when the Processing Type parameter is C, I
E, or H regardless of the value of the Send Indicator
field on the REACORR form.
Never extract Housing Code changes for financial
aid applicants when the Processing Type parameter
is C, D, or I regardless of the value of the Send
Indicator field on the REACORR form.
18-44
Banner Financial Aid 8.3
User Guide
Reports and Processes
Institution Changes only, no other
corrections nor Housing Code
Changes
Note: The Send Indicator field on the
REACORR form is checked
automatically for those records
without a SPRIDEN ID or an SSN on
RORSTAT or SPBPERS.
January 2009
ISIR Correction/Request Process Sample
Performing Cobol program REBCD03 ...
Selecting
Selecting
Selecting
Selecting
ROBALOG
ROBALOG
ROBALOG
ROBALOG
institution changes...
housing changes...
history corrections...
duplicate requests...
Report Name..................REBCD03
Program Version..............5.3
One Up Number ...............786793
Aid Year ....................0203
Resend Prev.Processed Recs...N
Resend for Prior Date .......
Application ID ..............FINAID
Selection ID.................0203_APPS
Creator ID...................SMAGRONE
User ID......................SMAGRONE
Resend for Prior Date/Hour...
Resend for Prior Date/Minute.
Send with Discrepant Trans #.N
Date and time stamp
for DATE SENT
DATE
= 17-MAY-2002
Hour
= 14
Minute
= 51
Inst.Change requests processed = 00000
Corrections processed = 00068
Duplicate requests processed = 00000
Change/correction records written = 00012
Duplicate requests written = 00000
Connected.
18-45
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
CAL MIS Extract Process (RERCALX)
This process extracts data from Banner and populates two flat files, Applicant Data (RERCALXA.dat) and Applicant
Detail Data (RERCALXD.dat).
Description
The first flat file (RERCALXA.dat) contains the Financial Aid Applicant Data Elements and the second flat file
(RERCALXD.dat) contains the Financial Aid Award Data Elements.
Parameters
18-46
Name
Required?
Description
District College
Identifier
Yes
This is the three-character District College Indicator
for the MIS RX record.
Aid Year Code
Yes
This field identifies the Banner Aid Year Code for
which the process is extracting data.
Summer Term Code
No
This field identifies the Term Code used for the
Summer session of the aid year identified in
Parameter 02. Code 5 will be placed in the extract for
this term.
Fall Term Code
No
This field identifies the Term Code used for the Fall
term of the aid year identified in Parameter 02. Code
7 will be placed in extract for this term.
Winter Term Code
No
This field identifies the Term Code used for the
Winter term of the aid year identified in Parameter
02. Code 1 will be placed in extract for this term.
Spring Term Code
No
This field identifies the Term Code used for the
Spring term of the aid year identified in Parameter
02. Code 3 will be placed in extract for this term.
Summer Quarter
No
This field identifies the Term Code used for the
Summer Quarter of the aid year. Code 6 will be
placed in extract for this term.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
January 2009
Parameters (cont)
Name
Required?
Description
Fall Quarter
No
This field identifies the Term Code used for the Fall
Quarter of the aid year. Code 8 will be placed in
extract for this term.
Winter Quarter
No
This field identifies the Term Code used for the
Winter Quarter of the aid year. Code 2 will be placed
in extract for this term.
Spring Quarter
No
This field identifies the Term code used for the
Spring Quarter of the aid year. Code 4 will be placed
in extract for this term.
Report Option
Yes
This is the option to print an unformatted dump.
Valid values: Y (prints an unformatted dump of the
data that exists in the flat files), N (does not provide
any report output, just the flat file -- default).
Y
Yes
N
No (Default)
1 - 360
Budget Category Field
No
This is the field the budget category data is stored in
on the RORUSER form. Correct values: 1 - 360.
Campus Code
No
This field identifies the Campus Code being run.
Offered, Accepted,
Paid Amt SF01
Yes
This parameter identifies which field will be
referenced when populating the SF01 Student
Applicant Status.
Offered, Accepted,
Paid Amt SF22
18-47
Banner Financial Aid 8.3
User Guide
Reports and Processes
Yes
This parameter identifies which field will be used to
populate the detail record RERCALXD.dat with the
Student-Aid-Amount-Received.
Values
O
Offered
A
Accepted
P
Paid Amount
O
Offered
A
Accepted
P
Paid Amount
January 2009
Parameters (cont)
Name
Required?
Description
Detail Code for BOGW
Code BA
No
This identifies which Detail Code a school uses to
identify BOGW (Board of Governors Enrollment
Fee Waiver) used to populate SF21 when handled as
an exemption. BA = BOGW-Method A-? (unknown
base).
Values
Note: Leave this and the following parameters blank
if your BOGW funds are awarded as part of the
student’s package.
Detail Code for
BOGW Code B1
No
This identifies which Detail Code a school uses to
identify BOGW (Board of Governors Enrollment
Fee Waiver) used to populate SF21 when handled as
an exemption. B1 = BOGW-Method A-1 based on
TANF recipient status.
Detail Code for
BOGW Code B2
No
This identifies which Detail Code a school uses to
identify BOGW (Board of Governors Enrollment
Fee Waiver) used to populate SF21 when handled as
an exemption. B2 = BOGW-Method A-2 based on
SSI recipient status.
Detail Code for BOGW
Code B3
No
This identifies which Detail Code a school uses to
identify BOGW (Board of Governors Enrollment
Fee Waiver) used to populate SF21 when handled as
an exemption. B3 = BOGW-Method A-3 based on
general assistance recipient status.
No
This identifies which Detail Code a school uses to
identify BOGW (Board of Governors Enrollment
Fee Waiver) used to populate SF21when handled as
an exemption. BB = BOGW-Method B based on
income standards.
Not used at this time
Detail Code for BOGW
Code BB
18-48
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont)
Name
Required?
Description
Values
Detail Code for
BOGW Code BC
No
This identifies which Detail Code a school uses to
identify BOGW (Board of Governors Enrollment
Fee Waiver) used to populate SF21 when handled as
an exemption. BC = BOGW-Method C based on
financial need.
Application ID
No
General area for which the selection ID was defined. Application Inquiry form (GLIAPPL)
Selection ID
No
Code that identifies the sub-population to work with.
Creator ID
No
ID of the person creating the sub-population rules.
User ID
No
ID of the person using the sub-population rules.
Detail Code for BOGW
code F1
No
Identifies which Detail Code a school uses to
identify the BOGW (Board of Governors
Enrollment Fee Waiver) used to populate SF21.
This is the F1 code for Fee Waiver – Dependent
(children) of Deceased Law Enforcement/Fire
Suppression (Subject to Group C edits)
Detail Code for BOGW
code F2
No
Identifies which Detail Code a school uses to
identify the BOGW (Board of Governors
Enrollment Fee Waiver) used to populate SF21.
This is the F2 code for Fee Waiver – Dependent
(surviving spouse and children) of a deceased or
disabled member of CA National Guard (Subject to
Group C edits)
Detail Code for BOGW
code F3
No
Identifies which Detail Code a school uses to
identify the BOGW (Board of Governors
Enrollment Fee Waiver) used to populate SF21.
This is the F3 code for Fee Waiver – Dependent of
(children) a deceased or disabled Veteran (Subject to
Group C edits)
18-49
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont)
Name
Required?
Description
Detail Code for BOGW
code F4
No
Identifies which Detail Code a school uses to
identify the BOGW (Board of Governors
Enrollment Fee Waiver) used to populate SF21.
Values
This is the F4 code for Fee Waiver – Dependent of
(children) of Congressional Medal of Honor
recipient (CMH) or CMH recipient (Subject to
Group C edits)
Detail Code for BOGW
code F5
No
Identifies which Detail Code a school uses to
identify the BOGW (Board of Governors
Enrollment Fee Waiver) used to populate SF21.
This is the F5 code for Fee Waiver – Dependent of
(surviving spouse and children) of Deceased victims
of September 11, 2001 terrorist attack. (Subject of
Group C edits)
18-50
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 COD Print Process (RERCD09)
The COD Print Process prints a report of Pell, ACG, SMART, or Direct Loan origination and/or disbursement
Document IDs which have been sent to COD. You can select specific Document IDs, all Document IDs for a
specific date, or all Document IDs for the aid year.
Description
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Fund Type
Yes
Enter the fund type that you want to report.
AL All fund types - Pell, Direct Loan,
ACG, and SMART (default)
AG All grants
PL Pell Grant
DL Direct Loan
AC ACG Grant
SM SMART Grant
Fund Code
No
Use one or more fund codes if you want to limit the
report output by fund. The fund codes must be valid
for the selected Fund Type parameter.
Fund Code (RFRBASE)
Origination Report
Yes
Use this parameter to produce a listing of either sent
or unsent origination records.
S
Sent origination records
U
Unsent origination records
N
None
Origination Document
ID
18-51
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
Use this parameter to produce a listing of origination
records by Document ID. You can enter multiple
Document IDs for this parameter.
Document ID (REICODD)
January 2009
Parameters (cont) Name
Disbursement Report
Required?
Description
Values
Yes
Use this parameter to produce a listing of
disbursements.
Y
Yes, produce the disbursement
report
N
No, do not produce the
disbursement report
Disbursement Document No
ID
Use this parameter to produce a listing of
disbursement records by Document ID. You can
enter multiple Document IDs for this parameter.
Beginning Date Sent
No
Create the beginning of listing by the Document ID
send date. If you do not specify a date range with one
of the preceding parameters such as the Origination
Report parameter, the report lists all records for the
year.
Ending Date Sent
No
Create the end of a listing by the Document ID send
date. If you do not specify a date range with one of
the preceding parameters such as the Origination
Report parameter, the report lists all records for the
year.
Application ID
No
Application code of the population selection.
Document ID (REICODD)
Application Inquiry form (GLIAPPL)
If you enter a value for this parameter, you must also
enter a value for the Selection ID, Creator ID, and
User ID.
Selection ID
18-52
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application ID, User ID, and Creator
ID.
January 2009
Parameters (cont) Name
Required?
Description
Values
Creator ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID, User ID, and Application ID.
User ID
No
The ID of the person using the subpopulation rule. If
you enter a value for this parameter, you must also
enter a value for the Selection ID, Application ID,
and Creator ID parameters.
Pell Origination Report - Sent Origination Records
30-MAR-2007 10:17:38 AM
BANNER University
1
Aid Year: 0809
2008-2009 Pell Origination Report
RERCD08
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-08T08:43:10.0070488331
Origination ID
Name
517006010 517006010RU200800011000 RUCKER, TEST6010 R.
517006001 517006001RU200800011000 RUCKER, TEST6001 K.
*****
ID
Document ID: 2007-03-27T10:39:20.0070488331
Origination ID
Name
517003052 517003052RU200800011000 RUCKER, TEST3052 J.
517003066 517003066RU200800011000 RUCKER, TEST3066 L.
Total of All Documents:
18-53
Date: 08-MAR-2007
Orig
Seq
1
3
Attend
Cost
15350.00
15350.00
Recs Sent: 2
Ver
Stat
V
V
Date: 27-MAR-2007
Orig
Seq
2
1
Attend
Cost
15350.00
15350.00
Amt
Paid
2025.00
400.00
Amt
Due
4050.00
400.00
Total:
Status
S
S
Recs Sent: 2
Ver
Stat
V
V
Amt
Paid
1100.00
2025.00
Amt
Due
2200.00
4050.00
4450.00
Total:
6250.00
Status
A
C
10700.00
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
ACG Origination Report - Sent Origination Records
30-MAR-2007 10:17:38 AM
BANNER University
1
Aid Year: 0809
2008-2009 ACG Origination Report
RERCD08
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-08T08:43:10.0070488331
Award ID
Name
517006010 517006010A08000110001
517006001 517006001A08000110001
*****
ID
RUCKER, TEST6010 R.
RUCKER, TEST6001 K.
Document ID: 2007-03-27T10:39:20.0070488331
Award ID
Name
517003052 517003052A08000110001
517003066 517003066A08000110001
Total of All Documents:
RUCKER, TEST3052 J.
RUCKER, TEST3066 L.
Date: 08-MAR-2007
Fund
Code
ACG
ACG
Orig
Seq
1
1
Date: 27-MAR-2007
Fund
Code
ACG2
ACG
Orig
Seq
1
2
Recs Sent: 2
Amt
Paid
375.00
750.00
Amt
Due
750.00
750.00
Total:
Status
S
S
Recs Sent: 2
Amt
Paid
1300.00
750.00
Amt
Due
1300.00
750.00
1500.00
Total:
2050.00
Status
A
A
3550.00
SMART Origination Report - Sent Origination Records
30-MAR-2007 10:17:38 AM
BANNER University
1
Aid Year: 0809
2008-2009 SMART Origination Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-08T08:43:10.0070488331
Award ID
Name
517006010 517006010T08000110001
517006001 517006001T08000110001
*****
ID
Document ID: 2007-03-27T10:39:20.0070488331
Award ID
Name
517003052 517003052T08000110001
517003066 517003066T08000110001
Total of All Documents:
18-54
RUCKER, TEST6010 R.
RUCKER, TEST6001 K.
RUCKER, TEST3052 J.
RUCKER, TEST3066 L.
Date: 08-MAR-2007
Fund
Code
SMART3
SMART3
Orig
Seq
1
1
Date: 27-MAR-2007
Fund
Code
SMART3
SMART4
Orig
Seq
1
2
Recs Sent: 2
Amt
Paid
2000.00
1000.00
Amt
Due
4000.00
4000.00
Total:
Status
S
S
Recs Sent: 2
Amt
Paid
2000.00
2000.00
Amt
Due
4000.00
4000.00
8000.00
Total:
8000.00
Status
A
A
16000.00
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Direct Loan Origination Report - Sent Origination Records
30-MAR-2007 10:17:38 AM
BANNER University
1
Aid Year: 0809
2008-2009 DL Origination Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-08T08:43:10.0070488331
Loan ID
517006010 517006010S08G80006001
517006001 517006001U08G80006001
*****
ID
Name
RUCKER, TEST6010 R.
RUCKER, TEST6001 K.
Document ID: 2007-03-27T10:39:20.0070488331
Loan ID
517003052 517003052S08G80006001
517003066 517003066U08G80006001
Name
RUCKER, TEST3052 J.
RUCKER, TEST3066 L.
Date: 08-MAR-2007
Fund
Code
DIRECT
DLUNSB
Loan
Type
S
U
Date: 27-MAR-2007
Fund
Code
DIRECT
DLUNSB
Loan
Type
S
U
Recs Sent: 2
Amt
Paid
1313.00
2000.00
Total:
Loan
Amt
2625.00
4000.00
Status
S
S
Recs Sent: 2
Amt
Paid
1313.00
2000.00
Loan
Amt
2625.00
4000.00
6625.00
Total:
6625.00
Status
A
A
Pell Origination Report - Unsent Origination Records
30-MAR-2007 10:18:29 AM
BANNER University
1
Aid Year: 0809
2008-2009 Pell Origination Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------ID
Origination ID
Name
Orig
Attend
Ver
Amt
Amt
Status
Seq
Cost
Stat
Paid
Due
586070308 586070308AP200862000400 APNGUYEN, A308 S.
1
15350.00 V
4050.00
698765432 698765432AN200862001600 ANDERSON, ALBERT T.
3
19400.00
3500.00
165000001 165000001AN200862001600 ANDREAS, ADAM
1
19400.00 W
3300.00
165060011 165060011AN200800011000 ANDREAS, FISAP 6-11 A.
1
19400.00 V
3600.00
586070309 586070309BP200862000400 BPNGUYEN, B309 B.
2
17400.00 V
4050.00
511080919 511080919LA200860000500 QUTHERFORD-LAIRD, SAMANTHA
1
30900.00
3749.89
208000175 208000175ED200800011000 EDE05165, XXXXXXXXXXXX A.
1
950.00 V
950.00
Total Amount Due for All Records:
18-55
Banner Financial Aid 8.3
User Guide
Reports and Processes
23199.89
January 2009
ACG Origination Report - Unsent Origination Records
30-MAR-2007 10:18:29 AM
BANNER University
1
Aid Year: 0809
2008-2009 ACG Origination Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------ID
Award ID
Name
Fund
Orig
Amt
Amt
Status
Code
Seq
Paid
Due
586070308 586070308A08000110001
APNGUYEN, A308 S.
ACG
1
750.00
698765432 698765432A08000110001
ANDERSON, ALBERT T.
ACG
3
750.00
165000001 165000001A08000110002
ANDREAS, ADAM
ACG
1
750.00
165060011 165060011A08000110001
ANDREAS, FISAP 6-11 A.
ACG2
1
1300.00
586070309 586070309A08000110001
BPNGUYEN, B309 B.
ACG
2
750.00
511080919 511080919A08000110002
QUTHERFORD-LAIRD, SAMANTHA
ACG2
1
1300.00
208000175 208000175A08000110001
EDE05165, XXXXXXXXXXXX A.
ACG2
1
1300.00
Total Amount Due for All Records:
6900.00
SMART Origination Report - Unsent Origination Records
30-MAR-2007 10:18:29 AM
BANNER University
1
Aid Year: 0809
2008-2009 SMART Origination Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------ID
Award ID
Name
Fund
Orig
Amt
Amt
Status
Code
Seq
Paid
Due
586070308 586070308T08000110001
APNGUYEN, A308 S.
SMART
1
4000.00
698765432 698765432T08000110001
ANDERSON, ALBERT T.
SMART
3
4000.00
165000001 165000001T08000110002
ANDREAS, ADAM
SMART
1
4000.00
165060011 165060011T08000110001
ANDREAS, FISAP 6-11 A.
SMART4
1
4000.00
586070309 586070309T08000110001
BPNGUYEN, B309 B.
SMART
2
4000.00
511080919 511080919T08000110002
QUTHERFORD-LAIRD, SAMANTHA
SMART4
1
4000.00
208000175 208000175T08000110001
EDE05165, XXXXXXXXXXXX A.
SMART4
1
4000.00
Total Amount Due for All Records:
18-56
Banner Financial Aid 8.3
User Guide
Reports and Processes
28000.00
January 2009
Direct Loan Origination Report - Unsent Origination Records
30-MAR-2007 10:18:29 AM
BANNER University
1
Aid Year: 0809
2008-2009 DL Origination Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------ID
Loan ID
Name
Fund
Loan
Amt
Amt
Status
Code
Type
Paid
Due
586070308 586070308S08000110001
APNGUYEN, A308 S.
DIRECT
S
2625.00 N
698765432 698765432U08000110001
ANDERSON, ALBERT T.
DLUNSB
U
4000.00 R
165000001 165000001S08000110002
ANDREAS, ADAM
DIRECT
S
3500.00 R
165060011 165060011P08000110001
ANDREAS, FISAP 6-11 A.
DLPLUS
P
6000.00 N
586070309 586070309P08000110001
BPNGUYEN, B309 B.
DGPLUS
G
6500.00 R
511080919 511080919U08000110002
QUTHERFORD-LAIRD, SAMANTHA
DLUNSB
U
4000.00 R
208000175 208000175S08000110001
EDE05165, XXXXXXXXXXXX A.
DIRECT
S
5500.00 N
Total Amount Due for All Records:
32125.00
Pell Disbursement Report
30-MAR-2007 10:15:53 AM
BANNER University
1
Aid Year: 0809
2008-2009 Pell Disbursement Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-11T18:28:59.0065167086
Origination ID
530910001 530910001TE200804000400
530910002 530910002TE200804000400
530910009 530910009TE200804000400
*****
ID
Name
TEST1, STUDENT P.
TEST2, STUDENT P.
TEST9, STUDENT C.
Document ID: 2007-03-12T17:30:01.0065167086
Origination ID
530910002 530910002TE200804000400
530910003 530910003TE200804000400
530910008 530910008TE200804000400
Name
TEST2, STUDENT P.
TEST3, STUDENT P.
TEST8, STUDENT C.
Total Sent for All Documents:
7150.00
Total Accepted for All Documents:
5125.00
18-57
Banner Financial Aid 8.3
User Guide
Reports and Processes
Date: 30-MAR-2007
Fund
Code
PELL
PELL
PELL
Term
Code
200810
200820
200810
Date: 30-MAR-2007
Fund
Code
PELL
PELL
PELL
Term
Code
200810
200810
200810
Recs Sent: 3 Total Sent:
Disb
No
01
01
01
Disb
Seq
01
02
01
3600.00 Total Accepted:
Sign
Ind
P
N
P
Recs Sent: 3 Total Sent:
Disb
Ref
01
01
01
Disb
Seq
03
01
01
Sign
Ind
N
P
P
Disb
Amount
2025.00
450.00
2025.00
Status
A
A
R
3550.00 Total Accepted:
Disb
Amount
500.00
2025.00
2025.00
Status
A
A
A
1575.00
Accepted
Amount
2025.00
450.00
2025.00
3550.00
Accepted
Amount
500.00
2025.00
2025.00
January 2009
ACG Disbursement Report
30-MAR-2007 10:15:53 AM
BANNER University
1
Aid Year: 0809
2008-2009 ACG Disbursement Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-11T18:28:59.0065167086
Award ID
530910001 530910001A08000110001
530910002 530910002A08000110001
530910009 530910009A08000110001
*****
ID
Name
TEST1, STUDENT P.
TEST2, STUDENT P.
TEST9, STUDENT C.
Document ID: 2007-03-12T17:30:01.0065167086
Award ID
530910002 530910002A08000110001
530910003 530910003A08000110001
530910008 530910008A08000110001
Name
TEST2, STUDENT P.
TEST3, STUDENT P.
TEST8, STUDENT C.
Total Sent for All Documents:
1900.00
Total Accepted for All Documents:
1250.00
Date: 30-MAR-2007
Fund
Code
ACG
ACG
ACG2
Term
Code
200810
200810
200820
Date: 30-MAR-2007
Fund
Code
ACG2
ACG2
ACG
Term
Code
200820
200810
200810
Recs Sent: 3 Total Sent:
Disb
No
01
01
01
Disb
Seq
01
02
01
975.00 Total Accepted:
Sign
Ind
P
N
P
Disb
Amount
375.00
50.00
650.00
Recs Sent: 3 Total Sent:
Disb
Ref
01
01
01
Disb
Seq
03
01
01
Status
A
A
R
925.00 Total Accepted:
Sign
Ind
N
P
P
Disb
Amount
100.00
650.00
375.00
Status
A
A
A
325.00
Accepted
Amount
375.00
50.00
650.00
925.00
Accepted
Amount
100.00
650.00
375.00
SMART Disbursement Report
30-MAR-2007 10:15:53 AM
BANNER University
1
Aid Year: 0809
2008-2009 SMART Disbursement Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------*****
ID
Document ID: 2007-03-11T18:28:59.0065167086
Award ID
530910001 530910001T08000110001
530910002 530910002T08000110001
530910009 530910009T08000110001
*****
ID
Name
TEST1, STUDENT P.
TEST2, STUDENT P.
TEST9, STUDENT C.
Document ID: 2007-03-12T17:30:01.0065167086
Award ID
530910002 530910002T08000110001
530910003 530910003T08000110001
530910008 530910008T08000110001
Name
TEST2, STUDENT P.
TEST3, STUDENT P.
TEST8, STUDENT C.
Total Sent for All Documents:
5000.00
Total Accepted for All Documents:
3000.00
18-58
Banner Financial Aid 8.3
User Guide
Reports and Processes
Date: 30-MAR-2007
Fund
Code
SMART
SMART
SMART4
Term
Code
200910
200910
200920
Date: 30-MAR-2007
Fund
Code
SMART4
SMART
SMART4
Term
Code
200920
200910
200910
Recs Sent: 3 Total Sent:
Disb
No
01
01
01
Disb
Seq
01
02
01
2000.00 Total Accepted:
Sign
Ind
P
N
P
Recs Sent: 3 Total Sent:
Disb
Ref
01
01
01
Disb
Seq
03
01
01
Sign
Ind
N
P
P
Disb
Amount
2000.00
2000.00
2000.00
Status
A
A
R
3000.00 Total Accepted:
Disb
Amount
1000.00
2000.00
2000.00
Status
A
A
A
0.00
Accepted
Amount
2000.00
2000.00
2000.00
3000.00
Accepted
Amount
1000.00
2000.00
2000.00
January 2009
Direct Loan Disbursement Report
30-MAR-2007 10:15:53 AM
BANNER University
1
Aid Year: 0809
2008-2009 DL Disbursement Report
RERCD09
-----------------------------------------------------------------------------------------------------------------------------------****Document ID: 2007-03-11T18:28:59.0065167086 Date: 30-MAR-2007 Recs Sent: 3 Total Actual Sent: 1313.00 Total Actual Acpt: 1313.00
ID
Loan ID
530910001 530910001S08000110001
530910002 530910002U08000110001
530910009 530910009S08000110001
Name
TEST1, STUDENT P.
TEST2, STUDENT P.
TEST9, STUDENT C.
****Document ID: 2007-03-12T17:30:01.0065167086
ID
Loan ID
530910002 530910002P08000110001
530910003 530910003S08000110001
530910008 530910008P08000110001
TEST2, STUDENT P.
TEST3, STUDENT P.
TEST8, STUDENT C.
Total Actual Accepted for All Documents:
18-59
Banner Financial Aid 8.3
User Guide
Reports and Processes
Loan
Type
S
U
S
Term
Code
200910
200910
200920
Disb
No
01
01
01
Disb
Seq
01
02
01
Disb
Amount
1313.00
2000.00
1750.00
Status
A
2
3
Disb
Pd?
Yes
No
No
Date: 30-MAR-2007 Recs Sent: 3 Total Actual Sent: 9250.00 Total Actual Acpt: 6750.00
Name
Total Actual Sent for All Documents:
Fund
Code
DIRECT
DLUNSB
DIRECT
Fund
Code
DLPLUS
DIRECT
DGPLUS
Loan
Type
P
S
G
Term
Code
200920
200910
200910
Disb
Ref
01
01
01
Disb
Seq
03
01
01
Disb
Amount
2500.00
2750.00
4000.00
Status
R
A
A
Disb
Pd?
Yes
Yes
Yes
10563.00
8063.00
January 2009
2008-2009 Correction Error Report (RERCE09)
This process is used specifically for reporting the correction errors when the CORE09OP file is loaded.
Description
Importing EDE Correction/Rejection Records (CORE09OP message file)
This process loads ISIR correction response files showing ISIR correction processing errors. Error reports are
returned to institutions in the CORE09OP message class. The response files in this message class are not loaded
into the Banner database. During the RERCE09 import process, the files are read and a report for Record Level
(student rejects) is created. You can then use this report to determine the changes needed to correct the errors.
The CORE09OP message file contains the following type of rejected records.
• The Record Level rejects, which deal with student errors. This record includes the following information:
the SAR ID, last name, first name, error message number, and the error message text.
Warning
CORE09OP files do not contain a header or trailer record. In order for RERCE09 to recognize
the CORE09OP header-less files and associate them with an aid year, you must use the
required naming conventions. Therefore, in order for RERCE09 to process the CORE09OP
message class file, you must name the files with CORE09... or core09 in the first 6 positions. If
the CORE09OP files supplied to this process have any other name, the program will reject the
file with an error message: %Error% - Invalid file (filename). Also, since the process can no
longer write PROCESSED to the header, there is no way to prevent re-running already
processed CORE09OP files. You will need to manage this function by renaming already
processed files, or by removing the files from the $DATA_HOME/finaid directory after
processing the files. Finally, because the header information previously loaded into REBDRCT
„
is no longer available, REBDRCT for CORE09OP file processing is no longer updated.
Parameters
18-60
Name
Required?
Description
Values
Correction Error File
Yes
Enter the CORE09OP message file for this
parameter.
EDE Correction file name with
extension
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
ISIR Corr/Request Control Report (RERCRCR)
The ISIR Corr /Request Control Report lists EDE corrections and ISIR requests that were created on a specific
date.
Description
Parameters
18-61
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Activity Date
No
You can optionally enter an activity date to print
records processed on that particular date.
DD-MMM-YYYY
Activity Date/Hour
No
The ISIR Correction/Request Process (REBCDxx)
uses the system date, hour, and minute during the
batch creation of student records. All records in that
same batch use the same time stamp.
00 - 23
Activity Date/Minute
No
The ISIR Correction/Request Process (REBCDxx)
uses the system date, hour, and minute during the
batch creation of student records. All records in that
same batch use the same time stamp.
00 - 59
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
ISIR Corr/Request Control Report Sample
17-MAY-2002 03:00 PM
1
AID YEAR: 0203 Award Year 2002-2003
SAR ID
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200012 AN 01 Andreas,Lindsey
EDE
1
098
RCRAPP1_SIGNED_MTH_DAY
165200001 AN 01 Andreas,AbbeyQ.
EDE
1
078
165200001 AN 01 Andreas,AbbeyQ.
EDE
1
079
165200001 AN 01 Andreas,AbbeyQ.
EDE
1
044
165200001 AN 01 Andreas,AbbeyQ.
EDE
1
045
165200002 AN 01 Andreas,Barney
EDE
1
078
165200002 AN 01 Andreas,Barney
EDE
1
079
165200002 AN 01 Andreas,Barney
EDE
1
044
165200002 AN 01 Andreas,Barney
EDE
1
045
165200004 AN 01 Andreas,Donald
EDE
1
018
165200004 AN 01 Andreas,Donald
EDE
1
021
165200004 AN 01 Andreas,Donald
EDE
1
020
165200004 AN 01 Andreas,Donald
EDE
1
019
165200004 AN 01 Andreas,Donald
EDE
1
017
165200005 AN 01 Andreas,Evelyn
EDE
1
903
165200005 AN 01 Andreas,Evelyn
EDE
1
907
165200005 AN 01 Andreas,Evelyn
EDE
1
906
165200005 AN 01 Andreas,Evelyn
EDE
1
904
165200005 AN 01 Andreas,Evelyn
EDE
1
902
165200005 AN 01 Andreas,Evelyn
EDE
1
901
RCRAPP4_PAR_WORKSHEET_A
3000
RCRAPP4_PAR_WORKSHEET_B
3000
RCRAPP4_WORKSHEET_A
1500
RCRAPP4_WORKSHEET_B
1500
RCRAPP4_PAR_WORKSHEET_A
500
RCRAPP4_PAR_WORKSHEET_B
500
RCRAPP4_WORKSHEET_A
250
RCRAPP4_WORKSHEET_B
250
RCRAPP1_RQST_FA_FALL_THIS_YR
1
RCRAPP1_RQST_FA_SUMMER_NEXT_YR
1
RCRAPP1_RQST_FA_SPRING_NEXT_YR
1
RCRAPP1_RQST_FA_WINTER_NEXT_YR
1
RCRAPP1_RQST_FA_SUMMER_THIS_YR
1
ASSM_3
1
ASSM_6
1
ASSM_5
1
ASSM_4
1
ASSM_2
1
ASSM_1
1
18-62
NAME
SunGard Higher Education Development
Banner Financial Aid 8.3
User Guide
Reports and Processes
PAGE
RERCRCR
DATE SENT
TIME
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
January 2009
17-MAY-2002 03:00 PM
2
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200010 AN 01 Andreas,JacksonQ.
EDE
1
034
165200010 AN 01 Andreas,JacksonQ.
EDE
1
026
165200010 AN 01 Andreas,JacksonQ.
EDE
1
033
165200010 AN 01 Andreas,JacksonQ.
EDE
1
025
165200010 AN 01 Andreas,JacksonQ.
EDE
1
031
165200010 AN 01 Andreas,JacksonQ.
EDE
1
035
165200010 AN 01 Andreas,JacksonQ.
EDE
1
022
165200010 AN 01 Andreas,JacksonQ.
EDE
1
023
165200010 AN 01 Andreas,JacksonQ.
165200010 AN 01 Andreas,JacksonQ.
EDE
EDE
1
1
019
011
165200010 AN 01 Andreas,JacksonQ.
EDE
1
032
RCRAPP4_WORK_STUDY
1
RCRAPP4_S_RES_DATE_MO_YR
199501
RCRAPP4_LOAN_INT
1
RCRAPP4_LEGAL_RES_IND
1
RCRAPP4_HS_GED_RCVD
2
RCRAPP4_DRUG_OFFENSE_CONVIC
1
RCRAPP3_FATHER_HI_GRADE
2
RCRAPP3_MOTHER_HI_GRADE
2
RCRAPP1_RQST_FA_WINTER_NEXT_YR
RCRAPP1_DRIVER_LIC_NO
PA-123456789
RCRAPP1_DEGREE_BY_JULY
165200010 AN 01 Andreas,JacksonQ.
EDE
1
013
165200010 AN 01 Andreas,JacksonQ.
EDE
1
005
PAGE
RERCRCR
DATE SENT
TIME
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
18-63
Banner Financial Aid 8.3
User Guide
Reports and Processes
RCRAPP1_CITZ_IND
1
RCRAPP1_CITY
Anyplace
28-NOV-2001 14:39
January 2009
17-MAY-2002 03:00 PM
3
AID YEAR: 0203 Award Year 2002-2003
SAR ID
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200010 AN 01 Andreas,JacksonQ.
EDE
1
009
165200010 AN 01 Andreas,JacksonQ.
EDE
1
007
165200010 AN 01 Andreas,JacksonQ.
EDE
1
027
165200010 AN 01 Andreas,JacksonQ.
EDE
1
024
165200010 AN 01 Andreas,JacksonQ.
EDE
1
012
165200010 AN 01 Andreas,JacksonQ.
EDE
1
006
165200010 AN 01 Andreas,JacksonQ.
EDE
1
008
165200010 AN 01 Andreas,JacksonQ.
EDE
1
014
165200010 AN 01 Andreas,JacksonQ.
EDE
1
004
165200010 AN 01 Andreas,JacksonQ.
EDE
1
016
165200010 AN 01 Andreas,JacksonQ.
EDE
1
030
165200011 AN 01 Andreas,Kelsey
EDE
1
053
165200011 AN 01 Andreas,Kelsey
EDE
1
048
165200011 AN 01 Andreas,Kelsey
EDE
1
047
165200011 AN 01 Andreas,Kelsey
EDE
1
044
165200011 AN 01 Andreas,Kelsey
EDE
1
057
165200011 AN 01 Andreas,Kelsey
EDE
1
058
165200011 AN 01 Andreas,Kelsey
EDE
1
040
165200011 AN 01 Andreas,Kelsey
EDE
1
039
165200011 AN 01 Andreas,Kelsey
EDE
1
037
RCRAPP1_BIRTH_DATE
18-MAR-1985
RCRAPP1_ZIP
19320
RCRAPP1_TITLE
2
RCRAPP1_STAT_CODE_RES
PA
RCRAPP1_STAT_CODE_LIC
PA
RCRAPP1_STAT_CODE
PA
RCRAPP1_SSN
165990010
RCRAPP1_ALIEN_REG_NO
123456789
RCRAPP1_ADDR
4 Any Road
RCRAPP3_S_MAR_MTH_YR
199501
RCRAPP3_YR_IN_COLL_2
0
RCRAPP3_GRAD_OR_PROF
1
RCRAPP4_BUS_NET_WORTH
500
RCRAPP4_INV_NET_WORTH
500
RCRAPP4_WORKSHEET_A
500
RCRAPP1_WARD_OF_COURT
1
RCRAPP1_US_VET
1
RCRAPP1_US_INC_TAX_PD
500
RCRAPP1_US_INC
500
RCRAPP1_TAX_FORM_IND
1
18-64
NAME
SunGard Higher Education Development
Banner Financial Aid 8.3
User Guide
Reports and Processes
PAGE
RERCRCR
DATE SENT
TIME
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
January 2009
17-MAY-2002 03:00 PM
4
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200011 AN 01 Andreas,Kelsey
EDE
1
042
165200011 AN 01 Andreas,Kelsey
EDE
1
056
165200011 AN 01 Andreas,Kelsey
EDE
1
049
165200011 AN 01 Andreas,Kelsey
EDE
1
052
165200011 AN 01 Andreas,Kelsey
EDE
1
046
165200011 AN 01 Andreas,Kelsey
EDE
1
045
165200011 AN 01 Andreas,Kelsey
EDE
1
036
165200011 AN 01 Andreas,Kelsey
EDE
1
055
165200011 AN 01 Andreas,Kelsey
EDE
1
038
165200011 AN 01 Andreas,Kelsey
EDE
1
054
165200012 AN 01 Andreas,Lindsey
EDE
1
105
165200012 AN 01 Andreas,Lindsey
EDE
1
101
165200012 AN 01 Andreas,Lindsey
EDE
1
076
165200012 AN 01 Andreas,Lindsey
EDE
1
084
165200012 AN 01 Andreas,Lindsey
EDE
1
068
165200012 AN 01 Andreas,Lindsey
EDE
1
080
165200012 AN 01 Andreas,Lindsey
EDE
1
079
165200012 AN 01 Andreas,Lindsey
EDE
1
078
165200012 AN 01 Andreas,Lindsey
EDE
1
070
165200012 AN 01 Andreas,Lindsey
EDE
1
067
RCRAPP1_INC_FR_WRK
500
RCRAPP1_HAS_LEGAL_DEPEND
1
RCRAPP1_CASH_AMT
500
RCRAPP1_BORN_BEFORE_1_1_XX
1
RCRAPP4_WORKSHEET_C
500
RCRAPP4_WORKSHEET_B
500
RCRAPP4_TX_RET_FILED_IND
1
RCRAPP4_HAVE_CHILDREN
1
RCRAPP4_1040A_ELIG_IND
1
RCRAPP3_MARRIED
1
RCRAPP3_EFC_RECALC_CORR_REQ
Y
RCRAPP3_PREPARER_EIN
999009999
RCRAPP1_FATH_INC_FR_WRK
500
RCRAPP1_FAM_MEMB
9
RCRAPP4_P_RES_DATE_MO_YR
199001
RCRAPP4_PAR_WORKSHEET_C
500
RCRAPP4_PAR_WORKSHEET_B
500
RCRAPP4_PAR_WORKSHEET_A
500
RCRAPP4_PAR_TX_RET_FILED_IND
2
RCRAPP4_PAR_LEGAL_RES_IND
PAGE
RERCRCR
DATE SENT
TIME
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
18-65
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
17-MAY-2002 03:00 PM
PAGE
5
AID YEAR: 0203 Award Year 2002-2003
SAR ID
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200012 AN 01 Andreas,Lindsey
EDE
1
075
165200012 AN 01 Andreas,Lindsey
EDE
1
059
165200012 AN 01 Andreas,Lindsey
EDE
1
064
165200012 AN 01 Andreas,Lindsey
EDE
1
083
165200012 AN 01 Andreas,Lindsey
EDE
1
085
165200012 AN 01 Andreas,Lindsey
EDE
1
077
165200012 AN 01 Andreas,Lindsey
EDE
1
098
165200012 AN 01 Andreas,Lindsey
EDE
1
099
165200012 AN 01 Andreas,Lindsey
EDE
1
074
165200012 AN 01 Andreas,Lindsey
EDE
1
073
165200012 AN 01 Andreas,Lindsey
EDE
1
071
165200012 AN 01 Andreas,Lindsey
EDE
1
082
165200012 AN 01 Andreas,Lindsey
EDE
1
072
165200012 AN 01 Andreas,Lindsey
EDE
1
062
165200012 AN 01 Andreas,Lindsey
EDE
1
063
165200012 AN 01 Andreas,Lindsey
EDE
1
060
165200012 AN 01 Andreas,Lindsey
EDE
1
061
165200012 AN 01 Andreas,Lindsey
EDE
1
920
165200012 AN 01 Andreas,Lindsey
EDE
1
102
165200012 AN 01 Andreas,Lindsey
EDE
1
100
165200004 AN 01 Andreas,Donald
EDE
1
018
165200004 AN 01 Andreas,Donald
EDE
1
017
165200004 AN 01 Andreas,Donald
EDE
1
019
165200004 AN 01 Andreas,Donald
EDE
1
021
RCRAPP1_PAR_NO_EXEMPT
9
RCRAPP1_PAR_MRTL_STATUS
3
RCRAPP1_PAR_FAM_MEMB
9
RCRAPP1_PAR_CASH_AMT
500
RCRAPP1_NO_IN_COLL
9
RCRAPP1_MOTH_INC_FR_WRK
500
RCRAPP1_SIGNED_YR
2
RCRAPP1_SIGNED
A
RCRAPP1_PAR_US_INC_TAX_PD
500
RCRAPP1_PAR_US_INC
500
RCRAPP1_PAR_TAX_FORM_IND
2
RCRAPP4_PAR_BUS_NET_WORTH
500
RCRAPP4_PAR_1040A_ELIG_IND
2
RCRAPP4_MOTH_SSN
165990000
RCRAPP4_MOTH_LAST_NAME
Andreas
RCRAPP4_FATH_SSN
165009999
RCRAPP4_FATH_LAST_NAME
Andreas
RCRAPP4_EMAIL_ADDRESS
[email protected]
RCRAPP3_PREPARER_SIGN
1
RCRAPP3_PREPARER_SSN
000990000
RCRAPP1_RQST_FA_FALL_THIS_YR
3
RCRAPP1_RQST_FA_SUMMER_THIS_YR
3
RCRAPP1_RQST_FA_WINTER_NEXT_YR
3
RCRAPP1_RQST_FA_SUMMER_NEXT_YR
18-66
NAME
SunGard Higher Education Development
Banner Financial Aid 8.3
User Guide
Reports and Processes
RERCRCR
DATE SENT
TIME
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
28-NOV-2001 14:39
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
January 2009
17-MAY-2002 03:00 PM
PAGE
6
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200004 AN 01 Andreas,Donald
EDE
1
020
165200005 AN 01 Andreas,Evelyn
EDE
1
903
165200005 AN 01 Andreas,Evelyn
EDE
1
907
165200005 AN 01 Andreas,Evelyn
EDE
1
906
165200005 AN 01 Andreas,Evelyn
EDE
1
901
165200005 AN 01 Andreas,Evelyn
EDE
1
902
165200005 AN 01 Andreas,Evelyn
EDE
1
904
165200006 AN 01 Andreas,Florence
EDE
1
913
165200006 AN 01 Andreas,Florence
EDE
1
909
165200006 AN 01 Andreas,Florence
EDE
1
911
165200010 AN 01 Andreas,JacksonQ.
EDE
1
022
165200010 AN 01 Andreas,JacksonQ.
EDE
1
016
165200010 AN 01 Andreas,JacksonQ.
EDE
1
030
165200010 AN 01 Andreas,JacksonQ.
EDE
1
031
165200010 AN 01 Andreas,JacksonQ.
EDE
1
033
165200010 AN 01 Andreas,JacksonQ.
EDE
1
034
165200010 AN 01 Andreas,JacksonQ.
EDE
1
014
RCRAPP1_RQST_FA_SPRING_NEXT_YR
3
ASSM_3
1
ASSM_6
1
ASSM_5
1
ASSM_1
1
ASSM_2
1
ASSM_4
1
REJ_W
1
REJ_B
1
REJ_N
1
RCRAPP3_FATHER_HI_GRADE
3
RCRAPP3_S_MAR_MTH_YR
200101
RCRAPP3_YR_IN_COLL_2
1
RCRAPP4_HS_GED_RCVD
1
RCRAPP4_LOAN_INT
2
RCRAPP4_WORK_STUDY
2
RCRAPP1_ALIEN_REG_NO
165200010 AN 01 Andreas,JacksonQ.
EDE
1
015
165200010 AN 01 Andreas,JacksonQ.
EDE
1
003
165200010 AN 01 Andreas,JacksonQ.
EDE
1
001
RERCRCR
DATE SENT
TIME
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
18-67
Banner Financial Aid 8.3
User Guide
Reports and Processes
RCRAPP1_MRTL_STATUS
1
RCRAPP1_MI
Q
RCRAPP1_LAST_NAME
Andreas
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
January 2009
17-MAY-2002 03:00 PM
7
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200010 AN 01 Andreas,JacksonQ.
EDE
1
005
165200010 AN 01 Andreas,JacksonQ.
EDE
1
009
165200010 AN 01 Andreas,JacksonQ.
EDE
1
007
165200010 AN 01 Andreas,JacksonQ.
EDE
1
027
165200010 AN 01 Andreas,JacksonQ.
EDE
1
024
165200010 AN 01 Andreas,JacksonQ.
EDE
1
012
165200010 AN 01 Andreas,JacksonQ.
EDE
1
006
165200010 AN 01 Andreas,JacksonQ.
EDE
1
008
165200010 AN 01 Andreas,JacksonQ.
EDE
1
019
165200010 AN 01 Andreas,JacksonQ.
EDE
1
017
165200010 AN 01 Andreas,JacksonQ.
EDE
1
021
165200010 AN 01 Andreas,JacksonQ.
EDE
1
020
165200010 AN 01 Andreas,JacksonQ.
EDE
1
018
165200010 AN 01 Andreas,JacksonQ.
EDE
1
010
165200010 AN 01 Andreas,JacksonQ.
EDE
1
010
165200010 AN 01 Andreas,JacksonQ.
EDE
1
028
RCRAPP1_CITY
Somewhere
RCRAPP1_BIRTH_DATE
01-FEB-1965
RCRAPP1_ZIP
88888
RCRAPP1_TITLE
1
RCRAPP1_STAT_CODE_RES
AZ
RCRAPP1_STAT_CODE_LIC
AZ
RCRAPP1_STAT_CODE
AZ
RCRAPP1_SSN
165200010
RCRAPP1_RQST_FA_WINTER_NEXT_YR
2
RCRAPP1_RQST_FA_SUMMER_THIS_YR
2
RCRAPP1_RQST_FA_SUMMER_NEXT_YR
2
RCRAPP1_RQST_FA_SPRING_NEXT_YR
2
RCRAPP1_RQST_FA_FALL_THIS_YR
2
RCRAPP1_PHONE_NO
5551212
RCRAPP1_PHONE_AREA
999
RCRAPP1_PERMIT_DRAFT_REG
165200010 AN 01 Andreas,JacksonQ.
EDE
1
004
165200010 AN 01 Andreas,JacksonQ.
EDE
1
026
165200010 AN 01 Andreas,JacksonQ.
EDE
1
025
165200010 AN 01 Andreas,JacksonQ.
EDE
1
035
165200010 AN 01 Andreas,JacksonQ.
EDE
1
023
165200010 AN 01 Andreas,JacksonQ.
EDE
1
053
165200011 AN 01 Andreas,Kelsey
EDE
1
053
165200011 AN 01 Andreas,Kelsey
EDE
1
054
PAGE
RERCRCR
DATE SENT
TIME
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
RCRAPP1_ADDR
12 Any Street
RCRAPP4_S_RES_DATE_MO_YR
200001
RCRAPP4_LEGAL_RES_IND
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
18-68
Banner Financial Aid 8.3
User Guide
Reports and Processes
RCRAPP4_DRUG_OFFENSE_CONVIC
3
RCRAPP3_MOTHER_HI_GRADE
3
RCRAPP3_GRAD_OR_PROF
1
RCRAPP3_GRAD_OR_PROF
2
RCRAPP3_MARRIED
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
January 2009
17-MAY-2002 03:00 PM
8
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200011 AN 01 Andreas,Kelsey
EDE
1
051
165200011 AN 01 Andreas,Kelsey
EDE
1
041
165200011 AN 01 Andreas,Kelsey
EDE
1
042
165200011 AN 01 Andreas,Kelsey
EDE
1
056
165200011 AN 01 Andreas,Kelsey
EDE
1
049
165200011 AN 01 Andreas,Kelsey
EDE
1
052
165200011 AN 01 Andreas,Kelsey
EDE
1
046
165200011 AN 01 Andreas,Kelsey
EDE
1
045
165200011 AN 01 Andreas,Kelsey
EDE
1
044
165200011 AN 01 Andreas,Kelsey
EDE
1
057
165200011 AN 01 Andreas,Kelsey
EDE
1
058
165200011 AN 01 Andreas,Kelsey
EDE
1
040
165200011 AN 01 Andreas,Kelsey
EDE
1
039
165200011 AN 01 Andreas,Kelsey
EDE
1
037
165200011 AN 01 Andreas,Kelsey
EDE
1
043
165200011 AN 01 Andreas,Kelsey
EDE
1
050
165200011 AN 01 Andreas,Kelsey
EDE
1
036
165200011 AN 01 Andreas,Kelsey
EDE
1
047
165200011 AN 01 Andreas,Kelsey
EDE
1
055
165200011 AN 01 Andreas,Kelsey
EDE
1
048
RCRAPP1_OTH_VA_AMT
100
RCRAPP1_NO_EXEMPT
1
RCRAPP1_INC_FR_WRK
1000
RCRAPP1_HAS_LEGAL_DEPEND
2
RCRAPP1_CASH_AMT
1000
RCRAPP1_BORN_BEFORE_1_1_XX
2
RCRAPP4_WORKSHEET_C
1000
RCRAPP4_WORKSHEET_B
1000
RCRAPP4_WORKSHEET_A
1000
RCRAPP1_WARD_OF_COURT
2
RCRAPP1_US_VET
2
RCRAPP1_US_INC_TAX_PD
1000
RCRAPP1_US_INC
1000
RCRAPP1_TAX_FORM_IND
2
RCRAPP1_SPS_INC_FR_WRK
1000
RCRAPP1_OTH_VA_MTH
9
RCRAPP4_TX_RET_FILED_IND
2
RCRAPP4_INV_NET_WORTH
1000
RCRAPP4_HAVE_CHILDREN
2
RCRAPP4_BUS_NET_WORTH
1000
2
RCRAPP3_EFC_RECALC_CORR_REQ
165200012 AN 01 Andreas,Lindsey
EDE
1
105
165200012 AN 01 Andreas,Lindsey
EDE
1
101
165200012 AN 01 Andreas,Lindsey
EDE
1
100
PAGE
RERCRCR
DATE SENT
TIME
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
18-69
Banner Financial Aid 8.3
User Guide
Reports and Processes
RCRAPP3_PREPARER_EIN
111111111
RCRAPP3_PREPARER_SSN
222222222
29-NOV-2001 10:02
29-NOV-2001 10:02
January 2009
17-MAY-2002 03:00 PM
9
AID YEAR: 0203 Award Year 2002-2003
SAR ID
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200012 AN 01 Andreas,Lindsey
EDE
1
098
165200012 AN 01 Andreas,Lindsey
EDE
1
099
165200012 AN 01 Andreas,Lindsey
EDE
1
074
165200012 AN 01 Andreas,Lindsey
EDE
1
073
165200012 AN 01 Andreas,Lindsey
EDE
1
071
165200012 AN 01 Andreas,Lindsey
EDE
1
066
165200012 AN 01 Andreas,Lindsey
EDE
1
069
165200012 AN 01 Andreas,Lindsey
EDE
1
065
165200012 AN 01 Andreas,Lindsey
EDE
1
075
165200012 AN 01 Andreas,Lindsey
EDE
1
098
165200012 AN 01 Andreas,Lindsey
EDE
1
059
165200012 AN 01 Andreas,Lindsey
EDE
1
064
165200012 AN 01 Andreas,Lindsey
EDE
1
083
165200012 AN 01 Andreas,Lindsey
EDE
1
085
165200012 AN 01 Andreas,Lindsey
EDE
1
077
165200012 AN 01 Andreas,Lindsey
EDE
1
076
165200012 AN 01 Andreas,Lindsey
EDE
1
084
165200012 AN 01 Andreas,Lindsey
EDE
1
067
165200012 AN 01 Andreas,Lindsey
EDE
1
081
165200012 AN 01 Andreas,Lindsey
EDE
1
082
165200012 AN 01 Andreas,Lindsey
EDE
1
072
165200012 AN 01 Andreas,Lindsey
EDE
1
062
165200012 AN 01 Andreas,Lindsey
EDE
1
063
165200012 AN 01 Andreas,Lindsey
EDE
1
060
RCRAPP1_SIGNED_MTH_DAY
1231
RCRAPP1_SIGNED
B
RCRAPP1_PAR_US_INC_TAX_PD
1000
RCRAPP1_PAR_US_INC
1000
RCRAPP1_PAR_TAX_FORM_IND
1
RCRAPP1_PAR_STAT_CODE_RES
AL
RCRAPP1_PAR_OLDER_AGE
65
RCRAPP1_PAR_NO_IN_COLL
1
RCRAPP1_PAR_NO_EXEMPT
0
RCRAPP1_SIGNED_YR
1
RCRAPP1_PAR_MRTL_STATUS
1
RCRAPP1_PAR_FAM_MEMB
1
RCRAPP1_PAR_CASH_AMT
1000
RCRAPP1_NO_IN_COLL
1
RCRAPP1_MOTH_INC_FR_WRK
1000
RCRAPP1_FATH_INC_FR_WRK
1000
RCRAPP1_FAM_MEMB
1
RCRAPP4_PAR_LEGAL_RES_IND
2
RCRAPP4_PAR_INV_NET_WORTH
1000
RCRAPP4_PAR_BUS_NET_WORTH
1000
RCRAPP4_PAR_1040A_ELIG_IND
1
RCRAPP4_MOTH_SSN
555555555
RCRAPP4_MOTH_LAST_NAME
Jones
RCRAPP4_FATH_SSN
444444444
18-70
NAME
SunGard Higher Education Development
Banner Financial Aid 8.3
User Guide
Reports and Processes
PAGE
RERCRCR
DATE SENT
TIME
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
January 2009
17-MAY-2002 03:00 PM
PAGE
10
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
165200012 AN 01 Andreas,Lindsey
EDE
1
061
165200012 AN 01 Andreas,Lindsey
EDE
1
920
165200012 AN 01 Andreas,Lindsey
EDE
1
068
165200012 AN 01 Andreas,Lindsey
EDE
1
080
165200012 AN 01 Andreas,Lindsey
EDE
1
079
165200012 AN 01 Andreas,Lindsey
EDE
1
078
165200012 AN 01 Andreas,Lindsey
EDE
1
070
165200012 AN 01 Andreas,Lindsey
EDE
1
102
RCRAPP4_FATH_LAST_NAME
Jones
RCRAPP4_EMAIL_ADDRESS
[email protected]
RCRAPP4_P_RES_DATE_MO_YR
195012
RCRAPP4_PAR_WORKSHEET_C
1000
RCRAPP4_PAR_WORKSHEET_B
1000
RCRAPP4_PAR_WORKSHEET_A
1000
RCRAPP4_PAR_TX_RET_FILED_IND
1
RCRAPP3_PREPARER_SIGN
171990060 AN 01 Soroka,Abbey
EDE
1
048
171990060 AN 01 Soroka,Abbey
EDE
1
082
171990060 AN 01 Soroka,Abbey
EDE
1
039
171990060 AN 01 Soroka,Abbey
EDE
1
043
171990060 AN 01 Soroka,Abbey
EDE
1
074
171990060 AN 01 Soroka,Abbey
EDE
1
083
171990060 AN 01 Soroka,Abbey
EDE
1
077
171990060 AN 01 Soroka,Abbey
EDE
1
042
171990060 AN 01 Soroka,Abbey
EDE
1
076
171990060 AN 01 Soroka,Abbey
EDE
1
049
171990060 AN 01 Soroka,Abbey
EDE
1
073
171990060 AN 01 Soroka,Abbey
EDE
1
040
171990060 AN 01 Soroka,Abbey
EDE
1
001
171990060 AN 01 Soroka,Abbey
EDE
1
046
171990060 AN 01 Soroka,Abbey
EDE
1
045
171990060 AN 01 Soroka,Abbey
EDE
1
044
RERCRCR
DATE SENT
TIME
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
29-NOV-2001 10:02
18-71
Banner Financial Aid 8.3
User Guide
Reports and Processes
RCRAPP4_BUS_NET_WORTH
111
RCRAPP4_PAR_BUS_NET_WORTH
111
RCRAPP1_US_INC
22222
RCRAPP1_SPS_INC_FR_WRK
22222
RCRAPP1_PAR_US_INC_TAX_PD
111111
RCRAPP1_PAR_CASH_AMT
111
RCRAPP1_MOTH_INC_FR_WRK
111111
RCRAPP1_INC_FR_WRK
2222
RCRAPP1_FATH_INC_FR_WRK
111111
RCRAPP1_CASH_AMT
111
RCRAPP1_PAR_US_INC
111111
RCRAPP1_US_INC_TAX_PD
222
RCRAPP1_LAST_NAME
Soroka
RCRAPP4_WORKSHEET_C
555
RCRAPP4_WORKSHEET_B
555
RCRAPP4_WORKSHEET_A
555
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
January 2009
222
SunGard Higher Education Development
17-MAY-2002 03:00 PM
11
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
171990060 AN 01 Soroka,Abbey
EDE
1
080
171990060 AN 01 Soroka,Abbey
EDE
1
079
171990060 AN 01 Soroka,Abbey
EDE
1
078
171990060 AN 01 Soroka,Abbey
EDE
1
081
171990060 AN 01 Soroka,Abbey
EDE
1
047
171990004 SO
soroka,venturo
MANUAL
1
078
171990004 SO
soroka,venturo
MANUAL
1
079
171990004 SO
soroka,venturo
MANUAL
1
080
171990004 SO
soroka,venturo
MANUAL
1
044
171990004 SO
soroka,venturo
MANUAL
1
045
171990004 SO
soroka,venturo
MANUAL
1
046
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
029
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
043
RCRAPP4_PAR_WORKSHEET_C
555
RCRAPP4_PAR_WORKSHEET_B
555
RCRAPP4_PAR_WORKSHEET_A
555
RCRAPP4_PAR_INV_NET_WORTH
111
RCRAPP4_INV_NET_WORTH
111
RCRAPP4_PAR_WORKSHEET_A
1
RCRAPP4_PAR_WORKSHEET_B
1
RCRAPP4_PAR_WORKSHEET_C
1
RCRAPP4_WORKSHEET_A
1
RCRAPP4_WORKSHEET_B
1
RCRAPP4_WORKSHEET_C
1
RCRAPP3_DEGREE_TYPE
1
RCRAPP1_SPS_INC_FR_WRK
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
077
RCRAPP1_MOTH_INC_FR_WRK
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
076
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
074
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
073
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
099
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
032
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
009
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
046
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
080
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
081
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
082
RCRAPP1_FATH_INC_FR_WRK
72000
RCRAPP1_PAR_US_INC_TAX_PD
72483
RCRAPP1_PAR_US_INC
72483
RCRAPP1_SIGNED
B
RCRAPP1_DEGREE_BY_JULY
2
RCRAPP1_BIRTH_DATE
06-DEC-2001 12:41
02-APR-1984
RCRAPP4_WORKSHEET_C
0
RCRAPP4_PAR_WORKSHEET_C
0
RCRAPP4_PAR_INV_NET_WORTH
500
RCRAPP4_PAR_BUS_NET_WORTH
0
PAGE
RERCRCR
DATE SENT
TIME
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
06-DEC-2001 12:41
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
18-72
Banner Financial Aid 8.3
User Guide
Reports and Processes
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
January 2009
17-MAY-2002 03:00 PM
12
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
047
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
053
181030503 MA 01 MAGRONE,BRIANA.
EDE
1
030
181030510 MA 01 MAGRONE,COLLINC.
EDE
1
042
181030510 MA 01 MAGRONE,COLLINC.
EDE
1
040
181030510 MA 01 MAGRONE,COLLINC.
EDE
1
009
181030510 MA 01 MAGRONE,COLLINC.
EDE
1
052
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
029
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
053
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
032
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
052
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
009
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
080
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
046
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
079
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
078
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
081
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
030
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
083
181030504 MA 01 MAGRONE,DANIELB.
EDE
1
099
181030513 MA 01 MAGRONE,JASONM.
EDE
1
009
181030513 MA 01 MAGRONE,JASONM.
EDE
1
040
181030502 MA 01 MAGRONE,JODIL.
EDE
1
039
RCRAPP4_INV_NET_WORTH
0
RCRAPP3_GRAD_OR_PROF
2
RCRAPP3_YR_IN_COLL_2
4
RCRAPP1_INC_FR_WRK
1004
RCRAPP1_US_INC_TAX_PD
1004
RCRAPP1_BIRTH_DATE
26-JUL-1919
RCRAPP1_BORN_BEFORE_1_1_XX
1
RCRAPP3_DEGREE_TYPE
1
RCRAPP3_GRAD_OR_PROF
2
RCRAPP1_DEGREE_BY_JULY
2
RCRAPP1_BORN_BEFORE_1_1_XX
2
RCRAPP1_BIRTH_DATE
09-JUL-1984
RCRAPP4_PAR_WORKSHEET_C
0
RCRAPP4_WORKSHEET_C
0
RCRAPP4_PAR_WORKSHEET_B
15000
RCRAPP4_PAR_WORKSHEET_A
5000
RCRAPP4_PAR_INV_NET_WORTH
7800
RCRAPP3_YR_IN_COLL_2
4
RCRAPP1_PAR_CASH_AMT
3300
RCRAPP1_SIGNED
B
RCRAPP1_BIRTH_DATE
14-OCT-1916
RCRAPP1_US_INC_TAX_PD
2912
RCRAPP1_US_INC
181030502 MA 01 MAGRONE,JODIL.
EDE
1
009
PAGE
RERCRCR
DATE SENT
TIME
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
18-73
Banner Financial Aid 8.3
User Guide
Reports and Processes
RCRAPP1_BIRTH_DATE
10-FEB-1917
17-MAY-2002 14:51
January 2009
17-MAY-2002 03:00 PM
13
AID YEAR: 0203 Award Year 2002-2003
SAR ID
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
181030515 MA 01 MAGRONE,KYLED.
EDE
1
907
181030515 MA 01 MAGRONE,KYLED.
EDE
1
911
181030515 MA 01 MAGRONE,KYLED.
EDE
1
046
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
046
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
042
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
049
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
039
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
040
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
050
181030501 MA 01 MAGRONE,MELANIEN.
EDE
1
051
181030520 MA 01 MAGRONE,ONKAR
EDE
1
907
181030520 MA 01 MAGRONE,ONKAR
EDE
1
040
181030520 MA 01 MAGRONE,ONKAR
EDE
1
042
181030520 MA 01 MAGRONE,ONKAR
EDE
1
039
181030520 MA 01 MAGRONE,ONKAR
EDE
1
046
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
044
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
040
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
039
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
074
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
073
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
045
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
046
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
084
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
042
ASSM_6
1
REJ_N
1
RCRAPP4_WORKSHEET_C
99999
RCRAPP4_WORKSHEET_C
25000
RCRAPP1_INC_FR_WRK
75000
RCRAPP1_CASH_AMT
150
RCRAPP1_US_INC
75000
RCRAPP1_US_INC_TAX_PD
7500
RCRAPP1_OTH_VA_MTH
9
RCRAPP1_OTH_VA_AMT
400
ASSM_6
1
RCRAPP1_US_INC_TAX_PD
2891
RCRAPP1_INC_FR_WRK
6779
RCRAPP1_US_INC
6802
RCRAPP4_WORKSHEET_C
1000
RCRAPP4_WORKSHEET_A
25000
RCRAPP1_US_INC_TAX_PD
1000
RCRAPP1_US_INC
10000
RCRAPP1_PAR_US_INC_TAX_PD
5000
RCRAPP1_PAR_US_INC
50000
RCRAPP4_WORKSHEET_B
30000
RCRAPP4_WORKSHEET_C
20000
RCRAPP1_FAM_MEMB
3
RCRAPP1_INC_FR_WRK
10000
18-74
NAME
SunGard Higher Education Development
Banner Financial Aid 8.3
User Guide
Reports and Processes
PAGE
RERCRCR
DATE SENT
TIME
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
January 2009
17-MAY-2002 03:00 PM
14
AID YEAR: 0203 Award Year 2002-2003
SAR ID
NAME
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SOURCE
SEQ SAR FLD
DATA ELEMENT/VALUE
181030103 MA 01 MAGRONE,TRUMBONE
EDE
1
076
181030506 MA 01 SILVAINT,KEVINY.
EDE
1
029
181030506 MA 01 SILVAINT,KEVINY.
EDE
1
053
181030506 MA 01 SILVAINT,KEVINY.
EDE
1
030
181030506 MA 01 SILVAINT,KEVINY.
EDE
1
032
181030506 MA 01 SILVAINT,KEVINY.
EDE
1
099
181030506 MA 01 SILVAINT,KEVINY.
EDE
1
074
RCRAPP1_FATH_INC_FR_WRK
50000
RCRAPP3_DEGREE_TYPE
1
RCRAPP3_GRAD_OR_PROF
2
RCRAPP3_YR_IN_COLL_2
4
RCRAPP1_DEGREE_BY_JULY
2
RCRAPP1_SIGNED
B
RCRAPP1_PAR_US_INC_TAX_PD
19544
Total NO batches:
Banner Financial Aid 8.3
User Guide
Reports and Processes
DATE SENT
TIME
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
17-MAY-2002 14:51
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SAR ID
18-75
RERCRCR
5
17-MAY-2002 03:00 PM
15
AID YEAR: 0203 Award Year 2002-2003
Total NO batches:
PAGE
165100001
165100002
165100003
165100004
165100005
165100006
165100007
165100008
165100009
165100010
165100011
165100012
165100001
165100002
165100003
165100004
165100005
165100006
165100007
165100008
165100009
165100010
165100011
165100012
2
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
01
DATE SENT
TIME
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
PAGE
RERCRCR
January 2009
17-MAY-2002 03:00 PM
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
SAR ID
INSTITUTION
DATE SENT
TIME
165200001
165200002
165200003
165200004
165200005
165200006
165200007
165200008
165200009
165200010
165200011
165200012
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
01
01
01
01
01
01
01
01
01
01
01
01
1
2
3
4
5
6
1
2
3
4
5
6
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
28-NOV-2001
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
14:39
165200001
165200002
165200003
165200004
165200005
165200006
165200007
165200008
165200009
165200010
165200011
165200012
2
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
AN
01
01
01
01
01
01
01
01
01
01
01
01
1
2
3
4
5
6
1
2
3
4
5
6
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
29-NOV-2001
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
10:02
PAGE
16
PAGE
17
RERCRCR
** ** ** ** ** **
Total NO batches:
17-MAY-2002 03:00 PM
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
EDE Correction/Request/Change Control Report
RERCRCR
* * * REPORT CONTROL INFORMATION * * *
RPTNAME: RERCRCR
VERSION: 5.1
REPORT SEQUENCE NUMBER: 786794
AID YEAR: 0203
ACTIVITY DATE:
ACTIVITY DATE HOUR:
ACTIVITY DATE MINUTE:
LINE COUNT: 55
RECORD COUNT: 367
18-76
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 COD Extract Process (REREX09)
Description
The COD Extract Process:
• Extracts Federal Pell Grant, Direct Loan, ACG, and SMART award and disbursement data from Banner and
formats the data in the appropriate XML format for transmission to COD.
• Selects or creates a COD student identifier.
• If a student identifier does not currently exist for the student for any aid year, the process creates a
student identifier with a sequence number of 1.
• If a student identifier already exists for a student for any aid year, the process selects the highest
accepted sequence number associated with the student identifier. This ensures that the most recent
student identifier is used in those cases where the student identifier record spans more than one aid
year.
Selecting ACG and SMART Records to Extract
ACG Award Records
ACG award records are selected for extraction if the following conditions are met:
• The Extract ACG Funds parameter is set to Y.
• The Date Sent field for the origination on the ACG/SMART window of the REAOR09 form is blank.
• or
The record is (1) the latest origination for the Fund Code, (2) the Action Code status of the origination on
the ACG/SMART window of the REAOR09 form is A=Accepted or C=Corrected, and (3) there is an ACG
disbursement record for extraction (see below).
ACG Disbursement Records
Note that Just in Time (JIT) functionality does not apply to ACG.
ACG disbursement records are selected for extraction if the following conditions are met:
• The Extract ACG Funds parameter is set to Y.
18-77
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
• The disbursement has been paid as indicated by an amount in the Disbursement Amount field on the
READI09 form.
• The Lock field on the READI09 form for the disbursement record is not checked.
• The disbursement record has not yet been sent to COD (there is no date in the Date Sent field on the
READI09 form) and the disbursement is not a correction or COD system-generated disbursement record
(the Action Code field on the READI09 form is not X).
or
The disbursement record has been sent (there is a date in the Date Sent field on the READI09 form) and the
disbursement record is rejected (the Action Code field on the READI09 form is R).
SMART Award Records:
SMART award records are selected for extraction if the following conditions are met:
• The Extract SMART Funds parameter is set to Y.
• The Date Sent field for the origination on the ACG/SMART window of the REAOR09 form is blank.
or
The record is (1) the latest origination for the Fund Code, (2) the Action Code status of the origination on
the ACG/SMART window of the REAOR09 form is A=Accepted or C=Corrected, and (3) there is a
SMART disbursement record for extraction (see below).
SMART Disbursement Records:
Note that Just in Time (JIT) functionality does not apply to SMART.
SMART disbursement records are selected for extraction if the following conditions are met:
• The Extract SMART Funds parameter is set to Y.
The disbursement has been paid as indicated by an amount in the Disbursement Amount field on the
READI09 form.
The Lock field on the READI09 form for the disbursement record is not checked.
18-78
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
• The disbursement record has not yet been sent to COD (there is no date in the Date Sent field on the
READI09 form) and the disbursement is not a correction or COD system-generated disbursement record
(the Action Code field on the READI09 form is not X).
or
The disbursement record has been sent (there is a date in the Date Sent field on the READI09 form) and the
disbursement record is rejected (the Action Code field on the READI09 form is R).
COD Address Requirements and the REREX09 Process
For Pell, ACG, or SMART records, COD requires a complete address for all domestic and foreign records.
Additionally, you must provide the nation code with all foreign addresses. You’ll receive a reject code if the
address is not complete. For a foreign address, a nation code on the latest active student address record (SPAIDEN)
and a corresponding crosswalk value (entered on the RTVCDNT) are needed for the award to extract.
REREX09 retrieves address information as follows:
1. Students with Pell and/or DL loans
• uses the address from the highest Direct Loan application number for the aid year on RPALORG
(including the foreign nation code), or else
• uses the address from RCRAPP1 (entered on the RNANA09 form)
2. Students with Pell, ACG, or SMART only
• uses the address from RCRAPP1 (entered on the RNANA09 form)
• uses the foreign nation code from SPRADDR (not the entire address).
For foreign addresses, a foreign nation code must exist on any student address record as long as it is active and
current. REREX09 will select the latest record if multiple current/active records exist with a foreign address. The
address type is not considered in the selection.
Output Files
Full Participant Message Classes are used to exchange data with the COD System. Effective December 16, 2006,
all extracted files use the COD 2.0e schema.
18-79
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
If a student record is not extracted, all encountered error conditions are reported in the log file with the student's
SPRIDEN_ID and the reason the record was not extracted.
Extract files are named with the appropriate aid year and program specific message classes depending on the
parameters entered when the job is submitted. Message classes that end with an IN are for documents exported
from Banner and sent to the COD System. The extract file names are as follows:
• craa09in_jobsubnumber.xml: (Pell/Direct Loan/ACG/SMART - any combination of two or more)
• crpg09in_jobsubnumber.xml: (Pell only)
• crdl09in_jobsubnumber.xml: (Direct Loan only)
• crag09in_jobsubnumber.xml: (ACG only)
• crsg09in_jobsubnumber.xml: (SMART only)
Once REREX09 has completed, if the Print RERIMEX Report parameter is set to Y, the RERIMEX Process is
automatically run to produce the E (Extract) report for the Document ID just extracted through REREX09.
Parameters
18-80
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
DL Fund Code(s)
No
Direct Loan fund codes representing the subsidized,
unsubsidized, and PLUS Direct Loan records you
want to extract.
Fund Base Data form (RFRBASE)
Extract Pell Funds
Yes
This parameter provides you with the option of
including Pell records in the extraction.
Y
Extract all Pell Funds.
N
Do Not Extract Pell Funds
(default)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
DL Records to Extract
Promissory Note Print
Required?
Description
Values
No
This parameter determines whether to extract only
those Direct Loan records that have Direct Loan
changes logged, to extract only those Direct Loan
records that do not have Direct Loan changes
logged, to extract all Direct Loan records, or to not
extract any Direct Loan records. This parameter is
only used to select which loan records are extracted.
Once the loan ID is selected for extraction,
disbursement records are also extracted for that loan,
if necessary. This is preferred by COD as any Direct
Loan changes that also affect the disbursement
records should be reported in the same record to
avoid warning edit messages.The REREX09
Process also extracts pending Student Identifier
change records regardless of the value in this
parameter. The process recognizes that the Student
Identifier has changed based on the Status Code
value of null on the REASTID form. When you use
a population selection, all Student Identifier changes
for students in that population are extracted
regardless of the value of this parameter. However,
Student Identifier changes for students not in the
population selection are not extracted.
C
Extract only those Direct Loan
records for the fund codes listed in
the DL Fund Code(s) parameter
that have Direct Loan changes to
extract. The Extract Pell Funds,
Extract ACG Funds, and Extract
SMART Funds parameters must
also be N.
O
Extract only those Direct Loan
records for the fund codes listed in
the DL Fund Code(s) parameter
that do not have Direct Loan
Changes to extract.
B
Extract all Direct Loan records for
the fund codes listed in the DL
Fund Code(s) parameter with or
without Direct Loan Changes to
extract.
This parameter determines whether COD or the
school is responsible for the printing of the
promissory note.
O
School prints from Banner
R
COD prints; sends to school
S
COD prints; sends to borrower
No
BlankDo not extract any Direct Loan
records (default).
Note: The RERIMEX report output
separates Direct Loan Changes
from Direct Loan Originations in
order to identify which students to
review on ROAALOG in the case of
rejected Direct Loan Change
records.
Blank (Default)
18-81
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Extract ACG Funds
Extract SMART Funds
18-82
Banner Financial Aid 8.3
User Guide
Reports and Processes
Required?
Description
Values
Yes
The Extract ACG Funds parameter determines
whether or not to extract ACG origination and
disbursement records.
Valid values are:
Yes
The Extract SMART Funds parameter determines
whether or not to extract SMART origination and
disbursement records.
Y
Yes, extract all ACG origination
and disbursement records
N
No, do not extract any ACG
origination or disbursement
records.
Valid values are:
Y
Yes, extract all SMART
origination and disbursement
records
N
No, do not extract any SMART
origination or disbursement
records.
January 2009
Parameters (cont) Name
Attending School ID
Required?
Description
Values
No
The Attending School ID parameter enables you to
extract Pell, Direct Loan, ACG and SMART records
by campus. This parameter is optional as it should be
entered when you resend a document with the
Resend Document ID parameter. However, this
parameter is required for all other extracts.
COD Entity ID Rules (RORCODI)
To extract records, enter the campus Attending ID.
The process extracts Direct Loans (entered for the
DL Fund Code(s) parameter) when the School Code
on RPALORG matches the Direct Loan School
Code on RORCODI using the Attending ID as the
reference point.
The process extracts Pell, ACG, and SMART records
(when the Extract Pell Funds, Extract ACG Funds,
and Extract SMART Funds parameters are
respectively set to Y) when the Campus Pell ID for
the origination record on REAOR09 matches the
Federal Pell ID on RORCODI using the Attending
ID as the reference point.
Response Type
18-83
Banner Financial Aid 8.3
User Guide
Reports and Processes
Yes
The COD System sends one Response document for F (Full Response)
each Common Record document submitted. For
Responses received via the SAIG mailbox, COD
gives schools the option to receive a Full or Standard
Response to Common Records processed by the
COD System. A Full Response contains all the
original tags sent by the school and the rejected data
elements and reason codes. A Standard Response
contains only the rejected data elements and reason
codes. At this time, Banner only supports Full
Response files. The only valid value for the Full
Response tag is F.
January 2009
Parameters (cont) Name
Resend Document ID
Required?
Description
Values
No
Allows you to re-extract a previously extracted
Document ID. The process re-extracts all records in
Banner that are associated with this Document ID —
provided that a response document has not already
been imported for this same document ID.
Validates to an existing Document ID
on the COD Document Control form
(REICODD).
If all records with this document ID are still in an S
(Sent) status and the COD Website indicates that
they did not receive and process this document ID,
use the Resend Document ID option.
If all records with this document ID are not in an S
(Sent) status, do not use the Resend Document ID
option. Instead, review the RERIM09 log file, the
RERIMEX report when run for both import and
exported records, and the COD response file to
determine which records did not update and the
cause.
To ensure accuracy in the resend
process, the Attending ID, Reporting
ID and Source ID used in the extract
file are captured when records are
initially extracted. These values are
stored in the RERCODD table and are
retrieved and used during the resend
process.
If all records with this document ID are still in an S
(Sent) status and the COD Website indicates that
they did receive and process this document ID,
locate and import the response file with the
RERIM09 Process. If necessary, request that COD
resend the response file.
18-84
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection ID, Creator ID, and User ID
parameters.
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application ID, User ID, and Creator
ID parameters.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Required?
Description
Creator ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID, User ID, and Application ID
parameters.
User ID
No
The ID of the person using the subpopulation rule. If
you enter a value for this parameter, you must also
enter a value for the Selection ID, Application ID,
and Creator ID parameters.
Print RERIMEX Report
Yes
This parameter enables you to decide whether or not
you want to print the RERIMEX report. If Y is
selected, RERIMEX is automatically run to produce
the E (Extract) report for the Document ID extracted
through REREX09.
Y
Yes, print the RERIMEX report
(default)
N
No, do not print the RERIMEX
report
Do you want to create a new COD Student Identifier
when the current COD Student Identifier on the
REASTID form and the current ISIR record on
RNANA09 do not match?
Y (Yes) Default
Update Student
Identifier
Yes
If you select N (No), you indicate that you want to
prevent the record from extraction so that you can
review the data manually. Any students that have a
mismatch between the RERSTID and RCRAPP1
tables are reported in an error message to the log file.
Values
N (No)
Note: This compare only affects the
Student Identifier. This compare
does not occur in any instance for
the Parent PLUS Borrower Identifier.
If you select Y (Yes), the process automatically
inserts a new COD Student ID into the RERSTID
Table when these records do not match.
18-85
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 COD Extract Process
04-MAY-2007 05:39:25 PM
BANNER University
Page 1
Aid Year: 0809
COD Export Process
REREX09
---------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name.................: REREX09
Version......................: 8.1
One up Number................: 100576
Aid Year Code................: 0809
DL Fund Code(s)..............:
Extract Pell Funds...........: Y
Records to extract...........:
Promissory Note Print........:
Attended ID..................: 65167086
Response type................: F
Resend Document ID...........:
Application Code.............: FINAID
Selection ID.................: MANUAL
Creator ID...................: DRUCKER
User ID......................: DRUCKER
Print Report.................: Y
Update Student Identifier?...: Y
Number of Lines Per Page.....: 55
Document ID: 2007-05-04T17:39:26.0065167086
Total Students Extracted.................: 1
Total
Total
Total
Total
Connected.
18-86
Pell Awards Extracted..............:
DL Plus Awards Extracted...........:
DL Subsidized Awards Extracted.....:
DL Unsubsidized Awards Extracted...:
Banner Financial Aid 8.3
User Guide
Reports and Processes
1
0
0
0
January 2009
Grant File Import Process (RERFI09)
Description
The Grant File Import Process loads the fixed length flat file acknowledgement (response) files received from
COD into Banner. The RERFI09 Process cannot be used for files received in XML format. The message classes
accepted by the RERFI09 process are:
Pell Grant Message Classes
• PGRA09OP#R - Pell Data Request Response
• PGAS09OP#A - Pell Electronic Statement of Account (ESOA)
• PGMR09OP#M - Pell Multiple Reporting Record (MRR)
• PGRC09OP#C - Pell Reconciliation Report
• PGYR09OP#Y - Pell Year-to-Date Record
ACG Message Classes
• AGRA09OPAR - ACG Data Request Response
• AGAS09OPAA - ACG Electronic Statement of Account (ESOA)
• AGMR09OPAM - ACG Multiple Reporting Record
• AGRC09OPAC - ACG Reconciliation Report
• AGYR09OPAY - ACG Year-to-Date Record
SMART Grant Message Classes
• SGRA09OPSR - SMART Data Request Response
• SGAS09OPSA - SMART Electronic Statement of Account (ESOA)
• SGMR09OPSM - SMART Multiple Reporting Record
• SGRC09OPSC - SMART Reconciliation Report
• SGYR09OPSY - SMART Year-to-Date Record
18-87
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
18-88
Name
Required?
Description
Values
Grant Acknowledgement or EDE Correction
Filename
Yes
Enter the COD response file name(s) or EDE
correction file that you want to import into Banner.
This parameter allows you to enter multiple files that
can be processed in one run.
COD Files
PGRA09OP
PGAS09OP
PGMR09OP
PGRC09OP
PGYR09OP
AGRA09OP
AGAS09OP
AGMR09OP
AGRC09OP
AGYR09OP
SGRA09OP
SGAS09OP
SGMR09OP
SGRC09OP
SGYR09OP
Accepted Records Print
Option
Yes
A Y indicates that you want to print accepted data
request records on the report. In all cases, the
corrected and rejected records are always printed.
Y - Yes
Banner Financial Aid 8.3
User Guide
Reports and Processes
N - No
January 2009
Pell File Import (RERFIxx.lis)
13-APR-2007 03:36:22 PM
Banner University
1
Aid Year: 0809
RERFI09
-------------------------------------------------------------------------------CONTROL SUMMARY
-------------------Program Name.......................: RERFI09
Version............................: 8.1
Run Sequence Number................: 90298
Print Accepted?....................: Y
I/P File...........................: pgmr09op.dat
Pell File Import (RERFIxx.log)
File Name: /u01/B70/devl/banner/dataload/finaid/pgmr09op.dat
Processing message class PGMR05OP...
Batch Number: #M200962000420070413123456
Reported Number of Records: 1
Reported Total of Batch: $0.00
Accepted and Corrected Number of Records: 1
Accepted and Corrected Total of Batch: $0.00
Accepted and Corrected Total Sign Ind: P
Number of Duplicate Records: 0
Processing message class PGMR09OP...
Batch Number: #M200962000420070413123567
Reported Number of Records: 9
Reported Total of Batch: $0.00
Accepted and Corrected Number of Records: 9
Accepted and Corrected Total of Batch: $0.00
Accepted and Corrected Total Sign Ind: P
Number of Duplicate Records: 0
Connected.
Connected.
Connected.
18-89
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Pell File Import (RERFIxx.ls1)
13-APR-2007 03:36:22 PM
Banner University
1
Aid Year: 0809
RERFI09
-------------------------------------------------------------------------------MULTIPLE REPORTING RECORDS
-------------------------------------------------------------------------------Name
ID
SAR SSN
SAR INIT Record Type Req Pell ID Inst Pell ID Code 1 Code 2
---------------------------------------------------------------------------------------------------------------Rucker, Test1002 C
517001002 517001002 RU
PU
620004
620004
O
I
Rucker, Test1002 C
517001002 517001002 RU
PU
620004
620004
O
I
Total MRR Records for batch #M200962000420070413123456: 2
13-APR-2004 03:36:22 PM
Banner University
1
Aid Year: 0405
RERFI05
-------------------------------------------------------------------------------MULTIPLE REPORTING RECORDS
-------------------------------------------------------------------------------Name
ID
SAR SSN
SAR INIT Record Type Req Pell ID Inst Pell ID Code 1 Code 2
---------------------------------------------------------------------------------------------------------------Rucker, Test1005 J
517001005 517001005 RU
RD
620004
620004
D
I
Rucker, Test1004
517001004 517001004 RU
RO
620004
620004
O
I
Total MRR Records for batch #M200962000420070413123567: 2
Pell File Import (RERFIxx.ls2)
#M200962000420070413123567
000
18-90
No batch level errors for batch
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Grant COD Miscellaneous Report (RERGRNT)
The Grant COD Miscellaneous Report lets you access COD data stored in the database. This can be used to help
identify exception processing requirements.The types of available data include:
Description
• All students with Verification Code=‘W.’
• COD Grant disbursement locked records.
• Just in Time, no disbursement acknowledged.
• Just in Time, no charge accepted.
• All MRR records.
• Rejected Origination records.
• Rejected Disbursement records.
• Year-to-date reporting.
If you select more than one option simultaneously, a page break between each set of students appears with the
option selected clearly identified at the top of each page. However, the output only displays the relevant sections of
the report. If you only select one parameter, only that section of the report is generated. If you select two
parameters, two sections are generated, and so on, with a page break between each section.
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Grant Type
Yes
Select the type of grant data that you want to list on
the report.
PL Pell
AG ACG
SG SMART
18-91
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Required?
Select Verif. Code = ‘W’ Yes
Select System Gen Disb
Nos
18-92
Banner Financial Aid 8.3
User Guide
Reports and Processes
Yes
Description
Values
If the student has a verification W (Without
Documentation) status at the end of the year, COD
will send a corrected record with a disbursement
amount of $0. All Pell for this student must be
reversed for this aid year. Until an updated
origination record has been acknowledged with a
valid verification status code, no more payments can
be made to this student.
Y
Select all records with a W
verification code
N
Do not select all records with a W
verification code
You can only set this parameter to Y if
the Grant Type parameter is set to PL.
Sequence numbers 66–99 are reserved for COD use Y
for adjusting disbursements automatically at the end
of the year that were never resolved. Enter Y to select
all records with a disbursement sequence in this
range.
N
Based on the value for the Grant
Type parameter, select all records
with a disbursement sequence in
the 66-99 range.
Do not select all records with a
disbursement sequence in the 6699 range.
January 2009
Parameters (cont) Name
Select COD Grant Disb.
Locked
Required?
Description
Values
Yes
The system processes disbursement response data
for Disbursement sequence numbers 66–99 where
there has not been a corresponding disbursement
record created by the school. The RERIM09 process
inserts the adjusted disbursement records. Once this
data exists, the disbursement process executes, most
likely recovering Pell, ACG, or SMART dollars.
Y
Based on the value for the Grant
Type parameter, select records
with the Pell, ACG, or SMART
disbursement lock checked on the
ROAPELL form.
N
Do not select records with the
Pell, ACG, or SMART
disbursement lock checked on the
ROAPELL form.
For students where a disbursement sequence number
66– 99 has been received at the same time this data
is loaded, the Pell, ACG, or SMART locked field is
updated (the Lock Pell Disbursement, Lock ACG
Disbursement, or Lock SMART Disbursement
field on the ROAPELL form). This field is set to Y
when the sequence numbers 66–99 are received, and
can only be turned off manually. This requires you to
correct and report whatever conditions caused this
Pell, ACG, or SMART grant to be reversed. At that
time, Banner will calculate the correct amount to be
paid and will create the new disbursement records.
In other words, if this lock field is set to Y for the
specific disbursement lock indicator, Pell, ACG, or
SMART is not disbursed.
18-93
Banner Financial Aid 8.3
User Guide
Reports and Processes
Banner backs out these funds and locks
any further disbursement activity to
keep COD and Banner in sync. Once
the problems are resolved and sent to
COD, such as an updated origination,
only then should you remove the lock
to prevent additional disbursement
activity. To do otherwise could result in
discrepancies at year end and a
potentially large reconciliation effort.
January 2009
Parameters (cont) Name
Required?
Select MRR record types No
Description
Values
Multiple Reporting Records (MRRs) provide
information to an institution about a student’s
origination and disbursement status at other
institutions and the amount of the scheduled award
disbursed. This allows you to identify the two
primary types of multiple reporting conditions:
concurrent enrollment and eligibility overaward.
Enter an MRR record type value(s) for a listing of
records with that MRR type based on the Grant Type
parameter.
RO Originated Institution
RD Disbursed Institution
RN None Found
CE Concurrent Enrollment Institution
PB
Blocked Institution
PR Blocker Institution
PU Unblocked Institution
BC Blocked & Concurrent
Enrollment
RC Blocker & Concurrent Enrollment
Select JIT no disb
acknowledge
Yes
A check in the Just-in-Time Pymt field and an entry
in the # of Days for JIT field on the ROAINST form
determines the number of days to be used for Just In
Time students. This field is the number of days prior
to the scheduled disbursement date that a
disbursement can be extracted. For JIT students,
only authorized aid will be reported to COD to
request additional funding.
Based on the value in this field, the REREX09
process allows a JIT school’s Pell funds to be
extracted within the specified number of days prior
to the scheduled disbursement date.
Y
Select all JIT records with
disbursement error code 047.
N
Do not select all JIT records with
disbursement error code 047.
Since the Disbursement Process
(RPEDISB) requires COD approval
under these conditions, disbursement
reject code 047 - Disbursement
requires approval from COD is issued
when approval has not yet been
received from COD.
You can only set this parameter to Y if
the Grant Type parameter is set to PL.
18-94
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Select JIT no charge
accept
Select all Rejected Orig.
Recs
Select all Rejected Disb.
Recs
18-95
Banner Financial Aid 8.3
User Guide
Reports and Processes
Required?
Description
Values
Yes
Disbursement does not occur until a student accepts
the charges if the Disburse if Charges Not
Accepted option is checked on the RPROPTS form.
Since the Disbursement Process (RPEDISB)
requires student approval under JIT conditions,
disbursement reject code 045 - Charges have not
been accepted is issued if the student has not yet
accepted the charges.
Y
Select all JIT records with
disbursement error code 045.
N
Do not select all JIT records with
disbursement error code 045.
Yes
Yes
You can only set this parameter to Y if
the Grant Type parameter is set to PL.
Selects all students with a status code of R Y
representing a rejected origination record. The
student is only selected if this is the latest origination
record for the student.
N
Selects all students with a status code of R representing a rejected disbursement record.
Based on the value for the Grant
Type parameter, select all rejected
origination records.
Do not select all rejected
origination records.
Y
Based on the value for the Grant
Type parameter, select all rejected
disbursement records.
N
Do not select all rejected
disbursement records.
January 2009
Parameters (cont) Name
Year to Date Reporting
Required?
Description
Values
No
This parameter selects year-to-date information on
students for the aid year by comparing Banner totals
to COD totals.
A
All grant recipients
B
Banner origination records
without matching reconciliation
records
C
COD reconciliation records
without matching Banner
origination records
D
Disbursement year to date
reporting
O
Offer amount year to date
reporting (the COD accepted
amount does not equal the Banner
Award Amount)
T
Transaction number year to date
reporting
V
Verification status year to date
reporting. (You can only use this
parameter if the Grant Type
parameter is set to PL (Pell).)
You can identify students when their Banner records
do not match the data COD has. You can run this
report on an as needed basis throughout the year as
well as at the end of the year.
This parameter works in conjunction with any
combination of other parameters for this process,
including population selection to limit the scope of
the population selected.
Application ID
No
Application code of the population selection.
Application Inquiry form (GLIAPPL)
If you enter a value for this parameter, you must also
enter a value for the Selection ID, Creator ID, and
User ID.
Selection ID
18-96
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application ID, User ID, and Creator
ID.
January 2009
Parameters (cont) Name
Required?
Description
Creator ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID, User ID, and Application ID.
User ID
No
The ID of the person using the subpopulation rule. If
you enter a value for this parameter, you must also
enter a value for the Selection ID, Application ID,
and Creator ID parameters.
Values
Pell Disbursement Locked for COD
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Pell Disbursement Locked for COD:
Name
ID
Rucker, Test6010
517006010
Rucker, Test3052
517003052
Rucker, Test6011
517006011
Records printed : 3
18-97
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
ACG Disbursement Locked for COD
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------ACG Disbursement Locked for COD:
Name
ID
Rucker, Test6010
517006010
Rucker, Test3052
517003052
Rucker, Test6011
517006011
Records printed : 3
SMART Disbursement Locked for COD
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------SMART Disbursement Locked for COD:
Name
ID
Rucker, Test6010
517006010
Rucker, Test3052
517003052
Rucker, Test6011
517006011
Records printed : 3
18-98
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Multiple Reporting Records
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Multiple Reporting Records:
Name
ID
SAR SSN
SAR INIT Grant Type
Record Type Activity Date
Rucker, Test6010
517006010 517006010 MI
AG
CE
30-NOV-2006
Rucker, Test6001
517006001 517006001 MI
AG
CE
30-JAN-2007
Records printed : 2
Rejected Origination Records
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Rejected Origination Records:
Name
Message Code Message Text
Award ID
Document ID
Rucker, Test6010
517006010A09000110001
2006-04-11T18:28:59.0065167096
Rucker, Test6001
517006001A09000110002
2006-04-18T12:15:59.0070488331
Records printed : 2
Rejected Disbursement Records
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Rejected Disbursement Records:
Name
Message Code Message Text
Award ID
Document ID
Disb Ref #/Seq #
Fund Code
Rucker, Test6010
517006010A09000110001
2006-11-28T13:06:54.0070488331
01/01
ACG2
Rucker, Test6001
517006001A09000110001
2006-11-28T13:06:54.0070488331
01/01
ACG
Records printed : 2
18-99
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Year To Date Records: Reconciliation Records without a Matching Banner
Origination Record
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Year To Date Records: Reconciliation Records without a Matching Banner Origination Record
Program Type: Pell
Banner Pell ID:
Banner
Trans#:
COD
Trans#:02
ID:
Verif Msg:
Banner Pell ID:
Banner
Trans#:
COD
Trans#:
ID:
Verif Msg:
Banner Pell ID:
Banner
Trans#:
COD
Trans#:01
ID:
Verif Msg:
Name: Rucker, Test6010
Verif Stat:
Offer Amt:
Verif Stat:S
Origination ID:
Acpt Amt:
Acpt Amt:
1100.00
Pd. Amt:
YTD Amt:
Name: Rucker, Test6001
Verif Stat:
Offer Amt:
Verif Stat: V
Origination ID:
Acpt Amt:
Acpt Amt:
2025.00
Pd. Amt:
YTD Amt:
Name: Rucker, Test3052
Verif Stat:
Offer Amt:
Verif Stat:V
Origination ID:
Acpt Amt:
Acpt Amt:
2600.00
Pd. Amt:
YTD Amt:
0.00
2025.00
2600.00
Records printed : 3
Banner Totals:
------------Offered Amount:
Accepted Amount:
Paid Amount:
0.00
0.00
0.00
COD Totals:
----------Accepted Amount:
YTD Paid Amount:
5725.00
4625.00
18-100
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Year To Date Records: Banner Originations without a Matching
Reconciliation Record
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Year To Date Records: Banner Originations without a Matching Reconciliation Record
Program Type: ACG
Banner Pell ID: 517006010RU01
Banner
Trans#:01
COD
Trans#:
ID: 517006010
Name: Rucker, Test6010
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:
1300.00
Acpt Amt:
Acpt Amt:
Banner Pell ID: 517006001RU01
Banner
Trans#:01
COD
Trans#:
ID: 517006063
Name: Rucker, Test6063
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:
750.00
Acpt Amt:
Acpt Amt:
Award ID:
1300.00
517006010A09000110001
Pd. Amt:
0.00
YTD Amt:
Award ID:
750.00
517006063A09000110001
Pd. Amt:
0.00
YTD Amt:
Records printed : 2
Banner Totals:
------------Offered Amount:
Accepted Amount:
Paid Amount:
2050.00
2050.00
0.00
COD Totals:
----------Accepted Amount:
YTD Paid Amount:
0.00
0.00
18-101
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Year To Date Records: All Grant Recipients
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Year To Date Records: All Grant Recipients
Program Type: Pell
Banner Pell ID: 517006010RU01
Banner
Trans#:01
COD
Trans#:02
ID: 517006010
Name: Rucker, Test6010
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:S
2600.00
Origination ID: 517006010RU200900011000
Acpt Amt:
2600.00
Pd. Amt:
0.00
Acpt Amt:
1100.00
YTD Amt:
0.00
Banner Pell ID: 517006001RU01
Banner
Trans#:01
COD
Trans#:
ID: 517006001
Name: Rucker, Test6001
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:
2600.00
Origination ID: 517006001RU200900011000
Acpt Amt:
2600.00
Pd. Amt:
0.00
Acpt Amt:
YTD Amt:
Banner Pell ID:
Banner
Trans#:
COD
Trans#:01
ID:
Verif Msg:
Name: Rucker, Test3052
Verif Stat:
Offer Amt:
Verif Stat:V
Origination ID: 517003052RU200900011000
Acpt Amt:
Pd. Amt:
Acpt Amt:
2600.00
YTD Amt:
2600.00
Records printed : 3
Banner Totals:
------------Offered Amount:
Accepted Amount:
Paid Amount:
5200.00
5200.00
0.00
COD Totals:
----------Accepted Amount:
YTD Paid Amount:
3700.00
2600.00
18-102
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Year To Date Records: All Grant Recipients
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Year To Date Records: All Grant Recipients
Program Type: ACG
Banner Pell ID: 517006010RU01
Banner
Trans#:01
COD
Trans#:02
ID: 517006010
Name: Rucker, Test6010
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:S
1300.00
Acpt Amt:
Acpt Amt:
Banner Pell ID: 517006001RU01
Banner
Trans#:01
COD
Trans#:
ID: 517006001
Name: Rucker, Test6001
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:
750.00
Acpt Amt:
Acpt Amt:
Banner Pell ID:
Banner
Trans#:
COD
Trans#:01
ID:
Verif Msg:
Name: Rucker, Test3052
Verif Stat:
Offer Amt:
Verif Stat:V
Acpt Amt:
Acpt Amt:
Award ID:
1300.00
1100.00
517006010A09000110001
Pd. Amt:
0.00
YTD Amt:
0.00
Award ID:
750.00
517006001A09000110001
Pd. Amt:
0.00
YTD Amt:
Award ID:
517003052A09000110001
Pd. Amt:
YTD Amt:
750.00
750.00
Records printed : 3
Banner Totals:
------------Offered Amount:
Accepted Amount:
Paid Amount:
2050.00
2050.00
0.00
COD Totals:
----------Accepted Amount:
YTD Paid Amount:
1850.00
750.00
18-103
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Year To Date Records: COD Accept Amount <> Banner Award Amount
30-JAN-2007 02:55:09 PM
BANNER University
1
Aid Year: 0809
COD Miscellaneous Report
RERGRNT
-----------------------------------------------------------------------------------------------------------------------------------Year To Date Records: COD Accept Amount <> Banner Award Amount
Program Type: ACG
Banner Pell ID: 517006010RU01
Banner
Trans#:01
COD
Trans#:02
ID: 517006010
Name: Rucker, Test6010
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:S
1300.00
Acpt Amt:
Acpt Amt:
Award ID:
1300.00
1100.00
517006010A09000110001
Pd. Amt:
0.00
YTD Amt:
0.00
Banner Pell ID: 517006001RU01
Banner
Trans#:01
COD
Trans#:01
ID: 517006063
Name: Rucker, Test6063
Verif Msg:
Verif Stat:V
Offer Amt:
Verif Stat:V
750.00
Acpt Amt:
Acpt Amt:
Award ID:
750.00
375.00
517006063A09000110001
Pd. Amt:
0.00
YTD Amt:
0.00
Records printed : 2
Banner Totals:
------------Offered Amount:
Accepted Amount:
Paid Amount:
2050.00
2050.00
0.00
COD Totals:
----------Accepted Amount:
YTD Paid Amount:
1475.00
0.00
18-104
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 COD Import Process (RERIM09)
Description
The RERIM09 Process imports Pell, ACG, SMART and Direct Loan XML response files received from COD.
Message classes that end with an OP are for documents imported to Banner from the COD System. This process
supports the following XML imports:
Pell Imports
• CRRC09OP — COD Document receipt file sent from the COD System to the school in response to the
CRPG09IN message class.
• CRPG09OP — Pell Origination and Disbursement records sent in response to the CRPG09IN message
class.
• CRND09OP — COD System-Generated Pell Negative Disbursement records
ACG Imports
• CRRC09OP — COD Document receipt file sent from the COD System to the school in response to the
CRAG09IN message class.
• CRAG09OP — ACG Origination and Disbursement records sent in response to the CRAG09IN message
class.
• CRND09OP — COD System-Generated ACG Negative Disbursement records
SMART Imports
• CRRC09OP — COD Document receipt file sent from the COD System to the school in response to the
CRSG09IN message class.
• CRSG09OP — Pell Origination and Disbursement records sent in response to the CRSG09IN message
class.
• CRND09OP — COD System-Generated SMART Negative Disbursement records
Direct Loan Imports
• CRRC09OP — COD Document receipt file sent from the COD System to the school in response to the
CRDL09IN message class.
18-105
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
• CRDL09OP — Direct Loan Origination, Origination Change, and Disbursement records sent in response to
the CRDL09IN message class.
• COD System-Generated Records
• CRPN09OP — Promissory Note Records.
• CRCO09OP — Credit Decision Override Records.
• CRPS09OP — Payment to Servicer Records.
• CRBN09OP — Booking Notification Records.
Combined Pell, ACG, SMART and Direct Loan Imports
• CRRC09OP — COD Document receipt file sent from the COD System to the school in response to the
CRAA09IN message class.
• CRAA09OP — Pell Origination and Disbursement records/ACG Origination and Disbursement records/
SMART Origination and Disbursement records/Direct Loan Origination, Origination Change, and
Disbursement records in response to the CRAA09IN message class.
Note
The RERIM09 Process verifies that a response to a Document ID has not already been
imported by checking the Document ID, Response Date, and Response Status field. (You can
view these fields on the COD Document Control form (REICODD). If the Document ID and
Response Date match the document being imported, and a status exists for the Response
Status field, the RERIM09 Process assumes that the data file has already been processed and
prevents the accidental re-importation of the same file.
To reload a file that has already been processed, you must open the XML document and
change the date in the <ProcessDate> tag to a different date so that it no longer matches the
Response Date as listed on REICODD for the document. This will allow you to reload the
„
document.
18-106
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
18-107
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
XML Import Document
Filename
Yes
The name of the file that you want to import from the
data home directory. The import process validates
the COD XML file to the 2.0e schema prior to
import. The import process does not validate the
filename to the message class.
Print RERIMEX Report
No
This parameter enables you to decide how you want
to print the RERIMEX report for the Document ID
you’re importing.
Banner Financial Aid 8.3
User Guide
Reports and Processes
B
Print both Import and Extract/
Sent records RERIMEX reports
(default)
I
Only print the Import records on
the RERIMEX report
N
No, do not print the RERIMEX
report
January 2009
2008-2009 COD Import Process
18-APR-2007 03:29:34 PM
BANNER University
Page 1
Aid Year: 0809
COD Import Process
RERIM09
---------------------------------------------------------------------------------------------Document ID
Created Date Time
Source Entity ID
Destination Entity ID
Receipt
=
=
=
=
=
2007-04-18T12:15:59.0070488331
2007-04-18T15:05:44.290
1
70488331
null
Document Type Code
Document Status Code
Process Date
Software Provider
Software Version
Full Response Code
=
=
=
=
=
=
RS
A
2007-07-07
Banner
7
F
Total Reporting Schools
Total Attended Schools
Total Students
= 1
= 1
= 9
Reporting School Entity ID
Financial Award Type
Total Count
Total Reported Award
Total Reported Disbursement
Total Count Accepted
Total Count Rejected
Total Count Corrected
Total Count Duplicate
Total Count Verification Selected
Total Count SS Administration
Total Financial Award Accepted
Total Financial Disbursement Accepted
Total Funded Disbursement Accepted
Total Non Funded Disbursement Accepted
Total Financial Award Corrected
18-108
Banner Financial Aid 8.3
User Guide
Reports and Processes
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
70488331
DLPLUS
1
1000.00
1000.00
1
0
0
0
0
0
1000.00
1000.00
1000.00
0
0
January 2009
18-APR-2007 03:29:34 PM
BANNER University
Page 2
Aid Year: 0809
COD Import Process
RERIM09
---------------------------------------------------------------------------------------------Financial Award Type
Total Count
Total Reported Award
Total Reported Disbursement
Total Count Accepted
Total Count Rejected
Total Count Corrected
Total Count Duplicate
Total Count Verification Selected
Total Count SS Administration
Total Financial Award Accepted
Total Financial Disbursement Accepted
Total Funded Disbursement Accepted
Total Non Funded Disbursement Accepted
Total Financial Award Corrected
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
DLSubsidized
4
14725.00
14725.00
4
0
0
0
4
4
14725.00
14725.00
3750.00
10975.00
0
Financial Award Type
Total Count
Total Reported Award
Total Reported Disbursement
Total Count Accepted
Total Count Rejected
Total Count Corrected
Total Count Duplicate
Total Count Verification Selected
Total Count SS Administration
Total Financial Award Accepted
Total Financial Disbursement Accepted
Total Funded Disbursement Accepted
Total Non Funded Disbursement Accepted
Total Financial Award Corrected
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
DLUnsubsidized
4
9225.00
9225.00
4
0
0
0
4
4
9225.00
9225.00
2500.00
6725.00
0
18-109
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
18-APR-2007 03:29:34 PM
BANNER University
Page 3
Aid Year: 0809
COD Import Process
RERIM09
---------------------------------------------------------------------------------------------Financial Award Type
Total Count
Total Reported Award
Total Reported Disbursement
Total Count Accepted
Total Count Rejected
Total Count Corrected
Total Count Duplicate
Total Count Verification Selected
Total Count SS Administration
Total Financial Award Accepted
Total Financial Disbursement Accepted
Total Funded Disbursement Accepted
Total Non Funded Disbursement Accepted
Total Financial Award Corrected
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
Pell
5
17100.00
8550.00
4
1
0
0
4
4
13050.00
6525.00
2475.00
4050.00
0.00
18-APR-2007 03:29:34 PM
BANNER University
Page 4
Aid Year: 0809
COD Import Process
RERIM09
---------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name.................:
Version......................:
One up Number................:
Aid Year Code................:
XML Document Imported........:
Print Report.................:
Number of Lines Per Page.....:
RERIM09
8.1
97795
0809
crtestop.001
B
60
Document ID: 2007-04-18T12:15:59.0070488331
Connected.
18-110
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
COD Import/Export Report (RERIMEX)
Description
The COD Import/Export Report enables you to review XML records extracted from the Banner database for
transmission to COD and to review COD responses that have been imported into the Banner database. Based on
report parameters, you can modify the output so that the process selects only extracted documents (records still in a
Sent status), only imported documents, or both extracted and imported documents. You can select records to report
based on Document ID or a selected date range based on either a response or extract date.
This report includes the following sections:
For Extracted Documents
DL Origination Records
DL Origination Change Records DL Disbursement Records
ACG Origination Records
ACG Disbursement Records
SMART Origination Records
SMART Disbursement Records
Pell Origination Records
Pell Disbursement Records
Identifier Change Records
For Imported Documents
DL Origination Records
DL Origination Change Records DL Disbursement Records
ACG Origination Records
ACG Disbursement Records
SMART Origination Records
SMART Disbursement Records
Pell Origination Records
Pell Disbursement Records
Negative Disbursement Records
Booking Notification Records
Payment to Servicer Records
Promissory Note Records
Credit Override Records
Identifier Change Records
This report can also be automatically run after the completion of the REREX09 and RERIM09 processes to
produce either the E (Extract)/Sent Records or I (Import) reports for the particular Document ID being processed
by REREX09 or RERIM09. To use this functionality, the Print Report parameter in the REREX09 or RERIM09
process must be set to the appropriate value.
18-111
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Identifier Compare Report
The Update Student Identifier? parameter enables you to optionally create a report identifying those students that
have a mismatch between their current COD Student Identifier (as displayed on REASTID) and the ISIR record (as
displayed on RNANA09). The COD Student Identifier consists of the student's last name, SSN, and date of birth.
These values are those that are compared for a mismatch between REASTID and RNANA09.
The following criteria determines if the compare between the current RERSTID Student Identifier record and the
ISIR record occurs, and if the student is reported on the output:
• If the aid year code on the RERSTID table is greater than the aid year being processed then no comparison
between RERSTID and RCRAPP1 occurs because the identifier currently in use for the student contains
data from a more recent aid year ISIR record.
• If the aid year code on the RERSTID table is less than or equal to the aid year being processed then the
comparison between RERSTID and RCRAPP1 occurs.
Note
This compare only affects the Student Identifier. This compare will not occur in any instance for
„
the Parent PLUS Borrower Identifier.
The fields compared are the Last Name, Date of Birth, and SSN. The compare is between:
• The Current Student Identifier record (as displayed on REASTID):
• The record in RERSTID where there is no Status Code
or
• if there is no record without a Status Code, the most recent record where the Status Code is A (Accepted)
• The current RCRAPP1 record (as displayed on RNANA09)
If a mismatch is found between RERSTID and RCRAPP1, the data is reported in the report output.
Note
The Student Identifier Compare report is not dependent on a Document ID existing in the
RERCODD table because the identifier currently in use for the student contains data from the
current or from a prior aid year ISIR record. Only the Import and Extract Reports generated
18-112
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
through parameter 02 are dependent on a Document ID in RERCODD. The Student Identifier
„
Compare report is strictly a compare between the RERSTID and RCRAPP1 tables.
Note
When the most recent Student Identifier record is in a Sent status on RERSTID, no
comparison takes place and the student is not reported in the output as you cannot make
manual updates on the REASTID form for these students. When the response to the Sent
identifier record is imported so that the identifier is no longer in a Sent status, the students will
„
be reported on the next run of the RERIMEX Student Identifier Compare report.
18-113
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Records to Report
No
Use this parameter to restrict your selection to either
extracted, imported documents, or both imported
and exported documents. The default is to report on
both extracted and imported documents.
E
When the process is run, you must enter values for
this parameter and/or the Identifier Compare
Report? parameter for the Student Identifier
Compare report. You can populate both of these
I
parameters to generate multiple report types, but you
cannot run the process with both parameters blank.
If a report type is selected for the 02 Records to
Report parameter when also running the Student
Identifier Compare report, the Extract/Import
reports are generated along with the Student
Identifier compare report. However, the data
reported on the Student Identifier Compare report is
completely independent of any of the other
parameter values entered for the process as they are
only used in conjunction with the Extract/Import
reports.
Document ID
18-114
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
B
Extracted Documents Only. This
option reports all records in the
selected Document IDs that have
not yet had a response from COD
that has been imported to Banner.
This includes records that are still
in a Sent status.
Imported Documents Only. This
option reports all records in the
Document IDs selected that have
received a response from COD
that has been imported to Banner.
This includes records that are no
longer in a Sent status.
Both Extracted and Imported
Documents (Default). This option
reports both records that are in a
Sent status (as selected with
option E above) and records that
are not in a Sent status (as selected
with option I above) for the
Document IDs selected.
This parameter enables you to request a report based Validated to existing Document IDs on
on one or more specific Document IDs. If you do not the REICODD form
know the specific Document ID, you can leave this
parameter blank and instead use the Date Selection
Type, Beginning Date, and Ending Date parameters
to select a particular range of dates.
January 2009
Parameters (cont) Name
Date Selection Type
Required?
Description
Values
No
You can select a date range for your report with this
parameter. The value that you enter determines if
you want to report by the extraction date or by the
response date of the records as displayed on
REICODD.
E
Extract Date
R
Response Date
If you enter a value for this parameter, you must
enter a range of dates with the Beginning Date and
Ending Date parameters.
18-115
Beginning Date
No
The beginning date for the extract or response date
range. You must enter a value for the Date Selection
Type and Ending Date parameters in order to use this
parameter.
Date
Ending Date
No
The ending date for the extract or response date
range. You must enter a value for the Date Selection
Type and Beginning Date parameters in order to use
this parameter.
Date
Identifier Compare
Report?
No
The Update Student Identifier? parameter enables
you to optionally create a report identifying those
students that have a mismatch between their current
COD Student Identifier (as displayed on REASTID)
and the ISIR record (as displayed on RNANA09).
The fields compared are the Last Name, Date of
Birth, and SSN.
Y
(Yes)
N
(No)
Banner Financial Aid 8.3
User Guide
Reports and Processes
Blank (Default)
January 2009
Financial Aid COD Extract/Import Report Sample - (Direct Loan Origination
Records - Extract Report/Records in Sent Status)
26-APR-2007 03:56:52 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 01
RERIMEX
DL ORIGINATION RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND
LOAN ID
--------------------------------------------------------------------------------------------------------------------------517009001 Rucker, Test8001 J
DLPLUS 517009001P09G80006001
517009005 Rucker, Test8005 F
DGPLUS 517009005P09G80006001
2007-04-26T15:56:51.0070488331
-----------------------------Total Records: 2
Financial Aid COD Extract/Import Report Sample - (Direct Loan Disbursement
Records - Extract Report/Records in Sent Status)
26-APR-2007 03:56:52 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 02
RERIMEX
DL DISBURSEMENT RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND
LOAN ID
DISB/SEQ TERM TYPE
--------------------------------------------------------------------------------------------------------------------------517009001 Rucker, Test8001 J
DLPLUS 517009001P09G80006001 01/01 200910 E
517009001 Rucker, Test8001 J
DLPLUS 517009001P09G80006001 02/01 200920 E
517009005 Rucker, Test8005 F
DGPLUS 517009005P09G80006001 01/01 200910 E
517009005 Rucker, Test8005 F
DGPLUS 517009005P09G80006001 02/01 200920 E
2007-04-26T15:56:51.0070488331
-----------------------------Total Records: 4
18-116
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (Direct Loan Origination
Change Records - Extract Report/Records in Sent Status)
24-APR-2007 08:38:10 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 01
RERIMEX
DL ORIGINATIONS WITH LOG RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND
LOAN ID
--------------------------------------------------------------------------------------------------------------------------517009004
517009006
Rucker, Test8004 L
RPRLAPP_PREP_OR_TEACH_IND
Rucker, Test8006 N
RPRLAPP_PREP_OR_TEACH_IND
DLUNSB
517009004U09G80006001
DLUNSB
517009006U09G80006001
From: N
To:
T
From: T
To:
G
2007-04-24T20:38:08.0070488331
-----------------------------Total Records: 2
Financial Aid COD Extract/Import Report Sample - (Pell Award Records Extract Report/Records in Sent Status)
10-APR-2007 07:16:27 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 01
RERIMEX
PELL AWARD RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
ORIG ID
SEQ NO
--------------------------------------------------------------------------------------------------------------------------517009004 Rucker, Test8004 L
517009004RU200955444400
4
2007-04-10T19:16:26.0012345678
-----------------------------Total Records: 1
18-117
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (Pell Disbursement
Records - Extract Report/Records in Sent Status)
10-APR-2007 07:16:27 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 02
RERIMEX
PELL DISBURSEMENT RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND CODE
ORIG ID
DISB/SEQ TERM
--------------------------------------------------------------------------------------------------------------------------517009004 Rucker, Test8004 L
PELL
517009004RU200955444400 02/01
200920
2007-04-10T19:16:26.0012345678
-----------------------------Total Records: 1
Financial Aid COD Extract/Import Report Sample - (ACG Award Records Extract Report/Records in Sent Status)
25-APR-2007 11:34:29 AM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 01
RERIMEX
ACG AWARD RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND CODE
ORIG ID
SEQ NO
--------------------------------------------------------------------------------------------------------------------------517009004 Rucker, Test8004 L
ACG2
517009004A09554444002
1
2007-04-25T11:34:28.0012345678
-----------------------------Total Records: 1
18-118
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (ACG Disbursement
Records - Extract Report/Records in Sent Status)
25-APR-2007 11:34:29 AM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 02
RERIMEX
ACG DISBURSEMENT RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND CODE
ORIG ID
DISB/SEQ TERM
--------------------------------------------------------------------------------------------------------------------------517009004 Rucker, Test8004 L
ACG2
517009004A09554444002
01/01
200910
2007-04-25T11:34:28.0012345678
-----------------------------Total Records: 1
Financial Aid COD Extract/Import Report Sample - (SMART Award Records Extract Report/Records in Sent Status)
10-MAY-2007 02:35:31 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 01
RERIMEX
SMART AWARD RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND CODE
ORIG ID
SEQ NO
--------------------------------------------------------------------------------------------------------------------------517009006 Rucker, Test8006 N
SMART
517009006T09620004001
1
2007-05-10T14:35:28.0070488331
-----------------------------Total Records: 1
18-119
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (SMART Disbursement
Records - Extract Report/Records in Sent Status)
10-MAY-2007 02:35:31 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 02
RERIMEX
SMART DISBURSEMENT RECORDS - Extract Report/Records in Sent Status
--------------------------------------------------------------------------------------------------------------------------ID
NAME
FUND CODE
ORIG ID
DISB/SEQ TERM
--------------------------------------------------------------------------------------------------------------------------517009006 Rucker, Test8006 N
SMART
517009006T09620004001
01/01
200920
2007-05-10T14:35:28.0070488331
-----------------------------Total Records: 1
Financial Aid COD Extract/Import Report Sample - (Pell Origination Records Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 01
RERIMEX
PELL ORIGINATION RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
162440011
162440015
162440014
162440013
162440012
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Eleven K
Fifteen O
Fourteen N
Thirteen M
Twelve L
162440011MU200960000500
162440015MU200960000500
162440014MU200960000500
162440013MU200960000500
162440012MU200960000500
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
-----------------------------Total Accepted Records: 5
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
18-120
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (Pell Disbursement
Records - Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 08
RERIMEX
PELL DISBURSEMENT RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
162440011
162440013
Muehlhof, Eleven K
Muehlhof, Thirteen M
162440011MU200960000500
162440013MU200960000500
1 /1
1 /1
2007-04-06T09:13:52.0090488335
2007-04-06T09:13:52.0090488335
2007-04-06T08:13:52.0090488335
-----------------------------Total Accepted Records: 2
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
18-121
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (Direct Loan Origination
Records - Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 02
RERIMEX
DL ORIGINATION RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------Accepted
162440011
162440011
162440015
162440017
162440017
162440016
162440016
162440013
162440012
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Muehlhof,
Eleven K
Eleven K
Fifteen O
Seventeen Q
Seventeen Q
Sixteen P
Sixteen P
Thirteen M
Twelve L
162440011S09G80005001
162440011U09G80005001
162440015U09G80005001
162440017S09G80005001
162440017U09G80005001
162440016S09G80005001
162440016U09G80005001
162440013U09G80005001
162440012S09G80005001
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
Muehlhof, Seventeen Q
Muehlhof, Sixteen P
162440017P09G80005001
162440016P09G80005001
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
Acpt/Cr Pending
162440017
162440016
2007-04-04T12:41:19.0090488335
-----------------------------Total Accepted Records: 9
Total Rejected Records: 0
Total Acpt/Cr Accept Records: 0
Total Acpt/Cr Denied Records: 0
Total Acpt/Cr Pending Records: 2
18-122
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (Direct Loan Change
Records - Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 17
RERIMEX
DL ORIGINATIONS WITH LOG RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
179400010
Wood, Joseph J
179400010U09G80006001
RPRLAPP_PREP_OR_TEACH_IND
From: N
To:
G
RPRLAPP_DISC_NEED_PRINT_FLAG
From: Y
To:
Z
2007-04-11T16:09:17.0070488331
2007-04-11T16:09:17.0070488331
-----------------------------Total Accepted Records: 2
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
Financial Aid COD Extract/Import Report Sample - (ACG Origination Records Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 04
RERIMEX
ACG ORIGINATION RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
Fund Code R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
162440011
162440012
Muehlhof, Eleven K
Muehlhof, Twelve L
162440011A07600005001
162440012A07600005001
ACG
ACG2
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
-----------------------------Total Accepted Records: 2
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
18-123
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (ACG Disbursement
Records - Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 09
RERIMEX
ACG DISBURSEMENT RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
Fund Code R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
162440011
Muehlhof, Eleven K
162440011A07600005001
ACG
1 /1
2007-04-06T09:13:52.0090488335
2007-04-06T09:13:52.0090488335
-----------------------------Total Accepted Records: 1
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
Financial Aid COD Extract/Import Report Sample - (SMART Origination
Records - Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 05
RERIMEX
SMART ORIGINATION RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
Fund Code R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
162440014
162440013
Muehlhof, Fourteen N
Muehlhof, Thirteen M
162440014T07600005001
162440013T07600005001
SMART2
SMART
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
2007-04-04T12:41:19.0090488335
-----------------------------Total Accepted Records: 2
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
18-124
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Extract/Import Report Sample - (SMART Disbursement
Records - Import Report)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 10
RERIMEX
SMART DISBURSEMENT RECORDS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------Banner ID
Name
Orig/Loan ID
Fund Code R#/S# Document ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
162440013
Muehlhof, Thirteen M
162440013T07600005001
SMART
1 /1
2007-04-06T09:13:52.0090488335
2007-04-06T09:13:52.0090488335
-----------------------------Total Accepted Records: 1
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
Financial Aid COD Import/Export Report — (Student Identifier Compare)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 56
RERIMEX
STUDENT IDENTIFIER COMPARE REPORT
----------------------------------------------------------------------------------------------------------------------------COD
ISIR
-------------------------------------------------------------------------------------ID
NAME
SSN
LAST NAME
BIRTH DATE
SSN
LAST NAME
BIRTH DATE
----------------------------------------------------------------------------------------------------------------------------162440001 Muehlhof, One A
162440001
Muehlhof
01-JAN-1985
162440001
Muehlhof
01-JAN-1986
162440002 Muehlhof, Two B
162440002
Muehlhof
02-FEB-1985
162440002
Muehlhof
02-FEB-1986
162440003 Muehlhof, Three C
162440003
Muehlhof
03-MAR-1982
162440003
Muehlhof
03-MAR-1986
162440004 Muehlhof, Four D
162440004
Muehlhof
04-APR-1984
162440004
Muehlhof
04-APR-1986
162440005 Muehlhof, Five E
162440005
Mismatch
01-JAN-1985
162440005
Muehlhof
05-MAY-1986
162440006 Muehlhof, Six F
162440006
Muehlhof
06-JUN-1986
162440006
MUEHLHOF
06-JUN-1987
-----------------------------Total Records:
6
18-125
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid COD Import/Export Report — (Identifier Change Records and
Identifier Records with Edits/Rejects)
10-MAY-2007 02:15:47 PM
AID YEAR: 0809
BANNER University
Financial Aid COD Extract/Import Report
PAGE 13
RERIMEX
IDENTIFIER CHANGE RECORDS AND IDENTIFIER RECORDS WITH EDITS/REJECTS - IMPORT REPORT
--------------------------------------------------------------------------------------------------------------------------ID
NAME
ID TYPE ID SEQ PLUS ID
--------------------------------------------------------------------------------------------------------------------------'A'ccepted
179400010
Wood, Joseph J
Student
4
2007-04-11T09:48:56.0070488331
-----------------------------Total Accepted Records: 1
Total Corrected Records: 0
Total Duplicate Records: 0
Total Rejected Records: 0
18-126
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
ISIR Print Process (RERISxx)
The ISIR Print Process is used to print ISIRs in the format recommended by the Department of Education for a
specified aid year. The print specifications are in the EDE Technical Reference Manual.
Description
When printing ISIRs, you have the option to print the following:
• Comment text
• Certification page
• NSLDS page
Also, ISIRs may be printed for an individual student or a group of student as follows:
• An individual student’s ISIR using a Banner Student ID, Transaction Number (optional), and Sequence
Number (optional)
• A group of ISIRs using Population Selection
• A group of ISIRs using a the date range of the Processed Date or Create Date
If a population is used, the ISIR that is printed is the one that matches the transaction number in the student’s
RORSTAT record for the parameter aid year.
Note
Certain ISIR Comment Codes cause the C code to be printed on the ISIR. As part of Banner's
annual ISIR print process updates, ISIR Comment Codes are reviewed to ensure that the C
„
code prints when required.
Parameters
18-127
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Print Comment
Text (Y/N)
No
Print the Comment Text, Yes or No.
Y Yes (default)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Required?
Description
Values
Print Certification
Page (Y/N)
No
Print the Certification Page, Yes or No.
Y
Yes (default)
Print NSLDS
Page (Y/N)
No
Print the NSLDS Page, Yes or No.
Y
Yes (default)
Banner ID Trans No
No
Enter Banner Student ID, transaction number, and
sequence number in this format: 111111111 02 003.
Application ID
No
General area for which the selection ID was defined.
Selection ID
No
Code that identifies the sub-population to work with.
Creator ID
No
The ID of the person who created the sub-population
rules
User ID
No
The ID of the person using the sub-population rules
Postscript Laser Printer
(Y/N)
No
Print ISIRs to the Laser Printer, Yes or No.
Y
Yes
N
No (default)
Beginning Processed
Date
No
Not used at this time
Not used at this time
18-128
The processing start date for the print population.
DD-MMM-YYYY
Ending Processed Date
The processing end date for the print population.
DD-MMM-YYYY
Beginning Created Date
The creation start date for the print population.
DD-MMM-YYYY
Ending Created Date
The creation end date for the print population.
DD-MMM-YYYY
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
ISIR Print Process Sample
2005-2006 Institutional Student Information Record
****************************************************************************************************
*
IMPORTANT: Read ALL information to find out what to do with this Report.
*
****************************************************************************************************
OMB Number: 1845-0008
Studentnn A Blattner
March 17, 2005
123 E. RAVALLI ST
HAMILTON MT 59840
EFC
There are issues with your application information that need to be resolved before your eligibility
can be determined. Read this letter carefully and review any items marked on this ISIR. After
making all necessary corrections, you must return all documentation to your school.
The name you reported on your application does not match the name in the Social Security
Administration's (SSA) records for your SSN. You should correct your SSN or name. If your name is
correct, you need to confirm it by re-entering it. If you confirm your name, you should also
contact the SSA to make sure that they correct it in their records.
If you need to make corrections to your information, you may make them on the web at
www.fafsa.ed.gov. You must use your PIN to access your record online. If you need help with your
ISIR, contact your school Financial Aid Administrator (FAA) or the Federal Student Aid Information
Center at 1-800-4-FED-AID (1-800-433-3243). If your address changes, make the correction online,
contact your school, or call 1-800-4-FED-AID and ask a customer service representative to make the
change for you.
Page 1 of 4
18-129
Banner Financial Aid 8.3
User Guide
Reports and Processes
200-50-6317 BL 01
January 2009
2005-2006 Institutional Student Information Record
Student ID
200-50-6317 BL 01
STEP ONE (THE STUDENT) (Q1-Q31)
Name
Studentnn A Blattner
Address:
123 E. RAVALLI ST
HAMILTON MT 59840
h Social Security Number
200-50-6317
Date of Birth
08/26/1961
Permanent Home Phone #
Driver's Lic #
NONE
Citizenship Status
U.S. CITIZEN
Alien Registration Number
E-mail Address
Marital Status
UNMARRIED
Marital Status Date
10/1997
State of Legal Residence
MT
Legal Resident Before 1-1-2000?
YES
Legal Residence Date
Are You Male?
NO
Register for Selective Service?
Degree/Certificate
ASSOC.TECHNICAL
Grade Level in College
1ST YR ATT PREV
HS Diploma or GED Received?
YES
First Bachelor's Degree by 7-1-2005?
NO
Interested in Student Loans?
YES
Interested in Student Employment?
YES
Father's Educational Level
HIGH SCHOOL
Mother's Educational Level
HIGH SCHOOL
Drug Conv Affecting Elig?
NO
STEP TWO (STUDENT & SPOUSE) (Q32 - Q47)
Tax Return Filed?
NOT FILING
Type of 2004 Tax Return Used
Eligible to File 1040A or 1040EZ?
Adjusted Gross Income
U.S. Income Tax Paid
Exemptions Claimed
Student's Inc Earned from Work
1200
Spouse's Inc Earned from Work
Total from Worksheet A
0
Total from Worksheet B
0
Total from Worksheet C
1600
Cash, Savings, and Checking
0
Net Worth of Investments
0
Net Worth of Business/Farm
0
No. of Months VA Benefits Received
Monthly VA Education Benefits
EFC
Dependency Status
STEP THREE (THE STUDENT) (Q48 - Q54)
Born Before 1-1-1982?
Working on Master's/Doctorate Program?
Is Student Married?
Have Children You Support?
Dependents Other Than Children/Spouse?
Orphan or Ward of the Court?
Veteran of U.S. Armed Forces?
Banner Financial Aid 8.3
User Guide
Reports and Processes
YES
NO
NO
YES
NO
NO
NO
STEP FOUR (PARENTS) (Q55 - Q83)
Marital Status
Marital Status Date
Father's/Stepfather's SSN
Father's Last Name
Father's First Initial
Father's Date of Birth
Mother's/Stepmother's SSN
Mother's Last Name
Mother's First Initial
Mother's Date of Birth
Number of Family Members
Number in College
State of Legal Residence
Legal Residents before 1-1-2000?
Legal Residence Date
E-mail Address
Tax Return Filed?
Type of 2004 Tax Return Used
Eligible to File 1040A or 1040EZ?
Adjusted Gross Income
U.S. Income Tax Paid
Exemptions Claimed
Father's Inc Earned from Work
Mother's Inc Earned from Work
Total from Worksheet A
Total from Worksheet B
Total from Worksheet C
Cash, Savings, and Checking
Net Worth of Investments
Worth of Business/Farm
STEP FIVE (STUDENT HH) (Q84 - Q85)
Number of Family Members
Number in College
*=assumption h=highlight flag #=correction this trans @=corrected previous trans
18-130
Y
2
1
Page 2 of 4
January 2009
2005-2006 Institutional Student Information Record
Student ID
Last Name
200-50-6317 BL 01
Blattner
STEP SIX (Q86 - Q98)
School #1 009314 Housing
School #2 002528 Housing
School #3
Housing
School #4
Housing
School #5
Housing
School #6
Housing
Enrollment Status
#1
#2
#3
#4
#5
#6
EFC
OFF CAMPUS
OFF CAMPUS
OFFICE INFORMATION
DRN
Primary EFC Type
FULL TIME
Secondary EFC Type
Processed Date
02/01/2005
STEP SEVEN (Q99 - Q104)
Transaction Data Source/Type:
Date Application Completed
01/25/2005
WEB STUDENT - APPLICATION
Signed By
APPLICANT
Source of Correction
Preparer's SSN
Federal School Code Indicator
Preparer's EIN
Reject Override Codes:
Preparer's Signature
A: B: C: G: J: K: N: W: 3: 12:
Assumption Override Codes:
1: 2: 3: 4: 5: 6:1
---------------------------------------------------------------------------------------------------FAA INFORMATION
CPS Pushed ISIR Flag
Date ISIR Received
02/09/2005
Rejects Met:
D
Verification Flag
Verification Tracking Flag
FAA Adjustement
Dependency Override
Transaction Receipt Date
01/25/2005
ETI
1
Reprocessing Code
Correction # Applied To
Processed Record Type
Application Receipt Date
01/25/2005
Pell Elig Flag
Primary EFC
Mon 1
Mon
Mon 2
Mon
Mon 3
Mon
Mon 4
Mon
Mon 5
Mon
Mon 6
7
8
10
11
12
Secondary EFC
Mon 1
Mon 7
Mon 2
Mon 8
Mon 3
Mon 10
Mon 4
Mon 11
Mon 5
Mon 12
Mon 6
Auto Zero TFC Flag
YES
EFC Change Flag
NO CHANGE
SNT Flag
Match Flags:
SSN 3
SSA N DHS
DHS Ver. No.
NSLDS Transaction Number
SS
01
Intermediate
TI
ATI
STX
EA
IPA
AI
CAI
DNW
NW
APA
Values
0 PCA
0 AAI
0 TSC
0 TPC
0 PC
0 STI
SATI
0 SIC
0 SDNW
0 SCA
FTI
Duplicate SSN Flag
Address Only Correction
SAR C Change Flag
NSLDS 1 VA
DHS Sec. Conf.
SS Registration Flag
NSLDS Database Results Flag 3
0
0
0
0
0
0
Father SSN
Mother SSN
8
8
Comments: 050,061,006
*=assumption h=highlight flag #=correction this trans @=corrected previous trans
18-131
Banner Financial Aid 8.3
User Guide
Reports and Processes
Page 3 of 4
January 2009
Studentnn A Blattner
200-50-6317
2005-2006 NSLDS FINANCIAL AID HISTORY
Processed: 02/01/2005
This page contains your previous financial aid information, which is contained in the
National Student Loan Data System (NSLDS). Your Financial Aid Administrator will use it
to determine your eligibility.
****************************************************************************************************
Overpayment: Contact: Discharged
Defaulted
Loan Sat.
Active
PostScreening
Loan Flag:N
Loans:N
Repayment:N
Bankruptcy:N
Reason:
Pell:
N N/A
FSEOG:
N N/A
Perkins:
N N/A
****************************************************************************************************
Aggregate Amount
Outstanding
Pending
Total:
FFEL/Direct Loans:
Prin. Bal.
Disb(s)
Subsidized Loans:
N/A
N/A
N/A
Unsubsidized Loans:
N/A
N/A
N/A
FFEL Unallocated Consol. Loans:
N/A
N/A
N/A
Combined Loans:
N/A
N/A
N/A
Perkins Loans:
Outstanding Principal Bal.:
N/A
Current Year Loan Amount:
N/A
****************************************************************************************************
MPN/Loan Limit Information
Direct Loan Subsidized/Unsubsidized MPN:Not on File
Direct Loan PLUS MPN:
Not on File
Subsidized Loan Limit Flag:
Not near limit
Combined Loan Limit Flag:
Not near limit
Page 4 of 4
18-132
Banner Financial Aid 8.3
User Guide
Reports and Processes
200-50-6317 BL 01
January 2009
17-MAR-2005 12:52:39 PM
Aid Year: 0506
BANNER University
ISIR Print Process
Page:
1
* * * REPORT CONTROL INFORMATION * * *
Parameters have been entered via Job Submission.
Parameter Name
_______________________________________
Value
________________
Program Name:
Parameter Seq No:
Aid Year Code:
Print Comment Text (Y/N):
Print Certification Page (Y/N):
Print NSLDS Page (Y/N):
Banner ID & Optional Trans No:
Application Code:
Report Selection Query ID:
Creator ID of Selection ID:
User ID:
PostScript Laser Print (Y/N):
Beginning Processed Date:
Ending Processed Date:
Beginning Created Date:
Ending Created Date:
RERIS06(7.2)
36176
0506
Y
N
Y
200506317 01 001
Total ISIR's Selected:
Total Pages Printed:
1
4
N
****** END OF REPORT ******
18-133
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 Grant Origination Creation Process (REROR09)
Description
The Grant Origination Creation Process enables you to create Pell Grant, ACG, and SMART Grant origination
records. You can also use REROR09 to process data requests scheduled on the Data Request Record form
(RERRDRQ). These requests include Multiple Reporting Records (MRRs), Reconciliation records, Statement of
Account records, and Year-to-Date records.
Conditions for the Creation of Pell Originations
• The REROR09 Process creates origination records for all students who have the Pell Origination field
checked on the Packaging Group Information block of the RPAAWRD, RPAAPMT, or ROARMAN forms.
The REROR09 process creates an origination record for those students who already have Pell awards for
the year, but do not yet have an origination record.
Conditions for the Creation of ACG and SMART Originations
Unlike Pell origination records, ACG and SMART originations do not use an origination indicator to determine if
an origination needs to be created for the fund. Instead, when the REROR09 process is run it determines if an
origination already exists for the fund code, and if an origination does not exist, creates the origination record. If an
origination already exists for the fund code, the process compares the current awarded amount for the fund to the
amount due to the student on the origination record. If the awarded amount is more than the amount due to the
student, an updated origination record is created for the student with the increased amount. This is the only time an
updated origination is automatically created for the student through the REROR09 process. Other data changes that
are needed on an origination record must be made using the REAOR09 form.
• In order for an ACG or SMART origination record to be created, a Pell origination record must already
exist or a Pell origination must be in the process of being created in this same run of the REROR09 process.
If no Pell origination exists, the ACG or SMART origination is not created. (This Pell award validation rule
for the ACG or SMART grant award is overridden when the No Pell override field on the RPAAPMT,
RPAAWRD, or RPAMOFF forms has been used to award the ACG or SMART grant when the student does
not have a Pell award in Banner.)
• The year level for any ACG or SMART fund code must be defined on the Fund Management form
(RFRMGMT). The ACG Grade Level field cannot be blank for an ACG fund and the SMART Grade
Level field cannot be blank for a SMART Fund. If the indicator is blank for the fund code, the ACG or
SMART origination is not created.
18-134
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
• If the existing active origination for the Fund Code is locked, a new origination is not created for the Fund
Code even if the data has changed as compared to the current locked origination record.
For example, if the student’s existing origination for fund code ACG1 is locked, a new sequence of the
ACG1 origination is not created.
However, if the student also needs a Fund Code ACG2 origination created and the student does not have an
existing ACG2 fund code origination record that is locked (and all other conditions are passed), the ACG2
origination record is created.
• If the existing active origination for the fund code is in a S (Sent) status in the Action Code field on the
ACG/SMART window of the REAOR09 form, a new origination is not created for the fund code.
For example, if the student’s existing origination for fund code ACG1 in a S (Sent) status, a new sequence
of the ACG1 origination is not created.
However, if the student also needs a Fund Code ACG2 origination created and the student does not have an
existing ACG2 fund code origination record that is in a S (Sent) status (and all other conditions are passed),
the ACG2 origination is created.
• If the student does not have a valid value in the SAR Transaction Number field on the ROAPELL form,
the origination is not created.
• The Year in College determined for the student must match the Grant Type being created on the ACG/
SMART window of the REAOR09 form.
For example, if the student has a Year in College value of 2nd year, sophomore, and the Grant Type value
is A1=ACG Year 1, the origination is not created.
The following levels are valid for Grant Type and Year in College combinations:
18-135
Grant Type
Year in College
A1=ACG Year 1
A2=ACG Year 2
S3=SMART Year 3
S4=SMART Year 4
1st year, no prior college or 1st year, prior college
2nd year, sophomore
3rd year, junior
4th year, senior
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Create Pell Originations
Yes
This parameter enables you to create Pell origination Y
records for all students for the aid year who have the
N
Pell Origination field checked on the Packaging
Group Information window of the RPAAWRD,
RPAAPMT, or ROARMAN forms.
Create Pell Origination Records
This parameter enables you to create ACG
origination records for all students for the aid year
who have an ACG award with an Accepted status or
Offered status (depending on the Create
Originations Award Stat parameter setting.)
Y
Create ACG Origination Records
N
Do not create ACG Origination
Records
This parameter enables you to create SMART
origination records for all students for the aid year
who have a SMART award with an Accepted status
or Offered status (depending on the Create
Originations Award Stat parameter setting.)
Y
Create SMART Origination
Records
N
Do not create SMART
Origination Records
This parameter determines the value of the student
award status when the origination record is created.
O
Create origination records with an
Offered and Accepted award
status
A
Create origination records with an
Accepted award status.
Create ACG
Originations
Yes
Create SMART
Originations
Yes
Create Originations
Award Stat
Yes
When this parameter is A, an origination record is
created for any student with an Accepted award.
18-136
Banner Financial Aid 8.3
User Guide
Reports and Processes
Do not create Pell Origination
Records
January 2009
Parameters (cont) Name
Proc Data Request
Records
Required?
Description
Values
Yes
This parameter processes the data requests
scheduled on the Data Request Record form
(RERRDRQ). You can use the RERRDRQ form to
request Multiple Reporting Records (MRRs),
Reconciliation records, Statement of Account
records, and Year-to-Date records.
PL Process Pell Data Requests
(PGRQ09IN)
AG Process ACG Data Requests
(AGRQ09IN)
SG Process SMART Data Requests
(SGRQ09IN)
AL Process All Grant Type Data
Requests (PGRQ09IN,
AGRQ09IN, and/or SGRQ09IN)
NO Do not process data request
records (default)
18-137
Application ID
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection ID, Creator ID, and User ID
parameters.
Application Inquiry form (GLIAPPL)
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application ID, User ID, and Creator
ID parameters.
Population Selection Inquiry form
(GLISLCT)
Creator ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID, User ID, and Application ID
parameters.
User ID
No
The ID of the person using the subpopulation rule. If
you enter a value for this parameter, you must also
enter a value for the Selection ID, Application ID,
and Creator ID parameters.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 Grant Origination Creation Process Report Sample
22-APR-2007 10:14:18 AM
Aid Year: 0809
BANNER University
2008-2009 Grant Origination Process
1
REROR08
PELL ORIGINATIONS
-----------------------------------------------------------------------------------------------------------------------------------Student ID | Origination/Award ID
| GRANT TYPE
| RESULT/COMMENT
----------- | ------------------------- | ------------- | -------------------------------------------------------------------------586070302
|
| PELL
| *ERROR* Origination Create - No SAR Tran No
ACG ORIGINATIONS
-----------------------------------------------------------------------------------------------------------------------------------Student ID | Origination/Award ID
| GRANT TYPE
| FUND CODE | RESULT/COMMENT
----------- | ------------------------- | ------------- | --------- | -------------------------------------------------------------586070201
| 586070201A09620004001
| ACG YEAR 1
| ACG
| *ERROR* Award Amount is not valid.
781300011
| 781300011A09554444001
| ACG YEAR 1
| ACG
| *ERROR* Year In College is not valid for grant type.
SMART ORIGINATIONS
-----------------------------------------------------------------------------------------------------------------------------------Student ID | Origination/Award ID
| GRANT TYPE
| FUND CODE | RESULT/COMMENT
----------- | ------------------------- | ------------- | --------- | -------------------------------------------------------------517006008
| 517006008T09554444001
| SMART YEAR 3 | SMART
| *ERROR* CIP Code is missing.
586070301
| 586070301T09620004001
| SMART YEAR 3 | SMART
| *ERROR* Award Amount is not valid.
781300011
| 781300011T09554444001
| SMART YEAR 3 | SMART
| *ERROR* Year In College is not valid for grant type.
Contd...2
18-138
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2008-2009 Grant Origination Creation Process Report Sample
22-APR-2007 10:14:18 AM
Aid Year: 0809
BANNER University
2008-2009 Grant Origination Process
2
REROR09
CONTROL SUMMARY
--------------Program Name.................................:REROR09(8.1)
One up Number................................:145337
PARAMETERS
Aid Year Code................................:0809
Create Pell Originations.....................:Y
Create ACG Originations......................:Y
Create SMART Originations....................:Y
Create Originations Award Status.............:O
Proc Data Request Records....................:N
Application Code.............................:FINAID
Selection ID.................................:PNN2
Creator ID...................................:PNGUYEN
User ID......................................:PNGUYEN
Number of lines per page.....................:60
FILE NAMES
Report file name.............................:/export/home/pnguyen/jobsub/reror09_145337.lis
Data Request Extract file name...............:
PELL ORIGINATION CREATE
Total Student Records Read...................:1
Total Student Records Rejected...............:1
Total PELL Origination Records Created.......:0
ACG ORIGINATION CREATE
Total Records Read...........................:2
Total Records Rejected.......................:1
Total ACG Origination Records Created........:1
SMART ORIGINATION CREATE
Total Records Read...........................:3
Total Records Rejected.......................:2
Total SMART Origination Records Created......:1
18-139
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Fund Balance Roll Process (RFPFBRL)
The new Fund Balance Roll Process rolls fund balances forward from one aid year to the next aid year.
If the Prior Balance amount is not zero in the To Aid Year, the process does not update the Prior Balance amount
for that particular fund. An error message is included in the output file. The process continues on to the next fund to
process any remaining fund balance rolls.
When the Prior Balance amount is updated, the Total Allocated Amount is also updated to the total of the Prior
Balance (RFRASPC_PRIOR_BAL_AMT) plus the Transferred Amount (RFRASPC_TRANSFER_AMT) plus the Budget
Allocated (RFRASPC_BUDG_ALLOC_AMT) amount.
When the Prior Balance amount is updated, the Over-Commitment Percent (RFRASPC_AVAIL_OFFER_PCT) is
also recalculated by dividing the Available to Offer amount (RFRASPC_AVAIL_OFFER_AMT) by the new Total
Allocated Amount (RFRASPC_TOTAL_ALLOC_AMT).
Fund Balance Roll Option
• If the Fund Balance Roll Option (parameter 07) is set to O (Offered), the process rolls the Total Allocated
Amount (RFRASPC_TOTAL_ALLOC_AMT) minus the Current Offer amount (RFRASPC_OFFER_AMT) in the
From Aid Year to the Prior Balance amount (RFRASPC_PRIOR_BAL_AMT) in the To Aid Year.
• If the Fund Balance Roll Option (parameter 07) is set to A (Accepted), the process rolls the Total Allocated
Amount (RFRASPC_TOTAL_ALLOC_AMT) minus the Accepted Amount (RFRASPC_ACCEPT_AMT) in the From
Aid Year to the Prior Balance amount (RFRASPC_PRIOR_BAL_AMT) in the To Aid Year.
• If the Fund Balance Roll Option (parameter 07) is set to P (Paid), the process rolls the Total Allocated
Amount (RFRASPC_TOTAL_ALLOC_AMT) minus the Paid Amount (RFRASPC_PAID_AMT) in the From Aid
Year to the Prior Balance amount (RFRASPC_PRIOR_BAL_AMT) in the To Aid Year.
Adjusting the Prior Year Allocation Amount
If the Adjust From Yr Total Allocated option (parameter 08) is set to Y (Adjust prior year allocation amount), the
prior year Budget Allocated amount and Total Allocated Amount are reduced by the adjustment amount
calculated from the Fund Balance Roll Option for the From Aid Year code and the current fund code being
processed. The Over-Commitment Percent amount is also recalculated.
18-140
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
Name
Required?
Description
Values
From Aid Year
Yes
Aid year code from which fund balances are rolled.
Aid Year Inquiry (ROIAIDY)
To Aid Year
Yes
Aid year code to which fund balances are rolled.
Aid Year Inquiry (ROIAIDY)
Fund Code
No
Fund code balance to roll.
Fund Base Data (RFRBASE)
Fund Source
No
Fund source balance to roll.
Fund Source Code Validation
(RTVFSRC)
Fund Type
No
Fund type balance to roll.
Financial Aid Fund Type Validation
(RTVFTYP)
Federal Fund ID
No
Federal Fund ID balance to roll.
Federal Fund ID Inquiry (RFIFFID)
Fund Balance Roll
Option
Yes
Rolls the prior year amount using the remaining
offered, accepted, or paid amount. The default is the
offered amount.
O (Offered)
A (Accepted)
P (Paid)
Adjust From Yr Total
Allocated
Yes
Print Option
Yes
Adjust the prior year allocation amount by the
amount rolled? (Y or N) The default is N.
Y (Adjust prior year allocation amount)
Print the report? (Y or N) The default is Y.
Y (Yes, print the report.)
N (Do not adjust prior year allocation
amount)
N (No. do not print the report.)
18-141
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
12-DEC-2007 01:56:00 PM
BANNER System Test
PAGE
1
AID YEAR: 0809 2008-2009 Aid Year
Fund Balance Roll Process
RFPFBRL
-----------------------------------------------------------------------------------------------------------------------------------FUND
DIRECT
DESCRIPTION
Federal Direct Stafford Loan
SOURCE
FDRL
TYPE
LOAN
FFID
STFD
--- FROM AID YEAR 0708 --49606.00
--- TO AID YEAR 0809 --49606.00
DLPLUS
Federal Direct Parent Loan
FDRL
LOAN
PLUS
20000.00
20000.00
DLUNSB
Federal Direct Unsub. Stafford
FDRL
LOAN
STFD
33000.00
33000.00
GPLUS
Grad PLUS loan
FDRL
LOAN
PLUS
999999.00
999999.00
ICL
Income Contingent Loan
OTHR
LOAN
ICL
0.00
0.00
INLN
Institutional Loan
INST
LOAN
GTIV
Fund balance not rolled; non-zero balance already exists.
STFD
Stafford
FDRL
LOAN
STFD
Fund balance not rolled; no fund exists for to aid year.
NURSLN
Nursing Loan Program
FDRL
LOAN
NSL
PERK
Federal Perkins Loan
FDRL
LOAN
PLUS
Fed. Parent Loan for Student
FDRL
STFD
Federal Stafford Loan
MNLSUB
ELSUB
0.00
0.00
PERK
9984299.00
9984299.00
LOAN
PLUS
47000.00
47000.00
FDRL
LOAN
STFD
992124.00
992124.00
Manual Sub loan
FDRL
LOAN
STFD
200000.00
200000.00
EL Sub
FDRL
LOAN
STFD
25555.00
25555.00
ELUNSUB EL Unsub
FDRL
LOAN
STFD
555000.00
555000.00
UNSTFD
FDRL
LOAN
STFD
99996374.00
99996374.00
18-142
Federal Unsub. Stafford Loan
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
12-DEC-2007 01:56:00 PM
BANNER System Test
PAGE
2
AID YEAR: 0809 2008-2009 Aid Year
Fund Balance Roll Process
RFPFBRL
-----------------------------------------------------------------------------------------------------------------------------------* * * REPORT CONTROL INFORMATION * * *
Program Name.................................: RFPFBRL
Version......................................: 8.0
Report Sequence Number.......................:
From Aid Year................................:
To Aid Year..................................:
Fund Code....................................:
Fund Source..................................:
Fund Type....................................:
Federal Fund ID..............................:
Fund Balance Roll Option.....................:
Adjust From Year Total Allocated.............:
Print Option.................................:
Line Count...................................:
29610
0708
0809
LOAN
O
N
Y
55
Number of Fund Balances rolled...............: 13
Number of Fund Balances not rolled...........: 2
18-143
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Account Balance Report (RFRABAL)
The Account Balance Report prints detailed information on the status of each fund for a given aid year.
Description
Parameters
18-144
Name
Required?
Description
Values
Aid Year
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Fund Code
No
You can optionally enter fund codes. Only those
Fund Base Data form (RFRBASE)
fund codes that you enter will be printed. The system
accepts a single fund code or a multiple number of
fund codes for this report parameter.
Fund Source
No
You can optionally enter fund source codes. Only
Fund Source Code Validation form
those fund sources that you enter will be printed. The (RTVFSRC)
system accepts a single fund source code or a
multiple number of fund source codes for this report
parameter.
Fund Type
No
You can optionally enter fund type codes. Only those Financial Aid Fund Type Validation
fund types that you enter will be printed. The system form (RTVFTYP)
accepts a single fund type code or a multiple number
of fund type codes for this report parameter.
Federal Fund ID
No
You can optionally enter federal fund ID codes. Only Federal Fund ID Inquiry form
those federal fund IDs that you enter will be printed. (RFIFFID)
The system accepts a single federal fund ID code or
a multiple number of federal fund ID codes for this
report parameter.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
18-145
Required?
Description
Term Code
No
You can optionally enter term codes. Only those
Financial Aid Term Code Inquiry form
term codes that you enter will be printed. The system (ROITERM)
accepts a single term code or a multiple number of
term codes for this report parameter. The Account
Balance Report prints both annual and term data
when you enter a term code parameter.
Sorting Sequence
No
This parameter utilizes one of two available fund
code sorting options.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
A
Ascending (default)
D
Descending
January 2009
Account Balance Report Sample
29-MAY-2002 16:38:24
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
PAGE 1
Account Balance Report
RFRABAL
FUND CODE: INLN Institutional Loan
FUND SOURCE: INST Institutional
FED FUND ID: GTIV General Title IV Rules
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
FUND TYPE: LOAN Loan
NUMBER OF
AWARDS
23
19
19
0
0
0
0
19
AMOUNT OF
AWARDS
38600.00
33500.00
33500.00
.00
.00
.00
.00
16750.00
AMOUNT
REMAINING
NUMBER OF
AWARDS
20
20
20
0
0
0
0
19
AMOUNT OF
AWARDS
17500.00
17500.00
17500.00
.00
.00
.00
.00
16750.00
AMOUNT
REMAINING
NUMBER OF
AWARDS
20
20
20
0
0
0
0
0
AMOUNT OF
AWARDS
17500.00
17500.00
17500.00
.00
.00
.00
.00
.00
AMOUNT
REMAINING
PERCENT
REMAINING
989845267.00
.00
16750.00
100.00
.00
PRIOR BALANCE:
TRANSFERRED:
BUDGET ALLOCATED:
TOTAL ALLOCATED:
.00
.00
989878767.00
989878767.00
AVAILABLE TO OFFER:
PERCENT:
989878767.00
100.000
50.00
TERM CODE: 200310
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
PERCENT
REMAINING
.00
.00
750.00
4.29
TERM CODE: 200320
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
18-146
Banner Financial Aid 8.3
User Guide
Reports and Processes
PERCENT
REMAINING
.00
.00
17500.00
100.00
January 2009
29-MAY-2002 16:38:24
2
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
PAGE
Account Balance Report
RFRABAL
FUND CODE: MERIT Merit Scholarship
FUND SOURCE: INST Institutional
FED FUND ID:
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
FUND TYPE: GRNT Grant
NUMBER OF
AWARDS
208
25
14
0
0
2
0
0
AMOUNT OF
AWARDS
1593448.00
58950.00
13900.00
.00
.00
3788.00
.00
.00
AMOUNT
REMAINING
NUMBER OF
AWARDS
25
25
13
1
1
2
0
0
AMOUNT OF
AWARDS
29713.00
28925.00
5750.00
.00
.00
3788.00
.00
.00
AMOUNT
REMAINING
NUMBER OF
AWARDS
25
25
13
1
1
0
0
0
AMOUNT OF
AWARDS
29712.00
29425.00
5750.00
.00
.00
.00
.00
.00
AMOUNT
REMAINING
19941050.00
45050.00
13900.00
PERCENT
REMAINING
99.71
76.42
PRIOR BALANCE:
TRANSFERRED:
BUDGET ALLOCATED:
TOTAL ALLOCATED:
20000000.00
.00
.00
20000000.00
AVAILABLE TO OFFER:
PERCENT:
20000000.00
100.000
100.00
TERM CODE: 200310
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
PERCENT
REMAINING
23175.00
80.12
5750.00
100.00
TERM CODE: 200320
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
18-147
Banner Financial Aid 8.3
User Guide
Reports and Processes
PERCENT
REMAINING
23675.00
80.46
5750.00
100.00
January 2009
29-MAY-2002 16:38:24
3
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Account Balance Report
PAGE
RFRABAL
* * * REPORT CONTROL INFORMATION * * *
RPTNAME:
REPORT SEQUENCE NUMBER:
AID YEAR:
FUND CODE:
FUND SOURCE:
FUND TYPE:
FEDERAL FUND ID:
TERM CODE:
SORTING SEQUENCE:
LINE COUNT:
RFRABAL
789076
0203
INLN MERIT
200320 200310
A
55
RECORD COUNT: 2
18-148
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Fund Budget Report (RFRBUDG)
The Fund Budget Report provides fund budget allocation information for each fund account for a given aid year.
Description
Parameters
18-149
Name
Required?
Description
Values
Aid Year
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Fund Code
No
You can optionally enter fund codes. Only those
Fund Base Data form (RFRBASE)
fund codes that you enter will be printed. The system
accepts a single fund code or a multiple number of
fund codes for this report parameter.
Fund Source Code
No
You can optionally enter fund source codes. Only
Fund Source Code Validation form
those fund sources that you enter will be printed. The (RTVFSRC)
system accepts a single fund source code or a
multiple number of fund source codes for this report
parameter.
Fund Type Code
No
You can optionally enter fund type codes. Only those Financial Aid Fund Type Validation
fund types that you enter will be printed. The system form (RTVFTYP)
accepts a single fund type code or a multiple number
of fund type codes for this report parameter.
Federal Fund ID
No
You can optionally enter federal fund ID codes. Only Federal Fund ID Inquiry form
those federal fund IDs that you enter will be printed. (RFIFFID)
The system accepts a single federal fund ID code or
a multiple number of federal fund ID codes for this
report parameter.
Sorting Sequence
No
This parameter utilizes one of two available fund
code sorting options.
Banner Financial Aid 8.3
User Guide
Reports and Processes
A
Ascending (default)
D
Descending
January 2009
Fund Budget Report Sample
29-MAY-2002 17:07:10
PAGE 1
AID YEAR: 0203 Award Year 2002-2003
FUND
CODE
AL2
ALOAN
ALOAN3
ALTLN
ALTLNE
BXS1
BXS3
BXST
DEBALT
DIREC1
DIRECT
DLPLUS
DLUNSB
HALS
HALS3
HALS4
ICL
INLN
JAN1
NURSLN
PERK
PLUS
PLUS2
SLS
STFD
STFDX
STFDY
SUEALT
SUEPL
SUESB2
SUESL1
SUESL2
SUESL3
SUESL4
SUESL5
SUESL6
SUESL7
SUESL8
SUESL9
SUESUB
SUEUNS
TZLOAN
UNSTFD
WXT1
SunGard Higher Education Development
Fund Budget Report
TOTAL
ALLOCATION
AVAILABLE
TO OFFER
ORIGINAL
OFFERED
CURRENT
OFFERED
ACCEPTED
CANCELLED/
DECLINED
PAID
REMAINING
ALLOCATION
0.00
999,999.00
0.00
999,999,999.99
999,999.00
999,999,999.00
999,999,999.00
999,999,999.00
15,000,000.00
0.00
10,000,000.00
999,999,999.00
99,999,999.00
0.00
0.00
0.00
0.00
989,878,767.00
999,999,999.00
0.00
994,999.00
9,999,999.00
999,999,999.99
0.00
10,000,000.00
10,000,000.00
10,000,000.00
5,000,000.00
9,000,000.00
0.00
5,000,000.00
500,000.00
600,000.00
6,000,000.00
60,000.00
6,000,000.00
6,000,000.00
6,500,000.00
500,000.00
6,000,000.00
6,000,000.00
0.00
10,000,000.00
0.00
0.00
999,999.00
0.00
999,999,999.99
999,999.00
999,999,999.00
999,999,999.00
999,999,999.00
22,500,000.00
0.00
10,000,000.00
999,999,999.00
99,999,999.00
0.00
0.00
0.00
0.00
989,878,767.00
999,999,999.00
0.00
1,044,748.95
9,999,999.00
999,999,999.99
0.00
10,000,000.00
10,000,000.00
10,000,000.00
6,000,000.00
9,000,000.00
0.00
5,000,000.00
500,000.00
600,000.00
6,000,000.00
300,000.00
6,000,000.00
15,000,000.00
3,250,000.00
1,500,000.00
6,000,000.00
6,000,000.00
0.00
10,000,000.00
0.00
0.00
0.00
0.00
5,800.00
1,000.00
0.00
0.00
0.00
11,750.00
0.00
52,725.00
33,695.00
17,011.00
0.00
0.00
0.00
0.00
38,600.00
0.00
0.00
2,000.00
1,091,475.00
13,250.00
0.00
105,706.00
26,275.00
19,000.00
56,739.00
48,166.00
0.00
0.00
0.00
600.00
0.00
600.00
0.00
0.00
0.00
400.00
56,576.00
60,895.00
0.00
389,652.00
0.00
0.00
0.00
0.00
4,825.00
0.00
0.00
0.00
0.00
12,500.00
0.00
45,400.00
16,137.00
13,011.00
0.00
0.00
0.00
0.00
33,500.00
0.00
0.00
1,000.00
67,225.00
12,250.00
0.00
11,336.00
15,025.00
12,800.00
42,600.00
50,466.00
0.00
0.00
0.00
600.00
0.00
600.00
0.00
0.00
0.00
400.00
62,071.00
61,695.00
0.00
21,624.00
0.00
0.00
0.00
0.00
4,825.00
0.00
0.00
0.00
0.00
12,500.00
0.00
45,400.00
16,137.00
13,011.00
0.00
0.00
0.00
0.00
33,500.00
0.00
0.00
1,000.00
3,500.00
12,250.00
0.00
0.00
14,925.00
12,800.00
42,600.00
50,466.00
0.00
0.00
0.00
600.00
0.00
600.00
0.00
0.00
0.00
400.00
62,071.00
61,695.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
6,125.11
5,333.00
1,500.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
10,000.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
9,479.00
407.00
3,452.00
0.00
0.00
0.00
0.00
16,750.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
0.00
1,086.00
0.00
0.00
0.00
0.00
999,999.00
0.00
999,995,174.99
999,999.00
999,999,999.00
999,999,999.00
999,999,999.00
22,487,500.00
0.00
9,948,474.89
999,978,529.00
99,985,488.00
0.00
0.00
0.00
0.00
989,845,267.00
999,999,999.00
0.00
1,043,748.95
9,932,774.00
999,987,749.99
0.00
9,988,664.00
9,984,975.00
9,987,200.00
5,947,400.00
8,949,534.00
0.00
5,000,000.00
500,000.00
599,400.00
6,000,000.00
299,400.00
6,000,000.00
15,000,000.00
3,250,000.00
1,499,600.00
5,937,929.00
5,938,305.00
0.00
9,978,376.00
0.00
TOT:
8,240,573,506.93
8,225,033,756.98
18-150
RFRBUDG
Banner Financial Aid 8.3
User Guide
Reports and Processes
485,065.00
2,031,915.00
22,958.11
388,280.00
8,240,065,483.82
31,174.00
January 2009
* * * REPORT CONTROL INFORMATION * * *
RPTNAME:
REPORT SEQUENCE NUMBER:
AID YEAR:
FUND CODE:
FUND SOURCE:
FUND TYPE:
FEDERAL FUND ID:
SORTING SEQUENCE:
LINE COUNT:
RFRBUDG
789086
0203
LOAN
A
55
RECORD COUNT: 44
18-151
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Fund Description Report (RFRFUND)
The Fund Description Report provides detailed descriptive information on the fund, system rules, and budget
allocation assigned each fund account for a given aid year.
Description
Parameters
18-152
Name
Required?
Description
Values
Aid Year
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Fund Code
No
You can optionally enter fund source codes. Only
Fund Base Data form (RFRBASE)
those fund sources that you enter will be printed. The
system accepts a single fund source code or a
multiple number of fund source codes for this report
parameter.
Fund Source
No
You can optionally enter fund source codes. Only
Fund Source Code Validation form
those fund sources that you enter will be printed. The (RTVFSRC)
system accepts a single fund source code or a
multiple number of fund source codes for this report
parameter.
Fund Type
No
You can optionally enter fund type codes. Only those Financial Aid Fund Type Validation
fund types that you enter will be printed. The system form (RTVFTYP)
accepts a single fund type code or a multiple number
of fund type codes for this report parameter.
Federal Fund ID
No
You can optionally enter federal fund ID codes. Only Federal Fund ID Inquiry form
those federal fund IDs that you enter will be printed. (RFIFFID)
The system accepts a single federal fund ID code or
a multiple number of federal fund ID codes for this
report parameter.
Fund Code
Sorting Sequence
No
This parameter utilizes one of 2 available fund code
sorting options.
Banner Financial Aid 8.3
User Guide
Reports and Processes
A
Ascending (default)
D
Descending
January 2009
Fund Description Report Sample
17-APR-2007 11:18:14
AID YEAR: 0708 2008-2009 aid year
FUND CODE:
PELL
FUND SOURCE: FDRL
BANNER University
Fund Description Report
PAGE 1
RFRFUND
Federal Pell Grant
Federal
PRIOR BALANCE:
TRANSFERRED:
BUDGET ALLOCATED:
TOTAL ALLOCATED:
FUND TYPE:
10000000.00
.00
.00
10000000.00
GRNT Grant
AVAILABLE TO OFFER:
PERCENT:
FED FUND ID:
PELL
10000000.00
100.00
------------------------------------------------- PACKAGING OPTIONS -------------------------------------------------------AWARD MAX:
AWARD MIN:
AUTO PACKAGE:
AUTO SCHEDULE:
AUTO ACCEPT:
DISBURSE:
MEMO CREDIT:
OVERRIDE NEED:
OVERRIDE NEED COA:
4310.00
.00
Y
Y
Y
S
A
Y
OFFER AWARD STATUS: OFRD Offered
ACCEPT AWARD STATUS: ACPT Accepted
DECLINE AWARD STATUS: DECL Declined
REPLACE EFC:
REDUCE NEED:
EQUITY:
ROUND AWARD:
ROUND SCHEDULE:
OVERRIDE RQMT:
WEB ACCEPT:
NCAA:
ELIGIBLE TO ROLL:
N
Y
Y
001
RD
N
N
SELF-HELP REDUCTION %:
NEED ANALYSIS REQ'D: Y
AWARD CHANGE LETTER IND: Y
LMS LOAN FUND:
OVERRIDE SAPR:
ALT LOAN PROG:
ACG GRADE LEVEL:
SMART GRADE LEVEL:
AWARD USING EST EFC: Y
N
REBATE %:
INTEREST %:
LOAN FEE %:
LOAN PROCESS: N
DIRECT LOAN:
MANUAL LOAN:
ELECTRONIC LOAN:
------------------------------------------------- DISBURSEMENT OPTIONS ----------------------------------------------------IF DISB. LOAD > PCKG
PAYMENT % FOR 3/4
PAYMENT % FOR 1/2
PAYMENT % FOR LESS 1/2
CHANGE
LOAD: D
LOAD:
LOAD:
LOAD:
LOAD: A
IF INELIGIBLE BEFORE CUT-OFF DATE:
IF INELIGIBLE AFTER CUT-OFF DATE:
IF SELECTED VERIFICATION INCOMPLETE:
RECOUP: Y
OVERRIDE GENERAL REQ:
PROMISSORY NOTE REQ'D:
B
B
N
N
N
DISB ENRL EDITS FOR MEMO: Y
USE ATTENDING HOURS: Y
AID PERIOD : FA/SPR
AWARD SCHEDULE: (DEFAULT)
TERM CODE
AWARD PCT.
200810
50.000
200820
50.000
PELL AWARD PCT.
50.000
50.000
DISBURSEMENT SCHEDULE: (DEFAULT)
TERM CODE
DISBURSEMENT DATE
200810
01-SEP-2007
200820
01-JAN-2008
MEMO EXPIRATION
31-DEC-2007
31-MAY-2008
DISBURSEMENT PCT.
100.000
100.000
+/- DAYS
ACTIVITY DATE
12-FEB-2007
29-JAN-2007
ACTIVITY DATE
03-AUG-2006
03-AUG-2006
AID PERIOD : FALL
AWARD SCHEDULE: (DEFAULT)
TERM CODE
AWARD PCT.
200810
100.000
PELL AWARD PCT.
100.000
DISBURSEMENT SCHEDULE: (DEFAULT)
TERM CODE
DISBURSEMENT DATE
200810
01-NOV-2007
18-153
Banner Financial Aid 8.3
User Guide
Reports and Processes
MEMO EXPIRATION
01-DEC-2007
DISBURSEMENT PCT.
100.000
+/- DAYS
ACTIVITY DATE
18-DEC-2006
ACTIVITY DATE
18-DEC-2006
January 2009
17-APR-2007 11:18:14
AID YEAR: 0708 2008-2009 aid year
BANNER University
Fund Description Report
PAGE 7
RFRFUND
* * * REPORT CONTROL INFORMATION * * *
RPTNAME:
VERSION #:
REPORT SEQUENCE NUMBER:
AID YEAR:
FUND CODE:
FUND SOURCE:
FUND TYPE:
FEDERAL FUND ID:
SORTING SEQUENCE:
LINE COUNT:
18-154
RFRFUND
(7.8)
186348
0809
PELL
A
55
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Simulation Fund Balance Report (RFRSBAL)
The Simulation Fund Balance Report provides detailed fund balance information for use during packaging
simulation.
Description
Parameters
Name
Required?
Description
Values
•
Aid Year
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
•
Fund Code
No
You can optionally enter fund codes. Only those
fund codes that you enter will be printed. Banner
accepts a single fund code or a multiple number of
fund codes for this report parameter.
Fund Base Data form (RFRBASE)
•
Fund Source
No
You can optionally enter fund source codes. Only
Fund Source Code Validation form
those fund sources that you enter will be printed. The (RTVFSRC)
system accepts a single fund source code or a
multiple number of fund source codes for this report
parameter.
•
Fund Type
No
You can optionally enter fund type codes. Only those Financial Aid Fund Type Validation
fund types that you enter will be printed. The system form (RTVFTYP)
accepts a single fund type code or a multiple number
of fund type codes for this report parameter.
•
Federal Fund ID
No
You can optionally enter federal fund ID codes. Only Federal Fund ID Inquiry form
those federal fund IDs that you enter will be printed. (RFIFFID)
The system accepts a single federal fund ID code or
a multiple number of federal fund ID codes for this
report parameter.
•
Sorting Sequence
No
This parameter utilizes one of two available fund
code sorting options.
18-155
Banner Financial Aid 8.3
User Guide
Reports and Processes
A
Ascending (default)
D
Descending
January 2009
Simulation Fund Balance Report Sample
29-MAY-2002 17:01:22
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Simulation Fund Balance Report
PAGE 1
RFRSBAL
FUND CODE: INLN Institutional Loan
FUND SOURCE: INST Institutional
FED FUND ID: GTIV General Title IV Rules
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
NUMBER OF
AWARDS
23
19
19
0
0
0
0
19
AMOUNT OF
AWARDS
38600.00
33500.00
33500.00
0.00
0.00
0.00
0.00
16750.00
INSUFFICIENT:
0
0.00
29-MAY-2002 17:01:22
AID YEAR: 0203 Award Year 2002-2003
FUND TYPE: LOAN Loan
AMOUNT
REMAINING
989845267.00
0.00
16750.00
PERCENT
REMAINING
100.00
0.00
PRIOR BALANCE:
TRANSFERRED:
BUDGET ALLOCATED:
TOTAL ALLOCATED:
0.00
0.00
989878767.00
989878767.00
AVAILABLE TO OFFER:
PERCENT:
989878767.00
100.000
50.00
SunGard Higher Education Development
Simulation Fund Balance Report
PAGE 2
RFRSBAL
FUND CODE: MERIT Merit Scholarship
FUND SOURCE: INST Institutional
FED FUND ID:
18-156
FUND TYPE: GRNT Grant
ORIGINAL OFFERS:
CURRENT OFFERED:
ACCEPTED:
DECLINED:
CANCELLED:
MEMO'D:
AUTHORIZED:
PAID:
NUMBER OF
AWARDS
208
25
14
0
0
2
0
0
AMOUNT OF
AWARDS
1593448.00
58950.00
13900.00
0.00
0.00
3788.00
0.00
0.00
INSUFFICIENT:
0
0.00
Banner Financial Aid 8.3
User Guide
Reports and Processes
AMOUNT
REMAINING
19941050.00
45050.00
13900.00
PERCENT
REMAINING
99.71
76.42
PRIOR BALANCE:
TRANSFERRED:
BUDGET ALLOCATED:
TOTAL ALLOCATED:
20000000.00
0.00
0.00
20000000.00
AVAILABLE TO OFFER:
PERCENT:
20000000.00
100.000
100.00
January 2009
29-MAY-2002 17:01:22
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Simulation Fund Balance Report
PAGE 3
RFRSBAL
* * * REPORT CONTROL INFORMATION * * *
RPTNAME:
REPORT SEQUENCE NUMBER:
AID YEAR:
FUND CODE:
FUND SOURCE:
FUND TYPE:
FEDERAL FUND ID:
SORTING SEQUENCE:
LINE COUNT:
RFRSBAL
789084
0203
INLN MERIT
55
RECORD COUNT: 2
18-157
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Applicant Comments Report (RHRCOMM)
The Applicant Comments Report prints comments about each applicant.
Description
Parameters
Name
Required?
Description
Values
Beginning Aid Year
Code
No
You can optionally restrict the Applicant Comments
Report to a range of aid years. The beginning aid
year code date determines the starting range of dates
in which the comments associated with an aid year
should fall.
Aid Year Inquiry form (ROIAIDY)
Ending Aid Year Code
No
You can optionally restrict the Applicant Comments
Report to a range of aid years. The ending aid year
code date determines the ending range of dates in
which the comments associated with an aid year
should fall.
Aid Year Inquiry form (ROIAIDY)
Beginning Date
No
You can optionally restrict the Applicant Comments
Report to a range of activity dates. The beginning
date determines the beginning range of activity dates
in which the comments should fall.
DD-MON-YYYY
Ending Date
No
You can optionally restrict the Applicant Comments
Report to a range of activity dates. The ending date
determines the ending range of activity dates in
which the comments should fall.
DD-MON-YYYY
Category Code
No
All records with a Category Code equal to this
parameter display on the report.
Comment Category Code Validation
(RTVCCOM)
Sort Order
Yes
Sorts report by the designated parameter value.
IAC Sort by ID, aid year, category
ICA Sort by ID, category, aid year
NACSort by name, aid year, category
(default)
NCASort by name, category, aid year
18-158
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
18-159
Required?
Description
Values
Applicant ID
No
Enter an ID to produce a single student report.
Person Search (SOAIDEN)
Page Break Indicator
No
Use this parameter to indicate whether or not you
want a page break for each student. The allowable
values are Y or N . This parameter defaults to N.
Y
Yes
N
No (default)
Application Code
No
General area for which the Selection ID was defined. Application Inquiry (GLIAPPL)
Selection Identifier
No
Code that identifies the sub-population to work with.
Creator ID
No
ID of the person creating the sub-population rules.
User ID
No
ID of the person who used the population rules.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Applicant Comments Report Sample
23-AUG-2007 09:54:39 AM
BANNER University
PAGE
1
Applicant Comments Report
RHRCOMM
-----------------------------------------------------------------------------------------------------------------------------------Kichline, Test D
ID: 999123456
COMMENTS
This is a test to show the sort option in the RHRCOMM output file of
Name, Category and Aid Year. The output file should sort by
student's name then sort by categories then by aid year.
CATEGORY
NP1
ORIG. DATE
21-AUG-2007
ACT. DATE
23-AUG-2007
AID YEAR
0708
USER ID
JDOE
NP2
23-AUG-2007
23-AUG-2007
0708
JDOE
CATEGORY
CJS1234
ORIG. DATE
23-AUG-2007
ACT. DATE
23-AUG-2007
AID YEAR
0708
USER ID
JDOE
Here is a category code listed for this student. This will show that
when we use the NCA sort option on RHRCOMM that this comment will
appear before a category code that is blank.
INSTEST
23-AUG-2007
23-AUG-2007
0607
JDOE
This is the comment that appears under the INSTEST category. Since
we used the NCA sort option for RHRCOMM, it should appear after the
CJS1234 comment.
INSTEST
23-AUG-2007
23-AUG-2007
0708
JDOE
23-AUG-2007
23-AUG-2007
0607
JDOE
This new RHACOMM functionality is really cool. We can type in up to
4000 characters now so people will not have to decipher our
abbreviated code. Wow, and words now wrap so they do not get broken
up. This trully is amazing.
We can also list comments by category so when we do reporting we
know how many students fall within a specific category. If we do
this properly, the categories will help us identify the most common
issues at hand so we can better counsel families and redo our
brochures and/or web site information so families will have answers
up front.
Lairddepend, Newcalcn
ID: 511007001
COMMENTS
Let's use two category codes now for 07-08. The first one will be
CJS1234 and the second will be INSTEST. Since we used the NCA sort
option on RHRCOMM, the CJS1234 comment should come before the
INSTEST comment.
There is no category code listed for this comment. It is just a
general comment for this student.
18-160
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
23-AUG-2007 09:54:39 AM
BANNER University
PAGE
2
Applicant Comments Report
RHRCOMM
-----------------------------------------------------------------------------------------------------------------------------------* * * REPORT CONTROL INFORMATION * * *
Program Name.................................: RHRCOMM
Version......................................: 7.9
Report Sequence Number.......................:
Beginning Aid Year Code......................:
Ending Aid Year Code.........................:
Beginning Date...............................:
Ending Date..................................:
Category Code................................:
Sort Order...................................:
Applicant Id.................................:
Page Break Indicator.........................:
207762
0607
0708
21-AUG-2007
Application Id...............................:
Selection Id.................................:
Creator Id...................................:
User Id......................................:
FINAID
MANUAL
JDOE
JDOE
NCA
N
Line Count...................................: 55
Number of students selected..................: 2
Number of comments...........................: 6
18-161
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Applicant Comments Purge Process (RHRPCOM)
The RHRPCOM Process enables you to purge applicant comments based on the information you enter for the
following parameters.
Description
For example, suppose you create a population selection and enter the following information for these parameters:
Beginning Aid Year Code
Ending Aid Year Code
Beginning Date
Ending Date
Category Code
0607
0708
01-JAN-2001
31-DEC-2006
Some defined category code
The process would purge records that:
• belong to the population selection,
• belong to the category code entered for the Category Code parameter,
• have an activity date greater than or equal to 01/01/2001,
• have an activity date less than or equal to 12/31/2006, and
• are between aid year end years corresponding to the 0607 and 0708 aid year codes.
Parameters
18-162
Name
Required?
Description
Beginning Aid Year
Code
No
All records with an aid year start year
Aid Year Inquiry form (ROIAIDY)
(ROBINST_AIDY_START_YEAR) greater than or equal
to this aid year (derived from the aid year code) are
deleted. If you enter a Beginning Aid Year Code, you
must also enter an Ending Aid Year Code.
Ending Aid Year Code
No
All records with an aid year end year
(ROBINST_AIDY_END_YEAR) less than or equal to this
aid year (derived from the aid year code) are deleted
If you enter an Ending Aid Year Code, you must also
enter a Beginning Aid Year Code.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
Aid Year Inquiry form (ROIAIDY)
January 2009
Parameters (cont) Name
Required?
Description
Values
Beginning Date
No
All records with an activity date greater than or equal DD-MON-YYYY
to this date are deleted. If you enter a Beginning
Date, you must also enter an Ending Date.
Ending Date
No
All records with an activity date less than or equal to
this date are deleted. If you enter an Ending Date,
you must also enter a Beginning Date.
DD-MON-YYYY
Category Code
No
All records with a Category Code equal to this
parameter are deleted.
Comment Category Code Validation
(RTVCCOM)
Sort Order
Yes
Sorts report by the designated parameter value.
IAC Sort by ID, aid year, category
ICA Sort by ID, category, aid year
NACSort by name, aid year, category
(default)
NCASort by name, category, aid year
Print Comments
18-163
Yes
Determines whether you want to print the
Comments field on the report.
Y
Yes
N
No (Default)
Application Code
No
General area for which the Selection ID was defined. Application Inquiry (GLIAPPL)
Selection Identifier
No
Code that identifies the sub-population to work with.
Creator ID
No
ID of the person creating the sub-population rules.
User ID
No
ID of the person who used the population rules.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Applicant Comments Purge Report
23-AUG-2007 10:32:17 AM
BANNER University
PAGE
1
Applicant Comments Purge Report
RHRPCOM
-----------------------------------------------------------------------------------------------------------------------------------ID: 511007002
Name: Laird-Depend, New7002
Aid Year: 0708
Category: T E S T
Original Date: 23-AUG-2007
Activity Date: 23-AUG-2007
User ID: JDOE
Comments: Just testing to make sure only the T E S T category codes are deleted for these students.
ID: 999878787
Name: Hammer, Duck
Aid Year: 0708
Category: T E S T
Original Date: 23-AUG-2007
Activity Date: 23-AUG-2007
User ID: JDOE
Comments: This is a test to use the new comment purge process. The user running the program can delete another user's
comments. So, the RHRPCOM process should be used with caution. We think we are going to limit who has the
capabilities of running the process in our office.
This new process will really help us clean up our database. We would like to get rid of comments that are more than
5 years old.
23-AUG-2007 10:32:17 AM
BANNER University
PAGE
2
Applicant Comments Purge Report
RHRPCOM
-----------------------------------------------------------------------------------------------------------------------------------* * * REPORT CONTROL INFORMATION * * *
Program Name.................................: RHRPCOM
Version......................................: 7.9
Report Sequence Number.......................:
Beginning Aid Year Code......................:
Ending Aid Year Code.........................:
Beginning Date...............................:
Ending Date..................................:
Category Code................................:
Sort Order...................................:
Print Comments...............................:
207788
0607
0708
Application Id...............................:
Selection Id.................................:
Creator Id...................................:
User Id......................................:
FINAID
MANUAL
JDOE
JDOE
T E S T
ICA
Y
Line Count...................................: 55
Number of students selected..................: 2
Number of comments purged....................: 2
18-164
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Authorization Report (RJRAUTH)
The Authorization Report displays a listing of current work authorizations based on activity date.
Description
Parameters
18-165
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Selection Query ID
No
Selection Query ID of the population selection. If
you enter a value for this parameter, you must also
enter a value for the Application Status Code and
Creator ID of Selection ID parameters.
Population Selection Inquiry form
(GLISLCT)
Selection Application
Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Creator ID of Selection ID
parameters.
Application Inquiry form
(GLIAPPL)
Creator ID
of Selection ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection Query ID and Selection Application Code
parameters.
User Identification Control form
(GUAIDEN)
Selection Date
Yes
Enter a selection date for this parameter. The
selection date does not have to fall within the aid
year's start date and end date. The report will only
show authorizations where the activity date on the
authorization is greater than the parameter specified
selection date. Through the use of the selection date,
you can run the report to only include authorizations
made or changed since the last time the report was
run.
DD-MMM-YYYY
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Required?
Description
Values
Authorization
Status Code
No
You can optionally restrict the Student Employment Employment Authorization Status
Authorization Report to only include those
Validation form (RTVAUST)
authorization status codes that you enter for this
parameter. The system accepts a single authorization
status code or a multiple number of authorization
status codes.
Sort Option
No
This parameter utilizes one of two available sorting
options.
1
Student Name, ID (default)
2
Authorization Status, Name, ID
Authorization Report Sample
26-MAY-2001
11:45
AM
AID YEAR: 0001
NAME
ID
EMPLOYEE
PAY PERIOD
CLASS
START
END
Arnold, James B.
911111115
08 01-JUL-2000 30-JUN-2001
Davis, William A.
911111111
18 01-JUL-2000 30-JUN-2001
Gardner, Jessica
911111116
18 01-JUL-2000 30-JUN-2001
Hendley, Jason R.
911111113
18 01-JUL-2000 30-JUN-2001
Jacob, O’ Brien
911111117
18 01-JUL-2000 30-JUN-2001
Mulder, Fox
999555111
18 01-JUL-2000 30-JUN-2001
Quick, Andrea
911111118
18 01-JUL-2000 30-JUN-2001
Scully, Dana
111555999
18 01-JUL-2000 30-JUN-2001
Trammel, Julie A.
911111112
08 01-JUL-2000 30-JUN-2001
Wiley, Sandra
911111114
18 01-JUL-2000 30-JUN-2001
18-166
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
PAGE
Student Employment Authorization Report
1
RJRAUTH
SS#
POSITION
911111115
000017 00
911111111
C10001 00
911111116
777777 00
911111113
777777 00
911111117
S00001 00
999555111
C10001 00
911111118
777777 00
111555999
C10001 00
911111112
000017 00
911111114
C10001 00
HOURLY
RATE
AUTHORIZED
COA
HOURS
AMOUNT CODE
ORGN
CODE
STATUS
4.75
947.00
4498.25
B
11005
AUTH Authorized to Work
4.75
947.00
4498.25
B
11
AUTH Authorized to Work
4.75
947.00
4498.25
B
11206
AUTH Authorized to Work
4.75
947.00
4498.25
B
11206
AUTH Authorized to Work
4.75
947.00
4498.25
B
11
AUTH Authorized to Work
4.75
525.00
2493.75
B
11
TEMP Temporary work assignment
4.75
947.00
4498.25
B
11206
AUTH Authorized to Work
4.75
525.00
2493.75
B
11
TEMP Temporary work assignment
4.75
945.00
4488.75
B
11005
AUTH Authorized to Work
4.75
947.00
4498.25
B
11
AUTH Authorized to Work
January 2009
26-MAY-2001
11:45
AM
AID YEAR: 0001
SunGard Higher Education Development
Student Employment Authorization Report
PAGE
2
RJRAUTH
* * * REPORT CONTROL INFORMATION * * *
RPTNAME ...............................
REPORT SEQUENCE NUMBER ................
SELECTION IDENTIFIER ..................
APPLICATION CODE ......................
CREATOR ID ............................
AID YEAR ..............................
SELECTION DATE ........................
AUTHORIZATION STATUS CODE .............
SORT OPTION ...........................
LINE COUNT ............................
RECORD COUNT - Students ...
18-167
Banner Financial Aid 8.3
User Guide
Reports and Processes
RJRAUTH
175365
0001
01-SEP-2000
STUDENT NAME, STUDENT ID
55
10
January 2009
Pay Period Report (RJRDPPR)
The Pay Period Report displays information for the monitoring of student earnings and /or the production of a
departmental time-sheet.
Description
Parameters
18-168
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application Code and Creator ID
parameters.
Population Selection Inquiry form
(GLISLCT)
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Application Code and Creator ID of
Selection ID parameters.
Application Inquiry form (GLIAPPL)
Creator ID
of Selection ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID and Application Code parameters.
User Identification Control form
(GUAIDEN)
Time Sheet Option
Yes
Enter a value to specify the format of the output
T
Print as Time Sheet
R
Print as Report
Pay Period End Date
No
You can optionally enter a pay period end date if you
elect to use the time sheet option. This date displays
on each page of the report.
DD-MMM-YYYY
Placement Code
No
You can optionally restrict the Employment
Departmental Pay Period Report to only include the
placement code that you enter for this parameter.
Placement Rules form (RJRPLRL)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Pay Period Report Sample
26-MAY-2001 12:37 PM
AID YEAR: 0001
SunGard Higher Education Development
Student Employment Departmental Pay Period Report - Report Option
PAGE
RJRDPPR
1
Reginald Reynolds
215 Orchard Way
Johnson Building
Malvern, AK
19355
PHONE: (610) 234-9865
Placement: FINAID Financial Aid Office
Position: C10001 Clerk I
Allocation: 50000.00
ID
--------999555111
911111111
111555999
911111114
COA:
Organization:
NAME
--------------------------Blake, John
Davis, William A.
Santoro, Bert
Wiley, Sandra
AUTHORIZED
SUFFIX HOURS
AMOUNT
------ ------- -----------00
525.00
2493.75
00
947.00
4498.25
00
525.00
2493.75
00
947.00
4498.25
Position: S00001 Federal Work Study (Pooled)
Allocation: 10000.00
ID
--------911111117
NAME
--------------------------Jacob, O’ Brien
26-MAY-2001 12:37 PM
AID YEAR: 0001
Fred Smith
23 Poplar St.
Holloway Hall
Salisbury, MD
COA:
Organization:
AUTHORIZED
SUFFIX HOURS
AMOUNT
------ ------- -----------00
947.00
4498.25
B SunGard Higher Education University
122 General Administrative Service
REMAINING ELIGIBILITY
HOURS
AMOUNT
PCT
------- ------------ -------525.00
2493.75
100.00
947.00
4498.25
100.00
525.00
2493.75
100.00
947.00
4498.25
100.00
LAST PAY
DATE
-----------
STATUS
----------NO EARNINGS
NO EARNINGS
NO EARNINGS
NO EARNINGS
B SunGard Higher Education University
122 General Administrative Service
REMAINING ELIGIBILITY
HOURS
AMOUNT
PCT
------- ------------ -------947.00
4498.25
100.00
LAST PAY
DATE
-----------
SunGard Higher Education Development
Student Employment Departmental Pay Period Report - Report Option
STATUS
----------NO EARNINGS
PAGE
RJRDPPR
2
Suite 473
Placement: HIST History Department
Position: 000017
Allocation: 25000.00
ID
--------911111115
911111112
18-169
NAME
--------------------------Arnold, James B.
Trammel, Julie A.
Banner Financial Aid 8.3
User Guide
Reports and Processes
COA:
Organization:
AUTHORIZED
SUFFIX HOURS
AMOUNT
------ ------- -----------00
947.00
4498.25
00
945.00
4488.75
B SunGard Higher Education University
11005
REMAINING ELIGIBILITY
HOURS
AMOUNT
PCT
------- ------------ -------947.00
4498.25
100.00
945.00
4488.75
100.00
LAST PAY
DATE
-----------
STATUS
----------NO EARNINGS
NO EARNINGS
January 2009
26-MAY-2001 12:37 PM
AID YEAR: 0001
SunGard Higher Education Development
Student Employment Departmental Pay Period Report - Report Option
PAGE
RJRDPPR
4
* * * REPORT CONTROL INFORMATION * * *
RPTNAME ...............................
REPORT SEQUENCE NUMBER ................
SELECTION IDENTIFIER ..................
APPLICATION CODE ......................
CREATOR ID ............................
AID YEAR ..............................
TIME SHEET OPTION .....................
PAY PERIOD END DATE ...................
PLACEMENT CODE ........................
LINE COUNT ............................
RECORD COUNT ..........................
18-170
Banner Financial Aid 8.3
User Guide
Reports and Processes
RJRDPPR
175380
0001
R
55
10
January 2009
Payroll Load Process (RJRLOAD)
The Payroll Load Process serves as an interface between Banner Human Resources and Financial Aid. It updates
the student employment information within the Financial Aid System with actual payroll earnings. This process
also produces the Payroll Load Result Report (RJRLOAD) which lists the payroll information for each student that
was entered into the Student Employment Module as a result of this process. The Payroll Load process:
Description
• automatically updates the Financial Aid work history records with actual earnings on the Student
Employment Work History form (RJISEWH),
• automatically updates the fund balances with actual earnings on the Fund Budget Inquiry form
(RFIBUDG), and
• automatically updates the award paid amounts and the term paid amounts on the student award record as
represented on the Award form (RPAAWRD) and Package Maintenance form (RPAAPMT).
Parameters
18-171
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Payroll ID
Required?
Description
Values
Yes
Banner accepts a single Payroll ID or a multiple
Payroll Load Control form (RJRPAYL)
number of Payroll IDs for this process parameter.
The Payroll Load Control form (RJRPAYL) lists the
valid values for this parameter. The Payroll
Disposition indicator on the RJRPAYL form
displays a C (Complete) if the Banner Human
Resources System indicates that the payroll year,
payroll ID, and payroll number combination are
equal to a disposition code of 50 (Complete) meaning that all requirements have been satisfied for
the issue of the check. You can only enter a Payroll
ID with a Complete status as a valid parameter.
Payroll ID (format: YYYY_II_NNN)
YYYY
Year
Sort Option
No
=
Payroll
You can sort the report data with one of two options. 1
2
18-172
Banner Financial Aid 8.3
User Guide
Reports and Processes
Pay Yr, Pay ID, Pay #, Name
(default)
Name, ID, Place Cd, End Pay Dt
January 2009
Payroll Load Process Sample
AID YEAR: 0001
PAYROLL YEAR: 2001
Payroll Load Result Report
ID: CW
RJRLOAD
NO: 23
ID
NAME
PLACE
BEGINNING
CODE
POSITION
PAY DATE
900000004 Atkinson, Susan M.
NEWOFF CWS001 14 01-SEP-00
ENDING
PAY DATE
FUND
HOURS
RATE
AMOUNT
31-JUL-01
CWS
15.00
6.00
90.00
222000005 Evans, Frank
NEWOFF CWS001 15
01-SEP-00
31-JUL-01
CWS
25.00
6.00
150.00
601000022 Geller, Becky A.
NEWOFF CWS001 16
01-SEP-00
31-JUL-01
CWS
35.00
6.00
210.00
601000015 Gibson, Patricia L.
NEWOFF CWS001 18 01-SEP-00
31-JUL-01
CWS
37.00
601000010 Johnson, Judy J.
NEWOFF CWS001 17
31-JUL-01
CWS
40.00
01-SEP-00
AID YEAR: 0001
Payroll Load Result Report
RJRLOAD
* * * REPORT CONTROL INFORMATION * * *
RPTNAME ...............................
REPORT SEQUENCE NUMBER ................
AID YEAR ..............................
PAYROLL YEAR/ID/NO ....................
SORT OPTION ...........................
LINE COUNT ............................
RECORD COUNT Payrolls ...
18-173
RJRLOAD
56874
0001
2000/CW/23
PAYROLL YEAR/ID/NUMBER, STUDENT NAME/ID, POSITION/SUFFIX
55
1
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Payroll Exception Report (RJRPAYE)
The Payroll Exception Report lists those work study employees who have been paid, but not authorized, within the
Financial Aid Student Employment module.
Description
Parameters
18-174
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application Code and Creator ID of
Selection ID parameters.
Population Selection Inquiry form
(GLISLCT)
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection ID and Creator ID of
Selection parameters.
Application Inquiry form (GLIAPPL)
Creator ID
of Selection ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID and Application Code parameters.
User Identification Control form
(GUAIDEN)
Employee Class
Yes
Enter the employee class codes that reference
college work study programs. The system accepts a
single employee class code or a multiple number of
employee class codes.
Employee Class Query form
(PTQECLS)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Payroll ID
Required?
Description
Values
Yes
The system accepts a single Payroll ID or a multiple Payroll Load Rules Table (RJRPAYL)
number of Payroll IDs for this process parameter.
The Payroll Load Control form (RJRPAYL) lists the
valid values for this parameter. The Payroll
Disposition indicator on the RJRPAYL form
displays a C (Complete) if the Banner Human
Resources System indicates that the payroll year,
payroll ID, and payroll number combination are
equal to a disposition code of 50 (Complete) meaning that all requirements have been satisfied for
the issue of the check. You can only enter a Payroll
ID with a Complete status as a valid parameter.
Payroll ID (format: YYYY_II_NNN)
YYYY
Sort Option
No
= Payroll Year
You can sort the report data with one of two options. 1
2
Name, ID, Employee Class
(default)
Emp. Class, Pay Yr. Pay ID, Pay
Payroll Exception Report Sample
01/12/01 09:41 AM
AID YEAR: 0001
ID
NAME
900000004 Atkinson, Susan M.
222000005 Evans, Frank
601000022 Geller, Becky A.
601000015 Gibson, Patricia L.
601000010 Johnson, Judy J.
602000008 Welker, George
18-175
Banner Financial Aid 8.3
User Guide
Reports and Processes
Banner University
Payroll Exception Report
EMP
CLASS
WS
WS
WS
WS
WS
WS
POSITION
CWS001 00
CWS001 00
CWS001 00
CWS001 00
CWS001 00
CWS001 00
HOURS
35.00
15.00
18.00
20.00
20.00
30.00
RATE
6.00
6.00
6.50
6.50
7.00
6.00
PAGE
1
RJRPAYE
AMOUNT
210.00
90.00
117.00
130.00
140.00
180.00
PAYROLL
YEAR ID NO
1992 CW 21
1992 CW 21
1992 CW 21
1992 CW 21
1992 CW 21
1992 CW 21
BEGINNING
PAY DATE
16-OCT-92
16-OCT-92
16-OCT-92
16-OCT-92
16-OCT-92
16-OCT-92
ENDING
PAY DATE
31-OCT-92
31-OCT-92
31-OCT-92
31-OCT-92
31-OCT-92
31-OCT-92
January 2009
01/12/01 09:41 AM
AID YEAR: 0001
Banner University
Payroll Exception Report
PAGE
2
RJRPAYE
* * * REPORT CONTROL INFORMATION * * *
RPTNAME .............................
REPORT SEQUENCE NUMBER...............
SELECTION IDENTIFIER ................
APPLICATION CODE ....................
CREATOR ID ..........................
AID YEAR ............................
EMPLOYEE CLASS CODE .................
PAYROLL ID ..........................
SORT OPTION .........................
LINE COUNT...........................
RECORD COUNT - Payrolls ...
18-176
Banner Financial Aid 8.3
User Guide
Reports and Processes
RJRPAYE
56814
0001
WS
2001/CW/21
55
6
January 2009
Earnings Control Report (RJRSEEC)
The Earnings Control Report provides a listing of hours worked by pay period.
Description
Parameters
18-177
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application Code and Creator ID of
Selection ID parameters.
Population Selection Inquiry form
(GLISLCT)
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection ID and Creator ID of
Selection ID parameters.
Application Inquiry form (GLIAPPL)
Creator ID
of Selection ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID and Application Code parameters.
User Identification Control form
(GUAIDEN)
Starting Pay
Period Date
No
You can optionally restrict the Student Employment
Earnings Control Report to a range of pay period
dates. Only wages paid on or after this date will be
printed.
DD-MMM-YYYY
Ending Pay
Period Date
No
You can optionally restrict the Student Employment
Earnings Control Report to a range of pay period
dates. Only wages paid on or before this date will be
printed.
DD-MMM-YYYY
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
18-178
Required?
Description
Values
Fund Code
No
You can optionally enter fund codes. Only the
earnings associated with these fund codes will be
printed. The system accepts a single fund code or a
multiple number of fund codes for this report
parameter. This parameter is validated against the
Fund Base Data Table (RFRBASE).
Fund Base Data form (RFRBASE)
Sort Option
No
You can sort the report data with one of 2 options:
1
Name, Fund Cd, Place Cd, PP
Date (default)
2
Fund Cd, Name, Place Cd, PP
Date
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Earnings Control Report Sample
30-JUN-2001
02:07
PM
AID YEAR: 0001
NAME
FUND
PLACE
CODE
CODE
999555111 Blake, John
FWS
FINAID C10001 00
SunGard Higher Education Development
PAGE
Student Employment Earnings Control Report
RJRSEEC
ID
AUTHORIZED
HOURS
AMOUNT
525.00
PAY
DATE
2493.75 01-OCT-2000
15-DEC-2000
PAY
RATE
HOURS
WORKED
4.75
20.00
4.75
25.00
TOTAL
902109026 Caruso, Janet
FWS
FINAID C10001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
15.00
125.00
TOTAL
911111111 Davis, William A.
FWS
FINAID C10001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
23.00
75.00
TOTAL
902109025 Desmond, Michael
FWS
FINAID C10001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
20.00
56.00
TOTAL
902109024 Hunt, Natalie
FWS
FINAID C10001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
13.00
152.00
TOTAL
911111117 Jacob, O’ Brien
FWS
FINAID S00001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
25.00
27.00
TOTAL
18-179
Banner Financial Aid 8.3
User Guide
Reports and Processes
GROSS
PAY STATUS
95.00 TEMP Temporary work assignment
118.75
-----------213.75
============
213.75
71.25 AUTH Authorized to Work
593.75
-----------665.00
============
665.00
109.25 AUTH Authorized to Work
356.25
-----------465.50
============
465.50
95.00 AUTH Authorized to Work
266.00
-----------361.00
============
361.00
61.75 AUTH Authorized to Work
722.00
-----------783.75
============
783.75
118.75 AUTH Authorized to Work
128.25
-----------247.00
============
247.00
January 2009
1
30-JUN-2001
02:07
PM
AID YEAR: 0001
NAME
FUND
PLACE
CODE
CODE
902109027 Pennypacker, Melissa
FWS
FINAID C10001 00
SunGard Higher Education Development
PAGE
Student Employment Earnings Control Report
2
RJRSEEC
ID
AUTHORIZED
HOURS
AMOUNT
947.00
PAY
DATE
4498.25 01-OCT-2000
15-DEC-2000
PAY
RATE
4.75
4.75
HOURS
WORKED
19.00
85.00
TOTAL
111555999 Santoro, Bert
FWS
FINAID C10001 00
525.00
2493.75 01-OCT-2000
15-DEC-2000
4.75
4.75
16.00
195.00
TOTAL
902109023 Smith, Roger
FWS
FINAID C10001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
20.00
222.00
TOTAL
911111114 Wiley, Sandra
FWS
FINAID C10001 00
947.00
4498.25 01-OCT-2000
15-DEC-2000
4.75
4.75
13.00
157.00
TOTAL
18-180
Banner Financial Aid 8.3
User Guide
Reports and Processes
GROSS
PAY STATUS
90.25 AUTH Authorized to Work
403.75
-----------494.00
============
494.00
76.00 TEMP Temporary work assignment
926.25
-----------1002.25
============
1002.25
95.00 AUTH Authorized to Work
1054.50
-----------1149.50
============
1149.50
61.75 AUTH Authorized to Work
745.75
-----------807.50
============
807.50
January 2009
30-JUN-2001
02:07
PM
AID YEAR: 0001
SunGard Higher Education Development
Student Employment Earnings Control Report
PAGE
3
RJRSEEC
* * * REPORT CONTROL INFORMATION * * *
RPTNAME ...............................
REPORT SEQUENCE NUMBER ................
SELECTION IDENTIFIER ..................
APPLICATION CODE ......................
CREATOR ID ............................
AID YEAR ..............................
STARTING PAY PERIOD DATE ..............
ENDING PAY PERIOD DATE ................
FUND CODES ............................
SORT OPTION ...........................
LINE COUNT ............................
RECORD COUNT - Students ...........
18-181
Banner Financial Aid 8.3
User Guide
Reports and Processes
RJRSEEC
177755
0001
STUDENT NAME/ID, FUND CODE, PLACEMENT CODE, PAY PERIOD
55
10
January 2009
Award/Tracking Letter Indicator Reset Process (RLRLETR)
A tracking letter indicator and an award letter indicator exist on the RORSTAT Table. When a value of Y appears
in either of these fields, a significant change has occurred in the applicant’s tracking requirements or award
package that may require the generation of a new tracking letter or award letter. The tracking letter and award
letter can then be produced using these fields with population selection criteria.
Description
To create a population of students who should receive an award letter or tracking letter you should run the
GLBDATA process to find the students whose tracking letter indicator or award letter indicator is set to Y. When
you run the letter extract process (GLBLSEL) for your award letter or tracking letter, you should use the population
just created.
To reset the award letter or tracking letter indicator back to N you should run the RLRLETR process immediately
following the letter print process (GLRLETR). The parameters for the RLRLETR process call for the Application
Code, Selection ID, and Creator ID for the population of students you wish to reset. This must be the same as the
population you just used to print the award letters or tracking letters. This process resets the award and/or tracking
letter indicator back to N so the student will not be reselected for another award letter or tracking letter unless there
have been subsequent changes to the student's tracking requirements or award package.
Parameters
18-182
Name
Required?
Description
Selection ID
No
Code that identifies the sub-population to work with.
Application Code
No
General area for which the Selection ID was defined. Select valid values from the
Application Inquiry form (GLIAPPL).
Creator ID
No
The ID of the person creating the sub-population
rules.
Aid Year Code
Yes
A valid aid year code.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
Select valid values from the Aid Year
Inquiry form (ROIAIDY).
January 2009
Parameters
Name
Required?
Description
Values
Award or Tracking
Indicator
Yes
This parameter determines which letter indicators
you want to reset.
A
Award Letters
B
Both Award and Track. Letters
T
Tracking Letters
User ID
Yes
ID of the person using the sub-population rules.
Award/Tracking Letter Indicator Reset Process Sample
21-SEP-2005 12:07 PM
AID YEAR: 0506
BANNER University
Award/Tracking Letter Indicator Reset Process
PAGE
RLRLETR
1
* * * REPORT CONTROL INFORMATION * * *
RPTNAME ...............................
VERSION ...............................
REPORT SEQUENCE NUMBER ................
SELECTION IDENTIFIER ..................
APPLICATION CODE ......................
CREATOR ID ............................
AID YEAR ..............................
RESET (A)ward, (T)racking or (B)oth....
USER ID ...............................
LINE COUNT ............................
Award Letter Update Count ......
Tracking Letter Update Count ...
18-183
Banner Financial Aid 8.3
User Guide
Reports and Processes
RLRLETR
7.3
36580
JON
FINAID
JMILLER
0506
B
JMILLER
55
3
0
January 2009
Need Analysis Logging Report (RLRLOGG)
Banner Financial Aid allows changes to need analysis data to be stored in a special log table that can be used as an
audit trail of activity. The same method of logging is used for storing changes for processing. In order to
successfully log data changes for EDE, you must activate three levels of control switches.
Description
The first level is the institutional level. Pell correction logging must be activated by setting the switch to Y on the
Institution Financial Aid Options form (ROAINST) for the aid year. This indicator controls the default value for
the Pell Correction switch in the Key Block of the Need Analysis form (RNANAxx). This switch must also be set
to Y in order to log changes for Pell EDE. The third level is the individual field level. You must set the Pell
Correction indicator (Pell Ind) to Y on the Data Log Rules form (RORDATA) for the field that is being changed.
Under this method of logging need analysis or Pell corrections, the form stores the changes in temporary tables and
you must run another process to move the data from the temporary log tables to the permanent log tables
(ROBALOG).Once this process is completed, the changes can be viewed on either the Applicant Data Log form
(ROIALOG) or the Data Log Inquiry form (ROIILOG).
The date/time stamp on the audit log record is the date and time that the information was changed if it is data from
the RCRAPP1 or RORSTAT tables. It is the date/time that the RLBLOGG process was run if the changed data was
from the RCRAPP2 table.
You can use the Data Log Rules form (RORDATA) to turn logging on or off for any field in the RCRAPP1 table.
Logging of any RCRAPP1 field can be activated by setting the Audit Indicator on the RORDATA form to Y. It can
be deactivated by setting it to N. RCRAPP2 or RORSTAT fields, however, are not totally controlled by
RORDATA. If an RCRAPP2 or RORSTAT field was originally delivered with the Audit Indicator set to Y, then it
can be turned on or off. If it was originally delivered with the Audit Indicator set to N, then it cannot be logged
regardless of the Audit Indicator. (The RORDVAL table can be used to identify fields that were delivered as
logable.)
Parameters
18-184
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Need Analysis Calculation Process (RNEINxx)
Performs the need analysis process for a given aid year (where xx is the aid year).
Description
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
INAS Option
Yes
Long or short version.
L
Long (default)
S
Short
Process Indicator
Yes
When the Process Indicator value is B, INAS
B
performs the appropriate calculations for all students
R
in the Aid Year provided in Aid Year Code
parameter.
Batch - All Students for Aid Year
Recalc - In Waiting Status
When the Process Indicator value is R, INAS
performs the appropriate calculations for all students
who are designated as requiring a Need Analysis
recalculation.
Applicant Code
No
Applicant ID for the online process.
Person Search form (ROAIDEN)
Do not enter a value for this parameter when you run
this process in batch mode.
18-185
Selection ID
No
Name of Population Selection rule.
Creator ID
No
Person who wrote the Population Selection rule.
User ID
No
Person who executed Population Selection rule.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Need Analysis Calculation Process Sample
Date: 17-MAY-2002
TIME: 11:33
RESULTS OF THE INAS COMPARISON PROCESS
PGM: RNECP03
PAGE:
1
================================================================================
ID #: 181-03-0521
ADDRESS: 5802 BICENTENNIAL PLACE
NAME: MAGRONE, ANAND R
BEAUMONT, TX
-------------------------------------------------------------------------------7 DIFFERENCES FOUND
PROFILE
ISIR
DIFFERENCE
TOLERANCE
-------------------------------------------------------------------------------STUD: A G I
17,619
8,000
9,619- 54.59%
0
STUD: FEDERAL TAX
16
1,600
1,584 999.99%
0
STUD: FILER'S WAGES
381
20,000
19,619 999.99%
0
STUD: YEAR IN SCHOOL
0
1
7
n/a
n/a
n/a
PRNT: A G I
98,979
80,000
18,979- 19.17%
0
PRNT: FEDERAL TAX
17,057
15,000
2,057- 12.06%
0
PRNT: FATHER'S WAGES
77,768
70,000
7,7689.98%
0
================================================================================
Parameter (1)
= SMAGRONE
Parameter (2)
= XXXXXXXX
Parameter (3)
= 786741
Parameter (4)
= RNEIN03
Parameter (5)
=
Parameter (6)
=
Parameter (7)
=
Parameter (8)
=
Aid Year Code
= 0203
INAS Option
= L
All or Recalc
= O
ID
= 181030521
Application Code =
Selection ID
=
Creator ID
=
User ID
=
Extracting Table Data...
Long Need Analysis Calculation in Progress...
Updating IM Results...
Updating FM Results...
Successfully Completed INAS
Version 5.3.1
18-186
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Transfer Monitoring Application Creation Process(RNRTMAC)
Description
This process populates or updates the NSLDS Transfer Monitoring Application form (RNATMNT) with the same
functionality that currently exists for manually added records. That is, it creates or updates Transfer Monitoring
Inform Requests, Financial Aid History Requests, or both types of request records for each student found in the
Population Selection parameters that are included in the job.
Note
You must create your own Population Selection which will use Banner IDs to populate
RNATMNT during the process.
The Enrollment Begin Date, Remove From Monitoring?, and Use Class Start Date parameters
are only valid when you create Transfer Monitoring Inform Requests. You can only enter
values for these parameters when the Request Type parameter contains a value of T or B.
When you run the RNRTMAC process to set the remove indicator on TSM Inform Request
records (the Remove from Monitoring? parameter is Y), if the Request Type to Create
parameter is B to create both TSM and FAH records, only the TSM records will be updated for
„
the remove indicator. FAH records will not be updated or created.
Process Notes
1. Population Selection
• As with all Population Selection rules, you must enter all four of the population selection parameter values.
• The process does not default the User ID of the person who is running the process into the User ID
parameter. Rather, it verifies that the User ID entered into the parameter is associated with an existing
Population Selection.
• The process will fail to execute if any of the four parameters is not present.
2. Processing Remove Records from Transfer Monitoring
• For students with a single record, include the student in the Population Selection and select Y in Parameter
08 to remove from monitoring.
• For students with multiple records who have more than one school identified, include the student in the
Population Selection, indicate the appropriate School OPEID and Branch in Parameter 06, and select Y in
Parameter 08 to remove from monitoring. The process will then update only the related record for that
school to be removed.
18-187
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
• For students with multiple records who all have the same school identified but different Enrollment Begin
Dates exist, manually update the student record via the RNATMNT form to select the correct record to be
removed.
Parameters
18-188
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Application ID
Yes
General area for which the Selection ID was defined.
Selection ID
Yes
Code that identifies the population with which to
work.
Creator ID
Yes
ID of the person who created the population rules.
User ID
Yes
ID of the person who used the population rules.
School OPEID and
Branch
No
Enter a specific OPEID and OPEID Branch for the
Transfer Monitoring or Financial Aid History
request.The first six characters are the OPEID and
the last two characters are the OPEID Branch.
Enrollment Begin Date
No
Start Date for population if other than default date
(MM-DD-CCYY).
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Remove from
Monitoring?
Required?
Description
No
Enter Y to remove this population from the Transfer
Monitoring List. Additionally, if you attempt to
update the Remove Indicator for a student with one
of the following conditions, you will receive an error
message that indicates that the student could not be
removed from processing. The conditions which
will not allow removal are:
Values
Add/Request Batch ID is null
Remove Batch ID is not null
School code is invalid
No record is found for the update
You must review and/or update RNATMNT
manually for these records.
Print Report?
18-189
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
Print Report of Records Added?
Y
Yes
If Y is selected, the report includes both the records
that were added and any error messages. If N is
selected, the output is created and only the error
messages are included.
N
No
January 2009
Parameters (cont) Name
Use Class Start Date?
Request Type to Create?
Required?
Description
Values
No
Use earliest class start date for the enrollmwnt start
date?
Y
Yes
N
No
Determines whether you want to create Transfer
Monitoring Inform Requests, Financial Aid History
Requests, or both types of requests.
Valid values for this field are:
Yes
An FAH request is not created for a student if a prior
FAH request exists that has not yet had a FAH record
received (the FAH Received Date field on the
NSLDS Transfer Monitoring Application form
(RNATMNT) is blank).
T
Transfer Monitoring Inform
Request
H
Financial Aid History Request
B
Both TSM Inform Request and
FAH Request
Note: If the Remove from Monitoring? parameter is
Y and this parameter is B, only Transfer
Monitoring Inform Requests are updated with the
remove indicator. Financial Aid History records
are not created.
Transfer Monitoring Application Creation Process Sample
04-APR-2008 05:26:52 PM
BANNER University
1
Aid Year: 0809
Transfer Monitoring Application Creation Process
RNRTMAC
-----------------------------------------------------------------------------------------------------------------------------------Student ID SSN
Last Name
First Name
School Code Branch Begin Date
Type Error?
---------- --------- ----------------------------------- ------------ ----------- ------ ----------- ---- ------517009229
517009229 RUCKER
TEST9229
620044
55
02-SEP-2008 T
517009229
517009229 RUCKER
TEST9229
620044
55
H
517009230
517009230 RUCKER
TEST9230
620044
55
02-SEP-2008 T
517009230
517009230 RUCKER
TEST9230
620044
55
H
Total Records With Errors.................: 0
Total TSM Inform Records Created.........: 2
Total FAH Request Records Created.........: 2
18-190
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
04-APR-2008 05:26:52 PM
BANNER University
1
Aid Year: 0809
Transfer Monitoring Application Creation Process
RNRTMAC
-----------------------------------------------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name.................................:RNRTMAC(8.1)
One up Number................................:230103
PARAMETERS
Aid Year Code................................:0809
Application Code.............................:
Selection ID.................................:
Creator ID...................................:
User ID......................................:
School OPEID and Branch......................:
Enrollment Begin Date........................:
Remove From Monitoring?......................:
Use Earliest Class Start Date?...............:
18-191
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Transfer Monitoring Extract Process(RNRTMNE)
This extract process creates the School Inform/FAH Request file (which contains the names of the students who are
to be added to, or deleted from, the Transfer Monitoring list or for whom the school wants to request Financial Aid
History records). Data entered on the NSLDS Transfer Monitoring Application form (RNATMNT) is used by this
process to determine who should be included in the extract file.
Description
The TRNINFIN message class is extracted for both a TSM Inform Request and a FAH Request. Once received by
NSLDS, the school will receive a corresponding TRNINFOP error/acknowledgement file for each file sent.
The school will then receive either Alert files (TRALRTOP) for students added to the Transfer Monitoring list or
FAH files (FAHEXTOP) as requested.
Warning
A school must wait seven days before disbursing federal funds to students after informing
NSLDS about a mid-year transfer. To that end, Banner automatically places a seven-day hold
on disbursement for students being added to the Transfer Monitoring list. A Hold code
parameter is provided to allow you to specify a code for this purpose. The validation for the
Hold code parameter is RTVHOLD. When establishing a hold that will be used for the sevenday disbursement hold for Transfer Monitoring, the Disbursement Hold indicator for the Hold
code must be checked in order to prevent disbursement of aid. A disbursement hold is not set
„
for FAH Requests.
If a School Inform/FAH Request file is lost by the school or NSLDS, you may resend the entire batch of records by
selecting the Resend Batch parameter. This will create a duplicate of the file previously extracted with no new
records added.
Parameters
18-192
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
School OPEID and
Branch
No
Enter a specific OPEID and OPEID Branch for the
Transfer Monitoring or Financial Aid History
request.The first six characters are the OPEID and
the last two characters are the OPEID Branch.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
Hold Code
Required?
Description
Yes
This is the Hold code to be used for a seven-day
disbursement hold.
Values
Since FAH Requests do not set a Financial Aid Hold,
the Hold Code parameter is ignored for FAH
requests. The required seven-day disbursement hold
only applies when you extract Transfer Monitoring
Inform Requests.
Sort Order
18-193
Yes
This is the option to sort the report by Name or ID.
Application ID
No
This is the general area for which the selection ID
was defined.
Selection ID
No
This is the code that identifies the population with
which to work.
Creator ID
No
This is the ID of the person who created the
population rules.
User ID
No
This is the ID of the person who ran the GLBDATA
process to extract the students in the specified
population selection.
Banner Financial Aid 8.3
User Guide
Reports and Processes
N
Sort by Name
I
Sort by ID
Validated against the GLBAPPL table
January 2009
Parameters (cont) Name
Required?
Description
Resend TM Inform
File Batch ID
No
The Transfer Monitoring School Inform/FAH
Request File Batch ID to be resent. If a School
Inform/FAH Request file is lost by the school or
NSLDS, you may resend the entire batch of records.
This will create a duplicate of the file previously
extracted with no new records added.
Request Type to Extract
Yes
Determines whether you want to extract Transfer
Monitoring Inform Requests, Financial Aid History
Requests, or both types of requests.
Values
Valid values for this field are:
T
If you select B for this parameter, both TSM Inform
H
Requests and FAH Requests are extracted into the
file. However, if a student has both an FAH Request B
and a TSM Inform Request Record ready to extract
on the RNATMNT form, only one detail record is
extracted for the student with all the appropriate data
for both the FAH and TSM Inform Request. When
this occurs, both the FAH Request in RNATMNT
and the Inform Request record in RNATMNT are
updated to indicate that the request has been
extracted.
18-194
Banner Financial Aid 8.3
User Guide
Reports and Processes
Transfer Monitoring Inform
Requests
Financial Aid History Requests
Both TSM Inform Request and
FAH Requests
January 2009
Transfer Monitoring Inform/FAH Extract Report Sample
04-APR-2008 05:05:53 PM
BANNER University
1
Aid Year: 0809
Transfer Monitoring Inform/FAH Extract Report
RNRTMNE
-----------------------------------------------------------------------------------------------------------------------------------Student ID SSN
Last Name
First Name
School Code Branch Type Action
Enrl Begin
---------- --------- ----------------------------------- ------------ ----------- ------ ---- ------- ----------517009225
517009225 RUCKER
TEST9225
620004
00
H
517009226
517009226 RUCKER
TEST9226
620004
00
H
517009227
517009227 RUCKER
TEST9227
620004
00
T
Added
02-SEP-2008
517009228
517009228 RUCKER
TEST9228
620004
00
T
Added
02-SEP-2008
CONTROL SUMMARY
CONTROL SUMMARY
--------------Program Name.................................:
Job number...................................:
Aid Year Code................................:
School OPEID and Branch......................:
Hold Code....................................:
Sort Order...................................:
Application Code.............................:
Selection ID.................................:
Creator ID...................................:
User ID......................................:
Resend TSM File Batch ID.....................:
Request Type to Extract......................:
Number of Lines Per Page.....................:
Total Pages Printed..........................:
TSM
TSM
TSM
TSM
TSM
18-195
TSM EXTRACT
----------Records Read.............................:
Records Extracted........................:
Inform requests extracted................:
FAH requests extracted...................:
Records Rejected.........................:
Extract Batch ID.........................:
Extract file name........................:
Banner Financial Aid 8.3
User Guide
Reports and Processes
RNRTMNE(8.1)
230094
0809
62000400
10
N
B
55
1
4
4
2
2
0
2008040407
/export/home/jpoulin/jobsub/trninfin_230094.dat
January 2009
Transfer Monitoring Import Process(RNRTMNI)
The Transfer Monitoring Import Process imports and loads data into Banner from the three Transfer Monitoring
file types sent from NSLDS: the Error/Acknowledgement file (TRNINFOP), the Alert file (TRALRTOP), and the
Financial Aid History file (FAHEXTOP). RNRTMNI can also import concatenated files, though these
concatenated files must contain a single file type -- either all TRNINFOP, all TRALRTOP, or all FAHEXTOP files.
Description
During the import of a record, the RNRTMNI process determines if the record is a TSM Alert record, an FAH
record, or an Error/Acknowledgement record. Any file types other than the TRNINFOP, TRALRTOP, or
FAHEXTOP will generate an error message and will not be processed.
• An FAH record is identified by the words FAH HEADER contained in the header record
• A TSM Alert Record is identified by the words TSM ALERT HEADER in the header record
• An Error/Acknowledgement record is identified by the words TSM/FAH ERROR HEADER in the header
record.
When an FAH is received, you may, or may not, want to load the FAH as the current NSLDS record. Therefore, a
new parameter was added to the RNRTMNI process so that you can choose whether or not to load FAH records
received as the current NSLDS record. This is valid only for FAH records received and does not pertain to Alert
records. Alert records are always loaded as the current NSLDS record for the student.
When the FAH record is loaded into Banner, the record is loaded to the NSLDS tables with an INFC Code of FAH
so that it is clear that the data came from a Financial Aid History record. TRM will continue to be loaded as the
INFC Code for TSM Alert records. If a student has FAH requests for more than one aid year in the RNRTMNT
table, the FAH record will be imported to each aid year for which there is an unsatisfied request.
Parameters
18-196
Name
Required?
Description
Acknowledgement or
Alert File
Yes
Enter the Acknowledgment or Alert filename with
the extension here.
Print Report
Option (Y/N)
Yes
This is the option to print a report: Yes or No.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
Y
Yes (default)
N
No
January 2009
Parameters (cont) Name
18-197
Required?
Description
NSLDS Output
Application ID
No
This is the general area for which the Selection ID
was defined.
NSLDS Ouput
Selection ID
No
Code that identifies the population with which to
work.
NSLDS Output
Creator ID
No
This is the ID of the person who created the
population rules.
NSLDS Output
User ID
No
This is the ID of the person who used the population
rules.
Load FAH Record as
Current Record?
Yes
Determines whether you want to load a Financial
Aid History record as the current record.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
Valid values for this parameter are:
Y
Load FAH Record as the Current
NSLDS Record
N
Load FAH Records as a NonCurrent NSLDS Record
January 2009
Transfer Monitoring Import Process Sample
27-DEC-2005 06:30:09 PM
BANNER University
1
Transfer Monitoring FAH Report
RNRTMNI
-------------------------------------------------------------------------------Batch ID: 2005122201
Student ID
SSN
Aid Year
Last Name
First Name
517003061
517003061
517003063
517003063
517003064
517003064
517003065
517003065
517003061
517003061
517003063
517003063
517003064
517003064
517003065
517003065
0607
0506
0607
0506
0607
0506
0607
0506
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
TEST3061
TEST3061
TEST3063
TEST3063
TEST3064
TEST3064
TEST3065
TEST3065
27-DEC-2005 08:13:02 PM
BANNER University
1
Transfer Monitoring Alert Report
RNRTMNI
-------------------------------------------------------------------------------Batch ID: 2005102801
Student ID
SSN
Aid Year
Last Name
First Name
517003071
517003072
517003072
517003073
517003074
517003074
517003075
517003075
517003071
517003072
517003072
517003073
517003074
517003074
517003075
517003075
0506
0607
0506
0607
0607
0506
0607
0506
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
RUCKER
TEST3071
TEST3072
TEST3072
TEST3073
TEST3074
TEST3074
TEST3075
TEST3075
18-198
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
22-DEC-2005 06:27:19 PM
BANNER University
1
Transfer Monitoring Inform Error/Ack. Report
RNRTMNI
-------------------------------------------------------------------------------Batch ID: 2005122206
Student ID
SSN
Aid Year: 0506
Last Name
School Code: 62000400
First Name
517003066
517003066 RUCKER
TEST3066
001 No Alert Profile established
002 No header record
003 Header record with invalid Header Title
004 School/Branch does not exist in NSLDS
005 Servicer and School/Branch association not found
517003067
517003067 RUCKER
TEST3067
006 Submittal Date is not a valid date
007 Submittal Sequence Number is not numeric
008 Duplicate Submittal Date and Submittal Seq. Number combination
009 SSN is not numeric
010 First Name is all spaces
517003068
517003068 RUCKER
011 Last Name is all
012 Date of Birth is
013 Enrollment Begin
014 Enrollment Begin
015 Enrollment Begin
517003069
517003069 RUCKER
TEST3069
016 Monitor Begin Date is invalid date
017 Delete From List Indicator is not Y or N
021 Trailer record count does not match number of detail records
019 No trailer record
020 Trailer record with invalid Trailer Title
517003070
517003070 RUCKER
021 Trailer record count
022 Trailer record count
023 Enroll Begin current
024 Monitor Begin Date <
18-199
Banner Financial Aid 8.3
User Guide
Reports and Processes
TEST3068
spaces
invalid date
Date is invalid date
Date < current date minus 90 days
Date > current date plus 18 months (548 days)
TEST3070
does not match number of detail records
not numeric
or future and Monitor Begin > Enroll Begin
current date minus 18 months (548 days)
January 2009
22-DEC-2005 06:27:19 PM
BANNER University
1
Transfer Monitoring File Import Report
RNRTMNI
-------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name.................................: RNRTMNI(7.4)
Job number...................................: 80258
File Name................................(01): trninfop.001
Print Report Option..........................: Y
NSLDS Output Application Code................:
NSLDS Output Selection ID....................:
NSLDS Output Creator ID......................:
NSLDS Output User ID.........................:
Load FAH Record as Current...................: Y
Number of Lines Per Page.....................: 60
Inform Batch ID.........................: 2005122206
Aid Year......................: 0506
School Code...................: 62000400
Total detail records sent.....: 25
Detail records accepted.......: 20
Detail records with errors....: 5
Detail records with warnings..: 0
Detail error count............: 5
Detail warning count..........: 0
18-200
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Verification Discrepancy Report (RNRVRFY)
Verification Discrepancy Report prints discrepancies between verification documents and application data. You
can optionally update the application record with verification data.
Description
You can update a student application with the batch Verification Discrepancy Report. When you run this report,
you can either: (1) report discrepancies and update the student's application; or (2) just report the discrepancies. If
you choose the former option, the report compares all fields and updates the application with the verified
information when the discrepancy is greater than the tolerance for the field. If the verification data is non-existent
(that is, null) for a field, application updates do not take place for the field.
Situations frequently arise in which a student reports more other untaxed income than you can verify. This can
happen if the student originally reports a non-taxable source that is not included on any verification document. Add
the additional untaxed income to one of the other untaxed income fields on the Need Analysis Document
Verification form (RNAVRxx) to prevent the RNRVRFY Report from reducing the amount of other untaxed
income reported by the student. Otherwise, the RNRVRFY Report reduces the total of other untaxed income
reported by the student if the difference is greater than the tolerance, regardless of whether the difference is positive
or negative.
Parameters
18-201
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Update
Application Record
No
This parameter determines whether or not the
Y
verification data should replace the application data.
N
If you enter Y, the report compares all fields and
updates the application with the verified information
when the discrepancy is greater than the tolerance
for the field. If the verification data is non-existent
(null) for a field, application updates do not take
place for the field.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Update application record
Do not update application record
January 2009
Parameters (cont) Name
Report Type
Report Sequence
18-202
Required?
Description
Values
No
This parameter determines whether you want to
include all students with verification data or just
those students with discrepancies.
A - All students with verification data
(default)
No
You can sort the report data with one of the indicated
sort options.
Child Support Tolerance
No
You can optionally enter a child support tolerance
that indicates a significant difference.
Social Security
Benefit Toler.
No
You can optionally enter a social security benefit
tolerance that indicates a significant difference.
Other Untaxable Income
Toler.
No
You can optionally enter an other untaxable income
tolerance that indicates a significant difference.
Adjusted Gross
Income Toler.
No
You can optionally enter an adjusted gross income
tolerance that indicates a significant difference.
US Income Tax Paid
Tolerance
No
You can optionally enter a U.S. income tax paid
tolerance that indicates a significant difference.
AFDC Tolerance
No
Tolerance level before the difference is considered
significant.
Earned Income
Credit Tolerance
No
Tolerance level before the difference is considered
significant.
Child Support
Paid Tolerance
No
Tolerance level before the difference is considered
significant.
Banner Financial Aid 8.3
User Guide
Reports and Processes
D - Discrepancies Only - A student
only displays on the report if at
least one discrepancy exists for
the student and only records for
those students are updated.
N
Name (default)
I
ID
January 2009
Parameters (cont) Name
18-203
Required?
Description
Earned Income
Credit Tolerance
No
Tolerance level before the difference is considered
significant.
Sum of Discrepancies
Tolerance
No
You can optionally enter a sum of discrepancies
tolerance that indicates a significant difference.
Application ID
No
Application code of the population selection. Select
valid values from the Application Inquiry form
(GLIAPPL). If you enter a value for this parameter,
you must also enter a value for the Selection ID,
Creator ID and User ID parameters.
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application ID, Creator ID, and User
ID parameters.
Creator ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Application ID, Selection ID and User ID
parameters.
User ID
No
ID of the person using the sub-population rules.. If
you enter a value for this parameter, you must also
enter a value for the Application ID, Selection ID,
and Creator ID parameters.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
Application Inquiry form (GLIAPPL)
January 2009
Verification Discrepancy Report Sample
31-MAY-2002 07:37 AM
1
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Verification Discrepancy Report
PAGE
RNRVRFY
NAME
ID NUMBER PAR/STUDENT
------------------------------------------------------------------------------------------ --------- ----------Magrone,Melanie N.
181030501 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------GROSS INCOME:
50000
75000
INCOME TAX PAID:
20000
7500
STUDENT INC FROM WORK:
50000
75000
WORKSHEET A TOTAL:
1008
0
WORKSHEET C TOTAL:
0
25000
------------------------------------------------------------------------------------------ --------- ----------Magrone,Brian A.
181030503 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------NO DISCREPANCIES FOR THIS STUDENT
------------------------------------------------------------------------------------------ --------- ----------Magrone,Peter N.
181030522 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------NO DISCREPANCIES FOR THIS STUDENT
------------------------------------------------------------------------------------------ --------- ----------Magrone,Joytine R.
181030546 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------GROSS INCOME:
13500
14091
WORKSHEET A TOTAL:
300
0
WORKSHEET B TOTAL:
600
0
------------------------------------------------------------------------------------------ --------- ----------Magrone,Willy L.
181030547 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------GROSS INCOME:
27575
26753
INCOME TAX PAID:
1200
0
STUDENT INC FROM WORK:
1000
0
SPOUSE INC FROM WORK:
26000
26742
WORKSHEET B TOTAL:
2550
0
WORKSHEET C TOTAL:
3250
343
------------------------------------------------------------------------------------------ --------- ----------Magrone,JuliAnn M.
181030548 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------STUDENT INC FROM WORK:
2500
335
WORKSHEET B TOTAL:
1500
0
18-204
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
31-MAY-2002 07:37 AM
2
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Verification Discrepancy Report
PAGE
RNRVRFY
NAME
ID NUMBER PAR/STUDENT
------------------------------------------------------------------------------------------ --------- ----------Magrone,Oskarem
181030549 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------TAX FORM IND:
1
2
ELIGIBILITY IND:
1
GROSS INCOME:
7225
6802
INCOME TAX PAID:
900
891
STUDENT INC FROM WORK:
7100
6779
------------------------------------------------------------------------------------------ --------- ----------Magrone,Andora R.
181030550 STUDENT
VERIFICATION RECORD
CURRENT RECORD
----------------------------------------------------------ELIGIBILITY IND:
1
2
INCOME TAX PAID:
1600
16
STUDENT INC FROM WORK:
17001
381
18-205
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Automatic Rule Compilation Process (ROOGSQL)
This process creates a SQL statement from the Budgeting, Tracking and Packaging Group Selection rules.
Description
Parameters for running the ROOGSQL process are automatically created by the RORRULE form.
Parameters
Name
Required?
Description
Values
Compile Code
Yes
This is the Compile code.
%GAAwarding Rules
%GBBudgeting
%GDDisbursement Rules
%GFFund Rules
%GPPackaging
%GTTracking
Select ID
18-206
Banner Financial Aid 8.3
User Guide
Reports and Processes
Yes
Internal Identifier of the Group code
Aid Year Inquiry form (ROIAIDY)
January 2009
Financial Aid New Year Roll Process (ROPROLL)
This process rolls over selected, aid-year specific information from one aid year to another.
Description
Parameters
18-207
Name
Required?
Description
Values
From Aid Year Code
Yes
Aid Year Code from which rules are to be rolled.
Aid Year Inquiry form (ROIAIDY)
To Aid Year Code
Yes
.Aid Year Code to which rules are to be rolled.
Aid Year Inquiry form (ROIAIDY)
Perform roll of group
rolls
Yes
Perform roll of Group rolls.
Y
Yes (default)
N
No
Perform roll of FUND
data
Yes
Y
Yes (default)
N
No
Perform roll of
BUDGET data
Yes
Y
Yes (default)
N
No
Perform roll of
TRACKING data
Yes
Y
Yes (default)
N
No
Perform roll of
PACKAGING data
Yes
Y
Yes (default)
N
No
Perform roll of
COMMON data
Yes
Y
Yes (default)
N
No
Perform roll of
EMPLYMNT data
Yes
Y
Yes (default)
N
No
Perform roll of
ATHLETIC data
Yes
Y
Yes (default)
N
No
Banner Financial Aid 8.3
User Guide
Reports and Processes
Perform roll of Fund data.
Perform roll of Budget data.
Perform roll of Tracking data.
Perform roll of Packaging data.
Perform roll of Common data.
Perform roll of Employment data.
Perform roll of ATHLETIC data.
January 2009
Financial Aid New Year Roll Process Sample
19-MAR-2002 09:42:41 AM
BANNER University
1
New Year Roll Process
ROPROLL
-----------------------------------------------------------------------------------------------------------------------------------Roll
Results of Roll Performed
-------------- -----------------------------------------------------------RULE
RULE
RULE
RULE
RORGDAT records rolled from 0203
RORGSQL records rolled from 0203
RORCMPL records rolled from 0203
Rule records rolled from 0203 to
FUND
FUND
FUND
FUND
FUND
FUND
FUND
FUND
RFRASPC records rolled from 0203 to 0304
Unable to roll RFRCOMM records; 0203 records do not exist
Unable to roll RFRBCMP records; 0203 records do not exist
Unable to roll RFRDETC records; 0203 records do not exist
RFRTREQ records rolled from 0203 to 0304
RFRMESG records rolled from 0203 to 0304
RPBLOPT records rolled from 0203 to 0304
Financial Aid Fund data rolled from 0203 to 0304
BUDGET
BUDGET
BUDGET
RBRCOMP records rolled from 0203 to 0304
RBRGMSG records rolled from 0203 to 0304
Financial Aid Budget data rolled from 0203 to 0304
TRACKING
TRACKING
TRACKING
RRRTMSG records rolled from 0203 to 0304
RRRGREQ records rolled from 0203 to 0304
Financial Aid Tracking data rolled from 0203 to 0304
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
PACKAGING
RORAUDT records rolled from 0203 to 0304
RPBOPTS records rolled from 0203 to 0304
Unable to roll RPRGGAP records; 0203 records do not exist
Unable to roll RPRGSHP records; 0203 records do not exist
Unable to roll RPRGEQY records; 0203 records do not exist
Unable to roll RPRDEFG records; 0203 records do not exist
Unable to roll RPRDEFE records; 0203 records do not exist
Unable to roll RPRDEFS records; 0203 records do not exist
RPRGFND records rolled from 0203 to 0304
RPRCLSS records rolled from 0203 to 0304
Financial Aid Packaging data rolled from 0203 to 0304
COMMON
COMMON
COMMON
COMMON
COMMON
COMMON
RTVUSER records rolled from 0203 to 0304
RORPOST records rolled from 0203 to 0304
Unable to roll RCRINFR records; 0203 records do not exist
Unable to roll RCRINFC records; 0203 records do not exist
RORCAMP records rolled from 0203 to 0304
Financial Aid Common data rolled from 0203 to 0304
EMPLOYMENT
EMPLOYMENT
RJRPLRL records rolled from 0203 to 0304
Financial Aid Employment data rolled from 0203 to 0304
18-208
Banner Financial Aid 8.3
User Guide
Reports and Processes
to 0304
to 0304
to 0304
0304
January 2009
19-MAR-2002 09:42:41 AM
BANNER University
2
New Year Roll Process
ROPROLL
-----------------------------------------------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name
One up Number
Aid Year To .....................
Aid Year From ...................
Perform 'roll' of Group Rules
Perform 'roll' of Fund Data
Perform 'roll' of Budget Data
Perform 'roll' of Tracking Data
Perform 'roll' of Packaging Data
Perform 'roll' of Common Data
Perform 'roll' of Employment Data
Number of lines per page
Report file name
:ROPROLL(5.3)
:7446
:0203
:0304
:Y
:Y
:Y
:Y
:Y
:Y
:Y
:55
:c:\temp\jobsub\fatest_faisusr_roproll_7446.lis
Total pages Printed
:2
****** END OF REPORT ******
18-209
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
SAP Assignment Process (ROPSAPR)
This is the Satisfactory Academic Progress Assignment Process.
Description
Parameters
18-210
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution
Table (ROBINST).
Aid Year Inquiry form (ROIAIDY)
Term Code for
Calculation
Yes
Term for which SAP is to be calculated.
Financial Aid Term Query form
(ROITERM)
SAP Effective
Term Code
Yes
Term where the SAP Status Code will be stored.
Financial Aid Term Query form
(ROITERM)
Student ID
No
Must be left blank when running in batch.
NULL
Use All with RORSTAT
for aidy
Yes
Compute SAP for RORSTAT which exists in aid
year of Calculation Term.
Y
Yes (default)
N
No
Use All Enrolled for
Term
Yes
Compute SAP for SFBETRM which exists in
Calculation term.
Y
Yes (default)
N
No
Application Code
No
General area for which the Selection ID was defined. Application Inquiry form (GLIAPPL)
Creator ID
No
The ID of the person creating the sub-population
rules.
Selection Identifier
No
Code that identifies the sub-population to work with.
User ID
No
The ID of the person using the sub-population rules.
Create RORSTAT
Record Y or N
No
Enter Y to have a RORSTAT record created for each
aid year/applicant.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Y
Yes
N
No (default)
January 2009
SAP Assignment Process Sample
06-AUG-2001 04:24:09 PM
SunGard Higher Education Development
1
Aid Year: 0001
SAP Status Report
ROPSAPR
-----------------------------------------------------------------------------------------------------------------------------------Locked SAP Status Records for Term : 200120
NAME
ID
Locked SAP Code Description
------------------------------------------------------------ --------- --------------- ------------------------------
Total Locked SAP Records ....... : 0
Total Processed Records for Term : 484
06-AUG-2001 04:24:09 PM
2
SunGard Higher Education Development
CONTROL SUMMARY
--------------Program Name
One up Number
Aid Year Code
Term Code for Calculation
SAP Effective Term Code
Student ID
Use All with RORSTAT for aidy
Use All Enrolled for Term
Create RORSTAT record
Number of lines per page
Report file name
:ROPSAPR(5.1)
:750140
:0001
:200110
:200120
:
:Y
:N
:N
:55
:/u/jobsub/ropsapr_750140.lis
Total pages Printed
:2
****** END OF REPORT ******
18-211
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Financial Aid Term Roll Process (ROPTERM)
The Financial Aid Term Roll Process enables you to roll existing data for third party contracts and exemptions
from one term to a new term. By default, the process rolls both contracts and exemptions. You can use parameters
to only roll contracts or to only roll exemptions. You can also run the process in audit mode - to report what would
roll if you ran the process in update mode (without actually updating any data).
Description
Parameters
Name
Required?
Description
Values
From Term Code (1 - 8)
See
Description
Specify the “from” term code (the source of the data) Financial Aid Term Code Inquiry
and the “to” term code (the destination of the data) (ROITERM)
in parameters 01 and 02. You can optionally specify
up to eight “from” and “to” term code pairs.
To Term Code (1 - 8)
See
Description
Specify the “from” term code (the source of the data) Financial Aid Term Code Inquiry
and the “to” term code (the destination of the data) (ROITERM)
in parameters 01 and 02. You can optionally specify
up to eight “from” and “to” term code pairs.
Run Mode
Yes
Specify whether to run the process in audit or update
mode.
A (Audit) A report is generated, but no
data updates occur.
U (Update) Both a report and data
updates occur.
Roll Contracts
Yes
Roll eligible contracts to new term.
Y (Yes) (default)
N (No)
Roll Exemptions
Yes
Roll eligible exemptions to new term.
Y (Yes) (default)
N (No)
18-212
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
User-Defined Data Process (ROPUSER)
The ROPUSER Process:
Description
• creates an aid year-specific row in the ROBUSDF Table for all students with an Applicant Status record
(RORSTAT) based on the Aid Year Code parameter,
• optionally creates a non-aid year-specific row in the ROBNYUD Table based on the Create non year record
parameter for all students with an Applicant Status record (RORSTAT) for the aid year code entered as the
first parameter.
In both cases, row creation only occurs for those students that do not already have a row in the table. Once you’ve
created the rows, you can include data from the tables when you write simple rules on the Financial Aid Selection
Rules form (RORRULE).
Parameters
18-213
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Create non year record
Yes
If this parameter is set to Y, the process inserts a non
year user-defined field record for the PIDM if a
RORSTAT record exists for the student for the aid
year.
N
Do not create a non year record
(default)
Y
Create a non year record
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Audit Log Report (RORALOG)
The Audit Log Report prints logged data changes and deletions. It also provides the option to purge the data log.
Description
Parameters
18-214
Name
Required?
Description
Values
Aid Year/
Non-Aid Year Ind.
No
This option determines whether or not you want to
print data logs with the aid year in the table.
1
Print logs with aid year
2
Print logs without aid year
Aid Year Code
No
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Beginning Activity Date No
You can optionally restrict the Audit Log Report to a
range of activity dates. The beginning date
determines the beginning range of activity dates in
which the logged data should fall. The system prints
the logged data created on or after this date.
DD-MMM-YYYY format
Ending Activity Date
No
You can optionally restrict the Audit Log Report to a DD-MMM-YYYY format
range of activity dates. The ending date determines
the ending range of activity dates in which the
logged data should fall. The system prints the logged
data created on or before this date.
Purge Data Logs
Indicator
No
This optional parameter enables you to delete the
logged records after you print the records.
N
Do not purge data logs
Y
Purge data logs
Purge Beginning Date
No
You can optionally purge logged records for a range
of activity dates. The beginning date determines the
beginning of the range of records that you want to
purge. The system purges the logged data created on
or after this date.
DD-MMM-YYYY format
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
18-215
Required?
Description
Values
Purge Ending Date
No
You can optionally purge logged records for a range
of activity dates. The ending date determines the
ending of the range of records that you want to
purge. The system purges the logged data created on
or before this date.
DD-MMM-YYYY format
Sort Sequence
No
You can sort the report data with one of the
following options
1
Sort by Name and Activity date
2
Sort by ID, Name, and Activity dt
3
Sort by ID, Activity dt, and Name
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Audit Log Report Sample
26-MAY-2001 10:19:12
1
AID YEAR: 0001 Aid Year 2000 - 2001
ID
NAME
DATA ELEMENT
RPRDATE_CUT_OFF_CHG_DATE
SunGard Higher Education Development
PAGE
Audit Log Report
SOURCE
FROM
22-JAN-2001 00:00:00
SEQ
ACTIVITY DATE
USER ID
03-MAY-1999
BSANTORO
TO
03-MAY-2001
RORALOG
EDE CORRECTION
Y
EDE DATE SENT
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
22-JAN-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
22-JAN-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
05-MAY-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
05-MAY-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
03-MAY-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
22-JAN-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
05-MAY-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBLOPT_LENDER_ID
888888
18-216
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
26-MAY-2001 10:19:12
AID YEAR: 0001 Aid Year 2000 - 2001
ID
SunGard Higher Education Development
Audit Log Report
NAME
DATA ELEMENT
RPBLOPT_LENDER_ID
SOURCE
FROM
SEQ
ACTIVITY DATE
05-MAY-1999
TO
888888
PAGE
RORALOG
USER ID
BSANTORO
EDE CORRECTION
Y
EDE DATE SENT
SUPPLEMENTARY DATA ELEMENT
VALUE
(continued)
RPBLOPT_MEMO_LOAN_AMT_IND
Y
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-1999
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPRDATE_CUT_OFF_CHG_DATE
05-MAY-2001 00:00:00
05-MAY-2001
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
05-MAY-2001
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBOPTS_DISB_ACT_ENROLL_IND
E
B
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
06-MAY-2001
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBOPTS_DEFAULT_OPTION_IND
1
2
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
06-MAY-2001
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBOPTS_DEFAULT_OPTION_IND
2
1
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
06-MAY-2001
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBLOPT_LENDER_ID
888888
SUPPLEMENTARY DATA ELEMENT
VALUE
RPBLOPT_MEMO_LOAN_AMT_IND
Y
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
06-MAY-2001
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBLOPT_SAT_TREQ_IND
Y
N
SUPPLEMENTARY DATA ELEMENT
VALUE
RPBLOPT_LENDER_ID
888888
-----------------------------------------------------------------------------------------------------------------------------------ID
NAME
SOURCE
SEQ
ACTIVITY DATE
USER ID
EDE CORRECTION
EDE DATE SENT
06-MAY-2001
BSANTORO
Y
DATA ELEMENT
FROM
TO
RPBLOPT_LENDER_ID
888888
18-217
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
2
26-MAY-2000 10:19:12
AID YEAR: 0001 Aid Year 2000 - 2001
SunGard Higher Education Development
Audit Log Report
PAGE
RORALOG
659
* * * REPORT CONTROL INFORMATION * * *
RPTNAME..........................:
REPORT SEQUENCE NUMBER...........:
USE AID YEAR TO RETRIEVE RECS....:
AID YEAR.........................:
REPORT BEGIN ACTIVITY DATE.......:
REPORT END ACTIVITY_DATE.........:
PURGE LOGGED RECORDS.............:
PURGE BEGIN ACTIVITY DATE........:
PURGE END ACTIVITY DATE..........:
SORT OPTIONS CHOSEN..............:
LINE COUNT.......................:
RECORD COUNT.....................:
18-218
Banner Financial Aid 8.3
User Guide
Reports and Processes
RORALOG
175358
YES
0001
01-JAN-2000
26-MAY-2001
NAME & ACTIVITY DATE
55
5753
January 2009
Basic Applicant Report (RORAPLT)
The Basic Applicant Report produces a listing of applicant names, IDs, and application dates.
Description
Parameters
18-219
Name
Required?
Description
Values
Selection Identifier
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application Code and Creator ID of
Selection ID parameters.
Population Selection Inquiry form
(GLISLCT)
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection Identifier and Creator ID of
Selection ID parameters.
Application Inquiry form (GLIAPPL)
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Sort Option
Name or ID)
Yes
You can sort the report data with one of the
following options.
ID
Creator ID
of Selection ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection Identifier and Application Code
parameters.
User Identification Control form
(GUAIDEN)
Banner Financial Aid 8.3
User Guide
Reports and Processes
Name (default)
January 2009
Basic Applicant Report Sample
31-MAY-2002 07:43 AM
AID YEAR: 0203
Award Year 2002-2003
APPLICANT NAME
Case M1, 1st Test A.
Case M2, 2nd Test B.
Case M3, 3rd Test C.
Case M4, 4th Test D.
Case M5, 5th Test E.
Case M4, 6th Test F.
Case M5, 7th Test G.
Case M6, 8th Test H.
Case M7, 9th Test I.
Case M10, 10th Test J.
Magrone, Coronet
Magrone, Trumpet
Magrone, Trumbone
Magrone, Frenchhorn
Magrone, Clarinet
Magrone, Warmgun
Magrone, Motter
Magrone, Joe
Magrone, Ina Can
Magrone, Ina Cannot
Magrone, Melanie N.
Magrone, Jodi L.
Magrone, Brian A.
Magrone, Daniel B.
Magrone, Aaron C.
Silvaint, Kevin Y.
Magrone, Jenell M.
Magrone, Christian R.
Magrone, Neggy
Magrone, Collin C.
Magrone, Michael J.
Magrone, Shannon M.
Magrone, Jason M.
Magrone, Caroline M.
Magrone, Kyle D.
Magrone, Nathaniel M.
Magrone, Jyoti R.
Magrone, William L.
Magrone, Julie M.
Magrone, Onkar
Magrone, Anand R.
Magrone, Peter N.
Magrone, Ella A.
Magrone, Lea C.
Magrone, Michael
Magrone, Chinaemerem B.
Magrone, Kirsten
18-220
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
Basic Applicant Report
ID
181030001
181030002
181030003
181030004
181030005
181030006
181030007
181030008
181030009
181030010
181030101
181030102
181030103
181030104
181030105
181030106
181030107
181030108
181030109
181030110
181030501
181030502
181030503
181030504
181030505
181030506
181030507
181030508
181030509
181030510
181030511
181030512
181030513
181030514
181030515
181030516
181030517
181030518
181030519
181030520
181030521
181030522
181030523
181030524
181030525
181030526
181030527
PAGE
1
RORAPLT
APPLICATION
DATE
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
03-AUG-2001
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
01-JAN-2002
22-JAN-2002
22-JAN-2002
19-JAN-2002
26-JAN-2002
26-JAN-2002
25-JAN-2002
28-JAN-2002
01-FEB-2002
01-FEB-2002
01-FEB-2002
03-FEB-2002
02-FEB-2002
02-FEB-2002
03-FEB-2002
01-FEB-2002
03-FEB-2002
03-FEB-2002
02-FEB-2002
02-FEB-2002
03-FEB-2002
03-FEB-2002
04-FEB-2002
06-JAN-2002
04-JAN-2002
04-JAN-2002
05-JAN-2002
08-JAN-2002
January 2009
31-MAY-2002 07:43 AM
AID YEAR: 0203
Award Year 2002-2003
SunGard Higher Education Development
Basic Applicant Report
APPLICANT NAME
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
ID
Virginia C.
Cenzina
Kristen
Gina C.
Joliette N.
Toshana K.
Staley L.
Joytine R.
Willy L.
JuliAnn M.
Oskarem
Andora R.
31-MAY-2002 07:43 AM
AID YEAR: 0203
Award Year 2002-2003
181030528
181030529
181030541
181030542
181030543
181030544
181030545
181030546
181030547
181030548
181030549
181030550
PAGE
2
RORAPLT
APPLICATION
DATE
07-JAN-2002
29-APR-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
27-MAY-2002
SunGard Higher Education Development
Basic Applicant Report
PAGE
3
RORAPLT
* * * REPORT CONTROL INFORMATION * * *
RPTNAME: RORAPLT
VERSION#: (3.3)
REPORT SEQUENCE NUMBER: 789297
AID YEAR: 0203
SELECTION IDENTIFIER: 0203_APPS
APPLICATION CODE: FINAID
CREATOR ID: SMAGRONE
SORT OPTION: ID
LINE COUNT: 55
RECORD COUNT: 59
18-221
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Batch Posting Process (RORBPST)
Description
The purpose of the Batch Posting Process is to enable you to post the same data to all students who meet a common
set of criteria. For example, you could post a tracking requirement for proof of citizenship status for all students
who are permanent resident aliens. The use of batch posting can greatly reduce the number of budget or tracking
groups that you need to define.
Use the generic population selection process to identify the students to receive batch posted data. The Batch
Posting Process requires 3 steps.
1. Create a Population Selection ID to identify the subpopulation of students to receive the batch posted data.
This is done on the Population Selection Definition Rules form (GLRSLCT). The process to extract the IDs of
the students who meet the Population Selection ID criteria is called the Batch Report Selection Extract Process
(GLBDATA). Individual student IDs can be inserted into or deleted from the list of students generated by
using the Extract Application form (GLAEXTR).
2. Identify the type of data to be posted, the codes to be posted, and the information showing where the IDs of
the extracted students are being stored. This is done on the Batch Posting Rules form (RORPOST). The Batch
Posting Type Indicator Validation form (RTVPTYP) is used as a List form for the posting type code, but you
can't update any fields on this form. Multiple types of data can be set up to be posted during the same run of
the process. For example, you can post tracking requirements, budget adjustments, and award amounts all in
the same run of the program. The Use Indicator field tells the batch posting process which rules to execute
during the next run of the program. You cannot set the order in which multiple batch posting rules are
executed. Therefore, if batch posting of one type of data depends on the results of another type of batch
posting, you should run each batch posting rule by itself. This way you can control the order in which they are
processed.
3. Run the Batch Posting Process (RORBPST). The process uses the batch posting rules established on the
RORPOST form. The only parameters for the process are Aid Year and Print Report (Y/N). The optional
printed report shows a listing of students who received each type of batch posted data with comments about
anything unusual.
With this process, you may post a lock to the any of the three group locks (tracking, budgeting, packaging). When
any of these three lock fields is changed, the change is logged.
You can use the value in the RORPOST_ISIR_COMMENT_RJCT_CDE AND RORPOST_ISIR_COMMENT_RJCT_TYPE
columns to add additional selection criteria in addition to the population selection defined.
18-222
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Unless these two fields are populated, no change in processing occurs. However, if these two fields are populated,
the batch posting process uses this data to add a conditional statement to the population selection associated with
this record, and only performs the requested function if the defined comment code or reject code exists for this
applicant on the current needs analysis record.
If an applicant in the population does not meet the additional comment code or reject code condition, then a
message is posted to the report, stating: ‘Record not updated. Not a match on ISIR comment or reject code.’
The process updates all instances of a tracking requirement when the Satisfy All indicator is set on RTVTREQ for
that tracking requirement. This allows all instances of an entrance interview to be satisfied at one time, regardless
of the fund code associated with it, within the same aid year.
When updating a tracking requirement where RTVTREQ_SATISFY_ALL_IND = Y, the form updates all tracking
requirements that are the same (RRRAREQ_TREQ_CODE) regardless of any fund code that may exist on any of the
records or the fund code may be null.
When a Batch Post Type of VS is updated, Banner uses the status code to determine whether to update the
Verification Complete flag. If during processing, the Verification Complete flag is set to Y for yes, then the User
ID and Date will also be updated and displayed on the Applicant Status form (ROASTAT) with the Verification
Complete flag. If during processing, the Verification Complete flag is set to N for no, then null values will be
updated to the User ID and Date for the Verification Complete flag on ROASTAT.
Parameters
18-223
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Print Report (Y/N)
No
This parameter enables you to optionally print a
listing of students who received each type of batch
posted data.
Y
Print report (default)
N
Do not print report
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Batch Posting Process Sample
31-MAY-2002 08:39 AM
AID YEAR: 0203 Award Year 2002-2003
APPLICATION:
SELECTION ID:
CREATOR ID:
USER ID:
FINAID
0203_APPS
SMAGRONE
SMAGRONE
STUDENT NAME
Case M1, 1st Test A.
Case M10, 10th Test J.
Case M2, 2nd Test B.
Case M3, 3rd Test C.
Case M4, 4th Test D.
Case M4, 6th Test F.
Case M5, 5th Test E.
Case M5, 7th Test G.
Case M6, 8th Test H.
Case M7, 9th Test I.
Magrone, Aaron C.
Magrone, Anand R.
Magrone, Andora R.
Magrone, Andora R.
Magrone, Brian A.
Magrone, Caroline M.
Magrone, Cenzina
Magrone, Chinaemerem B.
Magrone, Christian R.
Magrone, Clarinet
Magrone, Collin C.
Magrone, Coronet
Magrone, Daniel B.
Magrone, Ella A.
Magrone, Frenchhorn
18-224
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
Batch Posting Process Report
PAGE
RORBPST
1
POSTING TYPE: E Enrollment Status for Year
CODE TO POST: 1
AMOUNT TO POST:
STATUS OR TERM:
DATE TO POST:
MISC CODE:
CATEGORY:
ISIR TYPE:
ISIR VALUE:
ID
181030001
181030010
181030002
181030003
181030004
181030006
181030005
181030007
181030008
181030009
181030505
181030521
181030550
181030550
181030503
181030514
181030529
181030526
181030508
181030105
181030510
181030101
181030504
181030523
181030104
RESULTS
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
FM record does not exist; enrollment status
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment status posted
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not updated
Enrollment status posted
not
not
not
not
not
not
not
not
not
not
posted
posted
posted
posted
posted
posted
posted
posted
posted
posted
January 2009
Magrone, Gina C.
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
Magrone,
18-225
181030542
Gina C.
Ina Can
Ina Cannot
Jason M.
Jenell M.
Jodi L.
Joe
Joliette N.
Joliette N.
Joytine R.
Joytine R.
JuliAnn M.
JuliAnn M.
Julie M.
Jyoti R.
Kirsten
Kristen
Banner Financial Aid 8.3
User Guide
Reports and Processes
181030542
181030109
181030110
181030513
181030507
181030502
181030108
181030543
181030543
181030546
181030546
181030548
181030548
181030519
181030517
181030527
181030541
Enrollment Status unchanged; not updated
Enrollment Status unchanged; not
Enrollment status posted
Enrollment status posted
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment status posted
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
Enrollment Status unchanged; not
updated
updated
updated
updated
updated
updated
updated
updated
updated
updated
updated
updated
updated
updated
January 2009
31-MAY-2002 08:39 AM
2
AID YEAR: 0203 Award Year 2002-2003
APPLICATION:
SELECTION ID:
CREATOR ID:
USER ID:
FINAID
0203_APPS
SMAGRONE
SMAGRONE
STUDENT NAME
Magrone, Kristen
Magrone, Kyle D.
Magrone, Lea C.
Magrone, Melanie N.
Magrone, Michael
Magrone, Michael J.
Magrone, Motter
Magrone, Nathaniel M.
Magrone, Neggy
Magrone, Onkar
Magrone, Oskarem
Magrone, Oskarem
Magrone, Peter N.
Magrone, Shannon M.
Magrone, Staley L.
Magrone, Staley L.
Magrone, Toshana K.
Magrone, Toshana K.
Magrone, Trumbone
Magrone, Trumpet
Magrone, Virginia C.
Magrone, Warmgun
Magrone, William L.
Magrone, Willy L.
Magrone, Willy L.
Silvaint, Kevin Y.
18-226
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
PAGE
Batch Posting Process Report
RORBPST
POSTING TYPE: E Enrollment Status for Year
CODE TO POST: 1
AMOUNT TO POST:
STATUS OR TERM:
DATE TO POST:
MISC CODE:
CATEGORY:
ISIR TYPE:
ISIR VALUE:
ID
RESULTS
181030541
181030515
181030524
181030501
181030525
181030511
181030107
181030516
181030509
181030520
181030549
181030549
181030522
181030512
181030545
181030545
181030544
181030544
181030103
181030102
181030528
181030106
181030518
181030547
181030547
181030506
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Enrollment
Status
Status
Status
Status
Status
Status
status
Status
Status
Status
Status
Status
Status
Status
Status
Status
status
Status
Status
Status
Status
status
Status
Status
Status
Status
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
posted
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
posted
unchanged;
unchanged;
unchanged;
unchanged;
posted
unchanged;
unchanged;
unchanged;
unchanged;
not
not
not
not
not
not
updated
updated
updated
updated
updated
updated
not
not
not
not
not
not
not
not
not
updated
updated
updated
updated
updated
updated
updated
updated
updated
not
not
not
not
updated
updated
updated
updated
not
not
not
not
updated
updated
updated
updated
January 2009
31-MAY-2002 08:39 AM
AID YEAR: 0203 Award Year 2002-2003
APPLICATION:
SELECTION ID:
CREATOR ID:
USER ID:
FINAID
DEBS_LOAN
DANDREAS
DANDREAS
Loan
Loan
Loan
Loan
Loan
Loan
Loan
Loan
ID
9000
9001
9002
9003
9004
9005
9006
9007
31-MAY-2002 08:39 AM
AID YEAR: 0203 Award Year 2002-2003
APPLICATION:
SELECTION ID:
CREATOR ID:
USER ID:
FINAID
MANUAL
TZIZOS
TZIZOS
STUDENT NAME
Silvaint, Kevin Y.
18-227
PAGE
RORBPST
3
PAGE
RORBPST
4
POSTING TYPE: VS Verification Status
CODE TO POST: W
AMOUNT TO POST:
STATUS OR TERM:
DATE TO POST:
MISC CODE:
CATEGORY:
ISIR TYPE:
ISIR VALUE:
STUDENT NAME
Andreas,
Andreas,
Andreas,
Andreas,
Andreas,
Andreas,
Andreas,
Andreas,
SunGard Higher Education Development
Batch Posting Process Report
Banner Financial Aid 8.3
User Guide
Reports and Processes
165009000
165009001
165009002
165009003
165009004
165009005
165009006
165009007
RESULTS
Verification
Verification
Verification
Verification
Verification
Verification
Verification
Verification
Status
Status
Status
Status
Status
Status
Status
Status
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
unchanged;
not
not
not
not
not
not
not
not
updated
updated
updated
updated
updated
updated
updated
updated
SunGard Higher Education Development
Batch Posting Process Report
POSTING TYPE: VS Verification Status
CODE TO POST: V
AMOUNT TO POST:
STATUS OR TERM:
DATE TO POST:
MISC CODE:
CATEGORY: VERIF_STAT
ISIR TYPE:
ISIR VALUE:
ID
181030506
RESULTS
Verification Status unchanged; not updated
January 2009
31-MAY-2002 08:39 AM
AID YEAR: 0203 Award Year 2002-2003
APPLICATION:
SELECTION ID:
CREATOR ID:
USER ID:
FINAID
SAM_V
SMAGRONE
SMAGRONE
STUDENT NAME
Magrone, Ella A.
Magrone, Lea C.
Magrone, Michael
31-MAY-2002 08:39 AM
AID YEAR: 0203 Award Year 2002-2003
APPLICATION:
SELECTION ID:
CREATOR ID:
USER ID:
FINAID
SAM_W
SMAGRONE
SMAGRONE
STUDENT NAME
Magrone, Chinaemerem B.
Magrone, Kirsten
Magrone, Virginia C.
18-228
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
Batch Posting Process Report
PAGE
RORBPST
5
PAGE
RORBPST
6
POSTING TYPE: VS Verification Status
CODE TO POST: V
AMOUNT TO POST:
STATUS OR TERM:
DATE TO POST:
MISC CODE:
CATEGORY:
ISIR TYPE:
ISIR VALUE:
ID
181030523
181030524
181030525
RESULTS
Verification Status unchanged; not updated
Verification Status unchanged; not updated
Verification Status unchanged; not updated
SunGard Higher Education Development
Batch Posting Process Report
POSTING TYPE: VS Verification Status
CODE TO POST: W
AMOUNT TO POST:
STATUS OR TERM:
DATE TO POST:
MISC CODE:
CATEGORY:
ISIR TYPE:
ISIR VALUE:
ID
181030526
181030527
181030528
RESULTS
Verification Status unchanged; not updated
Verification Status unchanged; not updated
Verification Status unchanged; not updated
January 2009
31-MAY-2002 08:39 AM
AID YEAR: 0203 Award Year 2002-2003
SunGard Higher Education Development
Batch Posting Process Report
PAGE
RORBPST
7
* * * REPORT CONTROL INFORMATION * * *
REPORT SEQUENCE NUMBER: 789303
RPTNAME: RORBPST
VERSION #: (5.5)
USER ID: SMAGRONE
AID YEAR: 0203
LINES PER PAGE: 55
RECORD COUNT: 84
18-229
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Calculated Values Process (RORCALC)
The Calculated Values Process calculates an applicant’s IM and FM values for Gross Need and Unmet Need.The
process stores the following values in the student's RORSTAT record.
Description
• RORSTAT_UNMET_NEED
• RORSTAT_TFC
• RORSTAT_RESOURCE_AMT
• RORSTAT_RESOURCE_ACT_DATE
• RORSTAT_IM_GRS_NEED
• RORSTAT_IM_UNMET_NEED
• RORSTAT_IM_TFC
It also enables you to optionally print the results on the Calculated Values Report.
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Print Report
No
This parameter enables you to optionally print the
Calculated Values Report.
F
Print FM Overawards Only
I
Print IM Overawards Only
N
Do Not Print Report (default)
O
Print ALL Overawards
Y
Print All Selected Students
Report Selection
Query ID
18-230
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application Code and Creator ID of
Selection ID parameters.
Population Selection Inquiry form
(GLISLCT)
January 2009
Parameters (cont) Name
Required?
Description
Values
Application Code
No
Application code of the population selection. If you
enter a value for this parameter, you must also enter
a value for the Selection ID and Creator ID of
Selection ID parameters.
Application Inquiry form (GLIAPPL)
Creator ID
of Selection ID
No
The Banner ID of the person that created the
population selection. If you enter a value for this
parameter, you must also enter a value for the
Selection ID and Application Code parameters.
User Identification Control form
(GUAIDEN)
Sort Order
No
The following sort options are available for this
report.
N
Name (default)
I
ID
User ID
18-231
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
The ID of the person using the sub-population base.
January 2009
Calculated Values Process Sample
27-MAY-2001 12:24 PM
1
AID YEAR: 0001 Aid Year 2000 - 2001
STUDENT NAME
Abba, Lucy
Abcde, Craig P.
Abell, Heather
Abell, Heather L.
Abraham, Daniel
Abraham, John
Adams, Natalie
Agosto, Anne S.
Arnold, James B..
B.Dot, A.’Baldwin, Steven B.
Baraka, Amiri L.
Barnet, Harold L.
Barney, Rubble A.
Bayler, Ross M.
Bennett, Toni
Bennett, Virginia
Blake, Ian Russell.
Blake, John
Bogart, Humphrey W.
Camp, James
Caruso, Janet
Clinton, Albert H.
Cloth, A Terry.
Cohen, Michele W.
Conway, Paul
D’Alessio, Lina
Davis, William Arthur.
DeCina, Robert
Demarco, Bernadete C.
Desmond, Michael
Douglas, Maria S.
Dunn, Charles D.
Dunn, Charles T.
Edwards, Anthony
Farber, Joan
Farber, Joan E.
Flite, Cloud T.
Fly You Way, Ana T.
Four, Lucy
Francis, Marty
Fred, Jim
Freely, Evan P..
Fudd, Elmer W.
Galella, Brandy
18-232
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
PAGE
Calculated Values Report
ID
212580001
236010009
058643000
058643000
@00000653
@00000654
236010027
@00000054
911111115
236010099
234567891
069987246
601000051
236010019
076289824
@00000918
161335820
181489814
999555111
236010011
902109021
902109026
345678910
610578709
236010017
902109028
236010005
911111111
058643011
456989101
902109025
236010013
690113400
@00000921
817190909
@00000922
678910111
236010046
236010015
212580004
236010028
056640002
332664167
236010014
058643111
FM GROSS NEED
FM UNMET NEED
15,450.00
.00
.00
.00
.00
.00
.00
.00
24,252.00
.00
.00
.00
10,172.00
.00
.00
16,287.00
16,287.00
.00
19,189.00
.00
.00
.00
19,400.00
.00
.00
.00
.00
14,015.00
.00
19,767.00
.00
15,752.00
16,511.00
16,511.00
.00
20,038.00
20,038.00
.00
.00
16,034.00
.00
.00
.00
.00
.00
8,875.00
.00
.00
.00
.00
.00
.00
.00
13,252.00
.00
.00
.00
10,172.00
.00
.00
16,287.00
16,287.00
.00
13,564.00
.00
-12,000.00
-14,009.00
19,400.00
.00
.00
-10,275.00
.00
1,150.00
-2,742.00
19,767.00
-12,605.00
15,722.05
16,511.00
16,511.00
.00
20,038.00
20,038.00
.00
.00
13,475.00
.00
.00
.00
.00
.00
RORCALC
FM EFC
IM GROSS NEED
IM UNMET NEED
IM EFC
.00
.00
24,999.00
24,999.00
.00
.00
102,595.00
166,798.00
.00
10,831.00
.00
99,999.00
9,228.00
57,256.00
2,080.00
1,413.00
1,413.00
17,692.00
.00
16,524.00
5,794.00
1,066.00
.00
20,904.00
.00
2,315.00
17,579.00
1,435.00
1,218.00
1,133.00
1,770.00
.00
1,189.00
1,189.00
10,831.00
862.00
862.00
.00
99,999.00
1,416.00
3,438.00
45,373.00
.00
January 2009
27-MAY-2001 12:24 PM
2
AID YEAR: 0001 Aid Year 2000 - 2001
STUDENT NAME
Ganesh, Shanmuganathan
Gardner, Jessica
Garling, Harriet T.
Garling, Howard T.
Harris, David
Hendley, Jason Ronald.
Hunt, Heather
Hunt, Natalie
Iffin, Muffin
Ionelli, Marsha
Jackson, Candy E.
Jacob, O’ Brien
Johnson, Elizbeth
Johnson, Judith Janine.
Johnson, Judy J.
Jones, Robin
Juarez, Alphonso J.
Kaplan, Andrea
Kleenex, Tissue A.
Laforge, Andrew M.
Laughlin, Michael
Lighting, Addison T.
Lopez, Lisa K.
Lothrop, Woodward E.
Louis, Darren
Lu, Mary H.
Lucy, Eight
Lucy, Nine
Luu, Jane T.
Marino, Daniel
Masi, Ronald N.
Masi, Roni N.
McBride, Jessica
McCleary, One O.
Mighty, Isis M.
Mitchell, Charles J.
Muehlhof, 24 M.
Munster, Constance
Nelson, Cameron R.
Newengland, Patriots K.
O’Toole, John J.
Oakridge, William W.
Parker, Tom Charles.
Pedds, Theodore
Pennypacker, Melissa
Peters, Nicholas
Phatak, Nikhil
18-233
Banner Financial Aid 8.3
User Guide
Reports and Processes
SunGard Higher Education Development
PAGE
Calculated Values Report
ID
GA
911111116
@00000893
@00000923
236010026
911111113
902109020
902109024
236010021
@00000894
076229870
911111117
@00000895
610009607
601000010
902109022
@00000896
236010024
236010023
129345382
@00000899
236010010
327684165
236010008
236010040
@00000884
212580008
212580009
@00000880
058643004
@00000900
@00000930
236010030
172420001
236010029
@00000931
162440024
333222111
031289426
236010037
002472030
236010016
123456789
236010047
902109027
214281728
NIKHIL
FM GROSS NEED
FM UNMET NEED
15,450.00
10,672.00
.00
.00
29,371.99
15,603.00
.00
.00
.00
17,700.00
.00
.00
.00
.00
.00
.00
19,400.00
.00
.00
13,000.00
1,864.00
16,752.00
.00
.00
.00
.00
6,800.00
6,500.00
.00
.00
19,400.00
19,400.00
21,752.00
.00
.00
17,215.00
.00
12,037.00
.00
.00
.00
.00
.00
.00
.00
.00
.00
4,325.00
3,547.00
.00
.00
15,771.99
5,478.00
-14,250.00
-13,832.00
.00
17,700.00
.00
-15,625.00
.00
.00
.00
-14,125.00
19,400.00
.00
.00
13,000.00
1,864.00
16,722.05
.00
.00
-29.95
.00
5,678.00
5,764.00
.00
-4,000.00
19,400.00
19,400.00
21,722.05
.00
.00
17,215.00
.00
12,037.00
.00
.00
.00
.00
.00
.00
-10,525.00
.00
.00
RORCALC
FM EFC
IM GROSS NEED
IM UNMET NEED
IM EFC
.00
10,228.00
19,903.00
19,903.00
627.00
2,097.00
.00
1,143.00
.00
.00
20,904.00
.00
19,275.00
3,170.00
23,005.00
.00
.00
99,999.00
.00
2,450.00
15,836.00
.00
3,106.00
.00
556.00
.00
.00
753.00
24,999.00
.00
.00
.00
62,136.00
.00
2,185.00
.00
7,042.00
49,946.00
99,999.00
1,350.00
99,999.00
70,952.00
2,052.00
2,790.00
33,161.00
January 2009
Financial Aid E-mail Process(ROREMAL)
This process provides you with the ability to send a mass mailing as an e-mail letter using a population selection.
You can run the process in audit mode, which will print the e-mail letter for all recipients with an e-mail address
selected in the log file. When the process is run in Update mode, the e-mails will be generated and RUAMAIL will
be updated to insert the letter code defined with an Originator of E-Initiated by E-mail process.
Description
Parameters
18-234
Name
Required?
Description
Values
Aid Year Code
Yes
Valid Aid Year Code
LOV: ROIAIDY
E-mail Letter Code
Yes
Letter Code defined for E-Mail letter
LOV: RORELTF form
E-mail Address Type No
Preference
E-Mail Address Type prefixed by a numeric priority
value. Example: 1FAEM, 2INST, 3YAHOO
Student ID
No
ID of Student when running this process for a single
ID
Application ID
No
General area for which the selection was defined.
Selection ID
No
Code that identifies the sub-population to work with. LOV: GLISLCT
Creator ID
No
The ID of the person creating the sub-population
rules.
User ID
No
The ID of the person using the sub-population rules.
Audit/Update Mode
Yes
Code to identify whether to run test (audit), or send e- A – Print to log
mail.
U – Send e-mail
E-mail Subject Text
No
Subject text for the e-mail
FROM E-mail
Address
Yes
Address to show as FROM
Banner Financial Aid 8.3
User Guide
Reports and Processes
LOV: GLIAPPL
January 2009
Parameters (cont Name
18-235
Required?
Description
E-mail Sender’s
Name
No
Name to be sent to personalize the e-mail FROM
address
Mail Host
Yes
Mail host from which the e-mail will be sent
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
January 2009
18-236
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
FISAP Report (RORFSxx)
Description
The FISAP (Fiscal Operations Report and Application to Participate) is the means through which a participating
institution applies for funds for the Federal Perkins Loan, Federal Work Study (FWS), and Federal Supplemental
Educational Opportunity Grant (FSEOG) programs. An institution must submit an electronic FISAP by a
predetermined date in order to qualify for allocations of federal campus-based program funds. Participating
institutions also account for expenditure of federal campus-based program funds for the award year through the
FISAP. The Banner FISAP report prints this required FISAP information in the standard format.
Note
The FISAP refers to the report which includes Fiscal Accounting of Campus Based funds
spent during an award year.
„
To be included on the FISAP, a student must have on file with the institution all information needed to perform a
need analysis based on the information required in Part F of the HEA of 1965, as amended. When certain critical
pieces of need analysis data are missing, the need analysis formula rejects the application and reports the reject
codes that were encountered. Therefore, the presence of reject codes indicates that the student does not have all the
information needed to perform a need analysis calculation. The Banner FISAP excludes students from the FISAP if
any of the student's contributions (that is, Student Contribution, Parent Contribution, or TFC) are flagged as
Estimated on the Results form (RNARSxx). Estimated contributions are a result of the need analysis formula
encountering reject conditions and therefore makes the student ineligible for Title IV funds and should not be
counted on the FISAP.
The FISAP report includes a student if their Total Family Contribution (RCRAPP4_C_INST_1_TOT_FAM_CTRB) is not
blank. This field is populated with a not null value if the record is loaded from a CSS or ACT tape, an AFSA or
EDE tape if no reject conditions exist, and by any INAS calculation performed locally. Therefore, a blank value in
this field means that the institution does not have all the information necessary to perform a need analysis
calculation.
FISAP reporting within Banner is separated into two steps.
1. Select all eligible students, calculate the data necessary to properly place the student on the grid, and store this
data in a temporary FISAP table.
When this step is run, a file called the FISAP Record Creation Log (RORFSxx.log) is created. It lists
students who were selected by the program’s main select routine but eliminated later in the process. It
may help explain why some students were not included on the report that you thought should have been
included. Since some students may be eliminated by the main select, this listing is not all inclusive. A
18-237
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Control Summary is also part of this file. That lists the parameters used when this step was run and
shows the number of students inserted into the FISAP table.
2. Calculate the number of students for each cell on the grid and print the report in the proper year-specific
format. Step 2 uses the data in the FISAP table. The entries in the table are not deleted after you perform this
step.
You can run steps 1 and 2 separately, or you can combine both steps into a single run of the program. You can use
the FISAP Person Maintenance form (ROAFSAP) to display and update individual student data in the table. You
can also use this form to insert or delete student records from the FISAP table.
The FISAP report is a report of federal expenditures made by institutions between July 1 and June 30 of the
particular award year. College work-study employment for summer terms crosses over this border. Some of the
wages are earned before and some are earned after July 1. Because of this breakdown, some students may have
been paid in an aid year for which the student didn’t actually apply for student aid. Banner would not select these
students for inclusion on the FISAP because the student does not have appropriate records in the Student or
Financial Aid systems. In other cases, payment data needs to be corrected because of adjustments made to the
student's AR records outside of Banner Financial Aid. Both of these circumstances can now be handled by the new
FISAP. You can now insert these students into the FISAP table and let Banner do the rest.
Warning
The FISAP Report depends on the student's dependency status and income being reported in
Banner. If you have created student records by just entering the student's EFC on the Results
form (RNARSxx) so that the student could be packaged, then Banner doesn't have sufficient
data in order to accurately place or count the student in the two income grids. As a minimum
you must enter the student's income (both taxable and non-taxable), parents' income (both
taxable and non-taxable) and the student's dependency status. (Dependency statuses can be
directly entered on the Applicant Override form (RNAOVxx) without running an INAS
„
calculation).
18-238
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters
Name
Required?
Description
Values
Aid Year Code
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Create/Print or Both
Yes
This parameter determines if you want to generate
the student data that is necessary for the production
of the FISAP Report.
B
Create and Print (default)
C
Create
The Create function will delete and replace any
current data that exists in the FISAP table.
CD Create and Print Detail
Note: Before being able to print any data, records
must have been created either through the
RORFSxx process and/or manually. Once data is
created by the RORFSxx process, it is possible to
go directly to the FISAP Person Maintenance
(ROAFSAP) and edit that data directly if any
changes are needed. However, it is important to
remember that if you run the RORFSxx process
again, all manual changes will be deleted and will
have to be re-entered.
D
Print Detail
P
Print Both
S
Print Summary
Print FPERK Paid/Offered award amount.
O
FPERK FISAP data based on
Offered amount
P
FPERK FISAP data based on
Paid amount (default)
O
FSEOG FISAP data based on
Offered amount
P
FSEOG FISAP data based on
Paid amount (default)
FPERK Paid or
Offered Amount.
FFSEOG Paid or
Offered Amt.
18-239
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
No
Print FSEOG Paid/Offered award amount.
CS Create and Print Summary
January 2009
Parameters (cont) Name
FWS Paid or
Offered Amount
Billing or
Adjusted Hours
18-240
Required?
Description
Values
No
Print FWS Paid/Offered award amount.
O
FWS FISAP data based on
Offered amount
P
FWS FISAP data based on Paid
amount (default)
A
Enrollment based on Adjusted
Hours (default)
B
Enrollment based on Billing
Hours
I
Sort by total FISAP Income
N
Sort by Last Name (default)
No
Billing or Adjusted hours to be used for enrollment
status.
Sort by Last Name/
FISAP Inc.
No
Application ID
No
General area for which the selection ID was defined.
Selection ID
No
Code that identifies the population with which to
work.
Creator ID
No
ID of the person who created the population rules.
User ID
No
ID of the person who used the population rules.
Undergraduate Level
Codes 1-19
No
Required to select undergraduate students for the
level code. You can specify as many as 19
Undergraduate Level codes and 19 Graduate Level
codes and define the full-time load for each of these
codes when you run the RORFSxx Process.
Although these parameter choices are optional, you
must define at least one Undergraduate or Graduate
Level code and its corresponding FT Load in order
to generate the proper output.
FT Load for UG Codes
1-19
No
Full-time load for Undergraduate Codes 1-19.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Sort by the Last Name or the total FISAP Income.
These parameters are listed as optional
in recognition of the fact that a school
might only have an undergraduate or
graduate course of study — but not
both.
January 2009
Parameters (cont) Name
18-241
Description
Values
Graduate Level Codes 1- No
19 1
Required to select graduate students with this level
code. You can specify as many as 19 Undergraduate
Level codes and 19 Graduate Level codes and define
the full-time load for each of these codes when you
run the RORFSxx Process. Although these
parameter choices are optional, you must define at
least one Undergraduate or Graduate Level code and
its corresponding FT Load in order to generate the
proper output.
These parameters are listed as optional
in recognition of the fact that a
school might only have an
undergraduate or graduate course
of study — but not both.
FT Load for Grad Codes
1-19
Full-time load for Graduate Codes 1-19.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Required?
No
January 2009
RORFSxx_yyyyy.lis File
07-JUL-2005 09:35:36 AM
BANNER University
1
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------Name
ID
FISAP
AUTO
DEP
LEVEL
FULL
AID
AID
INCOME
0 EFC
TIME
FUND
AMT
-----------------------------------------------|-------------|-------|------|------------|---------|---------|---------------------Ede05165, Xxxxxxxxx A.
208000175
|
13000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05166, Xxxxxxxxx A.
208000166
|
4000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05166, Xxxxxxxxx A.
208000176
|
10000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05167, Xxxxxxxxx A.
208000167
|
16000
|
N
| D
|
UWO
|
N
|
|
|
|
|
|
|
|
|
Ede05167, Xxxxxxxxx A.
208000177
|
19000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05168, Xxxxxxxxx A.
208000168
|
37000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05168, Xxxxxxxxx A.
208000178
|
49000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05169, Xxxxxxxxx A.
208000169
|
55000
|
N
| D
|
UWO
|
Y
|
|
|
|
|
|
|
|
|
Ede05169, Xxxxxxxxx A.
208000179
|
15001
|
Y
| D
|
UW
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
FISAPTEST, DEP1 O.
236222221
|
16000
|
N
| D
|
UWO
|
Y
| FPERK |
500.00
|
|
|
|
|
| FSEOG |
500.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTEST, DEP2 T.
236222222
|
10800
|
Y
| D
|
UWO
|
Y
| FPERK |
500.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTEST, DEP3 T.
236222223
|
20000
|
Y
| D
|
UWO
|
N
| FPERK |
500.00
|
|
|
|
|
| FSEOG |
750.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTEST, DEP4 F.
236222224
|
25000
|
N
| D
|
UWO
|
Y
| FPERK |
500.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTEST, DEP5 F.
236222225
|
35000
|
N
| D
|
UWO
|
Y
| FPERK |
500.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
18-242
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Contd...2
07-JUL-2005 09:35:36 AM
BANNER University
2
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------Name
ID
FISAP
AUTO
DEP
LEVEL
FULL
AID
AID
INCOME
0 EFC
TIME
FUND
AMT
-----------------------------------------------|-------------|-------|------|------------|---------|---------|---------------------FISAPTEST, DEP6 S.
236222226
|
43000
|
N
| D
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTest, Grad01 G.
236222241
|
16000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
FISAPTest, Grad03 G.
236222243
|
12000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad04 G.
236222244
|
10000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad05 G.
236222245
|
8000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad06 G.
236222246
|
6000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad07 G.
236222247
|
5000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad08 G.
236222248
|
4000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad09 G.
236222249
|
3000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
FISAPTest, Grad10 G.
236222250
|
2000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
FISAPTest, Grad11 G.
236222251
|
1000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Grad12 G.
236222252
|
500
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
FISAPTest, Ind01 O.
236222231
|
1800
|
N
| I
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTest, Ind02 T.
236222232
|
2500
|
Y
| I
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
18-243
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Contd...3
07-JUL-2005 09:35:36 AM
BANNER University
3
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------Name
ID
FISAP
AUTO
DEP
LEVEL
FULL
AID
AID
INCOME
0 EFC
TIME
FUND
AMT
-----------------------------------------------|-------------|-------|------|------------|---------|---------|---------------------FISAPTest, Ind03 T.
236222233
|
4500
|
N
| I
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
FISAPTest, Ind06 S.
236222236
|
50000
|
N
| I
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTest, Ind07 S.
236222237
|
72000
|
N
| D
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTest, Ind08 E.
236222238
|
17000
|
N
| I
|
UWO
|
Y
| FPERK |
1000.00
|
|
|
|
|
| FSEOG |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTest, Ind09 N.
236222239
|
20000
|
N
| I
|
G
|
Y
| FPERK |
1000.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
TESTFisap, Grad02 G.
236222242
|
14000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
Testc, Andrew A.
200405101
|
3000
|
N
| I
|
UWO
|
Y
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Brent P.
200405102
|
14500
|
N
| I
|
UWO
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Catalina
200405129
|
2700
|
N
| D
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Christopher I.
200405103
|
2100
|
N
| I
|
UWO
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, David M.
200405104
|
900
|
N
| I
|
UWO
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Dennis
200405130
|
15001
|
N
| I
|
UW
|
Y
| FSEOG |
600.00
|
|
|
|
|
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Efram
200405131
|
1000
|
N
| I
|
UW
|
N
|
|
|
|
|
|
|
|
|
Testc, Eleanora M.
200405105
|
6000
|
N
| D
|
UWO
|
N
|
|
18-244
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Contd...4
07-JUL-2005 09:35:36 AM
BANNER University
4
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------Name
ID
FISAP
AUTO
DEP
LEVEL
FULL
AID
AID
INCOME
0 EFC
TIME
FUND
AMT
-----------------------------------------------|-------------|-------|------|------------|---------|---------|---------------------Testc, Frank
200405132
|
500
|
N
| I
|
UW
|
Y
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Frida C.
200405106
|
10999
|
N
| D
|
UW
|
Y
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Glenda
200405133
|
2000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Howard
200405134
|
3000
|
N
| I
|
UW
|
Y
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Isabella
200405135
|
4000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Jordan
200405136
|
5000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Kimberly
200405137
|
6000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Lydia
200405138
|
8000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Martin
200405139
|
10000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Norman
200405140
|
12000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Orson
200405141
|
14000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Patricia
200405142
|
16000
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Quentin
200405143
|
18000
|
N
| I
|
UW
|
Y
| FSEOG |
600.00
|
|
|
|
|
|
FWS |
750.19
|
|
|
|
|
|
|
Testc, Rosalind
200405144
|
50001
|
N
| I
|
UW
|
Y
|
|
|
|
|
|
|
|
|
Testc, Stanley
200405145
|
18000
|
N
| I
|
G
|
Y
|
|
|
|
|
|
|
|
|
18-245
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Contd...5
07-JUL-2005 09:35:36 AM
BANNER University
5
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------PART II, SECTION F: INFORMATION ON ELIGIBLE AID APPLICANTS FOR THE AWARD YEAR (2004-2005 Financial Aid Year)
----------------------------------------------------------------------------------------------------------<--------DEPENDENT-------->
UG Without
UG With
1st Degree
1st Degree
------------------Students With
Auto Zero EFC
Taxable & NonTaxable Income
-------------$
0 -$ 2,999
3,000 - 5,999
6,000 - 8,999
9,000 - 11,999
12,000 - 14,999
15,000 - 17,999
18,000 - 23,999
24,000 - 29,999
30,000 - 35,999
36,000 - 41,999
42,000 - 47,999
48,000 - 53,999
54,000 - 59,999
60,000 & Over
Total
18-246
Banner Financial Aid 8.3
User Guide
Reports and Processes
2
<---------------INDEPENDENT--------------->
UG Without
UG With
Graduate/
1st Degree
1st Degree
Professional
------------------------------
1
0
1
1
1
1
2
1
1
1
1
1
1
1
1
1
0
0
1
0
0
0
0
0
0
0
0
0
0
Taxable & NonTaxable Income
-------------$
0 - $ 999
1,000 - 1,999
2,000 - 2,999
3,000 - 3,999
4,000 - 4,999
5,000 - 5,999
6,000 - 7,999
8,000 - 9,999
10,000 - 11,999
12,000 - 13,999
14,000 - 15,999
16,000 - 17,999
18,000 - 19,999
20,000 & Over
16
3
Total
1
0
0
1
1
1
1
1
0
0
0
1
1
1
1
0
1
1
1
1
1
1
1
1
1
1
1
2
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
11
15
14
January 2009
Contd...6
07-JUL-2005 09:35:36 AM
BANNER University
6
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------PART VI, SECTION A: DISTRIBUTION OF PROGRAM RECIPIENTS AND EXPENDITURES BY TYPE OF STUDENT (2004-2005 Financial Aid Year)
-----------------------------------------------------------------------------------------------------------------------Tax & Untax Inc
Category/Stud Type
------------------
<--Fed. Perk Loan--->
Recipients
Funds
---------------------
<-------FSEOG------->
Recipients
Funds
---------------------
<---------FWS------->
Recipients
Funds
---------------------
Summary
Recipients
----------
Ungrad. Dependent
----------------$
0
6,000
12,000
24,000
30,000
42,000
60,000
-$ 5,999
- 11,999
- 23,999
- 29,999
- 41,999
- 59,999
& Over
0
1
2
1
1
1
1
0
500
1000
500
500
1000
1000
0
1
2
1
1
1
1
0
1000
1250
1000
1000
1000
1000
0
2
3
1
1
1
1
0
2500
3500
1000
1000
1000
1000
0
2
3
1
1
1
1
1
1
1
1
1
1
1
1000
1000
1000
1000
1000
1000
1000
1
1
1
1
2
2
1
1000
1000
1000
1000
1600
1600
1000
3
4
1
1
3
2
1
4000
5500
1000
1000
4000
1750
1000
3
4
1
1
3
2
1
1
1000
-NA-
-NA-
1
1000
1
15
12500
16
14450
25
29250
25
1
3
500
2000
1
3
750
2750
5
4
7000
4500
5
4
Ungrad. Independent
------------------$
0
2,000
4,000
8,000
12,000
16,000
20,000
&
$1,999
3,999
7,999
11,999
15,999
19,999
Over
Graduate/Professional
T O T A L
Total Less than Full time
Total Automatic Zero EFC
18-247
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Contd...7
07-JUL-2005 09:35:36 AM
BANNER University
7
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------ADDENDUM I. PART-TIME STUDENT DETAIL
------------------------------------Name
FISAP
AUTO
DEP
LEVEL
FULL
AID
AID
INCOME
0 EFC
TIME
FUND
AMT
-----------------------------------------------|-------------|-------|------|------------|---------|---------|---------------------Ede05167, Xxxxxxxxx A.
208000167
|
16000
|
N
| D
|
UWO
|
N
|
|
|
|
|
|
|
|
|
Ede05169, Xxxxxxxxx A.
208000179
|
15001
|
Y
| D
|
UW
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
FISAPTEST, DEP3 T.
236222223
|
20000
|
Y
| D
|
UWO
|
N
| FPERK |
500.00
|
|
|
|
|
| FSEOG |
750.00
|
|
|
|
|
|
FWS |
1000.00
|
|
|
|
|
|
|
FISAPTest, Grad01 G.
236222241
|
16000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
FISAPTest, Grad09 G.
236222249
|
3000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
FISAPTest, Grad10 G.
236222250
|
2000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
TESTFisap, Grad02 G.
236222242
|
14000
|
N
| I
|
G
|
N
|
|
|
|
|
|
|
|
|
Testc, Brent P.
200405102
|
14500
|
N
| I
|
UWO
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Christopher I.
200405103
|
2100
|
N
| I
|
UWO
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, David M.
200405104
|
900
|
N
| I
|
UWO
|
N
|
FWS |
1500.00
|
|
|
|
|
|
|
Testc, Efram
200405131
|
1000
|
N
| I
|
UW
|
N
|
|
|
|
|
|
|
|
|
Testc, Eleanora M.
200405105
|
6000
|
N
| D
|
UWO
|
N
|
|
|
|
|
|
|
|
|
18-248
ID
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Contd...8
07-JUL-2005 09:35:36 AM
BANNER University
8
Aid Year: 0405
FISAP REPORT
RORFS05
-----------------------------------------------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name............................:RORFS05(7.2.1)
One up Number...........................:52070
Aid Year Code...........................:0405
Create/Print Summary/Detail/Both........:B
FPERK Paid or Offered Amount............:P
FSEOG Paid or Offered Amount............:P
FWS Paid or Offered Amount..............:O
Billing or Adjusted Hours...............:A
Sort Order selected.....................:N
Application Code........................:FINAID
Selection ID............................:TEST3
Creator ID............................. :WWOMACK
User ID.............................
:WWOMACK
Undergraduate Level Code 1..............:UG
FT Load for UG Code 1...................:12
Graduate Level Code 1...................:GR
FT Load for Grad Code 1.................:9
Number of lines per page................:55
Log file name .../export/home/wwomack/jobsub/rorfs05_52070.lis
Student Records Selected................:59
Students with no Aid Amounts............:34
Total pages Printed.....................:8
UWO - Undergraduate student WITHOUT prior baccalaureate or first professional degree
UW
- Undergraduate student WITH prior baccalaureate or first professional degree
G
- Graduate student
*
- Locked Record
****** END OF REPORT ******
18-249
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
RORFSxx_yyyyy.log File
07-JUL-2005 09:35:30 AM
BANNER University
** Create FISAP records process completed **
** Printing FISAP report completed **
** FISAP Program Complete **
-------CONTROL SUMMARY
--------------Program Name............................:RORFS05(7.2.1)
One up Number...........................:52070
Aid Year Code...........................:0405
Create/Print Summary/Detail/Both........:B
FPERK Paid or Offered Amount............:P
FSEOG Paid or Offered Amount............:P
FWS Paid or Offered Amount..............:O
Billing or Adjusted Hours...............:A
Sort Order selected.....................:N
Application Code........................:FINAID
Selection ID............................:TEST3
Creator ID............................. :WWOMACK
User ID.............................
:WWOMACK
Undergraduate Level Code 1..............:UG
FT Load for UG Code 1...................:12
Graduate Level Code 1...................:GR
FT Load for Grad Code 1.................:9
Number of lines per page................:55
Log file name .../export/home/jobsub/rorfs05_52070.log
Total Student Records Read..............:59
Total Student Records Created...........:59
Total pages Printed.....................:1
****** END OF REPORT ******
Connected.
Connected.
18-250
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Grade Exception Report (RORGRDE)
This report provides a report of courses for a student which are gradable, based on the registration status but have
not been rolled to Academic History. This assists you in identifying courses which have not been completed due to
an extension request for an Open Learning course or courses extending past normal term grade roll processing
when determining Satisfactory Academic Progress (SAP).
Description
There are two types of courses which are identified by this report: (1) Courses for which no grade has been
assigned, and (2) Courses which have been graded but have not been rolled to Academic History.
This report requires a valid, active Aid Year and a valid Term Code.
Parameters
Name
Required?
Description
Values
Aid Year
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Term Code
Yes
Enter the Term Code.
Grade Exceptions to
Report
Yes
Select the courses to include.
Courses to Report
Sort Sequence Indicator
18-251
No
Yes
Enter the courses to report.
Enter the sort sequence.
Application ID
No
General area for which the selection ID was defined.
Selection ID
No
Code that identifies the sub-population to work with.
Banner Financial Aid 8.3
User Guide
Reports and Processes
B
Both - not rolled and not graded
(default)
N
Courses with No Grade
R
Graded not in Academic History
A
All Courses - (default)
F
Financial Aid Eligible Courses
Only
I
ID
N
Name (default)
January 2009
Parameters (cont) Name
Required?
Description
Values
Creator ID
No
The ID of the person creating the sub-population
rules.
User ID
No
The ID of the person using the sub-population rules.
Grade Exception Report Sample
14-MAY-2003 01:53 PM
AID YEAR: 0203
TERM CODE: 200320
SunGard Higher Education Development
Financial Aid Grade Exception Report
Name
Laker, Mary
Part of CRN Course
Term
Number
1
10006 243
1
10020 10
10
10024 301
ID
511000022
Subj
BIOL
ANTH
COMP
Name
Nelson, Lindy
Part of CRN Course
Term
Number
1
10006 243
1
10020 10
1
10038 20
Subj
BIOL
ANTH
MATH
18-252
ID
511000001
Subj
MGMT
Credit
Hours
4.000
3.000
3.000
Billing
Hours
4.000
3.000
3.000
Excluded
From FA
N
N
N
End
Grade
Date
Code
30-APR-2003
30-APR-2003
B
30-APR-2003
Credit
Hours
4.000
3.000
3.000
Billing
Hours
4.000
3.000
3.000
Excluded
From FA
N
N
Y
End
Grade
Date
Code
30-APR-2003
AAA
Credit
Hours
3.000
Billing
Hours
3.000
Excluded
From FA
N
Student Level
UG
Reg.
Status
Course
Start
Stat
Date
Level
Date
RE
25-APR-2003
UG
01-JAN-2003
Banner Financial Aid 8.3
User Guide
Reports and Processes
End
Grade
Date
Code
30-APR-2003
C
30-APR-2003
15-FEB-2003
Student Level
01
Reg.
Status
Course
Start
Stat
Date
Level
Date
RE
01-MAY-2003
UG
01-JAN-2003
RE
01-MAY-2003
UG
01-JAN-2003
RE
01-MAY-2003
UG
01-JAN-2003
Name
Thompson, Sue
Part of CRN Course
Term
Number
1
10042 301
Student Level
UG
Reg.
Status
Course
Start
Stat
Date
Level
Date
RE
01-MAY-2003
UG
01-JAN-2003
RE
01-MAY-2003
UG
01-JAN-2003
RE
01-MAY-2003
UG
01-JAN-2003
ID
511000024
PAGE 1
RORGRDE
January 2009
Automatic Group Assignment Process (RORGRPS)
The Automatic Group Assignment Process assigns applicants to the following three types of groups:
Description
• Budgeting groups with the appropriate Applicant Budget Table (RBBABUD) entries and Applicant Budget
Component (RBRACMP) entries
• Tracking groups with the appropriate Applicant Requirements (RRRAREQ) entries
• Packaging groups
You can run this process in batch mode or in online mode. RORGRPS allows you to process a single applicant (in
online mode), to use a previously defined population selection, to process all applicants, or to process only
applicants inWait status. You can assign the applicant or applicants to budgeting groups, tracking groups, or
packaging groups, or any combination of the three group types.
Note
When processing more than one group type, RORGRPS will process the group based on the
order entered for the parameter. For example, if you want to process tracking, budgeting,
packaging groups in that order, you would enter TBP. If you enter BPT for the Group Type
Indicator parameter, RORGRPS will process budgeting first, then packaging, and the tracking
„
group last.
Parameters
Name
Required?
Description
Values
Aid Year
Yes
Enter a valid and active aid year. This parameter is
validated against the Financial Aid Institution Table
(ROBINST).
Aid Year Inquiry form (ROIAIDY)
Group Type Indicator
Yes
Select one or more group types to which applicants
will be assigned. You may enter a combination of
these values to perform a combination of the
grouping processes. If you enter multiple group
types, enter the values without any intervening
characters or spaces (e.g., BPT).
B
Budget groups
P
Packaging groups
T
Tracking groups
Enter a term code to limit processing to records in
the specified term.
Financial Aid Term Code Inquiry
(ROITERM)
Term Code
18-253
Banner Financial Aid 8.3
User Guide
Reports and Processes
No
January 2009
Parameters (cont) Name
Process Indicator
Required?
Description
Values
Yes
You can run this process in batch or in online mode.
The online method allows you to process a single
applicant. Batch mode enables you to process
multiple applicants.
B
Batch
O
Online
Applicant ID
No
Specify the applicant you want to assign to groups
when you set the Process Indicator parameter to O
(Online). This parameter is only used in online mode
and must be left blank if you run the process in batch
mode.
Use All Applicants
Indicator
No
If you select the N option, use the applicants within
the selection ID (if a population selection was
established using parameters 07–10) and all
applicants in Wait status.
Y
Use all applicants that have an
Applicant Status Record
(RORSTAT) for the specified aid
year.
If you select the N option and no population
selection was entered, all applicants in Wait status
are used.
N
Use applicants in a Wait status or
those in the selection ID.
Applicants are scheduled (Wait status) for the batch
grouping process when you enter a B (Batch) in the
Action Indicator field for a tracking, budgeting, or
packaging assignment and save the record on the
Applicant Immediate Process form (ROAIMMP).
18-254
Application ID
No
Application code of the population selection. If you Application Inquiry form (GLIAPPL)
enter a value for this parameter, you must also enter
a value for the Selection ID, Creator ID, and User ID
parameters.
Selection ID
No
Selection ID of the population selection. If you enter
a value for this parameter, you must also enter a
value for the Application ID, Creator ID, and User
ID parameters.
Banner Financial Aid 8.3
User Guide
Reports and Processes
January 2009
Parameters (cont) Name
18-255
Required?
Description
Creator ID
No
The ID of the person that created the population
selection. If you enter a value for this parameter, you
must also enter a value for the Application ID,
Selection ID, and User ID parameters.
User ID
No
The ID of the person using the sub-population rules.
If you enter a value for this parameter, you must also
enter a value for theApplication ID, Selection ID,
and Creator ID parameters.
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
January 2009
Financial Aid High School Data Posting Process (RORHSDP)
This process provides a means to batch post information to the Applicant High School Data table (RORHSDT) for
display on the Applicant High School Data form (ROAHSDT). You may be able to identify students meeting the
various rigorous program requirements with data in the Admissions module of the Banner Student System. By
using Population Selection, you may be able to automate a process that would otherwise be very labor intensive.
You can use this process to load the graduation date and the state of the student's high school graduation from the
Student table (SORHSCH). This process also provides you with the ability to update the code for approved State
Advanced or Honors program, the indicators for Advanced Placement/International Baccalaureate Courses or the
indicator for State Scholars Initiative or Required Courses. However, you should use caution when updating these
fields to ensure that the rigorous program criteria has truly been met.
A population selection is required for use with this process.
Parameters
18-256
Name
Required?
Description
Application Code
Yes
General area for which the selection ID was defined. Application Inquiry form (GLIAPPL)
Selection ID
Yes
Code that identifies the population with which to
work.
Creator ID
Yes
ID of the person who created the population rules.
User ID
Yes
ID of the person who used the population rules.
Update High School
Grad Date
Yes
This parameter determines whether or not you want
to load the student's high school graduation date
from the Student table (SORHSCH).
Banner Financial Aid 8.3
User Guide
Reports and Processes
Values
Population Selection Inquiry form
(GLISLCT)
Valid values are:
Y
Yes, update the student’s high
school graduation date
N
No, do not update the student’s
high school graduation date
(Default)
January 2009
Parameters (cont) Name
Required?
Update State of HS Grad Yes
Update AP/IB Indicator
Update Required
Courses Ind
Update Program of
Study Code
18-257
Banner Financial Aid 8.3
User Guide
Reports and Processes
Yes
Yes
No
Description
Values
This parameter determines whether or not you want
to load the state of the student's high school
graduation from the Student table (SORHSCH).
Valid values are:
This parameter determines whether or not you want
to update the Advanced Placement/International
Baccalaureate Courses indicator to Y (eligible). This
indicator specifies that the student completed the
required number of Advanced Placement or
International Baccalaureate courses and test scores.
This parameter determines whether or not you want
to update the Required Courses Similar to the
State Scholars Initiative field on the Applicant
High School Data form (ROAHSDT) to Y (eligible).
Code to use when updating the State Recognized
Program of Study field on the Applicant High
School Data form (ROAHSDT).
Y
Yes, update the state of the
student’s high school graduation
N
No, do not update the state of the
student’s high school graduation
(Default)
Valid values are:
Y
Yes, update the Advanced
Placement/International
Baccalaureate Courses indicator
to Y (eligible)
N
No, do not update the Advanced
Placement/International
Baccalaureate Courses indicator
to Y (eligible) (Default)
Valid values are:
Y
Yes, update the Required
Courses Similar to the State
Scholars Initiative field to Y
(eligible)
N
No, do not update the Required
Courses Similar to the State
Scholars Initiative field to Y
(eligible) (Default)
State Advanced/Honors Programs
(RPISAHP)
January 2009
Financial Aid High School Data Posting Sample
29-APR-2007 11:52:26 AM
Banner University
PAGE 001
Financial Aid High School Data Posting
RORHSDP
----------------------------------------------------------------------------------------------------------------------------------STUDENT NAME
---------------------------------------
ID
---------
RESULTS
---------------------------------------------
Laird,
Laird,
Laird,
Laird,
Laird,
511060702
511060704
511060706
511060701
511060703
Financial
Financial
Financial
Financial
Financial
Darla
Elizabeth M.
Jim
Marshal H.
Thomas M.
Aid
Aid
Aid
Aid
Aid
High
High
High
High
High
School
School
School
School
School
Data
Data
Data
Data
Data
Updated
Inserted
Updated
Inserted
Updated
29-APR-2007 11:52:26 AM
Banner University
PAGE 002
Financial Aid High School Data Posting
RORHSDP
----------------------------------------------------------------------------------------------------------------------------------CONTROL SUMMARY
--------------Program Name.................................:
Run sequence number..........................:
Application Code.............................:
Selection ID.................................:
Creator ID...................................:
User ID......................................:
Update High School Grad Date.................:
Update State of HS Grad......................:
Update AP/IP Indi