Results for “date_of_death”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AMS_LT_HZ_PERSON_PROFILES view is a data source object owned by the APPS schema within the Oracle E-Business Suite 12.1.1 / 12.2.2 environment. It belongs to the AMS (Marketing) product family and serves as a lightweight, flattened projection of person-level demographic data. The name prefix "LT" designates this view as part of the Oracle Marketing "List Template" / data source framework, which supplies pre-built queryable objects used by targeting, list generation, and campaign segmentation engines. Rather than exposing the full HZ_PERSON_PROFILES table, this view presents a curated subset of fifteen columns, allowing Marketing list builders and external integrations to select person attributes without navigating the broad column set of the underlying Trading Community Architecture (TCA) table. In practice it acts as a stable reporting and integration surface for person demographic attributes, and it is a common resolution point for user searches such as person_academic_title that reference TCA person columns through a Marketing data source.

Underlying Base Objects

The view is defined over a single documented base object, HZ_PERSON_PROFILES, accessed via a synonym of the same name. It performs no joins and no filtering; the definition is a straight column-list projection:

Because there is a one-to-one column mapping and no predicates, the view inherits the row population, cardinality, and joins of HZ_PERSON_PROFILES. Each row corresponds to one person profile, always associated with a single PARTY_ID in the TCA registry. The object status is documented as VALID in the ETRM metadata. Users should be aware that the synonym resolution and grants are managed at the APPS layer, and the view has no independent data storage.

Key Columns

  • PERSON_PROFILE_ID — Primary identifier of the person profile row; the natural join key to the base table.
  • PARTY_ID — Foreign reference to the TCA party record; the bridge to HZ_PARTIES, HZ_PERSON_PROFILES, and related party-level entities.
  • PERSON_ACADEMIC_TITLE — Free-text academic or honorific designation associated with the person (for example, Dr., Prof.); the column most frequently requested in Marketing list definitions.
  • DATE_OF_BIRTH, DATE_OF_DEATH — Vital dates used for age banding, deceased suppression, and deduplication logic.
  • PLACE_OF_BIRTH — Geographic origin attribute for segmentation.
  • GENDER, DECLARED_ETHNICITY, MARITAL_STATUS, MARITAL_STATUS_EFFECTIVE_DATE — Demographic and equality-monitoring attributes.
  • PERSONAL_INCOME, HOUSEHOLD_INCOME, HOUSEHOLD_SIZE, HEAD_OF_HOUSEHOLD_FLAG, RENT_OWN_IND — Financial and household composition fields used for propensity and targeting models.

Common Use Cases and Queries

Typical consumption is through Marketing list templates, audience segmentation, and ad hoc reporting. A representative query retrieving a person's academic title alongside core demographics is:

  • SELECT p.party_id, p.person_academic_title, p.gender, p.date_of_birth FROM apps.ams_lt_hz_person_profiles p WHERE p.person_academic_title IS NOT NULL;
  • SELECT h.party_name, p.household_income, p.household_size FROM apps.ams_lt_hz_person_profiles p, apps.hz_parties h WHERE p.party_id = h.party_id AND p.rent_own_ind = 'R';

Because the view is unfiltered, queries should always constrain on the relevant demographic predicate and join to HZ_PARTIES when a display name is required. For large campaign extracts, restricting by PARTY_ID ranges or indexing on the base table is advisable. When the academic title attribute is unavailable in AMS reporting, the same column can be sourced directly from HZ_PERSON_PROFILES, confirming that AMS_LT_HZ_PERSON_PROFILES is a presentation-layer convenience rather than an independent data store.