Issue: Pell Validation Edit 9601 - 'Student is Ineligible Because SAI is Greater than Twice Max Pell Amount for the Aid Year'

When packaging Pell for Aid Year 2026 students with a Student Aid Index (SAI) that is twice the maximum Pell amount (e.g.14790), the item type fails validation with edit 9601 - "Student is Ineligible Because SAI is Greater than Twice Max Pell Amount for the Aid Year".

This edit occurs for a Pell Item Type being awarded for the first time or when re-validating a student with an existing Pell. 

The 9601 edit is unexpected for Aid Year 2026, as the condition is expected to only apply beginning 07/01/2026. Students in 2026, assuming they are or were awarded prior to 07/01/2026, are still eligible for Pell, despite the high SAI, if the Minimum Pell Indicator is set on the ISIR.

Example:  Aid Year 2026 student has an SAI of 22,141 and is eligible for Pell. 

Once Pell is re-validated, Pell is cancelled:

The reason for the cancellation is Edit 9601 - "Student is ineligible because SAI is greater than twice Max PELL amount for the Aid Year."

Impact:  For the remainder of Aid Year 2026, colleges should be careful when re-validating Pell item-types when adjusting aid. Those mass packaging aid for Aid Year 2026, make sure to run and review CTC_FA_MASS_PACK_RESULTS_01 query to find students with Message Text "Student is ineligible because SAI is greater than twice Max PELL amount for the Aid Year" as Pell may need to be manually packaged.
 

Resolution: Fix is targeted for a PRP currently expected to post in mid July 2026 and then will also be included in Campus Solutions PUM Image 9.2.39.

Status: In Progress

After applying PRP Patch 38749448 - OBBB: DATA MODEL UPDATES and loading new ISIR files for the 2025-2026 aid year, the following error occurs when selecting the ‘Expand All’ or ‘Collapse All’ links on the NSLDS Data 1 link on the 2025-2026 ISIR File Data page.

'GetField: Field 'DERIVED_ISIRSTG.SFA_NSLDS_1LB5' not found in scroll level 0. (2,155) DERIVED_ISIRSTG.EXPAND_ALL_PB.FieldChange PCPC: 2151 Statement: 33'

Navigation: Financial Aid > File Management > ISIR Import > 2025-2026 ISIR File Data

Image: Error Message displays when selecting the 'Expand All' link:

Users can move past the error message by selecting ‘OK’ and the page displays without issue. The same behavior occurs when clicking the ‘Collapse All’ link

Resolution: Fix has not been targeted by Oracle.

Status: TBD

Oracle delivered the new OB3 Info tab for FA Term including two checkbox fields for OB3 Legacy Eligible Flag and OB3 Use Professional Lifetime. Because these fields were delivered without corresponding overrides, if either box is updated manually or using the Population Update Process, the value won't maintain and will get set back to the default value of ‘N’ with the box checked off, the next time the term rebuilds.

It's expected there should be an override flag to maintain the value, like with all other similar fields; OR when FA Term rebuilds, it should carry over the value (whether 'Y' or 'N') from the previous row, rather than rebuilding with the 'N' default value each time.

Bug 39474921 - OB3 FLAGS ON OB3 INFO TAB REBUILD AS 'NO' EACH TIME WITHOUT AVAILABLE OVERRIDES

Navigation: Financial Aid > Financial Aid Term > Maintain Student FA Term

Image: Previous row with 'OB3 Legacy Eligible Flag' selected

Image: Rebuilt row with 'OB3 Legacy Eligible Flag' returning to default of not being selected:

Should colleges need a process to update the values back onto a rebuilt row until a patch is delivered by Oracle, FA Support will create a pop-update process.

Resolution: Fix has not been determined by Oracle.

Status: TBD

When attempting to run the Process NSLDS Files process, the FAPTALRT COBOL SQL process fails during the ACG insert step with the following error:

Application Program Failed
Action Type     : SQL UPDATE
In Pgm Section  : SQLRT: EXECUTE-STMT
With Return Code: 08627

Error Message:
[Microsoft][ODBC Driver 17 for SQL Server][SQL Server]
String or binary data would be truncated in table 'SA92PTU.dbo.PS_NSLDS_ACG',
column 'SFA_ACG_SCHL_YR'. Truncated value: ' '.

Stored Stmt     : FAPTALRT_I_ACG
FAPTALRT - SQL ERROR IN SECTION: 20455-INSERT-ACG (I-ACG)

