October 2005 Release 7.3 - Prince Mohammad bin Fahd ... Early Decision release is used by SCT Banner...

What can we help you achieve?

SCT Banner Financial Aid Release Guide

October 2005Release 7.3.1

Confidential Business Information

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

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

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

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

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

Release Guide

Financial Aid System

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

Section 1 CSS PROFILE - Functional . . . . . . . . . . . . . . . . . . . . . . 11

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

The 2006–2007 PROFILE Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

New Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

2006–2007 Need Analysis Processing (RNAPR07) . . . . . . . . . . . . . . . . . . . . 122006–2007 Need Analysis Supplemental Form (RNASU07) . . . . . . . . . . . . . . . 14

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2005–2006 INAS Global Policy Options Rules Form (RNRGL06) . . . . . . . . . . . . 15Calculated Need Analysis Detail Inquiry (RNINAIQ) . . . . . . . . . . . . . . . . . . . 19ROQRPLS.PLL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

New Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2006–2007 Applicant Processing (*RESAPPL07) . . . . . . . . . . . . . . . . . . . . . 202006–2007 Need Analysis (*RESNEED07) . . . . . . . . . . . . . . . . . . . . . . . . 20

Changed Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Applicant Processing (*RESAPPL). . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Need Analysis (*RESNEED). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

New Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

2006–2007 Financial Aid CSS Data Load Part 1 (RCBCT07) . . . . . . . . . . . . . . . 212006–2007 Financial Aid Data Load Part 3 (RCRTP07). . . . . . . . . . . . . . . . . . 23

Changed Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Need Analysis Logging Report (RLRLOGG.PC) . . . . . . . . . . . . . . . . . . . . . . 24

3

Table of Contents

Section 2 INAS IM/EFM - Functional . . . . . . . . . . . . . . . . . . . . . . 25

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

2006–2007 Applicant Override Form (RNAOV07) . . . . . . . . . . . . . . . . . . . . 252006–2007 INAS Global Policy Options Rules Form (RNRGL07) . . . . . . . . . . . . 26

New/Changed Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

New Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

2006–2007 Need Analysis Calculation Process (INAS) (RNEIN07) . . . . . . . . . . . . 26

