Search Results party_site_number

Overview

OKX_PARTY_SITES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKX – Contracts Integration product. The view carries the status VALID and presents a flattened, presentation-ready perspective of party site address data used by contracts-related integration flows. In EBS 12.1.1 and 12.2.2, the Trading Community Architecture (TCA) model stores party sites and locations across multiple normalized tables, including HZ_PARTY_SITES and HZ_LOCATIONS. The OKX_PARTY_SITES_V view denormalizes a subset of that model into a single, cursor-friendly row per party site, coupling the site record with its postal address attributes and a pre-formatted address string. Its description, "Party site uses," indicates that the view exists to expose the set of party sites that downstream OKX contract processing or outbound integrations may reference when populating supplier, customer, or contract party address information.

Underlying Base Objects

The view definition joins HZ_PARTY_SITES (aliased PSE) to HZ_LOCATIONS (aliased LCN) on LOCATION_ID, with a predicate restricting results to locations where CONTENT_SOURCE_TYPE equals 'USER_ENTERED'. This filter excludes locations originating from external or non-user content sources, ensuring that only user-maintained addresses surface through the view. The documented base objects referenced by this view are HZ_PARTY_SITES, HZ_LOCATIONS (both exposed through synonyms), and the ARP_ADDR_LABEL_PKG package. ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS is invoked during the SELECT to build a consolidated address string, truncated to 80 characters, so that consumers do not need to replicate address formatting logic. Party site rows are also keyed with synthetic identifiers ID1 (PARTY_SITE_ID) and ID2 (a literal '#'), a convention commonly applied to views used as value sets or LOV sources.

Key Columns

The view exposes the following columns, drawn from the documented view text and column list:

• LOCATION_ID, PARTY_SITE_NUMBER, PARTY_ID – Identifiers linking the site to its location record, site number, and owning party.
• NAME – The party site name (from PARTY_SITE_NAME).
• STATUS – The site status indicator.
• ADDRESS1 through ADDRESS4, CITY, POSTAL_CODE, STATE, PROVINCE, COUNTY, COUNTRY – Postal address attributes sourced from HZ_LOCATIONS.
• LOCATION_DESCRIPTION – The location description from HZ_LOCATIONS.DESCRIPTION.
• DESCRIPTION – A formatted address string produced by ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS and truncated to 80 characters.
• IDENTIFYING_ADDRESS_FLAG – Flag indicating whether the site is the identifying address for the party.
• ADDRESSEE – The addressee text associated with the party site.
• ID1, ID2 – Surrogate key columns (PARTY_SITE_ID and a literal '#') supporting lookup integration.

Common Use Cases and Queries

The view is typically consumed when contract integration routines need to enumerate valid party sites with user-entered addresses, or when reporting must resolve a party site to a single display-ready address line. A representative query retrieving all sites for a given party follows:

SELECT party_site_id, party_site_number, name, country, city, address1, description
FROM apps.okx_party_sites_v
WHERE party_id = :p_party_id
AND status = 'A';

To locate a site by its formatted address string, consumers may filter on DESCRIPTION, for example: SELECT party_site_id, address1, city, description FROM apps.okx_party_sites_v WHERE UPPER(description) LIKE '%MAIN STREET%'. Because the formatted string is precomputed at query time by ARP_ADDR_LABEL_PKG, queries against DESCRIPTION can be resource-intensive on large data sets, and filtering on indexed base columns such as PARTY_ID or LOCATION_ID is preferable. The view is also suited for LOV and value-set style integration, using ID1 as the returned identifier and DESCRIPTION as the displayed value.