Description: Tags: 102307PerkinsDPIV4

U.S.
Department of Education
Federal Perkins
Data Provider Instructions
(Version 4)
June 2007
Final Copy
Perkins Data Provider Instructions Contents
Contents
Chapter 1: Introduction ................................................................................................................1

1.1 About This Manual ..............................................................................................................1
1.2 What Is NSLDS?..................................................................................................................2
1.2.1 NSLDS Functions .......................................................................................................3
1.2.2 Origination of NSLDS Data........................................................................................6
1.2.3 NSLDS Users..............................................................................................................7
1.3 Getting Help.........................................................................................................................9
Chapter 2: Data Provider Responsibilities ................................................................................10

2.1 Data Privacy.......................................................................................................................11
2.2 Data Accuracy and Timeliness ..........................................................................................12
Chapter 3: The Update Process ..................................................................................................13

3.1 Files Used in the NSLDS Update Process .........................................................................17
3.1.1 Loans Closed Prior to October 1, 1989.....................................................................19
3.1.2 Report Outstanding Principal Balances Monthly .....................................................19
3.1.3 Reporting Outstanding Principal Balances That Are Less Than $1 .........................19
3.1.4 Data Provider Loan ID..............................................................................................19
Chapter 4: System Requirements...............................................................................................20

4.1 Estimating Required Disk Space .......................................................................................20
4.2 Setting Up Communications Links with NSLDS ..............................................................21
4.3 Obtaining a Submittal Schedule.........................................................................................22
4.4 Initial Population................................................................................................................22
4.5 File Protection and Backups ..............................................................................................22
4.6 Using Servicers ..................................................................................................................23
4.7 Multiple Schools or School Branches................................................................................24
Chapter 5: Installation, Utilities, and Testing ...........................................................................25

5.1 Installation..........................................................................................................................25
5.1.1 Installing DataPrep on a Windows- Based PC .........................................................25
5.1.2 Installation Instructions Using Microsoft Internet Explorer.....................................26
5.1.3 Installation Instructions Using Netscape ..................................................................31
5.1.4 Uninstallation Instructions ........................................................................................38
5.1.5 Installing DataPrep on a z/OS LE Version 3.1 or Higher Mainframe ......................42
5.2 Options and Utilities ..........................................................................................................43
5.2.1 Changing Directory Paths .........................................................................................43
5.2.2 Viewers .....................................................................................................................45
5.2.3 File Transfer..............................................................................................................48
5.2.4 File Backup ...............................................................................................................52
5.2.5 Help System ..............................................................................................................58
5.3 Running Test Files .............................................................................................................59
5.3.1 Successful Extract Validation ...................................................................................60
5.3.2 Unsuccessful Validation ...........................................................................................66
June 2007 Version 4

i
5.3.3 Test Load Process Error Report................................................................................68

5.3.4 Test Error Submittal Notification Report .................................................................72
5.4 Deleting Test Files .............................................................................................................76
5.5 Sample Files z/OS LE Version 3.1 ....................................................................................79
Chapter 6: The Database Extract File .......................................................................................80

6.1 Business Rules ...................................................................................................................80
6.2 Record Types .....................................................................................................................81
6.2.1 Header Record ..........................................................................................................82
6.2.2 Detail Records...........................................................................................................82
6.2.3 Past Period Change Records .....................................................................................83
6.3 File Standards.....................................................................................................................83
6.4 Field Standards...................................................................................................................85
6.5 Updating Identifier Data ....................................................................................................85
6.5.1 Loan and Student Identifiers.....................................................................................86
6.5.2 The Identifier Change Process ..................................................................................86
6.5.3 Updating Identifiers on Multiple Records ................................................................88
6.6 Updating Non-Identifier Data ............................................................................................88
6.6.1 What NSLDS Does ...................................................................................................89
6.6.2 What You Do ............................................................................................................94
6.7 Copy Your Database Extract File to the Extract Directory .............................................100
Chapter 7: Extract Validation ..................................................................................................101

7.1 What Happens in Extract Validation?..............................................................................101
7.2 DataPrep Error Path .........................................................................................................103
7.2.1 File-Level Edits.......................................................................................................104
7.2.2 Domain-Level Edits ................................................................................................104
7.3 Running Extract Validation on a PC................................................................................105
7.3.1 Output .....................................................................................................................108
7.3.2 Using the Extract Validation Log Report ...............................................................108
7.4 Running Extract Validation on a z/OS LE Version 3.1 or Higher Mainframe................114
Chapter 8: Sending and Receiving Files ..................................................................................115

8.1 Sending the Submittal File...............................................................................................115
8.1.1 Submittal Schedule .................................................................................................115
8.1.2 Submittal File Format .............................................................................................116
8.1.3 Submitting by Student Aid Internet Gateway.........................................................117
8.2 Receiving Files.................................................................................................................118
8.2.1 Receiving Files by Student Aid Internet Gateway..................................................118
Chapter 9: The NSLDS Load Process......................................................................................119

9.1 File-Level Edits................................................................................................................121
9.2 Domain-Level Edits .........................................................................................................121
9.3 Record-Level Edits ..........................................................................................................122
9.3.1 Duplicates ...............................................................................................................122
9.3.2 Reasonability Edits .................................................................................................122
9.4 Load-Level Edits..............................................................................................................123
June 2007 Version 4

ii
9.4.1 Identifier Edits ........................................................................................................123

9.4.2 OPEID Edits............................................................................................................125
9.4.3 Validate Codes ........................................................................................................125
9.4.4 Date Sequence Edits ...............................................................................................125
Chapter 10: Generating Reports on Windows-Based PCs ....................................................127

10.1 The Extract Validation Log Report................................................................................128
10.2 Error Reports..................................................................................................................130
10.2.1 Error Files .............................................................................................................130
10.2.2 Generating Summary Error Reports .....................................................................131
10.2.3 Generating Detail Error Reports ...........................................................................134
10.3 Loan Detail Reports .......................................................................................................139
10.3.1 Loan Detail Files...................................................................................................139
10.3.2 Generating Loan Detail Reports ...........................................................................140
10.4 The Error Submittal Summary Notification Report.......................................................144
10.4.1 The Error Submittal Summary Notification File ..................................................144
10.4.2 Generating the Error Submittal Summary Notification Report ............................145
10.5 Selection Criteria ...........................................................................................................147
10.5.1 Adding Selection Criteria .....................................................................................149
10.5.2 Editing Selection Criteria......................................................................................151
10.5.3 Deleting Selection Criteria....................................................................................152
10.5.4 Adding Variable Selection Criteria.......................................................................152
10.5.5 Selection Criteria Comparisons Syntax ................................................................155
10.6 Sort Options ...................................................................................................................158
10.6.1 Adding a Sort Option ............................................................................................159
10.6.2 Editing a Sort Option ............................................................................................162
10.6.3 Deleting a Sort Option ..........................................................................................162
10.6.4 Sort Parameter Positions’ Syntax..........................................................................162
Chapter 11: Generating Reports on z/OS LE Version 3.1 or Higher Mainframes .............164
11.1 Extract Error Report.......................................................................................................164
11.1.1 Summary Report Sorting ......................................................................................164
11.1.2 Detail Report Sorting ............................................................................................165
11.2 Load Process Error Report.............................................................................................166
Chapter 12: Using Reports........................................................................................................167

12.1 Extract Validation Log Report.......................................................................................167
12.2 Error Reports..................................................................................................................167
12.2.1 Summary Error Reports ........................................................................................167
12.2.2 Detail Error Reports..............................................................................................169
12.3 Loan Detail Reports .......................................................................................................171
12.4 Error Submittal Summary Notification Report..............................................................173
12.5 Error Types ....................................................................................................................173
12.5.1 File-Level Errors...................................................................................................173
12.5.2 Domain-Level Errors ............................................................................................174
12.5.3 Record-Level Errors..............................................................................................176
12.5.4 Load-Level Errors.................................................................................................177
June 2007 Version 4

iii
Chapter 13: Final Thoughts......................................................................................................180
Appendix A: Federal Perkins Loans Data Dictionary
Appendix B: Federal Perkins Loan Program Code and Error Tables
Appendix C: Past Period Change Record Layout
Appendix D: Federal Perkins Loans Load Error File (Record Layouts)
Appendix E: Federal Perkins Loans TEF File Layout
Appendix F: Error Submittal Summary Notification File
Appendix G: DataPrep JCL for z/OS LE
Appendix H: Glossary of Terms
Appendix I: Technical Updates
June 2007 Version 4

iv
Figures
Figure 1–1, Sources of NSLDS Data.............................................................................................. 7
Figure 1–2, Outflow of NSLDS Information.................................................................................. 8
Figure 3–1, Data Provider Six-Step Process................................................................................. 15
Figure 3–2, DataPrep Processing Flow for Extract Validation and Error Report Generation...... 16
Figure 3–3, NSLDS Edit Process.................................................................................................. 18
Figure 5–1, Directories Dialog Box.............................................................................................. 41
Figure 5–2, DataPrep Main Menu with Directories Selected on the Options Menu .................... 43
Figure 5–3, Directories Dialog Box.............................................................................................. 44
Figure 5–4, DataPrep Main Menu with Viewers Selection on the Options Menu ....................... 46
Figure 5–5, Viewer Maintenance Dialog Box .............................................................................. 47
Figure 5–6, Select Viewer Dialog Box ......................................................................................... 48
Figure 5–7, Initial File Transfer Dialog Box for File Import ....................................................... 49
Figure 5–8, Initial Select NSLDS File Dialog Box for TEF File ................................................. 50
Figure 5–9, Final Select NSLDS File Dialog Box for TEF File................................................... 51
Figure 5–10, Final File Transfer Dialog Box for File Import....................................................... 51
Figure 5–11, DataPrep Main Menu with File Backup Selected ................................................... 53
Figure 5–12, Backup Files Dialog Box......................................................................................... 54
Figure 5–13, New Backup File Folder Dialog Box ...................................................................... 54
Figure 5–14, Backup Files Dialog Box with Files Selected ......................................................... 55
Figure 5–15, Backup Files Dialog Box with Files and Backup Folder Selected.......................... 55
Figure 5–16, Backup Files Dialog Box after Copy....................................................................... 56
Figure 5–17, Backup Files Dialog Box after Move...................................................................... 56
Figure 5–18, List Backup Files Dialog Box ................................................................................. 57
Figure 5–19, Test Files Installed in C:\Nslds-v3\Samples............................................................ 59
Figure 5–20, C:\DataPrep Folder with Extract and Current Folders ............................................ 60
Figure 5–21, DataPrep Main Menu with Extract Validation Selected ......................................... 61
Figure 5–22, Extract Validation Dialog Box ................................................................................ 61
Figure 5–23, Extract Validation Process Dialog Box................................................................... 62
Figure 5–24, Log Report Dialog Box ........................................................................................... 63
Figure 5–25, Sample Log Report.................................................................................................. 63
Figure 5–26, Error Report Dialog Box ......................................................................................... 64
Figure 5–27, Summary Extract Error Report................................................................................ 65
Figure 5–28, Extract Folder .......................................................................................................... 66
Figure 5–30, Extract Validation Unsuccessful ............................................................................. 67
Figure 5–31, Default File Transfer Dialog Box............................................................................ 68
Figure 5–32, Initial File Transfer Dialog Box for Load Process Error File ................................. 69
Figure 5–33, Select NSLDS File Dialog Box for Load Process Error File .................................. 69
Figure 5–34, Final File Transfer Dialog Box for Load Process Error File................................... 70
Figure 5–35, Error Report Dialog Box for Load Process Error Report........................................ 71
Figure 5–36, Test Load Process Error Report .............................................................................. 72
Figure 5–37, Initial File Transfer Dialog Box for Importing Error Submittal Summary ............. 73
Notification File
Figure 5–38, Select NSLDS File Dialog Box for Submittal Notification Files............................ 73
June 2007 Version 4

v
Figure 5–39, Final File Transfer Dialog Box for Importing Error Submittal Summary .............. 74
Notification File
Figure 5–40, Notification Report Dialog Box .............................................................................. 75
Figure 5–41, Error Submittal Summary Notification Report ....................................................... 76
Figure 5–42, File Backup Dialog Box .......................................................................................... 77
Figure 5–43, New Backup File Folder Dialog Box ...................................................................... 77
Figure 5–44, File Backup Dialog Box .......................................................................................... 78
Figure 5–45, List Backup Files Dialog Box ................................................................................. 78
Figure 6–1, Loan and Student Identifiers ..................................................................................... 86
Figure 6–2, How to Update Loan Identifier Data ......................................................................... 87
Figure 6–3, NSLDS Update (1 of 2)............................................................................................. 90
Figure 6–4, NSLDS Update (2 of 2)............................................................................................. 91
Figure 6–5, Updating a Current Event.......................................................................................... 93
Figure 6–6, Updating Historical Events........................................................................................ 94
Figure 6–7, Fields and History...................................................................................................... 95
Figure 6–8, PPC Events, Keys, and Values .................................................................................. 97
Figure 7–1, Extract Validation Process ...................................................................................... 102
Figure 7–2, DataPrep Edit Process ............................................................................................. 103
Figure 7–3, DataPrep Main Menu with Extract Validation Selected ......................................... 106
Figure 7–5, Extract Validation Process Dialog Box................................................................... 108
Figure 9–1, NSLDS Load Process .............................................................................................. 120
Figure 10–1, DataPrep Main Menu with Log Report Selected .................................................. 128
Figure 10–2, Log Reports Dialog Box........................................................................................ 129
Figure 10–3, Extract Validation Log Report .............................................................................. 129
Figure 10–4, DataPrep Main Menu with Error Report Selected ................................................ 132
Figure 10–5, Error Report Dialog Box ....................................................................................... 132
Figure 10–6, Generate Summary Error Rpt Dialog Box ............................................................ 133
Figure 10–7, Summary Extract Error Report.............................................................................. 134
Figure 10–8, DataPrep Main Menu with Error Report Selected ................................................ 135
Figure 10–9, Error Report Dialog Box ....................................................................................... 135
Figure 10–10, Generate Summary Error Rpt Dialog Box .......................................................... 137
Figure 10–11, Detail Extract Error Report ................................................................................. 138
Figure 10–12, Detail Load Process Error Report........................................................................ 138
Figure 10–13, DataPrep Main Menu with Loan Detail Report Selected.................................... 141
Figure 10–14, Loan Detail Report Dialog Box........................................................................... 141
Figure 10–15, Extract Loan Detail Report.................................................................................. 144
Figure 10–16, Notification Report Dialog Box .......................................................................... 146
Figure 10–17, Error Submittal Summary Notification Report ................................................... 147
Figure 10–18, DataPrep Main Menu with Selection Criteria Selected on the Options Menu.... 148
Figure 10–19, Selection Criteria Dialog Box ............................................................................. 148
Figure 10–20, Selection Criteria Edit Dialog Box...................................................................... 149
Figure 10–24, Selection Variable Edit Dialog Box .................................................................... 153
June 2007 Version 4

vi

Figure 10–26, Selection Variable Edit Dialog Box .................................................................... 154
Figure 10–27, DataPrep Main Menu with Sort Parameters Selected on Options Menu ............ 158
Figure 10–28, Sort Parameters Dialog Box ................................................................................ 159
Figure 10–29, Sort Parameter Edit Dialog Box .......................................................................... 160
Figure 10–31, Sort Parameters Dialog Box ................................................................................ 161
Figure 12–1, Summary Extract Error Report.............................................................................. 168
Figure 12–2, Summary Load Process Error Report.................................................................... 168
Figure 12–3, Sample Detail Extract Error Report ...................................................................... 171
Figure 12–4, Sample Detail Load Process Error Report............................................................. 171
June 2007 Version 4

vii
Perkins Data Provider Instructions Introduction
Chapter 1: Introduction
Schools participating in the Federal Perkins Loan Program are
required to report detailed loan information to the National Student
Loan Data System (NSLDS). This operating manual explains
Federal Perkins Loan reporting requirements and the processes
Dear Colleague Letter
used to add or update Federal Perkins loans on NSLDS. It explains April 1995
how to use the new NSLDS DataPrep software and is for the use of CB-95-5 (LD)
data providers (schools and their servicers) with administrative All schools in the Title IV aid
responsibility for the Federal Perkins Loan Program. programs are required to
participate with NSLDS.
Schools with active Perkins
Loans (including National
1.1 About This Manual Direct Student Loans,
National Defense Student
This manual is intended to assist users with the data provider Loans, and Income
Contingent Loans) are
portion of the NSLDS update process, as well as provide basic required to provide updated
information about the entire process. data to NSLDS once a
month on a schedule
To make the instruction manual easy to follow, we have used the established by ED.
following icons to identify key points:
This icon indicates a definition or explanation that

you will need to keep in mind throughout the
discussion.
This icon indicates a special note, suggestion, or

comment that will assist you in running DataPrep or
in providing insight into the NSLDS update process.
This icon indicates a warning of which you should

take special note.
June 2007 Version 4

1
1.2 What Is NSLDS?

NSLDS supports the U.S. Department of Education (ED) in a
variety of operational and research functions meant to improve the
administration and delivery of student aid through Title IV aid
programs. Specifically, the three main goals of NSLDS are to:
1. Improve the quality and accessibility of student aid data. National

Student
2. Reduce the burden of administering Title IV aid. Loan
Data
3. Minimize abuse within the aid programs through accurate System
tracking of funds appropriated to assist the postsecondary
students for whom the programs were designed.
NSLDS is a national database of recipients, enrollment, loan,

grant, and overpayment information on student aid disbursed under
Title IV of the Higher Education Act of 1965, as amended (the
Act). Data in NSLDS are provided by schools, guaranty agencies,
and ED agencies. The data include information about the
following:
• The Federal Family Education Loan Program (FFELP)
• The Federal Direct Loan Program (FDLP)
• Federal Perkins loans (including National Direct Student

Loans, National Defense Student Loans, and Income
Contingent Loans)
• Federal Pell Grants, Federal Supplemental Educational

Opportunity Grants (FSEOGs), Academic Competitiveness
Grants (ACGs), and National Science and Mathematics Access
to Retain Talent (SMART) grants
• Overpayments from the Federal Pell Grants, FSEOGs, ACGs,

National SMART grants, and Federal Perkins Loan programs
• Demographic and enrollment data on Title IV recipients
June 2007 Version 4

2
1.2.1 NSLDS Functions

NSLDS currently has responsibility for the following functions:
1. Prescreening for Title IV Aid Eligibility—The NSLDS

Prescreening function gives schools electronic access to
information on prior Title IV aid received by aid applicants.
Schools use this information to determine applicants’ eligibility
for further Title IV aid.
2. Postscreening for Title IV Aid Eligibility—The NSLDS

Postscreening function informs institutions when their
applicants’ eligibility for Title IV aid has changed due to a
change in default or overpayment status after their initial
prescreening.
3. Default Rate Calculations—Cohort default rates are

calculated annually for schools participating in the William D.
Ford Federal Direct Loan Program and in FFELP. Rates are
also calculated for guaranty agencies and lenders. Schools with
default rates above established thresholds for at least 3
consecutive years can be disqualified from participating in
some or all student financial aid programs.
4. Monitoring of Guaranty Agencies and Lender Financial

Reporting for Reasonability—NSLDS allows ED to monitor
financial reporting for reasonability by supporting more timely
assessment and by providing loan-level information. This helps
ensure that the financial reporting submitted to ED by lenders
and guaranty agencies reflects the status of their portfolios as
reported to NSLDS.
5. Research Studies and Policy Development Support—

NSLDS provides several types of access in support of users
performing research and developing policy. Online queries
range from focused queries, pertaining to a single student or
school for relatively small amounts of data, to queries requiring
NSLDS to supply or summarize massive amounts of data.
6. ED Budget Analysis and Development—Every year, ED

develops input for the President’s budget, based partly on
projected loan program costs for a 7-year period. NSLDS
information is used to develop reliable, sound assumptions on
which to base the estimated program budget; answer budget-
related questions; and support necessary hypothetical analyses.
June 2007 Version 4

3
7. Audit and Program Review Planning—ED uses audits and

program reviews to assess the performance of various Title IV
aid delivery system participants. Audit and program review
planning functions include retrieving specific data from
NSLDS on organizations (schools, lenders, and guaranty
agencies), and identifying key indicators used to schedule
audits and reviews for maximum effectiveness.
8. Assessment of FFELP Administration by Guaranty

Agencies, Schools, and Lenders—NSLDS provides the data
for researching and assessing FFELP administration by
guaranty agencies, schools, and lenders. Such research can be
either short- or long-term, and generally aims to evaluate the
effectiveness of specific program practices.
9. Refund/Cancellation Support—When a student withdraws

from school early and qualifies for a refund, the school is
required to provide the refund or return of check to the
appropriate party within a fixed time period. NSLDS provides
information about the time schools take to perform these
actions. This information helps auditors and program reviewers
identify schools with poor records of handling refunds and
cancellations.
10. Borrower Tracking—The Borrower Tracking function helps

qualified users locate borrowers who have defaulted on student
loans. NSLDS Borrower Tracking capabilities allow these
qualified users to identify other schools, guaranty agencies, and
lenders previously associated with a borrower, so they can be
contacted for the borrower’s current address.
11. Loan Transfer Tracking—Loan Transfer Tracking monitors

transfer activity by maintaining dates of sale and names of loan
holders. This information identifies likely problems with
participants. It also helps evaluate the administration and
billing of Title IV loan programs.
12. Enrollment Reporting Process—The Enrollment Reporting

process allows loan holders to verify a borrower’s enrollment
status. This enrollment information enables loan holders to
place a borrower properly into repayment. NSLDS has
standardized the Enrollment Reporting process and it maintains
current enrollment information.
June 2007 Version 4

4
13. Financial Aid Transcript—The Financial Aid Transcript

(FAT) component of NSLDS summarizes all previous Title IV
aid a student has received.
14. Credit Reform Act Support—The Credit Reform Act (CRA)

requires loan-level tracking of all Federally guaranteed loans.
NSLDS tracks and reports loans by program, cohort year, and
risk category. Loan data are used semiannually to estimate
Government costs associated with loan programs.
15. Aid Overpayment—NSLDS maintains a record of

overpayments owed and repaid by students on Federal Pell
Grants, ACGs, National SMART grants, FSEOGs, and Federal
Perkins Loans. The information is used to determine a
student’s eligibility for aid.
16. Organization Contact—NSLDS enables organizations,

including schools, to enter contact information by function.
This contact capability is accessible by the NSLDS Financial
Aid Professionals (FAP) Web site (www.nsldsfap.ed.gov). It
helps users quickly locate the correct contact person at a
school, GA, lender, servicer, or other data provider.
17. Student Access—NSLDS gives students access to basic

information about their Federal loans at a secure Web site
accessible to standard Web browsers.
These function areas and the system capabilities that support them
reflect requirements established for NSLDS by the U.S. Congress
and ED.
June 2007 Version 4

5
1.2.2 Origination of NSLDS Data

As a comprehensive repository of Title IV recipients and their
loans, Pell Grants, overpayments, and enrollment information,
NSLDS receives data from many sources (some external and some
internal to ED) and makes it available to approved users for a
variety of purposes authorized by the Act. The principal sources of
NSLDS data are the following:
• Guaranty agencies provide loan data on FFELP loans from

loan origination until the loan is paid in full. Some of the
information guaranty agencies provide, such as loan balances,
is received from lenders who report on loans through their
guaranty agencies. Guaranty agencies submit their data
monthly and daily through online updates.
• Schools (or their servicers) provide enrollment data via the

Enrollment Reporting process.
• Schools (or their servicers) that participate in the Federal

Perkins Loan Program provide monthly updates of loans.
• The Debt Collection Service (DCS) provides data weekly on

loans and overpayments assigned to ED and on lenders and
lender servicers.
• The Postsecondary Education Participants System (PEPS)

provides daily data on schools.
• The Conditional Disability Discharge Tracking System

(CDDTS) provides monthly data on loans with permanent and
conditional disability discharges.
• The Central Processing System (CPS) provides quarterly

demographic data on students in the NSLDS database.
• The Common Origination and Disbursement (COD)

provides daily updates on all Federal grant payments to
students.
• The Federal Direct Loan Program (FDLP) Servicer provides

weekly data on FDLP loans.
• The Lender Reporting System (LARS) reports lenders and

lender servicer data to NSLDS daily.
June 2007 Version 4

6
LARS
Lender and Lender Servicer Data
All Schools CDDTS

Enrollment Reporting
Conditional Disabilities Discharges
Aid Overpayments
Perkins Schools CPS

Perkins Loan Information Student Demographic Data
PEPS DCMS
Aid Overpayments
School Demographic Data
Lender and Lender Servicer Data
NSL-1076
Loans Assigned to ED
COD FDLP
Pell/ACG/SMART Grants FDLP Loan Information
Guaranty Agencies
FFEL Loan Information
Lenders/Servicers
Figure 1-1, Sources of NSLDS Data

June 2007
Figure 1–1, Sources of NSLDS Data
1.2.3 NSLDS Users

NSLDS users include personnel from ED, other Federal agencies,
guaranty agencies, lenders, schools, and independent researchers.
NSLDS provides its users with Internet access and batch

processing. The system’s products are designed to provide efficient
access to NSLDS data for a variety of user levels and purposes.
See Figure 1–2 for the flow of data from NSLDS to various users.
June 2007 Version 4

7
CPS
Student Aid History
Students Department of Education

Financial Aid Review Queries, Reports, and Data Extracts
Schools FDLP
FAH Information Enrollment Reporting Information
Enrollment Reporting Roster Error Reports
Queries, Reports, and Data Extracts Queries, Reports, and Data Extracts
Guaranty Agencies
PIC Enrollment Reporting Information
Queries Error Reports, Queries, Reports,
and Data Extracts (NSL-1100)
Other Government
Agencies
Queries, Reports, and Data Extracts
Figure 1-2, Outflow of NSLDS Information

