Analytics Catalog/Data dictionary/HZ_LOCATIONS
Explore the catalogReportsModulesEnterprise modelOTBI subject areasBICC PVOs
Oracle Fusion · Data dictionary

HZ_LOCATIONS

Trading CommunityUsed in 78 subject areas24 reporting columns

Trading Community (HZ), geographic location master used by parties and sites.

Primary key: LOCATION_ID

Columns

ColumnKeyIn reportsDescription (inferred)
ADDRESS1Address1.
ADDRESS2Address2.
ADDRESS3Address3.
ADDRESS4Address4.
ADDRESS_LINES_PHONETICAddress lines phonetic.
BUILDINGBuilding.
CITYCity.
COUNTRYCountry.
COUNTYCounty.
DESCRIPTIONDescription.
FLOOR_NUMBERFloor number.
HOUSE_TYPEType of house.
LOCATION_IDPKIdentifier for the location.
LOCATION_LANGUAGELocation language.
ORIG_SYSTEM_REFERENCEOrig system reference.
POSTAL_CODECode identifying the postal.
POSTAL_PLUS4_CODECode identifying the postal plus4.
PROVINCEProvince.
SALES_TAX_GEOCODESales tax geocode.
SALES_TAX_INSIDE_CITY_LIMITSSales tax inside city limits.
SHORT_DESCRIPTIONDescription of the short.
STATEState.
STATUS_FLAGIndicator (Y/N) for the status.
TIMEZONE_CODECode identifying the timezone.

1 report read from this table

Change a column here and these are the reports that move with it, the blast radius for any change to HZ_LOCATIONS.

Where this surfaces in OTBI

The OTBI subject areas that expose this table. You can't join across them in OTBI, the owned conformed model joins them on shared keys.

Need the extract + dbt staging for HZ_LOCATIONS?
We ship parameterized SQL, BICC config, and dbt models you own.
Talk to us
Problems that run through this table
Aging as of any date · Reporting without memory · The export ceiling