EPY: Error code 153 (Subscript out of range) during Payroll Processing (PRIMARY SOLUTION) (Doc ID 607184.1)

Last updated on JULY 02, 2024

Applies to:

PeopleSoft Enterprise HCM Payroll for North America - Version 8.9 and later
Information in this document applies to any platform.

Purpose

This is a "living document" which is updated whenever new information becomes available.

Arrays define the amount of storage allocated to a given process. PeopleSoft delivers array sizes that we expect to be large enough to handle processing volumes for many of our clients, but due to the wide range of our customer base and specific data models and characteristics, it could be necessary for some clients to expand the sizes of their arrays to meet their processing requirements. We try to look for trends regarding what arrays are being exceeded. When Global Customer Support sees a pattern where a specific array is being consistently blown, we open an enhancement request that the array be delivered with a higher max-count in future releases.

Generally speaking, the arrays are related to comparatively static information in the system such as the number of earnings codes, rules, or tasks and therefore should not need to be re-expanded on a regular basis. Clients should not expect to have to expand arrays as the number of employees hired into a company grows.

Customers may occasionally exceed array sizes during payroll processing. The SUBSCRIPT OUT OF RANGE (153) error indicates that the program has tried to use an index value for an array area which is outside the bounds defined for the array. This can happen when:

There is more data than a program array is defined to hold (more than the maximum number of Earnings types or Deductions in a given pay run, for example); or
The subscript used as the pointer into an array contains a zero or spaces, which is not valid for subscripting and thus is out of range for the array.

The second source of this error (zero index value), occurs more frequently, so the first recommendation is to recompile all of your COBOL, being sure that you are using the most current set of COBOL programs and copybook files.

Have programs been recompiled recently as a result of an application of a fix or tax update?
Did you just compile selected modules or did you recompile everything?
The subscript out of range problem can be caused when you fail to include the correct version of a copybook or an old version of a related program when the COBOL programs were recompiled

If recompiling does not clear the problem, additional trouble shooting tips follow.

Note: Some payroll calculation errors can be resolved in advance by running and reviewing the PreCalculation Audit Report (PAY035) and the PreConfirm Audit Report (PAY)36).

See Document 1919072.2 for instructions on downloading and running self-service diagnostics on output from the PreCalculation Audit Report and PreConfirm Audit Reports.