Element Segmentation with and without Accumulator Drivers

When an accumulator used as a driver is sliced, the system observes the following rules:

  • Slicing of a driver accumulator automatically causes slicing of the earning or deduction that it drives.

    If an earning or deduction with an accumulator driver is sliced, the driver value is applied to each slice of the earning/deduction. The driver can then cause multiple resolutions for each slice of that earning or deduction.

  • Earnings and deductions use accumulator occurrences with matching slice dates.

    If a match is not found, the system uses accumulator instances whose slice dates encompass the slice dates of the earning or deduction.

Example 1: Element Segmentation of Earnings and Deductions without Accumulator Drivers

An accumulator AC1 is included in an element segmentation event definition.

AC1 has these members: earnings E1, E2, and E3.

These earnings are automatically included in the segmentation event definition along with the accumulator.

AC1, E1, E2, and E3 are sliced when there is a segmentation trigger.

Assume a monthly pay period with a segmentation trigger defined for January 15.

E1 = 700, E2 = 1000, and E3 = 1500.

This table contains the earning/deduction results:

Earnings Instance Slice Number Slice Dates Amount

E1

1

1

January 1–14

350

E1

2

2

January 15–31

350

E2

1

1

January 1–14

500

E2

2

2

January 15–31

500

E3

1

1

January 1–14

750

E3

2

2

January 15–31

750

This table contains the accumulator results:

Accumulator Instance Number Slice Number Slice Dates Amounts

AC1

1

1

January 1–14

1600

AC1

2

2

January 15–31

1600

Example 2: Element Segmentation of Earnings and Deductions with Accumulator Drivers

An accumulator AC1 is included in an element segmentation event definition.

AC1 has these members: earnings E1, E2, and E3.

These earnings are automatically included in the segmentation event definition along with the accumulator.

AC1 is the driver accumulator for deduction D1.

Slicing of the driver accumulator AC1 automatically causes slicing of the deduction that it drives (D1).

STATE is the user key for AC1; STATE is also a user field for D1.

D1 is defined as Base x Percent (assume the percent is the same for each state).

Base = CURR_DRIVER_VAL and Percent = 15%.

Note:

CURR_DRIVER_VAL is a delivered system element that can be used to retrieve the current value of a driver accumulator if that accumulator is used in the calculation of an element. We discuss this and other system elements later in this topic.

See Using System Elements.

Assume a monthly pay period with a segmentation trigger defined for January 15.

E1 = 700, E2 = 1000, and E3 = 1500.

This table contains the earnings results:

Earnings Instance Slice Number Slice Dates Amount User Field

E1

1

1

January 1–14

175

State 1

E1

2

2

January 15–31

175

State 1

E1

3

1

January 1–14

175

State 2

E1

4

2

January 15–31

175

State 2

E2

1

1

January 1–14

250

State 1

E2

2

2

January 15–31

250

State 1

E2

3

1

January 1–14

250

State 2

E2

4

2

January 15–31

250

State 2

E3

1

1

January 1–14

375

State 1

E3

2

2

January 15–31

375

State 1

E3

3

1

January 1–14

375

State 2

E3

4

2

January 15–31

375

State 2

This table shows the accumulator results:

Accumulator Instance Number Slice Number Slice Dates Amounts User Field

AC1

1

1

January 1–14

800

State 1

AC1

2

2

January 15–31

800

State 1

AC1

3

1

January 1–14

800

State 2

AC1

4

2

January 15–31

800

State 2

This table shows the deduction results:

Deduction Instance Number Slice Number Slice Dates Amounts User Field

D1

1

1

January 1–14

120

State 1

D1

2

2

January 15–31

120

State 1

D1

3

1

January 1–14

120

State 2

D1

4

2

January 15–31

120

State 2