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.
Guardrail for dates to transactions to be back-dated
Summary:
Hello Experts,
Got a requirement on Back dated transaction. any inputs on this are really appreciable.
1. Identify a guardrail for dates to transactions to be back-dated (a maximum of 60 days) (Change Assignment, Promotion, Demotion, Transfer, Global Transfer, Salary Change, and create a work relationship. Example of this type of issue is a rate increase was not entered into Oracle HCM in April 2023 when all other team members receive their rate increase. Almost a year goes by and it is just identified Oracle does not display the correct pay rate. HR typically would log into HCM and back-date a Salary Change to April 2023. We don't want the HR sites to back-date that far
0