Search Results party_rel




Overview
Explore in AI Chat

Overview

APPS.CSC_HZ_PER_PROFILES_V is a reporting and integration view in the Oracle E-Business Suite (EBS) Releases 12.1.1 and 12.2.2 that consolidates party-level person profile information with organizational contact data. It is owned by the APPS schema and is built as a UNION of two SELECT statements, allowing it to present both persons who are linked to an organization through a party relationship and persons who are not. The view is part of the Oracle Customer (Trading Community Architecture / HZ) data model lineage, and is commonly used by downstream applications, concurrent programs, and custom reports that need a flattened, joined representation of person and organization-contact attributes without directly navigating the normalized HZ_PERSON_PROFILES, HZ_ORG_CONTACTS, and HZ_RELATIONSHIPS tables. Its presence supports the "party_rel" relationship path users frequently search for, since the relationship between person and organization is resolved through HZ_RELATIONSHIPS.

Underlying Base Objects

The view is documented as referencing three base objects, each accessed through APPS synonyms:

  • HZ_PERSON_PROFILES (SYNONYM) — supplies person identity attributes such as party identifier, known-as name, phonetic name, date of birth, personal income, name suffix, and person title.
  • HZ_ORG_CONTACTS (SYNONYM) — supplies organization contact attributes such as contact ID, decision maker flag, job title, managed-by, languages, rank, department, and mail stop.
  • HZ_RELATIONSHIPS (SYNONYM) — supplies the party relationship linkage that joins a person to an organization contact, using subject/object identifiers, table names, and the directional flag.

The first branch of the UNION joins HZ_ORG_CONTACTS to HZ_RELATIONSHIPS via ORG_CONT.PARTY_RELATIONSHIP_ID = PARTY_REL.RELATIONSHIP_ID, then links the relationship to the person profile where PARTY_REL.SUBJECT_ID or PARTY_REL.OBJECT_ID equals the person's PARTY_ID. It restricts relationships to those with subject_table_name and object_table_name equal to 'HZ_PARTIES' and directional_flag = 'F', and applies effective-date filtering. The second branch returns person profiles that have no such forward party relationship, padding the organization-contact columns with NULLs.

Key Columns

The view exposes a merged column set drawn from both branches:

Common Use Cases and Queries

Typical scenarios include resolving a person's organization contacts through the party relationship path, generating contact rosters for a customer organization, and extracting demographic plus contact attributes for analytics or integrations.

Sample query returning linked persons and their organization contacts:

  • SELECT party_id, known_as, org_contact_id, job_title, department
  • FROM apps.csc_hz_per_profiles_v
  • WHERE org_contact_id IS NOT NULL;

Sample query returning persons with no forward organizational relationship:

  • SELECT party_id, known_as, date_of_birth
  • FROM apps.csc_hz_per_profiles_v
  • WHERE org_contact_id IS NULL;

Because effective-date filtering is embedded in the first branch, results reflect only currently active person profiles where an end date is present. Reports relying on this view should account for the UNION semantics, since contact columns are populated only where a qualifying forward 'HZ_PARTIES' relationship exists.