Results for “hz_person_profiles”

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

Overview

HZ_PERSON_PROFILES is a core Trading Community Architecture (TCA) table owned by the AR schema and exposed through the Oracle Receivables product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores detailed, descriptive information about people (parties of type PERSON) that supplements the identity and relationship data held in the parent HZ_PARTIES table. Whereas HZ_PARTIES captures the party record itself and its core attributes, HZ_PERSON_PROFILES holds the richer biographical, demographic, fiscal, and personal-context details that describe an individual, such as name components, identifiers, birth and death information, and household attributes. The table is documented as VALID and contains 106 columns in the 12.2.2 physical schema.

From a Data Vault modeling perspective, the heuristic mined from the foreign-key structure classifies HZ_PERSON_PROFILES as hub-leaning. This suggests it can be modeled as a hub-like entity anchored on its own primary key, PERSON_PROFILE_ID, with a foreign-key dependency to HZ_PARTIES. In practice, it behaves as a detail or profile extension keyed to each party, and analysts should treat PERSON_PROFILE_ID as the stable technical identifier while PARTY_ID links the profile back to the master party record.

Key Information Stored

The primary key is HZ_PERSON_PROFILES_PK on PERSON_PROFILE_ID, and a unique index HZ_PERSON_PROFILES_U1 also exists on PERSON_PROFILE_ID, confirming it as the dominant business-key candidate. The foreign key PARTY_ID references HZ_PARTIES, tying each profile row to a specific party. The most important columns include:

• PERSON_PROFILE_ID — surrogate primary key identifying the profile row.
• PARTY_ID — foreign key to HZ_PARTIES; the owning person party.
• PERSON_NAME and the structured name columns (PERSON_FIRST_NAME, PERSON_MIDDLE_NAME, PERSON_LAST_NAME, PERSON_PRE_NAME_ADJUNCT, PERSON_NAME_SUFFIX, PERSON_TITLE, PERSON_ACADEMIC_TITLE, PERSON_INITIALS, KNOWN_AS) — full and component names for the person.
• PERSON_IDENTIFIER / PERSON_IDEN_TYPE — government or internal identifier and its type.
• TAX_REFERENCE / JGZZ_FISCAL_CODE — tax and fiscal identifiers used in jurisdictions reporting.
• DATE_OF_BIRTH, PLACE_OF_BIRTH, DATE_OF_DEATH, DECEASED_FLAG — vital status attributes.
• GENDER, MARITAL_STATUS, DECLARED_ETHNICITY — demographic characteristics.
• PERSONAL_INCOME, HOUSEHOLD_INCOME, HOUSEHOLD_SIZE, HEAD_OF_HOUSEHOLD_FLAG, RENT_OWN_IND — household and financial context.
• PRIMARY_CONTACT_ID — reference to the person's primary contact point.
• STATUS, EFFECTIVE_START_DATE, EFFECTIVE_END_DATE — lifecycle and validity of the profile.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and the ATTRIBUTE1–20 / GLOBAL_ATTRIBUTE1–20 descriptive flexfield and global DFF segments used for customer extensions.

Common Use Cases and Queries

Typical reporting scenarios include customer master data extracts, KYC and compliance reporting, demographic segmentation, and household analysis. A common join retrieves the profile alongside its party:

SELECT p.party_number, pp.person_first_name, pp.person_last_name, pp.date_of_birth, pp.gender
FROM hz_parties p, hz_person_profiles pp
WHERE p.party_id = pp.party_id AND pp.status = 'A';

Other patterns filter on demographic or fiscal attributes (for example, DECLARED_ETHNICITY or JGZZ_FISCAL_CODE), resolve a person's primary contact via PRIMARY_CONTACT_ID against HZ_CONTACT_POINTS, or extract DFF attributes for downstream analytics. Because the DFF columns are generic, queries should join to the flexfield definition to resolve ATTRIBUTE_CATEGORY before interpreting ATTRIBUTE1–20.

Related Objects

The following objects are directly connected through the documented FK/PK relationships:

• HZ_PARTIES — parent entity; join on HZ_PERSON_PROFILES.PARTY_ID = HZ_PARTIES.PARTY_ID.
• HZ_PER_PROFILES_EXT_B — extension table; join on PERSON_PROFILE_ID.
• HZ_PER_PROFILES_EXT_TL — translated extension table; join on PERSON_PROFILE_ID.
• IGS_PE_STAT_DETAILS — higher-education status detail; join on PERSON_PROFILE_ID.

These dependents confirm the hub-like role of HZ_PERSON_PROFILES as a central anchor referenced by extension and detail tables. Analysts should typically drive queries through HZ_PARTIES or HZ_PERSON_PROFILES and resolve downstream details through PERSON_PROFILE_ID and PARTY_ID.