June 2007
Figure 1–2, Outflow of NSLDS Information
June 2007 Version 4

8
1.3 Getting Help

The NSLDS Customer Service Center (CSC) is available to answer
your questions. The CSC offers comprehensive assistance on all
aspects of using the DataPrep software, from step-by-step
installation questions to receiving error reports. The CSC can help
you identify and correct Extract problems resulting from file- and
domain-level edits, or NSLDS update problems resulting from
record-level and load-level errors. The CSC will address your
Perkins data provider set-up and scheduling questions and will
distribute your school’s yearly data provider load schedule each
November.
In addition, the CSC can help:
• Identify other data providers to resolve identifier conflicts.

• Clarify Data Provider Instructions.
• Schedule initial and ongoing data loads.
Customer Service Center
• Troubleshoot problems with DataPrep installation. Contact the CSC at 800-
• Discuss submittal requirements. 999-8219 between 8 a.m.
• Explain specific error codes. and 8 p.m. Eastern time,
• Review your submittal schedule. weekdays, excluding
Federal holidays. Customer
Service personnel will log
When you call the CSC, you may be asked to provide specific your call, issue a
information, including: confirmation number,
answer questions, and if
possible, resolve problems
• Your Office of Postsecondary Education (OPE) Identification
immediately. If the problem
(ID) code and school name and phone number requires further research,
Customer Service will
• Whether you are using the mainframe or Windows-based estimate when you can
version of the software expect a return call.
• The Version/Release number and release date of the DataPrep

software you are using
• The nature of the problem
• The part of the process you were working with at the time the
problem occurred
• Whether you have been able to duplicate the problem, and if

so, what the conditions were at the time
• Error messages or other indicators of the source of the

problem.
June 2007 Version 4

9
Perkins Data Provider Instructions The NSLDS Update Process
Chapter 2: Data Provider

Responsibilities
Data providers must provide information to NSLDS on Federal
Perkins loans; and they must regularly report on new loans and
changes to existing loans. These reports must be submitted on an
ongoing basis and on a regular schedule established between the Schools and Servicers
data provider and ED. The term “schools” in this
document includes both
Data providers must: schools and their servicers.
Together, schools and
servicers are referred to as
• Meet all NSLDS reporting requirements, as detailed in this “data providers.”
operating manual.
• Report all Federal Perkins loans that were open or closed on or

after October 1, 1989.
• Report new loans or updates to existing loans monthly on a

schedule established by NSLDS. Data reported must be current
and not extracted earlier than shown on the established
schedule for the data provider.
• Create a Database Extract file meeting the specifications

contained in Appendix A. Data providers are responsible for
coding and testing their software, as needed, to properly format
the Database Extract file.
• Use NSLDS-provided DataPrep software to perform Extract

Validation and create a Submittal file.
• Transmit the Submittal file to NSLDS on ED-provided

communications lines, in accordance with their established
schedule.
• Retrieve the Load Process Error file for each submittal. Data
providers must review errors and correct as many as possible
before the next submittal. Data providers are responsible for
the accuracy of their data, as well as for the timely reporting of
loan data to NSLDS.
• Retrieve any Error Submittal Summary Notification files sent

by NSLDS. Data providers are responsible for taking action to
remedy file-level errors or missed submissions identified by
such files.
June 2007 Version 4

10
• Work with other data providers—including guaranty agencies,

the Direct Loan Program, the Debt Management Collection
System, and the Pell Grant System—to resolve identifier
conflicts.
• Receive and process reconciliation files provided by NSLDS.

Reconciliation of loan data between NSLDS and the school’s
system of record can be done voluntarily upon request from the
school or mandated by ED if it determines reconciliation is
necessary to meet data quality standards.
In summary, data provider data must meet NSLDS reporting

requirements and quality standards. All data submitted to NSLDS
must be as complete and correct as possible. Schools that fail to
meet their NSLDS reporting requirements are subject to the
limitation, suspension, and termination regulatory provisions.
2.1 Data Privacy

NSLDS data are subject to the protections of the Privacy Act of
1974, as amended. Maintaining the security and confidentiality of
the personal data supplied by those applying for and receiving
loans is of paramount concern to NSLDS. Both NSLDS and its Privacy of Data
data providers are responsible for preserving the security of any All NSLDS data are subject
NSLDS data in their possession. to the protections of the
Privacy Act of 1974, as
amended. Failure to
You must be constantly vigilant in assuring the security of data
preserve its confidentiality
being prepared for, sent to, and received from NSLDS. You must can lead to personal liability
also protect student loan data against intentional or inadvertent under that act.
disclosure or destruction. You should label sensitive materials—
such as data, software documentation, operation manuals, and
handbooks—as such and store them in a secured location. Failure
to follow these steps can lead to personal liability under the
Privacy Act.
June 2007 Version 4

11
2.2 Data Accuracy and Timeliness

For NSLDS to meet the needs of its user community, the
submissions it receives from data providers must be timely,
complete, and accurate. To ensure the best data quality, NSLDS
monitors submissions in two ways:
Calculating the Error Rate:
1. Submittal Tracking—NSLDS monitors late and missed The error rate uses the
number of records that
submittals on a continuing basis. contain errors, not the total
number of errors. (There can
2. Error Tracking—NSLDS calculates the percentage of records be more than one error in a
in a submittal that are in error and maintains a record of all record.)
errors until the error condition is resolved. Error rates are
Example:
monitored on a regular basis to ensure data accuracy. If there are 25 errors in total,
but those errors appear in
The error rate is calculated by dividing the number of loan records only 19 records out of 456
with errors by the total number of records extracted. If a record records extracted, the
contains more than one error, the system still only counts it as a calculated error rate is:
single record with errors when calculating the error rate. Thus, the
total number of errors will not necessarily equal the number of
records with errors.
Data providers falling short of expectations in either of these areas

are subject to the limitation, suspension, and termination
regulations of ED.
June 2007 Version 4

12
Chapter 3: The Update Process

The NSLDS update process is comprised of six steps:
1. Data Providers Create a Database Extract File—You create

a copy of your loan portfolio in a format specified by NSLDS. Warning: Data Provider
This copy, called the Database Extract file, includes all open Responsibility
Data providers are
loans and all loans closed on or after October 1, 1989, responsible for submitting
formatted according to the guidelines established in data to NSLDS using the
Appendixes A and C. edit rules, format, and
processing flow specified by
2. Data Providers Run the Extract Validation Process Using ED. Caution should be
exercised when using
DataPrep—You run the Database Extract file through the specifications or software
NSLDS DataPrep Extract Validation process to check for file- applications developed by
level and domain-level errors. If there are file-level errors (such other organizations or
as an incorrect header or a school code for any record that does vendors. Regardless of
not match the header record school code), the process stops. whether third-party software
or procedures are used, data
providers remain responsible
If the rate of domain-level errors (such as a non-numeric for the accuracy of their data
character in a numeric field, an invalid date, a missing and for using procedures
identifier, or a missing new identifier) is above a specified approved by ED. Schools
threshold, the process also stops and the complete Database and Third-Party Servicers
are jointly and severally
Extract file is rejected. You must correct the error(s) before responsible for compliance.
proceeding.
If there are no file-level errors, and if the number of domain-

level errors is within the prescribed limits, DataPrep creates a
new file called the Submittal file.
3. Data Providers Perform Error Report Generations—Using

the Extract Error file produced by DataPrep, you generate
Extract Error reports (both a summary and detail report are
available) and use this information to make all necessary file-
level and domain-level changes to your database and/or extract
process. You can also use the Extract Validation Log report to
perform a test of reasonability—a review of the data comparing
the current data with previous submittals to look for the
numbers of records processed and loan amount totals.
If you make corrections, you then start again at step 1 by

recreating the Database Extract file, running the Extract
Validation process, and running Extract Error report.
June 2007 Version 4

13
4. Data Providers Send or Transmit the Submittal File—Once

a Submittal file has been successfully created (after all file-
level errors are corrected and after the number of domain-level
errors is below the specified thresholds), you transmit the data
to NSLDS via the Title IV Wide Area Network (WAN).
5. NSLDS Runs the Load and Update Process—NSLDS

receives your Submittal file and runs file-level edits on it. If the
file passes all file-level edits, NSLDS then checks each loan
record for domain-, record-, and load-level errors. Loan records
that pass all edits are matched against records already existing
in the NSLDS database. Depending on the outcome of that
match, NSLDS either creates new student or loan records, or
updates existing records. Loan records that fail one or more
edits are added to the Load Process Error file NSLDS returns
to you after loading your data.
6. Data Providers Retrieve Error Files and Generate Load

Process Error Reports—If your Submittal file passes all file-
level edits and is loaded onto NSLDS, NSLDS sends you,
within 48 hours, a Load Process Error file containing all the
domain-, record-, and load-level errors detected during the
Load process. You then use DataPrep to generate Load Process
Error reports (both summary and detail reports are available),
which will help you make corrections to your database and
resolve data conflicts prior to your next monthly extract.
If you fail to send NSLDS a Submittal file at the scheduled

time, or if the file you send is not loaded because of file-level
edits, NSLDS sends you, within 48 hours, an Error Submittal
Summary Notification file notifying you that your file was not
received or was not loaded. In this case, NSLDS does not send
you a Load Process Error file or Threshold Error File (TEF)
file.
June 2007 Version 4

14
Viewed as a linear sequence, the six-step update process looks like

this:
Data Providers create a Database Extract File

from their own databases, using their own
Step 1 software and ensuring that it meets NSLDS
system requirements.
Fix database(s) and/or

Extract Validation process
to correct file-level and
Data Providers run the Extract Validation domain-level errors.
Step 2 Process against their Database Extract File Rerun steps 1-3.
using DataPrep software.
Use information to
Data Providers perform Extract Error Report
Step 3 Generation.
correct database(s)
and/or Extract
Validation process.
Extract Error
Reports
Step 4 Data Providers send Submittal File to NSLDS.
NSLDS runs Load and Update process against

Data Providers' Submittal Files, updates
Step 5 NSLDS database, and creates error and TEF
files for Data Providers.
Data Providers retrieve error and TEF files

from NSLDS and generate Load Process Error
Step 6 Reports to correct record level errors in their
database.
NSL-1071
Figure 3–1, Data Provider Six-Step Process
June 2007 Version 4

15
Viewed as an ongoing or cyclical process, the update process can

also be illustrated in the following way, with the shaded boxes
representing school or data provider responsibility and the
darkened boxes representing operations handled by DataPrep.
Existing School Database Extract Database

Database Procedure Extract File
Extract
Database Update
Validation
Procedures
Procedure
Extract
Extract Error
Validation Log Submittal File
File
File
Detail Report Summary Report

Procedure Procedure
Electronic
Extract Error Extract Error Transmittal
Detail Report Summary Report
NSLDS
Extract Threshold, Error

Load Process
Reconciliation Code, and Field
Error File
File Code (TEF) File
Detail Report Summary Report Reconciliation

Procedure Procedure Report Procedure
NSLDS Responsibility
DataPrep Responsibility
Extract
Load Error Detail Load Error
Reconciliation School Responsibility
Report Summary Report
Report
NSL-1046
Figure 3–2, DataPrep Processing Flow for Extract Validation and

Error Report Generation
June 2007 Version 4

16
3.1 Files Used in the NSLDS Update

Process
The following files are created or updated in the update process:
• Database Extract File (extract.ff)—This is the formatted

Database Extract file you create from your loan database. It
File Names
includes Header and Detail records and can include Past Period You can determine the
Change (PPC) records to correct certain kinds of reporting naming conventions for files
errors in previous cycles. This file is the input to the Extract used and created exclusively
Validation process. at your own site. Windows
users cannot alter the
names used by DataPrep;
• Submittal File (submit.ff)—This file is created by DataPrep otherwise, the program will
software if there are no file-level errors and the number of not work properly.
domain-level errors in the Database Extract file is below the
acceptable threshold levels. The Submittal file contains all We strongly recommend that
mainframe users use the
current records and all PPC records. You transmit this file to suggested file names
NSLDS, where it becomes input to the Load Process. This file provided by DataPrep and
can contain four record types: Header, Detail, Past Period used in the sample Job
Change, and Trailer. The Trailer record is added by DataPrep. Control Language (JCL) in
Appendix G.
• Extract Error File (extrerr.ff)—This file is an output from
the Extract Validation process. It contains an error record for
each domain error listing the field in which the error occurred,
the value and description of the error. The contents of this file
can either be viewed on-screen or printed.
• Error Submittal Summary Notification File (shsntfop.ff)—

This file informs you that your Submittal file was not loaded
onto NSLDS database, either because it was not received by
NSLDS or because it contained file-level errors. In the latter
case, it identifies the errors that prevented the Submittal file
from being loaded. The contents of this file can either be
viewed on-screen or printed.
• Load Process Error File (loaderr.ff)—This file is an output

of the load process. It contains an error record for each domain,
record, and load-level error that failed NSLDS load edits. It
identifies errors detected during the Load process and also
contains header and trailer records. The contents of this file can
either be viewed on-screen or printed.
June 2007 Version 4

17
• Threshold, Error Code, and Field Code (TEF) File

(TEF.ff)—This file contains software parameters for Load
Process Error processing and error field names and messages
for the processing of the Load Process Error file.
Figure 3–3 shows the edit process, some of the problems that can
arise during that process, and possible solutions.
Edit Process Problem Solution
File-Level Edits
DataPrep Extract Validation

Extract Aborted
1. Incorrect Header Correct database
Validation 2. School Code does and/or extract process
Process not match Header and rerun Extract
Domain-Level Edits Validation
Threshold Failure
1. Numeric Field Error Correct database
2. Invalid Date and/or extract process
3. Missing Identifier and rerun Extract
4. Missing New Identifier Validation
Domain and
Record-Level Edits
Record Rejected
NSLDS 1. Numeric Field Error Correct database
Load 2. Invalid Date and/or extract process
Process 3. Missing Identifier before next submittal
4. Missing New Identifier
Load-Level Edits
5. Reasonability Error
6. Duplicate Record
Record not
Loaded/Updated
1. Date Sequence Error 1. Create PPC
2. Identifier Conflict 2. Resolve with other
data provider
3. Invalid Codes 3. Correct database/
NSLDS Updated extract process
NSL-1061
Figure 3–3, NSLDS Edit Process
June 2007 Version 4

18
3.1.1 Loans Closed Prior to October 1, 1989

If you currently extract loans that were closed before October 1,
1989, stop extracting such loans. A new edit will reject any loan
closed before October 1, 1989. You can prevent these rejects by
not extracting such loans.
3.1.2 Report Outstanding Principal Balances

Monthly
The Date of Outstanding Principal Balance reflects the date of the
most recent change in the principal balance. The Outstanding
Principal Balance may change due to a disbursement, loan
payment, or cancellation. Since you submit all loans in your
database every month, the requirement to update Outstanding
Principal Balance on a quarterly basis is eliminated. Instead, you
must update the dollar amount and the date of the Outstanding
Principal Balance using the current remaining amount and the date
of the most recent change in Outstanding Principal Balance. If you
have been reporting the last day of the month as the Date of
Outstanding Principal Balance regardless of when the balance
changed, you must modify your extract procedure to provide the
actual day when the balance changed.
3.1.3 Reporting Outstanding Principal Balances

That Are Less Than $1
If a loan is reported with an open loan status, it must have a
positive Outstanding Principal Balance. If the loan has a balance of
less than $1, but not zero, you should report the Outstanding
Principal Balance as $1. If the loan is being maintained in an open
status because of a negative balance on the account (that is, a credit
balance), you should also report a balance of $1 until the loan is
closed.
3.1.4 Data Provider Loan ID

You can track a loan through the NSLDS process using your own
unique Data Provider Loan ID if you so choose. The last field in
the Detail record is available to allow you to insert a unique loan
ID that will be carried through the update process and returned on
the error records in the Load Process Error file. The use of this new
field is optional.
June 2007 Version 4

19
Perkins Data Provider Instructions System Requirements
Chapter 4: System Requirements

This manual is written for data providers who use the ED-provided
DataPrep software to prepare data for submission to NSLDS from
either a mainframe (z/OS LE Version 3.1 or higher) batch
environment or a Windows-based personal computer (PC). Data
providers, who use other platforms or who want to develop their
own software, should contact ED for more information. Software
developed by data providers must meet the standards established in
this manual.
To run the DataPrep software and submit your data, the minimum
system requirements are either:
z/OS LE Runtime Library
• An IBM/IBM-compatible mainframe running the z/OS LE, If you are running in the z/OS
Version 3.1 or higher operating system and an appropriate sort LE environment, your LE
utility, or Runtime Library must be in
your standard system program
• An IBM-compatible personal computer with at least a 200 library concatenation.
MHz Pentium processor, 64 Mb of available memory, and 8
Mb of hard disk space to store the program and work files, with
additional hard disk space to store data files and backups. For
optimal viewing of reports, you may have to set your monitor’s
resolution to 1024 x 768 pixels. The new version of Perkins
DataPrep is fully compatible with Windows 2000 and
Windows XP. It is not compatible with Windows 95, Windows
98, or Windows NT. If you are using Windows 95, Windows
98, or Windows NT, you can only use the previous version of
Perkins DataPrep and cannot take advantage of the new
software enhancements. For more information about ED
system requirements, see Perkins Technical Update, PK-2004-
01 (January 2004).
Enough Disk Space?

Database Extract files can be
4.1 Estimating Required Disk Space quite large. So it is very
important that you evaluate
You will need approximately 8 Mb of disk space to store the PC whether your computer has
DataPrep software and its associated test data files. This is the enough disk space to store
minimum disk space required and does not include storage space both the DataPrep software
and the data files it
for your data files. You should also allow enough space in which processes.
to sort work files.
June 2007 Version 4

20
Estimate your space requirements by adding the following:
Database Extract files N * 300 bytes * Y

Submittal Files [(N * 300 bytes) + (PPC *
300 bytes)] * Y
Extract Error Files X * 300 bytes * Y
Extract Error Reports X * 132 bytes * Z * 1.1
Load Process Error Files X * 300 bytes * Y
Load Process Error Reports X * 132 bytes * Z * 1.1
Threshold Error File 32,000 bytes
Loan Detail File N * 300 bytes * Y
Loan Detail Reports N * 132 bytes * Z * 1.1
(Equals) _____ bytes of space required
Where:
N = Number of records extracted from your database

X = Estimated number of errors
PPC = Estimated number of PPC records
Y = Number of backup files created and stored
Z = Number of reports generated
All the mainframe examples in this document assume use of a

Direct Access Storage Device (DASD). Tape can be substituted for
DASD for any of the NSLDS files, but in that case, you are
responsible for converting the calculations from DASD to that
medium.
4.2 Setting Up Communications Links with

NSLDS
All data providers submit to NSLDS through the SAIG.
Contact Information
Contact SAIG Customer
SAIG Customer Service Center is responsible for setting up user Service Center to set up a
accounts on the SAIG. You can obtain user documentation for the SAIG user account:
SAIG by calling 800-330-5947. 800-330-5947.
June 2007 Version 4

21
4.3 Obtaining a Submittal Schedule

NSLDS will assign a submittal schedule to you each year, usually
in November. You can check your schedule at any time by
selecting the Data Provider Schedule link on the Organization page Submittal Schedules on
the Web
of the NSLDS Web site (www.nsldsfap.ed.gov). You can check your
submittal schedule at any
For more information, or to obtain a copy of the schedule, contact time on the Organization
the NSLDS Customer Service Center at 800-999-8219. page of the NSLDS Web site
(www.nsldsfap.ed.gov).
4.4 Initial Population

The first-time transfer of information from schools or data
providers to NSLDS is called the initial population. In addition to
current loan data, the initial population also includes data for loans
that are closed. See Appendix A for detailed information about
what data to include in an initial population Database Extract file.
Except for the addition of closed loan data and a slight difference
in data reporting requirements, the process for an initial population
submission is the same as the one you follow for subsequent
updates.
4.5 File Protection and Backups

Files are subject to corruption, especially during transmission.
Therefore, we recommend that you keep backups of at least your
last two Database Extract files and Submittal files in case errors
occur during transmission of the Submittal file or during the Load
Saving Generations
process. We recommend that you
plan on saving at least two
PC DataPrep provides a quick way to create and organize backup generations of all your files
copies of these files. The process for backing up files is described and reports. DataPrep can
in detail in Section 5.2.4. help you using the File
Backup utility.
While we recommend a minimum of two generations, the sample
JCL for z/OS LE Version 3.1 environments provided in Appendix
G allows for four generations of backups. Mainframe operators
who use the sample JCL provided in Appendix G will find that a
backup of the Submittal file, named NSLDS.SUBMIT.BKUP, is
created automatically by the software.
June 2007 Version 4

22
4.6 Using Servicers

While your school remains responsible for the timely and accurate
submission of its data to NSLDS, you can choose to work with a
servicer or third-party (including a centralized collection office for
a multi-campus school) to process and submit all of your loan-level
Institutional Responsibility
records to NSLDS. Because systems and
procedures vary significantly
If you use a servicer, you must consider and incorporate into your from one institution to
reporting procedures the following: another, each school is
responsible for determining
how it will meet the NSLDS
• Coordinating Any Changes to Identifiers—Whenever an reporting requirements.
identifier changes, you must submit the new identifier on every
loan affected by the change. This must be done through the
servicer.
• Transferring Records From School to Servicer or Third

Party—The organization reporting on a loan must report all
attributes for that specific loan. If the responsibility for
reporting on a specific loan is transferred from one party to
another, all the data for that loan must be transferred. The
receiving party must then continue to report all required
attributes on that loan even though there may not be updates to
a specific attribute.
For example, when a school transfers a loan to a servicer, the

school must transfer all the data for that loan, including the
student’s enrollment status at the time the loan was first
disbursed. Although the servicer may not update this attribute,
the servicer must include it as part of the loan record that it
extracts and submits to NSLDS. All data fields in the NSLDS
extract should be transferred.
• Changing Servicers—If a school changes servicers, it must

carefully coordinate with both the current and new servicers to
ensure that all data are properly transferred. Regardless of any
change in servicer, the school is expected to transmit the
Submittal file within 90 days from the date the new servicer
becomes responsible for servicing the loans. ED has
determined that servicers should transfer portfolios using the
same file layout as a Submittal file to NSLDS. The same data
should be extracted and prepared as would be for a Submittal
file. The Database Extract file thus created should be sent to
the new servicer, who in turn should use the Submittal file to
populate its database so it can provide the proper student and
loan identifiers to NSLDS.
June 2007 Version 4

23
4.7 Multiple Schools or School Branches

Servicers that report data for multiple schools, or schools that
report data for multiple branches with separate OPE IDs (Code for
Original Schools), must submit a single file to NSLDS containing
data for all the schools or branches being reported. The NSLDS Numbers of Schools or
DataPrep software has been developed to process a Database Branches
Extract file containing multiple OPE IDs. There is no limit on the
number of school or branch
data sets that can be
If you report data for multiple schools or branches, you must appended together in a
concatenate their data records into one single file for processing single Database Extract file.
through DataPrep. The resulting file should be structured to
contain a Header record, all Detail records, and all PPC records for
the first school or branch, then the same sequence (Header record,
Detail records, Past Period Change records) for each additional
school or branch in turn. The file structure is illustrated in the box
at right. Multiple School/Branch
File Structure
Once you have created the combined Database Extract file, you School 1 Header Record
can process it just like a file containing a single school’s data using School 1 Detail Records
School 1 PPC Records
the DataPrep software. School 2 Header Record
School 2 Detail Records
Note: You should not insert trailer records for individual schools or School 2 PPC Records
branches because DataPrep will do so for you during the Extract School 3 Header Record
Validation process. School 3 Detail Records
School 3 PPC Records
And so on.
June 2007 Version 4

24
Perkins Data Provider Instructions Installation, Utilities, and Testing
Chapter 5: Installation, Utilities, and

Testing
After you have made sure that you meet the system requirements
for Perkins DataPrep Version 3.1, you are ready to install Perkins
DataPrep, set up its utilities, and run test files designed both to test
whether you have installed DataPrep properly and to familiarize
yourself with how DataPrep works.
5.1 Installation
5.1.1 Installing DataPrep on a Windows-Based
PC
Important Installation Notes
• Perkins DataPrep is specifically designed to be downloaded
from the FSA download site address and installed on PCs
running the Windows 2000 or Windows XP Pro operating
systems.
• Perkins DataPrep’s Windows 2000 installation requires you to
have Administrator privileges on the install machine. If you are
unable to install Perkins DataPrep, contact your technical
support staff to set up Administrator privileges on the install
machine.
• Some organizations restrict downloading from File Transfer
Protocol (FTP) sites. If you are unable to download Perkins
DataPrep, contact your technical support staff to ensure that
you have full FTP download privileges.
• The time it takes to download the Perkins DataPrep software
depends on the file size and the speed of your Internet
connection. The table below shows the minimum download
time for various speeds. The actual time will vary depending
on the quality of the phone line and Internet traffic.
Modem 28.8 kbs 33.6 kbs 56 kbs 64 K 128 K 512 K

Speed ISDN ISDN ADSL
Download 49 min 42 min 26 min 22 min 11 min 3 min
Time
June 2007 Version 4

25
5.1.2 Installation Instructions Using Microsoft

Internet Explorer
1. Uninstall all previous versions of Perkins DataPrep on your
machine. If you are reinstalling Version 3.1, uninstall the
previous installation before proceeding.
2. Close all other Windows applications.
3. Open Microsoft Internet Explorer.
4. In the Address field, enter the following URL:
http://www.fsadownload.ed.gov/SoftPerkins.htm.
Then press Return.
5. On the Perkins DataPrep download page, in the Software area,

