My Oracle Support Banner

Financial Aid Term Rebuilds Enrollment Intensity Percent From the Previously Correct Values to Zero for Terms in the 2025 Aid Year (Doc ID 3037483.1)

Last updated on OCTOBER 24, 2024

Applies to:

PeopleSoft Enterprise CS Financial Aid - Version 9.2 and later
Information in this document applies to any platform.

Symptoms

When running Financial Aid Term build, on-line or batch, when Aid Year 2025 terms are rebuilt, the enrollment intensity percent values on these terms are changing in some cases - from the previously correct values (based on the Financial Aid Load) to zero. This issue is not seen in every singe case, but in a subset of cases that may vary in volume.

For terms in Aid Year 2025 and forward, the enrollment intensity percent should never be assigned a 0 except when the students have a Financial Aid Load of 'No Units' ('N'). In these cases, the terms being rebuilt are appropriately assigned an FA Load <> 'N'.

The issue can be reproduced at will with the following steps:

  1. Identify a student active and built on fa term (STDNT_FA_TERM) for terms in both Aid Year 2024 and 2025.
  2. Navigate to Financial Aid > Financial Aid Term > Maintain Student FA Term > FA Term and retrieve the record for the student using Aid Year 2025 on the search component.
  3. Click 'Build' if the student is not already built for one or more Aid Year 2025 terms, then switch to Acad Level tab for the term(s), and note the Financial Aid Load is populated with some value <> 'N' and the Enrollment Intensity is properly populated as > 0.
  4. Navigate out of the component and back in for the same student, this time using Aid Year 2024 on the search component.
  5. Click 'Build', then switch to the Acad Level tab and note the enrollment intensity has rebuilt to 0 on the 2025 term(s).

Changes

The issue occurs after applying all of the available fixes related to FAFSA Simplification up through and including the 30 fixes delivered in PeopleSoft Release Patchset (PRP) 36348679: SSA LABELS ARE DISPLAYING AS SSN FOR AY2025.

Specifically, this issue is found to be related to the code changes delivered as the resolution for <Bug 36644351> - FA TERM BUILD PROCESS SHOULD NOT CALC ENRL INTENSITY FOR AY PRIOR TO 2025.

Cause

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
Symptoms
Changes
Cause
Solution
References


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