Filling Out User Field Sets When There is Element Segmentation
When an earning/deduction undergoes element segmentation, the user field set is determined per slice.
Depending on whether user field values come from an element assignment, a positive input entry, or a driver accumulator, the system assigns the correct values as follows:
-
When User Field Values Come From an Element Assignment: An element assignment typically applies to all slices within a segment, and the user field values associated with the assignment also apply across all of the slices in that segment. However, if you set up your system to trigger element segmentation based on the begin and end dates of an element assignment, the user field values may be different from one slice to another.
-
When User Field Values Come From Positive Input: A given positive input entry always targets a specific slice or segment. The positive input end date determines the slice or segment to which the positive input entry applies and the user field set applies to that slice or segment only. For example, imagine that an earning is divided into two segments: the first segment has begin and end dates of June 1 and June 15, and the second segment has begin and end dates of June 16 and June 30. If you enter positive input for the earning with an end date of June 10, the positive input falls within the first segment of the pay period, and the user fields associated with the positive input apply to that segment only.
See Segmentation Considerations, Positive Input in a Segmented Calendar When User Field Sets are Defined.
-
When User Fields Come From a Driver Accumulator: Instances of a driver accumulator have associated user key values. Depending on whether the driver accumulator is on a segmentation event list, the instances may have either slice dates or segment dates. The user key values for each slice or segment of the driver apply to the corresponding segment or slice of the earning or deduction.
Example 1: Element Segmentation with Earning/Deduction Assignments; All Overrides Entered Using Earning/Deduction Assignments
Deduction D1 is included in the element list for a segmentation event.
The deduction does not have an accumulator driver.
Payroll is processed monthly.
The system generates a segmentation trigger with an effective date of June 16.
All user fields are entered as overrides on the element assignment pages.
This table lists the deduction assignments:
Note:
In this example, earning/deduction assignment is abbreviated E/D Assignment.
| E/D Assignment | E/D Assignment | E/D Assignment | |
|---|---|---|---|
|
Element Name |
D1 |
D1 |
D1 |
|
Instance Number |
1 |
2 |
3 |
|
Process Order |
10 |
20 |
30 |
|
Amount |
1000 |
500 |
600 |
|
User Field 1 (State) |
State 1 |
State 2 |
State 1 |
|
User Field 2 (Company) |
AAA |
AAA |
AAA |
The system resolves six instances of the deduction in the following order:
| Res. Nbr. | Slice Nbr. | Slice Dates | Amt. | User Field 1 (State) | User Field 2 (Company) | Override Source |
|---|---|---|---|---|---|---|
|
1 |
1 |
June 1– 15 |
500 |
State 1 |
AAA |
Element Assign. |
|
2 |
2 |
June 16 – 30 |
500 |
State 1 |
AAA |
Element Assign. |
|
3 |
1 |
June 1– 15 |
250 |
State 2 |
AAA |
Element Assign. |
|
4 |
2 |
June 16 – 30 |
250 |
State 2 |
AAA |
Element Assign. |
|
5 |
1 |
June 1– 15 |
300 |
State 1 |
AAA |
Element Assign. |
|
6 |
2 |
June 16 – 30 |
300 |
State 1 |
AAA |
Element Assign. |
In this example, the user field set for each resolution is entered with the element assignments and applies equally to both slices.
Example 2: Element Segmentation with Earning/Deduction Assignments; Not All Overrides Entered Using Earning/Deduction Assignments
Deduction D1 is included in the element list for a segmentation event.
The deduction does not have an accumulator driver.
Payroll is processed monthly.
The system generates a segmentation trigger with an effective date of June 16.
Not all user fields are entered as overrides on the element assignment pages. A formula determines the value of the Company user field; this field has a different value in each slice.
This table lists the deduction assignments:
Note:
In this example, earning/deduction assignment is abbreviated E/D Assignment.
| E/D Assignment | E/D Assignment | E/D Assignment | |
|---|---|---|---|
|
Element Name |
D1 |
D1 |
D1 |
|
Instance Number |
1 |
2 |
3 |
|
Process Order |
10 |
20 |
30 |
|
Amount |
1000 |
500 |
600 |
|
User Field 1 (State) |
State 1 |
State 2 |
State 1 |
The system resolves six instances of the deduction in the following order:
| Res. Nbr. | Slice Nbr. | Slice Dates | Amt. | User Field 1 (State) | User Field 2 (Company) | Override Source |
|---|---|---|---|---|---|---|
|
1 |
1 |
June 1– 15 |
500 |
State 1 |
AAA |
Element Assign. |
|
2 |
2 |
June 16 – 30 |
500 |
State 1 |
ZZZ |
Element Assign. |
|
3 |
1 |
June 1– 15 |
250 |
State 2 |
AAA |
Element Assign. |
|
4 |
2 |
June 16– 30 |
250 |
State 2 |
ZZZ |
Element Assign. |
|
5 |
1 |
June 1– 15 |
300 |
State 1 |
AAA |
Element Assign. |
|
6 |
2 |
June 16 – 30 |
300 |
State 1 |
ZZZ |
Element Assign. |
The values of the user fields not entered as element assignments are determined by slice and differ by slice.
Example 3: Element Segmentation with Positive Input; All Overrides Entered Using Positive Input
A deduction D1 is included in the element list for a segmentation event.
The deduction does not have an accumulator driver.
Payroll is processed monthly.
The system generates a segmentation trigger with an effective date of June 16.
All user fields are entered as overrides in positive input.
All positive input entries have begin and end dates.
This table lists the positive input entries for the deduction:
Note:
In this example, positive input is abbreviated PI, and the positive input action type of override is abbreviated Over.
| PI (Over) | PI (Over) | |
|---|---|---|
|
Element Name |
D1 |
D1 |
|
Instance Number |
1 |
2 |
|
Begin Date |
June 1 |
June 16 |
|
End Date |
June 15 |
June 30 |
|
Amount |
1000 |
600 |
|
User Field 1 (State) |
State 1 |
State 2 |
|
User Field 2 (Company) |
AAA |
ZZZ |
The system resolves two instances of the tax deduction in the following order:
| Res. Nbr. | Slice Nbr. | Slice Dates | Amt. | User Field 1 (State) | User Field 2 (Company) | Override Source |
|---|---|---|---|---|---|---|
|
1 |
1 |
June 1– 15 |
1000 |
State 1 |
AAA |
Positive Input |
|
2 |
2 |
June 16 – 30 |
600 |
State 2 |
ZZZ |
Positive Input |
Resolution 1 (Slice 1) uses the data defined in positive input Instance 1, and Resolution 2 (Slice 2) uses the data defined in positive input Instance 2.