Search Results ax_subs_v

Overview

AX_SUBS_V is a reporting view delivered within the Oracle E-Business Suite Global Accounting Engine (AX) module. Its documented purpose is to expose the ID and Name of third-party subidentifiers — the lowest level of the accounting distribution hierarchy used by the Global Accounting Engine. In the AX data model, balances and transactions are typically decomposed into a third party (a vendor, customer, or inventory organization) and a subidentifier beneath that third party (a vendor site, a bill-to customer site, a secondary inventory, a cost group, or an unspecified placeholder). AX_SUBS_V provides a single, union-based lookup that resolves those subidentifier IDs into human-readable names, making it suitable for ad-hoc reporting, reconciliation queries, and integration extracts that must translate numeric SUB_ID values into descriptive text.

The view is documented in ETRM 12.2.2 with no owner recorded and no referenced base objects formally specified, although the view text itself identifies the underlying tables. It is noted as "Not implemented in this database," indicating it is a seeded definition that may not exist in every environment. The view is not a stored table; it is a query-time construct and therefore carries no storage or indexing of its own.

Underlying Base Objects

AX_SUBS_V is defined as a series of UNION operations over the following documented base objects:

• PO_VENDOR_SITES_ALL — supplier sites, queried for the Purchasing application context (APPLICATION_ID 200), keyed on VENDOR_ID and VENDOR_SITE_ID.
• RA_ADDRESSES_ALL and RA_SITE_USES_ALL — Receivables customer addresses and site uses, restricted to SITE_USE_CODE = 'BILL_TO', providing the name for Receivables (APPLICATION_ID 222) subidentifiers.
• RA_CUSTOMERS — customer records, joined to AX_LOOKUPS to supply the "unidentified customer site" placeholder row.
• AX_SECONDARY_INVENTORY and MTL_PARAMETERS — Inventory secondary inventories, filtered where PRIMARY_COST_METHOD <> 2, for the Inventory application context (APPLICATION_ID 401).
• CST_COST_GROUPS and MTL_PARAMETERS — cost groups, used where PRIMARY_COST_METHOD = 2, since standard-cost organizations identify subidentifiers by cost group rather than secondary inventory.
• ORG_ORGANIZATION_DEFINITIONS — organization definitions, used to supply the inventory site placeholder row.
• AX_LOOKUPS — the AX lookup table, joined on LOOKUP_TYPE = 'AX_3RD_PARTY_UNIDENTIFIED' to provide meaning text for placeholder subidentifiers such as CUSTOMER_SITE and INVENTORY_SITE.

The UNION ALL semantics of the definition mean that each application context contributes its own set of rows, with the APPLICATION_ID column acting as the discriminator between contexts 200 (Purchasing), 222 (Receivables), and 401 (Inventory).

Key Columns

• APPLICATION_ID — Identifies the source application context: 200 for supplier sites, 222 for customer sites and related placeholders, 401 for inventory subidentifiers.
• THIRD_PARTY_ID — The ID of the parent third party (vendor ID, customer ID, or inventory organization ID).
• SUB_ID — The subidentifier ID, which is the column most commonly referenced when users search on "sub_id". This corresponds to vendor site ID, site use ID, secondary inventory ID, or cost group ID depending on context.
• SUB_NAME — The descriptive name of the subidentifier, derived from vendor site code, concatenated customer address components, secondary inventory name, cost group name, or lookup meaning.

Common Use Cases and Queries

The principal use case is resolving a stored SUB_ID into its descriptive name when producing AX balance or subledger reports. A typical query restricting to a single third party is:

• SELECT application_id, third_party_id, sub_id, sub_name FROM ax_subs_v WHERE sub_id = :sub_id; — direct lookup by the searched identifier.
• SELECT s.sub_id, s.sub_name FROM ax_subs_v s WHERE s.third_party_id = :vendor_id AND s.application_id = 200; — enumerating valid subidentifiers for a supplier.
• SELECT application_id, COUNT(*) FROM ax_subs_v GROUP BY application_id; — validating the population of subidentifiers by context.

Common pitfalls include reliance on UNION ALL producing duplicate-looking rows across contexts, and the appearance of -999 placeholder subidentifiers for unidentified customer sites. Reports should therefore filter on application_id and, where necessary, exclude sub_id = -999 unless placeholder handling is intended.