Bug 39336337 - OBBB: Data Model Update to NSLDS TEACH/ACG/NSG/IASG records

Resolution: Fix is targeted for a PRP currently expected to post in mid July 2026 and then will also be included in Campus Solutions PUM Image 9.2.39

Status: In Progress

Oracle currently has reported multiple scenarios where NSLDS information is displayed inaccurately in PS.

Bug 39465112 - NSLDS PUSH: NSLDS CROSS-REFERENCE TO AGGREGATE AREA HAS NOT BEEN DEFINED

When running the Update NSLDS with Aggregates (NSLDS Data 'Push') application engine process SFA_NSLDSUPD, it is not updating any aggregates. The aggregate rows get created, but the NSLDS amounts are not updated and left at 0. The message 'NSLDS Cross-Reference to Aggregate Area Has Not Been Defined' appears multiple times in SFA_NSLDSUPD output file.

Resolution: Fix is targeted for a PRP currently expected to post in mid July 2026 and then will also be included in Campus Solutions PUM Image 9.2.39

Status: In Progress

Bug 39416224 - AFTER OB3 UPDATE, LOADING 'OLD' ISIR LAYOUT NOT UPDATING NSLDS FIELDS THAT HAVE A LENGTH OF 6 AS EXPECTED

After applying OB3-related updates, loading ISIR files that use the old ISIR layout causes NSLDS aggregate amounts to be loaded incorrectly. Values that should be stored as whole-dollar amounts are instead written with an implied decimal, resulting in amounts being reduced by a factor of 100. For example, an incoming aggregate of $3500 is loaded as $35.00.

This issue occurs when processing old-format ISIR files, including prior-year ISIRs and the old 2027 ISIR layout. The problem is visible in the NSLDS data stored in the NSLDS_FAT_AGGR table.

Resolution: A fix is in a POC released June 9th. FA Support will review to determine if this should be applied to an environment for testing.

Status: TBD

Bug 39372779 - INCORRECT FIELD VALUES DISPLAYED AS ZERO AFTER LOADING NSLDS FILE IN OLD FORMAT

Details of the issues are not clear.

Resolution: A fix is in a POC released June 9th. FA Support will review to determine if this should be applied to an environment for testing.

Status: TBD

Bug 39487651 - NSLDS PUSH: ORA-01400: CANNOT INSERT NULL ERROR WITH PROCESSING TEACH

When running the Update NSLDS with Aggregates (NSLDS Data 'Push') application engine process SFA_NSLDSUPD, it finishes in 'No Success', with the following error message indicated in the .stdout file. The message will vary slightly in each case, but below is an example of the error:

Return: 1400 - ORA-01400: cannot insert NULL into ("EMDBO"."PS_STDNT_AGGR_LIFE"."SFA_OB3_PROF_TOT")

Failed SQL stmt: INSERT INTO PS_STDNT_AGGR_LIFE (EMPLID , AGGREGATE_AREA , AID_YEAR , UNDRGRAD_TOTAL , GRADUATE_TOTAL , TOTAL_TERMS , CURRENCY_CD , SFA_NSLDS_AGGR_AMT , OVERRIDE , LASTUPDOPRID , SFA_NSLDS_UPDDTTM , SFA_NSLDS_PUSH_DT , SFA_PKG_DEP_STAT , PAR_CREDIT_WORTHY , DL_HEAL_LN_SW , SFA_NSLDS_GRAD_AMT , SFA_GRAD_OVERRIDE , SFA_PRCNT_USED_RPT , SFA_PRCNT_USED_TOT , SFA_PRCNT_OVERRIDE , SFA_LEU_NSLDS , SFA_LEU_NSLDS_OVRD ) VALUES ('FAPK0131' , 'TEACH' , '2027' , 0 , 0 , 0 , 'USD' , 0 , 'N' , ' ' , NULL , NULL , ' ' , ' ' , ' ' , 0 , 'N' , 0 , 0 , 'N' , 0 , 'N' )

The issue does not occur in every case, but happens specifically when the code for TEACH is triggered based on the available data and configuration for the TEACH aggregate set up on the Aggregate Translation and Aggregates for Institution tables.

Resolution: Fix is targeted for a PRP currently expected to post in mid-July 2026 and then will also be included in Campus Solutions PUM Image 9.2.39

Status: Workaround provided by FA Support on 06/23, see NSLDS Push SQL Issue and Solution doc

