Setting Up Overrides

This chapter provides an overview of overrides and discusses how to:

• Define pay entity overrides.

• Define pay group overrides.

• Define payee overrides.

• Define pay calendar overrides.

• Define overrides through elements.

• Resolve overrides in batch processing.

Understanding Overrides

This section lists common elements used in this chapter and discusses:

• Override levels.

• Overrides available for primary elements.

• Overrides available for supporting elements.

• Begin and end date logic for overrides.

• Element overrides and segmentation.

Use overrides to control the values the system uses to resolve an element for a specified time period. When you run the absence process, the system retrieves the rule definition for the element and applies any override instructions that you’ve entered.

Common Elements Used in This Chapter

Override Levels

Before entering instructions to override an element, you must specify allowed types of overrides for that element by selecting the appropriate check boxes in the Override Levels group box on the Element Name page.

When you enable overrides for a supporting element, clear the Always Recalculate check box on the Element Name page. Otherwise the system uses the value of the element according to the element definition, not the override value.

Note. An additional level, payee calendar overrides, exist for supporting elements through the Off-Cycle Requests component. This level is available for off-cycle requests only and does not extend to on-cycle calendars. Before entering supporting element overrides on the Payee Calendar SOVR page, you must select the Payee and the Calendar check boxes in the Override Levels group box on the Element Name page for the supporting element.

See Also

Managing Off Cycle Processing

Overrides Available for Primary Elements

Several override levels enable you to control the value of absence take, and absence entitlement elements, which the system applies in this order:

1. Payee overrides.

   Assign or disable absence elements or override the definition of absence elements.

2. Pay calendar overrides.

3. Via element overrides.

Overrides Available for Supporting Elements

Absence Management offers seven override levels which enable you to control the values of brackets, dates, duration, formulas, and variables:

• Pay entity overrides.

• Pay group overrides.

• Payee overrides: Override the value of a bracket, date, duration, formula, or variable element whenever it’s resolved for the payee.

• Payee/Element overrides. Overrides the value of a variable used by a specific entitlement or take assigned to a payee.

• Pay calendar overrides.

• Via element overrides.

• Element definition overrides.

When the system encounters multiple overrides for a supporting element, it applies the overrides in the sequence illustrated below, beginning with pay entity overrides.

Element Override Hierarchy

Note. A payee/element override refers to the override of a variable element that’s associated with a particular entitlement or take for a payee. Enter such overrides on the Element Detail page, linked to the Payee Assignment By Element and Element Assignment By Payee pages. A payee override is the override of a bracket, date, duration, formula, or variable that’s associated with a payee. Enter such overrides on the Payee Supporting Element Overrides page.

Example

VARIABLE1 has the following values:

• 30 according to the rule definition.

• 20 according to a pay entity override.

• 10 according to a pay group override.

In this case, VARIABLE1 resolves to 10, because pay group overrides take precedence over pay entity overrides.

Begin and End Date Logic for Overrides

When entering override instructions, you must specify a begin date.

The begin date tells the system when to start applying the override instructions. The current date is the default.

In most cases, end dates are optional. They specify when the override instructions become inactive. They are required only when you enter multiple rows of instructions for the same element.

The processing rules for begin and end dates vary, depending on the type of override being processed.

Payee Overrides and Segmentation

This section discusses:

• Payee overrides and segmentation.

• Segmentation caused by payee overrides.

• Proration and segmentation in the case of payee overrides.

Payee Overrides and Segmentation

You can set up your Absence Management system to slice or segment absence periods due to changes in Human Resource or other data, including:

• Changes in job status or title that occur mid period.

• Departmental transfers that occur mid period.

• Changes in compensation rate that occur mid period.

If there is a payee override in a sliced or segmented period, the system applies the override to the different slices/segments based on the segment/slice end dates as well as the override’s end date.

The system follows these rules to determine the slices or segments to which to apply an override:

• If an override is to apply to a segment, the end date of the override must equal or be greater (or blank) than the end date of the segment.

• An override can apply to more than one segment if the end date of the override is greater than one segment’s end date and greater than or equal to the subsequent segment’s end date (or blank).

• If the end date of the override is less than the end date of the segment, the override doesn’t apply to that segment.

• Payee overrides must be active as of the segment end date.

Pay entity, pay group, and element definition overrides are unaffected by segmentation. The system retrieves the definition of the element and the override only once every period, regardless of period or element segmentation.

