When implementing Oracle Fusion HCM Workforce Deployment, one of the most critical setup activities is configuring Geographies for Human Capital Management. Geographies act as the foundation for address data, tax validations, territory definitions, and overall data consistency across multiple Oracle applications. By carefully planning and setting up geography structures, hierarchies, and validations, organisations ensure that their HCM system not only maintains accurate employee and location information but also supports compliance and smooth integration with other modules such as Payroll and Financials. 

When setting up Oracle Fusion HCM Workforce Deployment, an essential configuration step involves defining Geographies, Geography Structures, and Geography Validations. 

You can bring geography data into the application using two methods: 

• Manual entry through the user interface, suitable for smaller datasets. 
• File-Based Data Import (FBDI), recommended when dealing with large or complex datasets, as it provides a faster and more efficient way to configure geographies. 

For data integrity purposes, once a geography hierarchy has been imported, you cannot create new geography structures or alter existing ones. Therefore, it is important to plan carefully before import. Consider the following: 

1. Include all necessary geography types that your application may require. For instance, you might want to define counties for potential use in sales territories, even if they are not currently used in address data. 
2. Account for cross-application needs, since geography reference data is shared across multiple Oracle applications. For example, financial applications may require specific geography structures to comply with local tax regulations. Even if you are not implementing financials at present, including these structures now can prevent rework in the future. 
3. Review the default address styles provided for each country you intend to import, and make adjustments where necessary to ensure they align with your organisation’s requirements. Address styles define the mandatory components of a street or tax address. You can access and modify them in the Setup and Maintenance work area by using the Manage Address Formats task. 
4. Validate the source and accuracy of your geography data before import to ensure consistency and reliability. 
5. From the Manage Geography Structure page, you can extend your country structure by adding additional geography types at the end of the hierarchy. 
6. If the geography hierarchy has not been loaded yet, you can insert additional geography types at any level within the structure. To do this, remove all geography types below the desired insertion point, add the missing type, and then re-add the ones you deleted. 

Take your expertise to the next level with our
Oracle Fusion HCM Core Implementation Training

Geography Model Concepts 

Geography 

A geography represents any defined geographic region, regardless of size. Examples of geographies include Kerala as a State, India as a Country, San Francisco as a City, Miami-Dade as a County, or Minato-ku as a Ward in Tokyo. 

Geography Type 

This refers to the category or label assigned to a geography, such as country, state, province, county, or city. 

Geography Structure

A geography structure outlines how geographic data is organised for a specific country. It defines which geography types are required for addresses and territories, and how these types relate to one another. Structures vary by country. For example, in the United States, cities and states are mandatory, while in Japan, the structure must include prefectures, municipalities, districts, and wards. 

Geography Hierarchy 

The geography hierarchy for a country is derived from its geography structure. It is a data model that defines parent–child relationships between different geographies. At the highest level, the hierarchy always begins with the Country, followed by its associated sub-geographies. 

For instance, within the hierarchy, the State of California is defined as the parent of San Mateo County, which in turn is the parent of Redwood City, which further contains the postal code 94065. When you enter only the postal code 94065, the application can automatically identify its location as Redwood City, within San Mateo County, in the State of California. 

Defining Geography Structure, Hierarchy, and Validation 

The following steps outline the process for setting up the Geography Structure, Geography Hierarchy, and Geography Validation specifically for India. 

These three components are interdependent when configuring a country in Oracle Fusion: 

• The Geography Structure must be defined first. 
• After finalising the geography structure, the next step is to set up the Geography Hierarchy. 
• Finally, the Geography Validation can be created, but only after the hierarchy is established. 

This sequence ensures that the application can correctly interpret and validate address and territory data for the selected country. 

Defining the Geography Structure 

For each country, you must first create a Geography Structure to determine which geography types belong to that country and how they are arranged in a hierarchy. 

For example, you might define geography types such as State, City, and Postal Code. In this case, the State would be the top level, the City would be the next level, and the Postal Code would sit at the lowest level of the structure. 

You can configure the geography structure using the Manage Geographies task in the Setup and Maintenance work area. 

Steps to Define the Geography Structure for India 

1. Navigate to the Manage Geographies page and enter IN in the Code field, then click Search. 
2. On the results page, click Structure Defined. 
3. On the Manage Geography Structure page, select Create under the Copy Country Structure From section. 
4. In the Geography Structure area, select State from the Add Geography Type dropdown and choose Add. 
5. Next, select City from the Add Geography Type dropdown and choose Add. Select Postal Code from the Add Geography Type field and click Add. 

Defining the Geography Hierarchy 

