Understanding Calculation Elements

You use calculation elements to calculate such elements as formulas, takes, and entitlements.

This topic discusses:

  • Variables

  • Dates

  • Duration

  • Formulas

  • Rounding rules

  • Counts

  • Proration rules

  • Absence entitlements

  • Absence takes

  • Accumulators

  • Generation control

You use a variable element to define and store a value such as a character, date, or number. For example, assume that on January 1, you have three formulas and two elements that use a factor of 20 in their calculations, and that this factor is scheduled to change on April 1 to a factor of 25. Without a variable element, you would have to make five effective-dated changes. However, if you define this factor as a variable element, you make just one effective-dated change to the variable itself. You can then use the new factor of 25 anywhere that the variable is used.

Variables are the only items that are used with arrays. When you create an array, you retrieve the values into variables.

Using the date element, you can calculate a date by starting with an existing date and adding to or subtracting from it to come up with a new date. For example, to determine the date for a payee’s five years of service, start with the payee’s hire date and add five years to it.

You can also parse parts of a date. For example, if you want only the year of a date to be returned, use a date element to parse out the years, months, or days of the date.

Use a duration element to calculate the period of time between two dates. A duration is the result of subtracting one date from another. You define duration in years, months, or days.

For example, to determine a payee’s age, calculate the duration between the payee's birth date and the calendar period end date.

Use formulas to create your own unique elements. You can define sophisticated rules, mathematical formulas, and iterative calculations as formula elements.

For example, you can define a formula to calculate an employee’s vacation entitlement.

Use rounding rules to round other elements such as formulas or absence elements that resolve to a numerical value. A rounding rule resolves to 1, if rounding is successful, or 0, if rounding is not successful.

For example, let’s say that you define a rounding rule that truncates resolved values to two decimal places. During a calculation, you get a resolved value of 2.833333. The rounding rule truncates the value to 2.83.

You specify whether you want to round based on such factors as the number of digits or decimals, or round to an incremental value. You also select the type of rounding: Nearest, Round Up, Round Down, or Round Up if Greater Than or Equal To, Else Down.

Counts are a way to calculate and summarize something on a daily basis. For example, you might track the number of hours that a payee worked. A count element provides a day-by-day check of the hours worked and keeps adding to the work hours for a defined period of time.

Once you define the calculation rules for a count, you can associate it with a proration rule. When segmentation occurs, the count elements used in the proration rule determine the numerator and denominator to use for prorating amounts.

You can use a proration rule to prorate a value when segmentation occurs. A proration rule generally works in conjunction with segmentation.

A proration rule defines a numerator and a denominator to apply to an amount during segmentation. A proration rule defines the from and to dates for a count.

As an example, for a calculation period of June 1–30, with one segment from June 1 to June 10, you define the numerator as the time of the segmentation (June 1 to June 10) and the denominator as the time of the entire calculation period (June 1 to June 30). Therefore, you set up your formula as 10/30, and the proration rule resolves to .333 (10/30).

You use absence entitlement elements to track absences such as vacations or leaves of absence. There are two types of absence entitlements:

  • Per frequency

    The entitlement amount is calculated, regardless of whether there is an absence.

    As an example, say that payees receive 12 days of vacation per year and that this entitlement is accumulated at 10 hours per month. This entitlement is a fixed, predetermined amount that is calculated and updated monthly, regardless of whether it is used.

  • Per absence

    The entitlement amount is calculated only if there is an absence.

You use an absence-take element to define the conditions that must be met for an absence to be paid. An absence take involves defining rules for minimum and maximum absence takes. You set up absence takes to accumulate in hours, days, or other units.

For example, if your organization gives payees 12 days of vacation each year, and a payee goes on vacation for five days, the absence take for the payee is five days.

Once you’ve defined your absence take rules on the Absence Take pages, you can track absences by entering them on the Absence Event Entry page.

You use accumulator elements to store and track balances. You can store an accumulator for a designated period of time. For example, you can store absence entitlement balance data for one year. The system can create accumulators automatically (automatically generated accumulators) or you can create them manually (additional accumulators).

You can add or subtract elements with accumulator members and define begin and end dates.

There are two types of accumulators:

  • Segment accumulators, which accumulate values through segment calculation.

  • Balance accumulators, which accumulate values over a period of time, such as a month or a year.

You can also define the level at which you want to track a balance. For example, you can track a balance by payee record number, payee ID, department, or organization. You set up the tracking levels that work best for your organization.

You use a generation control element to determine whether an element should be resolved. To define a generation control element, you must specify the criteria that have to be met before the element is processed, based on such factors as HR Status, Action, Frequency, Segment Status, and Formula.