Locations in Oracle Fusion Cloud Financials

Introduction

In the earlier topics, we covered the enterprise, legal entities, legal reporting units, business units, and reference data sets. Another foundational setup object is the Location. Locations store physical address information and related details for the places where an organization operates, and they are used across Financials, HCM, Procurement, and Supply Chain. Although a location looks like a simple address record, it plays a significant role in tax determination, shipping and billing, worker assignment, and statutory reporting.

1. What Is a Location?

A Location in Oracle Fusion is a record that defines a physical place, such as an office, warehouse, plant, store, or any site used by the enterprise. It holds an address together with supporting information such as a name, code, time zone, contact details, and the purpose the location serves.

Key points:

A location is not an organization. It does not own transactions or have its own accounting. It is a descriptive record that other objects reference.
A location is reusable. Once created, it can be referenced by many other setup objects and transactions.
Locations are shared across pillars. The same location used for a worker’s work address in HCM can be used as a ship-to or bill-to address in Procurement and Financials.

2. Why Locations Matter

Locations support several processes in Fusion:

Address defaults: Documents such as purchase orders, invoices, and requisitions use locations for ship-to and bill-to addresses.
Tax determination: Tax calculations often depend on the physical place of the transaction, so accurate addresses and countries are critical.
Worker assignment: In HCM, every worker assignment references a location, which drives work address, legislative information, and sometimes payroll and time zone behavior.
Inventory and logistics: Warehouses and inventory organizations are linked to locations.
Statutory and legal addresses: Legal entities and legal reporting units use addresses that are tied to location-type information.
Reporting: Reports can group or filter data by location, for example headcount by site or purchases by delivery location.

3. Key Attributes of a Location

When you create a location, you supply information such as:

Name and code: A unique identifier and descriptive name for the site.
Effective start date: Locations are date-effective, so changes can be tracked over time.
Set: The reference data set that the location belongs to. This controls which business units or organizations can see and use it.
Address details: Country, address lines, city, state or province, postal code, and county. The address format adapts to the country selected.
Time zone: Used for scheduling, time-related processing, and display.
Geography: Links the location to geographic hierarchy data used for tax and address validation.
Contact details: Phone, fax, and email.
Ship-to and bill-to settings: Indicators of whether the location can serve as a delivery or invoicing address, and which ship-to location it defaults to.
Inventory organization link: If the location relates to a warehouse or inventory organization.
Description and additional information: Free-text details and, in some cases, descriptive flexfields for country-specific attributes.

Because addresses differ globally, Fusion uses country-specific address styles. Selecting the country changes which fields are shown and which are mandatory.

4. Locations and Reference Data Sets

Locations are one of the objects that use reference data sharing. Each location is assigned to a set when it is created. The set determines which organizations can use it.

A location in the Common Set is visible everywhere.
A location in a regional or business unit set is visible only to units assigned to that set.

This matters when you design your sets. For example, a warehouse in Germany might belong to a Europe set so that only European business units see it in lists of values, while a global headquarters location might sit in the Common Set. In HCM, location sets are typically tied to the business unit or reference data determinant configured for locations, so the set strategy should be agreed across Finance and HR.

5. Creating and Managing Locations

Locations are maintained through the Manage Locations task in the Setup and Maintenance work area. This task belongs to the Define Enterprise Structures area (and related workforce structure areas in HCM).

Typical steps

Open Manage Locations and select Create.
Enter the name, code, and effective start date.
Select the reference data set.
Choose the country and enter the address.
Specify the time zone and contact information.
Set ship-to, bill-to, and receiving flags as appropriate.
Link to an inventory organization or other related object if needed.
Save and close.

Other ways to load locations

For large implementations, locations can be loaded in bulk using File-Based Data Import or HCM Data Loader, using the location templates. This is especially useful when migrating hundreds of sites from a legacy system.

Date-effective changes

Because locations are date-effective, you can update an address from a future date without losing the history. If a site closes, you end-date the location rather than deleting it, which preserves references from past transactions and assignments.

6. Where Locations Are Used in Financials

Procurement and Purchasing

Requisitions, purchase orders, and agreements use locations in several ways:

Ship-to location: Where goods are to be delivered.
Bill-to location: The address to which the supplier sends invoices.
Deliver-to location: A more specific internal destination, such as a department or building.

These come from locations that are flagged as ship-to or bill-to sites and are visible to the business unit through its set assignment.

Payables

Supplier invoices carry location information for tax purposes, and Payables defaults the bill-to location from the business unit. Fusion Tax may use the ship-to or bill-to location to decide the tax jurisdiction and which tax rules apply.

Receivables

Receivables transactions identify the customer’s bill-to and ship-to addresses, but the business unit’s own location information can feed ship-from and registration details on invoices. Tax determination in Receivables relies on both customer and internal locations.

Tax

Fusion Tax uses addresses to determine place of supply and tax jurisdiction. Whether a transaction is domestic or cross-border, state or local, often depends on the location. Incorrect or incomplete locations commonly lead to wrong tax results or failed tax determination.

