2675587 - Pay Scales: How to Improve the performance on Pay Scale Indirect Valuation using Business Rules

The current implementation method for Pay Scale Indirect Valuation rules (described in the "Implementing and Configuring Employee Compensation Data in Employee Central" handbook) is 1x Indirect Valuation rule to 1x Pay Component. For customers with very large Pay Structures, this methodology would require having a lot of Pay Scale Indirect Valuation rules (for example more than 10 - but this method can be implemented if there are less as well).

If you are using Business Rules to deliver further automation, then you could end up with a lot of rules, and then need to work on consolidating/improving their implementation to get better performance from the UI/system.

When customer has numerous Pay Scale based Pay Components, each Pay Component mandates creation of a unique Business Rules and hence the overall rule count in the system grows. This in turn impacts system performance during transactions in the UI (save times), Job Info Imports and Interfaces when executing Business Rules will also be impacted because many rules need to be executed for each record. Some other reasons why you might want to implement the Indirect Valuation rules slightly differently, could be because:

• Hourly employees can be assigned multiple/many different Recurring Pay Components.
• These Pay Components can be different for different groups of employees and is based on specific Pay Scale Structure
• Current configuration design is to write an indirect evaluation business rule per pay component..

Environment

• SAP SuccessFactors Employee Central

Resolution

The following solution should be implemented to improve the Import and UI times, when customer has implemented Business Rules heavily and also has large Pay Scale structures to manage.

The idea in the below solution, is to assigned all of the Pay Components at the same time, with the same rule, instead of having 1 rule per Pay Component

Indirect Valuation using Sequence Number

1) First you need to add a new "Number" field to the following 2 MDF objects:

• PayScaleLevel
• PayScalePayComponent

2) Create the Indirect Valuation (onSave) rule: Here is an example of what that rule would look like (just the 1 rule is needed):

IF

ELSE IF

Performance Improvement:

• Overall Transactions times are improved both via Import and UI (this is subjective to how many rules you have, how clean the logic is of the rules, and how you configured the rest of element)
• Using the number of Pay Components and Sequence Number, one business rule can be implemented instead of “as many rules as Pay Components based on Pay Scale Level”.
• The same rule would also accommodate for any future additions of Pay Components to Pay Scale Level or addition of new Pay Scales Levels to the Pay Structure.

Please refer to the "Implementing and Configuring Employee Compensation Data in Employee Central" handbook for further guidance on configuring this Pay Scale scenario.

See Also

2575134 - How to Add a custom association to PayScale Objects

Keywords

pay scale, payScaleLevel, indirect valuation, onSave, jobInfo, Pay Structures, ec, pay component, , KBA , LOD-SF-EC-CMP , LOD-SF-EC-JOB , How To