My Oracle Support Banner

Enable the Ability To Maintain Different Limits For Different Companies (Doc ID 3075278.1)

Last updated on MARCH 05, 2025

Applies to:

PeopleSoft Enterprise HCM Human Resources - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.

Symptoms

After applying SECURE 2.0 feature, the new Savings Age Catch Up Extension process now uses the limit table for the extension based on age. We have been running this job for the US, Puerto Rico, and Guam. Previously, this job did not utilize the limit table, and there was an option to manually add the extension amount in the run control based on the Company selected. However, the new process now uses the Limit Table for the extension amount. The issue is that the limit table is not company-specific.

The issue could be reproduced with the following steps:

  1. Add 402(g) limit. Navigation: Setup HCM > Product Related > Base Benefits > Rates and Rules > Limit tables. Note that the limit table is not company-specific.
  2. Run the Savings Plan Age Catch Up Extension process for Company C1. Navigation: Benefits > Monitor Savings Pln Extensions > Savings Age Catch Up Extension > Savings Plan Age Catch Up Extension.

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


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.