Mapping categories

A mapping category is an abstraction that allows you to map multiple objects of a similar kind, as they are configured in Timekeeping, to a singular, known, named classification for analytical reporting purposes. For example, an organization may pay overtime using multiple pay codes in Timekeeping, including Daily Overtime, Holiday Overtime, and Contractual Overtime. If each of these pay codes is mapped to a mapping category named "overtime," it is possible to create metrics that are associated with the overtime mapping category and return data associated with just overtime events.

Analytics provides types of mapping category for exceptions, pay codes, punch variances, generic jobs, volume drivers, adjustment drivers, and time entities. The corresponding objects in Timekeeping can be mapped to a mapping category of the appropriate type when they are added in Timekeeping setup.

Note: The Analytics component of Timekeeping does not use a fixed set of pay code categories, like Workforce Analytics does. In the Analytics component of Timekeeping, the categories are not connected; A single pay code can be in multiple categories. Do not sum across the categories. If you add overtime hours to actual hours, you are double counting some hours because actual hours include overtime hours. If you add regular hours to actual hours, you are doing the same thing.

Analytics also defines a number of standard mapping categories in some category types. For example, Overtime, Regular, and Excused Absenteeism are standard mapping categories of the Pay Code type; Missed Punch, Late In, and Early Out are standard mapping categories of the Exception type.

You can also create custom mapping categories that, when used with metrics, refine the data that is returned. For example, you could create a mapping category of the Exception type named "Deficient Punches" that includes only Late In, Very Late In, Early Out, and Very Early Out. You could also create a pay code mapping category called "worked" that includes all pay codes that are representative of worked hours.

The number of custom mapping categories that you can create is unlimited.

VOLUMEDRIVER and ADJUSTMENTDRIVER mapping category types

The VOLUMEDRIVER mapping category type allows metrics to be mapped to a volume driver so that these metrics, and the KPIs that use them, can be used in Dataviews and reports. They can thereby return up-to-date values for forecasted, actual, and budget data.

The ADJUSTMENTDRIVER mapping category type similarly allows metrics to be mapped to an adjustment driver that was created as part of the implementation of labor constraints on a labor forecast. Dataviews and reports that use these metrics and KPIs can thereby include information on the constraint that has been applied to the forecast.

The VOLUMEDRIVER and ADJUSTMENTDRIVER mapping categories are available exclusively for metrics created for Forecasting. They are provided only when you are creating a metric and select a data source that is related to Forecasting:

  • Actual Volume
  • Budget Labor Cost
  • Budget Labor Hours
  • Budget Volume
  • Earned Hours
  • Forecasted Hours
  • Forecasted Volume
  • Generated Forecasted Hours
  • Generated Forecasted Volume

GENERICJOB mapping category type

The GENERICJOB mapping category type provides a means to create a create a mapping category with selected generic jobs. A metric that is based on that mapping category returns data only for selected generic jobs. Essentially, the metric is looking for the job associated with the transaction to determine if it is part of the metric value, but ignores the rest of the organizational path.

For example, if the job mapping category included the generic job of “Associate," transactions related to any of the following org jobs would be included in the metric value:

  • RCo/Grocery/Region 1/District 1/Store 0404/Bakery/Associate
  • RCo/Grocery/Region 1/District 1/Store 0404/Produce/Associate
  • RCo/Grocery/Region 1/District 1/Store 0505/Bakery/Associate
  • RCo/Grocery/Region 1/District 3/Store 0505/Bakery/Associate
  • RCo/Grocery/Region 4/District 1/Store 0404/Produce/Associate
  • RCo/Retail/Region 1/District 1/Store 0404/Produce/Associate
  • RCo/Grocery/Region 2/Store 2424/Produce/Associate

When creating a metric that is based on any of the following data sources, an administrator can assign a single GENERICJOB mapping category:

  • Forecasted Hours
  • Generated Forecast Hours
  • Budget Labor Hours
  • Budget Labor Cost

A metric created with a GENERICJOB mapping category cannot be used in a conditional KPI.

A metric created with a GENERICJOB mapping category is available for use only in a Business Structure Dataview or a Business Structure Time Series Dataview.

When creating a metric that is based on any of the following data sources, an administrator can assign a single GENERICJOB mapping category and a single PAYCODE mapping category

  • Actual Hours
  • Actual Costs
  • Scheduled Hours
  • Scheduled Costs
  • Projected Total Hours
  • Projected Total Costs
  • Actual Days
  • Scheduled Days
  • Projected Total Days

A metric created with both a GENERICJOB mapping category and a PAYCODE mapping category provides data only for those transactions that meet both the defined job and the defined paycode conditions (that is it only supports an AND operator).

A metric created with both a GENERICJOB mapping category and a PAYCODE mapping category cannot be used in a conditional KPI.

A metric created with both a GENERICJOB mapping category and a PAYCODE mapping category is available for use only in a Business Structure Dataview or a Business Structure Time Series Dataview.