Resolving Overrides in Batch Processing

This topic discusses overrides in batch processing.

The following table describes how overrides to supporting elements are resolved during batch processing.

Program

Process

Payee Data Manager Page

Resolves hierarchy between pay entity, pay group, payee, and calendar supporting element overrides and loads the override with the highest priority into a supporting element override/value array.

PIN Manager Page

Checks to see if the supporting element is resolved.

  • If the element isn’t resolved, the Payee Data Manager looks for a supporting element override.

    • If a supporting element override exists, the override value is used.

    • If no supporting element override exists, the PIN resolution program is called.

  • If the element is resolved, the PIN manager checks the RECALC logic.

    • If RECALC = NO, the PIN manager returns the previously resolved value.

    • If RECALC = YES, the system looks for a supporting element override. If none exists, the PIN manager calls the PIN Resolution program to resolve the element.

Element Assignment Page

An array, formula, bracket, or date extract can assign a value to another element. In this case, the element is considered resolved.

Entitlement/Take program Page

Applies primary element overrides, then payee/element overrides, as applicable, to a supporting element used by take or entitlement elements.

For each type of override, the program saves and stores the current value of the supporting element before assigning the override value. Say a primary element override and a payee/element override exist for Variable A. The system stores the current value of Variable A (5), retrieves the primary override value (6), stores the current value of Variable 1 (6), retrieves the payee/element override value (3), and so on.

When the override is no longer in force, the saved value of the supporting element is restored—in our example, 5.