Thank you for supporting the Cloud Customer Connect Community in 2024. It's a gift to work with you!

Look back
You're almost there! Please answer a few more questions for access to the Applications content. Complete registration
Interested in joining? Complete your registration by providing Areas of Interest here. Register
Get Started with Redwood for Oracle Cloud HCM   Begin Now
To ensure that questions get required attention from community members and are NOT left unanswered, it’s important for the author to indicate (by selecting “Yes” or “No” when prompted) whether the question was answered. (newly added) Please note that it is also important to respond to EACH comment your question receives. Your Yes or No response ensures an accurate status for your question.

For more information, please refer to this announcement explaining best practices for getting answers to questions.

Validating Hourly Paid or Salaried Value and Job Exemption Status

Summary:

We have a requirement where Job Exemption Status and Hourly Paid or Salaried value should be aligned. If the Job Exemption is EXEMPT then Hourly Paid or Salaried should be Salaried and if Job Exemption is NONEXEMPT then Hourly Paid or Salaried should be Hourly. During a transaction like Hire and Employee, Promote, Transfer etc, when Manager changes the Job or Hourly Paid or Salaried value and if the new values are not aligned, the system should throw and error to correct the values. This is an approved Use Case.

The Object validation rule is working when the Job is changed from Exempt to Non-Exempt or vice-versa without changing the Hourly Paid or Salaried value. The system is throwing an error as expected. But in cases where Job is not changed but Hourly Paid or Salaried is changed from Hourly to Salaried or vice-versa, the rule is not triggering and is allowing the user to continue without any error.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

Don't have an account? Click here to get started!