Search Results xla_third_party_sites_v




Overview
Explore in AI Chat

Overview

XLA_THIRD_PARTY_SITES_V is a Subledger Accounting (XLA) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to expose third party site information in a consolidated, subledger-facing form. In Subledger Accounting, a "third party" is the external party associated with a subledger transaction — a supplier in the Payables context or a customer in the Receivables context. This view normalizes the site and location data attached to those parties into a single, uniformly named projection so that accounting and reporting components can retrieve a third party site without embedding product-specific joins to the underlying Payables and Receivables/HZ tables.

The view is a UNION ALL of two branches, one for supplier sites and one for customer sites. This design allows XLA reporting, journal line enrichment, and integration extracts to resolve site-level context through a single query regardless of whether the underlying third party is a supplier or a customer. The THIRD_PARTY_TYPE column acts as the discriminator between the two sources.

Underlying Base Objects

The view is defined over five base objects (referenced as synonyms in the APPS schema):

The supplier branch joins AP_SUPPLIERS to AP_SUPPLIER_SITES_ALL on VENDOR_ID. The customer branch joins 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. Because the view draws on all organization units in the sites tables, results are not implicitly restricted by operating unit; callers must apply that filter themselves where applicable.

Key Columns

  • THIRD_PARTY_SITE_ID — the site identifier. For suppliers this maps to VENDOR_SITE_ID; for customers it maps to SITE_USE_ID.
  • THIRD_PARTY_ID — the third party identifier. For suppliers this is VENDOR_ID; for customers it is CUST_ACCOUNT_ID. The user search term "third_party_id" resolves directly to this column and is the primary key used to correlate the view with XLA transaction and accounting data.
  • THIRD_PARTY_TYPE — a single-character discriminator: S for supplier (Payables) and C for customer (Receivables). Any join or aggregate must account for this value to avoid ambiguity between vendor and customer identifiers.
  • THIRD_PARTY_SITE_CODE — the site code. Suppliers provide VENDOR_SITE_CODE; customers provide SITE_USE_CODE, reflecting the differing semantics of site usage between the two products.
  • LOCATION — the address text. Suppliers return ADDRESS_LINE1; customers return the LOCATION value from the site use record.

Common Use Cases and Queries

This view is typically used in Subledger Accounting diagnostics, custom reports, and integration extracts where a third party site must be resolved alongside accounting entries. A representative query retrieves site details for a given third party:

  • SELECT third_party_id, third_party_type, third_party_site_id, third_party_site_code, location FROM xla_third_party_sites_v WHERE third_party_id = :p_id AND third_party_type = 'S';
  • SELECT third_party_type, COUNT(*) FROM xla_third_party_sites_v GROUP BY third_party_type;
  • Joining the view to XLA journal line tables on THIRD_PARTY_ID and THIRD_PARTY_TYPE to enrich accounting output with site-level location data.

Because the view performs a UNION ALL without deduplication, records for the same party may appear multiple times when multiple sites exist. Consumers should always constrain by THIRD_PARTY_TYPE and, where relevant, by the site identifier to obtain a deterministic result.