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.
User-defined tables or default values kept in the eligibility profiles for benefits?
Summary:
Hello,
We need to create some benefits in Oracle for which the main eligibility criteria and standard amounts are determined by grade.
We are analyzing two ways of doing the setup:
- Create user-defined tables and keep the standard values for each grade in these tables;
- Create elements with eligibility criteria grade and add the standard values as default amounts at the element eligibility level.
However, we haven't found enough documentation to be able to assess which approach would be more appropriate.
Does anyone have experience with this? Which would be the pros and cons for user-defined tables versus element default amounts? We are taking into consideration that the standard values will have to be updated on a regular basis (most probably yearly) and we will need to get the default amounts both at element entry level and in workforce compensation.
0