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

HZ_GEOGRAPHY_TYPES_B

Trading CommunityUsed in 0 subject areas16 reporting columnsBICC incremental-ready

Trading Community (Parties) (HZ), type / category reference.

Likely primary key: GEOGRAPHY_TYPE_CODE (inferred from Oracle naming conventions, verify against Tables & Views) · Incremental key: LAST_UPDATE_DATE

Columns

ColumnKeyIn reportsDescription (inferred)
CREATED_BY●User who created the row.
CREATED_BY_MODULE●Created by module.
CREATION_DATE●Date and time the row was created.
GEOGRAPHY_TYPE●Type of geography.
GEOGRAPHY_TYPE_CODEPK?○Code identifying the geography type.
GEOGRAPHY_TYPE_ID●Identifier for the geography type.
GEOGRAPHY_USE●Geography use.
JOB_DEFINITION_NAME●Name of the job definition.
JOB_DEFINITION_PACKAGE●Job definition package.
LAST_UPDATED_BY●User who last updated the row.
LAST_UPDATE_DATEINCR●Date and time the row was last updated (the incremental-extract key).
LAST_UPDATE_LOGIN●Session login of the user who last updated the row.
LIMITED_BY_GEOGRAPHY_ID●Identifier for the limited by geography.
OBJECT_VERSION_NUMBER●Optimistic-locking version number, incremented on each update.
POSTAL_CODE_RANGE_FLAG●Indicator (Y/N) for the postal code range.
REQUEST_ID●Identifier of the process that created or last updated the row.
SEED_DATA_SOURCE●Seed data source.

Used by reports

No cataloged report reads from this table yet, it's part of the broader Fusion dictionary.

Subject areas

Need the extract + dbt staging for HZ_GEOGRAPHY_TYPES_B?
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