FAPPKENG Subscript out of Range Error 153

(Doc ID 2255900.1)

Last updated on NOVEMBER 20, 2017

Applies to:

PeopleSoft Enterprise CS Financial Aid - Version 9 and later
Information in this document applies to any platform.

Symptoms

On : CS 9 or 9.2 any environments

When attempting to run mass packaging or mass repackaging,
the following error occurs (referenced line number of FAPPKENG.cbl may vary):

ERROR
-----------------------
Object Code error : file '/appl/psft/fam/trn/sa900/cblbin/FAPPKENG.gnt'
error code: 153, pc=0, call=1, seg=0
153 Subscript out of range (in FAPPKENG.cbl, line 9209)

A cobol trace file of the process will identify the emplid being processed when the program halted. If auto-packaging/re-packaging is executed for this same student, the on-line process will often (though not always) also fail. The on-line message won't be the same as what is seen in the batch log, but may look something like the following - again, the specific numbers referenced may vary:

(2,-1) DERIVED_PACKAGE.FETCH_PKG_BUTTON.FieldChange PCPC:2335 Statement:39

or

(2,-1) DERIVED_PACKAGE_VALIDATE_AWARD.PB.FieldChange PCPC:1071 Statement:19

However, if the on-line log files - .out and .err files - are generated for the process as it fails, the .err file will display the same message seen in the batch log file.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1.Run mass packaging/re-packaging select
2. Run mass packaging/re-packaging assign plans
3. Run process mass packaging/re-packaging

WHAT IS WORKING
-------------------------
The program may successfully process other students before running into the specific data condition causing the error. The error may begin "out of the blue" after the process has been running successfully for some time previously.

BUSINESS IMPACT
-----------------------
The issue has the following business impact:
Due to this issue, users cannot complete the process of packaging or repackaging all their students. These will usually be batches too large to handle manually. A problem with one record causes the entire batch to fail. A trace can be run to identify the problem student and remove them from the batch, but that is time-consuming, and the process may then fail on another student down the line.

Cause

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