Search Results party_address3




Overview
Explore in AI Chat

Overview

CS_SYSTEM_BILLTO_LOC_RG_V is a read-only view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the CS (Service) product family and is registered in ETRM with a VALID status. The view presents bill-to account site and party location information in a denormalized, report-friendly form. Rather than requiring the caller to join the four underlying Trading Community Architecture (TCA) tables and concatenate address elements manually, the view delivers pre-assembled address strings alongside the identifying keys of the customer account, account site, party site, and location.

Its primary role is to support Service module reporting, integration extracts, and downstream lookups where a single row per bill-to site is required together with a human-readable address and party name. Because the view resolves through TCA party, party site, and location entities, it reflects the master reference data used across Receivables, Order Management, and Service. Users who search for the term "party_address3" typically encounter this view because PARTY_ADDRESS3 is one of its exposed columns: it is the formatted address fragment generated by concatenating city, state, postal code, and country, truncated to 220 characters.

Underlying Base Objects

The view is defined over four TCA base tables, each accessed via a public synonym. These are HZ_CUST_ACCT_SITES_ALL, HZ_PARTY_SITES, HZ_LOCATIONS, and HZ_PARTIES. The joins are expressed as follows: HZ_PARTIES.PARTY_ID equals HZ_PARTY_SITES.PARTY_ID; HZ_CUST_ACCT_SITES_ALL.PARTY_SITE_ID equals HZ_PARTY_SITES.PARTY_SITE_ID; and HZ_PARTY_SITES.LOCATION_ID equals HZ_LOCATIONS.LOCATION_ID.

The effect of this join path is to associate each customer account site with its owning party, the party site that links it to a physical address, and the location record that stores the address components. HZ_CUST_ACCT_SITES_ALL is the account-site assignment table, HZ_PARTY_SITES is the intersection between parties and locations, HZ_LOCATIONS holds the street address, city, state, postal code, and country, and HZ_PARTIES holds the party name. The view inherits the security and data visibility characteristics of these TCA objects; no additional WHERE clause or organization filter is embedded in the documented view text.

Key Columns

  • PARTY_NAME — the party name from HZ_PARTIES, identifying the customer or organization associated with the bill-to site.
  • CUST_ACCOUNT_ID — the customer account identifier from HZ_CUST_ACCT_SITES_ALL.
  • CUST_ACCT_SITE_ID — the unique account site identifier, the most granular key exposed by the view.
  • LOCATION — the party site identifier (HZ_PARTY_SITES.PARTY_SITE_ID), linking the row to the party site entity.
  • PARTY_CITY — the city alone, taken directly from HZ_LOCATIONS.CITY.
  • PARTY_ADDRESS1 and PARTY_ADDRESS2 — the first two address lines from HZ_LOCATIONS.
  • PARTY_ADDRESS — a full concatenation of ADDRESS1 through ADDRESS4, city, state, postal code, and country, separated by spaces.
  • PARTY_ADDRESS3 — a condensed formatted address composed of city, state, postal code, and country. The expression inserts a comma-space separator after the city only when city is not null and at least one of state, country, or postal code is present, and the result is truncated with SUBSTR to 220 characters.

Note that ADDRESS3 and ADDRESS4 are used only inside the PARTY_ADDRESS concatenation; they are not exposed as individual columns.

Common Use Cases and Queries

Typical uses include Service request and installation reporting, bill-to address validation, and data extracts for interfaces that need a single formatted address per account site. A common query retrieves the formatted address for a given customer account:

SELECT cust_account_id,
       cust_acct_site_id,
       party_name,
       party_address3
FROM   apps.cs_system_billto_loc_rg_v
WHERE  cust_account_id = :p_cust_account_id;

A second pattern searches by city or party name to locate account sites for a region:

SELECT party_name,
       cust_acct_site_id,
       party_address
FROM   apps.cs_system_billto_loc_rg_v
WHERE  UPPER(party_city) = UPPER(:p_city);

Because PARTY_ADDRESS3 is capped at 220 characters and PARTY_ADDRESS contains embedded spaces for null elements, consumers should expect multiple consecutive spaces where address lines are absent. The view should be treated as a convenience reporting layer over TCA; for transactional updates, the underlying HZ tables remain the authoritative targets.