Search Results object_table_name




Overview
Explore in AI Chat

Overview

HZ_RELATIONSHIPS_V is an APPS-owned database view in the Oracle E-Business Suite Receivables (AR) product family. It exposes party-to-party relationship data maintained in the Oracle Trading Community Architecture (TCA) model and provides a denormalized, human-readable projection of the HZ_RELATIONSHIPS entity. The view is registered as VALID in the APPS schema and is available across both the 12.1.1 and 12.2.2 release streams without structural change.

The view is primarily used for reporting, inquiry, and integration purposes. Rather than requiring callers to join HZ_RELATIONSHIPS to lookup tables and party records manually, HZ_RELATIONSHIPS_V performs these joins internally, returning descriptive meanings for coded columns and the party name, party number, and party type of the subject party. This makes it a convenient source for BI Publisher reports, OAF-based inquiry pages, custom concurrent programs, and outbound integrations that need to resolve relationship types such as party_relations_type into a meaningful description.

Underlying Base Objects

The view is defined over the following documented base objects:

  • HZ_RELATIONSHIPS (synonym) — the primary driving table, supplying the relationship identifier, subject and object identifiers, directionality, dates, status, DFF attributes, and audit columns.
  • HZ_PARTIES (synonym) — joined to retrieve PARTY_NAME, PARTY_NUMBER, and PARTY_TYPE for the party associated with the relationship.
  • AR_LOOKUPS (view) — joined twice: once as LOOKUP to resolve the relationship code into RELATIONSHIP_MEANING, and once as LOT to resolve the relationship type into a descriptive meaning.
  • HZ_RELATIONSHIP_TYPES (synonym) — referenced in the documented base object list, supplying metadata about relationship type definitions.
  • HZ_CODE_ASSIGNMENTS (synonym) — referenced in the documented base object list and used in resolving classification codes associated with relationships.

The view therefore inherits the TCA model's relationship semantics while presenting a single flat row per relationship record.

Key Columns

Common Use Cases and Queries

Typical scenarios include retrieving all relationships of a given type for a party, reporting contact hierarchies, and validating relationship data prior to integration.

  • List all relationships for a specific party:
SELECT relationship_id, party_name, relationship_meaning,
       relationship_type, directionality, status
  FROM hz_relationships_v
 WHERE subject_id = :p_party_id
   AND status = 'A';
  • Filter by relationship type (party_relations_type):
SELECT party_name, relationship_meaning, start_date, end_date
  FROM hz_relationships_v
 WHERE relationship_type = :p_type
   AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, SYSDATE+1);
  • Resolve a relationship code to its descriptive meaning for a downstream report by selecting RELATIONSHIP_MEANING directly, avoiding a redundant lookup join.

Because the view already incorporates AR_LOOKUPS and HZ_PARTIES, most reporting requirements can be satisfied with a single SELECT against HZ_RELATIONSHIPS_V, which simplifies both ad hoc querying and packaged customizations.