Suspended Prior Year ISIR Due to Search/Match Loads When Subsequent Year ISIR Passes Search Match
(Doc ID 2947580.1)
Last updated on JANUARY 25, 2024
Applies to:
PeopleSoft Enterprise CS Financial Aid - Version 9.2 and laterInformation in this document applies to any platform.
Symptoms
A student had a suspended ISIR record from a prior aid year due to not passing the Search / Match setup. In one example, the student did not match the Date of Birth (DOB) search match setup. The student had a subsequent ISIR for current aid year that met the Search / Match setup and was successfully loaded. When the ISIR Load process was next ran for the prior aid year, the student's ISIR successfully loaded, even thought the Search / Match was not met on that record.
The issue can be reproduced at will with the following steps:
- Navigate to Financial Aid, File Management, ISIR Import, 20nn-20nn Suspense Management, ISIR Suspense Management nn/nn, where nn refers to the current Aid Year;
- Select an emplid whose ISIR load from the prior aid year failed due to not meeting the Search Match criteria;
- Click the 'Process ISIR' button, and note the ISIR successfully loads;
- Navigate to Financial Aid, File Management, ISIR Import, 20yy-20yy Suspense Management, ISIR Suspense Management yy/yy, where yy refers to the previous Aid Year;
- Select the same emplid as in Step 2;
- Click the 'Process ISIR' button and not the ISIR successfully loads when the Search Match criteria are not met.
Changes
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 |