Results for “axfv_trading_partner_sites”

4 results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AXFV_TRADING_PARTNER_SITES is a read-only view belonging to the AX - Global Accounting Engine product family in Oracle E-Business Suite. It presents a consolidated, reporting-friendly picture of trading partner sites by joining subscription records to their associated third party definitions and application registrations. In the context of the Global Accounting Engine, a "trading partner" represents an external or internal entity—such as a supplier, customer, or intercompany organization—with which accounting transactions are exchanged and balanced. The view exposes the relationship between a subscription (SUB_ID), the third party (THIRD_PARTY_ID) it is tied to, and the owning application (APPLICATION_ID).

Because the view is declared WITH READ ONLY, it is intended strictly for query and reporting workloads rather than for data manipulation. It is typically consumed by reporting tools, extracts, and integration interfaces that need to resolve a trading partner site to a human-readable name and its owning application. The view carries the Oracle Proprietary, Confidential Information designation, and its metadata is documented under ETRM 12.2.2.

Underlying Base Objects

The view is defined over three base objects, as shown in its documented view text:

The join conditions link subscriptions and third parties on both APPLICATION_ID and THIRD_PARTY_ID, while the application is joined purely on APPLICATION_ID. This ensures that a subscription, its third party, and the application name are always presented in a mutually consistent context. The ETRM metadata notes that referenced base objects are "none documented" at the table level, and that the object is "Not implemented in this database" for the specific environment captured—meaning the view exists as defined metadata but was not instantiated in that particular instance.

Key Columns

The view exposes the following documented columns. Note that the query aliases (SUB, TP, APP) map to the logical column set below; several site-specific columns appear in the column list as part of the standard trading partner site reporting shape:

  • APPLICATION_ID — identifier of the EBS application that owns the subscription and third party.
  • TRADING_PARTNER_ID — identifier of the trading partner (mapped from the third party).
  • TRADING_PARTNER_SITE_ID — the site identifier for the trading partner.
  • TRADING_PARTNER_SITE_NAME — descriptive name of the trading partner site.
  • TRADING_PARTNER_NAME — descriptive name of the trading partner (from AX_THIRD_PARTIES_V).
  • APPLICATION_NAME — the application's display name resolved through FND_APPLICATION_VL.

In the documented view text, the subscription name (SUB_NAME) is also selected, providing a useful label for the underlying subscription record.

Common Use Cases and Queries

Typical uses include resolving site names for intercompany or trading partner reporting, driving reconciliation extracts, and populating interface staging tables. A representative query follows:

  • List trading partner sites for an application: SELECT application_name, trading_partner_name, trading_partner_site_name FROM axfv_trading_partner_sites WHERE application_id = :app_id ORDER BY trading_partner_name;
  • Resolve a subscription to its partner: SELECT sub_name, trading_partner_name FROM axfv_trading_partner_sites WHERE sub_id = :sub_id;
  • Audit partner-to-application mappings: SELECT trading_partner_id, application_name FROM axfv_trading_partner_sites GROUP BY trading_partner_id, application_name;

Because the view is read-only and already joins the three base objects, it is preferable to querying AX_SUBS_V, AX_THIRD_PARTIES_V, and FND_APPLICATION_VL separately, reducing join complexity in reporting SQL.