Search Results ax_third_parties_subs_v




Overview

The view AX_THIRD_PARTIES_SUBS_V belongs to the AX – Global Accounting Engine product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a consolidated, normalized list of "third parties" and their associated "sub" entities (subsidiary addresses or site usages) drawn from multiple source systems — Payables suppliers, Receivables customers, and inventory organizations. The view's central purpose is to provide a unified identification roster that the Global Accounting Engine (AX) uses when classifying accounting transactions that cannot be attributed to a recognized party. The term unidentified third party is significant here: the view is closely tied to the lookup type AX_3RD_PARTY_UNIDENTIFIED, which supplies placeholder codes and meanings for transactions whose counterparty is unknown.

By returning a stable set of (THIRD_PARTY_ID, SUB_ID) pairs, the view supports AX subledger reconciliation, party balancing, and reporting across the ledger. It is a reporting and integration object rather than a transactional one.

Underlying Base Objects

The documented view definition is a UNION of several subqueries. The base tables and objects referenced are:

The ETRM metadata for 12.2.2 does not document a formal base-object list; the objects above are inferred from the view text. The view itself is not implemented as a physical table in the reference database.

Key Columns

  • APPLICATION_ID — numeric identifier of the source application (200 = Payables, 222 = Receivables, 401 = Inventory/Organizations).
  • THIRD_PARTY_ID — unique identifier of the party; sourced from VENDOR_ID, CUSTOMER_ID, or ORGANIZATION_ID. A value of -999 denotes an unidentified party.
  • THIRD_PARTY_NAME — display name of the party, or the AX lookup meaning for unidentified parties.
  • THIRD_PARTY_NUMBER — the supplier or customer number, or the lookup meaning where a real number is unavailable.
  • SUB_ID — the subsidiary identifier (VENDOR_SITE_ID, SITE_USE_ID, or -999 for unidentified sites).
  • SUB_NAME — the subsidiary name; for suppliers this is VENDOR_SITE_CODE, for customers a concatenated address string.

Common Use Cases and Queries

The view is typically queried to resolve party names and numbers during AX diagnostics, or to locate transactions assigned to the unidentified placeholder. A representative query:

SELECT application_id, third_party_id, third_party_name,
       third_party_number, sub_id, sub_name
FROM   ax_third_parties_subs_v
WHERE  third_party_id = -999;

Other uses include joining to AX subledger lines to enrich reporting, validating that every party is known, and auditing the AX_3RD_PARTY_UNIDENTIFIED lookup configuration across Payables, Receivables, and inventory. Because the view spans multiple schemas, appropriate AP, AR, and AX read privileges are required in both 12.1.1 and 12.2.2.