Search Results ax_third_parties_v




Overview
Explore in AI Chat

Overview

AX_THIRD_PARTIES_V is a consolidated reporting view delivered within the AX – Global Accounting Engine product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its purpose is to provide a single, normalized source for the identifier and descriptive name of every "third party" that the Global Accounting Engine may need to reference when producing subledger and general ledger accounting entries, reconciliation reports, and downstream integration extracts.

The view answers the recurring question of how third parties are named and numbered across the EBS modules that own them. Rather than forcing consumers to query supplier, customer, and inventory organization tables separately, AX_THIRD_PARTIES_V unions these sources into one row-per-third-party projection keyed by the owning application and by a third-party identifier. This makes it a natural lookup source for the third_party_name attribute commonly required in accounting engine extracts and audit reports.

Underlying Base Objects

Although ETRM does not document explicit dependencies, the view text shows it is defined as a UNION ALL-style consolidation over four sources, each tagged with the application that owns the third party:

  • PO_VENDORS — tagged with APPLICATION_ID 200 (Payables), supplying suppliers as third parties.
  • RA_CUSTOMERS — tagged with APPLICATION_ID 222 (Receivables), supplying customers, with the sentinel customer identifier -999 excluded.
  • ORG_ORGANIZATION_DEFINITIONS — tagged with APPLICATION_ID 401 (Inventory), supplying inventory organizations, with organization identifier 0 excluded.
  • AX_LOOKUPS — supplying placeholder rows for the AX_3RD_PARTY_UNIDENTIFIED lookup type, covering the "CUSTOMER" (-999) and "INVENTORY" (0) unidentified cases that are otherwise filtered out of the preceding branches.

The view therefore depends on the standard supplier, customer, and organization definition tables, plus the AX lookup table used for controlled values. It is a read-only virtual object; no physical storage or DBA implementation is required, and ETRM notes it is not implemented as a database object in the source environment.

Key Columns

  • APPLICATION_ID — the identifier of the application that owns the third party (200 for Payables/vendors, 222 for Receivables/customers, 401 for Inventory/organizations). It qualifies the meaning of THIRD_PARTY_ID.
  • THIRD_PARTY_ID — the surrogate key of the third party within its owning application, mapped from VENDOR_ID, CUSTOMER_ID, or ORGANIZATION_ID, with -999 and 0 reserved for unidentified customer and inventory third parties.
  • THIRD_PARTY_NAME — the descriptive display name of the third party, drawn from VENDOR_NAME, CUSTOMER_NAME, ORGANIZATION_NAME, or the AX_LOOKUPS meaning for placeholder rows.
  • THIRD_PARTY_NUMBER — the human-readable reference number, sourced from SEGMENT1 for vendors, CUSTOMER_NUMBER for customers, and ORGANIZATION_CODE for organizations.

Common Use Cases and Queries

The view is typically used to resolve third_party_name for a given identifier, to populate reconciliation and audit reports spanning suppliers, customers, and organizations, and to drive Global Accounting Engine extracts that must classify third parties consistently.

To resolve a name for a known third party:

  • SELECT third_party_name FROM ax_third_parties_v WHERE application_id = :app_id AND third_party_id = :id;

To list all third parties owned by a single application (for example, suppliers):

  • SELECT third_party_number, third_party_name FROM ax_third_parties_v WHERE application_id = 200 ORDER BY third_party_name;

To search by name fragment across all sources:

  • SELECT application_id, third_party_id, third_party_number, third_party_name FROM ax_third_parties_v WHERE UPPER(third_party_name) LIKE UPPER('%'||:name||'%');

Reports should always filter or group by APPLICATION_ID, since THIRD_PARTY_ID values are only unique within their owning application and can otherwise collide across sources.