2419330 - Reasons for an Incorrect Compa-Ratio/Range Penetration display in forms for a EC Integrated template - Compensation

When launching Compensation forms, Compa-Ratio and/or Range Penetration fields are displaying N/A or an incorrect value, even though correct data is shown in Employee Central.

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental.

• SAP SuccessFactors HCM Suite
• SAP SuccessFactors Compensation

This behavior could be due to many reasons, since Compensation and Employee Central have different logic to pull Pay Ranges for users. Please find below possible reasons for it.

Please find below the step by step to confirm the range that should be pulled into the compensation worksheets:

1. Corporate Data Model and Attributes Configuration

In the Corporate Data Model we define which fields will be associated to each Pay Range under <hris-element id="payRange">. Please download the Corporate Data Model, find the tag for pay range and at the very bottom of that hris-element there will be the associations.
These associations' order has to be followed also on the EC Pay Matrix. The rule is that Pay Grade will always be an association to the Pay Range and always displayed as the first association.

For example, if we want to define Geo Zone, Legal Entity and Pay Grade as associations we will always have to define Pay Grade as the first one and then follow the order we define for Geo Zone and Legal Entity in the Corporate Data Model for the EC Pay Matrix attributes.

In the above Corporate Data Model we have defined, after Pay Grade, Geo zone first and Legal entity second. Then, in the settings page of affected template, it needs to be defined Geo Zone as Attribute1 and Legal Entity as Attribute2. For Pay Grade, this is hard coded and first by default, so there is no need to add to the settings page below.

The fields available to be added to Attributes are coming from Design Worksheet. Make sure that the chosen fields will be mapped to the fields that will pull the same values from the associations in the Corporate Data Model. The matching happens by checking the values in EC and in the form.

2. Missing Relation defined in the system

The issue may be that there is no valid combination of the fields used to define the pay ranges. For example, a matching combination of Pay Grade, Geo Zone, and Legal Entity may not exist. To resolve this issue, create the missing pay range combination in the Pay Range foundation data.

To verify whether the required combination already exists, run an Ad Hoc Report for Foundation Objects > Pay Range. System will look in to the currency and frequency before matching the attributes. Follow the steps below to build the report:

1. Go to Reporting page
2. Create new > Table > Foundation Objects domain
3. Go to columns and click on Select Columns
4. Under All Columns select Pay Range
5. Then on the right side, select the following in this order: start-date, end-date, status, name, minimumPay, midPoint, maximumPay, currency, frequency, pay grade, geozone and legal entity (the last two columns is as per example above where these fields are part of the attributes, this may vary according to your configuration).
6. Save and run the report. Once report is downloaded, filter the first row.
7. Open the worksheet where affected user is, and filter column by column starting from currency with the values seen in the worksheet. Please make sure to always include blanks if that option is there. Blank field acts as a wild card and can be a match.
8. Once all fields are filtered according to the values in the worksheet, the first row will be the match for the user. In case that is not the expected as per your business, then this range might need to be deleted in case it is no longer used. 

In case there are are missing combinations, which causes the range to be N/A in the form, you can import it on the system or define it in the UI. That can be done under Import Foundation Data or in Manage Organization, Pay and Job Structures.

3. Pay Matrix Effective Date < Pay Ranges Effective dates

