Defining Calculation Elements

This chapter provides an overview of calculation elements and discusses how to:

• Define duration elements.

• Define variable elements.

• Define date elements.

• Define formula elements.

• Define message elements.

• Define rounding rule elements.

• Define count elements.

• Define proration rules.

• Define generation control elements.

• Define generation control frequency elements.

Understanding Calculation Elements

Supporting elements are the building blocks of your system. Calculation elements, a subset of supporting elements, assist in the calculation process and are used to further refine the more complex elements.

This section discusses:

• Calculation element names.

• Element pointers.

Calculation Element Names

You must name every element and define its basic parameters on an Element Name page. All element page components share the same first Element Name page (GP_PIN).

See Also

Defining Element Names

Element Pointers

An element pointer is an element that points to another element by its system identifying number (PIN).

Once you define an element, its value may change. This presents a dilemma when you try to use elements to calculate other elements. The problem is especially evident when you are creating formulas. Element pointers help you alleviate this problem.

Advantages of Element Pointers

The following are advantages of using element pointers:

• You can use them in formulas to make formulas generic and reusable.

• Different earning, deduction, and absence calculations can use the same formula.

• When you define a formula, the values for the various elements that constitute the formula will likely change. Rather than referring to the element's value, you can refer to its system identifying number—its element number.

• Because you point to its element number—which remains constant—a formula using the element can remain useful over time because the element values will be valid.

Element Pointer Example

You have written a formula to calculate garnishments. But different payees have different garnishments. If you use element pointers in your formula expression to point to an element using its identifying element number, then you won't have to rewrite the formula every time the number and types of garnishments change for different payees. The formula will adapt its calculations because it is retrieving current values for the elements referenced by the element pointer.

Elements that can Use Element Pointers

Pointers can reference almost all elements that use the Definition page.

Use the following major elements to retrieve, store, and assign element pointers:

• Variables

• Brackets

  When using brackets, element pointers can store values that are returned by the lookup. Select a pointer for storing bracket values on the Search Keys/Return Column page.

• Formulas

• Arrays

  Use a pointer to tell the system that a column to be retrieved contains a PIN number. Use the Fields Retrieved page to enter instructions for retrieving columns for an array

See Also

Understanding Element Pointers in Formulas

Defining Duration Elements

To define duration elements, use the Durations (GP_DURATION) component.

This section provides overviews of duration elements and batch processing of duration elements, and discusses how to:

• Name durations.

• Define a duration element.

• Use HR status to include or exclude time.

Understanding Duration Elements

A duration element calculates the time between two dates, by subtracting one date from another. For example, age at Pay Period End Date is calculated as Pay Period End Date minus Birth Date. The resulting value is a duration.

Duration elements always resolve to a number. You can define durations in years, months, or days. If you define duration in days, you can include or exclude certain periods of time based on PeopleSoft Enterprise Human Resources status codes. You can also include or exclude absence days that have been entered in Global Payroll.

Including or Excluding Absences

The typical use for the include or exclude absences feature is to exclude absence days from a duration. For example, you are calculating a service duration, but you do not want to include sick days. The daily absence formula will be resolved for each day absent between the begin and end dates of the duration. This formula returns a one for each paid sick day; for all others it returns a zero. The duration program will sum up each day's value. If the payee had 15 sick days within this time period and the Include Absence Days check box is cleared, then 15 will be subtracted from the total number of calendar days in the period.

Your formula can call any of the system elements that are designed specifically for absence duration. These elements have the same names as those that are used to generate the absence daily data, but they end with the suffix DU. For example, you can use the system element, ABS END DATE DU, to retrieve an absence end date for a particular absence.

Example 1: Rounding

On the Duration - Definition page, you can define whether the duration is a decimal and how to round the duration. This section provides an example of how rounding works for decimal durations.

The result (before rounding) is 2 years, 5 months, and 20 days and you want the result in months, without rounding. The result is:

(2 Years * 12) + 5 Months = 29 Months + 20/30 = 29.666667

If the Return Duration With Decimals check box is cleared, the value is 29.

If you select the Return Duration With Decimals check box and Add 1 Month if Days, with a value of 15, the result is:

(2 Years * 12) + 5 Months + 1 Month (because days are > 15) = 30

The small difference in the results can be significant when the duration resolution is used throughout the system.

Example 2: Rounding

In this example, assume that:

The Duration From date is January 1, 1999 and the Duration To date is January 31, 2001.