1. Navigate to the Manage Geographies page, enter IN in the Code field, and select Search. 
2. In the search results, choose Hierarchy Defined. 
3. On the Manage Geography Hierarchy page, within the Geography Hierarchy section, highlight India in the results table. 
4. Click Create to define a new hierarchy. 
5. On the Create State page, under the Primary and Alternate Names section, enter Tamil Nadu in the Name field. 
6. Click Save and Close. 
7. On the Manage Geography Hierarchy page, go to the Geography Hierarchy section and select Tamil Nadu to highlight the row. 
8. Click Create to add the next level. 
9. On the Create City page, under the Primary and Alternate Names section, enter Chennai in the Name field. 
10. Click Save and Close. 
11. On the Manage Geography Hierarchy page, under the Geography Hierarchy section, choose Chennai to select the corresponding row.
12. Click Create to add a new level.
13. On the Create Postal Code page, under the Primary and Alternate Names section, enter 600045 in the Name field. 
14. Click Save and Close. 

Defining Geography Validations 

Once the geography types have been added for India, the next step is to configure geography validations. This involves mapping geography types to attributes, enabling them for use in Lists of Values and Geography Validation, and setting the appropriate validation level. 

1. On the Manage Geographies page, select Validation Defined. 
2. On the Manage Geography Validation page, access the Address Style section and select the row called No Styles Format to move forward. 
3. In the Map to Attribute field, select State for the State geography type. 
4. Enable the List of Values option for the State geography type. 
5. Activate Geography Validation for the State geography type. 
6. In the Map to Attribute field, select City for the City geography type. 
7. Enable the List of Values option for the City geography type. 
8. Enable the Geography Validation option for the City geography type. 
9. In the Geography Validation Control section, set the Geography Validation Level for Country to Error. 
10. Click Save and Close to complete the setup. 

Address Style Format Configuration 

For every address style format, you can configure the following options: 

• Map to Attribute – Assign the geography type to the corresponding attribute. 
• Enable List of Values – Allow the geography type to appear in selectable lists. 
• Tax Validation – Specify validation rules for tax-related requirements. 
• Geography Validation – Activate this option to confirm that address details align accurately with the defined geography hierarchy. 
• Geography Validation Control – Define the level of enforcement (e.g., warning or error). 

Map to Attribute 

For each address style format, you can associate geography types with specific address attributes. For instance, in the United States, the State geography type can be linked to the State attribute, while in the United Kingdom, the State geography type might be mapped to the County attribute. The geography types that appear are based on how the country’s geography setup is defined, while the list of address attributes comes either from the standard address formats delivered with the application or from formats specifically designed by the organisation. 

Enable List of Values 

After mapping a geography type to an attribute, you can decide whether it should appear as a selectable list of values during address entry in the user interface. Careful consideration is needed before enabling this option. Enable a list of values only after sufficient geography data for that type has been loaded or created. Once enabled, users can only choose from the geography values that exist in the defined hierarchy. This means that if a particular geography value is missing from the hierarchy, it cannot be entered manually when creating an address. 

Tax Validation 

You can configure whether a geography type should be used for tax validation. For instance, within the North America address style format, you can include geography types like County, State, and City as part of tax validation. This ensures that whenever a transaction involves an address using the North America format, the system checks the accuracy of the county, state, and city combination against the defined geography hierarchy. Only when the details align correctly will the address be considered valid for tax calculation. 

Geography Validation 

You can configure whether a particular geography type participates in the geography validation process. For instance, when entering a U.S. address using the North America address style format, the system verifies that the country, state, and postal code combination matches the defined geography hierarchy to ensure it is geographically valid. 

Even if an address element is linked to a geography type but geography validation is not activated, the application will continue to suggest values as the address is entered. However, the system will not enforce validation on that element. 

Geography Validation Control 

You can specify the validation level for each country to determine how strictly geography validation is enforced. During address entry, the system checks whether the provided address details align with the available geography hierarchy data. The validation control setting decides whether an address that fails validation can still be saved. 

For example, if the validation level is set to Error, the system will prevent saving the address unless the entered values exactly match the hierarchy data. 

Geography Validation Levels 

The system provides different levels of geography validation that you can configure: 

• Error – Ensures that only fully valid addresses are saved, with all required address components entered correctly. 
• No Validation – Allows saving of addresses even if they are incomplete or contain invalid details. 

Conclusion 

A well-structured geography model is more than just a technical setup—it is the backbone of reliable data management in Oracle Fusion HCM. By defining the right geography structures, establishing accurate hierarchies, and enabling validations, businesses can ensure data integrity, improve address accuracy, and streamline cross-application processes. With a thoughtful approach to configuring Geographies for Human Capital Management, organisations can avoid future rework, support regulatory compliance, and build a scalable foundation for workforce operations.