SAP Knowledge Base Article - Public

2183718 - Normalization Impacts to Performance Ratings, Reports, Dashboards - Performance Management

Symptom

When ratings, overall ratings, reports, scores etc, are not calculating as expected, one area to review is Normalization, normalizing scales and scores.

  • Wrong/Inconsistent "Overall Form rating in %" calculation;
  • Overall rating incorrect on forms;
  • Ratings, overall ratings, calculated ratings incorrect on forms or in dashboards and reports.

Environment

  • SAP SuccessFactors Performance Management
  • SAP SuccessFactors Goal Management
  • SAP SuccessFactors Analytics

Resolution

What is Normalization?

Normalization happens any time more than 1 scale is present, which could be within the form, or between the form and the scale the dashboard or report is using.  Normalized Ratings are the result when for any reason two or more scales are part of the calculated result. This can happen for many reasons, for example:

  • You have one scale for goals but another for competencies
  • Or two or more scales within a performance form
  • Or reporting on different templates that use different scales
  • Or running a report where the report scale differs to any scale used within any of the forms being reported on.
  • The ratings from ALL sources will be considered, and when any are different Normalization takes place automatically within the system. All ratings get normalized-plotted on a percentage scale from 0 to 100-and then converted to the appropriate system rating scales for output.

At times there might be very small variations to the overall rating or calculated results you are expecting to see. You can show via excel that you get different results compared to what our system is calculating.

While values may not be as expected, do not view these as system defects or bugs, but as likely misconfigurations based on what your config is telling the system to do. From this angle, the form, report or system is actually working correctly as it can only calculate based on the rules given.

 

As Used in Reports & Dashboards - Normalization Calculator

The following article provides insights into how normalization is applied to dashboards and reports in particular and shows how the normalization calculator actually works.

2089661 - Ratings: Rating Scales - Normalized Ratings used in List Views, Dashboards and Succession Org Chart - Reporting and Analytics

 

Different Rating Scales in Different Sections Scenario: The customer wants to use different rating scales with differing levels for competencies,  objectives and the overall rating. Such that the competency section has a 3 pt. scale and the objective and overall have a 5 pt. scale. The Dashboard will normalize all ratings on the dashboard to the rating scale in the selected Process. The customer will find that the ratings from the form are not properly displayed on the Dashboard portlets for whichever scale is not the Process scale.

Rating Scale Order for Different Forms Scenario: Different rating scale order from one form to another (e.g., Comp and PM or 360 and PM).  The Dashboards and List Views will normalize ratings across the chosen rating scale for a process......so would make 4s show as 2s, etc

 

Case Example:

The following article walks through a typical scenario and shows how many things, including normalization can come into play when calculating or impacting final scores or ratings.

2078768 - Ratings; Understanding How Scores use Rounding; Scale Adjustments; Normalizations; Decimal Places - Performance Management

 

Specific To Performance Forms

We have seen rather strange results in some customer programs when normalization comes into play in summary sections. If you are using adjusted scales, scores from MLT (Metric Lookup Tables), large scales etc, and are seeing inexplicable wrong or inconsistent values in the overall form rating based on score %, you might need to disable normalization in the section. Note: This feature exists for good reason! The fact it is on might indicate it is needed for the program, so bef9ore any change is made, an evaluation needs to be made as to why you have the current configuration in place, to determine if you can support a change in this area. Otherwise you may resolve one issue only to introduce another issue.

The normalize-section-rating element can be used to specify if rating should be normalized or left non-normalized for section level score calculation.

The values allowed are "true", "false". Default "true".

The meta-normalize-form-rating element can be used to specify if rating should be normalized or left non-normalized for form level score calculation.

The values allowed are "true", "false". Default "true".

ococ-rating-calc-mode: determines what kind of calculation method is used to calculate the OCOC score

"avg"  - averages and normalizes the OCOC score (e.g. sum(rating * weight) / sum(weight))

 <!ELEMENT normalize-goal-weights (show-blank-for-incompleted-weights?)>

enabled (true | false) "true"

Compensation

PM Ratings Going to Compensation Worksheets. See: 2084825 - Rating Sources - Disable PM Rating normalization - Compensation

overrideSectionRatingNormalization (true | false) "false"

Attribute overrideSectionRatingNormalization is used to override normalize-section-rating setting of a PM section.

If it is set to true, then p4p section item rating normalization will be turned off in compensation module. If it is set to false, then we will respect normalize-section-rating setting in PM section. Default value is false.

comp-expected-rating-format - 0 if showing the expected rating in %; 1 if converting the % to a score normalized to the section scale; default is 0;

behavior-expected-rating-format - 0 if showing the expected rating in %; 1 if converting the % to a score normalized to the section scale; default is 0;

 

DTD Configuration Information to Consider

This information relates to program configurations that only Partners and Support are able to access, but nevertheless good to know exist. These could be variables to check in the program at issue.

Ratings require a rating scale that has a minimum and maximum value.  Ratings are representations of a percentage.  The calculation some customers are using is based on a score.

A score is different from a rating in that scores do not have a rating scale.  There is no notion of a maximum or minimum for a score, it is just a calculated mathematical value.

  1. The following combinations of fields are supported in configurations for a form template
    • Use normalized rating and normalized weight (default)
    • Use normalized rating and non-normalized weight (“sum” configuration)
    • Use non-normalized rating and normalized weight
    • Use non-normalized rating and non-normalized weight
  2. Normalization of a rating is defined as changing the rating value based on the rating scale min/max it is in and a set of target min/max rating scale values.
  3. The system shall support the ability to use non-normalized ratings at the following levels
    • Item ratings used for overall section score
    • Section ratings used for overall calculated performance score
    • Section ratings used for overall calculated objective score
    • Section ratings used for overall calculated competency score
    • Overall competency & objective scores used for OCOC score (not the matrix lookup but the “avg” and “sum” calculations).

See Also

Under Attachments, you may find the Normalization calculator.

Keywords

ratings PM Performance forms overall score scores rating , KBA , LOD-SF-PM , Performance Management , LOD-SF-ANA , Analytics & Reporting (Ad Hoc, YouCalc, ORD) , How To

Product

SAP SuccessFactors HXM Core all versions

Attachments

NormalizationCalculator.xls