Search Results rel_party_number




Overview
Explore in AI Chat

Overview

The CSC_HZ_PARTIES_REL_V view is a Customer Care (CSC) module database object owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its documented purpose is to expose Customer Party, Contact Party, and Relationship Party information in a single denormalized result set. The view joins records from the Trading Community Architecture (TCA) registry with relationship data, allowing callers to retrieve a party together with its associated counterparties without issuing multiple queries against the underlying base tables.

In practice, the view functions as a reporting and integration surface for Customer Care, TeleSales, and related modules that need to resolve a party to its contact and relationship parties. Because it flattens both the primary party attributes and the related party attributes into one row, it is well suited to concurrent program queries, Oracle Reports data models, and OAF-based or custom integrations that must present a unified party view. The user search term obj_person_title corresponds directly to the OBJ_PERSON_TITLE column in this view, which carries the person title (for example, job title or honorific context) of the object party on the relationship.

Underlying Base Objects

According to the ETRM 12.2.2 metadata, the view is defined over the following referenced base objects:

  • HZ_PARTIES (SYNONYM) — the TCA master party registry, supplying party identifiers, names, party type, person name components, address elements, and the ATTRIBUTE1 through ATTRIBUTE20 flex columns.
  • HZ_RELATIONSHIPS (SYNONYM) — the TCA relationship table that links parties, including subject and object party roles, relationship codes, and directionality.
  • FND_TERRITORIES_TL (SYNONYM) — the translated territory table, typically used to resolve country or territory codes to descriptions or names in the reporting language.
  • AR_LOOKUPS (VIEW) — the Receivables lookups view, used to decode lookup codes such as relationship types, party statuses, or phone/contact classifications into their display meanings.

The view text selects from an object party alias (OBJ) and a subject party alias (SUB), joining the relationship data between them. The OBJ_PERSON_TITLE column is sourced explicitly from OBJ.PERSON_TITLE, confirming that the title attribute is taken from the object party side of the relationship, not the subject party side.

Key Columns

The view exposes a broad set of columns, prefixed by OBJ_ for the object party and SUB_ for the associated subject party.

Common Use Cases and Queries

The most frequent use case is retrieving all parties related to a given customer, including the person title of each related contact. The following query illustrates this pattern:

SELECT obj_party_name, obj_person_title, sub_party_id FROM apps.csc_hz_parties_rel_v WHERE obj_party_id = :p_party_id;

Other common scenarios include generating contact directories that display OBJ_PERSON_TITLE alongside OBJ_ADDRESS, resolving relationship parties for service request routing, and building integration extracts that require both object and subject party identifiers. Because the view builds OBJ_ADDRESS by concatenating address lines, consumers that require discrete address elements should use OBJ_ADDRESS1 through OBJ_ADDRESS4 rather than parsing the concatenated column.

When querying, ensure the caller context has access to the APPS schema or that a synonym is granted, and filter on indexed columns such as OBJ_PARTY_ID to avoid full scans across the large HZ_PARTIES and HZ_RELATIONSHIPS base data sets.