Results for “address_error_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

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

• PARTY_ID, PARTY_SITE_ID, LOCATION_ID — Primary keys establishing the party, the site instance, and the address location.
• PARTY_SITE_NUMBER, PARTY_SITE_NAME — Operational identifiers and user-facing site names.
• SITE_USE_TYPE, PRIMARY_PER_TYPE, PARTY_SITE_USE_ID — The intended use of the site (for example, billing or shipping) and whether it is the primary use for that type.
• START_DATE_ACTIVE, END_DATE_ACTIVE, STATUS — Effective dating and active status of the party site.
• IDENTIFYING_ADDRESS_FLAG — Indicates whether the location serves as an identifying address.
• ADDRESS1–ADDRESS4, CITY, STATE, PROVINCE, COUNTY, POSTAL_CODE, COUNTRY — Core postal address columns sourced from HZ_LOCATIONS.
• ADDRESS_KEY, ADDRESS_STYLE, VALIDATED_FLAG — Address standardization, formatting, and validation attributes.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–ATTRIBUTE20, GLOBAL_ATTRIBUTE_CATEGORY, GLOBAL_ATTRIBUTE1–20 — Descriptive and global flexfield columns carried from the party site.
• ORIG_SYSTEM_REFERENCE, CUSTOMER_KEY_OSM, PHONE_KEY_OSM, CONTACT_KEY_OSM — Originating system and OSM integration keys.
• LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID — Standard EBS audit and concurrent program tracking 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.