Understanding Configurable Matrices

A configurable matrix is a special type of lookup table that can be designed and populated by the administrator. The administrator specifies the inputs (or criteria) that will be used as lookup variables and the outputs (or results) that the table will return for specific combinations of input values.

Defining a Configurable Matrix

The examples that follow illustrate the concept of matrices and their intended uses.

Simple Rate Matrix

Use this matrix to determine the compensation rate for a worker based on his department.

Department ID - Input

Rate (USD per hour) - Output

10012

10.00

10013

12.00

10014

14.00

10015

16.00

In this example, the single input is the Department of the worker, and the output is the Rate. If a worker is in Department 10012, then the pay rate is 10.00 USD per hour.

Matrix with Two Inputs and One Output

This matrix has two inputs and one output:

Time with Company (months) - Input

Site Risk - Input

Rate (USD per hour) - Output

0–24

Low

10.00

0–24

Medium

12.00

0–24

High

14.00

25–60

Low

12.00

25–60

Medium

14.00

25–60

High

15.00

61–120

Low

14.00

61–120

Medium

14.00

61–120

High

16.00

121–7200

Low

16.00

121–7200

Medium

17.00

121–7200

High

18.00

In this matrix, the rate is determined by a combination of the time in company and the risk level of the work site. A worker who has been with the company for 50 months and works at a Medium risk site will be compensated at the rate of 14.00 USD per hour.

Market Pay Matrix: Matrix with Multiple Outputs of Different Types

The outputs of a matrix can be of different types, and the following example is a matrix with multiple outputs, one of which is a percentage. You use this matrix to track the compensation rates for a job at various percentiles and different geographical areas. It also tracks rates for standard compensation figures, such as total cash compensation.

In this example, the only input is the geographical area; all other columns are outputs. You can associate this matrix with a specific job code, so that the compensation administrator can track market pay for that job code across different geographical regions.

Geo- graphy

Currency

Base 25th

Base 50th

Base 75th

Base 100th

Base Market Refer- ence

Variable Target Percent

Mean Total Compen- sation

Total

Compen- sation

Refer- ence

NORTH- EST REGION

USD

26,000

27,00

27,500

28,000

27,000

12.00

29,000

30,000

MID ATLAN- TIC REGION

USD

24,000

25,000

25,500

26,000

25,000

10.00

27,000

28,000

SOUTH- WEST REGION

USD

27,000

28,000

28,500

29,000

28,000

11.00

30,000

31,000

Matrix with Calculated Results

You can embed calculations in the results returned by a matrix. In this example, the matrix returns rates calculated by applying a formula:

Step - Input

Reference - Output

Percentage to Apply - Output

1

Base Salary

5

2

Grade Range Maximum

90

3

Base Salary

4

For example, if the worker's base salary is 10,000 USD and the worker is on Step 1, then this matrix will return a rate (Base Salary × 5%) = 10,500 USD.

Note: The system performs the appropriate checks to find the worker's current base salary. The base salary was not stored in the matrix.

This section discusses matrix inputs, outputs, and matrix evaluation rules for configurable matrices.

Matrix Inputs

Each matrix can have one or more inputs. These inputs are the search criteria against which you will evaluate a specific worker. The maximum number of inputs is 15. Each input is defined in the form of one or more source IDs.

HR contains a number of predefined source IDs as system data. You can use those to build your configurable matrices. However, you can create also additional custom source IDs.

See Defining Sources for Configurable Matrices.

Matrix Outputs

The outputs of a matrix are available in the form of Result IDs. You can have a maximum of 30 outputs for one matrix. The outputs are categorized into result types, based on their data format or the rules used to derive the result.

Base Compensation contains a number of predefined Result IDs as system data. These results can be used as outputs for the configurable matrices. However, you can create additional custom result IDs.

See Predefined Result IDs.

Matrix Evaluation Rules

Whenever the matrix is invoked, the system attempts to match the worker's data with keys in the matrix. The system checks all input variables against the keys defined for each input. The order of checking will be the same as the order in which the inputs were defined. At the first row where all input variables match the keys specified in the matrix, the system will return all result IDs for that row. When you are defining search keys, the system ensures that no rows are duplicated. You cannot have any blank search keys.

Using Wildcards as Search Keys

You can use wildcards when defining search keys. After you enter specific key values for one input, you can optionally add a wildcard key. If no explicit match is found against any of the other key values, then the wildcard key is considered a match. For example, assume you defined Dept ID as an input. You want to list specific non-zero rates for Dept IDs 101, 102, 103, and 104. However, for all other departments, you want a rate of 0. In this case, you would specify a total of five keys for the input, 101, 102, 103, 104, and '*' for the wildcard. Any worker not in Dept 101, 102, 103, and 104 would match the wildcard and would get a rate of 0. Using wildcards allows you to have a default rule defining what to do if the worker's data does not match any of the key values.

This section discusses the three types of matrices you can create using the configurable matrices feature.

  • Market pay matrix

    This matrix captures market pay information for a given job. The market pay matrix can then be associated with specific job codes by using the Associate Mkt Pay to Job Codes page (Set Up HCM > Product Related > Compensation > Market Pay > Associate Mkt Pay to Job Codes). You can also associate the matrix directly on the Market Pay Match page of the Job Code Table component (Set Up HCM > Foundation Tables > Job Attributes > Job Code Table > Market Pay Match).

  • Rate matrix

    This matrix is used to store compensation rates based on multiple criteria. You can then associate a rate matrix to a rate code defined on the Comp Rate Code Table page (Set Up HCM > Foundation Tables > Compensation Rules > Comp Rate Code Table). The rate matrix can return compensation rates that are directly listed in the matrix or derived using formula-based result IDs.

  • Salary increase matrix

    This matrix is used to store the salary increase guidelines, as percentages of base salary. These guidelines are usually based on the worker's performance ratings and ratios, such as Compa-Ratio and Percent-In-Range. You can attach this matrix to specific rate codes in a group budget (Compensation > Base Compensation > Group Budgets > Create/Approve Group Budget > Budget Components). When calculating the budget, the system applies the appropriate increases to workers based on the criteria in the matrix.

    Note: Depending upon the page, you can only associate a specific type of matrix to that page. For example, the system will only retrieve rate matrices when searching on a rate code definition page. Similarly, you can only associate market pay matrices to a job code.

Important! You cannot associate configurable matrices to seniority pay rate codes.

See Comp Rate Code Table Page.

See Understanding the Base Compensation Budgeting and Planning Business Process.

This section discusses how the system displays a configurable matrix.

Matrix Display

Within compensation processes, data is often presented and used in a two-dimensional table, or matrix form. An example is in salary increase guidelines, which store increase percentages for different performance ratings and percent-in-range ratios. How this data is presented affects how easily it can be understood. When defining inputs for a matrix, you can specify one of the inputs to be the column header instead of the row header. The following section explains this concept further.

Example: Displaying Inputs as Columns

Assume that you have two inputs (step and department) and one output (rate). The system can display the matrix in two ways.

Example 1: Each combination of inputs is like a row header.

Step

Department

Percent Rate

1

100

2

1

122

4

2

100

6

2

122

8

3

100

10

3

122

12

4

100

14

4

122

16

Example 2: One input is a column header.

This display is easier to understand because the Department input was set to Column rather than to Row, which is the standard.

Step

Department: 100

Department: 122

1

2

4

2

6

8

3

10

12

4

14

16