Implementation Considerations for Salary Processes

Here are the considerations for the Change Salary and Salary History processes.

Change Salary

You can typically use field value defaulting and validation in these cases.

• Default the proposed salary basis when employee legal employer is Vision when line managers propose salary change.
• Default the effective date to current date and next salary review date to 1 year after the effective date, when line managers propose salary change.
• Default the salary basis based on assignment flexfields when line managers propose salary change.
• Default salary basis for a full time employee belonging to US and a certain grade.
• Validate that the when date isn't in the past.
• Validate that the salary amount isn't below a minimum value.
• Validate that the when start date is 1st of next month.
• Validate that the user hasn't changed the rate component value.
• Advanced expressions working on Global HR and Recruiting pages need to be updated somewhat to work on the Change Salary page.

Note: Business rule defaults happen only on the first visit to the Salary section. They don't happen again, even if changes were made to other sections.

This table lists the supported attributes, exceptions, and the implementation recommendations for the My Team > Change Salary and My Client Groups > Change Salary pages.

In the Conditions	To Default Field Values	To Validate Field Values	Implementation Guidelines
User Roles Legal Employer Business Unit Country Start Date Action Reason Assignment attributes including Assignment Category Assignment Status Bargaining Unit Department FTE Full time or part time Grade Grade Code Grade Ladder Grade Ladder Step Salary Range Default Value (Grade Rate Value) Hourly or Salaried Hourly Paid or Salaried Job Job Code Job Family Job Function Legal Employer Legislation Code Location Next Payroll Start Date Payroll Start Date Person Assignment Union Person Assignment Union Member Person Type Position Position Budget Value Position Code Position Standard Working Hours Primary Work Relationship Termination Date US Job Info Overtime Status Worker Category Working Hours Working Hours Frequency Additional Assignment Info segments Assignment Flex Departments Flex Grade Ladders Flex Grades Flex Jobs Flex Positions Flex	Start Date Action Reason Proposed Salary Basis Salary Amount Next Salary Review Date	User Roles Legal Employer Business Unit Country Start Date Action Reason Assignment attributes including Assignment Category Assignment Status Bargaining Unit Department FTE Full time or part time Grade Grade Code Grade Ladder Grade Ladder Step Hourly or Salaried Hourly Paid or Salaried Job Job Code Job Family Job Function Legal Employer Legislation Code Location Next Payroll Start Date Payroll Start Date Person Assignment Union Person Assignment Union Member Person Type Position Position Budget Value Position Code Position Standard Working Hours Primary Work Relationship Salary Range Minimum Salary Range Midpoint Salary Range Maximum Salary Range Default Value (Grade Rate Value) Termination Date US Job Info Overtime Status Worker Category Working Hours Working Hours Frequency Simple Components Rate Components Additional Assignment Info segments Assignment Flex Departments Flex Grade Ladders Flex Grades Flex Jobs Flex Positions Flex	Defaulting Salary amount can be defaulted when using the user determined type of salary basis only. Fields in the salary section can be defaulted based on the fields listed "in the conditions" column of this table. Initial Field Values and Target Fields on salary fields are now supported. When there's more than one assignment on the same day, details from the highest sequenced assignment will be considered. Warnings are triggered on clicking Continue in a CGP flow and hence can't be seen by the user.

Salary History

You can typically use field value defaulting and validation in these cases.

• Default the proposed salary basis based on the employee's legal employer when compensation managers propose a salary change.
• Default the effective date to first day of next month and next salary review date to 1 year after the effective date, when line managers propose a salary change.
• Default the salary basis based on assignment flexfields when proposing salary change.
• Validate that users don't enter retro-active salary changes.
• Validate that the change of salary occurs on the first of the month.
• Validate that the salary amount is above a minimum value.
• Validate that users don't change a simple component value.
• Validate that users don't enter a zero value for a simple component.
• Validate the sum of a certain simple component is based on a formula (Adjustment needs to be sum of all components minus cost of living).
• Advanced expressions working on Global HR and Recruiting pages need to be updated somewhat to work on the Salary History page.

Note: Business rule defaults happen only on the first visit to the Salary section. They don't happen again, even if changes were made to other sections.

This table lists the supported attributes, exceptions, and the implementation recommendations for Salary History. It applies to the My Client Groups > Admin Salary History page.

In the Conditions to Default Values	To Default Field Values	In the Condition to Validate Values	To Validate Field Values	Implementation Guidelines
User Roles Legal Employer Business Unit Country Start Date Action Reason Assignment attributes including Assignment Category Assignment Status Bargaining Unit Department FTE Full time or part time Grade Grade Code Grade Ladder Grade Ladder Step Salary Range Default Value (Grade Rate Value) Hourly or Salaried Hourly Paid or Salaried Job Job Code Job Family Job Function Legal Employer Legislation Code Location Next Payroll Start Date Payroll Start Date Person Assignment Union Person Assignment Union Member Person Type Position Position Budget Value Position Code Position Standard Working Hours Primary Work Relationship Termination Date US Job Info Overtime Status Worker Category Working Hours Working Hours Frequency Additional Assignment Info segments Assignment Flex Departments Flex Grade Ladders Flex Grades Flex Jobs Flex Positions Flex	Start Date Action Reason Proposed Salary Basis Salary Amount Next Salary Review Date	User Roles Legal Employer Business Unit Country Start Date Action Reason Assignment attributes including Assignment Category Assignment Status Bargaining Unit Department FTE Full time or part time Grade Grade Code Grade Ladder Grade Ladder Step Hourly or Salaried Hourly Paid or Salaried Job Job Code Job Family Job Function Legal Employer Legislation Code Location Next Payroll Start Date Payroll Start Date Person Assignment Union Person Assignment Union Member Person Type Position Position Budget Value Position Code Position Standard Working Hours Primary Work Relationship Salary Range Minimum Salary Range Midpoint Salary Range Maximum Salary Range Default Value (Grade Rate Value) Termination Date US Job Info Overtime Status Worker Category Working Hours Working Hours Frequency Simple Components Rate Components Additional Assignment Info segments Assignment Flex Departments Flex Grade Ladders Flex Grades Flex Jobs Flex Positions Flex	Not Applicable	Salary amount can be defaulted when using user determined type of salary basis only. Defaulting is supported when salary is being created and not on correction of existing salary. When there's more than one assignment on the same day, details from the highest sequenced assignment will be considered. Warnings are triggered on clicking Continue in a CGP flow and hence can't be seen by the user. Validations can't be performed across salaries. Initial Field Values and Target Fields on salary fields are supported now. Validations will be triggered on clicking Save or OK button and not on clicking Submit button.