Search Results party_site_code




Overview
Explore in AI Chat

Overview

APPS.JAI_CMN_CUSTOMER_SITES_V is a documented Oracle E-Business Suite view owned by the APPS schema and registered under FND Design Data as JA.JAI_CMN_CUSTOMER_SITES_V. It exposes a compact projection of customer site information drawn from the Oracle Receivables and Trading Community (HZ) model, filtered to the party site and customer account site context. The view is part of the JAI (India Localization / JA common) object family and is marked VALID in ETRM metadata for both 12.1.1 and 12.2.2. Its role is to provide a simplified, denormalized customer site reference for downstream reporting and integration logic, particularly where a customer site must be resolved by its user-visible code rather than only by the internal numeric identifier. This is directly relevant to users searching on "party_site_code", since that attribute is one of only four columns the view exposes. Oracle's standard warning applies: this view is documented as Oracle Internal Use Only, and Oracle does not support direct access to application data through it except from standard Oracle Applications programs. Consequently it should be treated as a read-only, internal reference object rather than a supported public API.

Underlying Base Objects

ETRM dependency metadata records that JAI_CMN_CUSTOMER_SITES_V references the following APPS synonyms: HZ_CUST_ACCOUNTS, HZ_CUST_ACCT_SITES_ALL, HZ_CUST_SITE_USES_ALL, HZ_PARTIES, HZ_PARTY_SITES, and JAI_CMN_CUS_ADDRESSES. These correspond to the core TCA entities — the customer account header, the account site assignments, the site-use (bill-to/ship-to) definitions, the party record, the party site record — plus the JAI localization address table. The view therefore joins party-level and account-level site data into a single, lightweight rowset. On the dependency side, JAI_CMN_CUSTOMER_SITES_V is itself referenced by APPS.JAI_CMN_CESS_TRXS_V, confirming its intended function as a helper view rather than an end-user reporting object. Because the base objects are HZ and Receivables constructs, the view inherits their multi-org behavior through the ORG_ID column.

Key Columns

The view is deliberately narrow, exposing exactly four columns:

  • PARTY_SITE_ID (NUMBER(15), mandatory): the internal numeric identifier of the party site, corresponding to HZ_PARTY_SITES.PARTY_SITE_ID. This is the primary join key back to TCA party site data.
  • PARTY_SITE_CODE (VARCHAR2(40)): the externally visible, user-defined site code. This is the attribute referenced by the "party_site_code" search, and it is the natural-key equivalent to PARTY_SITE_ID. It is the value users recognize on customer and site forms.
  • ORG_ID (NUMBER(15)): the operating unit identifier, enabling multi-org filtering so callers see only sites relevant to their organization context.
  • PARTY_ID (NUMBER(15)): the party identifier linking the site back to the HZ_PARTIES record for the customer or party.

Common Use Cases and Queries

Typical usage is resolving a site code to a party site identifier, or restricting site lookups to a single operating unit. The simplest documented query is a full projection:

  • SELECT PARTY_SITE_ID, PARTY_SITE_CODE, ORG_ID, PARTY_ID FROM APPS.JAI_CMN_CUSTOMER_SITES_V;
  • Filtering by code: SELECT PARTY_SITE_ID, PARTY_ID FROM APPS.JAI_CMN_CUSTOMER_SITES_V WHERE PARTY_SITE_CODE = :p_code AND ORG_ID = :p_org_id;
  • Listing all sites for a party: SELECT PARTY_SITE_CODE FROM APPS.JAI_CMN_CUSTOMER_SITES_V WHERE PARTY_ID = :p_party_id;

In practice the view supports India-localization processes and any logic needing a code-based site lookup without joining the HZ schema directly. Developers should note the internal-only status and, where supported access is required, resolve sites through TCA public views instead.