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.
VALUE DEFINITIONS AND RANGE ITEMS: MODEL CHANGES
Summary:
VALUE DEFINITIONS AND RANGE ITEMS: MODEL CHANGES
Content (required):
Hi Team,
Greetings!
Considering that all data for value definitions and range items will be migrated to the new model by 24A release -have anyone started or have moved to new model?
This is about replacing the usage of tables with database views e.g.
PAY_RANGE_ITEMS_F table to be replaced with PAY_RANGE_DEFS_V
PAY_RANGE_ITEMS_F table to be replaced with PAY_RANGE_INST_V
PAY_VALUE_DEFINITIONS_F table to be replaced with PAY_VALUE_DEFS_V
PAY_VALUE_DEFINITIONS_F table to be replaced with PAY_VALUE_INSTANCES_V
Tagged:
0