Search Results declared_ethnicity




Overview
Explore in AI Chat

Overview

APPS.AMS_LT_HZ_PERSON_PROFILES is a lightweight reporting view shipped in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 environments. It exposes a curated subset of columns from the Oracle Trading Community Architecture (TCA) person profile entity, allowing downstream Oracle Marketing (AMS) and CRM reporting components to retrieve demographic, household, and income attributes for individual parties without querying the full base table. The view is owned by the APPS schema and is documented in the E-Business Suite Technical Reference Manual (ETRM) for release 12.2.2.

The "LT" prefix conventionally designates a lightweight or lookup-oriented variant used by Oracle Marketing's audience segmentation, list generation, and lead qualification features. Because the view is a simple projection, it inherits the security, indexing, and row-level access behavior of its base object rather than introducing its own logic.

Underlying Base Objects

According to the documented metadata, the view is defined over a single base object: HZ_PERSON_PROFILES, accessed through a synonym in the APPS schema. The view text is a straightforward SELECT with no joins, filters, aggregations, or WHERE clauses — every row of the base table is returned, limited only by the column list.

  • HZ_PERSON_PROFILES — the TCA table that stores person-level profile data keyed by PERSON_PROFILE_ID and linked to a party via PARTY_ID.
  • APPS synonym — the APPS-owned synonym resolving to the underlying HZ table, which permits the view to be created and queried within the APPS schema.

Because the view references only one table and performs no transformation, its cardinality is identical to HZ_PERSON_PROFILES, and any inserts, updates, or deletes against the base record are immediately visible through the view.

Key Columns

The view exposes fifteen columns, all inherited directly from the base table:

Common Use Cases and Queries

This view is typically used by Oracle Marketing and CRM modules to build target audiences based on demographic criteria, and by custom integrations that require a stable, read-only interface to person profile data. A typical query locating a specific profile might resemble:

SELECT PERSON_PROFILE_ID,
       PARTY_ID,
       DATE_OF_BIRTH,
       GENDER,
       HOUSEHOLD_INCOME,
       RENT_OWN_IND
FROM   APPS.AMS_LT_HZ_PERSON_PROFILES
WHERE  PARTY_ID = :party_id;

Because the view contains no filtering logic, callers are responsible for joining to HZ_PARTIES, HZ_PERSON_PROFILES, or related TCA tables to resolve names, addresses, or classification codes, and for applying any applicable row-level security or date-effective constraints. In EBS 12.2.2 the view remains a synonym-based projection of HZ_PERSON_PROFILES and should be treated as a read-only reporting object.