click Full Download, to start the download. The File
Download box appears.
Note: The box that appears may vary depending on your version of
Internet Explorer.
Note: Ignore the warning message in this box regarding this

download file. The installation program displays the warning
because it cannot find a digital signature with the install file. This
download file and its contents have been checked for viruses.
June 2007 Version 4

26
6. Click Open. Windows will now download the install files to a

temporary folder on the work station. When downloading is
complete, the Perkins DataPrep Setup box appears.
7. Click Next. The License Agreement box appears.
8. After reading the License Agreement, click Yes. The Customer

Information box appears.
June 2007 Version 4

27
9. Change User Name and Company Name if necessary and click

Next. The Choose Destination Location box appears.
10. This box shows the default Destination Folder where the
Perkins DataPrep software will be installed. To accept the
default Destination Folder, click Next. If you wish to install the
software in another folder, click Browse and change it. Then
click Next. The Select Program Folder box appears.
June 2007 Version 4

28
11. Click Next. Now the Select Final Setup Options box appears.
12. Click Next. The Start Copying Files box appears. Review the
information in the Current Settings area. If you wish to correct
any of the settings, click Back.
June 2007 Version 4

29
13. If all settings are correct, click Next. The setup program will
now install the Perkins DataPrep software on your machine.
Progress bars indicate the status of the installation. After the
installation is complete, the Setup Complete box appears.
14. Click Finish. The README document appears if the box for
the README file is checked.
June 2007 Version 4

30
Troubleshooting
While installing the Perkins DataPrep software on your machine,

the Files in Use box may appear.
This box indicates that another Windows program is using one or

more files needed by the Perkins DataPrep installation process.
Make sure that ALL other Windows programs are closed, then
click Retry.
In addition, while installing the Perkins DataPrep software on your

machine, the following error message may appear:
In this case, the installation program cannot check if the above file
needs to be updated. Click OK to continue installation.
5.1.3 Installation Instructions Using Netscape

1. Uninstall all previous versions of Perkins DataPrep on your
machine. If you are reinstalling Version 3.1, uninstall the
previous installation before proceeding. Instructions for
uninstalling Perkins DataPrep are found in Section 5.1.4.
June 2007 Version 4

31
2. Close all other Windows applications.
3. Open Netscape.
4. In the Address field, enter the following URL:

http://www.fsadownload.ed.gov/SoftPerkins.htm.
Then press Return.
5. On the Perkins DataPrep download page, in the Software area,

click Full Download, to start the download. The Enter name of
file to save to… box appears.
Note: The box that appears may vary depending on your version of
Netscape.
6. Click Save to save the “Perkins Setup.exe” file in the folder

displayed at the top of the box, or highlight a different folder
and click Save. (Please remember which folder you save the
“Perkins Setup.exe” file, if you decide to continue the install
later.)
7. Next, the Download Manager box appears with the “Perkins

Setup.exe” file highlighted.
June 2007 Version 4

32
8. Click Launch File in the menu at the top of the window to run
the “Perkins Setup.exe” file. The “Opening Perkins Setup.exe”
box appears.
Note: Ignore the warning message in this box regarding this

download file. The installation program displays the warning
because it cannot find a digital signature with the install file. This
download file and its contents have been checked for viruses.
9. Click OK. Windows will now download the install files to a

temporary folder on the workstation. When downloading is
complete, the Perkins DataPrep Setup box appears.
10. Click Next. The License Agreement box appears.
June 2007 Version 4

33
11. After reading the License Agreement, click Yes. The Customer
Information box appears.
12. Change User Name and Company Name if necessary and click
Next. The Choose Destination Location box appears.
June 2007 Version 4

34
13. This box shows the default Destination Folder where the
Perkins DataPrep software will be installed. To accept the
default Destination Folder, click Next. If you wish to install the
software in another folder, click Browse and select a different
destination folder. Then click Next. The Select Program Folder
box appears.
14. Click Next. Now the Select Final Setup Options box appears.
June 2007 Version 4

35
15. Click Next. The Start Copying Files box appears. Review the
information in the Current Settings area. If you wish to correct
any of the settings, click Back.
16. If all settings are correct, click Next. The setup program will
now install the Perkins DataPrep software on your machine.
Progress bars indicate the status of the installation. After the
installation is complete, the Setup Complete box appears.
June 2007 Version 4

36
17. Click Finish. The README document appears if the box for
the README file is checked.
Troubleshooting
While installing the Perkins DataPrep software on your machine,

the Files in Use box may appear.
June 2007 Version 4

37
This box indicates that another Windows program is using one or

more files needed by the Perkins DataPrep installation process.
Make sure that ALL other Windows programs are closed, then
click Retry.
In addition, while installing the Perkins DataPrep software on your

machine, the following error message may appear:
In this case, the installation program cannot check if the above file
needs to be updated. Click OK to continue installation.
5.1.4 Uninstallation Instructions

1. On your Windows taskbar, click Start, Settings, Control
Panel. The Windows Control Panel appears.
2. Click Add/Remove Programs. The Add/Remove Programs

box appears.
June 2007 Version 4

38
3. Scroll down the list and click NSLDS Perkins DataPrep 3.1.
Click Change/Remove. The Confirm Uninstall box appears.
4. Click OK. The InstallShield Wizard box appears.
5. Click Finish. The InstallShield Wizard box will close.
June 2007 Version 4

39
6. Open Windows Explorer and RIGHT click the NSLDS-

PERKINS-V3 folder (or the folder in which you installed
Perkins DataPrep).
7. Click SHIFT Delete to remove the Perkins DataPrep folder

Administrative Privileges
and its contents. If you run Windows NT and
If you are running Windows NT, the install program will check do not have administrative
privileges to install new
whether you have the administrative privileges required to install software on your computer,
new software. If you do not, you will get this message: you will get a warning when
you try to install DataPrep.
You can still install the
software, but some of its
functions may not work
properly. If you get this
warning, you should check
with your information
technology department
before proceeding.
You can still install DataPrep, but some of its functions might not
work properly. For example, you might not be able to print from
the DataPrep viewer. Check with your information technology
department before proceeding.
During the setup procedure, you must specify where the DataPrep
system files are installed. We strongly recommend that you use the
default path C:\Nslds-v3.
June 2007 Version 4

40
When you start PC DataPrep for the first time, the Directories
dialog box (Figure 5–1) appears, prompting you to select where
DataPrep’s work files are located. DataPrep supplies default
directory paths, but you can change them as needed. It is essential
that you supply the paths to where your working files are in fact Directories
located, or DataPrep will be unable to find your data. You must These are the folders where
DataPrep working files are
also specify the correct directory paths when you transmit your stored:
data to NSLDS via SAIG.
• Temp—the location of
When you are satisfied with the directory paths listed in the your temporary sort work
Directories dialog box, click OK. files (*.tmp)
• Extract—the location of
your Database Extract
file (extract.ff)
• Current—the location of
the TEF file (TEF.ff) and
all DataPrep output files
(*.ff)
• Backup—the location of
your backup file folders
(yCCYYmMM)
• Loan—the location of
the Loan Detail file
obtained by special
arrangement (loandtl.ff)
Figure 5–1, Directories Dialog Box
If you have named a path that does not currently exist, DataPrep
will ask you if you want to create it. Click Yes to do so.
June 2007 Version 4

41
5.1.5 Installing DataPrep on a z/OS LE Version

3.1 or Higher Mainframe
To install DataPrep on your mainframe, you must first install the
Installation JCL that appears in Step 1 of Appendix G. This
Installation JCL is not included on the tape that contains the rest of
DataPrep for z/OS LE Version 3.1, so you must create your own z/OS LE, Version 2.4 or
copy. Your site will probably have a JCL file for executing Higher
IEBCOPY that closely resembles the Installation JCL. To create For DataPrep to work on
your mainframe, you must
the Installation JCL, make a copy of the IEBCOPY JCL and be running z/OS LE, Version
modify it so it contains the same file names as the Installation JCL 3.1 or higher.
in Step 1 of Appendix G.
Run the Installation JCL once to unload the Unload JCL that
appears in Step 2 of Appendix G from the DataPrep tape. Then run
the Unload JCL once to unload and install the actual libraries and
software that will allow you to run DataPrep. If you need to run the
Unload JCL again to reinstall DataPrep, be aware that step
PSTEP005 will delete all data sets previously created.
Note: By installing DataPrep JCL for z/OS LE Version 3.1, you

will be creating data set names on your system. The second and
last node in all data set names created by DataPrep contain
identifying information (Version/Release/Levelset Date) meant to
track which release of DataPrep you are using. We strongly
recommend that you retain this naming convention.
The Unload JCL can be referenced from the library created by the
Installation JCL with CUTTAPE as part of the name. The library
member name is UNLOAD.
June 2007 Version 4

42
5.2 Options and Utilities

5.2.1 Changing Directory Paths
If at some time after installation you decide to change the directory
path for any of DataPrep’s working files, follow these steps:
1. From the DataPrep Main Menu, click Options and then

Directories. Directories and Folders
The terms “directory” and
“folder” refer to the same
object but viewed from
different perspectives. Both
refer to a place where files
are stored. That place is a
directory when it is viewed
from the point of view of a
computer or network’s total
file structure. The directory
path is the route a program
takes through that file
structure to find an individual
file. A folder is the visual
representation of the
directory as an individual
icon (as in a desktop
shortcut) or within My
Computer or Windows
Explorer.
Figure 5–2, DataPrep Main Menu with Directories

Selected on the Options Menu
2. The Directories dialog box appears.
June 2007 Version 4

43
Figure 5–3, Directories Dialog Box
3. Select new directory paths in one of two ways:
A. Type the new path into the text box.
B. Press the Browse button to the right of the text box and use
the Select File Directory dialog box that appears to select
the new path.
4. Click OK to save your changes.
Note: If you change the directory path for your Current folder, you
must use Windows Explorer or My Computer to copy the
following files from your old Current directory to your new
Current directory: Copy Your Sort Files
If you use the Directories
dialog box to change the
• ERRDTL.sel directory path for your
• ERRDTL.srt Current folder after you have
installed DataPrep, you must
• ERRDTL.var
be sure to copy the files
• LOANDTL.sel containing sort parameters
• LOANDTL.srt from your old Current
• LOANDTL.var directory to your new
Current directory. Those files
• TEF.ff have names that end with
the following suffixes:
If you fail to copy these files to your new Current directory,
DataPrep will be unable to sort your detailed Extract Error report • .sel
or Load Process Error report. • .srt
• .var
In addition, you may wish to copy any additional files that you
wish to retain.
June 2007 Version 4

44
5.2.2 Viewers
DataPrep allows you to generate a series of reports as you move
through the NSLDS update process. To view and print those
reports, you must use a viewer. When you install DataPrep, it
automatically establishes its own built-in viewer (uta0.exe) as the
default viewer for reports. This viewer was designed to display and
print reports in the correct format, and we recommend that you
become familiar with its features.
You can also use Notepad, WordPad, and some word processing
software as viewers. However, if you use them, you might have to
reformat reports to fit on screen or on paper. In addition, you may
need to increase your desktop size to at least 1024 by 768 pixels to
view reports without having to scroll horizontally.
Likewise, when you print reports from the DataPrep viewer

(uta0.exe), it automatically formats them so they look on the page
much as they do on screen, and so the individual rows of the report
are not broken across two or more lines of print. If you use another
viewer, you will need to set your printer options with care to
achieve equally good results.
There are situations in which you will want to use a viewer other
than the DataPrep viewer (uta0.exe) to view or print reports. The
figures in this manual frequently use Notepad to make the contents
of reports larger and so easier to read. But to view and print reports
that are correctly formatted, we recommend that you use the
DataPrep viewer (uta0.exe).
The DataPrep Viewer (uta0.exe)
The DataPrep viewer (uta0.exe) includes the following features,

which are deployed down the right side of your screen when it
displays:
• A drop-down zoom box—You can also zoom in by left

clicking on the text of the report, or zoom out by right clicking
on it.
• A button that centers the report on the screen.
• A spin box that allows you to navigate through the report one
page at a time.
June 2007 Version 4

45
• Fast-forward and rewind buttons that allow you to move

directly to the first or last page of the report.
• A Print Current Page button.
• A Print button.
• An Exit button.
• A Help button.
Changing Your Default Viewer
To change your default viewer for all reports, follow these steps:
1. From the DataPrep Main Menu, click Options and then

Viewers.
Figure 5–4, DataPrep Main Menu

with Viewers Selection on the Options Menu
2. The Viewer Maintenance dialog box appears.
June 2007 Version 4

46
Selecting the Viewer

The word processing
software at the top of the
Viewer Programs list is the
default viewer. To change
the default viewer, follow
Figure 5–5, Viewer Maintenance Dialog Box these steps:
1. Select the viewer you

The word processing software that appears at the top of the list is want to make the default
the default viewer for viewing and printing reports. To change the by highlighting it.
default viewer, follow these steps: 2. Click Move.
3. Point to the top of the list
1. Select the viewer you want to make the default by highlighting and click.
4. Click OK.
it.
The viewer you selected will
2. Click Move. be moved to the top of the
list, and DataPrep will use it
3. Point the cursor to the top of the list and click. This will move by default to view reports.
the highlighted software to the top of the list.
4. Click OK to exit the dialog box.
To change your default viewer, you must select the viewer you
want and move it to the top of the Viewer Programs list before
clicking OK. Just selecting a viewer and clicking OK will not
change your default viewer. Move the Viewer Before
Clicking OK
To change your default
If you want to add other word processing software to the viewer viewer, you must select the
list, click Add and then specify the directory path for the software viewer you want and move it
you want to add. to the top of the list before
clicking OK. Just selecting a
viewer and clicking OK will
To remove a viewer from the list, highlight it and then click not change your default
Remove. DataPrep will ask you to confirm that you want to delete viewer.
the viewer program from the list.
You can use any viewer to view a particular report after it is

generated, as long as it is one of the viewers on the list. But you
can only change the default viewer from the Viewer Maintenance
dialog box.
June 2007 Version 4

47
Changing Viewers for a Single Report
To select a different viewer for a single report without changing

your default viewer, follow these steps:
1. If you have already generated a report and displayed it in a

viewer, close or minimize the viewer and return to the report
dialog box from which you generated the report.
2. Click Viewer to display the Select Viewer dialog box. It will

display DataPrep’s built-in viewer (UTA0.exe), Notepad,
WordPad, and any other viewers you have installed using the
Viewers command on the Option menu.
Figure 5–6, Select Viewer Dialog Box
3. Select the viewer you want to use and click OK to view the
report.
This process only changes the viewer for the report you are
currently viewing. To change your default viewer, see the previous
subsection.
5.2.3 File Transfer

DataPrep’s File Transfer utility allows you to import specific files
associated with DataPrep and the NSLDS update process. You can
import the following files sent to you by NSLDS, normally via the
Student Aid Internet Gateway (SAIG):
June 2007 Version 4

48
• Load Process Error File (Message Class SLDERROP)
• Loan Detail File (Message Class SLNDTLOP)
• Error Submittal Summary Notification File (Message Class

SHSNTFOP)
(Note: To import the Thresholds, Error Codes and Field Codes

File, go to www.fsadownload.ed.gov).
When you import a file, the File Transfer utility copies (or moves)
it to the default folder for files of that type and renames it so
DataPrep will recognize it.
To import a file using the File Transfer utility, follow these steps:
1. From the DataPrep Main Menu, click File Transfer. The File
Transfer dialog box appears.
Message Class Input and

Output Files
Figure 5–7, Initial File Transfer Dialog Box for File Import Regardless of what file
name you insert in the input
2. Select the action you want to perform. DataPrep displays the screen, DataPrep will
default directory path for files of that type as the DataPrep File change the output name so
Output (Figure 5–7). You cannot change this default path. DataPrep can recognize the
file. The TEF file message
However, if you are importing an NSLDS Loan Detail file class, TEFFILOP, will output
(Section 10.3.1), DataPrep does give you the option of as TEF.ff.
assigning it a version name.
June 2007 Version 4

49
3. Press the Browse button to the right of the NSLDS File Input
box to display the Select NSLDS File dialog box. It will
display with the File of type option at the bottom of the dialog
box set to the kind of file you seek. Browsing for Files
When you browse for files,
For example, the first time you select Import Thresholds, Error make sure that the Files of
type option is set to the file
Codes and Field Codes File as an action and click browse, you type you seek or to All Files
should see a dialog box similar to the one in Figure 5–8. Notice (*.*).
that the File of type option is automatically set to Received
TEF File (teffilop.*).
Where to Look
These instructions assume
that when you receive files
from NSLDS via SAIG, they
Figure 5–8, Initial Select NSLDS File Dialog Box for TEF File are saved to a directory
named C:\IAM\ DATA. If you
4. Use the Look in option at the top of the dialog box to locate the store them elsewhere, you
folder that contains the NSLDS file you want to import will need to adjust
(normally C:\IAM\DATA). You can select any folder you have accordingly.
access to on your computer or network.
June 2007 Version 4

50
Figure 5–9, Final Select NSLDS File Dialog Box for TEF File
5. Select the file you want to import. Whatever file you select will
be displayed as the default NSLDS File Input option the next
time you import the same type of file. Click Open to return to
the File Transfer dialog box.
Figure 5–10, Final File Transfer Dialog Box for File Import
6. Clicking on the blue plus signs to the right of the Browse

buttons for the NSLDS File Input and DataPrep File Output
boxes displays a File Information message box you can use to
check that you are transferring the right file and that it is more
recent than any file it might replace.
June 2007 Version 4

51
7. If you displayed the File Information message box, click Exit

to return to the File Transfer dialog box.
8. Check that the directory paths in both the NSLDS File Input
and DataPrep File Output boxes are correct and click Copy or
Move. If a file of the type you are transferring already exists in
the destination folder, a message similar to the following Copy or Move
When you use DataPrep’s
displays: File Transfer utility to copy a
file, DataPrep copies and
pastes the file to a new
location. When you use it to
move a file, DataPrep cuts
and pastes the file to a new
location.
9. Click Yes to continue. If the copy or move is successful,

DataPrep displays a message similar to the following:
5.2.4 File Backup

We strongly recommend that you regularly back up all your data
files. Regular backups give you a full record of your submissions
to NSLDS and a potentially invaluable audit trail. DataPrep’s File
Backup function helps you copy or move files from your working
folders (Current, Extract, and Loan) to back up folders of your
choice. It also helps you maintain backups after you create them.
In addition, you can use it to delete backup files and folders when
you no longer need them.
June 2007 Version 4

52
To create a new backup folder, follow these steps:
1. From the DataPrep Main Menu, click File Backup.
Figure 5–11, DataPrep Main Menu with File Backup Selected
2. The File Backup dialog box appears. The Current Files list
shows all the DataPrep files (*.ff files) in your Current,
Extract, and Loan folders. It also lists each file’s last modified
date and time, and size in bytes. The Backup Folders box lists
all the folders in your Backup folder (C:\DataPrep\Backup).
June 2007 Version 4

53
Figure 5–12, Backup Files Dialog Box
3. To create a new backup folder, click New. The New Backup

File Folder dialog box appears with a default New Folder name
based on current year and prior month or next year and month
that does not have a folder.
Moving/Copying Files to
Figure 5–13, New Backup File Folder Dialog Box Backup Folders
Before you can move or
4. Use the New Folder counter to select the month and year of the copy files to a backup folder,
new backup folder. When you are satisfied with the New you must select the file(s)
Folder name, click OK to return to the Backup Files dialog and the folder. You can
determine the creation date
box. and time and number of
bytes in each file by moving
5. Select the file(s) you want to move or copy to the new folder. the scroll bar to the right
To select a file from the Current Files list, click on it and margin or by double-clicking
DataPrep will highlight it. Click on it again to de-select it and the file name.
remove the highlighting. You can select or de-select a group of
files by clicking on the first file in the group and then holding
down the shift key while you click on the last.
June 2007 Version 4

54
Figure 5–14, Backup Files Dialog Box with Files Selected
6. Select the backup folder in which you want to store the files by
clicking on it in the Backup Folders box.
Figure 5–15, Backup Files Dialog Box with Files and Backup
Folder Selected
7. Click Copy (or Move) to copy (or move) the files you selected
to the backup folder you selected.
June 2007 Version 4

55
If you copy files, DataPrep will leave the original files in the
Current, Extract, or Loan folders and create copies in the
backup folder you selected. In this case, the original files will
still be listed by the File Backup dialog box.
Figure 5–16, Backup Files Dialog Box after Copy
If, on the other hand, you move the files, DataPrep will remove
the originals from the Current, Extract, or Loan folders and
move them to the backup folder you selected. In this case, the
files will disappear from the File Backup dialog box.
Figure 5–17, Backup Files Dialog Box after Move
June 2007 Version 4

56
Several other features of the File Backup utility are worth

knowing.
From the File Backup dialog box, you can check a file’s last
modified date and time and size in bytes by double clicking on it.
From the File Backup dialog box, you can check the contents of an
existing backup folder by selecting it and then clicking List to
display the List Backup Files dialog box.
Figure 5–18, List Backup Files Dialog Box

Deleting Backup Files and
From the List Backup Files dialog box, you can delete individual Folders
backup files by selecting them and clicking Delete. DataPrep will If you want to delete a
ask you to confirm any deletions by displaying the following backup folder, delete all the
files in the folder. Then click
message: Delete again, and DataPrep
will ask you to confirm that
you want to delete the folder.
June 2007 Version 4

57
You can delete the backup folder itself by first deleting all the files
it contains and then clicking Delete again. DataPrep will display
the following message:
Click Yes to confirm your intention and delete the backup folder.
5.2.5 Help System

The PC version of DataPrep contains a full-featured Help system
covering these topics:
• All the menus, commands, and buttons on the DataPrep Main

Menu
• The input files, output files, controls, and processing options

associated with each DataPrep dialog box
• Built-in shortcut keys available in DataPrep
The Help system documents all DataPrep’s functions and includes

material not contained in this manual. It is your best source for
detailed information about specific DataPrep functions.
June 2007 Version 4

58
5.3 Running Test Files

Included in both the Windows-based and mainframe installation
software are test files, which will verify that you have installed the
software correctly, and will illustrate how DataPrep works.
File Locations
Here, and throughout this
For Windows-based DataPrep, the following test files are located manual, instructions for
in the Samples folder (C:\Nslds-v3\Samples, assuming you chose copying or moving files
the default directory paths at installation): presuppose that you
installed DataPrep’s work
folders in the following
• Two Database Extract files (extract-fail.ff and extract-pass.ff) default locations:
• A Threshold, Error Code and Field Code (TEF) file (TEF.ff)
• A Load Process Error file (loaderr.ff). • Samples Folder—
• An Error Submittal Notification Summary file (shsntfop.ff) C:\Nslds-v3\Samples
• Backup Folder—
C:\DataPrep\Backup
• Current Folder—
C:\DataPrep\Current
• Extract Folder—
C:\DataPrep\Extract
• Loan Folder—
C:\DataPrep\Loan
If you chose different folder

locations during installation
(Section 5.1.1) or moved
these folders after
installation (Section 5.2.1),
you will need to adjust
accordingly as you copy
files, then test and use
DataPrep.
Figure 5–19, Test Files Installed in C:\Nslds-v3\Samples
For mainframes, the Running Test Files JCL is in Appendix G; it

was unloaded when you installed DataPrep.
June 2007 Version 4

59
5.3.1 Successful Extract Validation

Extract Validation
First, test Extract Validation using the sample Database Extract

file. To test Extract Validation on DataPrep for Windows, follow
these steps:
Copying Test Files
Before you test DataPrep,
1. Use Windows Explorer or My Computer to copy the good you must copy two Database
Database Extract file (extract-pass.ff) from the Samples folder Extract files from the
to the Extract folder (C:\DataPrep\Extract) and rename it Samples folder (C:\Nslds-v3\
extract.ff. DataPrep will only validate files called extract.ff. Samples) to the Extract
folder (C:\DataPrep\
Extracts):
1. A file that should pass

Extract Validation
(extract-pass.ff)
2. A file that should fail
Extract Validation
(extract-fail.ff)
Be sure to copy (copy and

paste) these two files rather
than move (cut and paste)
them from one folder to the
other, so backup copies
remain in the Samples folder
if you need them later.
Use Windows Explorer or

My Computer to copy these
Figure 5–20, C:\DataPrep Folder with Extract and Current files. For more information
Folders about copying or renaming
files, refer to the online Help
2. From the DataPrep Main Menu, click Extract Validation. for Windows.
June 2007 Version 4

60
Figure 5–21, DataPrep Main Menu with Extract Validation

Selected
3. The Extract Validation dialog box appears.
Figure 5–22, Extract Validation Dialog Box
4. Check that the Input directory paths point to the folders where
the Extract and TEF files are located and click Run. The
Extract Validation Process dialog box displays the Extract
Validation Log Report containing a message telling you that
Extract Validation was completed successfully.
June 2007 Version 4

61
Figure 5–23, Extract Validation Process Dialog Box
If you get any other message, or if Extract Validation did not run,
check the following:
• When you copied the file originally called extract-pass.ff to the

Extract folder, you renamed it extract.ff.
• There was a valid TEF file in your Current folder.
• The Extract Validation dialog box showed the correct directory

path for the extract.ff file.
If you get a message that the Database Extract file was processed
successfully, click Close to return to the DataPrep Main Menu.
June 2007 Version 4

62
Extract Validation Log Report
If you wish to redisplay or print the test Extract Validation Log

report, do the following:
1. From the DataPrep Main Menu, click Log Report. The Log
Report dialog box appears.
Figure 5–24, Log Report Dialog Box
2. Select the Extract Validation Log file (C:\DataPrep\

Current\extrlog.ff) in the Log Files list by clicking on it, and
then click View. Your default viewer displays the Extract
Validation Log report.
Figure 5–25, Sample Log Report
June 2007 Version 4

