Search Results party_site_name




Overview
Explore in AI Chat

Overview

CSI_HZPTY_ADDRESSES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CSI (Install Base) product family. Its documented purpose is to present customer party addresses for use by Oracle EBS record groups, the functional groupings that govern which ledger, organization, and data context a concurrent program, report, or responsibility operates against. The view exposes address and party-site information in a single flattened, denormalized structure, allowing reports and integrations to resolve a party site to its parent party and location without navigating the normalized TCA (Trading Community Architecture) model directly.

The view is defined with a status of VALID and is present in both EBS 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; all content is derived at query time from the underlying TCA tables. The user search term "party_site_name" corresponds directly to the PARTY_SITE_NAME column exposed by this view.

Underlying Base Objects

The documented view definition selects from three base objects, all referenced through synonyms in the APPS schema:

Joins are established as HZP.PARTY_ID = HPS.PARTY_ID and HPS.LOCATION_ID = HL.LOCATION_ID. This is an inner join chain, so only party sites that resolve to both a valid party and a valid location are returned. The PARTY_SITE_ID is aliased to LOCATION in the projection, a naming convention worth noting since the column does not represent a location identifier in the HZ_LOCATIONS sense.

Key Columns

  • LOCATION — alias for HZ_PARTY_SITES.PARTY_SITE_ID; the primary key of the party site.
  • PARTY_SITE_NAME — the user-assigned name of the party site, typically matching the site usage context.
  • PARTY_SITE_NUMBER — the system-generated unique site number, useful for stable external references.
  • PARTY_NAME / PARTY_NUMBER / PARTY_ID — identification of the owning party (customer, prospect, or organization).
  • ADDRESS1–ADDRESS4, CITY, STATE, ZIP, COUNTRY — the formatted address fields from HZ_LOCATIONS, with POSTAL_CODE exposed as ZIP.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range of the party site.
  • STATUS — the active/inactive status of the party site.
  • IDENTIFYING_ADDRESS_FLAG — indicates whether the site is the identifying address for the party.
  • DESCRIPTION — the free-text description held on the location record.

Common Use Cases and Queries

The view is typically used to populate record group queries in Oracle Reports or concurrent program parameters, where a party site must be selectable by name. It is also used in install base and service reporting where customer site context is required alongside installed asset data.

A basic listing of active party sites for a given party:

  • SELECT party_site_name, party_site_number, address1, city, state, zip, country FROM csi_hzpty_addresses_v WHERE party_number = :p_party_number AND status = 'A' ORDER BY party_site_name;

To locate a specific site by name, matching the user's search term:

  • SELECT location, party_name, party_site_name, city, country FROM csi_hzpty_addresses_v WHERE UPPER(party_site_name) LIKE UPPER(:p_site_name)||'%';

To identify the primary identifying address for each party:

  • SELECT party_id, party_name, party_site_name, address1, city FROM csi_hzpty_addresses_v WHERE identifying_address_flag = 'Y';

Because the view performs no filtering on STATUS or date ranges, callers must apply their own effective-date and status predicates. Queries should also account for the inner-join behavior, which suppresses party sites lacking a resolvable location.