Search Results party_site_name

Overview

XNC_PVT_PARTY_SITES_V is a database view associated with the XNC – Sales for Communications product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the relationship between a Trading Community Architecture (TCA) party and the locations registered against that party. In TCA terms, a party site is the association of a party (a person or organization) with a physical location, optionally identified by a party site name. This view surfaces the active party site records — that is, rows whose STATUS is 'A' — and projects only the four columns most relevant to party-to-location resolution: PARTY_SITE_ID, PARTY_ID, LOCATION_ID, and PARTY_SITE_NAME.

The object name carries the XNC_PVT_ prefix. The PVT segment conventionally indicates a private or internal implementation object, and the ETRM documentation explicitly records this view as "Not implemented in this database," with no owner or base objects documented for the current release and the XNC product itself marked obsolete. Accordingly, the view should be treated as a historical or legacy artifact. Its value in reporting and integration lies less in active use than in understanding data model lineage where customizations, extracts, or older interfaces reference party site naming.

Underlying Base Objects

The documented view text is a simple projection over a single base table:

• HZ_PARTY_SITES — the TCA table that stores party-to-location associations, including the party site identifier, party identifier, location identifier, party site name, status, and related attributes.

The view imposes a single filter, STATUS = 'A', restricting output to active party sites. No joins to HZ_PARTIES, HZ_LOCATIONS, or other TCA entities are present in the documented definition; therefore the view is a denormalized, filtered slice of the base table rather than a multi-table construct. The ETRM metadata notes that referenced base objects are not documented in the 12.2.2 registry, consistent with the view's obsolete status.

Key Columns

• PARTY_SITE_ID — Primary identifier of the party site record in HZ_PARTY_SITES. Used to reference a specific party-location association.
• PARTY_ID — Identifier of the owning party in the TCA model. Links back to HZ_PARTIES.PARTY_ID.
• LOCATION_ID — Identifier of the associated location. Links back to HZ_LOCATIONS.LOCATION_ID.
• PARTY_SITE_NAME — The descriptive name assigned to the party site. This is the column most directly associated with the search term party_site_name, and it is the human-readable label distinguishing one site from another for the same party.

Note that the view deliberately omits status and audit columns; the active-status filter is applied internally.

Common Use Cases and Queries

Typical scenarios include resolving a party's active sites by name, remapping legacy XNC identifiers to standard TCA views such as HZ_PARTY_SITES_V, and validating data migration or interface loads that populated party site names. Because the view is obsolete and not implemented, equivalent results are normally obtained directly from HZ_PARTY_SITES_V or the base table.

A representative query against this view:

• SELECT party_site_id, party_id, location_id, party_site_name FROM xnc_pvt_party_sites_v WHERE party_id = :p_party_id;

For current implementations, the functionally equivalent query would target HZ_PARTY_SITES with an explicit status = 'A' predicate, ensuring the same active-site semantics while relying on a supported object.