Search Results printed_tax_name




Overview
Explore in AI Chat

Overview

The AR_AP_TAX_CODES_V view in the APPS schema provides a unified, cross-product listing of tax codes originating from both Oracle Receivables and Oracle Payables. In Oracle EBS 12.1.1 and 12.2.2, tax code definitions are maintained in separate product-specific stores — receivables tax codes in AR_VAT_TAX_ALL_VL and payables tax codes in AP_TAX_CODES_ALL — each keyed by a distinct primary identifier. This view reconciles those structures into a single shape by aliasing both VAT.VAT_TAX_ID and TC.TAX_ID to the common column name TAX_CODE_ID, allowing callers to retrieve a TAX_CODE_ID value regardless of the originating product. The view therefore acts as a lightweight integration and reporting surface, joining the tax configuration of the two sub-ledgers into one result set. It is exposed as a VALID object owned by APPS and is typically used by concurrent programs, reports, and custom extensions that must present or resolve tax codes without hard-coding product-specific table and column names.

Underlying Base Objects

Per the documented ETRM 12.2.2 metadata, the view is defined over two referenced base objects: AP_TAX_CODES_ALL (a SYNONYM) and AR_VAT_TAX_ALL_VL (a VIEW). The two branches are combined with UNION ALL. The Receivables branch selects from AR_VAT_TAX_ALL_VL where TAX_ACCOUNT_ID IS NOT NULL, and the Payables branch selects from AP_TAX_CODES_ALL where TAX_TYPE is not 'OFFSET' or 'AWT' and TAX_CODE_COMBINATION_ID IS NOT NULL. Because AP_TAX_CODES_ALL is referenced through a synonym, the underlying base table is resolved in the AP schema at runtime. The UNION ALL preserves rows from both sources without duplicate elimination beyond the DISTINCT keyword applied to each branch, and the PRODUCT column ('AR' or 'AP') identifies the origin of each row.

Key Columns

  • ORG_ID — Organization identifier, defaulted to -1 through NVL where the source row carries no organization.
  • SET_OF_BOOKS_ID — Ledger/set of books context for the tax code.
  • TAX_CODE_ID — The unified identifier; maps to VAT.VAT_TAX_ID for AR rows and TC.TAX_ID for AP rows. This is the column users search on when locating tax codes across products.
  • TAX_TYPE — Classification of the tax code from the source product.
  • VAT_TRANSACTION_TYPE — Transaction type associated with the tax code.
  • TAX_CLASS — Tax class; the AP branch hard-codes the value 'I'.
  • TAX_CODE — The user-facing tax code name (VAT.TAX_CODE or TC.NAME).
  • TAX_RATE — Applicable tax rate.
  • DESCRIPTION — Descriptive text for the tax code.
  • PRODUCT — Literal 'AR' or 'AP' indicating the originating sub-ledger.
  • START_DATE / END_DATE — Effective date range; the AP branch supplies NULL for START_DATE and TC.INACTIVE_DATE for END_DATE.
  • PRINTED_TAX_NAME — Display name printed on documents (VAT.PRINTED_TAX_NAME or TC.NAME).

Common Use Cases and Queries

Typical scenarios include LOV/reference lookups that must surface tax codes from both Receivables and Payables, reconciliation reporting between AR and AP tax configurations, and integration extracts that require a normalized TAX_CODE_ID. A representative query filtering by product and tax code is:

  • SELECT TAX_CODE_ID, TAX_CODE, TAX_RATE, PRODUCT FROM APPS.AR_AP_TAX_CODES_V WHERE PRODUCT = 'AR' AND SET_OF_BOOKS_ID = :p_sob;
  • SELECT TAX_CODE_ID, TAX_CODE, TAX_CLASS FROM APPS.AR_AP_TAX_CODES_V WHERE TAX_CODE_ID = :p_tax_code_id;
  • SELECT PRODUCT, COUNT(*) FROM APPS.AR_AP_TAX_CODES_V GROUP BY PRODUCT ORDER BY PRODUCT;

Because the view unions distinct product branches, queries should qualify by PRODUCT or SET_OF_BOOKS_ID where ambiguity is possible, and callers relying on TAX_CODE_ID must be aware that identifier values are only unique within their originating product.