HZ_LOCATIONS

-- ============================================================
-- Table  : HZ_LOCATIONS — The location master — the physical postal address itself (street, city, postal code, country, coordinates), shared by every party and account site that points at it
-- Purpose: Column-selected read of HZ_LOCATIONS — auto-generated from field metadata
-- Grain  : One row per LOCATION_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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",
  t.ADDRESS2 AS "Address line 2",
  t.CITY AS "City",
  t.STATE AS "State",
  t.POSTAL_CODE AS "Postal code",
  t.COUNTRY AS "Country territory code — required",
  t.LATITUDE AS "Latitude for proximity analysis",
  t.LONGITUDE AS "Longitude for proximity analysis",
  t.TIMEZONE_CODE AS "Time zone code for the address",
  t.VALIDATED_FLAG AS "Whether the address passed validation",
  t.VALIDATION_STATUS_CODE AS "Standardized address-validation result",
  t.ORIG_SYSTEM_REFERENCE AS "Legacy-system address key — required"
FROM <catalog>.<schema>.HZ_LOCATIONS t
WHERE
  1 = 1  -- no automatic partition anchor on this table; the filters below are optional
  -- AND t.LOCATION_ID = <LOCATION_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.LOCATION_ID;