Cube - Human Resources

Contents

• Usage/Purpose
• Overview Fact
• Used Dimensions
• Limitations and Configurations
• Fact and Dimension Connections
• Used Dimensions
• Fact and Dimension Connections
• Measures
• Included Example Reports and Dashboards
• Required Components

Usage/Purpose

Main scenarios are:

• Number of headcount analysis over time. Employed and FTE
• Age analysis and age distribution over time
• Headcount changes over time with respect to reasons

To see which dimensions that can be used with each fact in, for example Excel pivot analysis, see chapter Fact and Dimension Connections below.
 

Overview Fact

Each measure in the facts is described in section Measures. Corresponding Information Sources are described below. Detalled infomation about Information Sources can be found in IFS Online Documentation.

FACT_EMPLOYEE_ANALYSIS

Employee analysis information source is based on IFS\Employee Analysis. The information source offers analysis capabilities on headcontes over time.

• Total Headcount
• Employee Turnover changes
• Effective Headcount

Used Dimensions

Limitations and Configurations

In order for the cube to build properly it is necessary that person identities referenced in within a snapshot category share the same name. The person identity name is in this version not part of a dimension and the solution was to include the name in the fact table instead. This means that every time a snaphot is created with respect to a specific snapshot category, the name of a person identity must be the same (which is probably the normal case). It is allowed for the same person to have different names in different snapshot categories but not in the snapshots relaed to one category. The reason for a person identity to have different names over time could be due to incorrect name definition. So correcting the name might lead to problems.

The HR cube only supports one Age Group Class. It is necessary to define the Age Group Class in IFS Applications and then to define relevant lookup information for the ETL process. Refer technical documentation for more information.

Fact and Dimension Connections

The following picture shows how different facts in the cube are connected to the available dimensions.

Measures

General

Aggregation of measures is based on SUM if not explicitly noted.

Basic Measures

This sections describes the basic measures in the cube. These are either measures defined in the core Information Source or in the ETL process. The columns have the following meaning:

• Core Measure: A measure that has its origin in a core Information Source
• ETL Measure: A measures defined the the ETL process, in most cases by using existing core measures as input.
• Cube Measure: A measure specifically defined in the cube, e.g. count of rows etc.
• Measure Expression: Specifies if a measure expression has been used in the cube to modify a general measure. One special case is amounts calculated in Reporting Currency, where a basic measure is divided by the Currency Rate from the fact REPORTING CURRENCY RATES. This means that by using a filter on dimension REPORTING CURRENCY dimension, it is possible to present amounts in different companies in a common currency.
• Reporting Currency Measure: Specifies if a measure supports presentation in reporting currency.

Calculated Measures

Calculated measures are in the cube calculated with respect to other measures. The table below defines the general meaning/definition of each calculated measure.

Time Based Measures

No time based measure is used in the Human Resourced cube.

Included Example Reports and Dashboards

This section lists dashboards and reports in the example content for the BI Analysis Package that is using this cube:

Required Components

The BI specific and also related core components listed in this section are required, i.e. they must along with other dependent components, be part of the customer installation to successfully use this cube.

NOTE that only directly used components are listed. Each such component can have its own list of dependent components. Please refer to the Component Deployment Profile File for each component to get the full picture.

Note: BI Component used will be HRHCTC