Search Results party_address2

Overview

CSI_HZCA_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 serve as a customer account address view for record groups, a design role that places it firmly among the flexfield and concurrent program value-set sources rather than among transactional base tables. Record groups in Oracle EBS reporting tools such as Oracle Reports and BI Publisher draw their parameter lists from such views, so CSI_HZCA_ADDRESSES_V exists primarily to supply a denormalized, human-readable list of customer account addresses to report parameters and lookups. In the 12.1.1 and 12.2.2 releases the view retains a VALID status and remains defined in APPS, which means it is a supported, upgrade-carried object that customers can query directly or reference from custom concurrent programs and value sets without creating their own joins across the TCA (Trading Community Architecture) tables.

Underlying Base Objects

The ETRM metadata for 12.2.2 identifies four referenced base objects, all resolved through APPS synonyms: HZ_CUST_ACCT_SITES_ALL, HZ_LOCATIONS, HZ_PARTIES, and HZ_PARTY_SITES. These are core TCA entities. HZ_PARTIES stores the party record and the party name, HZ_PARTY_SITES links a party to a physical site, HZ_LOCATIONS holds the address lines, city, state, postal code, and country, and HZ_CUST_ACCT_SITES_ALL associates the party site with a specific customer account and account site. The view's SQL joins these tables on the standard TCA keys: PARTY_ID between HZ_PARTIES and HZ_PARTY_SITES, PARTY_SITE_ID between HZ_PARTY_SITES and HZ_CUST_ACCT_SITES_ALL, and LOCATION_ID between HZ_PARTY_SITES and HZ_LOCATIONS. Because the joins are inner joins, only customer account sites that resolve through all four tables appear in the result set.

Key Columns

The view exposes eight columns. CUST_ACCOUNT_ID and CUST_ACCT_SITE_ID carry the primary identifiers for the customer account and the account site, making them the join keys back to transactional Install Base data. PARTY_NAME returns the party name from HZ_PARTIES. PARTY_CITY is the city from HZ_LOCATIONS. PARTY_ADDRESS1 and PARTY_ADDRESS2 map directly to the ADDRESS1 and ADDRESS2 columns of HZ_LOCATIONS, so a search for "party_address2" resolves to this column as the raw second address line. PARTY_ADDRESS is a concatenation of ADDRESS1 through ADDRESS4, city, state, postal code, and country into a single display string. PARTY_ADDRESS3 is a derived, non-address column: it concatenates city, state, postal code, and country with conditional comma logic and truncates the result to 220 characters via SUBSTR. Users expecting three physical address lines should note that PARTY_ADDRESS3 is a locality string, not a street line.

Common Use Cases and Queries

The most frequent use is populating a report parameter or value set with customer account addresses. A typical lookup filters by account or site identifier:

• Retrieve a formatted address for one account site: SELECT PARTY_NAME, PARTY_ADDRESS FROM CSI_HZCA_ADDRESSES_V WHERE CUST_ACCT_SITE_ID = :site_id;
• List all sites for a customer: SELECT CUST_ACCT_SITE_ID, PARTY_ADDRESS1, PARTY_ADDRESS2, PARTY_CITY FROM CSI_HZCA_ADDRESSES_V WHERE CUST_ACCOUNT_ID = :account_id ORDER BY CUST_ACCT_SITE_ID;
• Build a searchable address list: SELECT CUST_ACCT_SITE_ID, PARTY_NAME, PARTY_ADDRESS2 FROM CSI_HZCA_ADDRESSES_V WHERE UPPER(PARTY_ADDRESS2) LIKE UPPER('%' || :search || '%');

Because the view performs concatenation and truncation at query time, it is suited to display and selection, not to bulk extraction of Install Base address data; for volume processing, query the base TCA tables directly and apply the same join conditions documented above.