Results for “axbv_trading_partners”

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

Overview

The view AXBV_TRADING_PARTNERS belongs to the Global Accounting Engine (AX) product family within Oracle E-Business Suite. It exposes trading partner reference data maintained by the Global Accounting Engine for use in financial reporting, subledger reconciliation, and intercompany accounting contexts. In releases 12.1.1 and 12.2.2, Global Accounting Engine objects such as this view serve as the bridge between transaction-level accounting data and the party definitions required for counterparty identification, reporting hierarchy mapping, and consolidation.

The view is defined with a WITH READ ONLY clause, which enforces read-only access. This is consistent with its role as a reporting and integration object: consumers query it to resolve trading partner identifiers and descriptive attributes, but they cannot use it as a DML path against the underlying party data. Because AXBV_TRADING_PARTNERS is designated a view rather than a base table, its contents are always derived from the source object at runtime, ensuring that reporting reflects the current state of the trading partner records without requiring a separate materialization step.

The ETRM documentation explicitly notes that the object is "Not implemented in this database." This is a significant operational detail. It means the view is shipped as part of the AX schema definition but is not necessarily deployed in every environment. Its presence depends on whether the Global Accounting Engine and the associated third-party data structures have been installed and configured. Analysts should verify deployment before relying on the object in a query or report definition.

Underlying Base Objects

The documented view text is straightforward:

SELECT APPLICATION_ID,
       THIRD_PARTY_ID,
       THIRD_PARTY_NAME,
       THIRD_PARTY_NUMBER
FROM   AX_THIRD_PARTIES_V
WITH READ ONLY

The sole documented base object is AX_THIRD_PARTIES_V, itself a view within the Global Accounting Engine schema. The ETRM metadata records "Referenced base objects: none documented," which indicates that no base tables are directly attributed to this view in the repository; the dependency chain terminates at another view layer. Practically, this layered design means that AXBV_TRADING_PARTNERS is a thin presentation wrapper over AX_THIRD_PARTIES_V, adding no transformation, filter, or join logic of its own. The column naming, however, is not a simple pass-through: the underlying columns are aliased to trading partner terminology, so the view serves primarily as a semantic renaming layer that aligns the generic third-party data model with the trading partner vocabulary used by intercompany and consolidation processes.

Key Columns

• APPLICATION_ID — Identifies the application context that owns the trading partner record. This column is passed through unchanged from AX_THIRD_PARTIES_V and typically corresponds to the FND_APPLICATION identifier, allowing consumers to scope trading partner data by owning application.
• TRADING_PARTNER_ID — The unique identifier of the trading partner. It is sourced from the THIRD_PARTY_ID column of the base view and is the primary join key for linking trading partner data to accounting, intercompany, or reporting records.
• TRADING_PARTNER_NAME — The descriptive name of the trading partner, mapped from THIRD_PARTY_NAME. This is the human-readable label used in reports and reconciliation listings.
• TRADING_PARTNER_NUMBER — The externally recognizable number or code assigned to the trading partner, mapped from THIRD_PARTY_NUMBER. This is typically the value used in printed output, correspondence, and cross-system matching.

Note that the view definition lists four source columns but the documented column list shows the aliased names, indicating the intentional renaming from "third party" to "trading partner" semantics.

Common Use Cases and Queries

The primary use case is resolving trading partner identifiers to names and numbers for financial and intercompany reporting. A typical query retrieves all partners for an application:

SELECT trading_partner_id,
       trading_partner_name,
       trading_partner_number
FROM   axbv_trading_partners
WHERE  application_id = :app_id
ORDER  BY trading_partner_name;

A second common pattern joins the view to accounting or intercompany detail to enrich transaction lines with partner names:

SELECT d.transaction_id,
       p.trading_partner_name,
       p.trading_partner_number,
       d.amount
FROM   axbv_trading_partners p,
       some_accounting_detail d
WHERE  d.trading_partner_id = p.trading_partner_id
AND    d.application_id     = p.application_id;

A third scenario is a validation or lookup query used to confirm that a given partner number exists before posting or reconciliation:

SELECT COUNT(*)
FROM   axbv_trading_partners
WHERE  trading_partner_number = :partner_number;

Because the object is read-only and not guaranteed to be implemented in every database, reports and integrations referencing AXBV_TRADING_PARTNERS should include defensive handling for the object's absence. Where the view is not deployed, consumers must fall back to AX_THIRD_PARTIES_V directly or to the underlying third-party data structures provided by the Global Accounting Engine installation.