2601883 - Pay Range: How to display Pay Range and attributes in Compensation Information

There is a requirement in the business to display the Pay Range and related attributes (Min, Mid, Max, and other values) in Compensation Information

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

• Employee Central  - Compensation Information
• Employee Central - Pay Range 

• Where to find the Pay Range in the UI
• Creating a custom configuration to display Pay Range and related attributes
• Business Rules

Where to find the Pay Range in the UI

The current Pay Range for an employee is always displayed in Compensation Information, when clicking the icon next to either Compa-Ratio or Range Penetration, and also on Salary Positioning Compensation widget:

 View Guide: Showing the Pay Range in Job Information

Creating a custom configuration to display Pay Range and related attributes 

If you have such requirement to display the Pay Range as a value in Compensation Information (for reporting purposes) and/or to display the attributes of the Pay Range (min, mid, max)To be able to display the actual Pay Range and related attributes such as Min, Mid and Max salary, you will need to implement custom configuration.

Important Considerations/Limitations:

1. You will need rules in both Job Information (jobInfo) and Compensation Information (compInfo) - this is because Pay Range is derived from data stored in Job Information. This means that if you only have a rule in Compensation Information, and you update Job Information values so that a different Pay Range is derived, it will not automatically update Compensation Information data - and then if you are reporting on Compensation Information data, you will end up getting the wrong Pay Range (as that is the value persisted in the database, and Pay Range is derived normally as a transient value to drive the UI calculations). If you are new to Pay Range derivation in Employee Central, please review the following article, which covers the entire topic of Pay Range derivation - 2136061 - How to determine which Pay Range is used in the Compa-Ratio and Range Penetration calculations - Employee Central
2. If you are creating the Job Information and Compensation Information data via Import or API, you need to ensure that the User Account has sufficient permissions to trigger rules on import of Job Information and Compensation Information.

Custom Implementation:

Create the needed custom fields in Manage Business Configuration > HRIS Element > compInfo. In our example, we will create 4 fields -

• Pay Range
• Pay Range - Minimum
• Pay Range - Maximum
• Pay Range - Custom Field

XML:

    <hris-field max-length="256" id="custom-string20" visibility="view" type="payRange" allow-import="true">
      <label>Pay Range</label>
      <label xml:lang="en-US">Pay Range</label>
      <label xml:lang="en-GB">Pay Range</label>
    </hris-field>
    <hris-field max-length="256" id="custom-double4" visibility="view" allow-import="true">
      <label>Pay Range - Minimum</label>
      <label xml:lang="en-US">Pay Range - Minimum</label>
      <label xml:lang="en-GB">Pay Range - Minimum</label>
    </hris-field>
    <hris-field max-length="256" id="custom-double5" visibility="view" allow-import="true">
      <label>Pay Range - Maximum</label>
      <label xml:lang="en-US">Pay Range - Maximum</label>
      <label xml:lang="en-GB">Pay Range - Maximum</label>
    </hris-field>
    <hris-field max-length="256" id="custom-string5" visibility="view" allow-import="true">
      <label>Pay Range - Custom Field</label>
      <label xml:lang="en-US">Pay Range - Custom Field</label>
      <label xml:lang="en-GB">Pay Range - Custom Field</label>
    </hris-field>

 Please note: the fields must be configured with the exact data types mentioned above ( pay range = payRange object, minimum and maximum = string)

Business Rules

Once you have created your fields, you must create 3 Business Rules (via Admin Center > Manage Business Rules).

• Go to Configure Business Rules
• Create new rule

Option:

For Basic

• Use Base Object : Compensation Information Model (recommended)

Or

for: Employee Central Core

 Select Use Trigger onSave Rules for HRIS Elements

• You can use this scenario to create rules that save changes to HRIS Elements. In Manage Business Configuration, rules created using this scenario can be registered only for the onSave event type.

Use Base Object: Compensation Information Model

1) Compensation Information

Please note that you must pay special attention to the Pay Range from Job Information rule function.

The rule can either be placed as onSave on the compInfo element (recommended), or you could also put this as an onChange rule if you want the rule to trigger during compInfo edit (optional).

2) Job Information

This will require knowing how your payRange object is configured, as you will need to consider the associated fields in your IF condition, to ensure the rules trigger when an associated value is changed.

In our below example, the Pay Range is associated with Legal Entity and Pay Grade. Therefore we need to ensure that whenever either of these values are changed in Job Information, that the Pay Range value and related fields in Compensation Information is updated.

Also note, this must be configured as 2 separate rules for several reasons -:

• compInfo onChange and onSave rules will not be triggered when the jobInfo rules create the Compensation Info data.
• You cannot set Pay Range and then update the related attribute fields in the same transaction

Option:

For Basic

• Use Base Object :Job Information Model (recommended)

for: Employee Central Core

• Use Trigger onSave Rules for HRIS Elements

You can use this scenario to create rules that save changes to HRIS Elements. In Manage Business Configuration, rules created using this scenario can be registered only for the onSave event type.

Use Base Object: Job Information Model

Rule 1: Set Pay Range

• Base Object: Job Information Model

Rule 2: Set Pay Range Fields

• Base Object: Job Information Model

The rules should be placed in the following order -:

XML

  <hris-element id="jobInfo">
    <label>Job Information</label>
    <label xml:lang="en-GB">Job Information</label>
    <label xml:lang="en-US">Job Information</label>
    <trigger-rule event="onSave" rule="JOB_SetPayRange_in_CMP"/>
    <trigger-rule event="onSave" rule="JOB_SetPayRangeFields_in_CMP"/>

Manage Business Configuration



FAQ - Additional Information

Q) Where can I get information on this from the Guide?

A) Guide : Implementing Business Rules in SAP SuccessFactors

    Guide:Implementing Employee Central Core   Chapter:Rule Scenarios for Employee Central Core

    Guide: Implementing Employee Compensation Data  Chapter: Example Business Rules  and Chapter: Showing the Pay Range in Job Information                                                                                                                      

• 2458839 - How to configure Pay Range in Positions
• 2271107 - How to export Pay Range Foundation Object for value check
• 2162127 - Compensation Information: Pay Component Group Calculations
• 2136061 - How to determine which Pay Range is used in the Compa-Ratio and Range Penetration calculations - Employee Central

Pay Range, Foundation Objects, Compa-Ratio, Range Penetration, Mid Point, Minimum Point, Maximum Point, Ad Hoc, Export, payRange, compa-ratio, range-penetration, compInfo, Compensation Information, , KBA , LOD-SF-EC-CMP , Compensation Information & One-Time Bonus , LOD-SF-EC-JOB , Job Information , How To