Search Results person_last_name_phonetic




Overview
Explore in AI Chat

Overview

APPS.CSC_HZ_PARTIES_SRCH_REL_V is a TCA (Trading Community Architecture) reporting view that joins the HZ_PARTIES entity to its relationship records in HZ_RELATIONSHIPS. The view presents each party (the "OBJ" or subject row) together with the related party (the "REL" row) and an intermediary ("SUB") party, exposing a three-way association useful for relationship-based searching and display. It resides in the APPS schema, is commonly referenced by Oracle Customer Care and other CRM/self-service modules, and is a documented object in Oracle EBS 12.1.1 and 12.2.2.

The view is most frequently encountered when searching for parties by attributes such as person_title. Each of the three party slots (OBJ, SUB, REL) carries its own title column—OBJ_PERSON_TITLE, SUB_PERSON_TITLE, and REL_PERSON_TITLE—so that a relationship query can filter or display the title of the subject party, the related party, or the intermediate party independently. This is significant because a single person may hold different titles in different roles, and the caller needs granular control over which party's title is matched.

Underlying Base Objects

Per ETRM 12.2.2, the view is defined over the following referenced base objects:

  • HZ_PARTIES (synonym) — the TCA party master table, supplying OBJ, SUB, and REL party attributes.
  • HZ_RELATIONSHIPS (synonym) — the relationship join table, supplying REL_PARTY_ID and the link between subject and related party.
  • AR_LOOKUPS (view) — used to decode lookup-coded values such as party type or relationship role.
  • FND_TERRITORIES_TL (synonym) — the translated territory table, providing territory descriptions for address or country codes.

The SELECT joins HZ_PARTIES three times—aliased as OBJ, SUB, and REL—to HZ_RELATIONSHIPS (REL link). The prefixes OBJ_, SUB_, and REL_ disambiguate identical columns drawn from the same underlying table.

Key Columns

Common Use Cases and Queries

Typical uses include relationship browsers, customer-search pages, and party deduplication checks that must return both a party and its related contacts with titles visible.

  • Filtering relationships by the subject party's title: 
    SELECT obj_party_id, obj_party_name, obj_person_title,
       rel_party_id, rel_party_name, rel_person_title
FROM   apps.csc_hz_parties_srch_rel_v
WHERE  UPPER(obj_person_title) LIKE UPPER('%MANAGER%');
  • Returning all relationships for a given party number, including related addresses and titles.
  • Resolving party names to party IDs for integration feeds that must carry title context.

Because the view spans three party aliases, queries return one row per relationship link; consumers must select the appropriate OBJ_/SUB_/REL_ prefixed column to obtain the intended party's person_title.