Last updated on APRIL 20, 2016
Applies to:PeopleSoft Enterprise CS Financial Aid - Version 9 and later
Information in this document applies to any platform.
When manually revising awards, Pell awards can redistribute between terms, sometimes
with no warning for the user. The root problem is an inconsistency in the
approach of recalculating term awards, versus the overall award amount. Term
amounts are allowed to be increased beyond the original specified amount,
while the overall award amount is not.
The issue can occur with both unlocked and locked awards. Some examples:
1) Pell Census date is early in the term - when students can still add classes. Pell is awarded Fall/Spring, based on half time/full time load respectively, and is unlocked. Student subsequently increases Fall load to Full Time. The next time the package is revalidated (for any reason), the Fall Pell will be recalculated to the Full Time amount; however, because the system won't increase the award beyond the original amount, it has to then *reduce* the spring amount accordingly; the two term amounts end up essentially "flipped".
2) Community College or other school where many R2TIV are processed. Fall amount is reduced and locked, but school does not want to be doing all subsequent recalculations manually, thus they will unlock the awards at some point so that subsequent terms can be repackaged in batch. Result after manually unlocking is the same as scenario 1 above. The fall amount will increase back up based on load, and the spring amount will subsequently reduce to keep the total award at the previously specified amount.
3) School awards summer as a header. Academic Pell is awarded first - based on half time load in fall, full time in spring. The award is locked after packaging based on setup. Summer Pell is then awarded which leads to necessary reduction in academic Pell. However, due to new logic introduced in CS 9 Bundle 22 and CS 8.9 Bundle 29, the system recalculates the Fall Pell amount based on full time due to the lock flag, and the spring amount to the remainder of the rule amount, which was clearly not the users' intent.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms