Search Results content_source_number




Overview
Explore in AI Chat

Overview

HZ_PERSON_PROFILES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and catalogued under the Receivables (AR) product family. It presents person-level profile information maintained within the Trading Community Architecture (TCA) model, exposing attributes such as names, identifiers, demographics, and contact preferences in a single denormalized projection. In Oracle EBS 12.1.1 and 12.2.2 the object is registered with a status of VALID, confirming it is a supported, compiled component of the applications data dictionary rather than a custom or deprecated artifact.

Because the view is a read-only projection, it is intended for reporting, inquiry, and integration purposes rather than direct DML. Oracle EBS reports, discoverer workbooks, and third-party integrations reference HZ_PERSON_PROFILES_V to retrieve person profile data without needing to reconcile the join logic between party and profile tables themselves. This encapsulation is the principal benefit of consuming the view.

Underlying Base Objects

The documented base objects referenced by HZ_PERSON_PROFILES_V are HZ_PARTIES and HZ_PERSON_PROFILES, both exposed to the view through synonyms. HZ_PARTIES is the central TCA entity that stores the core party record and its classification as a person, organization, or group. HZ_PERSON_PROFILES stores the extended person-specific profile attributes linked to a party by PARTY_ID and PERSON_PROFILE_ID.

The view selects primarily from the profile table (aliased B in the view text) and returns the full set of descriptive and control columns, including the WHO columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE), the DFF Attribute1–Attribute20 and Global Attribute1–Global Attribute20 flexfield columns, and the descriptive person name components. The reliance on HZ_PARTIES underpins the party-centric integrity of the data returned.

Key Columns

Common Use Cases and Queries

Typical uses include customer master reporting, marketing segmentation, and contact-preference analysis. The BEST_TIME_CONTACT_BEGIN and BEST_TIME_CONTACT_END columns are frequently queried to schedule outbound communications within a customer's stated availability window.

A representative query retrieving the preferred contact window for a party is shown below:

  • SELECT party_id, person_name, best_time_contact_begin, best_time_contact_end, last_update_date FROM apps.hz_person_profiles_v WHERE best_time_contact_begin IS NOT NULL ORDER BY person_name;
  • SELECT party_id, person_first_name, person_last_name, gender, date_of_birth FROM apps.hz_person_profiles_v WHERE party_id = :p_party_id;
  • SELECT p.party_id, p.person_name, h.party_number FROM apps.hz_person_profiles_v p JOIN apps.hz_parties h ON h.party_id = p.party_id WHERE p.effective_end_date IS NULL OR p.effective_end_date > SYSDATE;

Because the view supplies the WHO audit columns and both DFF families, it is also suitable for incremental data extracts that reconcile changes by LAST_UPDATE_DATE or REQUEST_ID.