Issue: To accommodate the OB3 changes, the COD system has updated their DSDF and PGRC files.

Impact: The PGRC file will have file length and field changes which require modification to the Pell Reconciliation CEMLI. Based on the expected changes to the DSDF file, the Loan Reconciliation report may not require modification. We cannot confirm that the Loan Reconciliation report will not be impacted until we have a valid DSDF file in July.

Workaround: Run report in COD and compare manually

Resolution: Anticipated timeline Mid-September

Issue: Selecting the 'Calc SAI' button for Aid Year 2027 generates the pop-up message ''FM NAC Calcs are not enabled for Aid Year 2027. (14400,2350)' on the Correct ISIR Records page and the Simulate FM page.

Example:

Bug: 38728309 - 2026-2027 SFP JAR FILE UPDATE #1

Impact: ISIR corrections cannot be performed in PS for Aid Year 2027.

Resolution: While the warning message will no longer appear with the application of PRP 2.1 (6/16). Calc SAI has not been enabled due to SAI calculations being under review.

Issue: The following fields’ translate values have not been updated by Oracle to the new values defined by Dept of Ed for Aid Year 2025 and forward

      Record - ISIR_STUDENT

      Field: MARITAL_STAT

      Field: CURRENT_GRADE_LVL

      Record - ISIR_PARENT

      Field: MARITAL_STAT

Example of ISIR_STUDENT record’s MARITAL_STAT field’s translate values

Bug: 18166065 - UPDATE THE TRANSLATE VALUES ON THE FIELDS THAT STORE DATA ON THE ISIR

Impact: Queries that pull marital status and current grade level data from ISIR_STUDENT and ISIR_PARENT need to be set to populate the number value (i.e. ‘2’) instead of the translate value (i.e. ‘Married’) to avoid confusion

Marital Status value of ‘3’ is ‘Remarried’ as of Aid Year 2025 but the results will incorrectly show ‘Separated’ if the translate values were to populate in the query

Resolution: No fix is targeted.

Known Issue: On the Correct ISIR or Simulate FM components, when accessing a record for an Aid Year that is different from the User Defaults defined Aid Year, then selecting ‘Return to Search’, the Aid Year changes to the Aid Year defined in User Defaults. For example, when 2025 is defined in User Defaults and staff view a 2026 record on the Correct ISIR page, when selecting ‘Return to Search’, the emplid remains but the Aid Year returns to the user's default of 2025.

It is expected that these components work like all others in Financial Aid with the ‘Return to Search’ maintaining the same aid year just being viewed.

Resolution: Because two different components are affected by the issue, Oracle has determined separate bug fixes are required:

• Correct ISIR component: Image 36
• Simulate FM component: PRP 3.3 (12/10)

Status: Updated, In Progress

Known Issue: Dept of Ed is not accepting any batch corrections from any software system for the 2024-2025 Aid Year

Update: As of 2/27/25, the Electronic Data Exchange (EDE) began processing batch corrections for both the 24-25 and 25-26 aid years. Due to ongoing issues with SAI calculation, it is recommended that colleges continue to make manual corrections in FPP until Oracle provides an accurate JAR file.

Impacts: Ability to make batch corrections from ctcLink

Workaround: Continue to make manual corrections directly in FPP

Resolution: TBD

Status: In Progress

Title: College costs header was not updated on the 2026 College Financing Plan template

Known Issue: When viewing the College Financing Plan for aid year 2026 there is a heading that displays ‘College Costs You Will Be Required to Pay’. The federal specifications show that the heading should reflect ‘Estimated College Costs You Will Be Required to Pay’.

Example:

Resolution: Oracle has fixed the issue for Aid Year 2027 and forward with PRP 1.3 (01/30/2026)

Status: No target date for fixing Aid Year 2026 at this time. 

Known Issue: When a student is Discontinued or Withdrawn from their Academic Program, the Enrollment Intensity field on FA Term is not updated to 0.

Bug 371106870

Resolution:  Fix TBA

Workaround:  Adjust FA Term manually w/ override

Status: Fix TBA

Known Issue:  When Build FA Term is run for census, students with no enrollment activity for the term have the FA Load value set to N units while Enrollment Intensity remains at it's original value. The expectation is that students with no enrollment activity for the term will have FA Load set to N units and Enrollment Intensity set to zero.

Impacts: FA Processing

Resolution: Fix to be determined by Oracle

