Last updated on APRIL 14, 2016
Applies to:PeopleSoft Enterprise CS Financial Aid - Version 9 and later
Information in this document applies to any platform.
The following issues are observed when FA Term rebuilds, after Program or Plan changes are made in Student Records:
1. Program and plan are updated by Records after the start of term, but before the max program effective date for term (last day for term activation). End result is when FA Term rebuilds, it updates the program, but not the plan, and this mismatch causes problems with SULA reporting (can't find matching program/plan on the credential level cross reference table).
2. Plan is updated after the start of the term, but before the max program effective date for term. Program remains the same. When fa term rebuilds it
doesn't update the plan. This doesn't cause the same problem with SULA reporting as in scenario 1....but it will cause a different problem of schools
reporting the WRONG plan.
3. Program and plan are updated by Records after the start of term, and after the max program effective date for term (last day for term activation), but
before the student's first actual class day for the term. End result is when FA Term rebuilds, it updates the plan, but not the program, causing same
problem described in scenario 1.
4. Program and plan are updated effective first day of the term, however the student is enrolled in at least one session or class beginning before the term start date. End result is same as described in scenario 1.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms