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)
ADDRESS1●Address1.
ADDRESS2●Address2.
ADDRESS3●Address3.
ADDRESS4●Address4.
ADDRESS_LINES_PHONETIC●Address lines phonetic.
BUILDING●Building.
CITY●City.
COUNTRY●Country.
COUNTY●County.
DESCRIPTION●Description.
FLOOR_NUMBER●Floor number.
HOUSE_TYPE●Type of house.
LOCATION_IDPK●Identifier for the location.
LOCATION_LANGUAGE●Location language.
ORIG_SYSTEM_REFERENCE●Orig system reference.
POSTAL_CODE●Code identifying the postal.
POSTAL_PLUS4_CODE●Code identifying the postal plus4.
PROVINCE●Province.
SALES_TAX_GEOCODE●Sales tax geocode.
SALES_TAX_INSIDE_CITY_LIMITS●Sales tax inside city limits.
SHORT_DESCRIPTION●Description of the short.
STATE●State.
STATUS_FLAG●Indicator (Y/N) for the status.
TIMEZONE_CODE●Code 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. In OTBI they combine only through shared dimensions or set operators such as union, inside one application; the owned conformed model joins this table across modules and systems on conformed 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