Skip to content
EBS Reference

HZ_LOCATIONS

Schema: ARmaster

The physical address master — pure address rows with no party context; one location can serve many parties, customer sites, and supplier sites

Identity
Module: Customers (TCA)Not org-partitioned
Notes

STATE and PROVINCE are separate columns — pick by country. COUNTRY holds the territory code, not a name.

What the badges mean
Schema: INV
Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Structural facts — how the table is partitioned, not a trap by itself

OU-striped (ORG_ID)
Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on ORG_ID, and don’t confuse it with ORGANIZATION_ID (see the quirks guide).
Per inventory org
Rows are scoped to an inventory organization (plant or warehouse) via ORGANIZATION_ID — a different partition from OU-striped tables (see the quirks guide).
Language-striped
The table carries a LANGUAGE column (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to one LANGUAGE or a join multiplies rows (see the quirks guide).

Join & extract hazards — verify before you rely on this

View
This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
In field listings, the Key chip marks a primary-key field.

Fields

13 fields · 1 key

13 fields.

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1LOCATION_IDSurrogate key of the addressNUMBER
Primary-key field
2ADDRESS1Address line 1 — the only mandatory lineVARCHAR2
3ADDRESS2Address line 2VARCHAR2
4CITYCityVARCHAR2
5STATEState — US-style; non-US addresses use PROVINCEVARCHAR2
6PROVINCEProvince — separate column from STATE; pick by countryVARCHAR2
7POSTAL_CODEPostal/ZIP codeVARCHAR2
8COUNTYCountyVARCHAR2
9COUNTRYCountry — the territory code, not a nameVARCHAR2
10ADDRESS_STYLEAddress format styleVARCHAR2
11VALIDATED_FLAGWhether the address has been validatedVARCHAR2
12ORIG_SYSTEM_REFERENCEThe legacy/source-system keyVARCHAR2
13CREATED_BY_MODULEWhich application created the addressVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading HZ_LOCATIONS on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters

4 parameters not filled: <catalog>, <schema>, <LOCATION_ID>, <watermark>

-- ============================================================
-- Table  : HZ_LOCATIONS — The physical address master — pure address rows with no party context; one location can serve many parties, customer sites, and supplier sites
-- Purpose: Column-selected read of HZ_LOCATIONS — auto-generated from field metadata
-- Grain  : One row per LOCATION_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.LOCATION_ID AS "Surrogate key of the address",
  t.ADDRESS1 AS "Address line 1 — the only mandatory line",
  t.ADDRESS2 AS "Address line 2",
  t.CITY AS "City",
  t.STATE AS "State — US-style; non-US addresses use PROVINCE",
  t.PROVINCE AS "Province — separate column from STATE; pick by country",
  t.POSTAL_CODE AS "Postal/ZIP code",
  t.COUNTY AS "County",
  t.COUNTRY AS "Country — the territory code, not a name",
  t.ADDRESS_STYLE AS "Address format style",
  t.VALIDATED_FLAG AS "Whether the address has been validated",
  t.ORIG_SYSTEM_REFERENCE AS "The legacy/source-system key",
  t.CREATED_BY_MODULE AS "Which application created the address"
FROM <catalog>.<schema>.HZ_LOCATIONS t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.LOCATION_ID = <LOCATION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.LOCATION_ID;

Verified September 2026

Relationships

Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • AP_SUPPLIER_SITES_ALLHZ_LOCATIONSforeign key · N:1
    ON AP_SUPPLIER_SITES_ALL.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID
  • HZ_PARTY_SITESHZ_LOCATIONSforeign key · N:1
    ON HZ_PARTY_SITES.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID

Browse more Customers (TCA) tables

More Customers (TCA) tables

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.