Search Results party_address2




Overview
Explore in AI Chat

Overview

APPS.CS_SYSTEM_BILLTO_LOC_RG_V is a read-only Oracle EBS database view owned by the APPS schema and registered under the FND Design Data application CS (Customer Service / Service/Oracle TeleService). It presents a consolidated result set of party and bill-to address information, joining customer account sites to their underlying party, party site, and physical location records. The view is classified as "Internal" with status VALID and is documented as Oracle Internal Use Only: Oracle Corporation does not support direct access to this object except from standard Oracle Applications programs. It is therefore intended to be consumed implicitly by Oracle Service and related runtime logic rather than as a supported public interface.

From a reporting and integration perspective, the view serves as a convenient denormalized projection combining the customer account site identifier, the customer account identifier, the party name, and address components (city, formatted address, and multiple address lines). The view is not referenced by any other database object, confirming it is a leaf-level consumer object. Users searching for the term "party_address" will find this view relevant because its PARTY_ADDRESS column exposes a long, concatenated address string (VARCHAR2(1207)), while PARTY_ADDRESS1/2/3 provide discrete, bounded address line values.

Underlying Base Objects

The view is defined over four base objects, exposed to APPS through synonyms:

Because these are the TCA (Trading Community Architecture) foundation tables, the view inherits the standard TCA data model relationships: a party owns party sites; a party site references a location; and a customer account site references a party site. The view collapses this multi-table chain into a single flattened SELECT list suited to Service application queries driven by a specific bill-to location requirement.

Key Columns

  • PARTY_ADDRESS (VARCHAR2(1207)) — the concatenated, display-ready party address; this is the column most directly associated with the "party_address" search term.
  • PARTY_ADDRESS1 / PARTY_ADDRESS2 / PARTY_ADDRESS3 (VARCHAR2 240/240/220) — the individual address line components of the location.
  • PARTY_CITY (VARCHAR2(60)) — the city of the party location.
  • PARTY_NAME (VARCHAR2(360)) — the party name from HZ_PARTIES.
  • CUST_ACCT_SITE_ID (NUMBER(15)) — the customer account site identifier, the primary join point to account site context.
  • CUST_ACCOUNT_ID (NUMBER(15)) — the customer account identifier.

No column in the documented structure is marked Mandatory, so consumers should guard against nulls, particularly for address elements that may be unmaintained on the base location record.

Common Use Cases and Queries

Typical scenarios include retrieving the bill-to address for a customer account site during Service request or order processing, resolving a party name and its mailing address for display, and reciprocal lookups between CUST_ACCT_SITE_ID and the address block. A basic query selecting all columns follows the documented query text:

  • Retrieve a bill-to location by account site:

SELECT PARTY_CITY, PARTY_ADDRESS, PARTY_NAME, CUST_ACCT_SITE_ID, PARTY_ADDRESS1, PARTY_ADDRESS2, PARTY_ADDRESS3, CUST_ACCOUNT_ID FROM APPS.CS_SYSTEM_BILLTO_LOC_RG_V WHERE CUST_ACCT_SITE_ID = :p_site_id;

  • Search by party name and city to locate candidate bill-to sites:

SELECT CUST_ACCOUNT_ID, CUST_ACCT_SITE_ID, PARTY_NAME, PARTY_ADDRESS FROM APPS.CS_SYSTEM_BILLTO_LOC_RG_V WHERE UPPER(PARTY_NAME) LIKE UPPER(:p_name) AND UPPER(PARTY_CITY) = UPPER(:p_city);

Given the Oracle Internal Use Only designation, these statements should be reserved for diagnostic and read-only reporting purposes. Where a supported integration is required, the underlying HZ_* TCA tables and their public APIs should be used instead.