This chapter discusses:
Pension variables, rules, and tables.
Pension rules parameters maintenance.
Tables usage.
Plan rules customization.
The system provides parameter pages, which you use to create definitions for the 19 core functions that handle pension calculations. The definition pages you use can reference variables, rules, and tables.
Type |
Description |
Variable (alias) |
An alias is a calculated value that varies by employee. A variable can be stored in the database (for example, an employee's birth date) or calculated (for example, an employee’s age at termination). When you use multiple job processes, there are special rules for resolving aliases. |
Rule |
Rules are incorporated into the main parameter pages to provide functions that enable you to reuse specific subsets of the definitions. For example, you can create an earnings projection method using the projections rule and then apply that method within the final average earnings, cash balance accounts, and employee accounts functions. |
Tables |
Tables are lists of values that you use for specific functions. For example, you can set up mortality tables that can be referenced from an actuarial assumption set. |
See Also
This section discusses:
Variables usage
Rule utilities usage
You can configure eight types of variables to calculate values. A separate chapter describes each variable.
See Also
Using Date Aliases and Date Options
Using Duration Aliases and Duration Options
Using Function Result and Actuarial Factor Aliases
Using Custom Statements and Spouse Eligibility Statements
You can drop certain rule utilities into other definitions as needed, enabling you to reuse a rule without having to set up all of its parameters each time. Each rule is described in a separate chapter.
See Also
Creating Action and Reason Categories
Applying Section 401(a)(17) Earnings Limits
Use mortality tables and service schedules for specific purposes:
Mortality tables are part of an actuarial assumption set. When you create the actuarial assumptions, you specify the mortality table to include.
Service schedules show the amount of service credited for a particular service period based on the number of hours worked during that period. You reference these schedules from certain hours-based service definitions.
See Also
Crediting Service Based on Hours Worked
Although PeopleSoft provides extensive options for setting up plan rules, it is possible to use your custom code at certain points. Pension Administration enables integrating your modifications by providing a way to reference custom modules.
PeopleSoft provides a number of predefined places—identified by the User Code option on the parameter pages—where you can indicate that the system should use your code in processing a specific function.
You can also insert user code modules directly into the calculation jobstream. Unlike the predefined user code modules, which always produce a specific type of result, user code in the jobstream can be set up to handle any functionality and produce any type of result.
To use a specific user code parameter within a function, use clearly marked exit points within the associated parameter pages to execute your own custom code. These predefined user code options appear in your parameter sets as one of several options for a specific portion of the calculation.
This ability to exit from the pension jobstream, perform a custom calculation, and then reenter the jobstream with the results of that calculation, minimizes the impact of your modifications on the core system.
See Also