Results for “ax_tax_codes_v”

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

Overview

The view AX_TAX_CODES_V belongs to the Oracle E-Business Suite Global Accounting Engine (AX) product family. Its documented purpose is to present the subledger tax codes applicable to each application and set of books defined within the EBS instance. In practice, it consolidates tax code identifiers from the Payables and Receivables subledgers into a single, normalized structure keyed by application, ledger (set of books), and tax identifier.

Within Oracle EBS 12.1.1 and 12.2.2, the Global Accounting Engine serves as the accounting transformation and consolidation layer that feeds the AX schemas. The view is therefore relevant to reporting, reconciliation, and integration routines that must resolve a TAX_ID to its human-readable TAX_CODE while remaining aware of which subledger and ledger the tax code originates from. Because it is a read-only view rather than a table, it is not an object users maintain directly; it is populated at runtime by the union of the underlying subledger tax tables.

Underlying Base Objects

The documented view text defines AX_TAX_CODES_V explicitly as a two-branch UNION query:

• The first branch selects constant 200 as APPLICATION_ID together with SET_OF_BOOKS_ID, TAX_ID, and NAME TAX_CODE from AP_TAX_CODES_ALL.
• The second branch selects constant 222 as APPLICATION_ID together with SET_OF_BOOKS_ID, VAT_TAX_ID TAX_ID, and TAX_CODE from AR_VAT_TAX_ALL_B.

Application ID 200 corresponds to Oracle Payables and 222 corresponds to Oracle Receivables, which is consistent with the union of an AP source and an AR source. The ETRM metadata for 12.2.2 lists no separately documented referenced base objects and no owner, and it notes that the view is not implemented in the database documented. The view text itself remains the authoritative description of its lineage. In 12.2.2, where the concept of a set of books is represented by the ledger, the SET_OF_BOOKS_ID column continues to be exposed for backward compatibility with the 12.1.1 model.

Key Columns

• APPLICATION_ID — A constant discriminator identifying the originating subledger: 200 for Payables, 222 for Receivables. This column is essential for disambiguating rows from the two branches of the union.
• SET_OF_BOOKS_ID — The ledger (set of books) to which the tax code is associated. It scopes the tax code to a specific accounting entity, permitting the same tax code name to exist across different ledgers.
• TAX_ID — The numeric tax identifier. For Payables rows this is the AP tax identifier; for Receivables rows it is sourced from VAT_TAX_ID. This is the column most commonly used as a join key.
• TAX_CODE — The display name or code of the tax, taken from NAME in AP_TAX_CODES_ALL and from TAX_CODE in AR_VAT_TAX_ALL_B.

Common Use Cases and Queries

Because users searched for tax_id, the most frequent application of this view is resolving a numeric tax identifier to its tax code, or enumerating the tax codes available to a given ledger and subledger. A representative query filtering by tax identifier and showing the originating application is:

• SELECT application_id, set_of_books_id, tax_id, tax_code FROM ax_tax_codes_v WHERE tax_id = :p_tax_id;
• Enumerating all codes for one subledger: SELECT tax_code FROM ax_tax_codes_v WHERE application_id = 200 AND set_of_books_id = :p_sob;
• Correlating AP and AR usage of the same code across ledgers by grouping on tax_code and set_of_books_id.

The view is typically joined to subledger distribution or accounting lines on TAX_ID, restricted further by APPLICATION_ID to avoid cross-subledger ambiguity. When report output must reconcile to the AX schema, retain APPLICATION_ID and SET_OF_BOOKS_ID in the result set so that identically named tax codes from different subledgers are not collapsed.