Results for “geography_id”

12 results




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

Overview

ZX_RULES_VL is an APPS-owned, VALID database view in Oracle E-Business Suite 12.1.1 and 12.2.2, catalogued under the FND - Application Object Library product grouping. It presents tax rule definitions maintained by the E-Business Tax (ETRM) module in a language-translated, business-facing form. The suffix "VL" denotes a "view with translation" that joins the transactional base table to its translation table and restricts the translation rows to the session language via USERENV('LANG'), so consumers see the tax rule name and description in the active language without writing their own language join.

Functionally the view exposes the tax rules stored in ZX_RULES_B, joined to the translated names and descriptions in ZX_RULES_TL. Tax rules drive how E-Business Tax determines the tax, tax regime, tax rate, recovery type, and applicability of a transaction based on determining factors. Because the view is owned by APPS and the referenced objects are exposed to the runtime environment as synonyms, ZX_RULES_VL is a natural reporting and integration surface for tax configuration data.

Underlying Base Objects

The view is defined as a join between two objects:

  • ZX_RULES_B (synonym) — the base table holding language-independent tax rule attributes.
  • ZX_RULES_TL (synonym) — the translation table holding TAX_RULE_NAME and TAX_RULE_DESC per language.

The join predicate is B.TAX_RULE_ID = T.TAX_RULE_ID, with the translation table filtered by T.LANGUAGE = USERENV('LANG'). The view selects T.ROWID as ROW_ID but otherwise projects the base table's ROWID-derived column and columns from both tables. This structure is characteristic of Oracle's standard _TL translation pattern: one row per tax rule, resolved into a single language for the querying session.

Key Columns

The view projects a broad set of tax rule attributes:

Common Use Cases and Queries

Typical uses include tax configuration reporting, impact analysis before changing regime or geography assignments, integration extracts for downstream tax engines, and reconciliation of translation coverage. A standard query is:

  • SELECT tax_rule_id, tax_rule_code, tax_rule_name, tax_regime_code, tax, priority, enabled_flag, effective_from, effective_to FROM zx_rules_vl WHERE enabled_flag = 'Y' AND SYSDATE BETWEEN effective_from AND NVL(effective_to, SYSDATE) ORDER BY tax_regime_code, priority;
  • SELECT tax_regime_code, COUNT(*) FROM zx_rules_vl WHERE enabled_flag = 'Y' GROUP BY tax_regime_code;
  • SELECT r.tax_rule_code, r.tax_rule_name FROM zx_rules_vl r WHERE r.geography_type IS NOT NULL;

Earlier correspondences located through the term "zx_rules_b" reflect the base table underlying the view; queries against ZX_RULES_B alone return codes and IDs without translated names, whereas ZX_RULES_VL supplies the language-resolved name and description required for user-facing reporting.