2419330 - Compensation - Top 5 Reasons why Compa-Ratio/Range Penetration do not display in forms for a EC Integrated template

When launching Compensation forms, Compa-Ratio and/or Range Penetration fields are not displaying any values while in Employee Central all calculations show correctly.

"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 Employee Central
• SAP SuccessFactors Compensation

This can be caused by a number of things from Compensation mapping to EC and configuration within Employee Central.

The following are five potential causes.

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">.
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 assocation.
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.

 

We have defined Geozone first and Legal entity second so we need to define Geo Zone as Attribute1 and Legal Entity as Attribute2.

2. Missing Relation defined in the system

The problem may be there is no valid combination for the fields that define our Pay Ranges (in our example a valid combination for Pay Grade + Geo Zone + Legal Entity).
In this case, the solution will be to define that combination. To know if such combination exists you can run an Ad Hoc report for Foundation Objects > Pay Range.

 

If there is are missing combinations you can import it on the system or define it in the UI.

Note: System will look in to the currency and frequency before matching the attributes.

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 to create an Ad Hoc report for Foundation Objects > Pay Ranges and include the Start and End Dates for each Pay 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. Invalid Job Codes in the system

It could also be that the Pay Range is correctly defined but there are invalid job codes in the system associated to it. 
If that is the case and the Job Code is displayed  on top of the list of associated Job Codes, the system is not able to move to the next Job Code to find the correct one. 
The way to review this possible error is to add the Job Codes to our Ad Hoc report including the start and end dates and the current status. 
If any of the jobcodes is Inactive then we need to remove the association with the Pay Range in the system.

5. Frequency field not defined for our employees

The Pay Range Frequency must match the Frequency of the Recurring Pay Component in Compensation Information for our employees. 
If that field is empty in Compensation Information, the system will default it to ANN (Annual) and maybe the Pay Range associated to this employee is looking for an Hourly frequency.
We will need to review the Frequency in our Ad Hoc report for the combination Pay Grade + Geo Zone +... and ensure it is the same as for our affected employees.

Note: Make sure that the Pay component frequency is the same as the Pay range desired.

Additional information

Compensation-EC column mapping

In some cases, after reviewing all of the above the cause of N/A compa-ratio etc may be down to how you are mapping attributes/associations into Compensation.

When mapping custom/standard columns to EC please ensure the following (CMP-16385):

• 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"/>

Required standard columns

Snsure the following columns are added to the template.

• salaryRateType
• FTE
• localCurrencyCode
• payGrade

EC Pay Range currency

• If all of the above has been checked and all data is correct yet there are still some employees missing compa ratio etc, then please ensure their pay range has a defined currency code.
• Also ensure 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 EC as EC  as Compensation Information supports the currency conversion between all currency codes automatically, which Compensation does not.

NOTE:

• If you will use custom field in Salary pay matrix then when you will make any change on the form you need to save changes to see new output otherwise you will see 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 , KBA , LOD-SF-CMP , Compensation Management , LOD-SF-CMP-EC , EC data, EC mappings, configuration & settings , Problem

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