Search Results content_source_number

Overview

AST_PERSON_PROFILE_V is a TeleSales (AST) reporting and integration view owned by the APPS schema. It exposes person-level profile information held in the Oracle E-Business Suite party model, joining the person profile record to its parent party and decoding several descriptive attributes through lookup views. The view presents a denormalized, read-friendly projection of demographic, contact, and classification data for individuals known to TeleSales and to the broader Oracle Customers Online / Trading Community Architecture (TCA) model.

Its principal role is to give concurrent programs, Oracle Reports, Discoverer workbooks, and custom integrations a single query point for person profile attributes without requiring a multi-table join against HZ_PERSON_PROFILES and HZ_PARTIES. Because it is a view, it carries no independent storage; it inherits the security and data currency of its underlying objects and reflects the current state of the profile records at query time. Users searching for the head_of_household_flag attribute will find it exposed directly by this view, alongside the lookup meaning that decodes it.

Underlying Base Objects

The documented base objects for AST_PERSON_PROFILE_V in ETRM 12.2.2 are AR_LOOKUPS (VIEW), FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), HZ_PARTIES (SYNONYM), and HZ_PERSON_PROFILES (SYNONYM).

• HZ_PERSON_PROFILES is the driving table. It supplies the profile identity columns (PERSON_PROFILE_ID, PARTY_ID), the person name components, the descriptive and demographic attributes, and the flexible ATTRIBUTE1–20 columns.
• HZ_PARTIES supplies party-level columns such as OBJECT_VERSION_NUMBER, CREATED_BY_MODULE, and APPLICATION_ID, joined on PARTY_ID.
• FND_LOOKUPS and AR_LOOKUPS are used through the LKUP2, LKUP3, LKUP4, and LKUP5 aliases to resolve coded values (for example, marital status, rent/own indicator, and the head-of-household flag) into user-facing MEANING text.
• FND_GLOBAL is referenced for session context values, typically supplying the current application or user identifier used in lookup resolution or row filtering.

Key Columns

• PERSON_PROFILE_ID / PARTY_ID — primary identifiers linking the profile to its owning party record.
• PERSON_NAME and name components — PERSON_NAME, PERSON_PRE_NAME_ADJUNCT, PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PERSON_NAME_SUFFIX, PERSON_TITLE, PERSON_INITIALS, KNOWN_AS, and phonetic variants.
• Demographic attributes — DATE_OF_BIRTH, PLACE_OF_BIRTH, DATE_OF_DEATH, GENDER, DECLARED_ETHNICITY, MARITAL_STATUS, MARITAL_STATUS_EFFECTIVE_DATE, PERSONAL_INCOME, HOUSEHOLD_INCOME, and HOUSEHOLD_SIZE.
• HEAD_OF_HOUSEHOLD_FLAG — the coded indicator identifying whether the person is recorded as head of household. The adjacent LKUP5.MEANING column decodes this flag into its display value.
• RENT_OWN_IND with LKUP4.MEANING — residence tenure indicator and its meaning.
• Dates and status — EFFECTIVE_START_DATE, EFFECTIVE_END_DATE, LAST_UPDATE_DATE, and STATUS.
• ATTRIBUTE1–20 — flexfield descriptors available for customer-specific extension.

Common Use Cases and Queries

Typical scenarios include household-level targeting, demographic segmentation for campaign lists, and profile enrichment for integrations. A query retrieving individuals flagged as head of household would read:

• SELECT person_profile_id, party_id, person_name, head_of_household_flag FROM apps.ast_person_profile_v WHERE head_of_household_flag = 'Y';
• Joining the view to HZ_CUST_ACCOUNTS or HZ_CUST_ACCT_SITES_ALL on PARTY_ID to attach household profiles to customer accounts.
• Filtering by EFFECTIVE_START_DATE and EFFECTIVE_END_DATE to return only profiles active for a reporting period.
• Aggregating HOUSEHOLD_SIZE and HOUSEHOLD_INCOME to build segmentation summaries for TeleSales campaigns.

Because the view decodes lookup values at runtime, reports should select the MEANING columns where a display label is required rather than the raw codes.