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.

Overriding a Missing Range Maximum

edited Sep 5, 2020 12:17AM in Compensation 2 comments

Summary

Range Maximum is missing for chunk of employees so merit increase is defaulting as a lump sum

Content

For some reason, the range maximum is not loading into Fusion for about ten percent of our workforce.  This results in any applied merit increase being paid as a lump sum instead of being applied as a pay adjustment.  Our HRIM team is working on this issue, but I thought I would reach out and see if this group had any ideas.  My concern, however, is that any override might enable any employees who are ARE over the max of the range to get an increase to base instead of a lump sum payment.

Howdy, Stranger!

Log In

To view full details, sign in.

Register

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