Results for “trading_partner_site_name”

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

Overview

AXBV_TRADING_PARTNER_SITES is a read-only database view shipped with the Oracle E-Business Suite Global Accounting Engine (product code AX). It presents trading partner site information in a denormalized form that maps a partner's application context, third-party identifier, and subordinate entity identifier into a reporting-friendly structure. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a lightweight access layer for downstream reporting, data extraction, and integration logic that must resolve a trading partner to its associated site or subordinate record without traversing the full underlying hierarchy directly.

The view is defined with the WITH READ ONLY clause, meaning no DML operations are permitted against it. It is therefore intended strictly for query and extraction purposes. The ETRM documentation notes that the referenced base objects are not separately documented and that the object is "Not implemented in this database" in the reference environment, which is common for AX views that are delivered but only instantiated in installations where the Global Accounting Engine is configured with third-party trading partner data.

Underlying Base Objects

The view is defined over a single documented base object, AX_SUBS_V, itself a view within the AX schema. The select list maps four source columns to the exposed column names:

• APPLICATION_ID — sourced directly from AX_SUBS_V.APPLICATION_ID, identifying the owning application (for example, the AX application context).
• THIRD_PARTY_ID — sourced from AX_SUBS_V.THIRD_PARTY_ID, the trading partner identifier, exposed as TRADING_PARTNER_ID.
• SUB_ID — sourced from AX_SUBS_V.SUB_ID, exposed as TRADING_PARTNER_SITE_ID.
• SUB_NAME — sourced from AX_SUBS_V.SUB_NAME, exposed as TRADING_PARTNER_SITE_NAME.

Because it resolves through a single intermediate view rather than joined base tables, the view does not perform additional filtering or aggregation. Its value lies in the column aliasing, which presents AX-internal naming (subs/third party) using trading-partner terminology familiar to financial and integration developers.

Key Columns

• APPLICATION_ID — Numeric identifier of the application context under which the trading partner record is registered. Used to scope queries to the correct AX application instance.
• TRADING_PARTNER_ID — The partner-level identifier (mapped from THIRD_PARTY_ID). This distinguishes one trading partner from another and is typically the join key to partner header data.
• TRADING_PARTNER_SITE_ID — The site or subordinate identifier (mapped from SUB_ID). It represents a specific location, address, or transactional site belonging to a trading partner.
• TRADING_PARTNER_SITE_NAME — The descriptive name associated with the site (mapped from SUB_NAME), suitable for display in reports and interfaces.

Common Use Cases and Queries

Typical scenarios include resolving site names for trading partners in GL or AX reconciliation reports, populating partner/site reference data in integrations, and validating that partner/site combinations exist before posting transactions. A basic query lists all sites for a given partner:

• SELECT trading_partner_id, trading_partner_site_id, trading_partner_site_name FROM axbv_trading_partner_sites WHERE application_id = :app_id ORDER BY trading_partner_id, trading_partner_site_id;
• SELECT trading_partner_site_name FROM axbv_trading_partner_sites WHERE trading_partner_id = :partner_id AND trading_partner_site_id = :site_id;

For lookups that join AX transaction data to partner site descriptions, the view can be joined on application_id, trading_partner_id, and trading_partner_site_id. Developers should note the read-only nature of the view and confirm availability, since ETRM records indicate the object may not be implemented in every database instance.