Search Results gl_tax_codes_v




Overview
Explore in AI Chat

Overview

GL_TAX_CODES_V is a General Ledger (GL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It presents a unified listing of tax codes available for use in subledger and General Ledger transactions, exposing both the technical identifiers and the translated, user-facing descriptions associated with each tax rate and tax regime configuration. The view is part of the E-Business Tax (ZX) reporting surface exposed through the GL product, and it is frequently referenced by Oracle Forms, concurrent programs, and custom reports that require a flat, query-friendly representation of tax codes without navigating the underlying normalized E-Business Tax tables.

Users searching for the column tax_type_code typically encounter this view because it is one of the few objects that derives a single-character classification of a tax rate as Input, Output, or a generic Tax type. This makes GL_TAX_CODES_V particularly useful for reconciliation, tax reporting, and integration extracts where a compact type indicator is needed.

Underlying Base Objects

The view is defined over four documented base objects:

Additional inline constraints restrict results to percentage-type rates (RATE_TYPE_CODE = 'PERCENTAGE'), exclude the STD_AR_INPUT tax status when a tax class exists, and require TAX_JURISDICTION_CODE IS NULL.

Key Columns

Common Use Cases and Queries

Typical uses include populating tax code lists of values, extracting input and output tax configurations for reporting, and joining tax codes to GL or AP/AR transaction data. A representative query filtering on the derived tax type is:

  • SELECT TAX_TYPE_CODE, TAX_TYPE, TAX_CODE, TAX_RATE, TAX_REGIME_CODE, TAX FROM GL_TAX_CODES_V WHERE TAX_TYPE_CODE = 'I' AND VALID_FLAG = 'Y';
  • SELECT TAX_CODE, DESCRIPTION, TAX_RATE, START_DATE, END_DATE FROM GL_TAX_CODES_V WHERE LEDGER_ID = :p_ledger_id ORDER BY TAX_CODE;
  • SELECT TAX_TYPE_CODE, COUNT(*) FROM GL_TAX_CODES_V GROUP BY TAX_TYPE_CODE;

Because the view is read-only and aggregates several E-Business Tax entities, it should be used for query and reporting rather than for DML.