Note. We discuss the rules for applying overrides to slices/segments in a period in greater detail in the chapter on segmentation.

See Segmentation and Payee Overrides.

Element Segmentation Caused by Payee Overrides

As noted previously, you can set up your Absence Management system to slice or segment pay periods due to changes in HR or other data. However, you can also configure the system to initiate segmentation and proration directly in response to an override—in the absence of an other data changes. That is, you can configure the system so that overrides are themselves treated as data changes that trigger segmentation. Then, when you assign or override the value of an element, the system slices the assigned element and any other elements included in the segmentation list set based on the begin and end dates of the override.

For example, assume that you set up the system to trigger segmentation when you assign or override entitlement element E1, and that you assign E1 to a payee on the Element Assignment by Payee (GP_ED_PYE) component with begin and end dates of 10 and 20 June respectively (assume a monthly pay period). Based on the assignment/override begin and end dates, the system will slice the element into three segments and process (and prorate) the element in the second slice:

Note. The only type of segmentation that can be triggered by an element assignment or override is element segmentation.

To set up the system to trigger segmentation in response to an element assignment:

1. Select the Active Anytime Within the Segment Period option on the Countries (GP_COUNTRY) component .

   When you do this, the system processes all element assignments/overrides that fall within a period—even those with end dates that are less than the pay period end date.

   See Defining Country-Level Setup.

2. If you want the element you are assigning to be prorated, associate the element with a proration rule on the entitlement definition pages.

   See Defining Rounding and Proration.

3. Set up segmentation triggers for the begin and end-dated entitlement and take assignment record (GP_ABS_OVRD), and list the entitlements and takes that should trigger element segmentation when the assignment begin date comes after the pay period begin date, and/or the assignment end date comes before the period end date.

Proration and Segmentation in the Case of Payee Level Overrides

Proration of payee level, primary element overrides occurs under the following conditions:

Note. Primary element overrides include entitlements and takes. Supporting element overrides include elements such as variables, formulas, arrays, and brackets.

• When period or element segmentation is triggered by data changes not directly related to an element override or assignment.

  • If there is period segmentation in the period to which an entitlement or take assignment applies (that is, all elements are segmented), the system prorates the assigned element based on the segment begin and end dates if the element is defined to be prorated. If not, the entire value of that element is applied to each of the targeted segments.

  • If there is element segmentation in the period to which an entitlement or take assignment applies, the assigned element is included in the list of elements to be sliced, and that element is defined to be prorated, the system prorates the element based on the slice dates. If not, the entire value of the element is applied to each of the targeted slices.

• When you configure your system so that primary element overrides or assignments directly trigger element segmentation.

  In this case, the system slices the assigned element (and any elements associated with that element on the list set) based on the begin and end dates of the assignment as long as that element is defined to be prorated. There does not have to be slicing or segmentation for any other reason. If the element is not defined to be prorated, the full value of the element is processed within the slice defined by the assignment begin and end dates.

  Note. You can set up the system to slice an element within a pay period based on the begin and end dates of the overrides assigned to a payee on the Element Assignment by Payee (GP_ED_PYE) and Payee Assignment by Element components (GP_ED_ELEM). We discuss how to do this in the chapter on trigger definitions.

  See Rules for Segmentation Triggers: Setting Trigger Effective Dates and Generating Triggers.

Note. Primary element overrides are prorated if the element is defined to be prorated and there is either period segmentation (all elements are segmented), or there is element segmentation and the element being assigned is on the list of elements to be sliced.

In the case of supporting element overrides, the supporting element is prorated if it is a component of an element that is defined to be prorated and that element is segmented/sliced.

Defining Pay Entity Overrides

This section provides an overview of processing rules for pay entity overrides and discusses how to override the value of elements that are associated with a pay entity.

Understanding Processing Rules for Pay Entity Overrides

During processing, the system refers to the begin and end dates (if any) and the Definition as of Date that were defined for the element on the Element Name page.

For the override instructions to take effect:

• The begin date must be before or equal to element’s Definition as of Date.

• The end date must be greater than or equal to the Definition as of Date.

Example

VARIABLE1 is defined as follows:

• Definition as of Date = Calendar Period Begin Date.

• Value = 100.

• Pay Period = January 01, 2004 − January 31, 2004.

The following pay entity override exists:

• Begin Date = January 16, 2004 (no End Date).

• Value = 200.

Payee 1 has segmentation on January 10, 2004. Payee 2 has no segmentation.

Both payees have the same value for VARIABLE1. Payee 1’s segmentation doesn’t alter the value of VARIABLE1.

In the diagram, the pay entity supporting element override is not applicable to either payee, because it wasn’t applicable as of the VARIABLE1 Definition as of Date (Calendar Period Begin Date), resulting in a value of 100 for both payees.

If the Definition as of Date for VARIABLE1 is Pay Period End Date, both payees use the pay entity override value 200.

Processing rules for pay entity overrides example

Page Used to Define Pay Entity Overrides

Overriding the Value of Elements That Are Associated with a Pay Entity

Access the Pay Entities - Supporting Element Overrides page (Set Up HRMS, Product Related, Global Payroll & Absence Mgmt, Framework, Organizational, Pay Entities, Supporting Element Overrides).

To define a pay entity override on the Pay Entities - Supporting Element Overrides page:

1. Select the type and name of the supporting element for which you want to enter override instructions.

2. Enter the override begin and end dates.

3. Enter the override value on the Values tab.

Defining Pay Group Overrides

This section provides an overview of pay group overrides and lists the page used to define pay group override.

Understanding Pay Group Overrides

To override the value of supporting elements that are associated with payees in a specific pay group, you use the Pay Groups - Supporting Elements Override page. This page is similar to the Pay Entities - Supporting Elements Override page, as are the processing rules.

Page Used to Define Pay Group Overrides

See Also

Overriding the Value of Elements That Are Associated with a Pay Entity

Defining Payee Overrides

This section provides an overview of payee overrides and processing rules for payee overrides, and discusses how to:

• Override component values, generation control, frequency, and variables for a payee.

• Override supporting element values for payees.

Understanding Payee Overrides

Payee overrides enable you to control how an entitlement or take element is resolved for a specific payee.

Using payee overrides, you can:

• Override variable elements used by a specific entitlement/take assigned to a payee.

• Override a variable for all elements that use the variable (not just one entitlement or take assigned to a payee).

• Override supporting elements associated with a payee.

Understanding Processing Rules for Payee Overrides

For payee overrides, the system looks at segment end dates (or period dates if there’s no segmentation) for a payee to determine if a supporting element override is used. The end date must be greater than or equal to the segment end date in order for it to be processed. Unlike pay entity and pay group, the system doesn’t look at the Definition as of Date.

Example: Segmentation and Payee Supporting Element Overrides

Two payees have the same override.

• Payee 1 has no segmentation.

• Payee 2 has segmentation. Segment 1 is January 1−15. Segment 2 is January 16−31.

• The pay period is January 1−31.

• VR1, a variable element, is defined as 50.

• VR1 has a payee-level override of 100 beginning on January 16.

For Payee 1, the value of VR1 is always 100, because there’s no segmentation.

For Payee 2, the value of VR1 is 50 for Segment 1 and 100 for Segment 2.

See Also

Payee Overrides and Segmentation

Page Used to Define Payee Overrides

Overriding Supporting Element Values for Payees

Use the Supporting Elements page to override the value of a bracket, date, duration, formula, or variable element that’s associated with a payee. Whenever the system resolves an element for the payee, it uses the override value that you select.

The Supporting Elements page is similar to the Pay Entities - Supporting Elements Override page, but the processing rules differ.

See Also

Defining Pay Entity Overrides

Defining Pay Calendar Overrides

When defining a calendar for an absence process, you can enter instructions for two types of overrides. You can:

• Specify any absence elements to exclude from processing for all payees.

  Enter these instructions on the Calendar - Excluded Elements page.

• Override the value of brackets, dates, duration, formulas, and variable elements on the Calendar - Overrides page.

  In this case, begin and end dates aren’t used, on the assumption that the override applies to the calendar period.

See Also

Defining Pay Entity Overrides

Overriding Supporting Elements for a Calendar

Entering Calendar Override Instructions for a Payee

Defining Overrides through Elements

The Update Via Element feature is used to control which elements can be updated by another element. You can update an element by means of another element in four places in the application:

• Arrays (through the Map Retrieved Fields to Variable Elements fields on the Array - Field Map and Keys page).

• Brackets (through the Return Column fields on the Bracket Search Keys/Return Columns page).

• Dates (through the Date Extract fields on the Date Extract page).

• Formulas (through the Assign To columns on the Formula - Field by Field Definition page).

Resolving Overrides in Batch Processing

This section discusses overrides in batch processing.

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