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.
For more information, please refer to this announcement explaining best practices for getting answers to questions.
Limit MSS Salary Change Effective Dates
Content
We have manager self-service enabled for the Salary Change quick action, and we're looking at what our options are to help reduce errors and complexity for our managers.
One scenario we're looking at is the ability to restrict the effective date of these transactions (submitted by MSS) to be after the effective date of the last salary transaction. This would prevent a situation where a manager submits a change, but then a future dated salary change is applied, unbeknownst to the manager at the time of submission, and changes the employee's salary.
Would love to hear if anyone else has faced something similar - and if so how you've addressed it!
1