Oracle Fusion HCM Geographies Table

Oracle Fusion HCM does not have a single specific “geographies table” that stores all geographical information. Instead, the geographical data in Oracle Fusion HCM is typically distributed across several related tables within the application’s database schema.

Geographical data in Oracle Fusion HCM is associated with various components, such as countries, regions, cities, postal codes, and addresses. Each of these components may be stored in separate tables based on their specific attributes and relationships.

Here are some of the key tables in Oracle Fusion HCM that may store geographical information:

1. PER_LOCATIONS_ALL: This table stores location-specific information, such as country, state, city, postal code, and address details. It is used to maintain data about an organization’s physical locations.
2. PER_COUNTRIES: This table contains a list of countries and their corresponding attributes like country code, currency, and tax details.
3. PER_STATES: This table holds data about states or regions within a country.
4. PER_CITIES: This table contains information about cities within a country or state.
5. PER_POSTAL_CODES: This table stores postal code data associated with specific locations.
6. PER_LEGAL_ENTITIES: This table is used to store information about legal entities, and it may include attributes related to their geographical location.

Please note that the actual table names and structures might vary based on the specific version of Oracle Fusion HCM and the configured modules. Additionally, Oracle Fusion HCM might introduce changes and updates in subsequent releases, which could impact the data model and tables related to geographies.

If you need to access or work with geographical data in Oracle Fusion HCM, I recommend consulting with your organization’s technical experts, system administrators, or reviewing the Oracle Fusion HCM documentation to understand the specific data model and table structure related to geographies in your implementation.