This table illustrates how various options, used together, affect the value returned by a duration element (the system's standard field size is 12.6, so all values are shown to the full six decimal places):

Including/Excluding HR Status Days

Using the Set Daily HR Status Criteria page you can include or exclude time periods from the duration calculation, based on Human Resources status codes.

If status Include or Exclude criteria are defined as part of the duration definition:

• The Date From date cannot be earlier than the first effective-dated PS_JOB row.

  If the Date From date is before the first effective-dated PS_JOB row, the duration calculation uses the earliest effective-dated PS_JOB row for this EmplID/Empl_Rcd combination as the default Date From date. The duration calculation doesn’t limit the Date From date based on other fields.

• The Date To date cannot be after the Calendar Period End Date.

  If the Date To date is after the Period End Date, the duration calculation uses the Period End Date as the default Date To date.

• Only the maximum effective sequence PS_JOB row is considered, because any nonmaximum effective sequence PS_JOB rows mean nothing from a status perspective.

• No warnings or errors are issued if the Date From or Date To dates are modified to be the effective date of the first PS_JOB row or the Period End Date in the above situations.

For example, if the first effective date PS_JOB row is January 7, 1995 but the Date From date is January 1, 1995, the system uses January 7, 1995 because the Date From date cannot be less than the first PS_JOB effective date.

Note. Payment keys are ignored in Status Control Include or Exclude calculations.

Example 1: Including/Excluding HR Status Days

For this example, assume the following:

Date From: January 1, 2000

Date To: January 31, 2000

Unit of measure: Days

Include From and To Date: Selected

Payee Status: Leave effective January 22, 2000

Days Active: 21 Days, Inactive: 10, Result of absence formula: 5

This table shows how the system resolves the duration value, based on various Include/Exclude options:

Example 2: Including/Excluding HR Status Days

Assume that a duration is set up as follows:

• Date From: June 23, 1999.

• Date To: September 23, 1999.

A subperiod is defined as follows:

• Include if status is Active.

• Subperiod > 5 days.

This table lists a payee's PS_JOB rows:

The duration resolves to eight days (first Active) plus nine days (second Active), meaning a value of 17 days. Both Active periods are included because they are both greater than five days.

Note. Payment keys and fields besides Employee Status aren’t considered during the Status inclusion/exclusion calculations.

Only PS_JOB rows that are less than or equal to the period end date are considered. The Date From or Date To dates can be modified to be the effective date of the first PS_JOB row, or the Period End Date, because of the system rule that the Date From date cannot be before the first PS_JOB effective date.

See Also

PeopleSoft Enterprise Human Resources 8.9 PeopleBook: Administer Workforce

Daily Data

Understanding Batch Processing of Duration Elements

The duration module resolves a duration element by:

1. Resolving Date From and Date To, if needed.

2. If there are status entries, validating that the first PS_JOB row isn’t less than the Date From and that Date To isn’t after the period end date.

3. Calculating the duration period (years, months, or days) between Date From and Date To.

4. If there are Human Resource status entries, processing them.

5. Including or excluding absence days, if applicable.

6. Applying rounding.

7. Truncating decimals if Return Duration With Decimals isn’t selected.

If you’ve indicated on the Duration - Definition page that the value should be returned in years and you’ve selected both the Add 1 Year if Months >= and Add 1 Month if Days >= options, the system evaluates the Add 1 Month if Days >= option and then evaluates and applies the Add 1 Year if Months >= option.

Pages Used to Define Duration Elements

Naming Durations

Access the Duration Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining a Duration Element

Access the Durations - Definition page.

Date From Type and Date To Type	Select the type of element that returns the Date From and Date To days. Valid values are: Bracket, Cal Date (calendar date), Date, Formula, System Elem (system element), and Variable.
Date From and Date To	Define the first and last day that the system is to include in the duration calculation. Select the names of the elements that return the dates. If the Date From date is the same as or greater than the Date To date, the duration element resolves to zero.

Define Return Value

Use the fields in the Define Return Value group box to:

• Select a unit of measure for the duration calculation.

• Apply rounding rules to the duration results.

• Include/exclude absence days from a duration.

• Include/exclude days from a duration based on HR status codes (Human Resources status codes).

• Retrieve duration results in decimal form.

Select a Unit of Measure

Use the following fields to select a unit of measure for the returned duration value:

Apply Rounding

Use the following check boxes to apply rounding rules to the result of your duration calculation. If you do not select a check box, no rounding occurs.

If you select either of these check boxes, and the months or days value is greater than the value that you enter, the calculation adds one year or one month, respectively.

For example, if Return Duration in is Years, and you select Add 1 Year if Months >= and enter 6, the system returns a duration of 3 years and 6 months as a value of 4 years.

Note. The system applies the selected rounding rule before converting durations to decimals. If you select the Return Duration With Decimals check box and a rounding option, the system rounds up the months or years, as applicable, leaving no decimal value.

Include/Exclude Absence Days

Leave the Include Absence Days check box cleared to exclude days. For example, if you leave this check box cleared, you can calculate a duration of time minus sick days.

Select the Include Absence Days check box to include absence days in the duration calculation.

This check box becomes available when you select Days as your unit of measure.

Note. The system automatically excludes absences if you do not select Include Absence Days and specify a daily absence formula.

Set Daily HR Status Criteria

The Set Daily HR Status Criteria link is available only when you calculate duration in days.

If you enter instructions to include daily absence data and include or exclude days based on status codes, the system performs two separate counts and combines the results. For example, if you include active days (based on HR status) and exclude absence days, the system counts the number of days the payee was active and subtracts the number of days the payee was absent.

Warning! Double counting can occur, depending on the instructions that you enter in the two group boxes. For example, if you include active days and days a payee is out sick, the days on which a payee is both active and sick are counted twice.

Return Duration with Decimals

If you select Return Duration With Decimals, the system converts durations to decimals after applying any rounding rules you may have defined.

Using HR Status to Include or Exclude Time

Access the Set Daily HR Status Criteria page.

If the unit of measure on the Durations - Definition page is set to Days, you can include or exclude time periods from the duration based on Human Resources status codes. You can also specify minimum and maximum periods to check against.

The code combinations that you enter are, as a group, either included or excluded, meaning that when you include specific status codes, those that you omit are automatically excluded. If you exclude certain codes, those that you don’t exclude are automatically included.

The time period indicated includes the PS_JOB Effective Date.

Additional Period Definitions

Use the following fields to further define the periods that you want to include or exclude from the duration.

Defining Variable Elements

To define variable elements, use the Variables (GP_VARIABLE) and Variables by Category (GP_VARIABLE_BY_CAT) components.

This section provides overviews of variable elements, field formats, and batch processing of variables, and discusses how to:

• Name variables.

• Define a variable.

Understanding Variable Elements

Variables are a means of storing a value and using it later. In situations requiring you to input a value—whether in a formula, in a calculation component, or elsewhere—the system enables you to identify the input as a variable and use the same value repeatedly. Using variables, you can define this value and invoke it anywhere in your formulas and calculations.

Example

On January 1, the batch process resolves three formulas and two earnings using a monetary factor of 20 in their calculations. This factor changes to 25 on April 1. If you assign this factor a format type of numeric, you have to make five effective-dated changes, but if you define this factor as a variable element, you have to make only one effective-dated change for the new factor, 25, to be used anywhere the variable is referenced.

Understanding Field Formats

Variables can be defined with any one of the following field formats:

• Character

  The field length for variables with a character field format is 30 spaces.

• Date

• Decimal

  The field length for variables with a decimal field format is 12.6.

• Monetary

  The field length for variables with a monetary field format is 12.6.

• Pointer

  Variables can be defined with the Element Pointer field format, which enables you to link a variable element to another element. This concept is useful when you use variable elements as components of a formula element to make the formula more generic and applicable to changing situations.

  An element pointer is a means of storing the element number of another element, not the element’s actual value. When you use the element pointer variable, the process uses the value of the element pointed to by the element pointer.

Note. When you assign a value to a variable either directly or by means of another element (for example, an array), consider whether the variable can support the assigned value in terms of field length and field format. For example, 50 characters of text should not be assigned to a character variable with a field length of 30 spaces. Similarly, a monetary value should not be assigned to a variable with a character format.

See Also

Understanding Element Pointers in Formulas

Understanding Batch Processing of Variables

Being data input elements, variables are resolved as they are encountered during batch processing. The resolution of the value equals the value you put in the definition.

If you’ve selected the Store check box on the Variable Name page, all resolutions of the variable are stored.

Pages Used to Define Variable Elements

Naming Variables

Access the Variable Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining a Variable

Access the Variables - Definition page.

Value	Enter the value to assign to this variable. The type of value that you assign depends on the format type that you designated on the Variable Name page.
Use As Chart Field and Prompt View	Select the Use As Chart Field check box to use the variable element as a ChartField. ChartFields are used by PeopleSoft Enterprise General Ledger. In the Prompt View field, select the record with which you want to associate this variable. The name of the record appears as a column heading on the GL Mapping page

See Also

Integrating Global Payroll with General Ledger

Defining Date Elements

To define date elements, use the Dates (GP_DATE) component.

Use a date element to include a date in a calculation or determine a new date by taking a starting date and adding or subtracting a period of time to get another date.

Note. Date elements are used for defining specific dates. If you need to subtract one date from another and determine the intervening duration, use a duration element, not a date element.

This section discusses how to:

• Name dates.

• Define a date or calculate a new date based on an existing date.

• Assign unique element identifiers.

See Also

Defining Duration Elements

Pages Used to Define Date Elements

Naming Dates

Access the Date Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining a Date or Calculating a New Date Based on an Existing Date

Access the Dates - Definition page.

Provide Date	Select to provide the date, and specify the entry type of the element containing the date in the Date From Type field. Define the date or date element in the Date From or Date From Element field. The Date From field appears when you select Cal Date in the Date From Type field.
Build Date	Select to have the system build the date, based on elements that you select. When you select Build Date, the Year Entry Type, Month Entry Type, and Day Entry Type fields become available. Use these fields to define the entry type of the elements containing the month, day, or year. Identify the date elements in the fields to the right.
Return Last Day of the Month	Select to have the system return the last day of the month as a value. You can use this check box with both the Provide Date and Build Date options. Selecting this check box will override the provided or built date by moving the last day of the month into the day portion of the date.

Parameters to Modify Built Date (Optional - Default None)

Examples

This table illustrates what date values result from various page selections:

Assigning Unique Element Identifiers

Access the Extract page.

Year Element, Month Element, and Day Element

Select the variable to extract the year, month, and day, as applicable. For example, say that you want to capture the year that your date element resolves to. You create a variable called YEAR and select it in the Year Element field. Now, say that the date element resolves to January 10, 2008. The system stores the value, 2008, in the YEAR variable.

The YEAR variable can then be used in another date formula to build a new date.

Defining Formula Elements

To define formula elements, use the Formulas (GP_FORMULA) component.

This section provides an overview of element pointers in formulas and discusses how to:

• Name formulas.

• Define formulas for use in calculations.

• Assign a rounding rule and element pointer selections.

• View formulas.

Understanding Element Pointers in Formulas

When you define a formula, the values of the elements that comprise it are likely to change. If you refer to an element's specific value at a given time, you have to change the formula every time a component element value changes. Rather than referring to the element's value, you can use an element pointer to refer to its system identifying number—its element number. When you do this, you are telling the system that during processing, it should return whatever value is stored in the element’s array. Because the element number remains constant, a formula using the element remains useful indefinitely, because the element values are valid.

During batch processing, any variable defined with a Pointer field format has a value stored in the Element Pointer field in the PINV array. That is, only the element number is stored and the variable element isn’t resolved to an actual character, numeric, or date value.

If the field format for the variable element used in a formula isn’t equal to Pointer and you select the Use Element Value option on the Element Name Attributes page, the formula uses the element's value.

If the field format for the variable element used in a formula isn’t equal to Pointer and you select the Use Element Number option on the Element Name Attributes page, the formula uses the element's number.

If the field format for the variable element used in a formula is equal to Pointer and you select the Use Element Value option on the Element Name Attributes page, the formula uses the value of the element to which the pointer element is pointing.

If the field format for the variable element in a formula equals Pointer and you select the Use Element Number option on the Element Name Attributes page, the formula uses the value of the pointer element. In other words, it uses the element number, because that’s what elements with a field format equal to Pointer store.

This table summarizes which values are used with different configurations:

Example 1

You’ve written a formula to calculate garnishments, but different payees have different garnishments. If you use element pointers in your formula expression to point to an element using its element number, you won't have to rewrite the formula whenever the number and types of garnishments change for different payees. The formula adapts its calculations, because it’s retrieving current values for the elements referenced by the element pointer.

Example 2

Say that before a certain formula is used, the values for the elements are as follows:

You've selected the Use Element Value option on the Element Name Attributes page.

If an element's field format isn’t Pointer, the formula uses the value of the element. So, if you’re using the following statement in your formula:

V1 Assign to V3

then, after the resolution of the formula, V3 equals 150.

If an element's field format is Pointer, the formula uses the value of the element pointed to by the pointer. So, if you’re using the following statement in your formula:

V4 Assign to V3

then, after the resolution of the formula, V3 equals 150.

If you want to use V4 in your formula, the formula checks whether the Use Element Value or Use Element Number option is selected. In this example, it's Use Element Value. The formula then checks whether the field format is Pointer In this example, it’s Pointer. The pointer value is 1000. Because 1000 is an element number and this element number represents V1, the formula uses the value of V1 (150).

Assume also that you've selected the Use Element Number option on the Element Name Attributes page.

If the field formats for Element Name 1 and Element Name 2 aren't Pointer, the formula uses the element number. So, if you’re using the following statement in your formula:

V2 Assign to V4

and you're using pointers, then, after resolution of the formula, V4 contains 2000 in the pointer value.

If the field formats for Element Name 1 and Element Name 2 are Pointer, the formula uses the pointer value. So, if you’re using the following statement in your formula:

If V4 = 2000

then the condition is true, because the pointer value of V4 equals 2000.

If you want to use V2 in your formula, the formula checks whether the Use Element Value or the Use Element Number option is selected. In this example, it's Use Element Number. The formula then checks whether the field format is a Pointer. In this example, it isn’t. This directs the formula to use the element number of V2, whose element number is 2000. So, 2000 will be assigned to the pointer value of V4.

Note. If you’re using the element number V2, the Assign To element must be in Pointer field format and the Use Element Number option must be selected on the Element Name Attributes page for Element Name 1, Element Name 2, and Element Name 3.

See Also

Understanding Field Formats

Defining Variable Elements

Pages Used to Define Formula Elements

Naming Formulas

Access the Formula Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining Formulas for Use in Calculations

Access the Field-by-Field Definition page.

Building Your Formula

Build your formula in the Field-by-Field Area group box, specifying one operation or result in each row.

Note. Under either parenthesis, you can enter multiple sets of parentheses. To do so, use multiple lines. You can enter only one ( or ) per row.

Validating Your Formula

After you define your formula, save it, then validate and edit the formula. Whenever you alter the formula, revalidate it.

Note. If you try to run a process using a formula that you’ve changed without validating, you get an error. Save the page before clicking the Validate button. You can save the page anytime, but no validation against the database occurs until you click the Validate button. Clicking the Validate button validates and saves the formula.

Example: Setting Up a Formula

Using the formula element, you can create elements using mathematical and logical operands, rules, and mathematical formulas.

In this example, you need a simple formula to calculate a pension deduction. The requirements are as follows:

• If basic earnings are less than 10,000, the pension deduction is one percent of basic earnings.

• If basic earnings are greater than or equal to 10,000, the pension deduction is one percent of the first 10,000 and two percent of the remainder.

The system uses basic earnings for all calculations. The formula should resolve to the amount of the deduction.

Start by turning the calculation into a mathematical formula.

If basic comp < 10,000, then
  pension = basic comp * .10,
else
    pension = (10,000 * .01) + ((basic comp - 10,000) * .02)
Endif

Formulas can often be expressed in multiple ways. To streamline processing, use the simplest version that requires the least processing.

After turning the calculation into a mathematical formula, you enter the formula into the system. If you haven’t defined the element and entered the basic descriptions, do so on the Formula Name page. Then, on the Field-by-Field Definition page, define the formula, line by line.

This table shows how you enter your pension formula:

Note. Every If statement must end with an Endif.

Each element name must be associated with an appropriate entry type. For example, on the first line, Element Name 1 (BASE COMP1) is associated with the entry type System Element. Element Name 2 (10,000) is associated with the entry type Numeric.

You can view your formula by accessing the Text Definition page. When you have defined the formula, validate it by clicking the Validate button on the Field-by-Field Definition page.

See Also

Understanding Element Pointers in Formulas

Assigning Rounding Rules and Element Pointer Selections

Access the Element Name Attributes page.

Rounding Rule Element

If the field format of the element that you selected on the Formula Name page is Monetary, Decimal, or Pointer, select a rounding rule from the list. If the field format isn’t Monetary, Decimal, or Pointer and you select a rounding rule on this page, you receive an error message indicating that rounding rules do no apply to the element. In this situation, you must remove the rounding rule before you can leave the page. The rounding rule applies only to the operand for which you’ve entered it. The element itself isn’t updated; only the calculation is affected.

Element Pointer Selection

Use these fields to define element pointers in your formula.

Old Value Selection

Viewing Formulas

Access the Text Definition page.

Use the Text Definition page to view the formula that you created on the Formula - Definitions page. If something isn’t correct, return to the Field-by-Field Definition page and adjust the formula.

Defining Message Elements

Message elements are closely related to formula elements. To fully understand message elements, read the section on formulas before reading this section.

This section discusses how to define message elements.

Note. No online pages specifically define message elements, because they are provided in system data.

By referencing the message element in a formula, you can manage the error messages that are created during batch processing. A message element calls a program that writes an error message into the error message table (PS_GP_MESSAGES) and then, optionally, puts the payment in error.

Many of the fields in the PS_GP_MESSAGES table are system-populated. Others are populated during batch processing. By using these field values as components of a formula, you can create your own message and error conditions during batch processing.

To populate fields that aren’t system-populated, these components and processes are provided:

• Five system elements (MSG_BIND1_PTR … MSG_BIND5_PTR), with the Pointer field format.

  These pointers point to the parameters that you’re using in your error messages.

• Five numeric system elements (MSG_BIND1_NM_IND … MSG_BIND5_NM_IND).

  If the value of MSG_BINDx_NM_IND equals zero, the system displays on the Payee Messages page the element name to which the MSG_BINDx_PTR element points. Otherwise it displays the value of the element that is pointed to by MSG_BINDx_PTR.

• Numeric system elements for the message number (MSG_NBR) and MSG_SET_NBR.

• A numeric system element (MSG_PAYMENT_ERR) that can put the calculation in error.

  If the value of this system element doesn’t equal 0, the calculation is in error.

• An error message element type.

  This element type has only one element in the GP_PIN_NM table (MESSAGE). The field format is Decimal. The Re-calc (recalculation) check box must be cleared. This entry type is available only on the Field-by-Field Definition page and for Element Name 1 and Element Name 2. When the batch process encounters this message (formula) element, it inserts a row in the PS_GP_MESSAGES table for the message ID and parameters specified. If there’s no error, the MESSAGE element equals zero. If there’s an error, the MESSAGE element equals one. The primary purpose of this element type is to enable the batch process to recognize that a user error needs invoking. The batch process doesn’t look at its value.

Every system element that is related to an error message is reset to blank or zero.

Note. You can create your own error messages only by using formula elements.

Example

This table gives an example of a formula element setup (a portion of an entire formula expression):

This table provides explanations of the formula described in the previous table:

Note. An indicator tells the system whether a number value is an element number so that the formula message program knows whether to leave that value alone or retrieve that element’s value. Leaving that value alone means that the element name is displayed on the online message page.

See Also

Defining Formula Elements

Defining Rounding Rule Elements

To define rounding rule elements, use the Rounding Rules (GP_ROUNDING) component.

This section provides an overview of rounding rule elements and discusses how to:

• Name rounding rule elements.

• Define how numeric values are rounded.

Understanding Rounding Rule Elements

When performing calculations that resolve to a numeric value, the value may need rounding. The rounded value is what gets stored or used in further calculations. Rounding is a tool that enables you to systematically change values according to predefined rules.

Once you’ve defined your rounding rule elements, you can apply them to other elements throughout the system to determine how rounding will occur.

Note. Many rounding rules apply to specific features of the system. They are explained in the section of this PeopleBook that discusses those features. The text here describes only the generic functionality of the rounding rules element.

Examples of Size Rounding

This table provides examples of how the rounding rules work if you select Rounding on the Rounding - Definition page:

Examples of Incremental Rounding

This table provides examples of how the rounding rules work if you select the Increment on the Rounding - Definition page:

Pages Used to Define Rounding Rule Elements

Naming Rounding Rules

Access the Rounding Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining How Numeric Values Are Rounded

Access the Rounding Rules - Definition page.

Rounding	Select to use traditional rounding rules.
Increment	Select to set rounding increments. When you select this option, the Increment field appears, where you define the incremental value.
Round Size	This field appears when you select the Rounding option. Specify a round size from the list. Values are 01 through 11, or 0 to 5 decimal places. The example fields on the bottom right half of the page enable you to view examples of each type of rounding.
Round Up if >= Else Down	Select to round up if the result is greater than or equal to the value you enter in the Round Adjustment field, based on the number of digits or decimal places entered. If the result doesn’t exceed or equal the value, the result is rounded down. The default value is 5 for rounding. If you select the Rounding option, you can enter only one digit in the Round Adjustment field. If you select the Increment option, you can enter a value of up to eight digits. This digit looks at the decimal place to the right of what is being rounded. For example, if you’re rounding to the tens (one decimal place), it looks to the hundreds field.
Up	Select to round up, based on the number of digits or decimal places entered. It rounds up if the value to the right of the digits or decimal places specified is greater than zero. The system looks at all the remaining digits or decimal places, not just the next digit.
Truncate/Down	Select to truncate (round down), based on the number of digits or decimal places entered. All digits or decimal places to the right of the number specified are changed to zero, and the rest are truncated.
Rounding Sample	Enter a value to see how the system would round the amount based on your page selections.

Defining Count Elements

To define count elements, use the Counts (GP_COUNT) component.

This section provides an overview of count elements and discusses how to define count elements.

Understanding Count Elements

You might need a process for counting the number of scheduled work days or hours from a specific period of time. For this purpose, you use count elements, which are primarily for proration calculations but can be used in other situations.

When you define a count element, you reference a formula that you’ve defined as the counting formula. That is, you define a formula that counts the number of scheduled work days or hours; then you reference that formula on the Counts - Definition page so that the system knows that it should process the referenced formula as a counting formula.

The count element refers to the work schedule that is associated with each payee to count the correct workdays. When the system finishes checking each day’s work schedule, counting the number of days or hours for the subperiods, either segments or slices.

The formula is resolved for each day in the work schedule within a date range. Set up the formula to return the number of units for each day. The count program will cumulate the formula results. If the count element is called from the proration element, the counting period is set by the proration element. If the count formula is not called from a proration element, the counting period is the segment.

An example of a simple count formula is GP COUNT WORK DAYS:

If SCHED HRS>0 Then
GP TRUE => GP COUNT WORK DAYS
Else
GP FALSE => GP COUNT WORK DAYS
Endif

See Also

Defining Proration Rules

Defining Formula Elements

Understanding Work Schedules

Defining Segmentation

Pages Used to Define Count Elements

See Also

Defining Formula Elements

Naming a Count Element

Access the Count Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining Counts

Access the Counts - Definition page.

Count Formula

Enter the name of the formula that performs the count.

Defining Proration Rules

To define proration rules, use the Proration Rules (GP_PRORATION) component.

This section provides an overview of proration rules and discusses how to define numerators and denominators.

Understanding Proration Rules

A proration rule can be triggered by segmentation or with the system element, PRORATE. You define what values to use as the numerator and denominator of a proration rule. When the system applies a proration rule, it multiples the amount by the numerator, and divides the result by the denominator.

You can use a proration rule in the definition of an earnings, deduction, or absence entitlement (frequency-based). Proration applies only to an element’s amount, base, or unit components. You can assign a default proration rule on the Pay Group - Defaults page.

When defining an earning, deduction, or frequency-based absence entitlement element, you have three choices for proration:

• Use no proration, regardless of segmentation.

• Use the paygroup proration rule.

• Specify a unique proration rule.

Denominator Schedule Example

The Denominator Schedule group box on the Proration - Definition page enables you to select which work schedules to include in the denominator calculation. Assume that a payee has two work schedules:

• Work Schedule A, 5 days a week.

• Work Schedule B, 3 days a week.

Also assume that February has exactly 4 weeks and that the proration rule is defined to use the number of workdays, then:

• If the payee has only Work Schedule A, the denominator is 20 (5 days × 4 weeks).

• If the payee has only Work Schedule B, the denominator is 12 (3 days × 4 weeks).

• If the payee has Work Schedule A for the first 2 weeks and Work Schedule B for the second 2 weeks, you can tell the system to use a denominator of:

  • 12 (3 × 4), if you’re using the work schedule as of the end of the period.

  • 16 ((5 × 2) + (3 × 2)), if you’re using both (all) work schedules.

Note. When you define a proration element, the Always Recalculate check box on the Proration Name page is automatically selected. This is to ensure that the system correctly calculates the proration factor when there is element segmentation.

Pages Used to Define Proration Rules

Naming Proration Elements

Access the Proration Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining Numerators and Denominators

Access the Proration - Definition page.

Numerator Entry Type, Denominator Entry Type, Numerator Element, and Denominator Element

Select the types of elements that define the numerator (slice period) and the denominator (the full pay period). Values are Accumulatr (accumulator), Count, Formula, Duration, and Variable. Enter the element name in the Numerator Element or Denominator Element field to the right. Counts are perhaps the most common element type used to define proration rules. For example, you can define count elements to count the number of scheduled work days or hours in a pay period. When a payee has segmentation, the system resolves the count element for the slice period (or segment if no slices) and uses that value as the numerator; the system resolves the count element for the entire period and uses that value as the denominator. If you want to count calendar days you should use a duration element. You could use a count element (returning a one per day), but a duration element results in better performance. For the numerator, calculate the calendar duration between the slice begin and slice end dates. For the denominator, use a duration element that calculates the calendar days between the period begin and period end dates. You might use a variable if you aren’t concerned with the number of days in a calendar period and prefer a static value. For example, in a monthly pay cycle, the number of calendar days in the period fluctuates every month but you may want to ignore this fluctuation. You can create a variable with a value of 30.00 and use it as the denominator.

Denominator Schedule

Use these fields to select which work schedules to include in the denominator calculation.

Defining Generation Control Elements

To define generation control elements, use the Generation Control (GP_GCTL_CONDITION) component.

This section provides an overview of generation control elements and discusses how to:

• Define the criteria for certain element conditions in batch processing.

• Include or exclude employee status conditions.

• Include or exclude action/reason code combinations.

• Include or exclude frequency codes.

• Include or exclude segment status conditions.

• Include or exclude formula elements.

• Include or exclude run types.

Understanding Generation Control Elements

In the basic processing of an element, the system assumes that the element is to be processed whenever a payee is processed. But sometimes you don’t want an element processed every time for every payee.

Generation control provides a type of filtering that enables you to control whether an element for a payee is processed during batch processing. Using generation control elements, you can tell the system whether to process an element based on predefined criteria.

The following six parameters are used to define generation control elements:

• HR Status

• HR Action/Reason

• Segment Status

• Frequency

• Formula

• Run Types

For each control parameter, you specify whether the entries exclude or include the element during batch processing. If you include the element, only payees that match on the selected values have the element processed. All other values are excluded. If you exclude the element, the element isn’t processed for payees that match on the selected value or values. All other values are included.

HR Status Example 1

You want to include for processing all payees whose HR status is Active, so you create a generation control element that includes all payees with this status. You then associate this generation control element with the elements that you want to control. So, in batch processing, only payees with an Active HR status have these elements processed. All payees with a different HR status, such as Inactive or Terminated, don’t have the element processed.

HR Status Example 2

This table lists the PS_JOB rows for a payee:

This table shows how elements E1 and E2 have the following generation control conditions applied to them with the HR Status page controls:

E1 isn’t processed, because the last Job row isn’t Leave of Absence. E2 is processed, because the Job row with Leave of Absence is in the segment.

HR Action/Reason Example (Without Segmentation)

This table lists a payee's PS_JOB row:

This table shows how element E1 has the following generation control conditions applied to it with the HR Action/Reason page controls:

If you’re processing January 1, 1999 through January 31, 1999, E1 isn’t processed, because the PS_JOB row doesn’t have an effective date in the segment.

HR Action/Reason Example (With Segmentation)

This table lists a payee's PS_JOB rows:

This table shows how element E1 has the following generation control conditions applied to it with the HR Action/Reason page controls:

For the January 1999 pay period, this payee has two segments: Segment 1 (January 1, 1999 through January 15, 1999) and Segment 2 (January 16, 1999 through January 31, 1999).

E1 is processed in Segment 1, because the effective date falls within the segment's date parameters. E1 isn’t processed in Segment 2, because the effective date doesn’t fall within these parameters.

HR Action/Reason Example (With Last Day Worked)

In this example, assume that you want a certain earnings to be paid to a payee upon termination. This table shows how elements E1 and E2 have the following generation control conditions applied to them on the HR Action/Reason page:

Assume the following:

Pay period is January 1, 2001 − January 31, 2001.

Payee’s last day of work is January 31, 2001.

Accordingly, a job row is inserted with an effective date of February 1, 2001 (which is the first day the person is terminated, or not active) with an Action of Termination.

E1 is processed because the system looks at the Last Day Worked (on the Employment record) to see if the action is within the period.

E2 is not processed in January because the effective date is February 1, 2001. If the payee is paid in February for some reason, E2 would be processed.

Note. The Generation Control HR Action/Reason page considers all PS_JOB rows for a given segment. The PS_JOB row must have an effective date in the segment.

Frequency Code Example

You have a weekly pay period and want to apply a particular deduction, only to the first pay period of the month. But you want to use the same process list for all four weekly runs during the month. To avoid having to create a new process list just to accommodate your needs for the first pay period, you can use the frequency generation control feature to define a frequency with a First of the Month value. In this way, you can use the same process list for all four pay periods and confine the particular deduction processing to the first pay period.

Understanding Batch Processing of Generation Control Elements

The Generation Control program is called from the Deduction, Earnings, and Absence Entitlement programs. The calling programs pass the Generation Control element to be resolved. The PIN Manager acts as the central program controlling the process.

Pages Used to Define Generation Control Elements

Naming Generation Control Elements

Access the Generation Control Name page.

You name every element and define its basic parameters on an Element Name page. All element components in Global Payroll share the same Element Name page (GP_PIN).

See Also

Defining Element Names

Defining Criteria for Certain Element Conditions in Batch Processing

Access the Generation Control - Conditions page.

HR Status (human resources status)	Click this link to access the HR Status page. Indicate which employee status conditions to process.
Action/Reason	Click this link to access the HR Action/Reason page. Indicate which Action/Reason code combinations to process.
Frequency	Click this link to access the Generation Control - Frequency page. Indicate which frequencies to process.
Segment Status	Click this link to access the Segment Status page. Indicate which segment status conditions to process.
Formula	Click this link to access the Generation Control - Formula page. Indicate which formulas to process.
Run Type	Click this link to access the Generation Control - Run Type page. Indicate which run types to process.

Important! When more than one generation control parameter type (such as HR status and frequency) is entered, the payee must meet both criteria to pass generation control. When more than one value (such as Actions of Hire or Rehire) for a particular generation control type is entered, the payee must meet only one of the criteria to pass generation control.

Including or Excluding Employee Status Conditions

Access the HR Status page.

Include and Exclude	Select the option to include or exclude the employee status conditions that you enter in the group box below.
All Job Records in Segment	Select to tell the system to look at all job rows in the segment. If any row contains the value indicated in the Employee Status field, it’s considered a match.
Last Job Record	Select to tell the system to look only at the maximum effective-dated PS_JOB row for the match, within the period in question.
Employee Status	Select a status code from the list.

Including or Excluding Action/Reason Code Combinations

Access the HR Action/Reason page.

Include and Exclude	Select the option to include or exclude the action/reason code combinations that you insert in the group box below.
Use Last Day Worked	Select to use the last day worked.
Action and Reason	Select from the list of HR Action codes.

Note. If an action is entered with no reason, the system assumes that all reasons are valid.

Including or Excluding Frequency Codes

Access the Generation Control - Frequency page.

Include and Exclude	Select the option to include or exclude the frequency codes that you insert into the group box below.
Frequency	Select from the list of codes.

Including or Excluding Segment Status Conditions

Access the Segment Status page.

Include and Exclude	Select the option to include or exclude the segment status conditions that you insert in the group box below.
Segment Status	Select from the list of conditions.

Including or Excluding Formula Elements

Access the Generation Control - Formula page.

Include and Exclude	Select the option to include or exclude the formula elements that you insert into the group box below.
Formula Name	Select from the list of elements.

Including or Excluding Run Types

Access the Generation Control - Run Type page.

Include and Exclude	Select the option to include or exclude the run type that you insert in the group box below.
Run Type	Select from the list of run types.

Defining Generation Control Frequency

To define generation control frequency, use the Generation Control Frequencies (GP_GCTL_FREQUENCY) component.

This section provides an overview of generation control frequency and discusses how to define a generation control frequency.

Understanding Generation Control Frequency

The frequency tag element is used to define an intermediary table so that the system can associate a Human Resources frequency (residing in the Human Resources Frequency Table) with a Global Payroll frequency. There are many frequencies that you use infrequently, and this feature enables you to define them through a table in Global Payroll rather than through the Human Resources Frequency Table.

Through use of the frequency tag, generation control is also related to how the system annualizes and deannualizes elements.

When you aren’t using generation control, the numerator for annualization is the element's frequency and the denominator is the calendar period frequency. When you are using generation control, the numerator for annualization is still the element's frequency but the denominator is the generation control frequency.

Page Used to Define Generation Control Frequency

Defining a Generation Control Frequency

Access the Generation Control Frequency page.

Frequency

Select from the list of available values (Annual, Biweekly, Contract, Daily, and so on.) The values in this field come from FREQUENCY_TBL.