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.
Salary Basis with Simple Components
Summary:
Hi Everyone,
Content (required):
Our client would like to define salary basis with default values (amount/percentage) for components. The best option is to go ahead with simple components.
I have below 2 questions.
- Number of components are expected to change almost every year. There may be new components added with some as amount and some as percentage. I have 2 options for this.
-Add "Future Use" in the lookup and rename as and when they will be used. I personally don't like this design as I have to add the future use components in the salary basis definitions with type as amount or percentage which cannot be modified once salary basis is assigned to employees.
0