My Oracle Support Banner

Issues Following the National Student Clearinghouse (NSC) Reporting Requirements 2014 Update, Patch 18069321 (Doc ID 1916204.1)

Last updated on FEBRUARY 04, 2022

Applies to:

PeopleSoft Enterprise CS Student Records - Version 9 and later
Information in this document applies to any platform.
****Patch 19386299 is posted and is available for download from Patches and Fixes****


After the National Student Clearinghouse New Reporting Requirements for 2014, Patch 18069321 was posted (see <Document 1901314.1>), the Clearinghouse revised the reporting requirements. In addition, some issues were found with the patch. This patch addresses the following issues:

Updates to SQR code:
1) Invalid Header Code- The header code changed with the new layout from A2 to A3. This change was omitted from patch 18069321.

2) Use of T Alias Issue-In the SQR the alias T is used in multiple locations, which is causing an issue for a few customers.

3) Change from Free-Form Country Description to 2-Character Country Code- this change is due to report revisions provided by the Clearinghouse after
Patch 18069321.

4)No Program Detail Message and Summary Count Added-This fix will provide details in the log file for students who have no program details in the

5) Issue with overall enrollment status and program enrollment status when academic load calculates to other than No Units.

6) Reporting NO SSN - There is a recent change to reporting students who do not have a SSN.  In Campus Solutions, a student in the US must have a national id value that is the SSN.  If a valid value is not entered, the system assigns XXXXXXXXX as the SSN.  In the past we have just reported this value on the extract. With the new regulations, all students must be reported, even if they do not have an SSN.  So the SQR has been modified to report NO SSN for SSN field values of XXXXXXXXX.  A new warning message added to report the XXXXXXXXX SSN student as a warning, and a summary counter is added to the end of the report.  

Updates to COBOL code:
1) Enrollment Status for Program Details Using Default Load Determination-For customers who define academic load with a determiner of default, no
enrollment status is calculated for students.

2) Invalid Academic Programs in Program Detail Reporting- If a student has multiple programs in the program/plan stack, and one program has been
inactivated, the current logic does not recognize the inactivated status. If a valid ACAD_PROG_TBL value is not found for the ACAD_PROG, then the program
should bypass this row of data. A message will be written in the log that states this program as not considered because of the data integrity issue.

3) Add logic to Correctly Set Enrollment Change Date for Q Status- The enrollment Change Date for Q status is not being correctly calculated.

4) Change in ACAD_PROG/PLAN in the Same Program Career Number-The Primacy Number sort routine in the delivered logic causes the wrong program data to
be reported.

5) Program Career Number
If a student has multiple program/plan values on the program/plan stack and the NSC configuration is such that the student's data from only one program
can be reported, the sort logic needs to be revised to select the optimal program.

a) The sort logic on FA Primacy Number value will be modified to remove blank values. This will prevent data from programs with a blank FA Primacy
value from being reported over data from a program with a non-blank FA Primacy Number value.

b) The logic to select Program/Plan needs will be modified to remove inactive program values from the sort results.

c) The current logic will be updated to remove programs from the sort results that are not FA eligible.

d) Add additional logic to correct a flaw in the start date determination when the student has multiple rows of program/plan data with multiple status
changes over time.

6) Add Logic to Create No Program Details
Add logic to SRPCCONS to not report any program detail if a plan (major) does not have a CIP code and the Program Indicator Value = N. This will correct
the issue of major data being reported for a non-FA eligible plan because the student is active in a program that IS FA eligible.

7) Reporting Suspended, Dismissed, and Discontinued students
If a student was dismissed after term start and dropped from classes but not withdrawn, the program details for the student don't report the same value (W) as the consolidation.  Some  conditional code logic in the SQR that executes if the student is Discontinued, Dismissed, or Suspended was missing from the logic in SRPCCONS where the individual programs are reported.  This logic has been added into the code.  




To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.