Search Results okx_cust_site_uses_v




Overview
Explore in AI Chat

Overview

OKX_CUST_SITE_USES_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the OKX product family, which handles Contracts Integration, and its documented description is "Customer site uses." The view consolidates customer account site-use records with their associated party sites, physical locations, and formatted addresses into a single, denormalized result set. Within the E-Business Suite data model, a customer account site represents a specific business purpose assigned to a party site, such as bill-to, ship-to, or statement-to. The view exposes these uses alongside human-readable geographic details, removing the need for callers to join the Trading Community Architecture (TCA) tables themselves.

The view is particularly relevant to keyword searches involving "party_site_name." That attribute is surfaced directly as the PARTY_SITE_NAME column, which originates from HZ_PARTY_SITES. By publishing this column together with account, location, and address attributes, the view supports contract integration processes and downstream reporting where the identity of a customer site must be resolved by its party site name rather than by internal identifiers alone.

Underlying Base Objects

The ETRM metadata documents the view as defined over the following referenced objects:

  • ARP_ADDR_LABEL_PKG (PACKAGE) — used to format the mailing address into a single DESCRIPTION string.
  • HZ_CUST_ACCT_SITES_ALL (SYNONYM) — the customer account site assignments.
  • HZ_CUST_SITE_USES (SYNONYM) — the site-use records driving the view.
  • HZ_LOCATIONS (SYNONYM) — the physical address records.
  • HZ_PARTY_SITES (SYNONYM) — the party site records, including PARTY_SITE_NAME and the identifying address flag.

The join path is explicit in the view text: HZ_CUST_SITE_USES joins to HZ_CUST_ACCT_SITES_ALL on CUST_ACCT_SITE_ID; HZ_CUST_ACCT_SITES_ALL joins to HZ_PARTY_SITES on PARTY_SITE_ID; and HZ_PARTY_SITES joins to HZ_LOCATIONS on LOCATION_ID. A filter restricts results to locations whose CONTENT_SOURCE_TYPE is 'USER_ENTERED', excluding seeded or imported locations. The address label package is invoked column-by-column at query time.

Key Columns

  • PARTY_SITE_NAME — the descriptive name of the party site, sourced from HZ_PARTY_SITES.
  • SITE_USE_CODE — identifies the purpose of the site use, for example bill-to or ship-to.
  • STATUS (aliased B_STATUS) and CUST_ACCT_SITE_STATUS — active/inactive indicators at the site-use and account-site levels respectively.
  • CUST_ACCT_SITE_ID, CUST_ACCOUNT_ID, PARTY_SITE_ID, PARTY_ID — the TCA identifiers linking the record to its account and party.
  • LOCATION_ID and NAME — the location identifier and the site-use name.
  • ADDRESS1 through ADDRESS4, CITY, COUNTY, STATE, PROVINCE, POSTAL_CODE, COUNTRY — the raw address components from HZ_LOCATIONS.
  • DESCRIPTION — the formatted address returned by ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS, with LOCATION_DESCRIPTION holding the location description.
  • IDENTIFYING_ADDRESS_FLAG — indicates whether the site is the party's identifying address.
  • ORG_ID — the operating unit context; PRIMARY_UOM_CODE is a placeholder of NULL; PAYMENT_TERM_ID carries the payment term from the site use.

Common Use Cases and Queries

Typical uses include resolving customer site uses for contract integration in OKX, validating that a party site name maps to an active bill-to or ship-to use, and extracting formatted customer addresses for reporting. A representative query searching by party site name is:

SELECT cust_account_id, party_site_id, party_site_name, site_use_code, status, city, country
FROM apps.okx_cust_site_uses_v
WHERE party_site_name = :p_party_site_name;

To retrieve all active site uses for a given account:

SELECT cust_acct_site_id, site_use_code, party_site_name, description
FROM apps.okx_cust_site_uses_v
WHERE cust_account_id = :p_cust_account_id
AND status = 'A';

Because the address is already formatted, the DESCRIPTION column can be selected directly for correspondence or integration payloads without additional TCA joins. Standard considerations apply: query via the APPS schema or a synonym, observe ORG_ID for multi-org filtering, and expect the underlying synonyms to resolve to the HZ tables documented above.