Search Results hz_party_sites_v




Overview
Explore in AI Chat

Overview

HZ_PARTY_SITES_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is registered under the Receivables (AR) product family and exposes the intersection of a party site, its site uses, and its physical address location in a single, flat result set. The view joins the HZ_PARTY_SITES base entity to HZ_LOCATIONS and HZ_PARTY_SITE_USES, allowing consumers to retrieve address and site-use context without writing the multi-table joins manually. It is used extensively by Receivables reporting, customer/party extraction routines, and integration interfaces that must materialize a complete party-site record.

Underlying Base Objects

Per the ETRM metadata, the view is defined over three referenced base objects, each accessed through APPS synonyms:

  • HZ_PARTY_SITES — aliased as A; supplies the party site identity, party reference, lifecycle dates, descriptive flexfields, and OSM key columns.
  • HZ_PARTY_SITE_USES — aliased as B; supplies the site-use type record, primary-per-type flag, comments, and the party site use identifier.
  • HZ_LOCATIONS — aliased as C; supplies the structured and descriptive address elements, country, validation flag, time zone, and phonetic address lines.

The relationship is driven by PARTY_SITE_ID linking HZ_PARTY_SITES to HZ_PARTY_SITE_USES, and by LOCATION_ID linking HZ_PARTY_SITES to HZ_LOCATIONS. Because one party site may have multiple site uses, the view can return more than one row per party site.

Key Columns

Common Use Cases and Queries

Typical scenarios include extracting validated billing addresses, reconciling site-use assignments for customers, and supplying downstream interfaces with flattened party-site data. The following query filters to primary billing uses for a given party:

  • SELECT party_site_id, party_site_name, address1, city, state, postal_code, country
  • FROM hz_party_sites_v
  • WHERE party_id = :p_party_id
  • AND site_use_type = 'BILL_TO'
  • AND primary_per_type = 'Y'
  • AND status = 'A';

Because the view does not join HZ_PARTIES, party attributes such as party name or party number must be obtained separately, typically by joining on PARTY_ID. Consumers should also account for effective dating on START_DATE_ACTIVE and END_DATE_ACTIVE, and note that multi-use sites produce multiple rows, requiring PRIMARY_PER_TYPE or site-use filtering for deterministic results.