Salary Range Violation Behavior for Proposed Salaries

Specify how to handle salary range violation for various compensation actions, such as Change Salary and Salary History. This handling also applies to Offer and HR actions that include the Salary section, such as Offer, Hire, Promote, and Transfer.

You configure violation behavior using the Salary Range Violation Behavior field of the salary basis. You can let people propose salaries that violate the salary range with or without a warning. Or, you can prevent people from proposing any salaries that violate the salary range. For example, you warn people when their proposed salaries are below or over the specified salary range. Or, you don't let anyone propose salaries that are below or over the specified salary range.

The default value for the Salary Range Violation Behavior field of all existing salary bases is Warn. We don't recommend that you change it to Error for existing salary bases because you can get errors with historic data. For example, you've an existing salary basis with a salary range of 100 to 200 USD. The salary basis is associated with a 2010 salary record where the salary amount was 95 USD. It's also associated with a 2015 salary record where the salary amount was 105 USD. When you change the violation behavior to Error and try to load salary for 2020, you can get the violation error for 2010. The error occurs even though that's not the record you're correcting. To set the violation behavior to Error, then we recommend that you create another salary basis to use with new salaries. This way, you can avoid issues with historic data.

When you set the violation behavior to Warn, you don't see the warning message when you load salaries using these tools: REST API, HCM Data Loader, and HCM Spreadsheet Data Loader. These tools show you only errors. The Download Salaries task and grate step progression processes ignore this violation behavior.