Workaround:  FA Support has developed a pop update that can be run after the census jobset, to set the enrollment intensity value to zero for students with no enrollment activity for the term. This process is expected to be available to colleges at the end of the week (October 4).

Priority: High

Status: In Progress

The following incorrect behavior has been observed after clicking the “Calc SAI” button without  making any data changes:

• Dependent Students (Formula A) is not calculating Payroll Tax Allowances correctly for the Parent, and is not using federal tax paid amount as an allowance against income for the student.
• Independents without dependents (Formula B) is not using the federal tax paid amount as an allowance against income, resulting in calculated SAIs that are higher than they should be.
• Independents w/dependents and tax filing status is 1 (Married filing separately) the calculation is using Formula B instead of Formula C, which means, Federal taxes paid is not  being considered as an allowance against income, resulting in higher SAI Calculations.
• Independents w/dependents and tax filing status is 2 (Married filing joint) the calculation is using Formula B instead of Formula C. In some cases, students in this category may also reject.

Oracle has logged it as a bug. Bug 36690305 SFP 2025 JAR File Update #5

Fix is targeted for Image 33 but may be delivered earlier in a PRP patch.

Workaround: Get the accurate SAI from the ISIR Suspense Management page and/or check the FPP in FPS.

Using the Mass EFC Calculation batch process produces the same issues as using the Calc SAI button. However, if there are students with Reject Reasons (accurate or not), error messages do not return in the Message Log for the Mass EFC Calculation process. The SAI will still update to an Official 0 SAI value. The Dependency Status is removed, and values on the SAI and Flags tab are set to 0.

Navigation:  Financial Aid > File Management > ISIR Import > 2024-2025 Suspense Management

Image below: SAI value from ISIR on the 2024-2025 Suspense Management page, Example -1500 SAI

Image below: SAI value from ISIR on the 2024-2025 Suspense Management page,  Example 31183 SAI

Navigation:  Financial Aid > Federal Application Data > Correct ISIR Records

Image below: Key data points set to 0 or removed, and SAI Status inaccurately set to an “Official” 0 on Correct ISIR Records page  True for both Examples

Some SAIs are modified by the new Calc SAI / Mass EFC Calculation logic, even when there are no Override values entered. Oracle has not yet provided an update for this functionality that can be used with confidence.

Navigations Impacted:

• Financial Aid > Federal Application Data > Correct ISIR Records
• Financial Aid > File Management > Mass EFC Calculation
• Financial Aid > File Management > ISIR Import > 2024-2025 Suspense Management*
• Financial Aid > File Management > ISIR Import > Process ISIRs*

* Pages impacted if the Call Mass EFC logic is selected in the college’s ISIR Data Load Parameters configuration.

One of the pages with an issue is Correct ISIR Records due to PS SAI calculation not being accurate in some cases. We strongly discourage relying on the SAI calculation derived from the PS SAI calculation processes since the underlying logic still has many reported bugs awaiting resolution from Oracle.

PS calculates SAI during the following processes:

• Loading ISIRs into the Correct ISIR Records page
• Running Mass EFC Calc
• Selecting Calc SAI button

Workaround:  The SAI straight from the ISIR file can be found on the 2024-2025 ISIR Suspense Management page.

Independent students often receive a “Rejects returned by the SAI Calculator” error message after using the Calc SAI button. The Transaction Detail tab displays Reject Reasons that do not accurately reflect the issues with the student’s data that needs to be modified/corrected. The SAI is then inaccurately updated to 0 and the SAI Status is set to "Official", significantly increasing the risk of inaccurate awarding. Similar error messages can occur for Dependent students, as well.

Navigations with Calc SAI Button

• Financial Aid > Federal Application Data > Correct ISIR Records
• Financial Aid > Federal Application Data > Simulate FM

Navigation:  Financial Aid > Federal Application Data > Correct ISIR Records > SAI and Flags tab

Image below: An independent student “Rejects returned by the SAI Calculator” error message

Navigation:  Financial Aid > Federal Application Data > Correct ISIR Records > Transaction Detail tab

Image below: The student’s Transaction Detail tab inaccurately populates reject reason codes tied to a dependent student

Workaround:  Until this is resolved by Oracle, it is recommended for colleges to review the ISIR in the FAFSA Partner Portal to confirm the reject codes associated with the ISIR transaction.

Until this is resolved by Oracle, it is recommended for colleges to review the ISIR in the FAFSA Partner Portal to confirm the reject codes associated with the ISIR transaction.