Next Aid Year Wipes Out Projections And Sets Students To Inactive For Current And Future Terms (Doc ID 3074174.1)

Last updated on FEBRUARY 26, 2025

Applies to:

Symptoms

When running FA Term for the future aid year (2026), the build of that new aid year is erroneously setting the summer 2025 term to inactive with a 'No Data' Source, even though the start date of that Term is in the future.

FA Term set up is set to project summer 2025 with no FA census date. Summer starts on 5/12/2025. When 2026 is run, the new terms for the 2026 aid year are created, and the projections for summer 2025 term (2255) is set to inactive.

It is expected that since the summer term has not started (future start date), and there is NO Census Date on the FA Term Setup for the summer, the term should build as projected, or remain an active, projected term.

The issue can be reproduced at will with the following steps:
1. The student has 3 terms built for the 2025 aid year - Fall 2024, Spring 2025 and Summer 2025 all the terms with an aid year of 2025. Note, summer 2025 term doesn't start until May (future start date).
2. Build FA Term in both Updates and Projections for the 2026 Aid Year after Spring 2025 Census Date has passed.
3. Note there are now 6 terms built for the student 3 for the 2026 aid year (Fall 2025, Spring 2026 and Summer 2026) the rows are active and the Build Source = Program.
4. Because the student is enrolled for both Fall 2024 and Spring 2025, these two terms remain active and a new row may get inserted depending on any changes from the last time FA Term was run. However, the summer 2025 term which has No Census Date defined, and the term has NOT started, the row is set to inactive.

Changes

Cause

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