Section 3 Loan Changes - Functional . . . . . . . . . . . . . . . . . . . . . . 27

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Use of NSLDS Data within SCT Banner. . . . . . . . . . . . . . . . . . . . . . . . . . 27

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Packaging Options (RPROPTS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Loan Application (RPALAPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Electronic Loan Application (RPAELAP) . . . . . . . . . . . . . . . . . . . . . . . . . 29


FA New Year Roll Process (ROPROLL) . . . . . . . . . . . . . . . . . . . . . . . . . . 29Electronic Loan Application (RPRELAP) . . . . . . . . . . . . . . . . . . . . . . . . . 29Direct Loan Record Creation (RPRLORC) . . . . . . . . . . . . . . . . . . . . . . . . 30UVARTN. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30UVDRTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Section 4 Applicant Requirements API - Functional . . . . . . . . . . . 33

Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

SCT Banner APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33New Applicant Requirements Business Process API . . . . . . . . . . . . . . . . . . . 33New Business Entity API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34New RRKAREQ Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Group Assignment Enhancements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Enhanced Exit Interview Requirements Process . . . . . . . . . . . . . . . . . . . . . 36Enhanced Tracking Letter Indicator Functionality . . . . . . . . . . . . . . . . . . . . 37Enhanced Processing for “Required Once” Requirements . . . . . . . . . . . . . . . . 39RBBABUD, RBRACMP, and RRRAREQ Table Logging Enhancement . . . . . . . . . . . 42

Financial Aid Release 7.3.1 October 20054 Release Guide Confidential

Table of Contents

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Applicant Pell Grant (ROAPELL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Applicant Summary (ROASMRY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Package Maintenance (RPAAPMT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Award Maintenance (RPAAWRD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Electronic Loan Application (RPAELAP) . . . . . . . . . . . . . . . . . . . . . . . . . 44Loan Application (RPALAPP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Direct Loan Origination (RPALORG). . . . . . . . . . . . . . . . . . . . . . . . . . . 44Applicant Requirements (RRAAREQ) . . . . . . . . . . . . . . . . . . . . . . . . . . 44Applicant Requirements Mass Entry (RRAMASS) . . . . . . . . . . . . . . . . . . . . . 46Requirements Tracking Validation (RTVTREQ) . . . . . . . . . . . . . . . . . . . . . . 46Requirements Tracking Status Validation (RTVTRST) . . . . . . . . . . . . . . . . . . . 47

New Reports and Processes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Automatic Group Assignment Process (RORGRPS) . . . . . . . . . . . . . . . . . . . 48


2005–2006 Financial Aid Dataload Part 3 (RCRTP06.pc) . . . . . . . . . . . . . . . . 50Award/Tracking Letter Indicator Reset Process (RLRLETR.pc). . . . . . . . . . . . . . . 51Batch Posting Process (RORBPST.pc). . . . . . . . . . . . . . . . . . . . . . . . . . . 51Disbursement Process (RPEDISB.pco) . . . . . . . . . . . . . . . . . . . . . . . . . . 51Packaging Process (RPEPCKG.pco) . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Packaging Process (RPEPELL.pco) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Packaging Initialization Process (RPEPINT.pco) . . . . . . . . . . . . . . . . . . . . . 51Award Cancellation Process Report (RPRCNCL.pc) . . . . . . . . . . . . . . . . . . . 522005–2006 Direct Loan Upload (RPRDU06.pc) . . . . . . . . . . . . . . . . . . . . . 52UAARTN COBOL Copybook . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Exit Interview Requirements Process (RRREXIT) . . . . . . . . . . . . . . . . . . . . . 52Financial Aid Transcript Requirements (RSRPCOL.pc) . . . . . . . . . . . . . . . . . . 57Applicant Requirements Report (RRRAREQ.pc) . . . . . . . . . . . . . . . . . . . . . 57

Obsolete Reports and Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Section 5 Miscellaneous Validation Methodology - Functional . . . 61

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Dependency Status Selection Simplified . . . . . . . . . . . . . . . . . . . . . . . . . 62Aid Year-Specific Need Analysis Result Form . . . . . . . . . . . . . . . . . . . . . . 62

New Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Miscellaneous Validation Rules Inquiry (ROIMVAL) . . . . . . . . . . . . . . . . . . . 632006–2007 Need Analysis Result Form (RNARS07) . . . . . . . . . . . . . . . . . . . 64

Changed Forms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Forms Using Miscellaneous Validation . . . . . . . . . . . . . . . . . . . . . . . . . 65Forms with Navigation Changes for RNARS07 . . . . . . . . . . . . . . . . . . . . . . 66

October 2005 FinancialAid Release 7.3.1Confidential Release Guide 5

Table of Contents

Need Analysis Result Form (RNARSLT) . . . . . . . . . . . . . . . . . . . . . . . . . . 67Applicant Status Form (ROASTAT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Package Maintenance Form (RPAAPMT) and Award Maintenance Form (RPAAWRD) . . 67

Changed Menus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Financial Aid Common Functions Control (*RESCOMNCM) . . . . . . . . . . . . . . . 68Menu Changes for RNARS07 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68


2006–2007 FA CSS Dataload Part 1 (RCBCT07) . . . . . . . . . . . . . . . . . . . . . 68The Cal MIS Extract (RERCALX) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Financial Aid Transcript (RHRTRAN) . . . . . . . . . . . . . . . . . . . . . . . . . . . 682006–2007 Needs Analysis Process (RNEIN07) . . . . . . . . . . . . . . . . . . . . . 69Applicant Requirements Report (RRRAREQ) . . . . . . . . . . . . . . . . . . . . . . . 69

Section 6 CSS PROFILE - Technical . . . . . . . . . . . . . . . . . . . . . . . 71

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Financial Aid Application Table, Part 1, Temporary Table (RCRTMP1) . . . . . . . . . . 71Financial Aid Application Table, Part 1, Permanent Table (RCRAPP1) . . . . . . . . . . 71Financial Aid Application Log Table, Part 1 (RLRAPP1). . . . . . . . . . . . . . . . . . 72Financial Aid Application Table, Part 4, Temporary Table (RCRTMP4) . . . . . . . . . . 72Financial Aid Application Table, Part 4, Permanent Table (RCRAPP4) . . . . . . . . . . 72Financial Aid Application Log Table, Part 4 (RLRAPP4). . . . . . . . . . . . . . . . . . 73Additional CSS PROFILE Data Table (RCRTMP5). . . . . . . . . . . . . . . . . . . . . 73Additional CSS PROFILE Data Table (RCRIMP1) . . . . . . . . . . . . . . . . . . . . . 73Logging Additional CSS PROFILE Data Table (RLRIMP1) . . . . . . . . . . . . . . . . . 73Pell Payment Schedule Table (RORPELL) . . . . . . . . . . . . . . . . . . . . . . . . . 73Alternate Pell Payment Schedule Table (RORAPEL). . . . . . . . . . . . . . . . . . . . 73Federal Rules Inquiry Table (RPRFEDR) . . . . . . . . . . . . . . . . . . . . . . . . . 74Data Log Rules Data (RORDATA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Logging Rules Table Data (RORDVAL) . . . . . . . . . . . . . . . . . . . . . . . . . . 74

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

New Banner Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

2006–2007 Admissions Applications View (ROVAD07) . . . . . . . . . . . . . . . . . 762006–2007 Current Year Only Admissions Applications View (ROVAM07) . . . . . . . 762006–2007 Admissions Application View, Including Students without

Admissions Decisions (ROVA207) . . . . . . . . . . . . . . . . . . . . . . . . . . . 762006–2007 Admissions Application View, Current Year Only

Including Students without Admissions Decisions (ROVAY07) . . . . . . . . . . . . . 762006–2007 Max Term SAP Status View (ROVSA07) . . . . . . . . . . . . . . . . . . . 762006–2007 Aid Year Specific Student View (ROVST07) . . . . . . . . . . . . . . . . . 76


Table of Contents

Section 7 INAS IM/EFM - Technical. . . . . . . . . . . . . . . . . . . . . . . 77

New Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

RINSGL07.SQL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Section 8 Applicant Requirements API - Technical . . . . . . . . . . . . 89

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Financial Aid Applicant Requirements Table (RRRAREQ) . . . . . . . . . . . . . . . . 89Tracking Requirements Validation Table (RTVTREQ) . . . . . . . . . . . . . . . . . . . 89Tracking Requirements Status Validation Table (RTVTRST) . . . . . . . . . . . . . . . . 90

New Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Applicant Requirements API Packages . . . . . . . . . . . . . . . . . . . . . . . . . . 90RRKAREQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Changed Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

RPKAWDL. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92RPKAWIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92RPKLOAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92BWRKACPT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Parameter Validation (ROKPVAL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92

Obsolete Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

New Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

RT_RBBABUD_LOG_INSUPDDTL . . . . . . . . . . . . . . . . . . . . . . . . . . . 93RT_RBRACMP_LOG_INSUPDDTL . . . . . . . . . . . . . . . . . . . . . . . . . . . 94RT_RRRAREQ_LOG_INSUPDDTL. . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Section 9 Miscellaneous Validation Methodology - Technical . . . . 97

Changed Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Miscellaneous Validation Rules Table (RORMVAL) . . . . . . . . . . . . . . . . . . . 97

New Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

RB_RORMVAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Changed Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

ROKSUMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

October 2005 FinancialAid Release 7.3.1Confidential Release Guide 7

Table of Contents

Changed Libraries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Financial Aid Object Library (ROQOLIB) . . . . . . . . . . . . . . . . . . . . . . . . 100Financial Aid PL/SQL Library (ROQRPLS) . . . . . . . . . . . . . . . . . . . . . . . . 101

Changed Form. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Financial Aid Global Establishment Form (ROQMENU) . . . . . . . . . . . . . . . . . 101

Section 10 Miscellaneous Enhancements . . . . . . . . . . . . . . . . . . . 103

Class Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Year in College . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Section 11 Problem Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . 105

Exit Interview Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Group Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Miscellaneous Problem Resolutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Appendix A Seed Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

Required Data for Miscellaneous Validation Metholology . . . . . . . . . . . . . . 111


Introduction

Introduction

This release guide documents SCT Banner® enhancements and modifications for Release 7.3.1.

CSS PROFILE

Release 7.3.1 includes updates to SCT Banner for CSS’s PROFILE® service for aid year 2006–2007. These changes are discussed in two sections, one with a functional focus and one with a technical focus.

INAS IM/EFM

Release 7.3.1 includes updates to SCT Banner for CSS’s Institutional Need Analysis System (INAS) for aid year 2006–2007. INAS calculates Expected Family Contribution (EFC) using both Institutional Methodology (IM) and Estimated Federal Methodology (EFM). These changes are discussed in two sections, one with a functional focus and one with a technical focus.

Loan Changes

This section discusses changes to U.S. Federal loan processing for determining default and overpayment status when the loan origination is created.

Applicant Requirements API

An Applicant Requirements API has been introduced, and processes for Automatic Group Assignment and Exit Interview Requirements have been rewritten. These changes are discussed in two sections, one with a functional focus and one with a technical focus.

Miscellaneous Validation Methodology

A new methodology for field validation has been implemented in many Financial Aid forms, using the Miscellaneous Validation Table to store valid values rather than hard-coding the validation in forms. In connection with this change, the Need Analysis Result Form has been made aid year-specific, starting with the 2006–2007 aid year. These changes are discussed in two sections, one with a functional focus and one with a technical focus. In addition, an appendix lists the Miscellaneous Validation Table data delivered with this release.

Miscellaneous Enhancements

This section discusses enhancements to Class Code values and Year in College processing.

Problem Resolutions

This section lists problem resolutions since the last release.

October 2005 Financial Aid Release 7.3.1Confidential Release Guide 9

Prerequisites

Prerequisites

Before you install Financial Aid Release 7.3.1, you must install Release 7.3.

Note: For customers who use SCT Banner Financial Aid in connection with SCT Banner XtenderSolutions (BXS), please note that changes in Requirements Tracking functionality introduced with Release 7.3.1 are incompatible with previous versions of BXS. BXS Release 7.0.1.1 will be available shortly after Financial Aid Release 7.3.1 and will resolve this issue. Once BXS Release 7.0.1.1 is available, you should install it before you install Financial Aid Release 7.3.1.


Section 1 CSS PROFILE - FunctionalOverview

Section 1 CSS PROFILE - Functional

Overview

The Early Decision release is used by SCT Banner clients to process and package estimated financial aid to students who apply for early admission. The College Scholarship Service (CSS) provides an early financial aid processing service called the CSS PROFILE®. Using PROFILE, students complete a CSS financial aid application/family financial statement online and submit to CSS for processing. CSS processes the data and delivers it electronically to schools for use with their processing systems.

PROFILE data is used by CSS’ INAS (Institutional Need Analysis System) software to calculate an Institutional Methodology (IM) EFC (Estimated Federal Contribution) and an Estimated Federal Methodology (EFM) EFC which schools use to determine institutional financial aid eligibility. SunGard SCT contracts with CSS to include the INAS software in SCT Banner.

IM-related SCT Banner forms and processes have been modified to incorporate CSS changes and accommodate normal updates for the new 2006–2007 aid year.

Note: Functional and technical cross-validation documents for CSS PROFILE to SCT Banner are available on the ActionWeb. See 2006-2007 css profile functional.xls and 2006-2007 css technical.xls.

Prerequisites

SCT Banner Financial Aid clients who subscribe to CSS’ PROFILE service import the information into the SCT Banner database through our data load programs.

SCT Banner clients who do not receive PROFILE data from CSS can still use the INAS software. Those clients populate the PROFILE data manually or by copying data from the FM (Federal Methodology) record in order to calculate an IM EFC. However, because data from the FM record will not be available until the Winter Regulatory Release of SCT Banner, the copy from FM to IM function will not be activated for this release.


Section 1 CSS PROFILE - Functional The 2006–2007 PROFILE Record

The 2006–2007 PROFILE Record

For aid year 2006–2007, the following changes were made to the PROFILE record.

• The size of the fields for Tax Form Used (for both student and parent) has been expanded to two characters, and new valid values were added.

• The size of the IM Base Custodial Parent Percent of Income field has been expanded to three.

• Two new fields were added: Fee Waiver Indicator and Parent Remarriage Date

• Valid values for Household Size and Number in College (for both student and parent) have been changed.

• Several fields have new start/end positions.

• Effective with 2006–2007, a question mark (?) is no longer accepted as a valid field value.

New Forms

New IM-related forms have been created for the 2006–2007 aid year. For the most part, these are copies of the corresponding forms from the 2005–2006 aid year. The differences between these new forms and the 2005–2006 forms are highlighted here.

2006–2007 Need Analysis Processing (RNAPR07)

This form, which displays and processes applicant FM and IM data for a specified aid year and lets you view data and process data changes for both calculations side-by-side, has been updated and modified for the 2006–2007 year.

Note: Because 2006–2007 FM data will not be available until January 2006 and because the SCT Banner Financial Aid forms to maintain FM data will not be delivered until the January 2006 release, the FM side of RNAPR07 has been disabled. It will be enabled with the January 2006 release.

Note: The link for the Need Analysis form on the Options menu is inactive. It will be activated with the January 2006 release. The Copy FM to IM feature is also inactive until the January 2006 release.


Section 1 CSS PROFILE - FunctionalNew Forms

Main Window

For the following fields, the range of valid values has changed.

• Number in Family for IM Parent accepts values from 02–99.

• Number in Family for IM Student accepts values from 01–99.

• Number in College for both IM Parent and IM Student accepts values from 01–99.

Marital Status for IM Parent has a new list of valid values. The field can be left blank, or one of the following can be selected: 1 Single, 2 Married, 3 Remarried, 4 Separated, 5 Divorced, or 6 Widowed.

Income and Benefits

1040 Type for both student and parent has an expanded list of valid values. The field can be left blank, or one of the following can be selected:

• 01 Estimated 1040

• 02 Estimated 1040A

• 03 Estimated 1040EZ

• 04 Estimated Canadian

• 05 Estimated Puerto Rican

• 06 Estimated Other Non-U.S. Return

• 07 Completed 1040

• 08 Completed 1040A

• 09 Completed 1040EZ

• 10 Completed Canadian

• 11 Completed Puerto Rican

• 12 Completed Other Non-U.S. Return

• 13 Will not file

Parents’ Expected Income and Expenses

The field previously labeled Who Established the Trusts is now labeled Trusts Established By.


Section 1 CSS PROFILE - Functional New Forms

2006–2007 Need Analysis Supplemental Form (RNASU07)

Note: The link for the Need Analysis form on the Options menu is inactive. It will be activated with the January 2006 release.

Main Window

The following fields were added to this window.

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

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

Parents’ Marital Status

Marital status of the student’s parents. Valid values are blank or any of the following: 1 Single, 2 Married, 3 Remarried, 4 Separated, 5 Divorced, 6 Widowed.

Remarriage Date

Parent’s remarriage date, in DD-MON-YYYY format.


Section 1 CSS PROFILE - FunctionalChanged Forms

Additional Supplemental Window

The Family Members Att field has a new list of valid values. The field can be left blank, or one of the following can be selected: 0 No, Will not Attend; 1 Yes, Full Time; 2 Yes, Half Time.

The following fields were added to this window.

Changed Forms

2005–2006 INAS Global Policy Options Rules Form (RNRGL06)

In response to RPE 47378, the INAS Global Policy Options Rules Form has been enhanced to allow users to access and update INAS options for comparing FAFSA and PROFILE information.

Comparison Controls for FAFSA and PROFILE Information

This new window has been added to the RNRGL06 form to allow you to view and update INAS global options for comparing FAFSA information with PROFILE

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

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

Fee Waiver Indicates if the PROFILE fee has been waived. Enter 1 if the fee has been waived, 2 if not.


Section 1 CSS PROFILE - Functional Changed Forms

information. One set of fields, under the heading Comparisons not using tolerances, allows you to make yes-or-no choices (by entering Y or N) about whether specific items will be compared between the two sets of data.

Other fields, under the heading Comparisons using tolerances, allow you to enter a tolerance value for comparison of FAFSA and PROFILE data items. The tolerance value is included in the calculation when determining whether a discrepancy between FAFSA and PROFILE data is large enough to be reported. Small discrepancies, below the threshold established by the tolerance value, are ignored. A value of 00000 means that any discrepancy is reported; the maximum value of 99999 means that the comparison is not made and no discrepancies are reported.

Comparisons Not Using Tolerances

These new fields indicate whether comparisons will be made between the indicated FAFSA and PROFILE data. Valid values are Y (yes, compare this item) and N (no, do not compare this item).

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

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

Marital Status (Parent)

Indicates whether the parents’ marital status will be checked for discrepancies between FAFSA and PROFILE.

Marital Status (Student)

Indicates whether the student’s marital status will be checked for discrepancies between FAFSA and PROFILE.

State of Residence (Parent)

Indicates whether the parents’ state of residence will be checked for discrepancies between FAFSA and PROFILE.



Comparisons Using Tolerances

These new fields establish tolerances for comparisons between the indicated FAFSA and PROFILE data. Valid values are 00000–99999.

State of Residence (Student)

Indicates whether the student’s state of residence will be checked for discrepancies between FAFSA and PROFILE.

1040 Type (Parent)

Indicates whether the parents’ type of 1040 tax form will be checked for discrepancies between FAFSA and PROFILE.

1040 Type (Student)

Indicates whether the student’s type of 1040 tax form will be checked for discrepancies between FAFSA and PROFILE.

Year in College (Student)

Indicates whether the student’s year in college will be checked for discrepancies between FAFSA and PROFILE.

Ward of Court (Student)

Indicates whether the student’s status as a ward of court will be checked for discrepancies between FAFSA and PROFILE.

Has Legal Dependants (Student)

Indicates whether the student’s claim of having legal dependants will be checked for discrepancies between FAFSA and PROFILE.

Citizenship (Student)

Indicates whether the student’s citizenship status will be checked for discrepancies between FAFSA and PROFILE.

Veteran (Student)

Indicates whether the student’s veteran status will be checked for discrepancies between FAFSA and PROFILE.

Date of Birth (Student)

Indicates whether the student’s date of birth will be checked for discrepancies between FAFSA and PROFILE.

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

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

Number in College (Parent)

Tolerance value used when comparing the parents’ number of family members in college between FAFSA and PROFILE.

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

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


Section 1 CSS PROFILE - Functional Changed Forms

Number in College (Student)

Tolerance value used when comparing the student’s number of family members in college between FAFSA and PROFILE.

Family Size (Parent)

Tolerance value used when comparing the parents’ family size between FAFSA and PROFILE.

Family Size (Student)

Tolerance value used when comparing the student’s family size between FAFSA and PROFILE.

Number of Exemptions (Parent)

Tolerance value used when comparing the parents’ number of tax exemptions between FAFSA and PROFILE.

Number of Exemptions (Student)

Tolerance value used when comparing the student’s number of tax exemptions between FAFSA and PROFILE.

Reported IRS Adjusted Gross Income (Parent)

Tolerance value used when comparing the parents’ reported IRS adjusted gross income between FAFSA and PROFILE.

Reported IRS Adjusted Gross Income (Student)

Tolerance value used when comparing the student’s reported IRS adjusted gross income between FAFSA and PROFILE.

Father/Student Wages (Parent)

Tolerance value used when comparing the father’s wages between FAFSA and PROFILE.

Father/Student Wages (Student)

Tolerance value used when comparing the student’s wages between FAFSA and PROFILE.

Mother/Spouse Wages (Parent)

Tolerance value used when comparing the mother’s wages between FAFSA and PROFILE.

Mother/Spouse Wages (Student)

Tolerance value used when comparing the student’s spouse’s wages between FAFSA and PROFILE.

Cash/Savings/Checking (Parent)

Tolerance value used when comparing the parents’ cash between FAFSA and PROFILE.

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

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



Calculated Need Analysis Detail Inquiry (RNINAIQ)

The Percentage of Income field for IM Custodial Parent has been expanded from two to three characters. This change allows a value of 100 (100%) to be viewed.

Cash/Savings/Checking (Student)

Tolerance value used when comparing the student’s cash between FAFSA and PROFILE.

Investments Net Worth (Parent)

Tolerance value used when comparing the net worth of parents’ investments between FAFSA and PROFILE.

Investments Net Worth (Student)

Tolerance value used when comparing the net worth of student’s investments between FAFSA and PROFILE.

Business and Farm Value (Parent)

Tolerance value used when comparing the value of parents’ business and farm between FAFSA and PROFILE.

Business and Farm Value (Student)

Tolerance value used when comparing the net worth of student’s business and farm between FAFSA and PROFILE.

Age of Oldest Parent (Student)

Tolerance value used when comparing the age of the student’s oldest parent between FAFSA and PROFILE.

Student’s Veteran Benefits (Student)

Tolerance value used when comparing student’s veteran benefits between FAFSA and PROFILE.

Number of Months of Benefits

Tolerance value used when comparing the number of months of the student’s veteran benefits between FAFSA and PROFILE

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

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


Section 1 CSS PROFILE - Functional New Menus

ROQRPLS.PLL

This Oracle Forms Library module was updated with new 2006–2007 CSS PROFILE columns used by RNAPR07.

• The R$_KEEP_SIM_IM_APP1 and R$_CREATE_SIM_IM_APP1 program units have added the new RCRAPP1_PAR_REMARRIAGE_DATE column.

• The R$_KEEP_SIM_IM_APP4 and R$_CREATE_SIM_IM_APP4 program units have added the new RCRAPP4_FEE_WAIVER_IND column.

New Menus

2006–2007 Applicant Processing (*RESAPPL07)

The 2006–2007 Applicant Processing menu has been created as an updated copy of the 2005–2006 Applicant Processing menu.

Note: Forms related to Federal Methodology (FM) will be excluded from this menu for this release. These forms—RNANA07, RNAVR07, and RNASL07—will be added in the January 2006 release.

2006–2007 Need Analysis (*RESNEED07)

The 2006–2007 Need Analysis menu has been created as an updated copy of the 2005–2006 Need Analysis menu.

This new menu includes the year-specific 2006–2007 Need Analysis Result form (RNARS07).

Note: Forms related to Federal Methodology (FM) will be excluded from this menu for this release. These forms—RNANA07, RNIMS07, RNAVR07, and RNASL07—will be added in the January 2006 release.

Changed Menus

Applicant Processing (*RESAPPL)

2006–2007 Applicant Processing (*RESAPPL07) has been added as the first entry in the Applicant Processing menu.


Section 1 CSS PROFILE - FunctionalNew Reports and Processes

Need Analysis (*RESNEED)

2006–2007 Need Analysis(*RESNEED07) has been added as the first entry in the Need Analysis menu.

New Reports and Processes

2006–2007 Financial Aid CSS Data Load Part 1 (RCBCT07)

The new 2006–2007 Financial Aid CSS Data Load Part 1 (RCBCT07) process is an updated copy of the 2005–2006 Financial Aid CSS Data Load Part 1 (RCBCT06) process.

Changes were made to the CSS record layout, requiring changes to the data load process to the temporary tables.

Note: All fields in the CSS Profile record layout are alphanumeric fields, which means that all fields that display numeric data and permit an arithmetic sign are one character longer than the actual amount allowed. For example, if a CSS Profile field is 7 characters and a minus sign is allowed, the maximum number that can be stored is 6 digits, or 999999. The seventh character is for the mathematical sign, thus allowing for -999999. Such fields in the Profile layout are stored as one digit less in the SCT Banner database.

Parameters

Parameter 03, Data Delivery Method, now only accepts the default value of D (Electronic). T (Tape) is no longer a valid entry for parameter 03.

New Fields

The following new CSS fields will be loaded into the Temporary Tables RCRTMP1 and RCRTMP4.

Field # Start Stop Size Record Description Name

Working Storage Name

Temporary Table Column Name

35B 244 244 1 CSSS-FEE-WAIVER-IND

DECL-FEE-WAIVER-IND

RCRTMP4_FEE_WAIVER_IND

86A 563 570 8 CSSS-P-REMARRIAGE-DATE

DECL-PAR-REMARR-DATE

RCRTMP1_PAR_REMARRIAGE_DATE


Section 1 CSS PROFILE - Functional New Reports and Processes

Deleted Fields

The following fields were deleted and replaced by filler. Two of the deleted fields were moved to other locations, renamed, and increased in length:

• The former field 453 is now 463A.

• The former field 457 is now 463B.

Modified Fields

Several fields have changed in length, resulting in new start and stop positions for other fields. The fields now named 463A and 463B are the former fields 453 and 457.




382 2520 2520 1 CSSS-MSG-7 DECL-MSG-7 RCRIMP1_MSG_7

453 2746 2747 2 CSSS-CUST-PAR-BASE-PRCNT-INC

DECL-CUST-PAR-BASE-PRCNT-INC

RCRTMP4_CUST_PAR_BASE_PCT_INC

457 2763 2764 2 CSSS-CUST-PAR-OPT-PRCNT-INC

DECL-CUST-PAR-OPT-PRCNT-INC

RCRTMP5_CUST_PAR_OPT_PCT_INC




36 245 246 2 CSSS-S-TAX-FIG DECL-TAX-FORM-IND

RCRTMP1_TAX_FORM_IND

82A 542 549 8 CSSS-P-SIBLINGS-PRE-TUIT

DECL-C-PAR-SIB-PRE-TUIT

RCRTMP5_PAR_SIB_PRE_TUIT

82B 550 557 8 CSSS-P-STUDENT-PRE-TUIT

DECL-C-PAR-STU-PRE-TUIT

RCRTMP5_PAR_STU_PRE_TUIT

83 558 559 2 CSSS-P-HSLD-SIZE DECL-PAR-FAM-MEMB

RCRTMP1_PAR_FAM_MEMB

84 560 560 1 CSSS-P-NUM-IN-COLL

DECL-PAR-NO-IN-COLL

RCRTMP1_PAR_NO_IN_COLL

85 561 561 1 CSSS-P-PARENTS-IN-COLL

DECL-PAR-PRNT-IN-COLL

RCRTMP5_PAR_PRNT_IN_COLL

86 562 562 1 CSSS-P-MAR-STAT DECL-PAR-MRTL-STATUS

RCRTMP1_PAR_MRTL_STATUS


Section 1 CSS PROFILE - FunctionalNew Reports and Processes

2006–2007 Financial Aid Data Load Part 3 (RCRTP07)

The new 2006–2007 Financial Aid Data Load Part 3(RCRTP07) process is an updated copy of the 2005–2006 Financial Aid Data Load Part 3(RCRTP06) process.

Data Load

Listed below are the new columns and columns with changed length in the updated data load process.

87 571 572 2 CSSS-P-STATE-LEG-RES

DECL-PAR-STAT-CODE-RES

RCRTMP1_PAR_STAT_CODE_RES

88 573 573 1 CSSS-P-NTRL-SEP-DIV

DECL-PAR-NTRL-SEP-DIV

RCRTMP5_PAR_NTRL_SEP_DIV

88A 574 574 1 CSSS-STU-LIVES-WITH

DECL-STU-LIVES-WITH

RCRTMP5_STU_LIVES_WITH

88B 575 575 1 CSSS-STU-MOST-SUPPORT-FROM

DECL-STU-MOST-SUPPORT-FROM

RCRTMP5_STU_MOST_SUPPORT_FROM

121 808 809 2 CSSS-P-TAX-FIG DECL-PAR-TAX-FORM-IND

RCRTMP1_PAR_TAX_FORM_IND

463A 2831 2833 3 CSSS-CUST-PAR-BASE-PRCNT-INC

DECL-CUST-PAR-BASE-PRCNT-INC

RCRTMP4_CUST_PAR_BASE_PCT_INC

463B 2834 2836 3 CSSS-CUST-PAR-OPT-PRCNT-INC

DECL-CUST-PAR-OPT-PRCNT-INC

RCRTMP5_CUST_PAR_OPT_PCT_INC




Temporary Table Column Name Size Permanent Table Column Name Change

RCRTMP1_PAR_REMARRIAGE_DATE 8 RCRAPP1_PAR_REMARRIAGE_DATE New column

RCRTMP1_TAX_FORM_IND 2 RCRAPP1_TAX_FORM_IND Column length changed

RCRTMP1_PAR_TAX_FORM_IND 2 RCRAPP1_PAR_TAX_FORM_IND Column length changed

RCRTMP4_FEE_WAIVER_IND 1 RCRAPP4_FEE_WAIVER_IND New column

RCRTMP4_CUST_PAR_BASE_PCT_INC 3 RCRAPP4_CUST_PAR_BASE_PCT_INC Column length changed


Section 1 CSS PROFILE - Functional Changed Reports and Processes

Discrepancy Report

Two PROFILE fields, RCRAPP1_PAR_TAX_FORM_IND and RCRAPP1_TAX_FORM_IND, have increased in length from one to two bytes. The Discrepancy Report has been modified for the increased length of these fields as part of the data comparison.

Note: The other field that has increased in size (RCRAPP4_CUST_PAR_BASE_PCT_INC) is not included in the discrepancy report. This field appears on the CSS PROFILE record only; therefore, no comparison is done.

Changed Reports and Processes

Need Analysis Logging Report (RLRLOGG.PC)

The Needs Analysis Logging has been modified to accommodate the increased length of the two PROFILE columns, RCRAPP1_PAR_TAX_FORM_IND and RCRAPP1_TAX_FORM_IND.

The new fields listed below have been added to the Need Analysis Logging Report.

• Parent’s Remarriage Date, RCRAPP1_PAR_REMARRIAGE_DATE

• Fee Waiver Indicator, RCRAPP4_FEE_WAIVER_IND


Section 2 INAS IM/EFM - FunctionalOverview

Section 2 INAS IM/EFM - Functional

Overview

The Early Decision release is used by SCT Banner clients to process and package estimated financial aid for students who apply for early admission. The College Scholarship Service (CSS) provides an early financial aid processing service called the CSS PROFILE to assist schools that make decisions on students applying for early admission. Using PROFILE, students complete a financial aid application/family financial statement and send the data to CSS for processing, which is then electronically delivered to schools to use with their processing systems.

This data is processed utilizing the Institutional Methodology (IM) formula through CSS’ Institutional Need Analysis System (INAS®) software. SCT Banner contracts with CSS to include the INAS software in our product. PROFILE data is fed to INAS to calculate an IM EFC (Expected Family Contribution) and an EFM (Estimated U.S. Federal Methodology) EFC. All SCT Banner INAS clients can use the IM formula, whether or not they subscribe to CSS’ PROFILE service, because it is built into the INAS software. All the functions needed to process IM are part of baseline SCT Banner. In order for SCT Banner clients who do not receive PROFILE data from CSS to use IM, the PROFILE data fields in SCT Banner must be populated either manually or by copying data from the FM (Federal Methodology) record. However, data from the FM record is not available until the Winter Release of SCT Banner.

Note: INAS Technical Upgrade #1 for 2006-2007 posted a new data file but did not include any code changes. Financial Aid Release 7.3.1 is current with INAS Technical Upgrade #1.

2006–2007 Applicant Override Form (RNAOV07)

The new 2006–2007 Applicant Override Form (RNAOV07) is an updated copy of the 2005–2006 Applicant Override Form (RNAOV06).

The Applicant Override Form allows you to set processing overrides for individual students, rather than using the global default values. This is necessary to allow INAS to apply specific options for individual students that are different from the global policies.

Note: The link for the Need Analysis form on the Options menu is inactive. It will be activated with the January 2006 release.


Section 2 INAS IM/EFM - Functional New/Changed Menus

2006–2007 INAS Global Policy Options Rules Form (RNRGL07)

The new 2006–2007 INAS Global Policy Options Rules Form (RNRGL07) is an updated copy of the 2005–2006 INAS Global Policy Options Rules Form (RNRGL06).

New/Changed Menus

See “New Menus” and “Changed Menus” in Section 1, “CSS Profile - Functional.”


2006–2007 Need Analysis Calculation Process (INAS) (RNEIN07)

The new 2006–2007 Need Analysis Calculation Process (RNEIN07) is an updated copy of the 2005–2006 Need Analysis Calculation Process (RNEIN06).

For 2006–2007, in response to CSS Data Reporting Layout changes, RNEIN07 has been modified to add the following new fields to the PRO07 copybook:

• Parent Remarriage Date (PR-P-DT-OF-REMARRIAGE)

• Fee Waiver Indicator (PR-FEE-WAIVER)

In addition, the PR-NON-CUS-PC field in PRO07 has changed; it is no longer a signed field.


Section 3 Loan Changes - FunctionalIntroduction

Section 3 Loan Changes - Functional

Introduction

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. SCT Banner still contained logic to examine the FAT table if the option was set to use SCT Banner history. For this reason, a change was made in SCT 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 (RNARS07). 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.

Use of NSLDS Data within SCT Banner

When NSLDS data became available to schools in the EDE data load files many years ago, SCT 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 (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 (RNARS07).


Section 3 Loan Changes - Functional Changed Forms

Changed Forms

Packaging Options (RPROPTS)

The B (Banner) option for the Source of Award History field (RPBOPTS_AWRD_HIST_SRC_IND) was removed beginning with the 2006–2007 aid year. Only N (NSLDS) is a valid option for this field for the 2006–2007 aid year and beyond.

Loan Application (RPALAPP)

Application Data Window

The NSLDS Match field was added to the Application Data Window.

NSLDS Match field (RNASLxx) NSLDS Override Field Must Be (RNARS07)

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

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

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

NSLDS Match (RCRLDS4_MATCH_IND). The NSLDS match from the current NSLDS record for the aid year.


Section 3 Loan Changes - FunctionalChanged Reports and Processes

The following fields were removed from the Application Data Window since this information is no longer populated in the corresponding RCRAPPx Tables. The Document ID field was the MDE ID associated with the Source and was not part of the CSS file so it was removed.

DefaultOwes RefundClass Last LoanTotal UnpaidLast UnpaidInterest RateDocument ID

When you create certification data using the Insert Record function, the Dependency Status will now be determined by RCRAPP2_MODEL_CDE with values of I (Independent) and D (Dependent).

Electronic Loan Application (RPAELAP)

When you create certification data using the Insert Record function, the Dependency Status will now be determined by RCRAPP2_MODEL_CDE with values of I (Independent) and D (Dependent).


FA New Year Roll Process (ROPROLL)

The process was modified to default an N (NSLDS) into the Source of Award History field (RPBOPTS_AWRD_HIST_SRC_IND) beginning with the 2006–2007 aid year.

Electronic Loan Application (RPRELAP)

RPRELAP no longer creates a loan application if a student is in default or owes a refund on U.S. Federal student aid unless an override has been granted. This change only affects U.S. Federal Stafford and PLUS loan borrowers.

An edit was removed that checked for default and overpayment from Financial Aid Transcript tables (RHBTRNS and RHBTINF) for the 2006–2007 aid year and beyond.

An edit was removed that checked for default and overpayment from the Need Analysis tables (RCRAPP1, RCRAPP3, RCRAPP4).


Section 3 Loan Changes - Functional Changed Reports and Processes

The RPRELAP process only uses NSLDS information for validation of default and/or overpayment information.

A check was added to prohibit the creation of a loan application for a Federal loan if the student is in default and/or overpayment and no override has been performed. An error message is written to the output: Student in default and/or overpayment.

The Loan Default field (RPRLAPP_IN_DEFAULT) is updated to N (Not in Default) when a loan application is created if the NSLDS Override field (RORSTAT_NSLDS_OVRD_IND) is D (Default tests) or A (All tests).

The Dependency Status is now be determined by RCRAPP2_MODEL_CDE with values of I (Independent) and D (Dependent).

Direct Loan Record Creation (RPRLORC)

RPRLORC no longer creates a loan application if a student is in default or owes a refund on U.S. Federal student aid unless an override has been granted. This change only affects Federal Stafford and PLUS loan borrowers.

An edit was removed that checked for default and overpayment from Financial Aid Transcript tables (RHBTRNS and RHBTINF) for the 2006–2007 aid year and beyond.

An edit was removed that checked for default and overpayment from the Need Analysis tables (RCRAPP1, RCRAPP3, RCRAPP4).

The RPRLORC process only uses NSLDS information for validation of default and/or overpayment information.

A check was added for the NSLDS_OVRD_IND and NSLDS_MATCH_IND to prohibit the creation of a loan application for a U.S. Federal loan if the student is in default and/or overpayment and no override has been performed. An error message is written to the output: Student in default and/or overpayment.

The Loan Default field (RPRLAPP_IN_DEFAULT) is updated to N (Not in Default) when a loan application is created if the NSLDS Override field (RORSTAT_NSLDS_OVRD_IND) is D (Default tests) or A (All tests).

UVARTN

The UVARTN COBOL copybook was modified to remove prior logic for default processing so that only NSLDS information is checked beginning with the 2006–2007 aid year.

• An edit to check for default and overpayment was removed from the Financial Aid RHBTRNS and RHBTINF transcript tables.

• An edit to check for default and overpayment was removed from the RCRAPP1, RCRAPP3, RCRAPP4 need analysis tables.


Section 3 Loan Changes - FunctionalChanged Reports and Processes

• NSLDS information is used consistently for validation of default and/or overpayment from RCRLDS4.

UVDRTN

The UVDRTN COBOL copybook was modified to remove prior logic for default processing so that only NSLDS information is checked beginning with the 2006–2007 aid year.

• An edit to check for default and overpayment was removed from the Financial Aid RHBTRNS and RHBTINF transcript tables.

• An edit to check for default and overpayment was removed from the RCRAPP1, RCRAPP3, RCRAPP4 need analysis tables.

• NSLDS information is used consistently for validation of default and/or overpayment from RCRLDS4.


Section 3 Loan Changes - Functional Changed Reports and Processes

This page intentionally left blank


Section 4 Applicant Requirements API - FunctionalOverview

Section 4 Applicant Requirements API - Functional

Overview

SCT Banner APIs

Since Release 6.0, SCT Banner has been evolving towards a layered architecture that is accessible through Application Programming Interfaces (APIs). The evolution of the architecture has been designed to minimize the impact on your institution.

The architecture's use of APIs consolidates code, thereby significantly reducing Banner's complexity.

Key Benefits of APIs

• APIs ensure that business logic validations are performed consistently when data is manipulated.

• APIs eliminate duplicate code that had previously been maintained in separate applications.

A Banner Business Entity API provides access to Banner business entities and supports create, update, delete, and read functions.

A Banner business entity is a person, place, or thing that the business process operates on. It is the smallest, most granular grouping of information that a Banner application can change. It is defined by information in one form or one form block.

A Banner Business Process API provides cross-entity business process logic. The API orchestrates a series of steps spanning calls to multiple Banner Business Entity APIs in the context of a single transaction.

New Applicant Requirements Business Process API

A Banner Business Process API is being delivered in this release for the Applicant Requirements Business Entity and associated business logic. The Business Process API supports the following:


Section 4 Applicant Requirements API - Functional Overview

• Creates an applicant requirement.

• Creates an applicant status record stored in the Applicant Status Table (RORSTAT), if one does not already exist.

• Creates a satisfactory academic progress record stored in the Satisfactory Academic Progress Rules Table (RORSAPR), if one does not already exist.

• Creates a mail record stored in the Mail Table (GURMAIL), if one does not already exist.

• Creates an applicant requirement with valid values before it is stored in the Applicant Requirement Table (RRRAREQ).

• Performs summary requirement processing.

• Retrieves an applicant requirement from RRRAREQ.

• Changes an existing applicant requirement.

• Changes the applicant requirement record.


• Removes an applicant requirement while preserving relationship integrity with other business entities in the system.

• Removes the applicant requirement record.


New Business Entity API

This release includes a Banner Business Entity API for the Applicant Requirements Business Entity. This new API supports the following:

• Creates an applicant requirement with valid values before it is stored in the Applicant Requirement Table (RRRAREQ).

• Retrieves an applicant requirement from RRRAREQ.

• Changes an existing applicant requirement while still supporting valid data in the system.

• Removes an applicant requirement while preserving relationship integrity with other business entities in the system.

New RRKAREQ Package

A new package (RRKAREQ) is being delivered to consolidate code and standardize processing in support of the Applicant Requirements Business Entity API (rb_requirement). The new RRKAREQ package will support adding and deleting tracking requirements associated with an award's fund code or with a tracking group code. RRKAREQ will also perform summary requirement processing, including the following:



• Updating all instances of a tracking requirement when the satisfy all indicator (RTVTREQ_SATISFY_ALL_IND) is set on the Requirements Tracking Validation Form (RTVTREQ) when a requirement is satisfied.

• Updating all instances of a tracking requirement when the satisfy once indicator (RTVTREQ_ONCE_IND) is set on the Requirements Tracking Validation Form (RTVTREQ) when a requirement is satisfied.

• Maintains the all requirements complete date (RORSTAT_ALL_REQ_COMP_DATE) on the Applicant Requirements Form (RRAAREQ).

• Maintains the memo requirements complete date (RORSTAT_MEMO_REQ_COMP_DATE).

• Maintains the packaging requirements complete date (RORSTAT_PCKG_REQ_COMP_DATE) on the Applicant Requirements Form (RRAAREQ).

• Maintains the disbursement requirements complete date (RORSTAT_DISB_REQ_COMP_DATE) on the Applicant Requirements Form (RRAAREQ).

• Maintains the request letter indicator (RORSTAT_TRK_LTR_IND) on the Applicant Requirements Form (RRAAREQ).

Since the summary requirement processing is performed by the processes that create, change, or remove applicant requirements, RPE 27354 is satisfied.

Group Assignment Enhancements

The Automatic Grouping Process (ROOAUTO) and the Batch Automated Grouping Process (ROBBGRP) have been replaced by the new Automatic Group Assignment Process (RORGRPS). RORGRPS provides all the functionality of the two prior processes, which have been made obsolete.

The Automatic Group Assignment Process assigns applicants to the following three types of groups:

• 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. This will be accomplished using the rrkareq.p_maintain_group packaged procedure.

• Packaging groups.

The new RORGRPS process resolves the following RPEs and defects.

• The process will commit data to the database after each applicant is processed (RPE 34996).

• The process will total the number of applicants assigned to each group and save the total in RORGDAT_ROWS_SELECTED (RPE 37613).



• A population selection User ID parameter has been added to the new process (RPE 26875).

• Fund-specific Once Only/Satisfy All requirements are now handled correctly (Defect 80916).

• The Tracking Letter Indicator is no longer incorrectly re-checked in certain situations (Defect 85957).

• The new process performs more quickly with large population selections (Defect 103123).

• Correctly formatted output can now be viewed on GJIREVO (Defect 104083).

Enhanced Exit Interview Requirements Process

The Exit Interview Requirements Process (RRREXIT) identifies students who require U.S. Federal loan exit counseling. If a student requires an exit interview, the process also enables you to establish an exit interview requirement code for the student’s tracking record.

For Release 7.3.1 the process has been streamlined to make it simpler and more straightforward to use. A new, expanded set of parameters gives you more flexibility in applying the process to a targeted subset of students.

The new version of the RRREXIT process resolves the following RPEs and defects.

• Transcript information from prior institutions is no longer drawn from the Prior Institution Transcript Award Table (RHRAWRD). All loan history data from other institutions is now drawn from the student’s NSLDS record. This change satisfies RPE 26053.

• Graduates can now be selected by term code, as well as by reference to their graduation date on SHADEGR. This change satisfies RPE 16614.

• The new parameter 13 allows you to select Report only or Report and update. The Report only option allows you to test the outcome of the job parameters before committing updates to the RRRAREQ table. This change satisfies RPE 25222.

• Defect 104328 has been resolved. When RRREXIT was run for a student having a satisfied requirement for an exit interview, the process set the tracking letter indicator and removed the All Requirements Complete date, even though all requirements were satisfied. This behavior has been corrected so that satisfied requirements are not updated.

• The Current Term Code parameter, previously required, has been made optional. This resolves defect 103072.

• New parameters allow you to explicitly specify whether the process will check for withdrawals, graduates, and low enrollment students. This change resolves defect 103075.



Enhanced Tracking Letter Indicator Functionality

SCT Banner Financial Aid includes an indicator on the student’s RORSTAT record (RORSTAT_TRK_LTR_IND) to control whether or not the student should receive an initial or subsequent tracking letter due to changes in the group of outstanding requirements for the student. This indicator may be used in the population selection process to select these students for the letter.

New Tracking Letter Fields

In Release 7.3.1, a new enhancement now gives you much more flexibility in controlling how the student Tracking Letter Indicator gets set. Three new fields have been added to the database for this enhancement:

• The Tracking Letter Indicator for a requirement (RRRAREQ_TRK_LTR_IND) indicates that a tracking letter should be generated for this requirement.

• The Tracking Letter Exclusion Indicator for a requirement (RTVTREQ_LTR_EXCLUDE_IND) indicates if the requirement should be excluded from setting the tracking letter flag when the requirement is established as unsatisfied.

• The Tracking Letter Indicator for a requirement status (RTVTRST_TRK_LTR_IND) indicates if a requirement with this status should appear on a tracking letter.

Tracking Letter Exclusion Indicator

The Tracking Letter Exclusion Indicator has been added to the Tracking Requirement Validation Table and Form. You check this box for requirements that do not affect whether or not the student needs a new tracking letter. For example:

You have a tracking requirement for an accepted admissions status to prevent awarding or disbursement of aid until the student is accepted for admissions. The student doesn’t necessarily need a new financial aid tracking letter when this requirement is created. The admissions office usually takes care of that. In this example, you would check the Tracking Letter Exclusion Indicator so that the creation of this requirement would not cause the overall RORSTAT Tracking Letter Indicator to be set to Y.

Tracking Letter Indicator for a Requirement Status

Tracking letters are usually sent to inform students of additional documents they need to submit to allow the awarding or disbursement of aid. Requirements with a status that indicates satisfied should not trigger a new tracking letter to the student. The same thing can be said for requirements with a status equivalent to canceled or withdrawn. The status Tracking Letter Indicator on the Tracking Status Validation Table and Form allows you to control the setting of the overall student (RORSTAT) Tracking Letter Indicator based on the status of the requirement. Check the box for this field on statuses that should generate a new tracking letter to be sent to the student, such as an Established status for paper documents.



Tracking Letter Indicator for an Applicant Requirement

The Tracking Letter Indicator has been added to the Applicant Requirements table (RRRAREQ) and the Applicant Requirements Form (RRAAREQ) to control if individual requirement records should cause the overall Tracking Letter Indicator to be set to Y. When individual requirement records are created or updated, SCT Banner looks at the Tracking Letter Exclusion Indicator on the Tracking Requirement Validation Table and the status Tracking Letter Indicator on the Tracking Status Validation Table to determine how to set the requirement Tracking Letter Indicator on the Applicant Requirements table. If we are dealing with a requirement code that should affect the tracking letter and a status code that should affect the tracking letter, then the tracking requirement indicator on the Applicant Requirements record is set to Y.

Interaction with the RORSTAT Tracking Letter Indicator

If any of the individual requirement records have a Tracking Letter Indicator of Y, then the overall RORSTAT Tracking Letter Indicator will be set to Y. If none of the individual requirement records have a Tracking Letter Indicator of Y, then the overall RORSTAT Tracking Letter Indicator will be set to N.

When the Award/Tracking Letter Reset Process (RLRLETR) is run, the RORSTAT Tracking Letter Indicator will be set to N and the individual tracking letter indicators on the RRRAREQ record will all be set to N if parameter 05, (Award or Tracking Indicator) is set to T (Tracking) or B (Both).

If you change the overall student (RORSTAT) Tracking Letter Indicator on the RRAAREQ form, all the individual tracking letter indicators will be updated accordingly.

• If the RORSTAT Tracking Letter Indicator is changed to N, all the individual tracking letter indicators that were Y will be updated to N.

• If the RORSTAT Tracking Letter Indicator is changed to Y, all the individual tracking letter indicators will be updated according to the Tracking Letter Exclusion Indicator on the Tracking Requirements Validation Table and the Tracking Letter Indicator on the Tracking Status Validation Table.

If you change any of the individual tracking letter indicators, it may affect the overall student (RORSTAT) Tracking Letter Indicator. For example, if only one RRRAREQ record has a Tracking Letter Indicator set to Y, and you change the value to N, the the overall student (RORSTAT) Tracking Letter Indicator will be updated to N.

Initial Values for the New Fields

With the installation of the 7.3.1 release, the Tracking Letter Indicator for a requirement status (RTVTRST_TRK_LTR_IND) will be set based on the value of the Satisfied Indicator (RTVTRST_SAT_IND) value. If a status represents that the



requirement is satisfied, the Tracking Letter Indicator will be N (No); if the status represents that the requirement is unsatisfied, the Tracking Letter Indicator will be Y (Yes, checked).

The initial value of the Tracking Letter Exclusion Indicator for a requirement (RTVTREQ_LTR_EXCLUDE_IND) is set to No. You should review the requirements your institution would like to exclude from setting the tracking letter flag when the requirement is established as unsatisfied and check the Tracking Letter Exclusion Indicator appropriately.

Once you have updated the Tracking Letter Indicator for your institution and the Tracking Letter Exclusion Indicator, you may run the Applicant Requirements Report (RRRAREQ) utilizing the new parameter, 17 Set Letter Indicator, to update the Applicant Tracking Letter flag based on the new Request Letter indicator for the Requirement status and the Tracking Letter Exclusion Indicator. Additional information on the new parameter for the Applicant Requirements Report (RRRAREQ) can be found later in this section; see “Applicant Requirements Report” under the “Reports and Processes” heading.

Enhanced Processing for “Required Once” Requirements

In the past, if you checked the Once (required once) field for a requirement code on the Requirements Tracking Validation Form (RTVTREQ), that requirement would inherit the characteristics of any previous occurrence of that code when the code was added in a subsequent aid year. For example, if a loan entrance interview requirement was satisfied in a previous aid year, that same requirement would automatically be updated to a satisfied status when established in a future aid year. This allowed schools to create loan entrance interview requirements for all students who are awarded loan funds and automatically have this requirement satisfied for students who have already had that interview for a loan in a prior year.

If a required once requirement existed as unsatisfied in a prior year and was created again in a future aid year, the record would inherit the unsatisfied status from the earlier year. When that requirement was satisfied in the current year Banner did not update the status to satisfied on the records for earlier years.

A new enhancement with this release includes a new Update Prior Year (RTVTREQ_UPDATE_PRIOR_YEAR_IND) field on the Requirements Tracking Validation Form (RTVTREQ) to indicate if a required once requirement should have the status updated for prior years. If this field is checked, Banner updates like requirements where the status date on the earlier record is less than or equal to the end date of the requirement aid year. For example, if a loan entrance interview requirement for the 0405 aid year remained outstanding and the student was awarded a new loan for 0506 and did attend the loan entrance interview for that loan, Banner would satisfy the requirement for 0506 and for 0405 (assuming that the new Update Prior Year Indicator was checked for that requirement). If the requirement exists as unsatisfied in both the 0405 and 0506 aid years and is satisfied in 0405, the 0506 requirement will now also be satisfied.



With the install of the 7.3.1 release, the initial value will be No for Update Prior Year. You should review your Required Once documents and update this field appropriately based on your institution's decisions

Example 1

The Update Prior Year field for the INTERV requirement code is unchecked (No). The Once field for the INTERV requirement code is checked (Yes).

Case 1

After you save the record, Banner updates the records in the following way.

Case 2


Record # Requirement Code Status Status Date Aid Year Aid Year End Date Notes

1 INTERV Established 01-SEP-2004 0405 30-JUN-2005

2 INTERV Satisfied 15-SEP-2005 0506 30-JUN-2006


1 INTERV Established 01-SEP-2004 0405 30-JUN-2005 No change.

2 INTERV Satisfied 15-SEP-2005 0506 30-JUN-2006 No change.






2 INTERV Satisfied 01-SEP-2004 0506 30-JUN-2006 Inherits values from record #1 due to required once processing.



Example 2

The Update Prior Year field for the INTERV requirement code is checked (Yes). The Once field for the INTERV requirement code is checked (Yes).

Case 1


Case 2






1 INTERV Satisfied 15-SEP-2005 0405 30-JUN-2005 Inherits values from record #2 due to update prior year processing.







2 INTERV Satisfied 01-SEP-2004 0506 30-JUN-2006 Inherits values from record #1 due to required once processing.



Case 3


RBBABUD, RBRACMP, and RRRAREQ Table Logging Enhancement

With this release, Banner’s table logging functionality has been enhanced to include support for the Applicant Budget Table (RBBABUD), Applicant Budget Component Table (RBRACMP), and Applicant Requirements Table (RRRAREQ). Logging support allows you to choose which Banner Financial Aid tables and columns to log, and which actions should be logged, through the Logging Control Form (ROALOGC).

Using the ROALOGC Form, you can activate logging on the tables by selecting the Active? checkbox to the right of the table description. At this point you can choose to Log Inserts; Log Updates; Log Deletes; Activate All Columns, or Inactivate All Columns of the desired table. You may choose any combination of these options.

If you’d prefer to log specific columns rather than all columns, navigate to the second window of this form. Here you can place a check next to the columns you want to log under the Log? heading. You may choose any combination of columns to log.

Your logging results will appear in the Logging Activity Inquiry Form (ROILOGA), which opens in Query mode. Use the first window to query on any field except Name. Fields 1–5 display the data in the row of the table in which the data was changed.







2 INTERV Satisfied 16-SEP-2005 0506 30-JUN-2006 Inherits values from record #1 due to update prior year processing.


Section 4 Applicant Requirements API - FunctionalChanged Forms

The second window displays the exact column name that was changed, what it was prior to the change, and what it was changed to. (This includes inserts and deletions assuming you set it up this way on ROALOGC).

With the addition of these three new tables, the following is the current list of tables that support logging via the ROALOGC form:

• Applicant Budget Table (RBBABUD)

• Applicant Budget Component Table (RBRACMP)

• Applicant Status Table (RORSTAT)

• Applicant Disbursement Schedule Table (RPRADSB)

• Applicant Award by Term Table (RPRATRM)

• Applicant Award Table (RPRAWRD)

• Applicant Requirements Table (RRRAREQ)

Changed Forms

Applicant Pell Grant (ROAPELL)

This form has been modified to call the rb_requirement API for inserting the SAR requirement and status defined on ROAINST when a SAR Certified Date is entered.

Applicant Summary (ROASMRY)

This form has been modified to call the rb_requirement API when updating the status of a requirement is performed from this form.

Defect 96384 has been resolved. When the Perkins MPN requirement was satisfied, the Satisfied Date and Expiration Date were not inserted into the RRRAREQ table. The use of the rb_requirement API has resolved this problem.

Package Maintenance (RPAAPMT)

Summary requirements processing has been removed from this form. The insert, update, or deletion of fund specific requirements are now handled by the RPKAWIU package which utilizes the rb_requirement API.


Section 4 Applicant Requirements API - Functional Changed Forms

Award Maintenance (RPAAWRD)

Summary requirements processing has been removed from this form. The insert, update, or deletion of fund specific requirements are now handled by the RPKAWIU package which utilizes the rb_requirement API.

Electronic Loan Application (RPAELAP)

The MODIFY_LOAN_REQ trigger in the RPRLAPP data block has been removed. Since a loan can never be manually inserted, this trigger cannot be executed.

Loan Application (RPALAPP)

This form has been modified to call the rb_requirement API for updating a requirement when Satisfy a Loan Application Requirement has been selected on the Loan Options form (RPRLOPT) with the requirement code and status.

Direct Loan Origination (RPALORG)

The MODIFY_LOAN_REQ trigger in the RPRLAPP data block has been removed. Since a loan can never be manually inserted, this trigger cannot be executed.

Applicant Requirements (RRAAREQ)

This form has been modified to call the rb_requirement API for insert, update, and delete of requirements, insert or delete of the Packaging Complete, Disbursement Complete, All Requirement Complete dates, and the setting of the Tracking letter flag.

The Tracking Letter Indicator (RORSTAT_TRK_LTR_IND) can be checked or unchecked on the Summary Block and a COMMIT performed from any block in the form, thus resolving RPE 29906.

Applicant Requirements Block

The Tracking Letter Indicator has been added to control whether individual requirement records should cause the overall tracking letter indicator to be set to Y. See “Enhanced Tracking Letter Indicator Functionality,” earlier in this section, for more details on tracking letter processing.

In addition, SGBI Description has been moved to the bottom of the form, to allow more space to display the entire description. Only the description for the currently selected row will be seen.



Applicant Additional Requirements Block

The Tracking Letter Indicator has been added to control whether individual requirement records should cause the overall tracking letter indicator to be set to Y. See “Enhanced Tracking Letter Indicator Functionality,” earlier in this section, for more details on tracking letter processing.

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

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

Letter (RRRAREQ_TRK_LTR_IND). Request Tracking Letter Indicator: Check this field if a tracking letter is needed for this requirement.


Section 4 Applicant Requirements API - Functional Changed Forms

Applicant Requirements Mass Entry (RRAMASS)

This form has been modified to call the rb_requirement API for inserting or updating of Applicant Requirements. Summary requirements processing has been removed from this form and will be handled instead by the rrkareq.p_finalize_requirements packaged procedure for updating of the Packaging Requirements, Disbursement Requirements, and All Requirements complete dates as well as setting the tracking letter flags appropriately.

Requirements Tracking Validation (RTVTREQ)

Two new fields have been added to this form.

• The Tracking Letter Exclusion Indicator has been added to allow you to exclude the requirement from setting the tracking letter flag when the requirement is added with an unsatisfied status. See “Enhanced Tracking Letter Indicator Functionality,” earlier in this section, for more details.

• The Update Prior Year Indicator has been added to specify if satisfying a required once requirement will update the requirement for a prior year. When this option is selected, the requirement will only be updated for aid years where the status date is prior or equal to the end date of an aid year as defined on ROAINST. See “Enhanced Processing for Required Once Requirements,” earlier in this section, for more details.

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

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

Letter (RRRAREQ_TRK_LTR_IND). Request Tracking Letter Indicator: Check this field if a tracking letter is needed for this requirement.



Requirements Tracking Status Validation (RTVTRST)

The new Request Letter field has been added. When selected, a requirement which has not been excluded from tracking letters (RTVTREQ_LTR_EXCLUDE_IND = N) with this status will indicate a tracking letter is needed. See “Enhanced Tracking Letter Indicator Functionality,” earlier in this section, for more details.

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

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

Letter Exclusion (RTVTREQ_LTR_EXCLUDE_IND). Tracking Letter Exclusion Indicator: If this field is checked, no tracking letter will be created for the requirement.

Update Prior Year

(RTVTREQ_UPDATE_PRIOR_YEAR_IND). If this field is checked, records for prior aid years can be updated for this requirement.

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

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

Letter (RTVTRST_TRK_LTR_IND). Request Tracking Letter Indicator: Check this field if a tracking letter is needed for this requirement.


Section 4 Applicant Requirements API - Functional New Reports and Processes


Automatic Group Assignment Process (RORGRPS)

The new Automatic Grouping Process (RORGRPS) replaces the functions previously performed by the Automatic Grouping Process (ROOAUTO) and the Batch Automated Grouping Process (ROBBGRP).

The new process can be run in batch mode or in online mode. It 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 in Wait 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 parameter 02, RORGRPS will process budgeting first, then packaging, and tracking group last.

Parameters

RORGRPS has the following parameters:

Parameter Description/Definitions Values/Validations Processing/Comments

01 Aid Year CodeRequired, SingleLength: 4Character

ROBINST_EQUAL_AIDY_ACTIVE

The aid year for the process

02 Group Type IndicatorRequired, SingleLength: 3Character

B, Budget groupsP, Packaging groupsT, Tracking groups

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 valueswithout any intervening characters or spaces (e.g., BPT).


Section 4 Applicant Requirements API - FunctionalNew Reports and Processes

03 Term CodeOptional, SingleLength: 6Character

STVTERM_EQUALS Enter a term code to limit processing to records in the specified term.

04 Process IndicatorRequired, SingleLength: 1Character

B, BatchO, Online

Must be B when running in batch mode.

05 Applicant IDOptional, Single Length: 9Character

Specific an applicant to be assigned to groups. This parameter is used only in online mode (parameter 04 is O). It must be left blank in batch mode.

06 Use All Applicants IndicatorOptional, SingleLength: 1Character

Y, Process all applicants with a status record in RORSTAT.N, Use applicants with Wait status or those in the selection ID.

If N is selected, use the applicants within the selection ID (if one was entered in parameters 07–10) and all applicants in Wait status. If no population selection has been entered, all applicants in Wait status will be used. Applicants are scheduled (Wait status) for the batch grouping process on the Immediate Process Form (ROAIMMP).

07 Application CodeOptional, SingleLength: 30Character

GLBAPPL_EQUAL Standards for population selection must be followed for parameters 07–10. If a population selection is identified with these parameters, the process will look for records only within that population selection. Application code is the general area for which the selection ID was defined.

08 Selection IDOptional, SingleLength: 30Character

Selection ID is the code that identifies the population selection.

09 Creator IDOptional, SingleLength: 30Character

ID of the person who created the population selection rules.



Section 4 Applicant Requirements API - Functional Changed Reports and Processes

Processing

RORGRPS is the reimplementation of the functionality present into both ROBBGRP and ROOAUTO. This allows us to have a single execution path for the automatic group assignment of any student whether the processing is online or in batch mode. RORGRPS processes student records as follows.

1. All student records to be processed by RORGRPS are first retrieved from Banner and stored by PIDM in the RORVIEW table.

2. The rules used by RORGRPS to determine how these students are automatically grouped are retrieved from RORRULE.

3. These rules may contain the variables :PIDM, :AIDY, and :TERM. Each of these variables, when present in a given rule, are replaced with the appropriate parameter value as provided when RORGRPS is executed. The variables :AIDY and :TERM are directly replaced with the corresponding values found in parameter 01 and parameter 03 respectively. The :PIDM variable is replaced by a query to the RORVIEW table, rather then just a single value. The :PIDM variable is required to be present in any rule retrieved by RORGRPS; if it is not present, the rule is not processed.


2005–2006 Financial Aid Dataload Part 3 (RCRTP06.pc)

This process has been updated to use the new rb_requirement API and the packaged procedures in RRKAREQ.

10 User IDOptional, SingleLength: 30Character

ID of the person who used the population selection rules.



Section 4 Applicant Requirements API - FunctionalChanged Reports and Processes

Award/Tracking Letter Indicator Reset Process (RLRLETR.pc)

This process has been updated to use the new packaged procedures in RRKAREQ.

This process also implements improvements in Tracking Letter Indicator processing. When this process (RLRLETR) is run, the RORSTAT Tracking Letter Indicator will be set to N and the individual tracking letter indicators on the RRRAREQ record will all be set to N if parameter 05, (Award or Tracking Indicator) is set to T (Tracking) or B (Both). See “Enhanced Tracking Letter Indicator Functionality,” earlier in this section, for more details.

Batch Posting Process (RORBPST.pc)

This process has been updated to use the new rb_requirement API and the packaged procedures in RRKAREQ. This process posts the date entered on the Batch Posting Rules Form (RORPOST), or the current date to RRRAREQ_STAT_DATE, resolving RPE 26936.

Note: As before, if the process is asked to update an already satisfied requirement, it will generate one of the following messages: Tracking Requirement Record not updated (when posting a tracking requirement) or Fund Tracking Requirement Record not updated (when posting a fund with associated tracking requirements).

Disbursement Process (RPEDISB.pco)

This process has been updated to use the new rb_requirement API when updating Perkins Master Promissory Note requirements.

Packaging Process (RPEPCKG.pco)

This process has no changes; however, it will be impacted by the changes to UAARTN documented below when packaging funds for a student.

Packaging Process (RPEPELL.pco)

This process has no changes; however, it will be impacted by the changes to UAARTN documented below when awarding Pell funds for a student.

Packaging Initialization Process (RPEPINT.pco)

This process has no changes; however, it will be impacted by the changes to UAARTN documented below when deleting funds for a student prior to running the packaging process.



Award Cancellation Process Report (RPRCNCL.pc)

This process has been updated to use the new packaged procedures in RRKAREQ.

2005–2006 Direct Loan Upload (RPRDU06.pc)


UAARTN COBOL Copybook

The UAARTN COBOL copybook has been updated to use the new rb_requirement API to satisfy loan application requirements when an award is being added. UAARTN also:

• Uses the new rrkareq.p_finalize_requirements packaged procedure to finalize summary requirement processing.

• Uses the new rrkareq.p_add_fund_requirements packaged procedure to add requirements associated with the award’s fund code when an award is being added or updated. All code made obsolete by the rrkareq.p_add_fund_requirements packaged procedure has been removed.

• Uses the new rrkareq.p_delete_fund_requirements packaged procedure to delete requirements associated with the award’s fund code when the award is being deleted. All code made obsolete by the rrkareq.p_delete_fund_requirements packaged procedure has been removed.

Exit Interview Requirements Process (RRREXIT)

The Exit Interview Requirements Process (RRREXIT) has been streamlined to make it simpler and more straightforward to use. A new, expanded set of parameters gives you more flexibility in applying the process to a targeted subset of students.

Selecting the Population

The RRREXIT process allows two basic approaches to selecting a population of students. You can enter a previously identified population selection code, using parameters 16–19, or you can use parameters 6–12 to select the population based on specific conditions.

You can also combine the two methods, using a population selection to further limit the population of students selected by parameters 6–12.

• Graduating Students: If parameter 05 is Y, the process checks for students who have a graduation date recorded which falls between the begin date and end



date parameters (09 and 10), or which have a graduation in the specified graduation term (parameter 08). Additionally the student's degree status code is checked to ensure that the degree is pending or has been awarded. Students selected in this category must have had loans in any year which is less than or equal to the parameter 01 aid year.

• Withdrawals: If parameter 06 is Y, the process checks for the student’s enrollment status for the parameter 11 current term. If the student is indicated as withdrawn (STVESTS_WD_IND is Y) or is not included in student headcount (STVESTS_EFF_HEADCOUNT is N), the process counts the student as withdrawn. Students selected in this category must have had loans in any year which is less than or equal to the parameter 01 aid year.

• Low Enrollment: If parameter 07 is Y, the process checks for two categories of students:

• Less Than Half-Time Enrollment: The process checks for students whose enrollment is below half-time in the parameter 11 current term. Students selected in this category must have had loans in any year which is less than or equal to the parameter 01 aid year. Hours are calculated based on current term registrations for courses which count in enrollment. The Audit Mode Rules (RORAUDT) are invoked to detect those courses which should not be counted. The result is matched to the financial aid load rules on the aid year's institutional options based on the parameter 11 current term code and the student level code. The student's level is determined from the maximum effective term general student record.

• No-Shows: This selection is for students who were enrolled in the parameter 12 previous term for at least half-time but are not enrolled in the parameter 11 current term. This excludes students who have a degree awarded or who withdrew in the prior term as these would have been detected in the prior term run.

Students selected in this category must have had loans in any year less than or equal to the parameter 01 aid year.

Selecting the Award

Regardless of the student selection method, you must specify an aid year (parameter 01) and one or more fund codes (parameter 02).

Students selected must have had loans in any year which is less than or equal to the parameter aid year. The loans checked are for those fund code(s) entered in parameter 02.

Loan amounts are taken from the Accepted Amounts in the student's award record. Award records are not processed if the accepted award amount is NULL or zero. A loan total of zero does not cause the system to post a requirement.



Posting the Requirement

You have the option of doing a dry run of the process, without updating the student’s requirement records, by entering R for parameter 13. When selecting the Report only value for parameter 13, the selected students are printed on the report along with a message that indicates whether the requirement would be established, updated, or already exists. When you enter U for parameter 13, selected students’ RRRAREQ records are updated with the tracking requirement code you specified as parameter 03 and the requirement status code you specified as parameter 04.

When the tracking requirement code is added:

• It posts with a system indicator of B. This is treated as a manual component when regrouping.

• The required for indicators are taken from the Tracking Requirement Validation Form for the tracking code being posted.

• If no RORSTAT record exists for the student for the parameter aid year, a RORSTAT record is created.

When a tracking requirement code is updated:

• The status date of the requirement is updated. The established date is not updated.

• The system indicator is set to B.

• The status will not be updated if the requirement has already been satisfied.

• Tracking completed dates are updated, or set to NULL if appropriate.

Requirement records are inserted and updated at the end of processing for each student (if parameter 13 is set to allow updates).

Parameters

There are several new parameters for the RRREXIT process, and existing parameters have been renumbered. The following table lists the complete set of parameters.


01 Aid Year CodeRequired, SingleLength: 4Character

ROBINST_EQUAL_AIDY_ACTIVE

The aid year for the process



02 Fund CodeRequired, MultipleLength: 6Character

RFRBASE_EQUAL The fund code or codes that require exit interviews

03 Exit Requirement CodeRequired, SingleLength: 6Character

RTVTREQ_EQUAL A tracking requirement code. If parameter 13 is U, this code will be inserted into RRRAREQ for students who are identified by the process as requiring exit interviews.

04 Requirement Status CodeRequired, SingleLength: 1Character

RTVTRST_EQUAL A requirement status code associated with the exit requirement code of parameter 04. If parameter 13 is U, this code will be inserted into RRRAREQ for students who are identified by the process as requiring exit interviews.

05 Check for GraduatesOptional, SingleLength: 1Character

Y, check for graduatesN (default), do not check for graduates

Specify whether the process will check graduate record. If Y, then you must provide values either for parameter 08 or for parameters 09 and 10.

06 Check for WithdrawalsOptional, SingleLength: 1Character

Y, check for withdrawalsN (default), do not check for withdrawals

Specify whether the process will check withdrawal status for the current term entered in parameter 11.

07 Check for Low EnrollmentOptional, SingleLength: 1Character

Y, check for low enrollmentN (default), do not check for low enrollment

Specify whether the process will check for low enrollment status. If Y, less than half time or no enrollment will be checked for the current and previous terms entered in parameters 11 and 12.

08 Graduation TermOptional, SingleLength: 6Character

STVTERM_EQUAL Student will be selected if the term entered equals the student’s graduation term as entered on SHADEGR (SHRDGMR_TERM_OCDE_GRAD). Applies only if parameter 05 is Y.




09 Graduation Beginning DateOptional, SingleLength: 11Date

CHK_CENTURY If student’s graduation date is on or after the beginning date (parameter 09) and before the ending date (parameter 10), the student will be selected. Applies only if parameter 05 is Y.

10 Graduation Ending DateOptional, SingleLength: 11Date

CHK_CENTURY See comments for parameter 09.

11 Current Term CodeOptional, SingleLength: 6Character

STVTERM_EQUAL The current term code will be checked for withdrawals (if parameter 06 is Y) or low enrollment (if parameter 07 is Y).

12 Previous Term CodeOptional, SingleLength: 6Character

STVTERM_EQUAL The previous term code will be checked for low enrollment (if parameter 07 is Y).

13 Report and/or UpdateRequired, SingleLength: 1Character

R, report onlyU (default), report and update

R will report records with applicable loans and (if parameter 15 is Y) NSLDS information. U will print the report and also update RRRAREQ records with the codes specified in parameters 03 and 04.

14 Page BreakOptional, SingleLength: 1Character

Y, new page for each studentN (default), no page breaks added

15 Print NSLDS SummaryOptional, SingleLength: 1Character

Y (default), print NSLDSN, do not print NSLDS

If Y, NSLDS Aggregate loan data and Perkins loan data will be printed for informational purposes on the report.




Financial Aid Transcript Requirements (RSRPCOL.pc)


Applicant Requirements Report (RRRAREQ.pc)

This report provides detailed information on each applicant’s tracking requirements. Its parameters provide many options for selecting subsets of the applicant population.

Three new parameters, 15, 16, and 17, have been added to this report to provide new options for tracking letter processing.

Parameter 17, Set Letter Indicator, gives you the option of using RRRAREQ to set the values of the Tracking Letter Indicator for your selected set of applicant requirements. This can be helpful when setting initial values for the new Tracking Letter Indicator field after installing Release 7.3.1. For more information, see “Enhanced Tracking Letter Indicator Functionality,” earlier in this section

16 Application IDOptional, SingleLength: 30Character

GLBAPPL_EQUAL Standards for population selection must be followed for parameters 16–19. If a population selection is identified with these parameters, the process will look for records only within that population selection. Application ID is the general area for which the selection ID was defined.

17 Selection IDOptional, SingleLength: 30Character

Selection ID is the code that identifies the population selection.

18 Creator IDOptional, SingleLength: 30Character

ID of the person who created the population selection rules.

19 User IDOptional, SingleLength: 30Character

ID of the person who used the population selection rules.




Note: As noted in Section 5, “Miscellaneous Validation Methodology - Functional,” this report’s dependency status processing has also been modified. The sel_rcrapp1 function was modified to use RCRAPP2_MODEL_CDE for the determination of dependency status (I - Independent, D - Dependent).

Parameters

The following is an example of the report output.


15 Applicant Letter IndicatorOptional, SingleLength: 1Character

Y, yesN, no Blank

If Y, records with the Applicant Letter Indicator checked (RORSTAT_TRK_LTR_IND = Y) will be selected. If N, records with the Applicant Letter Indicator unchecked (RORSTAT_TRK_LTR_IND = N) will be selected. If blank, records will be selected regardless of the value of the Applicant Letter Indicator.

16 Requirement Letter IndicatorOptional, SingleLength: 1Character

Y, yesN, no Blank

If Y, records with the Requirement Tracking Letter Indicator checked (RRRAREQ_TRK_LTR_IND = Y) will be selected. If N, records with the Requirement Tracking Letter Indicator unchecked (RRRAREQ_TRK_LTR_IND = N) will be selected. If blank, records will be selected regardless of the value of the Requirement Tracking Letter Indicator.

17 Set Letter IndicatorOptional, SingleLength: 1Character

Y, yesN, no (default)

If Y, the Requirement Tracking Letter Indicator will be updated when the process is run, based on the values of RORSTAT_TRK_LTR_IND for the applicant, RTVTREQ_EXCLUDE_LTR_IND for the requirement, and RTVTRST_TRK_LTR_IND for the status. (See “Enhanced Tracking Letter Indicator Functionality,” earlier in this section, for more details.)If N, the indicator will not be updated.


Section 4 Applicant Requirements API - FunctionalObsolete Reports and Processes

Obsolete Reports and Processes

The following processes have been made obsolete, with their functionality now handled by the new RORGRPS process:

• Automatic Grouping Process (ROOAUTO)

• Batch Automated Grouping Process (ROBBGRP)

11-OCT-2005 10:16 AM BANNER University PAGE 1AID YEAR: 0506 Applicant Requirements Tracking Report RRRAREQ

NAME ID TRK GRP LTR AID PERIOD BUD GRP PCKG GRP DEP CLASS ENROLL STATStembler, Kay S. 408002018 INDNVR Y Fall-Spring Semesters UGINON ONFRSH I < 1/2 (ACTUAL) STATUS SATISFIED REQUIREMENT CODE DATE STATUS SBGI PCKG DISB MEMO TRK FUND SYS INTERV Loan Entrance Inter E 07-OCT-2005 N N Y N Y DIRECT F INTERV Loan Entrance Inter E 07-OCT-2005 N N Y N Y STFDX F INTERV Loan Entrance Inter E 07-OCT-2005 N N Y N Y STFDY F PN-PER Perkins Prom Note E 07-OCT-2005 N N Y N Y DIRECT F SAR SAR E 07-OCT-2005 N N Y Y Y HALWS F SCTAPP Institutional Appl E 10-OCT-2005 N Y Y N Y S STFDAP Stafford Loan Appl. E 07-OCT-2005 N N Y Y Y STFDX FMarinich, Theodora A. 408002019 INDNVR Y Fall-Spring Semesters UGINOF ONFRSH I < 1/2 (ACTUAL) STATUS SATISFIED REQUIREMENT CODE DATE STATUS SBGI PCKG DISB MEMO TRK FUND SYS ADMIT Admissions Decision E 07-OCT-2005 N Y Y Y N M AWARD Award Letter E 17-AUG-2005 N N Y N Y MERIT F INTERV Loan Entrance Inter E 17-AUG-2005 N N Y N Y PERK F PN-PER Perkins Prom Note E 17-AUG-2005 N N Y N Y PERK F SCHL-R Scholarship Release E 17-AUG-2005 N N Y N Y MERIT F

11-OCT-2005 10:16 AM BANNER University PAGE 2AID YEAR: 0506 Applicant Requirements Tracking Report RRRAREQ * * * REPORT CONTROL INFORMATION * * *

RPTNAME ............................... RRRAREQVERSION# .............................. (7.3.1)REPORT SEQUENCE NUMBER ................ 67390SELECTION IDENTIFIER .................. MANUALAPPLICATION CODE ...................... FINAIDCREATOR ID ............................ ABRYANTUSER ID ............................... ABRYANTAID YEAR .............................. 0506TRACKING GROUP.........................REQ'D FOR PACKAGING (Y/N) ............. NREQ'D FOR DISBURSEMENT (Y/N) ..........REQ'D FOR FUND (Y/N) ..................TRACKING STATUS CODE ..................ENROLLMENT TERM CODE .................. 200610TRACKING REQUIREMENT CODE .............SATISFIED STATUS (Y/N) ................ NAPPLICANT LETTER INDICATOR (Y/N) ...... NREQUIREMENT LETTER INDICATOR (Y/N) ....SET LETTER INDICATOR (Y/N) ............ NPAGE BREAK BETWEEN APPLICANTS (Y/N) ... NLINE COUNT ............................ 55


Section 4 Applicant Requirements API - Functional Obsolete Reports and Processes



Section 5 Miscellaneous Validation Methodology - FunctionalOverview

Section 5 Miscellaneous Validation Methodology - Functional

Overview

You can load information into SCT Banner from outside sources. SCT Banner Financial Aid clients who subscribe to the CSS PROFILE service import the information into the SCT Banner database through data load programs. SCT Banner clients also use the Electronic Data Exchange (EDE) to receive federally processed information for the purpose of awarding and disbursing monies in accordance with U.S. Federal regulations. The EDE processes include the following: Institution Student Information Record (ISIR) and National Student Loan Data System (NSLDS) data load, and the Correction creation, extract, and data load.

The data received from these outside sources often have pre-defined values. In the past, these values were hard-coded into forms and processes. The new Miscellaneous Validation methodology attempts to standardize validation and translation of this data.

Release 7.3 included the underlying table structure for the new Miscellaneous Validation methodology, but no data was loaded into the new Miscellaneous Validation Rules Table (RORMVAL) as part of Release 7.3. With Release 7.3.1, this new feature has been incorporated into many of the forms and processes for the 2006–2007 aid year.

On several forms in SCT Banner, the Miscellaneous Validation Rules will be used to display the value for a field (as stored in the Banner database) along with the description of the value in either a drop-down list or a List of Values (LOV) for the field. For example, Marital Status on the RNAPR07 form is now a drop-down list containing the appropriate values associated with the fields for IM Parent and IM Student. Since the drop-down lists contain the valid values for the fields, you no longer need to look at the Auto hint to determine the possible values. When the FM portion of RNAPR07 is available, the values for marital status appropriate for EDE will be displayed for the FM side and the values for marital status appropriate for CSS will be displayed on the IM side. Only the valid values will be provided in the drop-down or LOV, and only those values may be selected for the field.

Caution: There is a change in navigation behavior that applies when your cursor is on a drop-down list on RNAPR07. The up arrow and down arrow keys, which typically navigate to the previous record or next record, navigate between columns for Parent and Student in RNAPR07. But when the cursor is on a field with a drop-down list, the up and down arrow keys will instead scroll the values available in the drop-down. This means that using the up/down arrows while on a drop-down list could potentially


Section 5 Miscellaneous Validation Methodology - Functional Overview

change the values for the field. To avoid inadvertently changing data values in these instances, you should navigate from column to column by using the mouse or the tool bar options.

Dependency Status Selection Simplified

As part of the Miscellaneous Validation implementation, the processing of Dependency Status values was simplified. Several forms and processes previously contained code to translate Dependency Status values. The RCRAPP2_C_DEPEND_STATUS column stores values of 1, 4, 5, or 8 for Independent students and 2, 6, 7, or null for Dependent students. These values were translated to a status of I for Independent or D for Dependent.

These forms and processes will no longer translate the numeric values; instead, they now use the value of RCRAPP2_MODEL_CDE which stores the values of I for Independent and D for Dependent.

Note: If you use Dependency Status as a selection criterion in reports, population selections, or RORRULE, no action is required. Your existing rules and population selections will work the same as before.

With Release 7.3.1 release we are recommending the use of RCRAPP2_MODEL_CDE to simplify selections based on dependency status. (Remember that aid year specifications remain.)

• RCRAPP2_MODEL_CDE = 'I' to select Independent students

• RCRAPP2_MODEL_CDE = 'D' to select Dependent students

As part of the installation of Release 7.3.1, an optional step has been provided to automatically update the Financial Aid variables which previously used RCRAPP2_C_DEPEND_STATUS to now use RCRAPP2_MODEL_CDE. The variables which will be updated by this step are:

• *CAMT

• *PARENT_CONTRIBUTIONS

• *PAR_CONTRB_LABEL

Aid Year-Specific Need Analysis Result Form

In connection with the implementation of the new Miscellaneous Validation methodology, the Need Analysis Result Form (RNARS07) has been made aid year-specific. Beginning with the 2006–2007 aid year, it replaces the RNARSLT form. RNARSLT will still be available for aid years prior to 2006–2007.


Section 5 Miscellaneous Validation Methodology - FunctionalNew Forms

New Forms

Miscellaneous Validation Rules Inquiry (ROIMVAL)

You can use the new Miscellaneous Validation Rules Inquiry form to view miscellaneous validation rules data. The data shown on this form is drawn from the Miscellaneous Validation Rules Table (RORMVAL) and sorted alphabetically by Column, Key 1, Key 2, and Code. The form is read-only; you cannot change or save any data.

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

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

Column The column for which validation is being provided.

Key 1 The first component of the validation code’s unique key, often the four-digit aid year (e.g., 0607).

Key 2 The second component of the validation code’s unique key.

Code A valid value for the column.

Description The description corresponding to the code.

Translation An alternate code into which the valid value can be translated, for example, for a different system or data source.

Comment A comment to explain how the translation code is used.

Activity Date The date this validation record was created or modified.


Section 5 Miscellaneous Validation Methodology - Functional New Forms

2006–2007 Need Analysis Result Form (RNARS07)

Main Window

The Need Analysis Result Form (RNARS07) is now aid year-specific and replaces the RNARSLT Form beginning with the 0607 aid year. The form no longer maintains secondary calculations. For this reason, the Secondary Calculations Block no longer displays on the main window of the form.

The form no longer accepts O (Official) or E (Estimated) as valid values for the official/estimated indicators. You must use 1=Official or 2=Estimated from the drop-down list. The following fields use the new Miscellaneous Validation Rules drop-down list methodology.

FM SC (Estimated) FM SC (Methodology Type)FM PC (Estimated) FM PC (Methodology Type)Total (Estimated) IM SC (Methodology Type)Pell EFC (Estimated) IM PC (Methodology Type)Official Source Indicator Dependency StatusSAR ‘C’ Flag


Section 5 Miscellaneous Validation Methodology - FunctionalChanged Forms

Federal Match Indicators Window

All fields in this window use the new Miscellaneous Validation Rules drop-down list methodology.

The following fields were removed from the Federal Match Indicators Window since these fields are no longer loaded or used.

Changed Forms

Forms Using Miscellaneous Validation

The new Miscellaneous Validation has been implemented in the following forms:

• 2006–2007 Need Analysis Processing (RNAPR07)

• 2006–2007 Supplemental Need Analysis (RNASU07)

• Batch Posting Rules (RORPOST)

The following form was modified to use values from the Miscellaneous Validation Rules Table (RORMVAL) for the 2006–2007 aid year and beyond. The form will use the existing structure for aid years prior to 2006–2007.

Title IV Default Hold FileSelective Service Guaranty Agency DefaultSSN Date of Death Prisoner Match


Section 5 Miscellaneous Validation Methodology - Functional Changed Forms

• Calculated Need Analysis Detail Inquiry Form (RNINAIQ)

• Financial Aid Record Maintenance (ROARMAN)

The form was modified to use values from the Miscellaneous Validation Rules Table (RORMVAL) for the 2006–2007 aid year and beyond. The Miscellaneous Validation Rules table is not used for aid years prior to 2006–2007.

Forms with Navigation Changes for RNARS07

Options Menu Change from RNARSLT to RNARSxx

The entry on the Options Menu was changed from Need Analysis Result (RNARSLT) to Need Analysis Result (RNARSxx) beginning with the 2006–2007 aid year on the following forms. RNARSLT continues to be used for years prior to 2006–2007.

• Applicant Budget Form (RBAABUD)

• Financial Aid Record Maintenance Form (ROARMAN)

• Applicant Status Form (ROASTAT)

• Package Maintenance Form (RPAAPMT)

• Award Maintenance Form (RPAAWRD)

• Applicant Requirements Form (RRAAREQ)

Applicant Override Form (RNAOV07)

The form was modified so that the Options menu calls the new Need Analysis Result Form (RNARS07).

Need Analysis Processing Form (RNAPR07)

When you select the Calc Need option on the RNAPR07 Form, the system advances you to the new Need Analysis Result Form (RNARS07) to review the results.

Supplemental Need Analysis Form (RNASU07)

When you select the Calc Need option on the RNASU07 Form, the system advances you to the new Need Analysis Result Form (RNARS07) to review the results.


Section 5 Miscellaneous Validation Methodology - FunctionalChanged Forms

Applicant Immediate Process Form (ROAIMMP)

When you perform a need analysis calculation, the system advances you to the Need Analysis Result Form (RNARS07) to view the results of the calculation for aid years beginning with 2006–2007. For aid years prior to 2006–2007, the Need Analysis Result Form (RNARSLT) is called.

Need Analysis Result Form (RNARSLT)

You can no longer access the RNARSLT beginning with the 2006–2007 aid year. This form has been converted to an aid year specific form (the Need Analysis Result Form (RNARS07)). However, you can still access the RNARSLT Form for aid years prior to 2006–2007.

Applicant Status Form (ROASTAT)

The form was modified to use RCRAPP2_MODEL_CDE whose values are I for Independent and D for Dependent from the Miscellaneous Validation Rules Table (RORMVAL). The Default and Owes Refund fields were removed from the form.

The NSLDS Match field was added to the Application Data Window. For the 2006-2007 aid year and beyond, Miscellaneous Validation Rules Table (RORMVAL) will be used to display the NSLDS Match value.

The NSLD Match field (DISPLAY_RCRLDS4_MATCH_IND) displays the match indicator for years prior to the 2006–2007 aid year.

Package Maintenance Form (RPAAPMT) and Award Maintenance Form (RPAAWRD)

The forms were modified to use RCRAPP2_MODEL_CDE from the Miscellaneous Validation Rules Table (RORMVAL). The Overall NSLDS Override Indicator field (DISPLAY_RORSTAT_NSLDS_OVRD) was modified to use the new Miscellaneous Validation Rules drop-down list methodology.

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

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

NSLDS Match (RCRLDS4_MATCH_IND). The NSLDS match from the current NSLDS record for the aid year.


Section 5 Miscellaneous Validation Methodology - Functional Changed Menus

Changed Menus

Financial Aid Common Functions Control (*RESCOMNCM)

Miscellaneous Validation Rules Inquiry (ROIMVAL) has been added to the Financial Aid Common Functions Control menu.

Menu Changes for RNARS07

The new 2006–2007 Need Analysis Result Form (RNARS07) was added to the *RESAPPL07 and *RESNEED07 menus—replacing the Need Analysis Result Form (RNARSLT), which was used in years prior to 2006–2007.


The following processes have been modified to remove hard-coded values and use the Miscellaneous Validation methodology instead.

• 2006–2007 FA CSS Dataload Part 1 (RCBCT07)

• Batch Posting Process (RORBPST)

2006–2007 FA CSS Dataload Part 1 (RCBCT07)

The MV07CSSS COBOL copybook no longer translates the FM SC methodology type. The MV07CSSS copybook uses the new Miscellaneous Validation Rules Table to translate the model code. A call to the rb_rormval.f_get_translation packaged function returns the translated value from the Miscellaneous Validation Rules (RORMVAL) Table.

The Cal MIS Extract (RERCALX)

The student_dependency function was modified to use RCRAPP2_MODEL_CDE for dependency status.

Financial Aid Transcript (RHRTRAN)

The sel_any_title_iv function was modified to use RCRAPP2_MODEL_CDE for dependency status.


Section 5 Miscellaneous Validation Methodology - FunctionalChanged Reports and Processes

2006–2007 Needs Analysis Process (RNEIN07)

The MVIRSL07 COBOL copybook was modified to no longer translate the FM PC, FM SC, IM PC, and IM SC methodology types. A call to the rb_rormval.f_get_translation packaged function uses INAR_METHOD to return the translated values from the Miscellaneous Validation Rules Table (RORMVAL).

The MVIRSL07 COBOL copybook was modified to get model code from dependency status. A call to the rb_rormval.f_get_translation packaged function uses RCRAPP2_C_DEPEND_STATUS to return the translated values from the Miscellaneous Validation Rules Table (RORMVAL).

The MVPRSL07 COBOL copybook was modified to get model code from dependency status. A call to the rb_rormval.f_get_translation packaged function uses RCRAPP2_C_DEPEND_STATUS to return the translated values from the Miscellaneous Validation Rules Table (RORMVAL).

Applicant Requirements Report (RRRAREQ)

The sel_rcrapp1 function was modified to use RCRAPP2_MODEL_CDE for the determination of dependency status (I - Independent, D - Dependent).

Note: Other changes to the RRRAREQ report are detailed in Section 4, “Applicant Requirements API - Functional.”


Section 5 Miscellaneous Validation Methodology - Functional Changed Reports and Processes



Section 6 CSS PROFILE - TechnicalChanged Tables

Section 6 CSS PROFILE - Technical

Changed Tables

Financial Aid Application Table, Part 1, Temporary Table (RCRTMP1)

The following columns were changed from VARCHAR2(1) to VARCHAR2(2):

• RCRTMP1_TAX_FORM_IND

• RCRTMP1_PAR_TAX_FORM_IND

The following column was added to this table.

Financial Aid Application Table, Part 1, Permanent Table (RCRAPP1)


• RCRAPP1_TAX_FORM_IND

• RCRAPP1_PAR_TAX_FORM_IND


Column Name Null? Type Description Column Comment(Dynamic Help)

RCRTMP1_PAR_REMARRIAGE_DATE YES DATE DATE OF REMARRIAGE

Date parent remarried.


RCRAPP1_PAR_REMARRIAGE_DATE YES DATE DATE OF REMARRIAGE



Section 6 CSS PROFILE - Technical Changed Tables

Financial Aid Application Log Table, Part 1 (RLRAPP1)


• RLRAPP1_TAX_FORM_IND

• RLRAPP1_PAR_TAX_FORM_IND


Financial Aid Application Table, Part 4, Temporary Table (RCRTMP4)

The following column was changed from VARCHAR2(2) to VARCHAR2(3):

• RCRTMP4_CUST_PAR_BASE_PCT_INC


Financial Aid Application Table, Part 4, Permanent Table (RCRAPP4)


• RCRAPP4_CUST_PAR_BASE_PCT_INC



RLRAPP1_PAR_REMARRIAGE_DATE YES DATE DATE OF REMARRIAGE



RCRTMP4_FEE_WAIVER_IND YES VARCHAR2(1) PROFILE FEE WAIVER INDICATOR

Indicates whether or not this applicant used a fee waiver


RCRAPP4_FEE_WAIVER_IND YES DATE PROFILE FEE WAIVER INDICATOR



Section 6 CSS PROFILE - TechnicalChanged Tables

Financial Aid Application Log Table, Part 4 (RLRAPP4)


• RLRAPP4_CUST_PAR_BASE_PCT_INC


Additional CSS PROFILE Data Table (RCRTMP5)

The RCRTMP5_CUST_PAR_OPT_PCT_INC column was changed from NUMBER(2) to NUMBER(3) type.

Additional CSS PROFILE Data Table (RCRIMP1)

The RCRIMP1_CUST_PAR_OPT_PCT_INC column was changed from NUMBER(2) to NUMBER(3) type.

Logging Additional CSS PROFILE Data Table (RLRIMP1)

The RLRIMP1_CUST_PAR_OPT_PCT_INC column was changed from NUMBER(2) to NUMBER(3) type.

Pell Payment Schedule Table (RORPELL)

Because the 2006–2007 maximum Pell Grant has not been determined and the 2006–2007 Pell Grant schedules are not yet published, the values for 2005–2006 in the RORPELL table have been copied to 2006–2007 and delivered with this release.

Alternate Pell Payment Schedule Table (RORAPEL)

Because the 2006–2007 maximum Pell Grant has not been determined and the 2006–2007 Pell Grant schedules are not yet published, the values for 2005–2006 in the RORAPEL table have been copied to 2006–2007 and delivered with this release.


RLRAPP4_FEE_WAIVER_IND YES DATE PROFILE FEE WAIVER INDICATOR



Section 6 CSS PROFILE - Technical Changed Tables

Federal Rules Inquiry Table (RPRFEDR)

At this time, the annual maximum for the Federal Pell Grant (Federal Fund ID of Pell) has not been finalized for the 2006–2007 aid year. It should be noted that there are no other U.S. Federal funds with annual or cumulative award changes. Therefore, the 2005–2006 RPRFEDR data was copied to 2006–2007 and delivered with this release.

Data Log Rules Data (RORDATA)

RORDATA records have been inserted for aid year 2006–2007 by copying the records for aid year 2005–2006 and updating year-specific descriptions for the following columns:

The following columns were added for 2006–2007:

Logging Rules Table Data (RORDVAL)

New rows for RNAOV07 have been added to the RORDVAL table by copying the existing rows for RNAOV06.

Aid Year

Column Name Description

0607 RCRAPP1_DEGREE_BY_JULY Degree By July 1, YYYY

0607 RCRAPP3_GRAD_OR_PROF Working on a Master’s or Doctorate program

0607 RCRAPP4_LEGAL_RES_IND Student legal resident before 01-JAN-YYYY

0607 RCRAPP4_PAR_LEGAL_RES_IND Parents legal resident before 01-JAN-YYYY

0607 REJ_A Birth year between 1900 and 19YY

Aid Year

Column Name AuditInd

PellInd

ActivityDate

Description SystemReq

0607 RCRAPP1_PAR_REMARRIAGE_DATE Y N SYSDATE Parent remarriage date Y

0607 RCRAPP4_FEE_WAIVER_IND Y N SYSDATE PROFILE fee waiver indicator Y


Section 6 CSS PROFILE - TechnicalNew Scripts

New Scripts

Note: Unless otherwise noted, new scripts are run as part of the upgrade process for a release.

The following new scripts insert data records for the 2006–2007 aid year.

• The rinsgl07.sql script inserts 2006–2007 global default values into the RNRGLBL table. This script can be re-run if, for any reason, you need to re-set all options back to the original default options.

• The glbl60801.sql script inserts default values for 2006–2007 into the RNRGLBL table during the install process.

• The vfrm70301.sql script updates data for the following letter generation variables to use RCRAPP2_MODEL_CDE instead of RCRAPP2_C_DEPEND_STATUS.

• CAMT

• PARENT_CONTRIBUTIONS

• PAR_CONTRB_LABEL

This script is not automatically run as part of the install process. This was done so that any changes you may have made to these variables will not be automatically overwritten by the script. If you choose to run this optional script you must recompile the variables either manually by overtyping a character and saving on the GLRVRBL form or by running GLBPARM followed by GLOLETT.

• The pell60801.sql script inserts RORPELL records for the 2006–2007 aid year. Because the 2006–2007 maximum Pell Grant has not been determined and the 2006–2007 Pell Grant schedules not yet published, the RORPELL values for 2005–2006 were copied to 2006–2007 and delivered with this release.

• The apel60801.sql script inserts RORAPEL records for the 2006–2007 aid year. Because the 2006–2007 maximum Pell Grant has not been determined and the 2006–2007 Pell Grant schedules not yet published, the RORAPEL values for 2005–2006 were copied to 2006–2007 and delivered with this release.

• The fedr60801.sql script inserts RPRFEDR records for the 2006–2007 aid year. The RPRFEDR values for 2005–2006 were copied to 2006–2007. At this time, the 2006–2007 maximum Pell Grant has not been determined, but there are no other U.S. Federal funds with annual or cumulative award changes.

• The data60801.sql script inserts RORDATA records for the 2006–2007 aid year. See the “RORDATA” topic in “Changed Tables,” earlier in this section for details of the 2006–2007 changes for RORDATA.

• The dval60801.sql script insert the RNAOV07 records into the RORDVAL table. All existing rows for RNAOV06 were copied to create new rows for RNAOV07.


Section 6 CSS PROFILE - Technical New Banner Views

New Banner Views

2006–2007 Admissions Applications View (ROVAD07)

The new ROVAD07 view is an updated copy of the ROVAD06 view, to be used for the 2006–2007 aid year.

2006–2007 Current Year Only Admissions Applications View (ROVAM07)

The new ROVAM07 view is an updated copy of the ROVAM06 view, to be used for the 2006–2007 aid year.

2006–2007 Admissions Application View, Including Students withoutAdmissions Decisions (ROVA207)

The new ROVA207 view is an updated copy of the ROVA206 view, to be used for the 2006–2007 aid year.

2006–2007 Admissions Application View, Current Year OnlyIncluding Students without Admissions Decisions (ROVAY07)

The new ROVAY07 view is an updated copy of the ROVAY06 view, to be used for the 2006–2007 aid year.

2006–2007 Max Term SAP Status View (ROVSA07)

The new ROVSA07 view is an updated copy of the ROVSA06 view, to be used for the 2006–2007 aid year. One change has been made to accommodate terms with the same start date in the same aid year. The view will return the term with the maximum term code when multiple terms in the same aid year have the same start date.

For example: Aid year 0607 includes term 200710 with start date 9/05/06 and term 200715 also with start date 9/05/06. The view will return term 200715.

2006–2007 Aid Year Specific Student View (ROVST07)

The new ROVST07 view is an updated copy of the ROVST06 view, to be used for the 2006–2007 aid year.


Section 7 INAS IM/EFM - TechnicalNew Scripts

Section 7 INAS IM/EFM - Technical

New Scripts

RINSGL07.SQL

A new script, RINSGL07.SQL, inserts 2006–2007 global default values into the RNRGLBL table. The new script is based on the 2005–2006 script, RINSGL06.

Caution: This script should not be run as part of the next mandatory release (6.9/7.4) if data already exists in the user’s database for 2006–2007. If it is re-run, it will overwrite user updates made prior to the new install. An additional script will be provided updating only the new FM values when available.

Note: The format for all data in the RNRGLBL table is VARCHAR2(x). Therefore, when moving data from the form to the database, numeric fields are right justified and left-padded with zeros. For example, a NUMBER(5) field with data of 123 is saved to the database as 00123.

Note: All CSS options on RNRGL07 affect the RNRGLBL_PART_1 column, whereas the options affecting the RNRGLBL_PART_2 column deal with IM/FM data comparison. The RNRGLBL_PART_2 options are not valid until FM data is loaded into the database in the 2006–2007 Winter Regulatory release; therefore, they are not included in this listing.

The columns in RNRGLBL are listed below.

Item Format Comment

RNRGLBL_AIDY_CODE VARCHAR2(4) Aid year for which the data in this record applies. Last year’s value was 0506; this year’s is 0607.

RNRGLBL_ACTIVITY_DATE DATE The date that this record was created or last updated

RNRGLBL_USER_ID VARCHAR2(30) User ID of the person creating or updating this record

RNRGLBL_PART_1 VARCHAR2(2000) The first 2000 bytes of the 4000-byte INAS GLOBAL record. See the table below for the details of this column.


Section 7 INAS IM/EFM - Technical New Scripts

The default settings for the items in the RNRGLBL_PART_1 column are shown in the table below. Values for last year (the 2005–2006 aid year) are shown in the 0506 column. Where changes have occurred, new values for the 2006–2007 aid year are shown in the 0607 column. A blank in the 0607 column indicates that the same value will be used for 0607 that was used for 0506. All changes affecting current items are highlighted with a gray background.

RNRGLBL_PART_2 VARCHAR2(2000) The second 2000 bytes of the 4000-byte INAS GLOBAL record. This part of the record covers IM to FM comparison, and it cannot be completed until FM data is available

Item Format Pos. 0506 Value 0607 Value Comment

RNRGLBL_ID VARCHAR2(5) 1 V0506 V0607 Year code

RNRGLBL_S_COMPARE VARCHAR2(1) 6 N

RNRGLBL_P_COMPARE VARCHAR2(1) 7 N

Filler VARCHAR2(2) 8

RNRGLBL_INAR VARCHAR2(1) 10 Y


RNRGLBL_COMP_TOL VARCHAR2(1) 14 Y


RNRGLBL_STATE VARCHAR2(2) 16


RNRGLBL_S_FM_CALC_TAX VARCHAR2(1) 84 N

RNRGLBL_P_FM_CALC_TAX VARCHAR2(1) 85 N

RNRGLBL_FM_IND_DUR NUMBER(2) 86 09

RNRGLBL_FM_DEP_DUR NUMBER(2) 88 09

RNRGLBL_FM_INDEP_PC VARCHAR2(1) 90 N


RNRGLBL_USE_IMP_AST_S VARCHAR2(1) 101 N

RNRGLBL_USE_IMP_AST_P VARCHAR2(1) 102 N

RNRGLBL_EST_PY_S VARCHAR2(1) 103 N



RNRGLBL_EST_PY_P VARCHAR2(1) 104 N

RNRGLBL_INC_OVR_S VARCHAR2(1) 105 N

RNRGLBL_INC_OVR_P VARCHAR2(1) 106 N

RNRGLBL_PRO_ASMPTNS VARCHAR2(1) 107 Y


RNRGLBL_IND_DURATION NUMBER(3,1) 151 090

RNRGLBL_DEP_DURATION NUMBER(3,1) 154 090

RNRGLBL_INDEP_PC VARCHAR2(1) 157 N

RNRGLBL_MAX_AGE_HSLD NUMBER(2) 158 00

RNRGLBL_MAX_AGE_CLGE NUMBER(2) 160 00


RNRGLBL_S_USE_PY VARCHAR2(1) 201 N

RNRGLBL_P_USE_PY VARCHAR2(1) 202 N


RNRGLBL_EXCL_TUIT_DED VARCHAR2(1) 206 N

RNRGLBL_USE_P_ST_TAX_ALWNCE VARCHAR2(1) 207 N

RNRGLBL_TUITION_ALWNCE NUMBER(5) 208 00000

RNRGLBL_S_MEDICAL_ALWNCE NUMBER(3,1) 213 035 036 Value change

RNRGLBL_P_MEDICAL_ALWNCE NUMBER(3,1) 216 035 036 Value change

RNRGLBL_S_EMPLMNT_RATE NUMBER(3) 219 040 042 Value change

RNRGLBL_S_EMPLMNT_MAX NUMBER(5) 222 03610 03780 Value change

RNRGLBL_P_EMPLMNT_RATE NUMBER(3) 227 040 042 Value change

RNRGLBL_P_EMPLMNT_MAX NUMBER(5) 230 03610 03780 Value change

RNRGLBL_S_CALC_US_TAX VARCHAR2(1) 235 1

RNRGLBL_P_CALC_US_TAX VARCHAR2(1) 236 1

RNRGLBL_S_LCL_FM VARCHAR2(1) 237 N

RNRGLBL_P_LCL_FM VARCHAR2(1) 238 N




RNRGLBL_ALT_INC_ASMNT_RT NUMBER(3,2) 239 000

RNRGLBL_REG_ADJ_IPA VARCHAR2(1) 242 N

RNRGLBL_BF_LOSS VARCHAR2(1) 243 N

RNRGLBL_OTH_LOSS VARCHAR2(1) 244 N


RNRGLBL_P_USE_AGI VARCHAR2(1) 246 1

RNRGLBL_AI_PCT NUMBER(2) 247 50

RNRGLBL_ADD_BK_HOPE_LLT VARCHAR2(1) 249 N

RNRGLBL_P_ADD_BK_HOPE_LLT VARCHAR2(1) 250 N

RNRGLBL_ASG_PCT_OF_INC_OPT VARCHAR2(1) 251 Y

RNRGLBL_LOW_INC_ASSET_ALWCE VARCHAR2(1) 252 Y

RNRGLBL_REG_ADJ_ERA VARCHAR2(1) 253 N



RNRGLBL_HOME_OPTION_1 NUMBER(1) 275 1






RNRGLBL_HOME_TOLERANCE_1 NUMBER(5) 289 00000






RNRGLBL_HOME_CAP_1 VARCHAR2(3) 309 999









RNRGLBL_CAP_HOME_EQT VARCHAR2(1) 349 N


RNRGLBL_ASSET_OPTION_1 VARCHAR2(1) 463 N






RNRGLBL_C_YIELD1_1 VARCHAR2(3) 479 000






RNRGLBL_C_LIMIT_1 NUMBER(5) 495 00000















RNRGLBL_C_TOLERANCE_1 NUMBER(5) 531 00000






RNRGLBL_I_YIELD1 VARCHAR2(3) 551 000


RNRGLBL_I_LIMIT NUMBER(5) 567 00000


RNRGLBL_I_YIELD2 VARCHAR2(3) 587 000


RNRGLBL_I_TOLERANCE NUMBER(5) 603 00000


RNRGLBL_S_IRA_KEOGH NUMBER(3) 621 000

RNRGLBL_FAMILY_ASSETS VARCHAR2(1) 624 1

Filler VARCHAR2(3) 625 3

RNRGLBL_S_ASSET_RATE_T1 NUMBER(3) 628 025



RNRGLBL_S_ASSET_RATE_T4 NUMBER(3) 637

RNRGLBL_P_ASSET_RATE NUMBER(3) 640

RNRGLBL_MIN_AST_S NUMBER(4) 643 0000




RNRGLBL_MIN_AST_P NUMBER(4) 647 0000

RNRGLBL_U_YR1_NEVER_ATTEND_1 NUMBER(4) 651 1150


RNRGLBL_U_YR1_NEVER_ATTEND_2 NUMBER(4) 656 1900


RNRGLBL_U_YR1_PRIOR_ATTEND_1 NUMBER(4) 661 1400


RNRGLBL_U_YR1_PRIOR_ATTEND_2 NUMBER(4) 666 1900


RNRGLBL_U_YR2_1 NUMBER(4) 671 1400
















RNRGLBL_G_YR1_1 NUMBER(4) 711 1400




















RNRGLBL_INC_LVL_1 NUMBER(6) 801 000000

RNRGLBL_MIN_PC_1 NUMBER (5) 807 00000

















RNRGLBL_S_INDEX_SC NUMBER(3,1) 879 000

RNRGLBL_P_INDEX_PC NUMBER(3,1) 882 000

RNRGLBL_USE_NCPC VARCHAR2(1) 885 N


RNRGLBL_MX_PC_PCT2 NUMBER(3,1) 887 600




RNRGLBL_S_FM_MIN VARCHAR2(1) 908 Y

RNRGLBL_P_FM_MIN VARCHAR2(1) 909 Y

RNRGLBL_USE_RPRTD_PC VARCHAR2(1) 910 N

RNRGLBL_MULT_CHLD_PC_ALLOC VARCHAR2(1) 911 S


RNRGLBL_BF_ID VARCHAR2(1) 931 Y

RNRGLBL_BF_ROW1_1 NUMBER(7) 932 0000000


RNRGLBL_BF_ROW1_2 NUMBER(7) 940 0100000 0105000 Value change





























RNRGLBL_ALT_MCPA_1_2_IN_COLL NUMBER(3,1) 1036



RNRGLBL_ALT_SCHL_YR VARCHAR2(1) 1045





RNRGLBL_IPA_ID VARCHAR2(1) 1326 Y




RNRGLBL_IPA_ROW1_1 NUMBER(5) 1327 17890 18400 Value change


RNRGLBL_IPA_ROW1_3 NUMBER(5) 1337 00000























RNRGLBL_IPA_ADDTL_1 NUMBER(4) 1452 2490 2560 Value change







RNRGLBL_NON_ENR_IPA_C NUMBER(4) 1468 0470 0480 Value change


RNRGLBL_BDGT_OPT VARCHAR2(1) 1476 N

RNRGLBL_BDGT1 NUMBER(5) 1477 10981






RNRGLBL_PT_PCT NUMBER(3) 1507 100

RNRGLBL_INST_BDGT1 NUMBER(5) 1510 30000







Section 8 Applicant Requirements API - TechnicalChanged Tables

Section 8 Applicant Requirements API - Technical

The new Application Requirements API is described in Section 4, “Applicant Requirements API - Functional.” For guidance on using SCT Banner APIs with external systems, refer to the SCT Banner API Developer Guide (api_dg.pdf).

Changed Tables

Financial Aid Applicant Requirements Table (RRRAREQ)

The following columns were added to this table.

Tracking Requirements Validation Table (RTVTREQ)


Column Name Null? Type Description

RRRAREQ_TRK_LTR_IND VARCHAR2(1) TRACKING LETTER INDICATOR: Indicates that a tracking letter should be generated for this requirement

RRRAREQ_DATA_ORIGIN VARCHAR2(30) DATA ORIGIN: Source system that created or updated the data.


RTVTREQ_LTR_EXCLUDE_IND VARCHAR2(1) TRACKING LETTER EXCLUSION INDICATOR: Indicates if the requirement should be excluded from the tracking letter.

RTVTREQ_UPDATE_PRIOR_YEAR_IND VARCHAR2(1) UPDATE PRIOR YEAR INDICATOR: Indicates if a satisfy once requirement will have the status updated for prior years.


Section 8 Applicant Requirements API - Technical New Packages

Tracking Requirements Status Validation Table (RTVTRST)


New Packages

Applicant Requirements API Packages

The rp_requirement package provides the business process interface for the Applicant Requirements API. Detailed documentation in HTML format is delivered with this package.

The following packages provide supporting processes for the API:

• rb_requirement: The business entity interface for the applicant requirement API

• rb_requirement_rules: Handles business rules for the API

• rb_requirement_strings: Defines message strings for the API

• dml_rrrareq: Handles data manipulation of the Applicant Requirements Table (RRRAREQ)

• rb_rtvtreq: Supports the Tracking Requirements Validation Table (RTVTREQ)

• rb_rtvtrst: Supports the Tracking Requirements Status Validation Table (RTVTRST)

RRKAREQ

The new RRKAREQ package handles processing previously embedded in requirements tracking forms and processes, and performs functions previously contained in the now obsolete ROK2000 package.

RRKAREQ contains the following procedures:


RTVTRST_TRK_LTR_IND VARCHAR2(1) TRACKING LETTER INDICATOR: Indicates if a requirement with this status should appear on a tracking letter.


Section 8 Applicant Requirements API - TechnicalNew Packages

• p_add_fund_requirements: Adds the tracking requirements associated with an award’s fund code.

• p_delete_fund_requirements: Deletes the tracking requirements associated with an award’s fund code.

• p_finalize_no_update: Performs summary requirement processing, including updating once only requirements and updating satisfy all requirements. The procedure returns the following columns but does not update the RORSTAT record:

• RORSTAT_ALL_REQ_COMP_DATE

• RORSTAT_MEMO_REQ_COMP_DATE

• RORSTAT_PCKG_REQ_COMP_DATE

• RORSTAT_DISB_REQ_COMP_DATE

• RORSTAT_TRK_LTR_IND

• p_finalize_requirements: Performs summary requirement processing, including updating once only requirements, updating satisfy all requirements, and maintaining the following columns in the RORSTAT table

• RORSTAT_ALL_REQ_COMP_DATE

• RORSTAT_MEMO_REQ_COMP_DATE

• RORSTAT_PCKG_REQ_COMP_DATE

• RORSTAT_DISB_REQ_COMP_DATE

• RORSTAT_TRK_LTR_IND

• p_get_reqt: Returns the information from a tracking requirement which exists in a previous year. The tracking requirements must have a null fund code and equal SBGI codes.

• p_get_rrrareq_fund: Returns the information from a tracking requirement with a fund code which exists in a previous year.

• p_get_rrrareq_sbgi: Returns the information from a tracking requirement with a SBGI code which exists in a previous year.

• p_get_rrrareq_treq: Returns the information from a tracking requirement which exists in a previous year.

• p_maintain_group: Deletes tracking requirements associated with the previous tracking group and add the tracking requirements associated with the new tracking group code for the student.

• p_maintain_trk_ltr_ind: Maintains the tracking letter indicator on each individual tracking requirement when the tracking letter indicator on RORSTAT is updated.

• p_pop_rrrareq_trk_ltr_ind: Initializes the tracking letter indicator on each individual tracking requirement when they are null.


Section 8 Applicant Requirements API - Technical Changed Packages

Changed Packages

RPKAWDL

This package uses the new rrkareq.p_delete_fund_requirements packaged procedure to delete requirements associated with the award’s fund code when the award is being deleted. All code made obsolete by the rrkareq.p_delete_fund_requirements packaged procedure has been removed.

RPKAWIU

This package uses the new rrkareq.p_add_fund_requirements packaged procedure to add requirements associated with the award’s fund code when an award is being added or updated. All code made obsolete by the rrkareq.p_add_fund_requirements packaged procedure has been removed.

RPKAWIU uses the new rb_requirement API to satisfy loan application requirements when an award is being added, and uses the new rrkareq.p_finalize_requirements packaged procedure to finalize summary requirement processing.

RPKLOAN

This package uses the new rrkareq.p_add_fund_requirements packaged procedure to add requirements associated with the award’s fund code when an award is being added. All code made obsolete by the rrkareq.p_add_fund_requirements packaged procedure has been removed.

BWRKACPT

This package, which supports Self-Service web processing, uses the new rp_requirement API packaged procedure to update requirements. All code made obsolete by the rp_requirement API has been removed.

Parameter Validation (ROKPVAL)

ROKPVAL has been modified to perform the necessary validation for the population selection (parameters 1, 9, and 10) parameters for the RPRCNCL process.

ROKPVAL has also been modified to perform the necessary parameter validation for the new parameters added to RRREXIT.


Section 8 Applicant Requirements API - TechnicalObsolete Packages

• If parameter 05 (Check for Graduates) is Y, then either parameter 08 (Graduation Term) or parameters 09 and 10 (Graduation Beginning Date and Graduation Ending Date) must be entered.

• If parameter 06 (Check for Withdrawals) is Y, then parameter 11 (Current Term Code) must be entered.

• If parameter 07 (Check for Low Enrollment) is Y, then parameter 11 (Current Term Code) and parameter 12 (Previous Term Code) must be entered.

Obsolete Packages

The following packages have been made obsolete with this release.

• ROK2000.SQL

• RTKTRKL.SQL

New Triggers

Three new triggers have been added to maintain user ID and activity date.

RT_RBBABUD_USERACTIVIT_INSUPD: This new trigger updates user ID and activity date whenever an Applicant Budget record is inserted or updated.

RT_RBRACMP_USERACTIVIT_INSUPD: This new trigger updates user ID and activity date whenever an Applicant Budget Component record is inserted or updated.

RT_RRRAREQ_USERACTIVIT_INSUPD: This new trigger updates user ID and activity date whenever an Applicant Requirements record is inserted or updated.

Three new triggers have been added to enable logging for additional tables. The addition of logging for these tables satisfies RPE 48034.

Note: Logging will not occur for the newly enabled tables unless you explicitly turn on logging for those tables. Go to the Logging Control form (ROALOGC) and check the appropriate checkboxes for each table that you want to activate for logging. For each of these tables, you can choose to log all columns, or you can select individual columns for logging.

RT_RBBABUD_LOG_INSUPDDTL

This new trigger enables logging of the Applicant Budget Table (RBBABUD). The following columns are available for logging:


Section 8 Applicant Requirements API - Technical New Triggers

• RBBABUD_AIDY_CODE

• RBBABUD_PIDM

• RBBABUD_TFC_IND

• RBBABUD_BTYP_CODE

• RBBABUD_USER_ID

• RBBABUD_SYS_IND

• RBBABUD_ACTIVITY_DATE

RT_RBRACMP_LOG_INSUPDDTL

This new trigger enables logging of the Applicant Budget Component Table (RBRACMP). The following columns are available for logging:

• RBRACMP_AIDY_CODE

• RBRACMP_PIDM

• RBRACMP_BTYP_CODE

• RBRACMP_COMP_CODE

• RBRACMP_AMT

• RBRACMP_USER_ID

• RBRACMP_SYS_IND

• RBRACMP_ACTIVITY_DATE

RT_RRRAREQ_LOG_INSUPDDTL

This new trigger enables logging of the Applicant Requirements Table (RRRAREQ). The following columns are available for logging:

• RRRAREQ_AIDY_CODE

• RRRAREQ_PIDM

• RRRAREQ_TREQ_CODE

• RRRAREQ_ACTIVITY_DATE

• RRRAREQ_TREQ_DESC

• RRRAREQ_SAT_IND

• RRRAREQ_STAT_DATE

• RRRAREQ_EST_DATE

• RRRAREQ_TRST_CODE

• RRRAREQ_PCKG_IND

• RRRAREQ_DISB_IND

• RRRAREQ_FUND_CODE


Section 8 Applicant Requirements API - TechnicalNew Triggers

• RRRAREQ_SYS_IND

• RRRAREQ_SBGI_CODE

• RRRAREQ_MEMO_IND

• RRRAREQ_USER_ID

• RRRAREQ_PERK_MPN_EXP_DATE

• RRRAREQ_SATISFIED_DATE

• RRRAREQ_MPN_FIRST_DISB_DATE

• RRRAREQ_MPN_SIGNED_DATE

• RRRAREQ_DATA_ORIGIN

• RRRAREQ_TRK_LTR_IND


Section 8 Applicant Requirements API - Technical New Triggers



Section 9 Miscellaneous Validation Methodology - TechnicalChanged Tables

Section 9 Miscellaneous Validation Methodology - Technical

Changed Tables

Miscellaneous Validation Rules Table (RORMVAL)

The Miscellaneous Validation Rules Table was introduced in Banner 7.3 in preparation for the new Miscellaneous Validation methodology.

For Release 7.3.1, the first data rows have been delivered for the RORMVAL table. These rows support the forms that have adopted the new Miscellaneous Validation methodology for this release. They are listed in Appendix A.

When SCT Banner attempts to verify the valid entries for a particular field, the new Miscellaneous Validation structure will be used. Values will be keyed to the default aid year, and depending upon the year accessed, different values may appear. This consolidation effort will centralize field validation and allow for a more consistent and standardized approach for data display. This approach will also eliminate the need to hard code field value content within the form. This will be especially helpful in the coding for fields which change periodically across aid years.

The structure of the Miscellaneous Validation Rules Table has not changed with this release. The following information is repeated here for your convenience.

The Miscellaneous Validation Rules Table has a unique key comprising four columns: RORMVAL_COLUMN, RORMVAL_CODE, RORMVAL_KEY_1, and RORMVAL_KEY_2.

Column Name Null? Type Description Column Comment

RORMVAL_COLUMN No VARCHAR2(30) Column The column that is being validated.

RORMVAL_KEY_1 VARCHAR2(10) Key 1 The first component in a compound key to uniquely identify the data being validated.

RORMVAL_KEY_2 VARCHAR2(10) Key 2 The second component in a compound key to uniquely identify the data being validated.


Section 9 Miscellaneous Validation Methodology - Technical Changed Tables

As an example, a validated field found on the Need Analysis Processing Form (RNAPR07) is displayed below. Under the new structure, the same RORMVAL column (for example, RCRAPP1_PAR_MRTL_STATUS) will be used for both the EDE and CSS fields. However, instead of having the validation for this field hard-coded onto the form, the Miscellaneous Validation Rules Table will be used to display the valid content for this field. In this example, though the same field is being used, the second key determines the values to display depending upon whether the field is for CSS or EDE. This structure will also be more adaptable to new year changes, and depending upon the aid year, different valid content may display.

RORMVAL_CODE No VARCHAR2(10) Code A valid value.

RORMVAL_DESC No VARCHAR2(30) Description The description of the valid value.

RORMVAL_TRANS_CODE VARCHAR2(10) Translation Code A code into which the valid value can be translated.

RORMVAL_TRANS_COMMENT VARCHAR2(60) Translation Comment A comment explaining the use of the translation code.

RORMVAL_SYSTEM_REQ_IND

No VARCHAR2(1) System Required Indicator

Indicates that this is required data that was delivered and should not be removed or changed.

RORMVAL_DATA_ORIGIN VARCHAR2(30) Data Origin Source system that created or updated the data.

RORMVAL_USER_ID No VARCHAR2(30) User ID The user ID of the person who inserted or last updated this record.

RORMVAL_ACTIVITY_DATE No DATE Activity Date The date that information in this record was entered or last updated.

Column Name Null? Type Description Column Comment

RORMVAL_COLUMN RORMVAL_KEY_1 RORMVAL_KEY_2

RCRAPP1_PAR_MRTL_STATUS 0607 EDE

RORMVAL_CODE RORMVAL_DESC RORMVAL_TRANS_CODE RORMVAL_TRANS_COMMENT

1 Married/remarried 2 CSS RCRAPP1_PAR_MRTL_STATUS

2 Single 1 CSS RCRAPP1_PAR_MRTL_STATUS


Section 9 Miscellaneous Validation Methodology - TechnicalChanged Tables

3 Divorced/separated 5 CSS RCRAPP1_PAR_MRTL_STATUS

4 Widowed 6 CSS RCRAPP1_PAR_MRTL_STATUS



RORMVAL_DATA_ORIGIN RORMVAL_USER_ID RORMVAL_ACTIVITY_DATE

Y Banner USER SYSDATE

RORMVAL_COLUMN RORMVAL_KEY_1 RORMVAL_KEY_2

RCRAPP1_PAR_MRTL_STATUS 0607 CSS


1 Single

2 Married

3 Remarried

4 Separated

5 Divorced

6 Widowed


RORMVAL_DATA_ORIGIN RORMVAL_USER_ID RORMVAL_ACTIVITY_DATE

Y Banner USER SYSDATE


Section 9 Miscellaneous Validation Methodology - Technical New Packages

New Packages

RB_RORMVAL

The new Validation Table package (RB_RORMVAL) supports Miscellaneous Validation processing. The package specification is contained in rokb_rormval0.sql, while the package body is in rokb_rormval1.sql.

The package has three functions. Each of the functions has the same set of four parameters, corresponding to the fields that comprise the unique key of the RORMVAL table. The parameters are p_column, p_key_1, p_key_2, and p_code. The three functions are:

• f_code_exists, which returns Y if the code exists, N if the code does not exist.

• f_get_description, which returns the associated description if the code exists, or null if the code does not exist.

• f_get_translation, which returns the translation value if the code exists, or null if the code does not exist.

Changed Package

ROKSUMM

In the database package ROKSUMM, the calc_fm and calc_im cursors have been modified to use RCRAPP2_MODEL_CDE for the determination of dependency status (I - Independent, D - Dependent).

Changed Libraries

Financial Aid Object Library (ROQOLIB)

To support Miscellaneous Validation, two items have been added to the Financial Aid Object Library:


Section 9 Miscellaneous Validation Methodology - TechnicalChanged Form

• A new Miscellaneous Validation Rules list of values (RORMVAL_LOV)

• A new Miscellaneous Validation Rules record group (RORMVAL_LIST_RG) to populate drop-down lists

Financial Aid PL/SQL Library (ROQRPLS)

The Financial Aid PL/SQL Library has three new procedures that support the Miscellaneous Rules methodology:

• The r$_get_rormval_desc procedure gets a description for a code

• The r$_chck_rormval_code_exists procedure validates that a code exists

• The r$_populate_rormval_list procedure populates drop-down lists

Changed Form

Financial Aid Global Establishment Form (ROQMENU)

In order to implement the Miscellaneous Validation methodology, the following global variables have been created in ROQMENU:

• rormval_column

• rormval_key_1

• rormval_key_2


Section 9 Miscellaneous Validation Methodology - Technical Changed Form



Section 10 Miscellaneous EnhancementsClass Code

Section 10 Miscellaneous Enhancements

Class Code

On the Class Code Translation form (RPRCLSS), the dropdown for the Financial Aid Class field has been modified to allow the option of defining graduate levels of 8 and 9.

Currently, the class codes of 8(second-year graduate/professional) and 9(third-year graduate/professional) are delivered with the U.S. Federal rules and loaded through the RPIFEDR process. These class codes may be batch posted to the student's need analysis record and used in electronic loan processing and in institutional rules for awarding and disbursing aid. The option to translate the Student level and class code to a Financial Aid class of 8 or 9 has now been added to RPRCLSS.

Year in College

The Batch Posting Rules form (RORPOST) and the Batch Posting Process (RORBPST) have been modified to make clear that Banner Year in College (and not Year in College) is the field updated by batch posting.

Students report their year in college on the FAFSA form when applying for U.S. Federal financial aid. This information is loaded into BANNER on the ISIR record via the dataload process and can be viewed on the RNANAxx forms. Beginning with the 2001-2002 aid year, the Year in College field received on the EDE records is converted to Banner Year in College field.

Both fields are displayed on the RNANAxx forms. The Banner Year in College field is used by Financial Aid processes to determine the appropriate financial aid class for the student. The Department of Education uses the Year in College field to approve loan amounts and determine aid eligibility. Schools sometime use Banner Year in College to further define graduate levels for use with electronic loans and/or institutional aid.


Section 10 Miscellaneous Enhancements Year in College



Section 11 Problem ResolutionsExit Interview Requirements

Section 11 Problem Resolutions

This section lists the problem resolutions included in Release 7.3.1.

Exit Interview Requirements

The following problems were resolved through a rewrite of the Exit Interview Requirements Process (RRREXIT). For more details, see “Exit Interview Requirements Process” in Section 4, “Applicant Requirements API - Functional.”

RRREXIT (#103072)Description: The three checks processed by RRREXIT are not executed as specified by the documentation.Client Impact: A specific check may not be processed even if the parameters are deliberately specified for that check.Resolution: The process RRREXIT has been rewritten. The three checks (Graduation, Withdrawal, and Low enrollment) are all mutually exclusive and can be specifically selected via the more complete parameter set.

RRREXIT (#103075)Description: The process flow in RRREXIT does not match its documentation.Client Impact: The process may produce unexpected results even when parameters are specified in accordance with the documentation.Resolution: The process RRREXIT has been rewritten. The parameter set for this process has been made more specific to the functionality available in the process.

RRREXIT (#103428)Description: The process RRREXIT.pc will incorrectly update the tracking letter indicator (RORSTAT_TRK_LTR_IND) and the all requirements complete date (RORSTAT_ALL_REQ_COMP_DATE), even if the exit requirement has previously been satisfied and all other requirements have been previously satisfied.Client Impact: The tracking letter indicator and the all requirements completion date fields may be inconsistent.Resolution: The process RRREXIT has been rewritten. The tracking letter indicator and all of the requirement completion date fields are now handled by the REQUIREMENTS API.

Group Assignment

The following problems were resolved when the new Automatic Group Assignment Process (RORGRPS) was created to replace ROBBGRP. See “Group Assignment


Section 11 Problem Resolutions Group Assignment

Enhancements” in Section 4, “Application Requirements API - Functional,” for more information on RORGRPS.

ROBBGRP (#80916)Description: When Once Only and Satisfy All are checked on RTVTREQ, fund-specific requirements in the current year are not automatically satisfied by the ROBBGRP process if the same non-fund-specific requirement was satisfied in a past year. The functionality works correctly on RRAAREQ.The process ROBBGRP will set the satisfied indicator for a tracking requirement to unsatisfied even if creating a tracking requirement that has been satisfied in a previous aid year and the requirement is set to 'Once only' and 'Satisfy all'.Client Impact: Tracking requirement's satisfied data might become inconsistent and incorrect.Resolution: The process COBOL process ROBBGRP and ROOAUTO have been rewritten in a single C process. The new process takes advantage of the REQUIREMENT API to correctly handle this defect's situation.

ROBBGRP (#85957)Description: When a student is processed twice by ROBBGRP, the tracking letter indicator will be rechecked even is RLRLETR has been run and the tracking letter has been sent.Client Impact: Multiple tracking letters may be incorrectly generated.Resolution: The process ROBBGRP has been rewritten in RORGRPS. RORGRPS takes advantage of the REQUIREMENTS API. The REQUIREMENTS API maintains the tracking letter indicator and will not recheck the indicator even in the case of the process running twice on the same day.

ROBBGRP (#103123)Description: The process ROBBGRP would perform poorly when run for a large population selection.Client Impact: The process ROBBGRP would take unnecessarily long to complete processing. Also the rest of the system may experience slowdown as a result.Resolution: The process ROBBGRP has been rewritten as RORGRPS. RORGRPS has been verified to correctly use all available indexes. Proper SQL tuning has been applied as well as large population selections have been executed in quick succession.

ROBBGRP (#104083)Description: The process ROBBGRP’s output was formatted in a way that could not be viewed correctly on GJIREVO.Client Impact: The output files would need to be reviewed manually.Resolution: The process ROBBGRP has been rewritten in RORGRPS. RORGRPS’s output .lis file is a reformatted version of the output from ROBBGRP. The output created by RORGRPS can easily be viewed on GJIREVO.


Section 11 Problem ResolutionsMiscellaneous Problem Resolutions

Miscellaneous Problem Resolutions

RCBTP06 (#104695) Description: Unnecessary use of call to DUAL to set ID is causing RCBTP06 to fail in some situations/environments. Client Impact: Data Load Part 1 abnormally terminates and no EDE records are loaded.Resolution: Changed EDE Data Load Part 1 to generate ID using direct call to generate-id function. Removed reference to DUAL.

REREX06 (#105647)Description: For Pell only records, COD now requires a complete Address for all domestic and foreign records. Additionally, the nation code must be provided with all foreign addresses. If the address is not complete, you will receive an 021 reject code, Address is Incomplete. This change is retroactive to the 0405 school year to present.Client Impact: Unable to extract Pell records with foreign addresses with a state code as FC.Resolution: The COD extract was modified to translate a FC state code to a blank. For a foreign address a nation code must now be entered on the latest active student address record (SPAIDEN) and a corresponding crosswalk value entered on RTVCDNT for the Pell award to extract. REREXxx retrieves address information as follows:

1. Student having Pell and/or DL loans

• address from highest DL application number for the aid year on RPALORG (including foreign nation code) ELSE

• address from RCRAPP1 (Form RNANAxx)

2. Student having Pell only

• address from RCRAPP1 (Form RNANAxx)

• 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 (spraddr_status_ind IS NULL) and AND current (spraddr_to_date >= sysdate). REREXxx will select the latest record if multiple current/active records exist with a foreign address. The address type is not considered in the selection.(Resolved in Release 7.3.0.2)

REREX06 (#105648)Description: In cases where there is a prior loan period change, direct loan disbursements in edit only accepted status do not extract until another change is made on the loan record.


Section 11 Problem Resolutions Miscellaneous Problem Resolutions

Client Impact: Unable to extract DL disbursements in edit only accepted status that have a prior loan period change without generating another change record on the loan.Resolution: Modified the COD extract process to correctly identify and extract edit only accepted disbursements on loans having a prior loan period change. (Resolved in Release 7.3.0.2)

RERIM06 (#105302)Description: If the school submits a change to the student identifier and either of the following is true—(1) the award year submitted on the change record is lower than the highest award year for the student or (2) for the same award year, if the CPS transaction number on the change record is lower than the highest transaction number for that award year for that student—then COD will ignore the submitted identifier changes and issue warning #116 (SSN, Date of Birth and/or Last Name have NOT been updated in the COD system). From that point on, the COD and Banner identifier data will no longer be in agreement and the COD response files will not load for that student due to the name mismatch. Client Impact: The name mismatch between Banner and COD would prevent importing records into Banner for the affected students. Resolution: When no match is found in RERSTID for SSN, DOB and Last Name, then (A) try to find the relevant student in the database using either DL loan ID for updates to DLPLUS, Sub and Unsub loans or SSN for updates to Pell awards, and(B) insert a new RERSTID record with the SSN, DOB and Last Name from the XML response document. The status of the new record will be A (Accepted) and any previous record in S (Sent) status will also be updated to A (Accepted).

RERIM06 (#105750)Description: The execution script RERIM06.com produces the following error: invalid IF-THEN-ELSE nesting structure or data inconsistency.Client Impact: There is no impact from this DCL error message.Resolution: Modified the DCL execution script RERIM06.com by removing the extraneous ENDIF keyword from the section used to execute RERIMEX.

robj70000.sql, robj70100.sql

(#105885)Description: The robj70000.sql and robj70100.sql scripts from the Banner Financial Aid 7.0 and 7.1 Upgrades are missing ROALOGC, ROILOGA, RORMESG records to be inserted into GUBOBJS table.Client Impact: These objects appear in the Banner system without description.Resolution: The GUBOBJS records for these objects are being delivered in 7.3.1.

RPEPELL (#104841)Description: On Linux platforms running Fujitsu NetCobol, calculations using complex COMPUTE statements are yielding incorrect results. This affects both Pell and non-Pell award amounts, term award amounts, term percentage calculations, and disbursement memo, authorization, and paid amounts.Client Impact: Students' awards and disbursements may be incorrect. Resolution: Modify copybooks UAARTN, UAADECL, UCPRTN and UCPDECL used by the RPEPELL Pell Award Calculation, the RPEPCKG Packaging process and


Section 11 Problem ResolutionsMiscellaneous Problem Resolutions

the RPEDISB Disbursement process to correct the calculations of awards and term percentages. Modify the RPEPCKG and RPEDISB processes to correct additional calculations which affect packaged award amounts and the calculation of memo, authorization and paid amounts.

RPEPELL (#103661)Description: When a Pell award is partially used at another institution, and the Pell fund within Banner is set to Round Cents (RC), the Banner calculation of the other school amount may be less than the actual amount used at the other institution, causing the remaining amount calculated by Banner to exceed the student's eligibility. For example, a student receives $3038 of a $4050 award at another school. The NSLDS Percent Schedule Used is calculated at 75.01%. Banner will calculate the other school amount as $3037.91, calculating a remaining Pell Grant of $1012.09. This exceeds the allowable maximum by 9 cents.Client Impact: Since the total awarded and paid to the student exceeds the maximum eligible Pell award by 9 cents, COD will reject the award and disbursement records.Resolution: The UCPRTN Pell Calculation routine used by RPEPELL and RPEDISB has been modified. Instead of calculating the Other School Amount based on the rounding indicator set within Banner, it will calculate amounts both rounded to dollars and rounded to cents, and will take the larger of these amounts as the Other School Amount. This will prevent the remaining amount calculated for the Banner award from exceeding the maximum allowable Pell award.

RPKLOAN1 (#104538)Description: Under certain conditions, RPRELAP incorrectly uses the default enrollment instead of the actual enrollment when creating the student's loan application. This will occur when a student has a SARADAP record for a prior term with a level code that is different from the level code on the SGBSTDN record in effect for first term in the student's loan period. Client Impact: Must manually maintain enrollment status under these conditions.Resolution: Removed the check for an admissions application when calculating enrollment status.

RPRELAP (#104989)Description: If a student's citizenship status on RNANAXX is 3 (neither 1 nor 2, ineligible), RPRELAP will create the electronic loan application with the same status. A citizenship status of 3 is invalid with CommonLine.Client Impact: A record with a student citizenship status of 3 will be rejected.Resolution: The process RPRELAP.pc was modified to DECODE() a value of 3 on RCRAPP1_CITZ_IND to NULL when creating the application. All other values are left as is (1, 2, and NULL). If a student's citizenship status is 3 on RNANAXX, RPRELAP will now create the electronic loan application with a null citizenship status to allow the correct processing for CommonLine records.

RRAAREQ (#103778) Description: The error A valid Code must be entered for this function is encountered when attempting to save an Effective Date or Satisfied Indicator update to a


Section 11 Problem Resolutions Miscellaneous Problem Resolutions

Promissory Note on the Non-Coded Requirements block of RRAAREQ. This error only occurs when the applicant does not have a tracking group assigned and no other requirements.Client Impact: Can't update record.Resolution: RRAAREQ was modified as part of RB_REQUIREMENT API specification to remove this edit.


Appendix A SeRequired Data

October 2005 111 Confidential

Append

Required

This append L). See Section 9, “Miscellaneous Validation M iscellaneous Validation Methodolog

ues for the RMVAL_ACTIVITY_DATE fields. In The other columns—DESC, RORMVAL_TRANS_CODE, and

Activity Date

SYSDATE

ed Data for Miscellaneous Validation Methodology

Financial Aid Release 7.3.1 Release Guide

ix A Seed Data

Data for Miscellaneous Validation Metholology

ix lists the required data delivered with this release for the Miscellaneous Validation Table (RORMVAethodology - Technical” for the details of RORMVAL’s table structure. This data supports the new My, which is described in Section 5.

Note: The required data for the RORMVAL Table contains the following common valRORMVAL_SYSTEM_REQ_IND, RORMVAL_DATA_ORIGIN, RORMVAL_USER_ID, and ROother words, these same values apply for all rows in this Required Data section. RORMVAL_COLUMN, RORMVAL_KEY_1, RORMVAL_KEY_2, RORMVAL_CODE, RORMVAL_RORMVAL_TRANS_COMMENT—vary for each required data row.

System Required Indicator Data Origin User ID

Y Banner USER

Appendix ARequired D


Columnanslation de Translation Comment

ATTEND_C

ATTEND_C

ATTEND_C

BPST_RCR RCRAPP3_YR_IN_COLL_2










EDE_ELIG CSS RCRAPP2_ELIGIBILITY_MSG

FED_HOUS RCRAPP1_INST_HOUS_CDE

Seed Data ata for Miscellaneous Validation Methodology


Key 1 Key 2 Code DescriptionTrCo

OLL 0607 0 No, will not attend

OLL 0607 1 Yes, Full time

OLL 0607 2 Yes, Half time

APP1_YR_IN_COLL 0607 0 Beyond 3rd yr grad 7

APP1_YR_IN_COLL 0607 1 1st yr/no college 0

APP1_YR_IN_COLL 0607 2 1st yr/some college 1

APP1_YR_IN_COLL 0607 3 2nd yr/sophomore 2

APP1_YR_IN_COLL 0607 4 3rd yr/junior 3

APP1_YR_IN_COLL 0607 5 4th yr/senior 4

APP1_YR_IN_COLL 0607 6 5th yr/oth undergrad 5

APP1_YR_IN_COLL 0607 7 1st yr grad/prof 6

APP1_YR_IN_COLL 0607 8 2nd yr grad/prof 7

APP1_YR_IN_COLL 0607 9 3rd yr grad/prof 7

IBILITY_MSG 0607 Y C flag set 1

_CDE 0607 1 On campus 2



FED_HOUS_C RCRAPP1_INST_HOUS_CDE

FED_HOUS_C RCRAPP1_INST_HOUS_CDE

HOUS_CDE RCRAPP1_INST_HOUS_CDE




INAR_METHO ANLY_TYPE



POST_SCREE

POST_SCREE

POST_SCREE

POST_SCREE

POST_SCREE

POST_SCREE

POST_SCREE

Columnation

Translation Comment



DE 0607 2 Off-campus 3

DE 0607 3 With parent 1

0607 1 Campus housing 2

0607 2 Off-campus 3

0607 3 With parents 1

0607 4 With relatives 4

D 0607 B Zero EFC 1

D 0607 R Regular 3

D 0607 S Simple 2

N_RSN_CDE 0607 01 Default added

N_RSN_CDE 0607 02 Overpayment added

N_RSN_CDE 0607 03 Default resolved

N_RSN_CDE 0607 04 Overpayment resolved

N_RSN_CDE 0607 05 MPN status change

N_RSN_CDE 0607 06 Loan into discharged status

N_RSN_CDE 0607 07 Loan out of discharged status

Key 1 Key 2 Code DescriptionTranslCode



POST_SCR

POST_SCR

POST_SCR

POST_SCR

POST_SCR

POST_SCR

POST_SCR

POST_SCR

POST_SCR

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_




EEN_RSN_CDE 0607 08 Closed school

EEN_RSN_CDE 0607 09 Exceeded subsidized loan limit

EEN_RSN_CDE 0607 10 Exceeded combined loan limit

EEN_RSN_CDE 0607 11 Doesn't exceed sub loan status

EEN_RSN_CDE 0607 12 Doesn't exceed comb loan limit

EEN_RSN_CDE 0607 13 Change in discharged loan type

EEN_RSN_CDE 0607 14 Loan entered active bankruptcy

EEN_RSN_CDE 0607 15 PLUS MPN status change

EEN_RSN_CDE 0607 99 Other

BORN_BEFORE_1_1_XX 0607 1 Yes

BORN_BEFORE_1_1_XX 0607 2 No

CITZ_IND 0607 1 U.S. citizen or U.S. national

CITZ_IND 0607 2 Eligible noncitizen

CITZ_IND 0607 3 Neither 1 nor 2, not eligible

DEGREE_BY_JULY 0607 1 Yes

DEGREE_BY_JULY 0607 2 No




RCRAPP1_EX

RCRAPP1_EX

RCRAPP1_EX

RCRAPP1_EX

RCRAPP1_EX

RCRAPP1_HA

RCRAPP1_HA

RCRAPP1_IN

RCRAPP1_IN

RCRAPP1_IN

RCRAPP1_IN

RCRAPP1_IN

RCRAPP1_IN

RCRAPP1_MR RCRAPP3_MARRIED



Columnation

Translation Comment



P_ENROLL_STATUS 0607 1 Full time

P_ENROLL_STATUS 0607 2 3/4 Time

P_ENROLL_STATUS 0607 3 1/2 Time

P_ENROLL_STATUS 0607 4 Less than 1/2 time

P_ENROLL_STATUS 0607 5 Not sure

S_LEGAL_DEPEND 0607 1 Yes

S_LEGAL_DEPEND 0607 2 No

S 0607 N Citizenship not confirmed

S 0607 Y Citizenship confirmed

ST_HOUS_CDE 0607 1 Commuter with parents

ST_HOUS_CDE 0607 2 Campus housing

ST_HOUS_CDE 0607 3 Off campus

ST_HOUS_CDE 0607 4 Commuter with relatives

TL_STATUS 0607 1 Unmarried 2

TL_STATUS 0607 2 Married/remarried 1

TL_STATUS 0607 3 Separated 2




RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_ CSS RCRAPP1_PAR_MRTL_STATUS




RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_




PAR_DIV_SEP_REM_IND 0607 1 Yes

PAR_MRTL_STATUS 0607 CSS 1 Single

PAR_MRTL_STATUS 0607 CSS 2 Married

PAR_MRTL_STATUS 0607 CSS 3 Remarried

PAR_MRTL_STATUS 0607 CSS 4 Separated

PAR_MRTL_STATUS 0607 CSS 5 Divorced

PAR_MRTL_STATUS 0607 CSS 6 Widowed

PAR_MRTL_STATUS 0607 EDE 1 Married/remarried 2

PAR_MRTL_STATUS 0607 EDE 2 Single 1

PAR_MRTL_STATUS 0607 EDE 3 Divorced/separated 5

PAR_MRTL_STATUS 0607 EDE 4 Widowed 6

PAR_TAX_FORM_IND 0607 CSS 01 Estimated 1040

PAR_TAX_FORM_IND 0607 CSS 02 Estimated 1040A

PAR_TAX_FORM_IND 0607 CSS 03 Estimated 1040EZ

PAR_TAX_FORM_IND 0607 CSS 04 Estimated Canadian

PAR_TAX_FORM_IND 0607 CSS 05 Estimated Puerto Rican




RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA

RCRAPP1_PA CSS RCRAPP1_PAR_TAX_FORM_IND




RCRAPP1_PE

RCRAPP1_PE

RCRAPP1_RQ

RCRAPP1_RQ

Columnation

Translation Comment



R_TAX_FORM_IND 0607 CSS 06 Estimated other non-U.S.

R_TAX_FORM_IND 0607 CSS 07 Completed 1040

R_TAX_FORM_IND 0607 CSS 08 Completed 1040A

R_TAX_FORM_IND 0607 CSS 09 Completed 1040EZ

R_TAX_FORM_IND 0607 CSS 10 Completed Canadian

R_TAX_FORM_IND 0607 CSS 11 Completed Puerto Rican

R_TAX_FORM_IND 0607 CSS 12 Completed other non-U.S.

R_TAX_FORM_IND 0607 CSS 13 Will not file

R_TAX_FORM_IND 0607 EDE 1 1040 07

R_TAX_FORM_IND 0607 EDE 2 1040A or 1040EZ 08

R_TAX_FORM_IND 0607 EDE 3 Foreign tax return 12

R_TAX_FORM_IND 0607 EDE 4 Other 11

RMIT_DRAFT_REG 0607 1 Yes

RMIT_DRAFT_REG 0607 2 No

ST_FA_FALL_THIS_YR 0607 1 Full time

ST_FA_FALL_THIS_YR 0607 2 3/4 Time




RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_




RQST_FA_FALL_THIS_YR 0607 3 1/2 Time

RQST_FA_FALL_THIS_YR 0607 4 Less than 1/2 time

RQST_FA_FALL_THIS_YR 0607 5 Not attending

RQST_FA_SPRING_NEXT_YR 0607 1 Full time

RQST_FA_SPRING_NEXT_YR 0607 2 3/4 Time

RQST_FA_SPRING_NEXT_YR 0607 3 1/2 Time

RQST_FA_SPRING_NEXT_YR 0607 4 Less than 1/2 time

RQST_FA_SPRING_NEXT_YR 0607 5 Not attending

RQST_FA_SUMMER_NEXT_YR 0607 1 Full time

RQST_FA_SUMMER_NEXT_YR 0607 2 3/4 Time

RQST_FA_SUMMER_NEXT_YR 0607 3 1/2 Time

RQST_FA_SUMMER_NEXT_YR 0607 4 Less than 1/2 time

RQST_FA_SUMMER_NEXT_YR 0607 5 Not attending

RQST_FA_SUMMER_THIS_YR 0607 1 Full time

RQST_FA_SUMMER_THIS_YR 0607 2 3/4 Time

RQST_FA_SUMMER_THIS_YR 0607 3 1/2 Time




RCRAPP1_RQ

RCRAPP1_RQ

RCRAPP1_RQ

RCRAPP1_RQ

RCRAPP1_RQ

RCRAPP1_RQ

RCRAPP1_RQ

RCRAPP1_SI

RCRAPP1_SI

RCRAPP1_SI

RCRAPP1_TA

RCRAPP1_TA

RCRAPP1_TA

RCRAPP1_TA

RCRAPP1_TA

RCRAPP1_TA

Columnation

Translation Comment



ST_FA_SUMMER_THIS_YR 0607 4 Less than 1/2 time

ST_FA_SUMMER_THIS_YR 0607 5 Not attending

ST_FA_WINTER_NEXT_YR 0607 1 Full time

ST_FA_WINTER_NEXT_YR 0607 2 3/4 Time

ST_FA_WINTER_NEXT_YR 0607 3 1/2 Time

ST_FA_WINTER_NEXT_YR 0607 4 Less than 1/2 time

ST_FA_WINTER_NEXT_YR 0607 5 Not attending

GNED 0607 A Applicant only

GNED 0607 B Applicant and parent

GNED 0607 P Parent only

X_FORM_IND 0607 CSS 01 Estimated 1040

X_FORM_IND 0607 CSS 02 Estimated 1040A

X_FORM_IND 0607 CSS 03 Estimated 1040EZ

X_FORM_IND 0607 CSS 04 Estimated Canadian

X_FORM_IND 0607 CSS 05 Estimated Puerto Rican

X_FORM_IND 0607 CSS 06 Estimated other non-U.S.




RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_ CSS RCRAPP1_TAX_FORM_IND




RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_

RCRAPP1_ RCRAPP3_GRAD_OR_PROF




TAX_FORM_IND 0607 CSS 07 Completed 1040

TAX_FORM_IND 0607 CSS 08 Completed 1040A

TAX_FORM_IND 0607 CSS 09 Completed 1040EZ

TAX_FORM_IND 0607 CSS 10 Completed Canadian

TAX_FORM_IND 0607 CSS 11 Completed Puerto Rican

TAX_FORM_IND 0607 CSS 12 Completed other non-U.S.

TAX_FORM_IND 0607 CSS 13 Will not file

TAX_FORM_IND 0607 EDE 1 1040 07

TAX_FORM_IND 0607 EDE 2 1040A or 1040EZ 08

TAX_FORM_IND 0607 EDE 3 Foreign tax return 12

TAX_FORM_IND 0607 EDE 4 Other 11

US_VET 0607 1 Yes

US_VET 0607 2 No

WARD_OF_COURT 0607 1 Yes

WARD_OF_COURT 0607 2 No

YR_IN_COLL 0607 0 Beyond 3rd yr grad 1




RCRAPP1_YR RCRAPP3_GRAD_OR_PROF









RCRAPP2_C_

RCRAPP2_C_

RCRAPP2_C_

RCRAPP2_C_

RCRAPP2_C_

RCRAPP2_C_ RCRAPP2_MODEL_CDE

RCRAPP2_C_ RCRAPP2_MODEL_CDE

Columnation

Translation Comment



_IN_COLL 0607 1 1st yr/no college 2

_IN_COLL 0607 2 1st yr/some college 2

_IN_COLL 0607 3 2nd yr/sophomore 2

_IN_COLL 0607 4 3rd yr/junior 2

_IN_COLL 0607 5 4th yr/senior 2

_IN_COLL 0607 6 5th yr/oth undergrad 2

_IN_COLL 0607 7 1st yr grad/prof 1

_IN_COLL 0607 8 2nd yr grad/prof 1

_IN_COLL 0607 9 3rd yr grad/prof 1

1_ANLY_TYPE 0607 1 Zero EFC

1_ANLY_TYPE 0607 2 Simple

1_ANLY_TYPE 0607 3 Regular

1_CTRB_OFFL_EST 0607 1 Official

1_CTRB_OFFL_EST 0607 2 Estimated

DEPEND_STATUS 0607 1 Independent I

DEPEND_STATUS 0607 2 Dependent D




RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_

RCRAPP2_




C_PAR_1_ANLY_TYPE 0607 1 Zero EFC

C_PAR_1_ANLY_TYPE 0607 2 Simple

C_PAR_1_ANLY_TYPE 0607 3 Regular

C_PAR_1_CTRB_OFFL_EST 0607 1 Official

C_PAR_1_CTRB_OFFL_EST 0607 2 Estimated

ELIGIBILITY_MSG 0607 1 C flag set

IM_1_ANLY_TYPE 0607 1 Zero EFC

IM_1_ANLY_TYPE 0607 2 Simple

IM_1_ANLY_TYPE 0607 3 Regular

IM_1_PAR_ANLY_TYPE 0607 1 Zero EFC

IM_1_PAR_ANLY_TYPE 0607 2 Simple

IM_1_PAR_ANLY_TYPE 0607 3 Regular

MODEL_CDE 0607 D Dependent

MODEL_CDE 0607 I Independent

PELL_PGI_OFFL_EST 0607 1 Official

PELL_PGI_OFFL_EST 0607 2 Estimated




RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_DE

RCRAPP3_EF

RCRAPP3_FA

RCRAPP3_FA

RCRAPP3_FA

RCRAPP3_FA

RCRAPP3_FA

Columnation

Translation Comment



GREE_TYPE 0607 1 1st bachelor's degree

GREE_TYPE 0607 2 2nd bachelor's degree

GREE_TYPE 0607 3 Associate degree (technical)

GREE_TYPE 0607 4 Assoc deg (gen ed or trans)

GREE_TYPE 0607 5 Cert/diploma (less 2 years)

GREE_TYPE 0607 6 Cert/diploma (2 or more yrs)

GREE_TYPE 0607 7 Teaching cred (nondegree)

GREE_TYPE 0607 8 Grad/professional

GREE_TYPE 0607 9 Other/undecided

C_RECALC_CORR_REQ 0607 1 Yes

TH_SSN_MATCH 0607 1 No match on SSN

TH_SSN_MATCH 0607 2 SSN and name match

TH_SSN_MATCH 0607 3 SSN match, no match on name

TH_SSN_MATCH 0607 4 SSN, name, and DOB match

TH_SSN_MATCH 0607 5 SSN, name, DOB match with DOD




RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_

RCRAPP3_




FATH_SSN_MATCH 0607 8 Record not sent to SSA

FATHER_HI_GRADE 0607 1 Middle school/junior high

FATHER_HI_GRADE 0607 2 High school

FATHER_HI_GRADE 0607 3 College or beyond

FATHER_HI_GRADE 0607 4 Other/unknown

GRAD_OR_PROF 0607 1 Yes

GRAD_OR_PROF 0607 2 No

LIVE_ON_FARM 0607 1 Yes

LIVE_ON_FARM 0607 2 No

MARRIED 0607 1 Yes

MARRIED 0607 2 No

MOTH_SSN_MATCH 0607 1 No match on SSN

MOTH_SSN_MATCH 0607 2 SSN and name match

MOTH_SSN_MATCH 0607 3 SSN match, no match on name

MOTH_SSN_MATCH 0607 4 SSN, name, and DOB match




RCRAPP3_MO

RCRAPP3_MO

RCRAPP3_MO

RCRAPP3_MO

RCRAPP3_MO

RCRAPP3_MO

RCRAPP3_OF

RCRAPP3_OF

RCRAPP3_PA

RCRAPP3_PA

RCRAPP3_PR

RCRAPP3_SO

RCRAPP3_SO

RCRAPP3_SO

RCRAPP3_SO

Columnation

Translation Comment



TH_SSN_MATCH 0607 5 SSN, name, DOB match with DOD

TH_SSN_MATCH 0607 8 Record not sent to SSA

THER_HI_GRADE 0607 1 Middle school/junior high

THER_HI_GRADE 0607 2 High school

THER_HI_GRADE 0607 3 College or beyond

THER_HI_GRADE 0607 4 Other/unknown

FL_UNOFFL_IND 0607 1 Official

FL_UNOFFL_IND 0607 2 Unofficial

R_LIVE_ON_FARM 0607 1 Yes

R_LIVE_ON_FARM 0607 2 No

EPARER_SIGN 0607 1 Yes

C_SEC 0607 1 No match on SSN

C_SEC 0607 2 SSN and name match

C_SEC 0607 3 SSN match, no match on name

C_SEC 0607 4 SSN, name and DOB match




RCRAPP3_

RCRAPP3_

RCRAPP3_ RCRAPP1_YR_IN_COLL








RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_




SOC_SEC 0607 5 SSN, name, DOB match with DOD

SOC_SEC 0607 8 Record not sent to SSA

YR_IN_COLL_2 0607 0 1st time freshman, no prior 1

YR_IN_COLL_2 0607 1 Freshman, prior college 2

YR_IN_COLL_2 0607 2 Sophomore (2nd yr undergrad) 3

YR_IN_COLL_2 0607 3 Junior (3rd year undergrad) 4

YR_IN_COLL_2 0607 4 Senior (4th year undergrad) 5

YR_IN_COLL_2 0607 5 5th year/other undergrad 6

YR_IN_COLL_2 0607 6 1st yr grad/professional 7

YR_IN_COLL_2 0607 7 Con't grad/prof or beyond 0

1040A_ELIG_IND 0607 1 Yes

1040A_ELIG_IND 0607 2 No

1040A_ELIG_IND 0607 3 Don't know

C_INST_1_TFC_OFFL_EST 0607 1 Official

C_INST_1_TFC_OFFL_EST 0607 2 Estimated




RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

RCRAPP4_C_

Columnation

Translation Comment



NA_1_ANLY_TYPE 0607 1 Zero EFC

NA_1_ANLY_TYPE 0607 2 Simple

NA_1_ANLY_TYPE 0607 3 Regular

NA_1_CTRB_OFFL_EST 0607 1 Official

NA_1_CTRB_OFFL_EST 0607 2 Estimated

NA_1_P_ANLY_TYPE 0607 1 Zero EFC

NA_1_P_ANLY_TYPE 0607 2 Simple

NA_1_P_ANLY_TYPE 0607 3 Regular

NA_1_P_CTRB_OFFL_EST 0607 1 Official

NA_1_P_CTRB_OFFL_EST 0607 2 Estimated

NA_1_PELL_OFFL_EST 0607 1 Official

NA_1_PELL_OFFL_EST 0607 2 Estimated

NA_2_ANLY_TYPE 0607 1 Zero EFC

NA_2_ANLY_TYPE 0607 2 Simple

NA_2_ANLY_TYPE 0607 3 Regular

NA_2_P_ANLY_TYPE 0607 1 Zero EFC




RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_




C_NA_2_P_ANLY_TYPE 0607 2 Simple

C_NA_2_P_ANLY_TYPE 0607 3 Regular

DRUG_OFFENSE_CONVIC 0607 1 Eligible

DRUG_OFFENSE_CONVIC 0607 2 Part year eligible

DRUG_OFFENSE_CONVIC 0607 3 Ineligible/don't know

FEE_WAIVER_IND 0607 1 Yes

FEE_WAIVER_IND 0607 2 No

HAVE_CHILDREN 0607 1 Yes

HAVE_CHILDREN 0607 2 No

HS_GED_RCVD 0607 1 Yes

HS_GED_RCVD 0607 2 No

LEGAL_RES_IND 0607 1 Yes

LEGAL_RES_IND 0607 2 No

LOAN_INT 0607 1 Yes

LOAN_INT 0607 2 No

PAR_1040A_ELIG_IND 0607 1 Yes




RCRAPP4_PA

RCRAPP4_PA

RCRAPP4_PA

RCRAPP4_PA

RCRAPP4_PA

RCRAPP4_PA

RCRAPP4_PA

RCRAPP4_SE

RCRAPP4_SE

RCRAPP4_SE

RCRAPP4_SE

RCRAPP4_SE

RCRAPP4_SS

RCRAPP4_SS

RCRAPP4_SS

RCRAPP4_SS

Columnation

Translation Comment



R_1040A_ELIG_IND 0607 2 No

R_1040A_ELIG_IND 0607 3 Don't know

R_LEGAL_RES_IND 0607 1 Yes

R_LEGAL_RES_IND 0607 2 No

R_TX_RET_FILED_IND 0607 1 Already completed

R_TX_RET_FILED_IND 0607 2 Will file

R_TX_RET_FILED_IND 0607 3 Will not file

C_INS_MATCH_IND 0607 C DHS has not yet confirmed

C_INS_MATCH_IND 0607 N DHS did not confirm

C_INS_MATCH_IND 0607 P Pending results

C_INS_MATCH_IND 0607 X Not enough information

C_INS_MATCH_IND 0607 Y Citizenship status confirmed

_MATCH 0607 N Reg status not confirmed

_MATCH 0607 T Temporarily exempt

_MATCH 0607 Y Registration status confirmed

_REG_FLAG 0607 N Registration not completed




RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_

RCRAPP4_




SS_REG_FLAG 0607 T Temporarily exempt

SS_REG_FLAG 0607 Y Registration completed

SSA_CITIZEN_IND 0607 * Foreign born

SSA_CITIZEN_IND 0607 A U.S. citizen

SSA_CITIZEN_IND 0607 B Legal alien, eligible to work

SSA_CITIZEN_IND 0607 C Legal alien, not work elig

SSA_CITIZEN_IND 0607 D Other

SSA_CITIZEN_IND 0607 E Alien, stu rest, work auth

SSA_CITIZEN_IND 0607 F Conditionally legalized alien

SSA_CITIZEN_IND 0607 N Unable to verify citizenship

TX_RET_FILED_IND 0607 1 Already completed

TX_RET_FILED_IND 0607 2 Will file

TX_RET_FILED_IND 0607 3 Will not file

VA_MATCH_FLAG 0607 1 Veteran status confirmed

VA_MATCH_FLAG 0607 2 Rec found, not qualify vet

VA_MATCH_FLAG 0607 3 Record not found




RCRAPP4_VA

RCRAPP4_VA

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_VI

RCRAPP4_WO

RCRAPP4_WO

RCRESAR_DE CSS RCRAPP2_C_DEPEND_STATUS



Columnation

Translation Comment



_MATCH_FLAG 0607 4 Record found, active duty

_MATCH_FLAG 0607 8 Record not sent to VA

SA_CLASS 0607 1 F1

SA_CLASS 0607 2 F2

SA_CLASS 0607 3 J1

SA_CLASS 0607 4 J2

SA_CLASS 0607 5 G1

SA_CLASS 0607 6 G2

SA_CLASS 0607 7 G3

SA_CLASS 0607 8 G4

SA_CLASS 0607 9 Other

RK_STUDY 0607 1 Yes

RK_STUDY 0607 2 No

P_INDEP_IND 0607 D Dependent, EFC provided 1

P_INDEP_IND 0607 I Independent, EFC provided 2

P_INDEP_IND 0607 X Dependent rejected, no EFC 1




RCRESAR_ CSS RCRAPP2_C_DEPEND_STATUS

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_

RCRIMP1_




DEP_INDEP_IND 0607 Y Independent rejected, no EFC 2

FIN_AID_STATUS 0607 1 1st time, entering

FIN_AID_STATUS 0607 2 Renewal, continuing

FIN_AID_STATUS 0607 3 1st time, continuing

LOCATION_COMPUTER 0607 1 Home

LOCATION_COMPUTER 0607 2 Father's work

LOCATION_COMPUTER 0607 3 Mother's work

LOCATION_COMPUTER 0607 4 High school

LOCATION_COMPUTER 0607 5 College

LOCATION_COMPUTER 0607 6 Library

LOCATION_COMPUTER 0607 7 Community center

LOCATION_COMPUTER 0607 8 Friend's or relative's house

LOCATION_COMPUTER 0607 9 Other

PAR_NTRL_SEP_DIV 0607 1 Yes

PAR_NTRL_SEP_DIV 0607 2 No

PAR_OWN_BUS_FARM 0607 1 Yes




RCRIMP1_PA

RCRIMP1_ST

RCRIMP1_ST

RCRIMP1_ST

RCRIMP1_ST

RCRIMP1_ST

RCRIMP1_TR

RCRIMP1_TR

RCRIMP1_TR

RCRIMP1_TR

RCRLDS4_AG

RCRLDS4_AG

RCRLDS4_AG

RCRLDS4_AG

RCRLDS4_AG

RCRLDS4_AG

Columnation

Translation Comment



R_OWN_BUS_FARM 0607 2 No

U_LIVES_WITH 0607 1 Father

U_LIVES_WITH 0607 2 Mother

U_LIVES_WITH 0607 3 Neither parent

U_MOST_SUPPORT_FROM 0607 1 Father

U_MOST_SUPPORT_FROM 0607 2 Mother

UST_AVAIL_IND 0607 1 Yes

UST_AVAIL_IND 0607 2 No

UST_ESTAB_BY 0607 1 Parents

UST_ESTAB_BY 0607 2 Other

T_OVER_LIMIT_COMB 0607 C Close to or equal to limit

T_OVER_LIMIT_COMB 0607 E Exceeded limit

T_OVER_LIMIT_COMB 0607 N No problem

T_OVER_LIMIT_SUB 0607 C Close to or equal to limit

T_OVER_LIMIT_SUB 0607 E Exceeded limit

T_OVER_LIMIT_SUB 0607 N No problem




RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_




DISCHARG_LOAN_FLG 0607 C Conditional

DISCHARG_LOAN_FLG 0607 D Death

DISCHARG_LOAN_FLG 0607 M Multiple

DISCHARG_LOAN_FLG 0607 N None

DISCHARG_LOAN_FLG 0607 P Permanent

DISCHARG_LOAN_FLG 0607 R Reaffirmed

DL_MPN_FLAG 0607 A Active

DL_MPN_FLAG 0607 C Closed

DL_MPN_FLAG 0607 I Inactive

DL_MPN_FLAG 0607 N No MPN on file

DL_PLUS_MPN_FLAG 0607 A Active

DL_PLUS_MPN_FLAG 0607 C Closed

DL_PLUS_MPN_FLAG 0607 I Inactive

DL_PLUS_MPN_FLAG 0607 N No MPN on file

MATCH_IND 0607 1 Not in default or overpayment

MATCH_IND 0607 2 Default




RCRLDS4_MA

RCRLDS4_MA

RCRLDS4_MA

RCRLDS4_MA

RCRLDS4_NS

RCRLDS4_NS

RCRLDS4_NS

RCRLDS4_NS

RCRLDS4_NS

RCRLDS4_PE

RCRLDS4_PE

RCRLDS4_PE

RCRLDS4_PE

RCRLDS4_PE

RCRLDS4_PE

RCRLDS4_PE

Columnation

Translation Comment



TCH_IND 0607 3 Overpayment

TCH_IND 0607 4 Default and overpayment

TCH_IND 0607 7 Match but no data provided

TCH_IND 0607 8 Record not sent to NSLDS

LDS_DB_RESULT_FLAG 0607 1 Record matched, data sent

LDS_DB_RESULT_FLAG 0607 2 Name or DOB no match

LDS_DB_RESULT_FLAG 0607 3 SSN not found in NSLDS

LDS_DB_RESULT_FLAG 0607 4 Full match, no data to send

LDS_DB_RESULT_FLAG 0607 5 Real-time transaction not sent

LL_OVER_PAY_FLAG 0607 D Deferred

LL_OVER_PAY_FLAG 0607 N N/A

LL_OVER_PAY_FLAG 0607 S Satisfactory pay arrangements

LL_OVER_PAY_FLAG 0607 W Waived

LL_OVER_PAY_FLAG 0607 Y Overpayment

RK_OVER_PAY_FLG 0607 D Deferred

RK_OVER_PAY_FLG 0607 N N/A




RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS4_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_




PERK_OVER_PAY_FLG 0607 S Satisfactory pay arrangements

PERK_OVER_PAY_FLG 0607 W Waived

PERK_OVER_PAY_FLG 0607 Y Overpayment

SEOG_OVER_PAY_FLAG 0607 D Deferred

SEOG_OVER_PAY_FLAG 0607 N N/A

SEOG_OVER_PAY_FLAG 0607 S Satisfactory pay arrangements

SEOG_OVER_PAY_FLAG 0607 W Waived

SEOG_OVER_PAY_FLAG 0607 Y Overpayment

CONTACT_TYPE 0607 DDP Disability data provider

CONTACT_TYPE 0607 DLS Direct Loan servicer

CONTACT_TYPE 0607 ERD ED region

CONTACT_TYPE 0607 GA Guaranty agency

CONTACT_TYPE 0607 LEN Lender

CONTACT_TYPE 0607 LNS Lender servicer

CONTACT_TYPE 0607 N/A Not applicable

CONTACT_TYPE 0607 RDS CDDTS Repayment Servicing




RCRLDS6_CO

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

Columnation

Translation Comment



NTACT_TYPE 0607 SCH School

R_STAT_CD 0607 AL Abandoned loan

R_STAT_CD 0607 BC Bankruptcy claim, discharged

R_STAT_CD 0607 BK Bankruptcy claim, active

R_STAT_CD 0607 CA Cancelled

R_STAT_CD 0607 CS Closed school discharge

R_STAT_CD 0607 DA Deferred

R_STAT_CD 0607 DB Defaulted, bankrupt, active

R_STAT_CD 0607 DC Defaulted, compromise

R_STAT_CD 0607 DD Defaulted, then died

R_STAT_CD 0607 DE Death

R_STAT_CD 0607 DF Defaulted, unresolved

R_STAT_CD 0607 DI Disability

R_STAT_CD 0607 DK Defaulted, bankrupt, dischrged

R_STAT_CD 0607 DL Defaulted, in Litigation

R_STAT_CD 0607 DN Def., Paid in Full Con. Loan




RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_




DIR_STAT_CD 0607 DO Def., bankrupt, active, other

DIR_STAT_CD 0607 DP Defaulted, Then Paid in Full

DIR_STAT_CD 0607 DR Defaulted Loan in Roll-up Loan

DIR_STAT_CD 0607 DS Defaulted, then disabled

DIR_STAT_CD 0607 DT Defaulted, collection termntd

DIR_STAT_CD 0607 DU Defaulted, unresolved

DIR_STAT_CD 0607 DW Defaulted, write-off

DIR_STAT_CD 0607 DX Defaulted, SA, 6c payments

DIR_STAT_CD 0607 DZ Defaulted, 6c pmt, missed pmt

DIR_STAT_CD 0607 FB Forbearance

DIR_STAT_CD 0607 FC False certification discharge

DIR_STAT_CD 0607 IA Loan originated

DIR_STAT_CD 0607 ID In School or Grace Period

DIR_STAT_CD 0607 IG In grace period

DIR_STAT_CD 0607 IM In military grace

DIR_STAT_CD 0607 IP In post-deferment grace




RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_DI

RCRLDS6_EX

RCRLDS6_EX

RCRLDS6_EX

Columnation

Translation Comment



R_STAT_CD 0607 OD Def., bankrupt, disch., other

R_STAT_CD 0607 PC Paid in Full Con. Loan

R_STAT_CD 0607 PF Paid in Full

R_STAT_CD 0607 PM Presumed Paid in Full

R_STAT_CD 0607 PN NDef, Paid in Full Con. Loan

R_STAT_CD 0607 RF Refinanced

R_STAT_CD 0607 RP In repayment

R_STAT_CD 0607 UA TU no default claim requested

R_STAT_CD 0607 UB TU default claim denied

R_STAT_CD 0607 UC PUU no default claim requested

R_STAT_CD 0607 UD PUU default claim denied

R_STAT_CD 0607 UI Uninsured/unreinsured

R_STAT_CD 0607 XD Defaulted, SA, 6c payments

TRA_UNSUB_LN_FLAG 0607 B Both

TRA_UNSUB_LN_FLAG 0607 H Health professional

TRA_UNSUB_LN_FLAG 0607 N Neither




RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_

RCRLDS6_




EXTRA_UNSUB_LN_FLAG 0607 P PLUS denial

GRADE_LEVEL 0607 1 Freshman/first year

GRADE_LEVEL 0607 2 Sophomore/second year

GRADE_LEVEL 0607 3 Junior/third year

GRADE_LEVEL 0607 4 Senior/fourth year

GRADE_LEVEL 0607 5 Fifth/other undergrad

GRADE_LEVEL 0607 A First year grad/prof

GRADE_LEVEL 0607 B Second year grad/prof

GRADE_LEVEL 0607 C Third year grad/prof

GRADE_LEVEL 0607 D Beyond third year grad/prof

GRADE_LEVEL 0607 G Grad/prof year unknown

GRADE_LEVEL 0607 N Not available

LOAN_CAP_INT_FLAG 0607 N No

LOAN_CAP_INT_FLAG 0607 Y Yes

TYPE_CD 0607 D Defaulted

TYPE_CD 0607 R Recent




RCRLDS6_TY

RELSHIP

RELSHIP

RELSHIP

RELSHIP

RELSHIP

RELSHIP

RELSHIP

RELSHIP

RNRVRFY_EL

RNRVRFY_EL

RNRVRFY_EL

RNRVRFY_TA

RNRVRFY_TA

RNRVRFY_TA

RNRVRFY_TA

Columnation

Translation Comment



PE_CD 0607 T Discharged

0607 1 Parent

0607 2 Stepparent

0607 3 Brother or sister

0607 4 Husband or wife

0607 5 Child/stepchild

0607 6 Grandparent

0607 7 Stepbrother or stepsister

0607 8 Other

IG_IND 0607 1 Yes

IG_IND 0607 2 No

IG_IND 0607 3 Don't know

X_FORM_IND 0607 1 1040

X_FORM_IND 0607 2 1040A, EZ, TeleFile

X_FORM_IND 0607 3 Foreign tax return

X_FORM_IND 0607 4 Other




RORSTAT_

RORSTAT_

RORSTAT_

RORSTAT_

SCHL_TYP

SCHL_TYP

SCHL_TYP

SCHL_TYP

SCHL_TYP

SCHL_TYP




NSLDS_OVRD_IND A All tests

NSLDS_OVRD_IND D Default tests

NSLDS_OVRD_IND L Limit tests

NSLDS_OVRD_IND O Overpayment tests

E 0607 1 2 year public

E 0607 2 2 year private

E 0607 3 4 year public

E 0607 4 4 year private

E 0607 5 Graduate/professional

E 0607 6 Proprietary


Date post:	01-Apr-2018
Category:	Documents
Upload:	duongkien
View:	216 times
Download:	1 times

October 2005 Release 7.3 - Prince Mohammad bin Fahd ... Early Decision release is used by SCT Banner...

Documents