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.
Compensation Zone - Two Zone for same Zone type for this Location/Person
Summary:
What are best practices regarding postal code range updates that move from one zone to another from year to year in order to prevent errors due to Two Zone for same Zone type for this location/person? In the Compensation Zone setup, under Associated Geographies, there is no delete or inactivate functionality for postal ranges and users can only update the End Date and not the Start Date on the UI.
Since we are unable to delete/inactivate any postal ranges, the end date is currently set to match the Start Date, however, this approach results in zone overlaps and multiple zone errors when running the ‘Generate Compensation Zone and Address’ process.
1