2458839 - How to Configure Pay Range in Positions - Employee Central

You want the payRange object to be displayed when creating, editing or simply viewing positions.

You have already configured the field and enabled it, but when you select a position or save you can see that payRange is still blank.

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 HXM Suite
• SAP SuccessFactors Employee Central 

When Creating or Editing One Position:

1. Fill all the values that you have configured to define payRange (in my example was company, pay grade and geozone) and see that pay range remains Blank;

 

When Selecting One Position in Manage Positions, Manage Data etc.:

You cannot see this field because payRange is a transient field. This means that the field value is calculated on the fly and it will never be stored in the database.

The payRange is calculated in flight so you need to make a series to settings to enable this field in the Position object.

A. You should never manually set values for payRange so this field should not be Editable.

To correct this:

1. Go to Configure Object Definitions -> Object Definition -> Position and click on Take Action -> Make Correction

2. Search for the field payRange -> click on Details -> Change the Visibility to Read Only;

 

Configuring PayRange to be Displayed When Editing and Creating Positions:

1. Create a business rule as the example below:

To have other Pay Range attributes (Min, Mid, Max Points) available in Position, you can use the Rule/Function Get Pay Range Attributes(). Keep in mind that you need to define additional Read Only custom fields in the Position object that will serve as holders of the values.
Please Note: the Get Pay Range Attributes() function can only be used on string data type fields on the position.

Sample Rule:

2. Add this rule to ALL the fields that are used to define pay Range (As example: Company, Gezone and Pay Grade):

You do this in configure object definitions, there you MUST look for each field that is used to determine payRange (in my case was company, Pay Grade and Geozone) then you click on details and add the rule you have just created.

Note: Usually customers configure geozone as one of the criteria to determine the payRange and you will notice that position does not have this field, this is expected the geozone used is determined by the Location of the position.

 

Configuring Pay Range to be Displayed When You Select a Position in Manage Positions, Manage Data etc.:

1. Navigate to Manage Data and Create a New Object Configuration:
2. Select as object Type Position and in Manage Data On Load Rules select the rule you have just created:

These settings will make payRange visible in position.

Note: If a custom UI has been added to the position object then you will need to add the Onload Rule to the custom UI in manage configuration UI for the pay range value to be visible.
- Navigate to the Position Object and copy the UI name from the Default Screen field
- Navigate to the UI in Manage Configuration UI 
- Hover over the UI name on the left-hand side and select "Edit Properties" in the popup
- Select the rule as an onLoad rule and save

 

PLEASE NOTE: 

The Pay Range Derivation used for the position is so implemented that there is the requirement that the same fields also exist in the job information. If the fields do not exist in the Job Information the Pay Range Derivation does not work.
For steps on how Pay Range is configured on Job Information please review the following section of the handbook.

 

Caveats:

Please ensure you consider the following information when implementing this functionality.

1. Field Configuration = The fields configured in the Position object that are used for Pay Range Derivation must be configured and available in Job Information HRIS Element also - and configured exactly the same. I.e. please ensure field-criteria is set in both places.
2. Custom UI's = If you are planning on using a "Default Screen" (Configuration UI), then you cannot use Pay Range derivation configuration as mentioned above. This is because the Configuration UI will treat the field "payRange" as a type = Resolver - meaning it will always try to resolve the value from the database. This is why, if you are using a Configuration UI for Position object, the Pay Range value is never displayed outside of edit mode (where the rule would be triggered onChange of related fields).
3. Derivation Behaviour = Please consult the article 2136061 (section Pay Range Foundation Object Configuration Issues) - and ensure the same limitations are observed in the configuration.
4. Export Position = Transient fields will not appear in an export of the position object, as the data is calculated on the fly, and not stored in the database

Position Implementation Guide here

2136061 - How to determine which Pay Range is used in the Compa-Ratio and Range Penetration calculations - Employee Central

Pay Range is blank in position, payRange is blank on position, pay range, payrange, position , KBA , LOD-SF-EC-POS , Position Management , How To

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