Optimize Obsolete Geography Hierarchies
NOTE: This feature isn't intended for unauthorized use by customers. Instead, it's a specialized tool that should only be used when recommended by the Oracle Support team in specific circumstances. The Oracle Support team will guide the customer on its proper use. Testing in a non production pod will be necessary to validate the desired outcomes are achieved. This will ensure the feature is used effectively and in the right context to address the customer needs.
As an administrator, you can optimize your geography hierarchies. A new action button called Optimize Hierarchies is available on the Geography Hierarchies page. Two actions are available:
- Update Objects to Latest Nodes: Use this action to update Recruiting objects using hierarchies, so that these objects use geography nodes from the active hierarchy instead of nodes from ended hierarchies when possible. Objects will be updated only if the active hierarchy contains a node referring to the same geography.
- Delete Unused Hierarchies: Use this action to delete hierarchies which aren't used by any objects. These hierarchies will be deleted. Only hierarchies which are ended (no longer active) and which none of the geography nodes are referenced by Recruiting objects will be deleted. Draft hierarchies aren't deleted.
Geography Hierarchies Page
To determine if a Recruiting object uses geography nodes from a hierarchy, the system looks for such nodes in gigs, job requisitions, and job requisitions from Workforce Modeling. These are the only Recruiting objects keeping references to geography nodes.
This enhancement improves system performance for customers who have a lot of geography hierarchies.
Steps to Enable
You don't need to do anything to enable this feature.
Key Resources
For more information on geography hierarchies, refer to this topic in the Implementing Recruiting guide available on Oracle Help Center: