Search Results cs_cp_addresses_v




Overview
Explore in AI Chat

Overview

APPS.CS_CP_ADDRESSES_V is a reporting view in the Oracle E-Business Suite Service (CS) module, shipped under the APPS schema and documented as VALID in ETRM for releases 12.1.1 and 12.2.2. Its documented purpose is to expose the Installed at / Ship To information of the Product — that is, the address records associated with the customer party and customer account that own a service product installation. The view consolidates location, party, and customer account attributes into a single denormalized row per active party site, which makes it suitable for service-related reporting, diagnostics, and integration extracts that require a resolved "Installed At" or "Ship To" address context.

The view is particularly relevant to searches involving party_site_name, because it exposes the PARTY_SITE_NAME column directly from HZ_PARTY_SITES, alongside the surrogate location identifier, address lines, and the owning party and account identifiers.

Underlying Base Objects

The documented base objects referenced by CS_CP_ADDRESSES_V are:

The joins are: HL.LOCATION_ID = PARTY_SITE.LOCATION_ID, PARTY_SITE.PARTY_ID = HCA.PARTY_ID, and PARTY_SITE.PARTY_ID = HZP.PARTY_ID. A STATUS = 'A' predicate restricts output to active party sites, and a /*+ FIRST_ROWS */ hint indicates the view is tuned for interactive, low-latency retrieval rather than bulk warehouse loads.

Key Columns

  • LOCATION — aliased from PARTY_SITE_ID; the effective site identifier for the row.
  • SITE_NUMBER — the human-readable party site number from HZ_PARTY_SITES.
  • PARTY_SITE_NAME — the descriptive site name; the column most commonly searched by users and matched against customer-facing address labels.
  • PARTY_NAME / PARTY_ID — the owning party and its surrogate key.
  • CUST_ACCOUNT_ID — the customer account tied to the party, essential for account-scoped reporting.
  • ADDRESS1–ADDRESS4, CITY, STATE, ZIP, COUNTRY — the formatted address components.
  • DESCRIPTION — the location description from HZ_LOCATIONS.

Common Use Cases and Queries

Typical uses include: resolving the Installed At / Ship To address for a service product installation; validating party site data for a customer account; and feeding downstream integrations that require a flattened address record.

Retrieving a site by name:

  • SELECT location, party_site_name, site_number, party_name, city, state FROM cs_cp_addresses_v WHERE party_site_name LIKE 'ACME%';

Listing all active sites for a customer account:

  • SELECT cust_account_id, party_site_name, address1, city, country FROM cs_cp_addresses_v WHERE cust_account_id = :p_account_id;

Addresses should be filtered by both PARTY_SITE_NAME and CUST_ACCOUNT_ID in multi-account environments, since a party may own several accounts and sites.