Another possibility is that the Effective Date defined on the Pay Matrix is earlier than the effective dates of the Pay Ranges in the system, so the Matrix cannot retrieve them. Again, the best way to look for this error is within the same report mentioned above on Foundation Objects. On that report you can check the start date of each range and ensure the start date is before the Pay Matrix effective date (as best practice 01/01/1900) and the end date is in the future (12/31/9999 for example if we don't expect the Pay Ranges to have an end date).

4. Different Effective Date for the Compensation template and Salary Pay Matrix

The Compa-Ratio displayed in Employee Central is recalculated dynamically each time an employee's profile is opened. The calculation always uses the currently effective Employee Central Salary Pay Matrix. As a result, differences can occur if the Compensation template is configured to use a Salary Pay Matrix effective date that differs from the date on which the Merit Planning forms are created.

To ensure that the Compa-Ratio displayed in Employee Central matches the value shown in the Merit Planning worksheet, configure the Compensation template to use the Salary Pay Matrix effective date that corresponds to the Merit Planning forms creation date. Set the Salary Pay Matrix effective date in the Compensation template to the Merit Planning forms creation date. This ensures that both Employee Central and Compensation use the same salary range data when calculating the Compa-Ratio, preventing discrepancies between the two modules.

Example

• May 9: Employee A has a salary of 110,000. The currently effective Salary Pay Matrix has a midpoint of 100,000, so Employee Central displays a Compa-Ratio of 110%.
• May 10: An Employee Central administrator uploads a new Salary Pay Matrix with a midpoint of 90,000, effective June 1.
• May 11: A Compensation administrator launches the Merit Planning worksheets and configures the template to use a Salary Pay Matrix effective date of June 1.

In this scenario, the Merit Planning worksheet calculates the Compa-Ratio using the June 1 midpoint of 90,000, resulting in a Compa-Ratio of approximately 122.22% (110,000 ÷ 90,000). However, Employee Central continues to display a Compa-Ratio of 110%, because the new Salary Pay Matrix is not yet effective. Employee Central always calculates the Compa-Ratio using the matrix that is effective on the current date, while the Compensation worksheet uses the effective date configured in the template.

5. Invalid Association Field in the system

The Pay Range may be configured correctly, but one or more associated Foundation Objects used as attributes may be invalid or inactive.

For example, after running the Foundation Objects > Pay Range Ad Hoc Report and filtering the results based on the employee's attribute values, you may find two matching pay range records. Although the employee appears to match the first record, the system may instead resolve to the second record because the first contains an invalid or inactive associated value.

In this case, review all attributes associated with the Pay Range and verify that they are active and valid. For example, if the Legal Entity referenced in the first pay range record is inactive, that pay range becomes invalid and cannot be used. As a result, the system evaluates the next valid matching pay range instead.

This issue can also happen due to invalid Job Code. If the inactive Job Code appears at the top of the list of associated Job Codes, the system cannot proceed to the next associated Job Code to find a valid match.

To verify whether this is the cause of the issue, include the associated Job Codes, along with their start date, end date, and status, in the Foundation Objects > Pay Range Ad Hoc Report. If any of the associated Job Codes are inactive, remove their association from the Pay Range. This ensures that the system can correctly evaluate and use the appropriate active Job Code when determining the applicable pay range.

6. Frequency field not defined for our employees

The Pay Range Frequency must match the Frequency of the employee's Recurring Pay Component in Compensation Information. If the Frequency field in Compensation Information is empty, the system defaults it to ANN (Annual). As a result, a matching pay range may not be found if the applicable Pay Range is configured with a different frequency, such as Hourly.

To verify this, review the Frequency value in the Foundation Objects > Pay Range Ad Hoc Report for the relevant combination of attributes (for example, Pay Grade, Geo Zone, and Legal Entity). Ensure that the Pay Range Frequency matches the Frequency defined for the affected employees' Recurring Pay Component. 

This issue can also occur when the frequency displayed in the Compensation Worksheet differs from the frequency defined in Employee Central. For example, if the salary fields are mapped to a Pay Component Group, the imported salary values are annualized by default. As a result, the standard salaryType field (which determines the frequency used in the worksheet) is also set to Annual.

If the employee's Recurring Pay Component in Employee Central has a Monthly frequency, and the corresponding Pay Range is also configured with a Monthly frequency, the worksheet will use Annual as the frequency. Because the worksheet frequency does not match the Pay Range frequency, the system is unable to find a matching pay range.

7. EC Pay Range currency

Ensure the pay range has a defined currency code and the employee matches the currency code of the range. For example an employee having USD and the range having EUR would not correctly or automatically convert.
To correct this, you should add a pay range with USD as the currency to fix this type of issue or update both so they match.
This behavior is different from Employee Central, since Compensation Information supports the currency conversion between all currency codes automatically, which Compensation does not.

8. Compensation-EC column mapping

Issue could be due to how mapping of attributes/associations is done in Compensation.

When mapping custom/standard columns to EC please ensure the following:

• Pay Grade is mapped to externalCode
• Custom associations are mapped to label, for example:
  <comp-ect-input-field-map componentType="jobInfo" fieldName="job-code"/> and not <comp-ect-input-field-map componentType="jobInfo" fieldName="job-code.name"/>

Additional information

• Required standard columns: Ensure the following columns are added to the template, that will help on identifying the behaviors mentioned above.
   - salaryRateType
   - FTE
   - localCurrencyCode
   - payGrade
• If a custom field is used in the Salary Pay Matrix, any changes made to the Compensation Worksheet must be saved before the system recalculates and displays the updated values. If the changes are not saved, the worksheet will not refresh the calculation and the related fields may continue to display N/A.

SF,successfactors, EC, PayGrade, PayRange, Pay Range, compa-ratio, compa ratio, range penetration, missing compa-ratio, compensation-ec, n/a compa ratio, cmp-16385, CMP-21381, N/A range, N/A compa ratio, missing salary ranges, range, Salary Midpoint , KBA , LOD-SF-CMP-FRM , Forms & Templates , LOD-SF-CMP-EC , EC data, EC mappings, configuration & settings , Problem

SAP SuccessFactors Compensation all versions ; SAP SuccessFactors HCM Suite all versions