63
When the Log report displays successfully, click Exit twice to

return to the DataPrep Main Menu.
Extract Error Reports
You are now ready to produce test Extract Error reports. To do so,
follow these steps:
1. From the DataPrep Main Menu, click Error Report. The Error
Figure 5–26, Error Report Dialog Box

Selecting Files for Reports
For DataPrep to create an
2. Select Extract Validation as the Error Source. Extract Error report (or any
other report), you must
3. Select Summary as the Report Type. select the individual file from
which you want to generate
the report. Select a file from
4. Select the error file listed in the Error Files list
the Error Files list by clicking
(C:\DataPrep\Current\extrerr.ff). on it. Files that have been
selected will appear
5. Click Generate. The Summary Error Report dialog box highlighted on your monitor
displays a Status message saying, “The Error Summary Report screen.
has been generated.”
June 2007 Version 4

64
6. Click View. Your default viewer displays the Summary Extract

Error report.
Figure 5–27, Summary Extract Error Report
If this report appears, you have successfully generated the Extract

Validation Summary Error Report.
To create an Extract Validation Detail Report, follow the same

steps as outlined above except in Step 3 change “Select Summary
as the Report Type” to “Select Detail as the Report Type.”
Now that you have verified that you installed DataPrep

successfully, and have generated Extract Error reports, you should
strengthen your familiarity with DataPrep by returning to the
DataPrep Main Menu and running error reports using different sort
criteria and different viewers. Then look over the reports to get a
good idea of what they are like. You can also check Chapters 10
and 12 for more information about reports.
June 2007 Version 4

65
5.3.2 Unsuccessful Validation

Now you are ready to run the second test and see what happens
when a Database Extract file contains too many errors. To do so,
follow these steps:
1. Rename the extract.ff file in the Extract folder extract-pass.ff.
2. Copy the file named extract-fail.ff from the Samples folder

(C:\Nslds-v3\Samples) to the Extract folder and rename it
extract.ff.
Figure 5–28, Extract Folder
3. From the DataPrep Main Menu, click Extract Validation. The

Extract Validation dialog box appears.
June 2007 Version 4

66
Figure 5–29, Extract Validation Dialog Box
4. Check that the Input directory paths point to the folders where
the Extract and TEF files are located and click Run. The
Extract Validation Process dialog box displays the Extract
Validation Log Report containing a message informing you,
“The percentage of domain errors exceeds the allowable
tolerances. Therefore, no Submittal File has been created.”
(Figure 5–30)
Figure 5–30, Extract Validation Unsuccessful
June 2007 Version 4

67
If this message appears, return to the DataPrep Main Menu and run
the Extract Error reports using the directions in the previous
subsection. You may also want to print the Extract Validation Log
Report as explained in a previous subsection.
If you want to know more about reports, use the instructions in

Chapter 9 to generate detailed Extract Error reports with different
sort criteria, then view them in the different viewers available in
DataPrep (Section 5.2.2).
5.3.3 Test Load Process Error Report

Now you are ready to generate a sample Load Process Error report.
Before you can do so, you must import the sample Load Process
Error file into the Current folder.
Mainframe Testing
You could use Windows Explorer or My Computer to copy these For testing the Load Process
files, but instead we will use DataPrep’s File Transfer function as a Error Report function for
mainframes, refer to
way of introducing you to that useful capability. Appendix G.
Import the Load Process Error File
1. From the DataPrep Main Menu, click File Transfer. The File
Transfer dialog box appears.
Figure 5–31, Default File Transfer Dialog Box
2. Select Import Load Processing Error File as the Action.

DataPrep will change the default DataPrep File Output to
C:\DataPrep\Current\loaderr.ff (Figure 5–32).
June 2007 Version 4
68
Figure 5–32, Initial File Transfer Dialog Box for Load Process
Error File
box to display the Select NSLDS File dialog box.
4. Set the Look in option to Samples (C:\Nslds-v3\Samples) and

the Files of type option to Load Process Error Files (loaderr*.*)
or to All Files (*.*).
Browsing for Files
When you browse for files,
make sure that the Files of
type box is set to the file
type you seek or to All Files
(*.*).
Figure 5–33, Select NSLDS File Dialog Box for Load Process
Error File
5. Select the Load Process Error file (loaderr.ff) and click Open
to return to the File Transfer dialog box.
June 2007 Version 4

69
6. Check that the directory path in the DataPrep File Output box
appears as it does in Figure 5–34 and click Copy.
Figure 5–34, Final File Transfer Dialog Box for Load Process
Error File
7. If the copy is successful, DataPrep displays the following

message:
If you have successfully run Extract Validation, there is already a

current TEF file in your Current folder (C:\DataPrep\Current). If
there is not a TEF file in your Current folder, you should use
DataPrep’s File Transfer utility to copy it there from the Samples
folder now.
Generate the Load Process Error Report
After you’ve successfully imported the Load Process Error file,

you are ready to generate a Load Process Error report. To do so,
follow these steps:
1. From the DataPrep Main Menu, click Error Report. The Error
June 2007 Version 4

70
Figure 5–35, Error Report Dialog Box for Load Process Error
Report
2. Select the Error Source, Report Type, Selection Criteria, and

Sort Sequence options shown in Figure 5–35.
3. Highlight the Load Process Error file (C:\DataPrep\Current\

loaderr.ff).
4. Click Generate. The Summary Error Report dialog box

displays a Status message saying, “The Error Summary Report
has been generated.”
5. Click View. The default viewer displays the Load Process

Error report.
June 2007 Version 4

71
Figure 5–36, Test Load Process Error Report
After looking over the report, try to generate other Load Process
Error reports; including detail reports with different sort options.
Refer to Section 10.2 for more information about generating error
reports.
5.3.4 Test Error Submittal Notification Report

Import the Error Submittal Summary Notification File
Now you are ready to generate a sample Error Submittal

Notification report. First, you may use DataPrep’s File Transfer
function to import the sample Error Submittal Notification file into
the Current folder. Alternatively, you may use Explorer or My Reports
Computer to move files from one folder to another. Creating reports is a three-
step process:
1. From the DataPrep Main Menu, click File Transfer. The File 1. Copy the file containing
Transfer dialog box appears. data for the report into
the Current folder
2. Select Import Error Submittal Summary Notification File as the (C:\DataPrep\Current).
Action. 2. Generate the report.
3. View the report.
June 2007 Version 4

72
Figure 5–37, Initial File Transfer Dialog Box for Importing Error
Submittal Summary Notification File
box to display the Select NSLDS File dialog box.
4. Set the Look in option to Samples (C:\Nslds-v3\Samples) and

the Files of type option to Submittal Notification Files
(shsntfop*.*) or to All Files (*.*).
Figure 5–38, Select NSLDS File Dialog Box for Submittal

Notification Files
5. Select the Submittal Notification File (shsntfop.ff) and click

Open to return to the File Transfer dialog box.
June 2007 Version 4

73
6. Check that the directory path in the DataPrep File Output box
appears as it does in Figure 5–39 and click Copy.
Figure 5–39, Final File Transfer Dialog Box for Importing Error
Submittal Summary Notification File
7. If the copy is successful, DataPrep displays the following

message:
Generate the Error Submittal Summary Notification

Report
Now you are ready to generate the Error Submittal Summary

Notification report. To do so, follow these steps:
1. On the Report menu of the DataPrep Main Menu, click

Notification. The Notification Report dialog box appears.
June 2007 Version 4

74
Figure 5–40, Notification Report Dialog Box
2. Select the Error Submittal Summary Notification file

(C:\DataPrep\Current\shsntfop.ff) and click Generate. The
Generate Notification Rpt dialog box displays a Status message
saying, “The Error Submittal Summary Notification Report has
been generated!”
3. To view the report, click View. Your default viewer displays

the report.
June 2007 Version 4

75
Delete All Sample Files

Once you are finished testing
DataPrep, you should delete
from DataPrep’s working
folders (C:\DataPrep and its
folders) all the sample files
you used and reports you
created during testing. That
way, you won’t confuse them
with real data once you begin
processing your institution’s
Database Extract file.
Do not delete TEF File nor

the sort and selection files
(that is, files with .srt, *.sel,
and *.var type).
Figure 5–41, Error Submittal Summary Notification Report Leave the TEF file (TEF.ff)
as well as the sort and
selection files in the Current
folder (C:\DataPrep\Current)
5.4 Deleting Test Files because you will need them
to process your first live
Before you start using DataPrep to process live data, you should Submittal file.
delete from DataPrep’s working folders (C:\DataPrep and its
folders) all the sample files you used and reports you created while And Remember
You may need the sample
testing DataPrep. You can use either Windows Explorer or files for later testing or
DataPrep’s File Backup function (Section 5.2.4) to delete them. To diagnostic purposes, so
delete test files using DataPrep, follow these steps: make sure that you have
copies of them in the
1. From the DataPrep Main Menu, click File Backup. The File Samples folder (C:\Nslds-
v3\Samples). If necessary,
Backup dialog box appears. Its Current Files list shows all the copy sample files back from
files in your Current, Extract, and Loan folders except sort and the working folders to the
selection files. Samples folder before
deleting them from the
working folders.
June 2007 Version 4

76
Figure 5–42, File Backup Dialog Box
2. Click New. The New Backup File Folder dialog box appears
with a default New Folder name.
Figure 5–43, New Backup File Folder Dialog Box
3. Click OK. A new backup folder appears in the Backup Folders

list of the File Backup dialog box.
June 2007 Version 4

77
Figure 5–44, File Backup Dialog Box
4. Select both the backup folder and all the files listed in the
Current Files list except for the TEF file (TEF.ff). Then click
Move, and DataPrep will move all the files you selected to the
new backup folder.
5. Click List to display the List Backup Files dialog box with a
list of all the files in the backup folder.
Figure 5–45, List Backup Files Dialog Box
6. Highlight all of the files in the Backup Files list, and then click
Delete to delete them from the backup folder.
7. Click Delete again to delete the backup folder.
June 2007 Version 4

78
You are now ready to begin using DataPrep to process your real
data. If you have any problems, remember to call the CSC at 800-
999-8219.
Problems?
If you have any problems with
installation or testing, call the
5.5 Sample Files z/OS LE Version 3.1 CSC at 800-999-8219
between the hours of 8 a.m.
and 8 p.m. Eastern Time,
The JCL for mainframes (IBM or fully compatible CPU) running
Monday through Friday
z/OS LE Version 3.1 or higher performs the Extract Validation excluding Federal holidays.
Process and error file generation. Appendix G contains the JCL for
these functions. It can be referenced from the library created with
JCLLIB as part of the name. The library member name is
PRBB1000.
The JCL references a sample Database Extract file containing 50

student/loan records of which 2 are in error. This should be
reported in the Extract Validation Log report, the Detail Extract
Error Report, and the Summary Extract Error Report.
A second sample Database Extract file contains 100 student/loan

records. Eight are in error, which causes the file to exceed the ED-
established error threshold. When you run this sample file, no
Submittal file should be created. To use the second sample, you
must change the JCL to reference the sample extract containing
DBEXTERR as part of the name.
The JCL also references a sample Load Process Error file

containing 36 student/loan records for 3 different schools, all in
one Database Extract file. School 002021 has 11 errors, school
003554 has 7 errors, and school 004920 has 2 errors. This should
be reported in the Detail Error Report and the Summary Error
Report.
June 2007 Version 4

79
Perkins Data Provider Instructions The Database Extract File
Chapter 6: The Database Extract File

The first step in the NSLDS update process is for you to create a
Database Extract file that accurately reflects the contents of your
school’s database(s) at the time of the extract. The Database
School Requirements
Extract file you create must follow the standards defined by this You must create a Database
chapter and the record layouts in the Federal Perkins Loans Data Extract file once a month
Dictionary (Appendix A). Remember that the Database Extract file and no more than 14 days
must be named extract.ff for DataPrep to work properly. prior to the load date
scheduled by NSLDS. The
file must be an exact
DataPrep does not create a Database Extract file, so you are reflection of your database
responsible for determining how to create the file from your and should not be edited or
school’s records or database(s). The Database Extract file you changed. The Database
create is subject to audit by ED. Extract file is fully auditable,
field by field, to your
database.
6.1 Business Rules

As a data provider, you must observe these business rules:
• Report all Federal Perkins loans that were open or closed on or

after October 1, 1989. An edit will reject any loan closed
before October 1, 1989. You can prevent unnecessary rejects
by not extracting such loans.
• Do not report closed loans already reported and successfully

loaded into the NSLDS database. For example, suppose a
borrower makes the final payment on a loan in March 1999.
You report the loan as paid in full (PF) with your April
submittal; the record contains no errors and updates NSLDS.
Because the loan was loaded into the NSLDS database, you
should not extract this loan record again when you create future
Database Extract files. If an error was made in closing the loan
and you need to reopen it, add the loan to your next Database
Extract file with the new information. If the loan record passes
all edits, NSLDS will load it and update the loan accordingly.
• Continue to report loans you assign to ED until you receive

notice that the loan has been accepted by ED. Once you receive
such notice, do not report the loan.
• Report new loans or updates to existing loans monthly on a

schedule established by NSLDS. The data you report must be
current and not extracted earlier than shown on your
established reporting schedule (that is, no more than 14 days
before the scheduled load date).
June 2007 Version 4

80
• Create Database Extract files that meet the detailed

specifications contained in Appendix A. You are responsible
for coding and testing your software as needed to properly
format the Database Extract file.
• If you report a loan with an open status, it must have a positive

Outstanding Principal Balance. If the loan has a balance of less
than $1, but not zero, you should report the Outstanding
Principal Balance as $1. If the loan is being maintained in an
open status because of a negative balance on the account (that
is, a credit balance), you should also report a balance of $1
until the loan is closed.
• The Date of Outstanding Principal Balance reflects the date of

the most recent change in the principal balance. The
Outstanding Principal Balance may change due to a
disbursement, loan payment, or cancellation. Since you submit
all loans in your database every month, the requirement to
update Outstanding Principal Balance on a quarterly basis is
eliminated. Instead, you must update the dollar amount and the
date of the Outstanding Principal Balance using the current
remaining amount and the date of the most recent change in
Outstanding Principal Balance. If you have been reporting the
last day of the month as the Date of Outstanding Principal
Balance regardless of when the balance actually changed, you
must modify your extract procedure to provide the actual date
when the balance changed.
6.2 Record Types

The Database Extract file contains three types of records:
1. Header Record
2. Detail Records
3. Past Period Change Records
The Database Extract file must not have a Trailer record, as

DataPrep will create a Trailer record during the Validation process.
June 2007 Version 4

81
6.2.1 Header Record

The Header record is for identification and tracking purposes. It
contains your school code; the submittal, initial load, and submittal
receive dates; the software version and release number; and the
Version and Release
record type. The capital letter H must appear in position 48 of the Number
Header record as the record type. DataPrep will automatically
insert its version and release
number in the Header
record, so you should leave
6.2.2 Detail Records this field blank when creating
the Header record for your
The Database Extract file must contain a separate Detail record for Database Extract file.
each loan record in your school’s database(s) that belongs to one of
the following categories:
• Loans that are currently open
• Loans that were closed on or after October 1, 1989, but not

successfully reported as closed to NSLDS
Individual Detail records must reflect the exact contents of your Initial Population
If you are a data provider
database without editing or other changes. submitting data to NSLDS
for the first time, that
Continue extracting and reporting loans to NSLDS until one of the submission is referred to as
following occurs: the Initial Population. During
that submission, you must
report to NSLDS not only all
• The loan is closed and successfully reported to NSLDS with a outstanding (open) loans,
Closed loan status. If you report the loan to NSLDS but the but also any loans that have
loan record is not accepted because of error conditions, you been closed on or after
must continue reporting the loan until it is accepted. Valid October 1, 1989.
closed loan status codes are listed in Table B–2 in Appendix B.
• Your school has assigned a loan to ED, received notice from

ED that it has accepted the loan, and you have successfully
reported the loan to NSLDS (that is, contains no errors).
Once either of these events occurs, you should no longer extract

that particular record when you create your Database Extract file.
Let us look at an example. When a borrower makes the final

payment on a Perkins loan, perform the following actions:
1. Extract the record from your database.
June 2007 Version 4

82
2. Report the activity with a valid closed loan status code (see
Appendix B–2).
3. Include the record in your next submission to NSLDS.
You should continue reporting this loan until it is accepted without

errors by NSLDS. Then your school should stop reporting on this
loan and no longer include it in future Database Extract files. Loans Erroneously
Reported as Closed
If a loan was erroneously
Loans that were nullified because they were incorrectly reported, reported as closed, you must
and loans that were awarded but the borrower did not go through include this loan in your next
with them, should be reported with a Loan Status Code of CA Database Extract file with
(Cancelled). the correct loan status and
date.
6.2.3 Past Period Change Records

PPC records enable you to correct reporting errors for events that
are stored in NSLDS as history, and therefore, cannot be corrected
by a Detail record. Use PPC records to:
Past Period Changes
1. Delete historical events that were reported in error (for When you develop a
process to extract records
example, an event reported for the wrong borrower). from your school’s database,
be certain it includes the
2. Correct historical events that cannot be adjusted simply by ability to identify and create
updating current data fields (for example, a previously reported PPC records in the
loan status that should have been reported with another value at Database Extract file. PPC
records require the
the time it was originally reported). previously reported event
date so that the specific
PPC records can be added to the Database Extract file anywhere posting can be corrected.
after the Header record, so you can easily append them to the file
after extracting Detail records from your database. Appendix C identifies which
attributes require this special
transaction for proper
correction.
6.3 File Standards
Each record in the Database Extract file must be in a 300-byte
layout without carriage returns and line feeds between records.
However, if you are a Windows user, you can leave carriage return
and line feed combinations in the Database Extract file because
DataPrep will strip them out before creating a Submittal file.
Database Extract files should be in the following formats:
• Fixed-Length EBCDIC for mainframes running z/OS LE

Version 3.1 or higher
June 2007 Version 4

83
• ASCII for PCs running Windows
You must combine all loan records you report on into a single
Database Extract file, even if you have loan data stored in multiple
databases or are reporting for several campuses or branches in the
same extract.
Multiple Databases
As you create Detail records for your Database Extract file, keep in All data must be combined
mind the following considerations: into a single Database
Extract file, even if you have
loan data stored in multiple
• Once you create your Database Extract file, you must use the databases or are reporting
DataPrep software to validate it for submittal to NSLDS. Use for several campuses or
the Extract Error report generated by DataPrep to correct any branches in the same
errors in your database before the next time you create your extract.
Database Extract file. Do not correct errors by editing or
otherwise altering the Database Extract file or any subsequent
files created by DataPrep.
• All data (including identifiers) must be reported until the

record containing that data passes all associated NSLDS edits.
Several Schools or
Verify that a record has been loaded onto NSLDS by checking Branches
the Load Process Error report for errors against that record. If you report for several
schools or branches, see
• Because the Detail records in the Database Extract file concern Section 4.7 for additional
information.
individual loans, you must report (and update) all information
at the loan level. This means, for example, that if you report on
three loans for the same student and the loans were first
reported with the wrong Date of Student’s Birth, you must
update the New Date of Student’s Birth on each of the three
loans. Updating the New Date of Student’s Birth on only one
loan will not update the erroneous date of birth on the other
two loan records.
June 2007 Version 4

84
6.4 Field Standards

The standards for populating the fields of your Database Extract
file are as follows:
• Character fields can contain letters, numbers, or blanks. Negative Numbers

NSLDS does not handle
negative numbers. If the
• Numeric fields must contain numbers only. Blanks, alpha, or outstanding balance on a
other characters will cause errors. loan becomes negative (that
is, a credit balance), you
must report the balance as
• Date fields must contain 8 digits, be valid dates, and appear in
$1 and keep the status open
the format CCYYMMDD (for example, 19990131 for January until you can set the balance
31, 1999), where: to zero.
− CC = 2 digits for the century If you report the Amount of

Outstanding Principal
− YY = 2 digits for the year Balance as negative,
− MM = 2 digits for the month NSLDS will read it as a
− DD = 2 digits for the day positive value.
• A valid date is any acceptable calendar date. Invalid dates

would be dates such as February 30, February 29 of a non-leap
year, or September 31. The default value of 00000000 can be
used in certain specifically identified fields.
• NSLDS does not accept cents in amount fields. Dollar and

cents amounts should be rounded to the nearest dollar.
Appendix B contains a complete account of the various codes you

will need to fill some fields in the Database Extract file.
6.5 Updating Identifier Data

After NSLDS has successfully loaded data from your school for
the first time, thus completing the Initial Population, processing
rules apply to any subsequent attempts to update or change the data
that were loaded. These rules are designed to maintain the integrity
of the data in NSLDS.
There are two sets of rules governing changes to data in NSLDS.

One governs changes to the fields that contain loan identifier data;
the other governs changes to the fields that contain non-identifier
data.
June 2007 Version 4

85
6.5.1 Loan and Student Identifiers

Loan identifiers are the values contained in positions 1–47 of
Detail or PPC records. They uniquely identify a loan,
distinguishing it from the millions of other loans stored in NSLDS.
Although loan identifiers appear on both Detail and PPC records,
you must use a Detail record to change them. Loan Identifiers
• Code for Original School
• Student’s Social Security
A particularly important subset of loan identifiers is made up of Number
student identifiers, which uniquely identify a student just as loan • Date of Student’s Birth
identifiers uniquely identify a loan. • Student’s First Name
• Type of Loan/Other Aid
Figure 6–1 lists the fields that constitute the loan identifier portion • Date of First
Disbursement
of a Detail record and which of them also serve as student
identifiers.
Field Position Type

Code for Original School 1–8 Loan Identifier
Student’s Social Security Number 9–17 Loan/Student Identifier
Student Identifiers
Date of Student’s Birth 18–25 Loan/Student Identifier • Student’s Social Security
Student’s First Name 26–37 Loan/Student Identifier Number
Type of Loan/Other Aid 38–39 Loan Identifier
• Date of Student’s Birth
• Student’s First Name
Date of First Disbursement 40–47 Loan Identifier
Figure 6–1, Loan and Student Identifiers
Section 9.4.1 presents an overview of how NSLDS goes about

matching the identifiers for newly submitted loan records against
student and loan information already in the NSLDS database. The
Identifier Match Criteria used in that process are described in detail
by the entry for the Student’s Social Security Number field in the
Data Dictionary (Appendix A).
Identifier Change Process

6.5.2 The Identifier Change Process Changing identifier
information without
submitting full sets of both
You must use the identifier change process to update loan original loan identifiers and
identifier data already loaded on NSLDS. Failure to follow this new loan identifiers can
process can create duplicate loan records that compromise the data create duplicate loan records
integrity of NSLDS and cause students to be denied Title IV aid to that compromise the data of
NSLDS and cause students
which they are entitled. to be denied Title IV aid to
which they are entitled.
Because the entire string of information contained in the identifier
fields is needed to singularly identify a loan, loan identifiers are
processed as a block. When you update one identifier, you must
June 2007 Version 4
86
reconfirm the values of the other identifiers. To this end, you must
supply a complete set of new identifiers.
To update identifiers, the Detail record must contain the identifier

values currently loaded on NSLDS in the original identifier fields
(positions 1–47). Then use the new identifier fields (positions 50–
96) on the same record to report changes. Whenever you update
one or more identifiers, you must fill in all the new identifier
fields, regardless of whether the values in them are new ones or
ones that you have been reporting all along.
The new loan identifier fields are:
• New Code for Original School

• New Student’s Social Security Number
New Loan Identifiers
• New Date of Student’s Birth • New Code for Original
• New Student’s First Name School
• New Type of Loan • New Student’s Social
• New Date of First Disbursement Security Number
• New Date of Student’s
Birth
Figure 6–2 gives an example of how to update identifier • New Student’s First
information on a loan that currently exists in the NSLDS database. Name
• New Type of Loan
Assume that the following loan information currently exists on • New Date of First
the NSLDS database: Disbursement
• Code for Original School = 00876500

• Student’s Social Security Number = 111223333
• Date of Student’s Birth = 19600508
• Student’s First Name = Robert
• Type of Loan/Other Aid = NU
• Date of First Disbursement = 19910903
Then you discover that the Type of Loan/Other Aid code is

incorrect. To update the erroneous identifier, submit the data
exactly as shown above in positions 1–47 of the record and, at
the same time, also report the following values in positions 50–
96 of the record:
• New Code for Original School = 00876500

• New Student’s Social Security Number = 111223333
• New Date of Student’s Birth = 19600508
• New Student’s First Name = Robert
• New Type of Loan/Other Aid = PU (only item changed)
• New Date of First Disbursement = 19910903
Note: Only the Type of Loan/Other Aid was changed. All other
values must be resubmitted as before.
Figure 6–2, How to Update Loan Identifier Data

June 2007 Version 4
87
6.5.3 Updating Identifiers on Multiple Records

Remember that all information on NSLDS, including identifier
information, must be updated at the loan level. This means that
your Database Extract file must contain a separate Detail record,
with full sets of old and new identifier data, for each loan record
whose identifiers you want to update. This is the case even if you
are making the same change—typically a change to student
identifiers—to a number of loans.
After you submit the updated information to NSLDS, review the

Load Process Error report to see that all the Detail records
containing the updates were loaded into NSLDS. If any records
erred out, correct and resubmit them with both the original loan
identifiers and new loan identifiers until they load successfully.
6.6 Updating Non-Identifier Data

