Search Results tax_full_name




Overview
Explore in AI Chat

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

Overview

ZX_TAXES_TL is the multilingual support (MLS) table for the E-Business Tax (ZX) module in Oracle EBS 12.1.1 and 12.2.2. It stores translated and language-specific descriptive attributes for each tax configuration record defined in the E-Business Tax repository. Rather than duplicating the full tax definition per language, Oracle EBS separates the language-neutral tax record into ZX_TAXES_B and the translatable text into ZX_TAXES_TL, linked by the TAX_ID surrogate key. This follows the standard Oracle Applications MLS pattern, in which a base (_B) table holds language-independent columns and a translation (_TL) table holds language-dependent columns keyed by both TAX_ID and LANGUAGE.

From a heuristic Data Vault modeling perspective, ZX_TAXES_TL is classified as satellite-leaning. It functions as a descriptive satellite attached to the ZX_TAXES_B hub: its primary key (TAX_ID, LANGUAGE) identifies the hub reference plus the language discriminator, and the table carries the descriptive, non-key attributes (such as TAX_FULL_NAME) that belong to that combination. It does not act as a hub in its own right because TAX_ID is a foreign key to ZX_TAXES_B.

Key Information Stored

The table contains nine documented columns. The most significant are:

  • TAX_ID — The surrogate identifier of the parent tax configuration record in ZX_TAXES_B; part of the composite primary key.
  • LANGUAGE — The language code for the translated row; the second component of the composite primary key and the MLS discriminator.
  • SOURCE_LANG — Indicates the source language of the translation, supporting Oracle's MLS translation-tracking convention.
  • TAX_FULL_NAME — The language-specific full descriptive name of the tax; the principal business-visible attribute held in this table.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle Applications WHO-column audit attributes recording row creation and modification metadata.

The surrogate primary key is ZX_TAXES_TL_PK, composed of (TAX_ID, LANGUAGE). A unique index, ZX_TAXES_TL_U1, is documented on the same (TAX_ID, LANGUAGE) pair, serving as the business-key candidate that enforces one translation row per tax per language.

Common Use Cases and Queries

Typical usage centers on displaying and reporting tax names in the user's session language, and on validating that translations exist for all required languages.

  • Retrieving the tax name in the current language: 
    SELECT t.tax_id, t.tax_full_name
FROM   zx_taxes_tl t
WHERE  t.tax_id = :tax_id
AND    t.language = USERENV('LANG');
  • Joining translated names to the base tax record: 
    SELECT b.tax_id, tl.tax_full_name
FROM   zx_taxes_b b, zx_taxes_tl tl
WHERE  b.tax_id = tl.tax_id
AND    tl.language = USERENV('LANG');
  • Identifying taxes missing a translation for a target language, to support localization or data-quality audits.
  • Feeding multilingual tax-name columns into tax reporting extracts and reconciliation reports where tax identifiers must be presented in the reporting language.

Related Objects

The following objects are most significant in relation to ZX_TAXES_TL:

  • ZX_TAXES_B — The base (language-neutral) tax definition table; joined via ZX_TAXES_TL.TAX_ID → ZX_TAXES_B.TAX_ID, and the parent referenced by the foreign key documented in this table's metadata.
  • ZX_TAXES_VL — The MLS view that presents ZX_TAXES_B and ZX_TAXES_TL together using the session language, typically the preferred access path for reporting.
  • ZX_TAX_REGIMES and regime-to-tax association objects — reference taxes defined by TAX_ID for hierarchical tax configuration.
  • ZX_RATES_B / ZX_RATES_TL — Tax rates associated with a tax, whose multilingual names follow the same MLS pattern keyed by TAX_ID.
  • ZX_TAX_STATUS / ZX_TAX_JURISDICTIONS — Configuration objects that reference the tax by TAX_ID and therefore depend on the base and translated tax records.

Because E-Business Tax UI pages and tax determination logic resolve tax names through the MLS view, dependents of ZX_TAXES_TL generally query the _VL view rather than the _TL table directly, except in translation maintenance and data-quality checking scenarios.