Search Results third_party_site_id




Overview
Explore in AI Chat

Overview

APPS.XLA_THIRD_PARTY_SITES_V is a reporting view in the Oracle E-Business Suite Subledger Accounting (XLA) schema. It presents a unified, consolidated list of "third party sites" drawn from two distinct master data domains: supplier sites from Payables and customer site uses from Receivables. The view is a UNION ALL of two independent queries, each producing a consistent five-column projection, so that downstream accounting and reporting components can reference either a supplier site or a customer site through a single, uniform interface.

Within the XLA architecture, third party sites are relevant wherever subledger accounting must identify the trading partner location associated with a transaction, such as the point of origination or destination of a goods or services exchange. The view abstracts away the differing primary key structures of the supplier and customer models and normalizes them into a common shape, which simplifies joins in accounting event and journal line extraction logic. Because it is a view rather than a table, it stores no data of its own and always reflects the current state of its underlying source tables.

The third_party_type column is the discriminator that indicates which source domain a given row originated from, making the view particularly useful when a query must filter or classify records by party category.

Underlying Base Objects

The view is owned by APPS and is defined over five referenced base objects, all exposed as synonyms for the convenience of the APPS schema:

  • AP_SUPPLIERS — supplier header records; supplies the VENDOR_ID used as the third party identifier.
  • AP_SUPPLIER_SITES_ALL — supplier site records across all operating units; supplies the site identifier, site code, and address line.
  • HZ_CUST_ACCOUNTS — customer (account) records; supplies the CUST_ACCOUNT_ID used as the third party identifier.
  • HZ_CUST_ACCT_SITES_ALL — the association between customer accounts and their addresses/sites.
  • HZ_CUST_SITE_USES_ALL — the specific business purposes (site uses) for a customer account site; supplies the site use identifier, code, and location.

The first branch of the UNION ALL joins AP_SUPPLIERS to AP_SUPPLIER_SITES_ALL on VENDOR_ID, generating rows that represent supplier sites. The second branch chains HZ_CUST_ACCOUNTS to HZ_CUST_ACCT_SITES_ALL on CUST_ACCOUNT_ID and then to HZ_CUST_SITE_USES_ALL on CUST_ACCT_SITE_ID, generating rows that represent customer site uses. No filtering predicates are applied beyond these join conditions, so all supplier sites and all customer site uses are returned.

Key Columns

  • THIRD_PARTY_SITE_ID — The site-level identifier. For supplier rows this is VENDOR_SITE_ID; for customer rows this is SITE_USE_ID. Note that the two branches draw this value from different sequences and tables, so identifiers are unique only within their own third party type.
  • THIRD_PARTY_ID — The party-level identifier. For supplier rows this is VENDOR_ID; for customer rows this is CUST_ACCOUNT_ID.
  • THIRD_PARTY_TYPE — A single-character discriminator: the literal 'S' identifies supplier sites, and 'C' identifies customer site uses. This is the primary column of interest when classifying or filtering results.
  • THIRD_PARTY_SITE_CODE — The site code: VENDOR_SITE_CODE for supplier sites or SITE_USE_CODE for customer site uses.
  • LOCATION — The address line associated with the site. For supplier rows this is ADDRESS_LINE1 from the supplier site; for customer rows it is the LOCATION column from the customer site use record.

Common Use Cases and Queries

Typical usage involves resolving a site identifier to a party and type, classifying third parties by category, or joining the view into broader accounting extraction queries. Because supplier and customer identifiers share the same column names but different value spaces, always constrain by THIRD_PARTY_TYPE when filtering on identifier.

Retrieve all supplier sites only:

  • SELECT third_party_site_id, third_party_id, third_party_site_code, location FROM apps.xla_third_party_sites_v WHERE third_party_type = 'S';

Retrieve customer site uses only:

  • SELECT third_party_site_id, third_party_id, third_party_site_code, location FROM apps.xla_third_party_sites_v WHERE third_party_type = 'C';

Count sites by party type:

  • SELECT third_party_type, COUNT(*) FROM apps.xla_third_party_sites_v GROUP BY third_party_type;

Resolve a specific customer account's sites by joining on the party identifier:

  • SELECT v.third_party_site_id, v.third_party_site_code FROM apps.xla_third_party_sites_v v WHERE v.third_party_type = 'C' AND v.third_party_id = :cust_account_id;

In all cases, apply the third_party_type predicate to avoid collisions between supplier and customer identifier ranges.