The process for updating loan identifier data is described in
Section 6.5. A completely different set of rules applies when you
report new data in fields that are not part of the loan identifier.
To follow those rules, you must answer two questions:
1. Is the field you want to update one for which NSLDS keeps
history?
2. If NSLDS keeps history for the field, are you trying to update
the current value of the field or an earlier historical value? (See
Figure 6–7 for the list of fields for which history is kept.)
Depending on how you answer these two questions, you face three
possible scenarios:
1. History Is Not Kept for the Field—In this case, the new data
should be captured by your normal extract process and
included in your regular submission as part of the Detail record
for that loan. You do not have to do anything special to report
the new value to NSLDS. As long as the new value passes all
applicable edits, it will be loaded onto NSLDS.
2. History Is Kept for the Field, and You Are Updating the
Current Value for That Field—In this case, the new data
June 2007 Version 4

88
should be captured by your normal extract process and

included in your regular submission as part of the Detail record
for that loan. You do not have to do anything special to report
the new value to NSLDS. As long as the new value passes all
applicable edits, it will be loaded onto NSLDS.
3. History Is Kept for the Field, and You Are Trying to

Update a Historical Value for That Field—In this case,
create a PPC record to report the new data.
6.6.1 What NSLDS Does

How NSLDS Creates History
When NSLDS updates a field for which history is not kept, the
updated value becomes the current value and the old current value
is discarded by the system. When NSLDS updates a field for which
history is kept, the updated value becomes the current value and
the old current value becomes the historical value. As further
updates occur, each current value becomes, in turn, a historical
value, and all the historical values are stored, in order, as history
for that field.
Figure 6–3 and Figure 6–4 will help illustrate how history is
created as part of the update process.
In Figure 6–3, the NSLDS database contains a record for Loan X

that has been loaded into the database but never updated. Each data
element for the loan (A, B, C, and D) has the same value it did
when the loan was first loaded onto the database; those are the
current values A1, B1, C1, and D1.
The data provider then sends NSLDS a Submittal file that contains
updates to two of the fields for Loan X. Those updates are denoted
by B2 and D2. The updates pass all the relevant edits and are
loaded onto the database. Because history is kept for field D but is
not kept for field B, the following occurs:
• The current value of field B is updated to B2, and the old

current value B1 is discarded.
• The current value of field D is updated to D2, and the old

current value is stored in history as D1.
June 2007 Version 4

89
Submittal File Loan X A1 B2 C1 D2
Database Before Update

Loan X A1 B1 C1 D1 - Current Values
Database After Update D1 - History (Prior Event)
NSL - 1097
Figure 6–3, NSLDS Update (1 of 2)
In Figure 6–4, the data provider sends another Submittal file to

NSLDS. This time, the Submittal file contains updates to fields A,
C, and D. Those updates are denoted by A2, C2 and D3. The
updates pass all the relevant edits and are loaded onto the database.
Because history is kept for fields A and D but not for C, the
following occurs:
• The current value of field A is updated to A2, and the old

current value is stored in history as A1.
• The current value of field C is updated to C2, and the old

current value is discarded.
• The current value of field D is updated to D3, the old current

value is stored in history as D2 (which is also part of the prior
event), and the original current value is stored in history as D1.
D1 is now strictly history and can only be changed by a PPC

record.
June 2007 Version 4

90
Submittal File Loan X A2 B2 C2 D3
Database Before Update Loan X A1 B2 C1 D2 - Current Values
D1 - History (Prior Event)

Database After Update A1 D2 - History (Prior Event)
D1 - History
NSL - 1098
Figure 6–4, NSLDS Update (2 of 2)
Events
The following events can be updated by a PPC record:
• Cancellation
• Deferment
Events
• Disbursement Events are made up of keys
• Loan Status and associated values. Keys
• School Servicer and values are treated as if
they were linked because
they give each other
An event is made up of a key, usually a date, and one or more meaning. For example, a
associated values. The key and values are linked together because Date of Loan Status is not
they give each other meaning. For example, a Date of Loan Status meaningful without an
is not meaningful without an accompanying Code for Loan Status. accompanying Code for
Together they constitute a discrete event, Loan Status. Loan Status. Together they
describe a discrete Loan
Status event.
Events can be classified as

current, prior, or history.
June 2007 Version 4

91
Notice in Figure 6–3 and Figure 6–4 that the event immediately
preceding the event that created the current value in a field for
which history is kept is known as the prior event. It can be
updated either by a PPC record or by a Detail record, but only if
the purpose of the Detail record is to delete the current value for
the field and reinstate the value of the prior event as the current
value.
How NSLDS Updates Current Events
Figure 6–5 shows what happens when you attempt to update a

current event (key and values) using a Detail record.
Case When the Key (Usually Date) When Value(s) NSLDS Does This
1 Stays the same. Changes to new value. Updates the value associated with
the current event.
2 Changes to earlier date not before the date Stays the same. Updates the date associated with
of the prior event. the current event.
3 Changes to a later date. Stays the same. Updates the date associated with
the current event.
4 Changes to a date before the date of the Stays the same. Returns a date sequence error and
prior event. does not update the record.
5 Changes to an earlier date, but one still Changes to new value. Updates the date and value fields
after the date of the prior event. associated with the current event.
6 Changes to the same date as the prior Stays the same. Deletes the current event, and the
event stored on NSLDS. prior event becomes the current
event. Updates with value.
7 Changes to the same date as the prior Changes to a new value. Deletes the current event, and the
event stored on NSLDS. prior event becomes the current
event. Updates with values.
8 Changes date to default value (zeros), Changes to default value (zeros Deletes the current event.
where there is no previous event in history, for numeric field, blanks for
and the field being changed is not part of a character field).
loan.
9 Changes date to default value (zeros), and Changes to default value (zeros Returns a date sequence error and
there is a previous event in history. for numeric field, blanks for does not update the record.
character field).
10 Changes date to default value (zeros), Changes to default value (zeros Returns an error and does not
where there is no previous event in history, for numeric field, blanks for update the record. (Deletion of
and the record being changed is a loan or character field). last loan or student status is not
student status event. allowed.)
June 2007 Version 4

92
Case When the Key (Usually Date) When Value(s) NSLDS Does This
11 Changes to a later date. Changes to new value. Creates a new event on NSLDS,
which becomes the current value.
What had been the current event
now becomes prior event/history.
Figure 6–5, Updating a Current Event
Notice what happens if, as in Case 4, you attempt to change a

current key (date) so it is earlier than the key (date) of the prior
event. This illustrates one of the two things you must keep in mind
when updating events, whether you are updating their current
values or historical values:
1. You cannot change the chronological order of events stored in

history. That is, you cannot re-date an event (for example, the
event of which data element D2 in Figure 6–4 is part) so that it
predates an event that occurred before it (D1) or postdates an
event that occurred after it (D3).
2. You cannot re-date events so they overlap in time.
Cases 6 and 7 illustrate the prior event exception. Normally, a

historical event can only be modified by a PPC record. However,
because NSLDS wants to make it easy for you to undo your most
recent change to the database, it allows you to delete a current
event and update the values of what was the prior event using a
Detail record. Do this only when you want to delete the current
event and make the old prior event the current event. If, on the
other hand, you want to change some value of the prior event
without deleting the current event, you must use a PPC record.
How NSLDS Updates Historical Events
Figure 6–6 shows what happens when you attempt to update the
various parts of a historical event (keys and values) using a PPC
record.
June 2007 Version 4

93
Case When the Key When Value(s) NSLDS Does This

1 Stays the same. Provides defaults (zeros or Deletes event.
blanks, as per record layout
specifications).
2 Stays the same. Provides new value. Updates value if it passes
validation edits.
3 Changes to a new date within the Stays the same or changes to Updates date to new date, keeps
range of acceptable dates. default value(s). existing value(s).
4 Changes to a new date within the Provides new value(s). Updates date, and value if it
range of acceptable dates. passes other edits.
5 Changes to a new date not within Stays the same or changes to Change not accepted. Date
the range of acceptable dates. default value(s). Sequence Error is reported on
Load Process Error report.
6 Changes to a new date not within Provides new value(s). Change not accepted. Date
the range of acceptable dates. Sequence Error is reported on
Figure 6–6, Updating Historical Events
6.6.2 What You Do

Does NSLDS Keep History for the Field?
To update a loan record on NSLDS successfully, you must be able

to answer the two questions posed in Section 6.6:
1. Is the field one for which NSLDS keeps history?
2. If NSLDS does keep history for the field, are you trying to
update the current value for the field or a historical value?
To answer the first question, check Figure 6–7 or the History Kept
box for the field in the Data Dictionary (Appendix A).
June 2007 Version 4

94
Fields for Which History Is Kept Fields for Which History Is Not Kept
Amount of Cancellation Amount of Loan
Amount of Disbursement
Amount of Outstanding Principal Balance
Code for Current School Data Provider Identifier
Code for Enrollment Status Code for Original School
Code for Loan Status Date Enrollment Period Begins
Code for Servicer Date Enrollment Period Ends
Date Deferment Starts Date Entered Repayment
Date Deferment Stops Date Grant Overpayment Repaid
Date Enrollment Status Effective
Date of Cancellation Date of Student’s Birth
Date of Disbursement Interest Rate
Date of First Disbursement New Code for Original School
Date of Loan Status New Date of First Disbursement
Date of Outstanding Principal Balance
Date of Servicer Responsibility New Date of Student’s Birth
Indicator of Grant Overpayment New Type of Loan/Other Aid
New Student’s Social Security Number Student’s Academic Level
New Student’s First Name Student’s Last Name
Student’s First Name Student’s Middle Initial
Student’s Social Security Number Type of Loan/Other Aid
Student’s Social Security Number Indicator
Type of Cancellation
Type of Deferment
Figure 6–7, Fields and History
If history is not kept for the field you want to update, the update
should be caught by your normal extract process and submitted to
NSLDS on a Detail record without any special effort on your part.
As long as the update passes all edits, it will be loaded onto
NSLDS.
If, on the other hand, history is kept for the field you want to
update, you must know whether you are updating a current value
or a historical value.
June 2007 Version 4

95
Are You Updating a Current Value or a Historical Value?
Most of the updates you submit to NSLDS will be to current

values. This is as true for fields for which history is kept as it is for
fields for which history is not kept. So even if history is kept for
the field you want to update, you will normally be updating the
Changing History
current value for that field. If that is the case, the update should be When data are submitted to
caught by your normal extract process and submitted to NSLDS on NSLDS, the system first
a Detail record without any special effort on your part. processes Detail records,
then PPC records. For this
On the other hand, you will sometimes know you want to update a reason, if you want to
change historical information
historical value because you are aware that a mistake was made on a loan whose identifiers
when reporting on an event prior to the event that supplied the are also being modified at
current values for a field. the same time, the PPC
record must refer to the new
More often, you will discover that you want to update a historical identifiers, not the old ones.
value because of the following sequence:
1. You submit a change to a current value on a Detail record, but

it errs out of NSLDS.
2. When you check your Load Process Error report, you discover
that the change you submitted was valid, but that it conflicted
with some other value stored in history on NSLDS.
Depending on the nature of the change you want to make, you may
need to know more about the historical values already on NSLDS.
Past Period Events
PPC records update events stored in history on NSLDS. Events are

made up of two components:
• The key that identifies the event

• The associated values(s) that describe the event
Figure 6–8 lists the events you can update using PPC records.
June 2007 Version 4

96
Event Key Associated Value(s)

Cancellation Old Date of Cancellation New Date of Cancellation
New Type of Cancellation
New Amount of Cancellation
Deferment Old Date Deferment Starts New Date Deferment Starts
New Date Deferment Stops
New Type of Deferment
Disbursement Old Date of Disbursement New Date of Disbursement
Loan Status Old Date of Loan Status New Date of Loan Status
New Code for Loan Status
School Servicer Old Code for Servicer New Code for Servicer
New Date of Servicer
Responsibility
Figure 6–8, PPC Events, Keys, and Values
Creating Past Period Change Records
PPC records must contain the following elements:
• A complete set of loan identifiers
• The key that enables NSLDS to identify the event to be

updated
• Any new values with which you want to update the event
Only report the loan identifiers, the key, and any new values for
the event that you want to change. Use default values for fields that
you are not changing. There is no need to fill all the Old/New
fields as you would for changes to loan identifiers.
Old and New
For PPC record layouts and detailed instructions explaining how to When a PPC field name
apply specific updates to each PPC event, see Appendix C. starts with the word Old (for
example, Old Date of Loan
Status) you must report the
exact value already
Changing Event Dates contained in the field you are
changing. When the PPC
Except for the School Servicer event, all the PPC events you can field name says New (for
update have a date as their key. So updating an event key normally example, New Date of Loan
involves updating a date. Status), you report the new
value you want that data
element to contain.
There are two important things to remember when making date
changes with a PPC:
June 2007 Version 4

97
1. You may not change the chronological order of events

contained in history. Do not re-date an event so it predates one
that occurred before it or postdates one that occurred after it.
2. You may not change the date of an event so that it equals the
date of a pre-existing event. For example, if there is a loan
status effective date of 3/1/98, you cannot correct another loan
status effective date to 3/1/98.
To change a date that is the key to an event, send NSLDS a PPC

record containing the loan identifiers, the “Old” date that serves as
the key, and the “New” date with which you want to update
NSLDS.
To change a date that is an event value, send NSLDS a PPC record

containing the loan identifiers, the event key stored in NSLDS, and
the new date with which you want to update NSLDS.
Example
The following is an example of a valid change of key date in a

Loan Status event.
In this example, the Date of Loan Status (key) is changed from

April 1, 1994, to March 1, 1995. Notice that it was not necessary to
provide the Code for Loan Status (value) associated with the April
1, 1994, event because it did not change.
For simplicity, here and in the examples that follow, loan

identifiers are represented by Loan XYZ, when in fact they consist
of all the information contained in positions 1–47 of the loan
record.
Old Date of Loan New Date of Loan New Code for Loan
Loan Identifiers Status Status Status
Loan XYZ 19940401 19950301 BLANKS
Changing Event Values
To change the value(s) associated with an event, send NSLDS a

PPC record containing the loan identifiers, the event key stored in
NSLDS, and any new value(s).
June 2007 Version 4

98
Example
In this example, the Code for Loan Status associated with the April
1, 1994, Loan Status is changed to RP, so the New Code for Loan
Status will replace the former value for the event. Since the date of
the event is not changing, it is not necessary to provide a New Date
of Loan Status.
Loan XYZ 19940401 ZEROS RP
Changing Both Date and Value
To change both the key date of the event and the associated data,
send a PPC record containing the loan identifiers, the event key
(date) stored in NSLDS, the new key (date), and the new value.
Example 1
Assume the following values for a series of Deferment events exist

on the NSLDS database:
Start Stop Type

01/01/98 01/15/98 FP
02/01/98 02/15/98 FP
03/01/98 03/15/98 FP
04/01/98 04/15/98 FP
If you want to correct the 02/01/98 deferment to a starting date of

02/02/98 and the Type of Deferment from FP to FS, use the
following PPC:
Old Deferment New Deferment New Deferment New Deferment

Loan Identifiers Start Date Start Date End Date Type
Loan XYZ 19980201 19980202 00000000 FS
The New Deferment End Date contains the default value 00000000
because the value is not being changed.
June 2007 Version 4

99
Example 2
If you want to change the date of a Loan Status event from April 1,
1994, to March 1, 1995, and the Code for Loan Status to RP, use
the following PPC:
Loan XYZ 19940401 19950301 RP
Deleting Historical Data
To delete an event, submit a PPC record that contains the loan

identifiers and event key stored in NSLDS, along with default
values (given in the PPC record layouts in Appendix C) in all the
New fields.
Example
To delete a Loan Status event from history, use the following PPC
record:
Loan XYZ 19940401 ZEROS BLANKS
6.7 Copy Your Database Extract File to the

Extract Directory
When you have created a Database Extract file that meets the
standards outlined in this chapter, you must copy it to PC
DataPrep’s Extract folder (C:\DataPrep\Extract) and name it
extract.ff. Extract Validation will fail if PC DataPrep does not find
a file named extract.ff in the Extract folder.
June 2007 Version 4

100
Perkins Data Provider Instructions Extract Validation
Chapter 7: Extract Validation

Once you have created your Database Extract file and copied it to
the Extract folder (C:\DataPrep\Extract), you are ready to run
Extract Validation. This task is performed entirely by DataPrep.
7.1 What Happens in Extract Validation?

In the Extract Validation process, DataPrep first examines your
Database Extract file to make certain its format is acceptable.
DataPrep checks for proper header record(s), 300-byte record
lengths, and matching school code(s). These are called file-level
edits.
If the header format is not correct, DataPrep cannot continue the

process, and an error message appears informing you that there
was a header error and that processing was aborted.
The Extract Validation process will also abort if any Detail or PPC
record has a school code that does not match the school code on its
Domain-Level Errors
Header record. There are four kinds of
domain-level errors:
If your Database Extract file passes the file-level edits, DataPrep
performs domain-level edits by examining all Detail and PPC 1. Numeric Field Errors—
records in the file to ensure that each data element meets domain A character other than a
number is in a field
requirements. If the percentage of domain errors exceeds the requiring all numbers
threshold levels set by ED (see box), DataPrep will issue an error 2. Invalid Date Errors—
message informing you that you have exceeded the threshold and Date specified does not
that no Submittal file was created. All errors are noted in an exist on a calendar or is
Extract Error file from which you can generate an Extract Error not zeros
3. Missing Identifiers in
report. Use this report to correct your database or extract program. one or more loan
Then create a new Database Extract file and rerun Extract identifier fields
Validation. 4. Missing New Identifiers
on records with identifier
If your Database Extract file passes the file-level edits and the changes
percentage of domain errors is below the maximum threshold
levels established by NSLDS, DataPrep creates a Submittal file
that you then send to NSLDS.
June 2007 Version 4

101
The Extract Validation process produces three output files:
1. Extract Validation Log File—A file containing a log report

that summarizes the results of the Extract Validation process Successful Extract
and counts of records processed. Validation
For Extract Validation to
2. Extract Error File—A file from which you can generate a create a Submittal file, your
Database Extract file must
report listing all domain errors. It is created only if the
not contain any file-level
Database Extract file passes file-level edits. errors, and the percentages
of domain-level errors must
3. Submittal File—The file you transmit to NSLDS. It is created be below the threshold
only if the Database Extract file passes file-level edits and levels established by ED.
remains below ED-established thresholds for domain-level
errors.
D a ta b a s e E x tra c t F ile
(C o n ta in s H e a d e r, D e ta il, P a s t
P e rio d C h a n g e (P P C ) R e c o rd s )
U p d a te d a ta b a s e (s ).
R e ru n c yc le a s
n e e d e d to c o rre c t
file -le v e l e rro rs a n d
d o m a in -le v e l e rro rs
(if a b o v e th re s h h o ld )
E x tra c t V a lid a tio n P ro c e s s b e fo re c re a tin g a
n e w e xtra c t file .
V a lid a tio n S u b m itta l F ile E x tra c t

(C o n ta in s H e a d e r, D e ta il, P P C ,
Log a n d T ra ile r R e c o rd s )
E rro r F ile
E x tra c t E rro r
R e p o rt
Send
S u b m itta l F ile
to N S L D S
NSLDS
Figure 7–1, Extract Validation Process
June 2007 Version 4

102
7.2 DataPrep Error Path

DataPrep performs two sets of edits during the Extract Validation
process:
1. File-level edits
2. Domain-level edits
File-Level Edits

Extract Aborted
1. Incorrect Header Correct database
Validation 2. School Code does and/or extract process
Process not match Header and rerun Extract
Domain-Level Edits Validation
Threshold Failure
1. Numeric Field Error Correct database
2. Invalid Date and/or extract process
3. Missing Identifier and rerun Extract
4. Missing New Identifier Validation
NSL-1111
Figure 7–2, DataPrep Edit Process
June 2007 Version 4

103
7.2.1 File-Level Edits

File-level edits check whether the Database Extract file is a
legitimate file with the correct header, 300-byte records, and a
school code in each record that matches the code in the header. If
DataPrep detects any one of these file-level errors, the Extract
Validation process aborts and an error message, with a description
of the error, appears on screen. If this happens, you must correct
your database and/or extract process and create a new Database
Extract file. You would then rerun Extract Validation. See
Appendix B–10 (PC users) or B–11 (z/OS LE users) for a
complete list of all the file-level and header errors that cause the
Extract Validation process to abort.
7.2.2 Domain-Level Edits

Domain-level edits check for four kinds of errors:
• Numeric Field Errors—A character other than a number in a

field requiring all numbers
Domain Error Rates
DataPrep validates the
• Invalid Date Errors—A date that does not exist on a calendar entire record and can detect
and is not all zeros multiple domain-level errors
on a single input record. The
error rates are calculated by
• Missing Identifiers in one or more loan identifier fields DataPrep based on the
number of records with one
• Missing New Identifiers on records with identifier changes or more errors, not on the
total number of errors
detected.
If the percentage of the records with these errors exceeds the
threshold levels established by ED, DataPrep will not create a
Submittal file. You must then correct your database or extract
process, create a new Database Extract file, and rerun Extract
Validation.
June 2007 Version 4

104
7.3 Running Extract Validation on a PC

Before you can run Extract Validation, you must perform the
following tasks:
• Install DataPrep and define the directory paths for DataPrep’s Naming the Extract File
data files (Section 5.1.1) Remember that your
Database Extract file must
• Create a Database Extract file named extract.ff and copy it to be named extract.ff in order
for DataPrep to locate and
the Extract folder (Chapter 5) process it.
• Copy the most recent TEF file to the Current folder.
For instructions on receiving the TEF file from NSLDS, see

Section 8.2. Once you have a current TEF file, use DataPrep’s File
Transfer utility (Section 5.2.3), Explorer, or My Computer to copy
it to your Current folder.
Once you have performed these tasks, you are ready to run Extract
Validation.
1. From the DataPrep Main Menu, click Extract Validation.
June 2007 Version 4

105
Figure 7–3, DataPrep Main Menu with Extract Validation

Selected
2. The Extract Validation dialog box appears.
File Date
Note that the date a file was
last modified or created
appears on the right side of
the Extract Validation dialog
box. This is to help you
make sure you are using the
right Database Extract file.
If you click on the plus sign

next to the file date, the File
Information Dialog Box
appears, showing the date
Figure 7–4, Extract Validation Dialog Box and time the file was last
modified and the number of
bytes in the file.
3. If you click any of the plus signs on the far right next to the file
date, the File Information dialog box appears. This box shows
the file name, the date and time the file was created or last
modified (whichever is more current), and the number of bytes
in the file.
June 2007 Version 4

106
4. Click Exit to return to the Extract Validation dialog box.
5. Click Run. Once Extract Validation begins, the Extract

Validation Process dialog box appears, showing you how much
While Extract Validation Is
of the process is complete. While Extract Validation is in in Progress
progress, you can close the Extract Validation dialog box and While Extract Validation is in
perform other DataPrep tasks. In addition, you can use other progress, you can use
software to perform tasks while Extract Validation runs. If you DataPrep or other software
decide to terminate Extract Validation before it is complete, to perform tasks. When
Extract Validation is done,
return to the Extract Validation dialog box and click Stop. the Extract Validation
Process dialog box will show
When processing is complete, the Extract Validation Process that 100 percent of the
dialog box shows a Processing Status of 100 percent and process was completed.
displays information about the Extract Validation process that
is repeated in the Extract Validation Log report (Section 7.3.2).
June 2007 Version 4

107
Halting Extract Validation

Once you have started to
run Extract Validation, you
cannot stop it from the
Extract Validation Process
dialog box.
If you want to stop the

before it has completed, you
must return to the Extract
Validation dialog box and
click Stop.
Figure 7–5, Extract Validation Process Dialog Box
Once you are satisfied that Extract Validation has run successfully,
click Close to return to the Extract Validation dialog box. Then
click Exit to return to the DataPrep Main Menu. From there you
have several options, including generating reports.
7.3.1 Output
The successful Extract Validation process produces three files:
1. Extract Validation Log File (extrlog.ff)

2. Extract Error File (extrerr.ff)
3. Submittal File (submit.ff)
7.3.2 Using the Extract Validation Log Report

Section 10.1 explains how to view and print the Extract Validation
Log report. This report repeats the information displayed by the
Extract Validation Process dialog box when Extract Validation is
complete. You must check this report to verify that the Submittal
June 2007 Version 4

108
file created by Extract Validation contains valid data that will load
onto the NSLDS database.
The Extract Validation Log report contains the following

information:
• Version and release numbers for DataPrep

• When Extract Validation began
• Whether Extract Validation was successful and what to do next
• Original School
• Extract Date
• Record counts for the Database Extract file
− Number of Detail records
− Number of PPC records
• Counts and percentages of domain-level errors
− Date/numeric errors
− Identifier errors
− New identifier errors
• Totals for open loans
− Number of open loans
− Amount of loan
− Amount of cancellation
− Outstanding principal balance
Original School is the school’s OPEID if the Database Extract file

contains only records for a single school. If the file contains
records from multiple schools, the number of schools reporting on
the file appears instead.
The record counts for the Database Extract file are useful when
you do reasonability checks. Look, in particular, for unusually
large changes in the number of Detail records from one submittal
to the next. Error Numbers
Remember that DataPrep
DataPrep totals the number of records that contain domain-level calculates the number of
errors and the percentage they represent of the records in the records containing errors if
there are multiple errors in a
Database Extract file. If you have exceeded the error threshold single record, not the total
levels defined by ED, DataPrep does not create a Submittal file. In number of errors (which
this case, you must correct your database and/or extract process, could be considerably
create a new Database Extract file, re-start the extract process, and higher).
re-validate until your error rate is below the threshold levels.
June 2007 Version 4

109
Extract Validation Is Successful
If your Database Extract file processes successfully, the Log states:
Your Database Extract file was processed successfully. Please

