Resolving FAPSAR00 Errors in PCD for the 2026-2027 AY F02 Service Indicator Process
Purpose: Use this document as a reference on how to resolve FAPSAR00 Run Statuses that run to Error in PCD.
Audience: Financial Aid Staff responsible for assigning F02s in PCD for the 2026/2027 Aid Year
In preparation of loading ISIR Files with the new layout from April 26th to current date before the FA PRP is delivered into Production, colleges have the option of loading new file layout ISIRs into PCD so that a list of students can be generated to add a F02 Service Indicator (Tuition Due- Pending Aid Hold) in Production.
FAPSAR00 Unique Constraint (SYSADM.PS_NSLDS_ISIR_DTL) Violated (KB291292)
When attempting to run the cobol program FAPSAR00, the following error occurs:
Application Program Failed
In Pgm Section : ERROR INSERTING I-NSLDSID (FAP00SLD)
With Return Code: 00805
Error Message : ORA-00001: unique constraint (SYSADM.PS_NSLDS_ISIR_DTL) violated
There are a couple of different known causes for the issue:
- The first known cause is when multiple instances of FAPSAR00 are being run in parallel. Typically this would occur in a multi-institution environment where the school chooses to run the job for multiple institutions at the same time. If a particular student happens to be included in the ISIR batch for two or more different institutions, then the process instances may attempt to insert the exact same NSLDS Detail transaction resulting in the error. This issue has been reported in the following bugs:
Release 9.2 - Bug 23114099-UNIQUE CONSTRAINT ON NSLDS TABLES WHEN LOADING ISIRS FOR MULTIPLE INSTITUTIONS - The second verified cause is bad data in PS_ISIR_00_4A_EC - the staging table for the NSLDS data that gets loaded into NSLDS_ISIR_DTL when the ISIR is loaded.
Normally in the loan sequence number fields you should only see values of blank, 00, or the number appropriate for the sequence number (01,02,03,04,05,06). In one case the values for five of the six sequence numbers were 'NN', and so the system translated that to some odd random number and attempted to insert multiple rows in the table using the same number, leading to the error.
The exact bad data could not be determined. If it is due to the file layout, then the issue will no longer occur once the FA PRP is in Production. If it is due to other bad data, the college will need to request a new file per Oracle.
Colleges will need to Skip the “problem” students to proceed with loading the rest of the ISIRs into PCD.
Due to institution security on the ISIR Suspense page, colleges may not be able to select the Skip/Done radio button.
There are two other ways to have the ISIR process skip the student:
- Update the student’s SSN on Add/Update a Person to XXX-XX-XXXX. This will result the FAPSAR00 process not finding the bad data student. Unfortunately, this does not work for all students. If there is already an ISIR attached to the student in the system, the ISIR process is able to find the student regardless of whether it is an ISIR from Aid Year 2026
Select the Skip/Done radio button on the bad data student’s ISIR via an equation engine.
At the end of the CBL_FAPSAR00_xxxxxxx.log, the problem student’s SSN is indicated:
Create Run Equation
Navigation: Set Up SACR > Common Definitions > Equation Engine > Run Equation
- At the Run Equation page and select CTCFAISIRSKP as the equation
- Define the first row:
- SSN
- String
- Student's SSN
The equation engine runs a SQL that updates the blank ISIR_LOAD_ACTION field (the field tied to the radio buttons Add ISIR, Recycle, Skip/Done) to ‘I’ (Skip/Done).
The student that is Skipped will not appear in PCD; review Skipped students' eligibility in FPS so a determination can be made to add an F02 in Production.
Note: There may be more than one student causing the FAPSAR00 Error problem so colleges may need to run FAPSAR00, get the error, run the equation, run FAPSAR00 again, a few times until the process runs to Success and Posted and students are loaded in PCD.
0 Comments
Add your comment