Search Results tax_line

Overview

ZX_JRNL_LINE_DESC_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite. It belongs to the ETRM (E-Business Tax) product family and is catalogued under the FND – Application Object Library module in the ETRM documentation repository. The view provides a human-readable, translated description of individual tax lines by resolving the surrogate identifiers held on ZX_LINES into their corresponding multilingual display names drawn from the ZX_*_TL translation tables.

In EBS 12.1.1 and 12.2.2 the view is registered with a status of VALID. Its principal role is to support diagnostics, reporting, and integration scenarios in which a tax line must be presented with its regime, tax, status, and rate names rather than internal numeric IDs. Because ZX_LINES itself carries only foreign keys (TAX_REGIME_ID, TAX_ID, TAX_STATUS_ID, TAX_RATE_ID), any consumer requiring descriptive tax context must join across four translation tables; this view encapsulates those joins so that reporting tools, custom concurrent programs, and SOA integrations can query a single object. Notably, the view is the resolution point for the object frequently searched by implementers as zx_status_tl, which appears within its FROM clause as STATUS_TL.

Underlying Base Objects

The documented base objects referenced by the view are ZX_LINES, ZX_RATES_TL, ZX_REGIMES_TL, ZX_STATUS_TL, and ZX_TAXES_TL, each exposed in the APPS schema as a synonym. The join topology is a star pattern centred on ZX_LINES (aliased TAX_LINE): each of the four translation tables is joined on its primary key column to the corresponding foreign key on the tax line.

• TAX_LINE.TAX_RATE_ID = RATES_TL.TAX_RATE_ID
• TAX_LINE.TAX_ID = TAXES_TL.TAX_ID
• TAX_LINE.TAX_STATUS_ID = STATUS_TL.TAX_STATUS_ID
• TAX_LINE.TAX_REGIME_ID = REGIMES_TL.TAX_REGIME_ID

Critically, the view does not simply join names to keys; it enforces language consistency by requiring that REGIMES_TL.LANGUAGE equals the LANGUAGE column of TAXES_TL, STATUS_TL, and RATES_TL. This constraint guarantees that all four descriptive attributes are returned in one and the same language, preventing mixed-language output. The view text does not filter on a literal language value, so callers must supply a language predicate themselves when a specific locale is required.

Key Columns

• TAX_LINE_ID – Surrogate identifier of the tax line from ZX_LINES; the primary correlation key to the underlying transaction line.
• TAX_REGIME_NAME – Translated regime name from ZX_REGIMES_TL, identifying the tax regime applicable to the line.
• TAX_FULL_NAME – Fully qualified tax name from ZX_TAXES_TL, describing the tax that was calculated.
• TAX_STATUS_NAME – Translated status name from ZX_STATUS_TL, indicating the tax status (for example, taxable, exempt, or zero-rated) applied to the line.
• TAX_RATE_NAME – Translated rate name from ZX_RATES_TL, identifying the rate assigned to the line.
• TAX_JURISDICTION_CODE – Jurisdiction code carried directly from ZX_LINES, useful for grouping and regulatory reporting.
• LANGUAGE – The language code shared by all four translation tables; used to constrain output to a single locale.

Common Use Cases and Queries

Typical usages include tax audit extracts, reconciliation reports that must display descriptive tax attributes alongside journal or transaction lines, and integration payloads where external systems cannot resolve EBS internal IDs. The following query restricts output to a single language and returns descriptive tax context for a given tax line:

• SELECT tax_line_id, tax_regime_name, tax_full_name, tax_status_name, tax_rate_name, tax_jurisdiction_code FROM zx_jrnl_line_desc_v WHERE language = 'US' AND tax_line_id = :p_tax_line_id;

For regime-level reporting, aggregate tax lines by regime and status:

• SELECT tax_regime_name, tax_status_name, COUNT(*) FROM zx_jrnl_line_desc_v WHERE language = USERENV('LANG') GROUP BY tax_regime_name, tax_status_name;

Because the view performs no filtering and joins four translation tables, queries against it should always include a LANGUAGE predicate to avoid four-way Cartesian expansion across languages. Users searching for zx_status_tl in this context will find that the table's data reaches reporting consumers exclusively through views such as ZX_JRNL_LINE_DESC_V, via the STATUS_TL alias and the TAX_STATUS_NAME column.