Inventory and Supply Chain

Inventory organizations, subinventories, and warehouses are associated with locations. Shipping, receiving, and transfer processes depend on those relationships.

Fixed Assets

In Fixed Assets, asset locations are defined through a separate asset location flexfield, but the enterprise location can still support the physical identification of sites where assets reside. Organizations often align the two for consistency.

7. Where Locations Are Used in HCM

Although this series focuses on Financials, locations are heavily shared with HCM, so it helps to understand their role there:

Worker assignments: Every assignment has a location, which determines work address, time zone, and sometimes statutory information.
Departments and organizations: Organizations can have a default location.
Legislative and payroll behavior: In some countries, the work location influences tax withholding and social insurance.
Directories and self-service: Employee directories show work location details.

Because both Finance and HR rely on the same location records, changes must be coordinated. Altering a location’s address affects both procurement defaults and worker work addresses.

8. Locations Versus Related Concepts

Concept	Purpose	Nature
Location	Physical address and site information	Descriptive record, reusable
Legal Entity	Legally accountable company	Organization with legal standing
Legal Reporting Unit	Registered establishment for tax and statutory reporting	Part of a legal entity
Business Unit	Transaction processing and security	Operational organization
Inventory Organization	Warehouse or plant tracking inventory	Supply chain organization
Asset Location	Where assets physically reside	Fixed Assets flexfield

A location is simply an address-based record. The legal entity, legal reporting unit, and inventory organization may each use a location, but the location itself carries no legal, accounting, or security meaning.

9. Practical Example

Consider “Global Foods Group”:

Headquarters, New York: Created in the Common Set, available to all business units. Flagged as bill-to location for the US business unit.
Distribution Center, Chicago: Created in the North America Set. Flagged as ship-to and linked to the Chicago inventory organization.
Office, London: Created in the Europe Set, with the UK time zone and country set to United Kingdom.
Warehouse, Frankfurt: Created in the Europe Set, flagged as ship-to and receiving location, linked to the Frankfurt inventory organization.

A buyer in the UK Sales BU creating a purchase order can see the London office and the Frankfurt warehouse (Europe Set) plus the headquarters (Common Set), but not the Chicago site. The ship-to location chosen on the order also feeds tax determination and delivery instructions. When a new employee joins in London, HR assigns them the London location, and their work address is derived automatically.

10. Best Practices

Standardize naming conventions. Use a consistent code and name format, for example city plus site type, so locations are easy to find.
Plan the set strategy first. Decide which locations are global, regional, or unit-specific before loading data.
Capture accurate addresses. Complete and correct addresses are essential for tax and shipping. Validate postal codes and geography information.
Do not duplicate locations. Create one record per physical site and reuse it, rather than making copies for different departments.
Coordinate with HR and Supply Chain. Because locations are shared, agree on ownership and change control.
Use effective dating properly. End-date rather than delete, and plan future-dated address changes carefully.
Set ship-to and bill-to flags deliberately. Only mark sites that genuinely serve those purposes, so lists of values stay clean.
Use bulk loading for migration. Use import templates for large volumes, and test with a small sample first.
Maintain time zones correctly. Incorrect time zones can affect scheduling and time-based processing.
Review regularly. Close sites that are no longer used to keep lists manageable.

11. Common Mistakes to Avoid

Creating a location in the wrong set, so intended business units cannot see it.
Confusing locations with legal reporting units or business units, and expecting locations to carry legal or accounting meaning.
Leaving out geography or country details, causing tax determination errors.
Duplicating the same physical address across several location records.
Deleting or overwriting locations instead of end-dating, losing history.
Marking every location as ship-to and bill-to, which clutters selection lists.
Changing an address without checking its impact on HCM assignments and open purchase orders.
Not aligning Finance and HR on a shared location design.

12. Troubleshooting Tips

If a location does not appear in a list of values or causes an error:

Confirm the set that the location belongs to and that the business unit is assigned to it, or that the location is in the Common Set.
Check that the location is active and its effective dates cover the transaction date.
Verify that the ship-to or bill-to flag is selected if the location is used for that purpose.
Review the country and geography values if tax determination is failing.
Ensure the user’s data access and the business unit context are correct.

Conclusion

Locations in Oracle Fusion Cloud are reusable records of the physical places where an enterprise operates. They are simple in form but wide in impact, feeding addresses to purchase orders and invoices, supporting tax determination, defining worker work sites in HCM, and linking to inventory organizations. Because locations use reference data sets, they can be shared globally or restricted to particular business units, which demands thoughtful planning of the set structure.

By designing locations carefully, with accurate addresses, appropriate sets, consistent naming, and coordination between Finance, HR, and Supply Chain, an organization ensures that the physical dimension of its structure is reliable. Together with the enterprise, legal entities, legal reporting units, business units, and reference data sets, locations complete the foundational enterprise structure on which the rest of Oracle Fusion Financials is built.

O SUPPORT

Search This Blog