Results for “party_site_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

ASO_PVT_PARTY_SITES_V is an APPS-owned database view in Oracle E-Business Suite, delivered under the ASO (Order Capture) product family. It exposes a restricted projection of party site data maintained in the Trading Community Architecture (TCA) registry. The view is published as a public synonym and is designed to provide Order Capture and related modules with a lightweight, read-only interface to active party sites without requiring direct access to the underlying HZ_PARTY_SITES table.

Because the view isolates a small set of columns and applies an intrinsic status filter, it functions as a security and abstraction layer. Report authors, form developers, and integration developers can query it for validated, active party site records while remaining insulated from the broader and more volatile column set of the base table. The object is marked VALID in ETRM for both 12.1.1 and 12.2.2, indicating the definition has remained stable across those releases.

Underlying Base Objects

The documented base object referenced by this view is HZ_PARTY_SITES, accessed in the APPS schema through its synonym. HZ_PARTY_SITES is the TCA table that stores the association between a party and a location, effectively representing a physical or business site belonging to that party. Every party site row links a PARTY_ID to a LOCATION_ID, where the location details (address, geography, and related attributes) reside in HZ_LOCATIONS and its dependent tables.

The view definition selects four columns from HZ_PARTY_SITES and restricts the result set to rows where STATUS equals 'A' (active). Consequently, inactive or obsolete party sites are excluded at the view layer, and all downstream consumers inherit that filter automatically. The synonym APPS.ASO_PVT_PARTY_SITES_V provides the standard naming path used by Oracle forms, concurrent programs, and custom code.

Key Columns

• PARTY_SITE_ID — The unique primary key of the party site record. This is the identifier most commonly stored as a foreign key on downstream transactional tables such as order headers and shipping assignments.
• PARTY_ID — The identifier of the owning party (customer, prospect, or organization) in the TCA model. It links the site to the party record in HZ_PARTIES.
• LOCATION_ID — The identifier of the associated location record, which resolves to the actual address and geography information. This value is used to join to HZ_LOCATIONS for address-based reporting.
• PARTY_SITE_NAME — The user-defined or system-generated name of the party site. This is the attribute most frequently retrieved by users searching for "party_site_name," and it is the human-readable label that distinguishes one site from another for the same party.

Common Use Cases and Queries

Typical usage includes validating that a selected party site is active before it is written to an order, populating list of values (LOV) pickers, and supplying site names to operational reports. A simple lookup by party demonstrates the most common pattern:

• SELECT party_site_id, party_id, location_id, party_site_name FROM aso_pvt_party_sites_v WHERE party_id = :p_party_id;
• SELECT party_site_id, party_site_name FROM aso_pvt_party_sites_v WHERE UPPER(party_site_name) LIKE UPPER(:p_name || '%');
• SELECT ps.party_site_id, ps.party_site_name, loc.address1, loc.city FROM aso_pvt_party_sites_v ps, hz_locations loc WHERE ps.location_id = loc.location_id AND ps.party_id = :p_party_id;

Because the view already filters on STATUS = 'A', no additional status predicate is required in these queries. Developers should note that the view is read-only, carries no column for status, and returns only four attributes, so any requirement for address, contact, or site-purpose detail must be satisfied by joining to the wider TCA tables.