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.
How to keep the values of the Change Statements static once generated for those Centrally Managed?
Our previous compensation campaign has completed last year and the “Process Workforce Compensation Change Statements” has been ran.
It used to display the year 2023 on the texts and also the date when it was posted “April 6, 2023”
However, we noticed today that when generating the template again, it now displays 2024 and the current date “January 18, 2024”.
We were expecting that the dates in the statement will remain static in the Compensation Change Statement page of the employee since it was already generated.
Is there anything that we should do in the plan configuration to keep the values the same as when we generated them?
0