Search Results known_as2




Overview
Explore in AI Chat

Overview

HZ_PERSON_PROFILES_CPUI_V is a concurrent-program and interface (CPUI) oriented database view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified under the Receivables (AR) product family and is documented in ETRM with the description "Person Profiles." The view consolidates party-level demographic, personal, and household information for persons (individuals) into a single denormalized projection. Its name follows the EBS convention for views used by concurrent programs and bulk data interfaces, meaning it is typically consumed by batch processes and report registrations rather than by end-user forms. Because it joins identity data from the HZ_PARTIES party model with profile attributes held in HZ_PERSON_PROFILES, it provides a reporting-friendly, flat representation of a customer or contact person. The view is a convenience layer, not a base entity; it exposes no independent storage and inherits the transaction integrity, concurrency, and validation rules of the two underlying synonyms.

Underlying Base Objects

According to the documented view metadata for ETRM 12.2.2, the view is defined over exactly two referenced base objects, both exposed to APPS as synonyms:

The join is performed on the shared PARTY_ID, and the primary key exposed by the projection is PERSON_PROFILE_ID from HZ_PERSON_PROFILES. Both synonyms resolve to the TCA (Trading Community Architecture) registry tables, so the view participates in the same referential model used across Receivables, Order Management, and CRM.

Key Columns

The column list spans identity, personal, demographic, and audit groups. Notable columns include:

The MARITAL_STATUS column, which prompted the search, holds the coded marital status of the person and is accompanied by MARITAL_STATUS_EFFECTIVE_DATE to indicate when the status became effective.

Common Use Cases and Queries

Typical uses include customer demographic reporting, contact data extraction for downstream warehouse loads, and concurrent-program output. A common query retrieves marital status together with core identity fields:

  • Marital status by party: SELECT party_number, person_name, marital_status, marital_status_effective_date FROM hz_person_profiles_cpui_v WHERE marital_status IS NOT NULL;
  • Demographic profile extraction: select party_id, gender, date_of_birth, declared_ethnicity, household_size, household_income filtered by LAST_UPDATE_DATE for incremental loads.
  • Household analysis: aggregate PERSONAL_INCOME and HOUSEHOLD_INCOME grouped by HEAD_OF_HOUSEHOLD_FLAG and RENT_OWN_IND.
  • Customer summary joins: join PARTY_ID back to RA_CUSTOMERS or HZ_CUST_ACCOUNTS to combine demographic attributes with receivable balances and order metrics such as TOTAL_ORDERED_AMOUNT.

Because the view is read-only and built on TCA synonyms, queries should always filter on indexed PARTY_ID or PARTY_NUMBER and restrict LAST_UPDATE_DATE ranges when used in high-volume programs. The MARITAL_STATUS column is the appropriate attribute for any report requiring an individual's marital status in EBS 12.1.1 or 12.2.2.