Search Results site_status




Overview
Explore in AI Chat

Overview

APPS.CSD_PARTY_SITES_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates party site information with its associated site uses and location address details. It is owned by the APPS schema and is a denormalized, read-only projection that joins the core Trading Community Architecture (TCA) tables. The view presents one row per combination of party site, site use, and location, thereby exposing the full contextual picture of a party's physical or logical address together with its purpose (site use type) and current status.

Because party sites underpin many downstream modules — including Order Management, Receivables, Payables, Shipping, and Contracts — this view is frequently used in custom reports, concurrent programs, and interface extracts. The user query term "site_status" maps directly to the SITE_STATUS column derived from HZ_PARTY_SITES.STATUS, and to the related SITE_USE_STATUS column derived from HZ_PARTY_SITE_USES.STATUS.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms:

  • HZ_PARTY_SITES (aliased A) — the driving table, joined on PARTY_SITE_ID.
  • HZ_PARTY_SITE_USES (aliased B) — joined with an outer join (B.PARTY_SITE_ID(+)) on PARTY_SITE_ID, allowing party sites without a site use to still be returned.
  • HZ_LOCATIONS (aliased C) — inner-joined to HZ_PARTY_SITES on LOCATION_ID, supplying the address components.

The outer join on HZ_PARTY_SITE_USES means rows can appear with NULL SITE_USE_STATUS, SITE_USE_TYPE, and related site-use columns when no active use record exists. Both master-detail relationships are anchored on PARTY_SITE_ID and LOCATION_ID respectively.

Key Columns

Common Use Cases and Queries

A frequent requirement is to list active party sites with their address and primary site use. The following query retrieves active bill-to or ship-to records:

  • SELECT party_site_id, party_site_number, party_site_name, site_status, site_use_status, site_use_type, primary_per_type, address1, city, state, postal_code FROM apps.csd_party_sites_v WHERE site_status = 'A' AND site_use_status = 'A' AND site_use_type IN ('BILL_TO','SHIP_TO');
  • Determine parties lacking any site use, exploiting the outer join: SELECT party_id, party_site_id, party_site_name FROM apps.csd_party_sites_v WHERE site_use_type IS NULL;
  • Identify identifying addresses: SELECT * FROM apps.csd_party_sites_v WHERE identifying_address_flag = 'Y';
  • Extract active sites by country for integration feeds: filter on COUNTRY and SITE_STATUS and join PARTY_ID back to HZ_PARTIES for party name and party type.

Because the view is a straight join of TCA base tables, it should not be updated directly; site status and site use status changes must be applied to the underlying tables through the TCA APIs or the standard Oracle forms. Indexed access is best driven by PARTY_ID, PARTY_SITE_ID, or LOCATION_ID to avoid full scans on large HZ_PARTY_SITES volumes.