Skip to Content
Author's profile photo Anil Sule

Position Management – Pay Scale Structure in Position Object

SuccessFactors EC Position Management is a very powerful EC Module that makes the Process of managing Positions very easy in addition to being the base for Succession Management and Recruiting Management Modules.

Earlier, Customers implementing EC have skipped implementing this Module, while it was in the Delta mode. But now that the Solution has matured, more and more Customers are implementing Position Management Module as part of their EC Rollout. Customers who had skipped Position Management are also implementing this Module now.

SF EC Position Management can be configured to synchronize the Data from Position to Employee JobInfo and vice versa. Customers are increasingly trending to put more and more of the Employee JobInfo fields on the Position and synchronize these fields from Position to Employee JobInfo.

One of the challenges in SF EC Position Management has been the inclusion of the Pay Scale Structure – which consists of the 4 fields – Pay Scale Area – Pay Scale Type – Pay Scale Group – Pay Scale Level. These are Generic Objects. These Objects are used in the 4 fields with those names in the Employee JobInfo and are built to be filtered from top to bottom. Customers can now include these fields in the Position Object and have the same filtering built on the Position Object and synchronize these fields to the Employee JobInfo

This blog details the configuration to enable the filtering of the Pay Scale Structure from top to bottom. With these steps you’ll be able to add Pay Scale Structure fields on the Position Object and filter it in the same way as on Job information. This is not delivered standard.

The steps are:


Pay Scale Structure fields in Employee JobInfo should be migrated from picklists to Generic Objects. This process is detailed in the Employee Central Master Implementation Guide Q12017 at  12.1.1 Pay Scale Type and Pay Scale Area Fields


Step 1.

If you do not already have it – Configure a Custom Field in Position Object for Country with Technical Name – cust_Country of type ‘Generic Object’ with Valid Values Source ‘Country’. You can label it anything you want. You can make  it ‘Read Only’ if you want.

Step 2.

Write an always true rule to set the value of this field based on the Country field value of the Legal Entity. Place this rule on the Legal Entity field of the Position Object

Step 3. Configure 4 Custom Fields on the Position Object of type ‘Generic Object’.

Technical Names -> cust_PayScaleArea, cust_PayScaleType, cust_PayScaleGroup and cust_PayScaleLevel.

Label these fields as -> Pay Scale Area – Pay Scale Type – Pay Scale Group – Pay Scale Level respectively and define the Valid Values Source as ‘PayScaleArea’, ‘PayScaleType, ‘PayScaleGroup’ and ‘PayScaleLevel’ respectively. These fields should be ‘Editable’

Step 4. Configure Field Criteria on Position fields as below:

Field -> Pay Scale Area -> Source Field Name = country Destination Field Value = cust_Country

Field -> Pay Scale Type -> Source Field Name = country Destination Field Value = cust_Country

Field -> Pay Scale Group -> Source Field Name = payScaleArea Destination Field Value = cust_PayScaleArea

Field -> Pay Scale Group -> Source Field Name = payScaleType Destination Field Value = cust_PayScaleType

(Note that there are 2 Field Criteria for Pay Scale Group)

Field Pay Scale Level -> Source Field Name = payScaleGroup.internalId Destination Field Value = cust_PayScaleGroup

(Note to ensure that you have a One-2-One association on PayScaleLevel Object with PayScaleGroup)

Step 5.

Save the Position Object and Test. You will be able to filter the Pay Scale Structure from top to bottom.

Step 6.

You can include these fields in your Pos2Job Synchronization Rule if you want them to be Synchronized. Include these fields in your CopyPosition Rule. Include these fields in your Pos2Job Propagation Rule that you have on the Position field on JobInfo.

This Configuration is facilitated by the ‘Business Key Fields‘ functionality that has been built into Generic Objects. Ensure that these fields exist in the GO’s and if not, enter them.

In the PayScaleArea GO, you will have the below as Business Key Fields:

  • country
  • payScaleArea

In the PayScacleType GO, you will have the below as Business Key Fields

  • country
  • payScaleType

In the PayScacleGroup GO, you will have the below as Business Key Fields

  • country
  • payScaleArea
  • payScaleType
  • payScaleGroup


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Manish Angane
      Manish Angane


      this is a very nice blog ..thank u question about propagation rule from position object to job information  the new custom fields pay scale area,level ,type group does not propogate to job information.

      Can you please comment on this issue.


      Thanks and regards

      Manish Angane

      Author's profile photo Emad Massoud
      Emad Massoud


      I tried this and worked well. One question. How to make the list of positions in jobinfo irrelevant to the employee's legal entity