ORC vs Core HR geographies: is there an Oracle best practice for alignment?

Hi team!

We are implementing Oracle Recruiting Cloud in a multi-country Oracle Cloud HCM project and would like to understand whether there is an established best practice on how the Recruiting geography configuration should relate to what is configured in Core HR.

What the documentation says (Implementing Recruiting, chapter “Geography Hierarchies”, release 26C):

• Recruiting uses the geographies managed in HCM (master geography, Manage Geographies), and the Geography Hierarchy Structure and Geography Hierarchies tasks define a limited universe on top of it.
• As a best practice, the Geography Hierarchy should include only the locations where hiring activities occur (e.g. cities with physical offices), to ease selection and avoid performance issues.