do a reasonability check comparing this Log with Logs from Checking Reasonability
prior runs. If the amounts and number of records extracted are The Extract Validation Log
reasonable, send the Submittal file to NSLDS. If not, review will tell you whether the
your Database Extract file, make the needed corrections, and was successful. If it was,
rerun Extract Validation. compare the Log with others
from prior Validations to
Compare this log to the logs for prior Validation Extracts to make make sure the number of
sure the numbers in the Submittal file DataPrep has just produced Detail records and totals for
open loans are reasonable.
are reasonable. In particular, look at the following:
Large increases in the
• Number of Detail records number of Detail records or
• Number of open loans numbers for open loans
could indicate that you have
• Amount of loan duplicated records or
• Amount of cancellation extracted some records
• Outstanding balance incorrectly.
Large, unexplained changes in any of these figures could indicate

that your Database Extract file contains flawed data, even though it
processed successfully.
Extract Validation Fails Because of File-Level Errors
If DataPrep detects a file-level error, it stops Extract Validation

and does not create a Submittal file. The Extract Validation Log
report announces that DataPrep has detected a file-level error and
terminated Extract Validation. It also describes the error and
suggests possible remedies.
June 2007 Version 4

110
Among the possible causes for a failed Extract Validation are the
following:
What to Do When Extract
• No Header record Validation Is Halted
• An incorrect format If Extract Validation failed
because a file-level error
• Data that shifted because you inserted a space or a character
caused the process to abort,
• Records were not the required 300-byte length verify that you have used the
• Mismatch between the Code for Original School in a Detail correct Database Extract file,
record and the school code in the Header record that it has a Header record,
is in the proper format, and
that the records are all 300
bytes in length.
June 2007 Version 4

111
Extract Validation Fails Because of Domain Errors
If the percentage of domain-level errors in your Database Extract

file exceeds the allowable threshold levels, the Log will state that
no Submittal file was created, will report the error rate, and will
explain the reason for the failure (excessive date/numeric, Domain Error Threshold
identifier, or new identifier errors). The Extract Validation Log Levels
will state: ED has set the threshold
levels for domain errors at:
The percentage of domain errors exceeds the allowable
tolerances. Therefore, no Submittal File has been created. You • Combined Date and
Numeric Field Errors 10%
can use the Loan Detail Error Report to help determine the • Missing Identifier 5%
cause. Please correct your database, create a new Database • Missing New Identifier 5%
Extract file, and rerun the Extract Validation process. Refer to
the Perkins DPI for help in identifying the possible cause of the These percentages are
problem. subject to change at ED’s
discretion.
When you receive this message, you must correct the domain-level
errors on your database so that the percentage of errors is
acceptable. Use the Extract Error report to see what corrections
must be made. But remember that the Database Extract file must
be an exact reflection of your database, so you should correct all
errors by updating your database, not by editing the Database
Extract file or any file created by DataPrep.
There are a number of possible reasons for domain-level errors.

Some of the following causes and corrections might explain yours:
• Your Data Is Stored Incorrectly on Your Database—The What to Do When Your

solution is to correct the appropriate fields on your database. Domain Errors Are in
For example, if your database accepts 6-digit dates, correct it Excess of the Threshold
so it stores the 8-digit dates required by NSLDS or make sure If the number of domain
errors (date/numeric field
your extract process converts 6-digit dates to 8 digits. errors, identifier errors, or
new Identifier errors) Extract
• Your Extract Process Calculates Fields Incorrectly— Validation finds in the Detail
Review and correct any programming logic in your extract and PPC records exceeds
process. For example, when you calculate Date Entered the threshold defined by ED,
it rejects the whole Database
Repayment by adding 1 day to the end of the enrollment Extract file.
period, make sure you are not producing invalid dates such as
February 29, 1999, rather than the valid March 1, 1999. The Extract Validation Log
report contains your error
rates. To learn more detail
• Your Extract Process Only Picks Up Changed Fields—
about what caused the
Change your process to populate the other fields with the errors, generate an Extract
current data for those fields. Error report.
June 2007 Version 4

112
TEF File Is Out of Date
If your TEF file is more than 90 days old, DataPrep will display a
message warning that the threshold error values it contains may be
out of date. However, DataPrep will perform Extract Validation
and create a Submittal file, assuming that your Database Extract
file meets the standards described in this manual.
June 2007 Version 4

113
7.4 Running Extract Validation on a z/OS

LE Version 3.1 or Higher Mainframe
The JCL for z/OS LE Version 3.1 or higher mainframes executes
Perkins DataPrep procedures that perform Extract Validation and
creates an error file. Appendix G contains the JCL for these
functions. It can be referenced from the library created with Previous Data Sets
JCLLIB as part of the name. The library member name is The first step in the JCL will
delete any data sets
PRBB1000. previously created. If you
want to save your previous
Submittal file, you must copy
it to another file name.
June 2007 Version 4

114
Perkins Data Provider Instructions Sending and Receiving Files
Chapter 8: Sending and Receiving

Files
8.1 Sending the Submittal File
You are required to transmit a current Submittal file to NSLDS
each month on the schedule assigned to you by ED. Because of the
number of data providers and the size of some Submittal files, it is
Meeting Your Scheduled
critical that you submit your data according to the schedule Submittal Date
established by NSLDS. Normally you will transmit files by SAIG; Schools and other data
but by special arrangement only you can send files by cartridge or providers have specific
tape. submittal windows within
which they must transmit
their Submittal files to
Make sure that the file you send meets the following standards: NSLDS. If you do not
transmit within your window,
• It is a Submittal file (named submit.ff), not a Database Extract your submittal will be
or some other file. rejected by NSLDS, and
you’ll receive a message
instructing you to submit a
• It was created no more than 14 days before your scheduled new Submittal file on your
load date. If you are not sure, use Windows Explorer or next scheduled date.
DataPrep’s File Transfer utility to check when the file was
created. ED keeps track of all missed
submissions as well as error
rates in determining an
institution’s ability to properly
8.1.1 Submittal Schedule manage Title IV student aid
programs.
NSLDS will assign a submittal schedule to you each year, usually
in December. You can check your schedule at any time by
selecting the Data Provider Schedule link on the Organization page
of the NSLDS Web site (www.nsldsfap.ed.gov).
Your Submittal file should arrive at NSLDS no later than 1 p.m.

Central time the day before it is scheduled for Load processing. Submittal Schedules on
The data it contains cannot have been extracted from your database the Web
You can check your
more than 14 days before your scheduled load date. Submittal files submittal schedule at any
received more than 15 days after your scheduled load date will not time on the Organization
be processed. The period from 14 days before your scheduled load page of the NSLDS Web site
date until 15 days after your scheduled load date is your submittal (www.nsldsfap.ed.gov).
window.
June 2007 Version 4

115
8.1.2 Submittal File Format

If you are reporting for a single campus, the Submittal file created
by DataPrep contains:
• Header Record
• Detail Records
• PPC Records (optional)
• Trailer Record
If you are reporting for multiple campuses, the Submittal file

contains records in the same sequence (Header, Detail, PPC,
Trailer) by campus. Each campus has its own Header and Trailer
record, and all the records for the first campus appear together,
followed by all the records for the second campus, and so on. The
sequence looks like this:
• Header record for Campus 1

• Detail records for Campus 1
• PPC records for Campus 1
• Trailer record for Campus 1
• Header record for Campus 2
• Detail records for Campus 2
• PPC records for Campus 2
• Trailer record for Campus 2
• Header record for Campus N
• Detail record for Campus N
• PPC records for Campus N
• Trailer record for Campus N
The Trailer record, which is created by DataPrep, marks the end of

the submittal and contains basic information about the number of
records processed and the number of records in error at each level
of validation.
June 2007 Version 4

116
8.1.3 Submitting by Student Aid Internet

Gateway
Once the DataPrep software has created the submittal file
(submit.ff), you are ready to transmit from the EDConnect
software using message class SHSLDSIN and searching for
C:\Dataprep\Current\submit.ff. Message Classes
Use this message class to
For full instructions on how to transmit a file using SAIG, see the send Submittal files to
EDConnect for Windows User’s Guide available on ED’s NSLDS:
Information for Financial Aid Professionals Web site • SHSLDSIN
(www.ifap.ed.gov).
NSLDS uses these message
classes to send files to you:
If some problem with DataPrep or NSLDS prevents you from • TEFFILOP—TEF File
transmitting your Submittal file successfully, contact the NSLDS • SLDERROP—Load
CSC at 800-999-8219. Process Error File
• SLNDTLOP—NSLDS
If your problem is with the EDConnect software or SAIG Loan Detail File
transmission lines, contact the CPS/WAN at 800-330-5947. • SHSNTFOP—Error
Submittal Summary
Notification File
June 2007 Version 4

117
8.2 Receiving Files

8.2.1 Receiving Files by Student Aid Internet
Gateway
NSLDS sends you files by SAIG using the following message
classes:
• Message Class SHSNTFOP—Error Submittal Summary

Notification File. NSLDS sends you this file if it fails to
receive your Submittal file, or the file you send contains file-
level errors that prevent NSLDS from processing it.
• Message Class SLDERROP—Load Process Error File.

NSLDS sends you this file within 48 hours after successfully
loading your Submittal file onto the database.
• Message Class SLNDTLOP—NSLDS Loan Detail File.

NSLDS sends you this file by special arrangement only.
Note: The Thresholds, Error Codes and Field Codes File (TEF) can
be downloaded into DataPrep from the FSA Web site located at
www.fsadownload.ed.gov. The file should be saved into the
DataPrep/Current directory with the file name TEF.ff. This file is
edited any time NSLDS includes or removes a new error code.
For full instructions on how to receive a file using EDConnect

Software and the SAIG, see the EDConnect for Windows User’s Help!
Guide available on ED’s Information for Financial Aid If you have problems with
Professionals Web site (www.ifap.ed.gov). DataPrep or NSLDS,
contact the NSLDS CSC at
If some problem with DataPrep or NSLDS prevents you from 800-999-8219.
receiving files from NSLDS, contact the NSLDS CSC at If you have problems with
800-999-8219. EDConnect or SAIG,
contact the CPS/WAN at
If your problem is with the EDConnect software or SAIG 800-330-5947.
transmission lines, contact the CPS/WAN at 800-330-5947.
June 2007 Version 4

118
Perkins Data Provider Instructions The NSLDS Load Process
Chapter 9: The NSLDS Load Process

The day before your Submittal file is scheduled for loading onto
NSLDS, NSLDS checks whether it has received your Submittal
file. If it has not, it sends you an Error Submittal Summary
Notification file reminding you that your submission is due and Submittal Window
that it will still be processed if it is received within your submittal Your submittal window runs
from 14 days before your
window. If NSLDS does not receive a Submittal file from you Submittal file is scheduled
within that window, it sends you another Error Submittal Summary for processing to 15 days
Notification file informing you that your Submittal file cannot be after. If NSLDS has not
processed that month and that you must send a new Submittal file received your Submittal file
the following month. by 1 p.m. Central Time the
day before the scheduled
load, it sends you an Error
Once it receives your Submittal file, NSLDS performs the Submittal Summary
following edits: Notification file. It sends
another if your submittal
window expires without a
• File-Level Edits Submittal file arriving. Your
• Domain-Level Edits Database Extract file cannot
• Record-Level Edits have been extracted more
• Load-Level Edits than 14 days before the
scheduled load date.
NSLDS performs file-level edits to determine whether there are
errors in the Submittal file that prevent it from being processed at
all. Such errors can include:
• Sending the wrong file

• Files that are incorrectly formatted
• Data that were corrupted during transmission to NSLDS
If your Submittal file contains file-level errors, NSLDS sends you

within 1 or 2 days an Error Submittal Summary Notification file,
which contains an error message (or messages) explaining why
NSLDS was unable to process your submittal. NSLDS then takes Check Your Mailbox Early
no further action, so it is up to you to create a successful Submittal It is important that you check
your SAIG mailbox a day or
file and send it to NSLDS within your processing window. two after transmitting your
Submittal file. If it encounters
After it verifies that your Submittal file does not contain any file- a problem reading the file or
level errors, NSLDS performs domain-level and record-level edits some other error that
on each record within the file. Domain-level edits check for prevents an update, NSLDS
will notify you through
records that contain non-numeric characters or spaces in a numeric message class SHSNTFOP
field, invalid dates (other than all zeros), missing identifiers, or that you must correct and
missing new identifiers. Record-level edits check for duplicate retransmit the Submittal file.
records and for records that violate reasonability rules or Perkins
program regulations. If NSLDS detects either a domain-level error
or a record-level error in a record, it writes the error to the Load
June 2007 Version 4

119
Process Error file but does not perform any further processing on
the record.
If records pass domain- and record-level edits, NSLDS performs

load-level edits that check for invalid codes, and for any date
sequence errors or identifier conflicts that would be caused by
loading those records onto the NSLDS database. Records that pass
the load-level edits are then loaded onto NSLDS and update the
database.
For more information about edits, see the Federal Perkins Data
Dictionary (Appendix A), which describes all the edits applied to
each field in a Perkins record, and Appendix B, which lists all the
error messages generated by DataPrep and the Load process.
File-Level Edits

Extract Aborted
1. Incorrect Header Check extract process
Validation 2. School Code does and rerun Extract
Process not match Header Validation
Domain-Level Edits
Threshold Failure
1. Numeric Field Error Check extract process
2. Invalid Date and rerun Extract
3. Missing Identifier Validation
4. Missing New Identifier
Domain and
Record-Level Edits
Record Rejected
NSLDS
1. Numeric Field Error Correct database and/or
Load 2. Invalid Date extract process for next
Process 3. Missing Identifier submittal
Load-Level Edits 4. Missing New Identifier
5. Reasonability Error
6. Duplicate Record
Record Not
Loaded/Updated
1. Date Sequence Error 1. PPC
2. Identifier Conflict 2. Resolve with other
data provider
3. Invalid Codes 3. Correct database/
NSLDS Updated extract process
NSL-1063
Figure 9–1, NSLDS Load Process
June 2007 Version 4

120
9.1 File-Level Edits

File-level edits check whether NSLDS has received a Submittal
file on schedule, and whether it will be able to process that file as a
whole. Among the errors NSLDS checks for are:
• File submittal date too early

• Submittal file not received
• File submittal date too late
• Invalid Header record
• No data in Submittal file
• Missing or invalid Trailer record
• Invalid OPEID
• Duplicate files
• Invalid date in Submittal Date field of Header record
• School Code in Detail record does not match code in Header
record Why Perform Domain-
Level Edits Twice?
If DataPrep has already
If your Submittal file fails any file-level edit, NSLDS will not performed domain-level
process the file and will, instead, send you an Error Submittal edits as part of Extract
Summary Notification file. Validation, why does NSLDS
perform them again as part
of the Load process?
DataPrep performs domain-
9.2 Domain-Level Edits level edits to determine
whether your Database
Domain-level edits check individual records for the following Extract file exceeds the
domain error thresholds
errors: established by ED. If it stays
below those thresholds,
• Non-numeric characters or spaces in a numeric field DataPrep creates a
• Invalid dates (other than all zeros) Submittal file, even though
some of the records in that
• Missing identifiers file contain domain-level
• Missing new identifiers errors. The Load Process,
on the other hand, performs
DataPrep applies the same domain-level edits to your Database domain-level edits to
Extract file as part of Extract Validation, but it does so only to determine whether the
individual records within the
calculate your domain-level error rate and to determine whether Submittal file meet NSLDS
that rate exceeds the threshold established by ED. As long as it standards and should be
stays below that threshold, DataPrep creates a Submittal file loaded onto the database.
(Section 7.2.2) even though some of the records in the file contain
domain-level errors.
June 2007 Version 4

121
The Load process, on the other hand, applies domain-level edits to

determine whether individual records within your Submittal file
should be loaded onto the database. If a record contains a domain-
level error, NSLDS writes it to the Load Process Error file but does
not process it any further. This means that load-level edits are not
applied to records that have failed domain-level edits.
Records that pass domain- and record-level edits are then edited
for load-level errors before being loaded onto the database.
9.3 Record-Level Edits

Record-level edits check the Submittal file as a whole for duplicate
records and then each individual record for reasonability errors. If
a record contains a record-level error, NSLDS writes it to the Load
Process Error file but does not process it any further. This means
that load-level edits are not applied to records that have failed
record-level edits.
Records that pass domain- and record-level edits are then edited
for load-level errors before being loaded onto the database.
9.3.1 Duplicates
NSLDS sorts the records in the Submittal file and compares
sequential rows to determine if the first 47 bytes of the record—the Duplicate Records
If two Detail records have
loan identifiers—match. If any two Detail records have the same the same loan identifiers,
loan identifiers, it rejects both records as duplicate records. If you both records will be rejected
have populated the Data Provider Loan ID field for each record, since NSLDS has no way of
you will be able to determine which record should be reported determining which record is
under those identifiers for the next submission. No record will pass correct. You will have to
resubmit the record in a later
this duplicate edit process if another record on the same submission. Duplicate loan
submission has the same loan identifiers. Neither duplicate record records will have an Error
will update the database since NSLDS has no way of knowing Code of 1423 (Identifiers
which loan record is correct. must be unique on each
detail record) on Field Code
225 (Date of First
Disbursement).
9.3.2 Reasonability Edits
Reasonability edits check that data are contained in proper fields
according to specific edit criteria. Such edits include checking that
required fields have been filled, such as the Date Entered
Repayment field or a Cancellation Amount on a loan that has a
Cancellation type.
June 2007 Version 4

122
Reasonability edits also check all date and amount fields on each
record to ensure that the data they contain are both reasonable and
in compliance with Perkins program regulations. For example, if a
loan is reported as a PU loan (Perkins Loan) with a Date of First
Disbursement of 19820115 (January 15, 1982), it will be rejected
since Perkins loans did not exist in 1982. Reasonability edits
ensure data integrity within individual records.
9.4 Load-Level Edits

NSLDS only applies load-level edits to records that have already
passed domain- and record-level edits. Records that fail domain-
or record-level edits are written to the Load Process Error file but
not processed further by NSLDS. This means that you cannot
assume that records that failed domain- or record-level edits would
otherwise have passed load-level edits and been loaded onto the
database.
Records that pass both domain- and record-level edits, but fail
load-level edits, are written to the Load Process Error file.
Records that pass domain-, record-, and load-level edits are loaded
onto NSLDS and update the database.
9.4.1 Identifier Edits

NSLDS reviews the student and loan identifiers in the records you
submit against those of records on the database. If the Student’s
SSN in an individual record does not match an SSN on NSLDS,
either current or in history, the student is considered a new student.
If the record then passes all the remaining edits, NSLDS creates a
new student and assigns a new loan to that student on the basis of
the data you submitted.
If the Student’s SSN on a record you submitted matches an SSN on

the NSLDS database, NSLDS uses Identifier Match Criteria to
match the loan identifiers on the record to the identifiers for a loan
currently on the system. If it matches an existing Perkins loan
record on four criteria—Student’s SSN, Original School, Loan
Type, and Date of First Disbursement—the record you submitted is
considered an attempted update. If all other edits are successful,
the record updates the NSLDS database.
June 2007 Version 4

123
If a record you submitted does not match on the loan identifiers

(Original School, Loan Type, and Date of First Disbursement), but
does match on the Student’s SSN, NSLDS uses Identifier Match
Criteria to match the student identifiers on the record to the
Correcting Student
identifiers for a student currently on the system. If a match is made Identifier Conflicts
and successive edits are passed, NSLDS creates a new loan record Submitting records that
for the existing student on the basis of the data you submitted. match an existing record on
Student’s SSN but not on
If the record you submitted does match a current Student’s SSN the other student identifiers
(Date of Student’s Birth and
but a student match cannot be made based on the Identifier Match Student’s First Name)
Criteria, NSLDS rejects the record. If that occurs, you must resolve causes an identifier conflict.
the identifier conflict by contacting the NSLDS Customer Care To correct this error, you
Center at 800-999-8219 or by e-mail to nslds@pearson.com. must resolve the conflict with
the data provider whose
data conflicts with yours.
If you submit a record that causes a student identifier conflict,
NSLDS writes a record to the Load Process Error file. The error
record contains the following information from your Submittal file:
• Student’s SSN you supplied

• Date of Student’s Birth you supplied
• Student’s First Name you supplied
In addition, the error record contains the following information for

the student record that conflicts with yours:
• Error Code
• Data Provider Code
• Data Provider Name
• Existing Student’s SSN
• Existing Date of Student’s Birth
• Existing Student’s First Name
• Existing Student’s Last Name
• Data Provider City
• Data Provider State
This information will help you resolve the conflict with the data
provider for the record already on NSLDS.
For a more detailed discussion of the Identifier Match Criteria for

student matches, see the discussion of the Student’s Social Security
field (positions 9–17 in the Detail record) in the Federal Perkins
Data Dictionary.
June 2007 Version 4

124
9.4.2 OPEID Edits

NSLDS reviews original and current school codes in the records
you submit against the most current ED data. If the OPEID code
on a record does not exist in the NSLDS database, NSLDS rejects
the record and does not update the database.
9.4.3 Validate Codes

NSLDS reviews all code fields to ensure that the codes they
contain are acceptable to NSLDS. See Appendix B for complete
lists of the following codes:
Correcting Invalid Codes
• Loan Type NSLDS rejects records
• Loan Status submitted with invalid codes.
• Enrollment Status To correct code errors, you
must correct either your
• Deferment Type
database or your extract
• Deferment Type Usage process.
• Cancellation Type
• Perkins Commercial Servicer
9.4.4 Date Sequence Edits

In addition to storing the current values for the individual fields
that make up a loan record, NSLDS also stores historical (or past)
values for selected fields. Often, those historical values are stored
as part of an event. This is because changes to some fields are only Correcting Date Sequence
meaningful if they are accompanied by a change to another field or Errors
fields. For example, a new Date of Loan Status is only meaningful Records you submit that do
not conform to date
if it is accompanied by a new Code for Loan Status. Together they sequence logic will not
constitute a Loan Status event. While you can update historical update NSLDS. To correct
values, you cannot change either current or historical values so the records already on
that you change the chronological order of events stored in NSLDS that cause these
history. errors, you may need to
submit a PPC record
(Section 6.6).
Therefore, NSLDS reviews records you submit against current and
historical values already stored on NSLDS for the same record to
ensure that any date changes do not alter the sequence of events. If
they do, NSLDS writes the record to the Load Process Error file
and does not update the database with it.
June 2007 Version 4

125
If a record you submit is rejected by NSLDS because it causes a

date sequence error, first check that the data you have submitted
are correct. If they are, you must submit a PPC record to update the
historical data already on NSLDS that are making your record
cause a date sequence error.
For a more detailed discussion of how NSLDS stores history and

how to update historical data using PPC records, see Section 6.6.
June 2007 Version 4

126
Perkins Data Provider Instructions Generating Reports on Windows-Based PCs
Chapter 10: Generating Reports on

Windows-Based PCs
From Extract Validation onward, the NSLDS update process
creates a series of data files that you can use to generate reports.
These reports will help you verify the contents of your database
and of your submissions to NSLDS. If necessary, they will help
you fix problems with your database or extract procedures, a topic
discussed in detail in Chapter 11.
Using files produced by either the Extract Validation process or

NSLDS, DataPrep can generate the following reports:
• Extract Validation Log Report—This report is generated

from the Extract Validation Log report created by Extract
Validation. It is identical in contents to the text displayed by
the Extract Validation Process dialog box after Extract
Validation is complete.
• Extract Error Report—This report is generated from the

Extract Error file created by Extract Validation and is available
in either summary or detail format.
• Load Process Error Report—This report is generated from

the Load Process Error file returned to you by NSLDS after it
has processed your Submittal file. It is available in either
summary or detail format.
• Extract Loan Detail Report—This report is generated from

the Extract Loan Detail file created by Extract Validation.
• NSLDS Loan Detail Report—This report is generated from

the Loan Detail file NSLDS can send you, by special
arrangement, to identify and resolve error conditions within
your database. Call the NSLDS Customer Service Center at
800-999-8219 to request a reconciliation file.
• Error Submittal Summary Notification Report—This report

is generated from the Error Submittal Summary Notification
file that NSLDS sends you when your Submittal file is not
received on schedule by the NSLDS Data Center or fails to
load onto the database.
June 2007 Version 4

127
DataPrep for PCs offers advanced users a particularly rich set of

selection and sort options for detail Error reports and Loan Detail
reports. These options are discussed at the end of this chapter.
10.1 The Extract Validation Log Report

The information that appears in the Extract Validation Process
dialog box after Extract Validation is complete (Figure 7–5) is also
written to the Extract Validation Log file, where it is available to
you for further examination or storage. From this file, you can
Extract Validation Log
view or print a report that provides a useful overview of Extract The Extract Validation Log
Validation. For a detailed discussion of the report’s contents, see file created by DataPrep
Section 7.3.2. includes the following
information:
To view or print the Extract Validation Log report, follow these
steps: • The number of domain-
level errors detected
1. From the DataPrep Main Menu, click Log Report. • Whether rejection
thresholds have been
exceeded
• The number of records
in the Database Extract
file
The log report can help you

identify problems in your
system or database.
Figure 10–1, DataPrep Main Menu with Log Report Selected
2. The Log Report dialog box appears.
June 2007 Version 4

128
Figure 10–2, Log Reports Dialog Box
3. Select the log file in your Current folder (C:\DataPrep\

Current\extrlog.ff), and click View. DataPrep displays the log
in your default viewer.
Viewers
When you installed
DataPrep, it automatically
selected its own built-in
viewer as the default for
viewing and printing reports.
For instructions on how to
change your default viewer,
or how to change your
viewer for an individual
report without changing the
default, see Section 5.2.2.
Figure 10–3, Extract Validation Log Report
June 2007 Version 4

129
If you want to print the report, you can do so directly from the
viewer, or you can return to the Log Report dialog box and click
Print.
10.2 Error Reports

The NSLDS update process includes two error reports:
• The Extract Error report identifies records that erred out of

Extract Validation. It is generated from the Extract Error file
Transferring the Load
produced by Extract Validation, and it will help you identify Process Error File from
and correct errors in your Database Extract file. Tape
If the Load Process Error file
• The Load Process Error report identifies records that erred is sent to you on tape, you
must develop your own
out of the NSLDS Load process. It is generated from the Load internal procedures for
Process Error file NSLDS sends you after it has loaded your transferring it to your PC.
Submittal file onto the database, and it will help you identify Then DataPrep can move or
and correct errors in your Submittal file. copy it to the Current
directory for generating the
Both reports will help you to identify and correct errors in your
database and in your extract process.
You can generate either error report in a summary or detail format.

Both summary and detail reports can be sorted by preprogrammed
sort parameters, and you can create your own additional sort
parameters for detail reports. In addition, you can use selection
criteria to limit which records are included in the detail error
reports. DataPrep includes a set of preprogrammed selection
criteria for detail reports, but you can also create your own,
including variable criteria that you assign a value each time you
run the report.
10.2.1 Error Files

DataPrep can only generate error reports from error files located in
your Current or Backup folders. This does not present a problem in
the case of the Extract Error file, which DataPrep automatically Retrieving the Load
Process Error and TEF
creates and places in your Current folder whenever a Database Files
Extract files passes the file-level edits performed by Extract We strongly suggest that
Validation. you retrieve both files a day
or two after your Submittal
However, before you can generate a Load Process Error report, file is loaded into NSLDS.
Both files are sent at the
you must use DataPrep’s File Transfer utility (Section 5.2.3) to same time. This will ensure
transfer two files to your Current folder: you have the latest error
codes and messages when
June 2007 you generate your LoadVersion 4
Process Error report.
130
• The Load Process Error File

• The TEF File
NSLDS will send you the Load Process Error file within 48 hours
after your Submittal file is processed. The file will be sent via
SAIG. The format of this file has not changed from DataPrep,
Version 1, except to add your unique Data Provider Loan ID to the
record. The SAIG message class for the Load Process Error file is
SLDERROP.
10.2.2 Generating Summary Error Reports

To generate a summary error report, the following files must be in
your Current folder (Section 10.2.1).
For the Summary Extract Error report:
• The Extract Error file created by DataPrep

• The latest TEF file sent to you by NSLDS
For the Summary Load Process Error report:
• The Load Process Error file sent to you by NSLDS

• The latest TEF file available at www.fsadownload.ed.gov
Once these files are in your Current directory, follow these steps to
generate a summary error report:
1. From the DataPrep Main Menu, click Error Report.
June 2007 Version 4

131
Figure 10–4, DataPrep Main Menu with Error Report Selected
2. The Error Report dialog box appears.
Extract Error Report or

Load Process Error Report
The Error Report dialog box
allows you to generate either
an Extract Error report from
your Validated Database
Extract file or a Load
Process Error report from
Figure 10–5, Error Report Dialog Box the Load Process Error file
NSLDS sends you after
processing your Submittal
3. Select Extract Validation or Load Processing as the Error
file. Be sure to specify the
Source. correct Error Source for the
report you request.
4. Select Summary as the Report Type.
June 2007 Version 4

132
5. Highlight the error file from which you want to generate a

report (here C:\DataPrep\Current\extrerr.ff).
If you double-click on a file listed in the Error Files list, a File

Information message box appears showing you the date and
time the file was created or last modified and the number of
bytes in the file.
If you do, click Exit to return to the Error Report dialog box.
6. Select a Sort Sequence (Section 10.6). If you select No Sort,

the report is sorted in the same order as the error file from
which it is generated.
7. When you are satisfied with the options you have selected on
the Error Report dialog box, click Generate. A status message
appears informing you the report has been generated.
Viewers
Remember that DataPrep’s
built-in viewer (ut0a.exe)
produces a correctly
formatted report, while the
other viewers may not. If you
use one of the other viewers
Figure 10–6, Generate Summary Error Rpt Dialog Box to view or print a report, you
may have to adjust the font
8. Click View. If you chose the options depicted in Figure 10–5, and size to fit on a page or
you should see a report that looks something like this when print your report using
viewed in DataPrep’s built-in viewer: landscape rather than
portrait format.
June 2007 Version 4

133
10.2.3 Generating Detail Error Reports

To generate a detail error report, the following files must be in
your Current folder.
For the Detail Extract Error Report:
• The Extract Error file created by DataPrep

For the Detail Load Process Error Report:
• The Load Process Error file sent to you by NSLDS

Once these files are in your Current directory, follow these steps to
generate a detail error report:
1. From the DataPrep Main Menu, click Error Report.
June 2007 Version 4

134
Figure 10–8, DataPrep Main Menu with Error Report Selected
2. The Error Report dialog box appears.
Extract Error Report or

Load Process Error Report
The Error Report dialog box
allows you to generate either
an Extract Error report from
your Validated Database
Extract file or a Load
Process Error report from
the Load Process Error file
NSLDS sends you after
processing your Submittal
file. Be sure to specify the
correct Error Source for the
report you want.
Figure 10–9, Error Report Dialog Box
3. Select Extract Validation or Load Processing as the Error

Source.
4. Select Detail as the Report Type.
June 2007 Version 4

135
5. Highlight the error file from which you want to generate a

report (here C:\DataPrep\Current\extrerr.ff).
If you double-click on a file listed in the Error Files list, a File

Information message dialog box appears showing you the date
and time the file was created or last modified and the number
of bytes in the file.
Click Exit to return to the Error Report dialog box.

the report will be sorted in the same order as the Extract Error
file or Load Process Error file from which it was generated.
7. Choose one or more Selection Criteria (Section 10.5).
If you choose a selection criteria containing one or more

variables, their current values will be shown in the Variables
list. You can click on a variable to bring up the Set Variable
Value dialog box. Change the variable value to the new required
value and click OK.
June 2007 Version 4

136
You should only run a single report using a selection criteria

option with variables at a time, since only one set of variable
values is stored for a given selection criteria option. In addition,
please remember that DataPrep only retains the latest version of
a selected report. Therefore, at any given time, only the report
that was run with the latest variable values will be available.
8. When you are satisfied with the options you have selected on
the Error Report dialog box, click Generate. A status message
appears informing you the report has been generated.
Viewers
Remember that DataPrep’s
built-in viewer (NSLDS-
V3/ut0a.exe) produces a
Figure 10–10, Generate Summary Error Rpt Dialog Box correctly formatted report,
while the other viewers may
not. If you use one of the
9. Click View. If you chose the options depicted in Figure 10–5, other viewers to view or print
you should see a report that looks something like this when a report, you may have to
viewed in DataPrep’s built-in viewer: adjust the font and size to fit
on a page or print your
report using landscape
rather than portrait format.
June 2007 Version 4

137
Figure 10–11, Detail Extract Error Report
Figure 10–12, Detail Load Process Error Report
June 2007 Version 4

138
10.3 Loan Detail Reports

Generating loan detail reports is not a routine step in the NSLDS
update process. However, loan detail reports are useful for
researching and resolving problems with individual loan records
that you have already identified from the Extract Error report or Do Not Change the
Load Process Error report. Database Extract File
If you view or review your
There are two loan detail reports: Database Extract file, be
certain you do not make any
changes to it. The Database
• The Extract Loan Detail report is generated from the Extract file must be a mirror
Database Extract file, and it allows you to review all or image of your database.
selected records in your file.
• The NSLDS Loan Detail report is generated from the Loan

Detail file that NSLDS can send you by special arrangement.
The Loan Detail file can take the form of a Reconciliation file
containing all the loans on NSLDS that you report on, or it can
include only loans that meet certain conditions. Like the
Extract Loan Detail report, the NSLDS Loan Detail report
allows you to view every field of each record it contains.
Comparing the contents of the NSLDS Loan Detail report to
the contents of your database will help you reconcile any
conflicts between your data and that on NSLDS.
10.3.1 Loan Detail Files

DataPrep looks for Extract Loan Detail files in these folders:
• Extract
• Backup Loan (or Current)
If you selected the default
DataPrep looks for NSLDS Loan Detail files in these folders: directory paths when you
installed DataPrep,
DataPrep looks for NSLDS
• Loan (or Current) Loan Detail files in the Loan
• Backup and Backup folders. If you
did not specify a directory
Unless you have transferred your Database Extract file out of your path for Loan Detail files,
DataPrep looks for them in
Extract folder, you will not have to transfer any files before the Current folder
creating the Extract Loan Detail file. (C:\DataPrep\Current). For
information about changing
However, when you receive the NSLDS Loan Detail file, you must default directories, see
load the file onto your computer or network and then use Section 5.2.1.
DataPrep’s File Transfer utility (Section 5.2.3) to move or copy the
file to your Loan (or Current) folder.
June 2007 Version 4

139
The File Transfer dialog box allows you to give version names to
NSLDS Loan Detail files. This is useful if you receive more than
one Loan Detail file in a single month. If you give a version name
to an NSLDS Loan Detail file, DataPrep will assign the file a name
of the form loandtlVersionname.ff, where:
loandtl is the constant name for Loan Detail files

Versionname is the version name you assign to the file
.ff is the constant for DataPrep files
Do not change such names; doing so will prevent DataPrep from

finding and processing the files.
10.3.2 Generating Loan Detail Reports

To generate a loan detail report, the following files must be in the
following folders:
For the Extract Loan Detail report:
• A Database Extract file in the Extract folder
For the NSLDS Loan Detail report:
• An NSLDS Loan Detail file in the Loan (or Current) folder
To generate a loan detail report, follow these steps:
1. From the DataPrep Main Menu, click Loan Detail Report.
June 2007 Version 4

140
Figure 10–13, DataPrep Main Menu with Loan Detail

Report Selected
2. The Loan Detail Report dialog box appears.
Figure 10–14, Loan Detail Report Dialog Box
3. Select Extract Loan Detail or NSLDS Loan Detail as the

Source option.
June 2007 Version 4

141
There are several ways to see the date and time a file in the
Detail Files list was last modified and the number of bytes in
the file. This can be useful if you have several Database Extract
or NSLDS Loan Detail files and are not sure which one you
want to view or print.
A. Use the horizontal scroll bar to scroll to the right on the

Detail Files list.
B. Double-click the file name, or select a file name in the

Detail Files list and then click the blue star to the right of
the file name in the Report File section. Either action
causes a File Information message to appear.
4. When you know which Database Extract or NSLDS Loan

Detail file you want to create an Extract Loan Detail report for,
select it in the Detail Files list of the Loan Detail Report dialog
box.
5. Choose a Selection Criteria (Section 10.5).
If you choose a selection criterion containing one or more

variables, their current values will be shown in the Variables
list. You can click on a variable to bring up the Set Variable
Value dialog box. Change the variable value to the new required
value and click OK.
June 2007 Version 4

142
You should only run a single report using a selection criteria

option with variables at a time, since only one set of variable
values is stored for a given selection criteria option. In addition,
please remember that DataPrep only retains the latest version of a
selected report. Therefore, at any given time, only the report that
was run with the latest variable values will be available.

the report will be sorted in the same order as the Database
Extract file or NSLDS Loan Detail file from which it was
generated.
7. Click Generate. DataPrep displays a message notifying you

that the report has been successfully generated.
8. Click View to view the Extract or NSLDS Loan Detail report

in your default viewer. Viewed in DataPrep’s built-in viewer, it
should look similar to or resemble Figure 10–15.
June 2007 Version 4

143
Figure 10–15, Extract Loan Detail Report
From the viewer, you can view or print the report as you please. To
change viewers for a specific report or to change your default
viewer, see the instructions in Section 5.2.2.
10.4 The Error Submittal Summary

Notification Report
10.4.1 The Error Submittal Summary Notification
File
If you fail to send NSLDS a Submittal file or send one that cannot
be processed, NSLDS will distribute a notification that your
Submittal file was not processed. This Notification file will be sent
via SAIG message class SHSNTFOP within 1 or 2 days from your
scheduled load date. If this occurs, you must make the necessary
corrections and resubmit as soon as possible. If the time frame
within which you are scheduled to submit your data has passed, the
submittal will be considered missed for the month. You must then
include the corrections and appropriate updates with your next
scheduled transmission.
Causes that can prompt NSLDS to send you an Error Submittal

Summary Notification file include:
June 2007 Version 4

144
• You sent some file other than a validated Submittal file, such
as your Database Extract file. (The Submittal file will be
labeled submit.ff, while the Database Extract file will be called
extract.ff.)
• You sent a file in an invalid format. For example, the file you
sent has no valid header, no 300-byte records, or no trailer
record.
• The file got corrupted during the SAIG transmission process.
• NSLDS did not receive your Submittal file during the time
frame in which NSLDS can load your data.
The Error Submittal Summary Notification file consists of a

Header record, one or more Detail records containing error
messages, and a Trailer record. See Appendix F for the complete
layout description.
The Detail record(s) will indicate why the Submittal file was
rejected and will give you a brief description of the problem
through a message code that can be found in Appendix F.
Appendix F also lists the actions you must take to correct the
error(s).
10.4.2 Generating the Error Submittal Summary

Notification Report
If NSLDS sends you an Error Submittal Summary Notification
file, use DataPrep’s File Transfer utility (Section 5.2.3) to import
the file into your Current folder. The SAIG message class for the
Error Submittal Summary Notification file is SHSNTFOP.
To generate the Error Submittal Summary Notification report,

follow these steps:
1. On the Report menu of the DataPrep Main Menu, click

Notification. The Notification Report dialog box appears.
June 2007 Version 4

145
Figure 10–16, Notification Report Dialog Box
2. Select the Error Submittal Summary Notification file

(C:\DataPrep\Current\shsntfop.ff) and click Generate. The
Generate Notification Rpt dialog box displays a Status message
telling you the Error Submittal Summary Notification report
has been generated.
3. To view the report, click View. Your default viewer displays

the report.
June 2007 Version 4

146
Figure 10–17, Error Submittal Summary Notification Report
10.5 Selection Criteria

DataPrep gives you the option of generating detail error reports
and loan detail reports using different selection criteria. Several
selection options have been preprogrammed:
• Data Fields in Error

• Identifier Fields in Error
• New Identifier Fields in Error
• No SSN Conflict Records
• Only SSN Conflict Records
• Selected Code for Original School
• Selected Error Code
• Selected Error and Field Code
• Selected Field Code
DataPrep allows you to create new selection criteria, and to change

or delete existing selection criteria.
To update selection criteria from the DataPrep Main Menu, begin

by clicking Selection Criteria on the Options drop-down menu.
June 2007 Version 4

147
Figure 10–18, DataPrep Main Menu with Selection Criteria

Selected on the Options Menu
The Selection Criteria dialog box displays.
Figure 10–19, Selection Criteria Dialog Box
From this dialog box you can Add, Edit, or Delete any selection
criterion for the following detail reports:
• Extract Error Report

• Load Process Error Report
• Loan Detail Report
June 2007 Version 4

148
Select Error Detail Records or Loan Detail Records as the Record

Type to add, edit, or delete selection criteria for that report type.
See Section 10.5.5 for a description of the Selection Criteria

Comparison Syntax.
10.5.1 Adding Selection Criteria

To create new selection criteria, follow these steps:
1. From the Selection Criteria dialog box (Figure 10–19), click

Add. The Selection Criteria Edit dialog box appears.
Figure 10–20, Selection Criteria Edit Dialog Box

Use of Spaces
2. Enter up to 10 characters that name the selection criteria in the Do not insert any spaces
Sel Key box. The Sel Key generally includes the field name; after position numbers. If
for example, if you want to select for all loans with an in you do, the program will
repayment status, you could use “LoanStatRP” as the Sel Key. assume the selection
criterion you have specified
has ended. If you want to
3. Enter up to 35 characters that describe the selection criteria in add any comments (for
the Description box, for example, “Loan Status in Repayment.” example additional
If you select the Available for selection option, this description description) you can put
appears in a drop-down list on the Error Report or Loan Detail comments after a space.
dialog box when you go to run a report.
4. Enter the codes that specify which records are to be included in

the report:
June 2007 Version 4

149
• Field Position (Refer to Appendix A for field positions)

• Comparison Operator (for example, less than, equal to,
greater than)
• Comparison Value
5. Click OK.
One Criterion
To add a selection criterion for all loans with loan status in

repayment, enter these values:
Sel Key LoanStatRP

Description Loan Status in Repayment
Comparison 119–120,EQ,RP
Note: Loan Status is position 119–120.
Two Criteria
To add selection criteria for all loans with loan status in repayment
and a date of first disbursement after January 1, 1998, enter these
values:
Sel Key RP-Jan1998

Description Loan in RP and Disbursement>= Jan 1998
Comparison (119–120,EQ,RP,&,40–47,GE,‘19980101’)
June 2007 Version 4

150
Notes: 119–120 is the Loan Status position, 40–47 is the Date of

First Disbursement position, an ampersand (&) is the AND
connector, and GE is greater than or equal to. You must surround
the comparison with parentheses when including an ampersand (&)
sign.
10.5.2 Editing Selection Criteria

To edit an existing selection criterion, follow these steps:
1. From the Selection Criteria dialog box (Figure 10–19), choose

the selection criterion you want to change and click Edit. The
Selection Criteria Edit dialog box appears populated by the
criterion you selected.
June 2007 Version 4

151
2. Edit the criterion values as necessary and click OK to return to

the Selection Criteria dialog box.
10.5.3 Deleting Selection Criteria

To delete a selection criterion, choose it on the Selection Criteria
Dialog box (Figure 10–19) and click Delete.
10.5.4 Adding Variable Selection Criteria

Perhaps you want to create an Error report that selects all loans
equal to a given value. But rather than establishing that value in
advance, you want to set it each time you run the report. You need
a report with a variable selection criterion. Adding a Variable
Criterion
To create one, start from the Selection Criteria Edit dialog box To create a report with a
criterion that varies each
(Figure 10–20) and follow these steps: time you run the report, fill in
the upper portion of the
1. Fill in the fields of the Selection Criteria Edit dialog box as Selection Criteria Edit dialog
described in Section 10.5.1. box. Then click Add to
access the Selection
Variable Edit dialog box. Fill
2. Click Add. The Selection Variable Edit dialog box appears. in its fields to define the
variable criterion.
June 2007 Version 4

152
Figure 10–24, Selection Variable Edit Dialog Box
3. Enter a name of up to 10 characters in the Name field.
4. Enter the length of the data element to which the selection

variable is to be compared in the Length field.
5. Enter up to 35 characters that describe the variable in the

Description field.
6. Enter the initial value of the selection variable in the Value

field. The initial value must be a valid value for that field, for
example ‘RP’ for the Loan Status field (positions 119–120).
7. Click OK to return to the Selection Criteria Edit dialog box.
One Variable Criterion
First, enter the following values in the Selection Criteria Edit

dialog box:
Sel Key SelLoanSt

Description Selected Loan Status
Comparison 119–120,EQ,*LoanStat
Notes: Position 119–120 is the Loan Status field, EQ is equal to,

and * indicates that the following is the name of the variable you
will set when you select the specific report (for example, RP or
FB).
June 2007 Version 4

153
To add the variable, click Add to bring up the Selection Variable

Edit dialog box. Enter the following values:
Name LoanStat
Length 2
Description Loan Status Code
Value ‘RP’
Figure 10–26, Selection Variable Edit Dialog Box
For more information about adding, editing, and creating your own
selection criteria, refer to the Help for the Selection Criteria and
Selection Criteria Edit dialog boxes and to the discussion of
Comparison Syntax that follows.
June 2007 Version 4

154
10.5.5 Selection Criteria Comparisons Syntax

Comparisons
Comparisons are made up of one or more comparison parameters linked using the AND
connector within commas (,&,) or the OR connector within commas (,|,), and grouped using
parentheses ().
Square brackets ([]) indicate optional items.
[(]comparison1[)][[,connector2,[(]comparison2[)]]…[,connectorN,[(]comparisonN[)]]][)]
[comments]
( ) pairs Balanced pairs of parentheses that enclose comparison parameters in order to

clarify or to alter the order in which the comparisons are done.
Without parentheses, the comparisons ‘A,|,B,&,C,|,D’ would be

interpreted as ‘((A,|,B),&,C),|,D’, but you will need to use parentheses if
the intent is either ‘(A,|,B),&,(C,|,D)’ or ‘A,|,(B,&,C),|,D’ or
‘A,|,((B,&,C),|,D)’.
comparison1 First comparison parameter.
connector2 Second compare parameter connector. (optional)
Use ampersand (&) for the AND connector, and use bar (|) for the OR
connector.
comparison2 Second comparison parameter (optional)
connectorN Nth compare parameter connector. (optional)
connector.
comparisonN Nth comparison parameter. (optional)
comments Comments. (optional)
At least 1 space between last compare parameter and start of comments.
Comparison Parameters
A comparison parameter is made up of one or more compare parameters linked using the AND
connector within commas (,&,) or the OR connector within commas (,|,).
June 2007 Version 4

155
compare1[[,connector2,compare2]…[,connectorN,compareN]]
compare1 First compare parameter
connector2 Second compare parameter connector (optional)
Use ampersand (&) for the AND condition, and use bar (|) for the OR
condition.
compare2 Second compare parameter (optional)
connectorN Nth compare parameter connector (optional)
connector.
compareN Nth compare parameter (optional)
Compare Parameters
A compare parameter is made up of a record character position, a compare condition, and a

compare value linked by commas (,).
compare => start[-end|:length|:1],condition,string|position|*variable
start Data Element starting position.
A number from 1 to 640.
end Data Element ending position (optional).
A number from starting position to 640.
length Data Element length (optional).
A number from 1 to 1 + 300 - starting position. Defaults to a length of 1

when neither the ending position nor the length is given.
condition The code identifying the compare condition.
One of the following 2-character compare conditions—not case sensitive:
June 2007 Version 4

