Understanding the Pension Job Stack

Although many action and reason events are important to pensions, others are not. For example, assignment completion is unlikely to impact pensions. Even events that may seem to be significant for pensions may turn out to be irrelevant. For example, a transfer action is not itself significant, but the new location or job may be.

At the beginning of every pension calculation, the system identifies all the codes you include in action and reason categories and creates a pension job stack. This is a job history that excludes all the events that have irrelevant action and reason codes.

Then, when you calculate service and consolidations, the pension functions further filter the job stack to include only the action codes referenced in a function's parameters.