156
EQ = Equal to
NE = Not Equal to
GT = Greater than
GE = Greater than or Equal to
LT = Less than
LE = Less than or Equal to
string The character string that is to be compared with the Data Element.
A string of characters whose length is equal to that of the Data Element.
If a string’s first character is a number, an asterisk (*), pound sign (#), or

its last character is a space, then the string must be enclosed in single
quotation marks (‘string’).
When a quoted string is less than the length of the Data Element, the string
is padded out to the correct length using the last character in the string.
{You can use ‘ ’ to check for spaces and ‘0’ to check for zeros.}
When a pound sign (#) prefixes a quoted string that is less than the length
of the data element, the string is shifted to the right and padded with
zeroes. {You could use #’500’ to check for the number 000500 in a 6-
character field or for the number 00000500 in an 8-character field.}
If you want to include a single quote (‘) in the comparison string, then you
will need to enter two single quotes (“).
position The starting position of a second Data Element within the record that is to be
compared with the first Data Element.
A number from 1 to 1 + 300 - length of Data Element.
variable The variable name that is replaced with a value at report generation time.
The variable name must be prefixed with an asterisk (*) and defined in the
Variable Name list.
Examples
105-110,gt,‘0’ Amount of Loan is greater than zero.
(58-66,NE,‘ ’,&,58-66,NE,4) New SSN is not spaces, and it is not equal to current SSN.
9-17,eq,*ssn Student SSN is equal to the variable value.
June 2007 Version 4

157
10.6 Sort Options

Summary Error reports can be sorted by count, error code, or field
code. Detail Error reports, however, can be sorted by any sort
parameter you select. Sorting allows you to focus on specific types
of errors or to distribute sections. DataPrep has provided the Sorting Reports
following pre-programmed sort parameters: Summary Error reports can
be sorted by count, error
code, or field code. Detail
• Data Provider Loan Identifier reports can be sorted by any
• Error Code parameters you choose.
• Field Code DataPrep has provided
preprogrammed sort
• Student Name (Last, First) parameters.
• Student Social Security Number
When you sort by count
For the Detail report, you can also select No Sort, which means the (summary reports only), the
records in the report will be listed in the same order as they were in report is organized in
descending order, so the
the Database Extract file from which the report was generated. field with the largest number
of errors appears first.
DataPrep allows you to create new sort options, and to change or
delete existing sort options. If you select No Sort (detail
report only), the report will
be sorted in the same order
To update sort options from the DataPrep Main Menu, begin by as the file from which it was
clicking Sort Parameters on the Options menu. created.
Figure 10–27, DataPrep Main Menu with Sort Parameters

Selected on Options Menu
June 2007 Version 4

158
The Sort Parameters dialog box appears.
Figure 10–28, Sort Parameters Dialog Box
From this dialog box you can add, edit, or delete any sort option
for the following reports:
• Detail Extract Error Report

• Load Process Error Report
• Loan Detail Report
Select Error Detail Records or Loan Detail Records as the Record

Type to add, edit, or delete sort options for that report type.
See Section 10.6.4 for a description of the Sort Parameter

Positions’ Syntax.
10.6.1 Adding a Sort Option

To create a new sort option, follow these steps:
1. From the Sort Parameters dialog box (Figure 10–28), click

Add. The Sort Parameter Edit dialog box appears.
June 2007 Version 4

159
Figure 10–29, Sort Parameter Edit Dialog Box
2. Enter up to 10 characters that name the report in the Sort Key

box. The Sort Key generally includes the field name, for
example “Field Code.”
Use of Spaces
3. Enter up to 35 characters that describe the sort sequence in the Do not insert any spaces
Description box. If you select the Available for selection after position numbers. If
option, this description appears in the drop-down list on the you do, the program will
assume the sort parameter
Error Report or Loan Detail Report dialog box when you go to
you have specified has
run a report. ended. If you want to add
any comments (for example
4. Enter up to 60 characters that define the positions in the record additional description), you
by which the report will sort in the Positions box. Use commas can put comments after a
space.
between fields. Refer to the Federal Perkins Data Dictionary
(Appendix A) for a complete account of data fields and the
positions they occupy.
5. Click OK.
For example, if you want a report that sorts by Loan Type and
Social Security number, follow these steps:
1. Enter Type-SSN in the Sort Key box of the Sort Parameter Edit Available for Selection
dialog box. Option
Check the Available for
Selection box if you want the
2. Enter Loan Type & SSN in the Description box. new Sort Parameter to be
listed in the Sort Sequence
3. Enter 38–39,9–17 in the Positions box. drop-down list on the Error
Report dialog box.
June 2007 Version 4

160
4. Click OK. The Sort Parameters Dialog Box displays with the
new sort parameter that you have just created.
Figure 10–31, Sort Parameters Dialog Box
This sort parameter will now be listed as a sort sequence option on

the Error Report or Loan Detail dialog box.
June 2007 Version 4

161
10.6.2 Editing a Sort Option

To edit an existing sort option, follow these steps:
1. From the Sort Parameters dialog box (Figure 10–28), select the
sort option you want to edit and click Edit. The Sort Parameter
Edit dialog box appears populated by the sort option you
selected (in this case, the Type-SSN sort created in Section
10.6.1).
2. Edit the sort values as necessary and click OK to return to the

Sort Parameters dialog box.
10.6.3 Deleting a Sort Option

To delete a sort option, select it on the Sort Parameters dialog box
(Figure 10–28) and click Delete.
10.6.4 Sort Parameter Positions’ Syntax

Note: Parameters in brackets [ ] are optional.
Positions are made up of one or more position parameters linked

together with commas (,).
positions => position1[[,position2]…[,positionN]] [comments]
position1 First data element position parameter

position2 Second data element position parameter (optional)
positionN Nth data element position parameter (optional)
comments Comments (optional) {At least one space between last
position parameter and start of comments.}
June 2007 Version 4

162
A position parameter is made up of a data element’s starting

position, and optionally its ending position or length.
position => start[-end|:length|:1]
start Data element starting position {A number from 1 to 300.}

end Data element ending position (optional) {A number from
starting position to 300.}
length Data element length (optional) {A number from 1 to 1+
300 – starting position. Defaults to a length of one when
neither the ending position nor length is given.}
Example: 39-73,21-32 Sort by 35-byte field starting in position

39, then by 12-byte field starting in position 21.
June 2007 Version 4

163
Perkins Data Provider Instructions Generating Reports on z/OS LE Mainframes
Chapter 11: Generating Reports on

z/OS LE Version 3.1 or Higher
Mainframes
11.1 Extract Error Report
The JCL for z/OS LE Version 3.1 or higher executes DataPrep
procedures that perform Extract Validation and generate the
Extract Error report (Appendix G).
You have the following options for generating the Extract Error
report:
• To generate both the summary and detail report, leave the

Extract Validation JCL as it appears in Appendix G.
• To generate the detail report, remove the asterisk (*) from the
line immediately before this line in the JCL shown on page
G–13.
PSTEP100 EXEC PGM=UTB300PB
To generate the summary report as well as the detail report,

comment out (that is, add an asterisk after the double slashes)
on the line before this line in the JCL shown on page G–13:
PSTEP100 EXEC PGM=UTB300PB
• To prevent DataPrep from generating any report, remove the

asterisk from the line immediately before this line in the JCL
shown on page G–11:
PSTEP070 EXEC PGM=TIRIOVFI

Main Frame Users:
Extract Report Sorting
11.1.1 Summary Report Sorting The Summary Extract Error
Report for mainframes can
be sorted by count, error
The sort JCL offers three options for sorting the Summary Extract code, and field code.
Error report: However, the Detail Extract
Error Report for mainframes
• By Error Count is only sorted by Social
Security number.
• By Error Code
• By Field Code
June 2007 Version 4

164
Error count is the default, which is why the other two options are
commented out by the addition of an asterisk (*) after the two
slashes at the beginning of the lines on which they appear.
//*
//* ERROR COUNT ORDER
// SET SORTPARM=PUTB4001
//*
//* FIELD CODE ORDER
//* SET SORTPARM=PUTB4002
//*
//* ERROR CODE ORDER
//*
If you want to change this default, you must add an asterisk (*)
after the two slashes in the JCL line for the error count option
// SET SORTPARM=PUTB4001
and delete the asterisk in the JCL line for the sort option you want
to use.
For field code order, remove the asterisk from this line:
For error code order, remove the asterisk from this line:
Whenever you change sort options, remember to select an option

by removing the asterisk from that line of JCL and to deselect the
other options by adding asterisks after the double slashes at the
beginning of those lines of JCL.
11.1.2 Detail Report Sorting

The Detail Extract Error report is automatically sorted by SSN
within school. This is the only sorting option available for the
Detail report.
If do not want to automatically produce a Detail Extract Error

Report, you must change the JCL (see Appendix G).
June 2007 Version 4

165
11.2 Load Process Error Report

Appendix G contains the JCL used to generate the Load Process
Error report from the Load Process Error file that you retrieve from
NSLDS after each submittal. This JCL also generates the Extract Data Sets Deleted
Error Report. The first step in the JCL will
delete any data sets
This JCL can be found in the library created with JCLLIB as part previously created. If you
of the name. The library member name is PRBB2000. want to save your previous
error files, you should
rename them.
As with the Extract Error report, you can sort the Summary Load
Process Error report in three different ways by changing the SET
statement:
• By Error Count
• By Error Code Sorting the Summary Error
Report
• By Field Code You can sort the Summary
Error report in any of three
See the in-stream documentation in Appendix G. Note that the ways: error count, error
Detail Load Process Error report can be sorted only by SSN. code, or field code. To select
a sort option, use the SET
statement.
June 2007 Version 4

166
Perkins Data Provider Instructions Using Reports
Chapter 12: Using Reports

12.1 Extract Validation Log Report
The Extract Validation Log report is discussed in detail in Section
7.3.2 as part of the Extract Validation process. Use it to verify that
a successful Extract Validation has, in fact, produced a Submittal
file that passes reasonability checks when compared to previous
months’ Submittal files.
12.2 Error Reports

12.2.1 Summary Error Reports
Both the Summary Extract Error report and the Summary Load
Process report list the following information for each field on your
Submittal file containing one or more errors:
Using Summary Error
• The number of errors that occurred for that field Reports
You can use summary error
• The percentage those errors represent of the total number of reports to focus quickly on
errors in the file the types of errors your
• The field code Submittal file contains.
• The error code
If a large portion of your
• The field name errors come from the DOB
• The error message field, for example, that will
show up in the summary
There is one significant difference between the two summary error error reports. You can then
reports. The Summary Extract Error report summarizes all the generate detail error reports
to show individual records
domain-level errors in your Submittal file, while the Summary that need to be corrected.
Load Process Error report summarizes all the domain-, record-,
and load-level errors in your Submittal file. Thus, the Summary
Load Process Error report offers a fuller picture of the types of
errors that occur in your Submittal file. However, the Summary
Extract Error report identifies domain-level errors earlier in the
NSLDS update process, and it is invaluable if you need to lower
your rate of domain-level errors beneath the ED-established
threshold in order to create a Submittal file at all.
Use the summary error reports to help you quickly spot problem
areas in your Database Extract file. Then use detail error reports to
research how those problems affect individual loan records. Once
you have diagnosed problems in this fashion, you should be able to
attack them at the source by updating your database or extract
procedures.
June 2007 Version 4

167
Figure 12–2, Summary Load Process Error Report
June 2007 Version 4

168
12.2.2 Detail Error Reports

Both the Detail Extract Error report and the Detail Load Process
Error report supply the following information for each error in
your Submittal file:
View the Summary
• Student’s SSN Reports First
• Date of Student’s Birth We suggest that you
• Student’s Last Name generate and view summary
error reports before viewing
• Student’s First Name
detail reports. The summary
• Type of Loan reports will quantify the
• Date of Loan types of errors in your
• Loan Status Database Extract file,
making it easy for you to
• School Code spot large problems.
• Data Provider Loan Identifier
• Error Level
• Name of Field in Error
• Value of Field in Error
• Error Message
In addition, the Detail Load Process Error report provides the

following information for each SSN conflict caused by a record on
your Submittal file:
• Student’s SSN you supplied

• Date of Student’s Birth you supplied
• Student’s First Name you supplied
• Error Code
• Error Message
• Existing Student’s SSN
• Existing Date of Student’s Birth
• Existing Student’s First Name
• Existing Student’s Last Name
• Data Provider Code
• Data Provider Name
• Data Provider City
• Data Provider State
There is one significant difference between the two detail error

reports. The Detail Extract Error report contains all the domain-
level errors in your Submittal file, while the Detail Load Process
Error report contains all the domain-, record-, and load-level errors
in your Submittal file. Thus, the Detail Load Process Error report
offers a fuller picture of the types of errors that occur in your
June 2007 Version 4

169
Submittal file. However, the Detail Extract Error report identifies

domain-level errors earlier in the NSLDS update process, and it is
invaluable if you need to lower your rate of domain-level errors
beneath the ED-established threshold in order to create a Submittal
file at all.
Use detail error reports to research how problems in your database

or extract procedure affect individual loan records. DataPrep’s
range of selection and sort options (Section 10.5 and Section 10.6)
will help you zero in on how general types of problems affect
specific loan records. Once you have diagnosed problems in this
fashion, you should be able to update your database or extract
procedures.
It is essential that you correct your database or extract procedures

rather than editing or otherwise massaging the Database Extract
file. If you do not, the errors will remain in your database and
reappear in your next Database Extract file, which will then be out Correct Your Database
of sync with the correct data loaded onto NSLDS as a result of Use error reports to correct
your previous submittal. your database or extract
procedures, not the
Database Extract file itself.
Appendix B contains a detailed list of all error messages, a cross-
Editing your Database
reference to the fields to which they refer, and the error message Extract file to correct errors
associated with each edit applied against a data element. You can violates ED policy, which
also refer to the Field Code and use Appendix A to review the requires your Database
requirements for reporting on the specific field. Extract file to be an exact
image of your database, and
perpetuates errors, since
any errors that remain on
your database get reported
to NSLDS again the next
month.
June 2007 Version 4

170
Figure 12–3, Sample Detail Extract Error Report
Figure 12–4, Sample Detail Load Process Error Report
12.3 Loan Detail Reports

Both the Extract Loan Detail report and the NSLDS Loan Detail
report list in a readable format the value for every field of every
record they contain. In the case of the Extract Loan Detail report,
June 2007 Version 4

171
the records are those contained in your own database. In the case
of the NSLDS Loan Detail report, the records are contained in the
NSLDS database. Together, the two reports are useful for
researching discrepancies between the data on your database and
the data on the NSLDS database.
While error reports are useful for identifying types of errors and
specific records with errors in your database, loan detail reports are
useful for establishing the full contents of those records that
contain errors. DataPrep’s select and sort options will help you
identify and categorize the records that appear in loan detail
reports.
June 2007 Version 4

172
12.4 Error Submittal Summary Notification

Report
The Error Submittal Summary Notification report informs you that
NSLDS has not received your Submittal file, or that it cannot
process the Submittal file it did receive because of some file-level
error. Since Extract Validation will not create a Submittal file at all
if it detects any file-level errors in your Database Extract file, most
file-level errors that can be remedied by correcting your database
or extract process will be caught by Extract Validation and will
never appear on an Error Submittal Summary Notification report.
The file-level errors that cause NSLDS to send you an Error

Submittal Summary Notification file usually result from one of the
following:
• Some problem with your submittal schedule

• Transmitting the wrong file or wrong Submittal file to NSLDS
• Data corruption while the file was being transmitted
The remedies to these types of errors usually involve meeting your

submittal schedule, modifying your file-handling procedures, or
simply retransmitting your Submittal file. They do not normally
involve correcting your database or extract procedures.
12.5 Error Types

12.5.1 File-Level Errors
File-level errors that result from faulty data in your database or
flawed extract procedures should be caught by Extract Validation
and prevent DataPrep from creating a Submittal file. Such errors
will cause Extract Validation to generate an error message that
identifies what went wrong and suggests how you might be able to
correct it. You must remedy such errors and rerun Extract
Validation in order to create a Submittal file.
File-level errors that prevent NSLDS from processing your

Submittal file are normally the result of faulty file handling or data
corruption during transmission. Often, these problems can be
resolved by re-sending your Submittal file or by sending the
correct Submittal file to NSLDS.
June 2007 Version 4

173
12.5.2 Domain-Level Errors

There are four types of domain-level errors:
1. Numeric Field Errors

2. Invalid Date Errors
3. Missing Identifiers
4. Missing New Identifiers
DataPrep checks for domain-level errors as part of Extract

Validation, and NSLDS checks for them again as part of the Load
Process.
Domain Error Threshold
If the rate of domain-level errors in your Database Extract file Levels
ED has set the threshold
exceeds the threshold established by ED, DataPrep will not create levels for domain errors at:
a Submittal file. However, it will create an Extract Error file that
you can use to generate Extract Error reports and correct your • Combined Date and
database before creating a new Database Extract file and re- Numeric Field Errors 10%
running Extract Validation. Even if your error rates are below the • Missing Identifier 5%
thresholds, you can still generate Extract Error reports and get a • Missing New Identifier 5%
head start on correcting any domain-level errors Extract Validation
does identify in your Submittal file.
While Extract Validation will process records with domain-level

errors as long as your error rate remains below the threshold, the
Load Process will not load such records onto NSLDS. Instead, it
will write them to the Load Process Error report, which you should
use to correct your database or extract procedure.
Numeric Field Errors
A numeric field error occurs when a field requiring all numeric

characters is populated by some other character or space. This type
of domain error can indicate extraction of the wrong data, an
incorrect result in a calculated field, truncated data, incorrect field
length, or some other type of data problem. The Extract Error
report will identify the data that erred, and you can use either the
Summary Report or the Detail Report to identify the data in your
system needing correction or to trace it back to the source of the
corruption. You can also use the Extract Loan Detail report to
review the entire record.
June 2007 Version 4

174
Invalid Date Errors
An invalid date error occurs when an invalid date appears in a field

requiring a date. This can be caused by an incorrect character in
the date field (for example, a non-numeric character) or a date that
is not a calendar date (for example, 19980230—February 30th is
not a valid date).
An invalid date error will not occur if the date is valid, regardless
of whether or not it is reasonable. For example, a student date of
birth of 19980228 will pass this domain-level edit, although clearly
1998 is not a reasonable birth date for a current student. That
record-level error will be picked up later when NSLDS processes
your Submittal file.
You should note that a date field with all zeros will pass the
domain edit, but it may err in the load process if a date is required.
Missing Identifiers
Identifier errors occur when one or more loan or student identifier

fields are left unpopulated. Examples of identifier errors are Loan
Type with spaces or Date of Student’s Birth with zeros. These
create a loan record with an invalid format. Identifier errors often
occur either when there are data missing from your database or
when your extract process is not working properly. It is essential
you review the cause of this error so it does not continue to occur.
Missing New Identifiers
New Identifier errors occur when one or more of the loan or

student new identifiers are populated by valid data, but the
remaining new identifiers are not. This occurs if you try to perform
an Identifier change but fail to fill in all of the New Identifiers.
New identifier errors indicate an identifier change process that is
not occurring properly, so it is essential you review the cause of
the error.
June 2007 Version 4

175
12.5.3 Record-Level Errors

NSLDS first checks for record-level errors as part of the Load
process. Individual loan records that contain record-level errors are
not loaded onto the database and are, instead, written to the Load
Process Error report. You can then use that report to correct your
Correcting Record-Level
database or extract procedure before extracting the records again Errors
the following month. There are two types of
record-level errors: duplicate
There are two types of record-level errors: records and reasonability
errors.
1. Duplicate Records To correct them, you must
2. Reasonability Errors correct the data in your
database. When you next
extract the data using
DataPrep, the new Submittal
Duplicate Records
file should have the
corrected information. Once
If two Detail records in the same Submittal file have the same loan the data have passed the
identifiers, NSLDS rejects them both because it has no way of edits described in Chapter 8,
telling which is correct. Remedy problems with duplicate records NSLDS will load it onto the
by removing duplicates from your database or by checking your database.
extract process for any step that may be creating duplicate records
even though they do not exist in your database. The Loan identifier
that DataPrep allows you to assign to individual loans can help you
track duplicate records and identify their cause.
Reasonability Errors
Reasonability errors result from data that do not make logical

sense. To correct these errors you must correct the information in
your database. When you next run Extract Validation, the
Submittal file produced by DataPrep should contain the corrected
data. Once the data have passed the edits, NSLDS updates its
database to reflect the corrected, and reasonable, data.
The following are two examples of Reasonability Errors:
1. Loan Type equals PU (Federal Perkins Loan). Date of First

Disbursement submitted equals 19810120 (January 20,
1981)—This is not reasonable since the Perkins Loan Program
did not exist until 1987. (Date of First Disbursement must be at
least 19870101.) Therefore, you must correct your database to
reflect that either the loan type equals NU, National Direct
Student Loan (NDSL), or the date.
June 2007 Version 4

176
2. Date of First Disbursement equals 19950905. Date of Birth

submitted for student equals 19910713—A student cannot
have received a Perkins loan and be only 4 years old. Correct
the information in your database as needed. (Date of birth must
be at least 12 years before Date of First Disbursement.)
Reasonability errors usually require that you make changes to the

respective field(s) in your database before your next extract.
For example, the Load Process Error report might contain a

record with the typographical error 20960125 (January 25,
2096) in the Date of Disbursement field instead of the correct
19960125 (January 25, 1996). NSLDS would reject this date as
being in the future. In your next Submittal file, you must
resubmit the record that contained the error with a valid Date
of Disbursement.
However, they can also require changes to your extract process.
For example, you might extract a record with a valid

Cancellation Date but a Cancellation Amount of zeros, even
though the correct Cancellation Amount is in your database.
Although the Cancellation Date is valid, it will err out of
NSLDS because the record that contains it fails the companion
field edit on Cancellation Amount. To fix this error, you must
change your extract process so it extracts Cancellation Amount
along with Cancellation Date.
12.5.4 Load-Level Errors

Load-level errors occur when records in your Submittal file
contain data that conflict with the data already in NSLDS. When
there is a load-level error, the entire record is rejected. NSLDS
checks for load-level errors during the Load process and writes
records that contain them to the Load Process Error report.
To correct load-level errors, you must correct the information in

your database before you create your next Submittal file.
Normally, you must resubmit corrected data in Detail records.
However, if you need to change historical (rather than current data)
in NSLDS, you must re-submit corrected data in a PPC record.
June 2007 Version 4

177
There are four types of load-level errors:
1. Identifier Conflicts
2. OPEID Code Errors
3. Invalid Code Errors
4. Date Sequence Errors
Identifier Conflicts
Identifier conflicts occur when a new loan record is submitted for a

Student’s SSN already on the NSLDS database, but a student
match cannot be made based on the Identifier Match Criteria
(Section 9.4.1). This kind of error can be caused by a number of
factors: typos, a student reporting two different first names to two
different data providers, (for example, a student who uses a middle
name as a first name), two different students mistakenly using the
same SSN, or even fraud. Regardless of the reason for the conflict,
you must resolve the conflict for the record to load successfully
onto NSLDS.
Loan records erring due to identifier conflicts should be compared

with the data the record erred against in the load process. The Load
Process Error report will show the conflicting identifiers and the
data provider that supplied them. You should check to see what the
conflict is and if it results from something that should be corrected
on your database.
If it appears your data are accurate but they conflict with data from
another data provider anyway, you must resolve the conflict before
NSLDS can be updated. Call the NSLDS Customer Care Center at
800-999-8219 to negotiate identifier conflicts with other data
providers.
OPEID Errors
NSLDS reviews original and current school codes in the records

you submit against the most current ED data. If the OPEID code
on a record does not exist in the NSLDS database, NSLDS rejects
the record and does not update the database. OPEID codes can be
found at www.nsldsfap.ed.gov under the ORG tab by searching on
the school name.
June 2007 Version 4

178
Invalid Codes
NSLDS reviews all code fields to ensure that the codes they
contain are acceptable to NSLDS. See Appendix B for complete
lists of the following codes:
Correcting Invalid Codes
• Loan Type NSLDS rejects records
• Loan Status submitted with invalid
• Enrollment Status OPEID codes. To correct
• Deferment Type code errors, you must
correct either your database
• Deferment Type Usage or your extract process.
• Cancellation Type Correct OPEID codes
• Perkins Commercial Servicer can be found at
www.nsldsfap.ed.gov under
the ORG tab by searching
on the school name.
Date Sequence Edits
In addition to storing the current values for the individual fields

that make up a loan record, NSLDS also stores historical (or past)
values for selected fields. Often, those historical values are stored
as part of an event. This is because changes to some fields are only
meaningful if they are accompanied by a change to another field or Correcting Date Sequence
fields. For example, a new Date of Loan Status is only meaningful Errors
if it is accompanied by a new Code for Loan Status. Together they Records you submit that do
not conform to date
constitute a Loan Status event. While you can update historical
sequence logic will not
values, you cannot change either current or historical values so update NSLDS. To correct
that you change the chronological order of events stored in the records already on
history. NSLDS that cause these
errors, you may need to
submit a PPC record
Therefore, NSLDS reviews records you submit against current and
(Section 6.6).
historical values already stored on NSLDS for the same record to
ensure that any date changes do not alter the sequence of events. If
they do, NSLDS writes the record to the Load Process Error file
and does not update the database with it.
If a record you submit is rejected by NSLDS because it causes a

date sequence error, first check that the data you have submitted
are correct. If they are, you must submit a PPC record to update the
historical data already on NSLDS that are making your record
cause a date sequence error.
For more detailed discussions on how NSLDS stores history and

on how to update historical data using PPC records, see Section
6.6.
June 2007 Version 4

179
Perkins Data Provider Instructions Final Thoughts
Chapter 13: Final Thoughts

We hope this Data Provider Instructions manual has helped you
learn how DataPrep functions. We also hope its description of how
DataPrep interacts with NSLDS gives you a useful overview of the
entire NSLDS update process.
If you have any questions, use the full-featured Help system. The
Help system documents all DataPrep’s functions and includes
material not contained in this manual. It is your best source for
detailed information about specific DataPrep functions.
If you still have questions about using DataPrep or about the

NSLDS update process, please call the CSC at 800-999-8219
between the hours of 8 a.m. and 8 p.m. Eastern Time, weekdays
except Federal holidays.
In addition, if you have any suggestions about how this manual can
be improved, please call the CSC and let it know.
June 2007 Version 4

180

Description: Tags: 102307PerkinsDPIV4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Description: Tags: 102307PerkinsDPIV4

Uploaded by

Copyright:

Available Formats

U.S.

Chapter 1: Introduction ................................................................................................................1

Chapter 2: Data Provider Responsibilities ................................................................................10

Chapter 3: The Update Process ..................................................................................................13

Chapter 4: System Requirements...............................................................................................20

Chapter 5: Installation, Utilities, and Testing ...........................................................................25

June 2007 Version 4

5.3.3 Test Load Process Error Report................................................................................68

Chapter 6: The Database Extract File .......................................................................................80

Chapter 7: Extract Validation ..................................................................................................101

Chapter 8: Sending and Receiving Files ..................................................................................115

Chapter 9: The NSLDS Load Process......................................................................................119

June 2007 Version 4

9.4.1 Identifier Edits ........................................................................................................123

Chapter 10: Generating Reports on Windows-Based PCs ....................................................127

Chapter 12: Using Reports........................................................................................................167

June 2007 Version 4

Chapter 13: Final Thoughts......................................................................................................180

Appendix A: Federal Perkins Loans Data Dictionary

Appendix B: Federal Perkins Loan Program Code and Error Tables

Appendix C: Past Period Change Record Layout

Appendix D: Federal Perkins Loans Load Error File (Record Layouts)

Appendix E: Federal Perkins Loans TEF File Layout

Appendix F: Error Submittal Summary Notification File

Appendix G: DataPrep JCL for z/OS LE

Appendix H: Glossary of Terms

Appendix I: Technical Updates

June 2007 Version 4

June 2007 Version 4

June 2007 Version 4

Figure 10–25, Selection Criteria Edit Dialog Box...................................................................... 154

June 2007 Version 4

This icon indicates a definition or explanation that

This icon indicates a special note, suggestion, or

This icon indicates a warning of which you should

June 2007 Version 4

1.2 What Is NSLDS?

1. Improve the quality and accessibility of student aid data. National

NSLDS is a national database of recipients, enrollment, loan,

• The Federal Family Education Loan Program (FFELP)

• The Federal Direct Loan Program (FDLP)

• Federal Perkins loans (including National Direct Student

• Federal Pell Grants, Federal Supplemental Educational

• Overpayments from the Federal Pell Grants, FSEOGs, ACGs,

• Demographic and enrollment data on Title IV recipients

June 2007 Version 4

1.2.1 NSLDS Functions

1. Prescreening for Title IV Aid Eligibility—The NSLDS

2. Postscreening for Title IV Aid Eligibility—The NSLDS

3. Default Rate Calculations—Cohort default rates are

4. Monitoring of Guaranty Agencies and Lender Financial

5. Research Studies and Policy Development Support—

6. ED Budget Analysis and Development—Every year, ED

June 2007 Version 4

7. Audit and Program Review Planning—ED uses audits and

8. Assessment of FFELP Administration by Guaranty

9. Refund/Cancellation Support—When a student withdraws

10. Borrower Tracking—The Borrower Tracking function helps

11. Loan Transfer Tracking—Loan Transfer Tracking monitors

12. Enrollment Reporting Process—The Enrollment Reporting

June 2007 Version 4

13. Financial Aid Transcript—The Financial Aid Transcript

14. Credit Reform Act Support—The Credit Reform Act (CRA)