Results for “tax_calculation_plsql_block”

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

Overview

AR_VAT_TAX_ALL_VL is a multilingual (ML) validation view owned by the APPS schema in Oracle E-Business Suite Receivables. It presents VAT and tax code configuration for the Oracle Receivables module, joining together the base and translation tables that store tax setup information. The view exposes tax codes, tax rates, tax types, accounting flexfield references, and descriptive attributes for each tax record defined at the operating unit level. In Oracle EBS 12.1.1 and 12.2.2 the view carries a VALID status and remains a documented object within the E-Business Tax and Receivables reporting surface.

The "_VL" suffix denotes a "view with translation" that surfaces the translated (language-specific) description columns alongside the base transactional columns, resolving the current user's language through USERENV('LANG'). This makes the view suitable for forms, concurrent programs, and integration queries that must display tax code names and printed tax names in the session language. Because it aggregates setup rather than transaction-level data, AR_VAT_TAX_ALL_VL is most commonly used for configuration reporting, tax validation, and reference lookups rather than for direct transactional posting.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over two referenced base objects:

• AR_VAT_TAX_ALL_B (SYNONYM) — the base table holding language-independent tax definition data such as tax rate, tax type, accounting CCIDs, and flags.
• AR_VAT_TAX_ALL_TL (SYNONYM) — the translation table holding language-dependent text such as the printed tax name and description.

The join condition is B.VAT_TAX_ID = T.VAT_TAX_ID AND NVL(B.ORG_ID, -99) = NVL(T.ORG_ID, -99) AND T.LANGUAGE = USERENV('LANG'). This correlates base and translation rows on the tax identifier and organization, and filters translations to the current session language. The NVL(...) pattern ensures records with a null ORG_ID are matched consistently, since not all tax records are organization-specific.

Key Columns

• VAT_TAX_ID — primary identifier of the tax record; the join key between base and translation tables.
• ORG_ID — operating unit identifier; the view is multiorg-aware, with null values permitted.
• SET_OF_BOOKS_ID — the ledger (set of books) under which the tax code is defined.
• TAX_CODE — the user-visible tax code used on transactions.
• TAX_RATE / TAX_TYPE — the percentage or amount used in tax calculation and the classification (for example, VAT, exempt, or sales tax).
• PRINTED_TAX_NAME — the translated, printable tax name sourced from AR_VAT_TAX_ALL_TL.
• TAX_ACCOUNT_ID, ADJ_CCID, EDISC_CCID, UNEDISC_CCID, FINCHRG_CCID — accounting flexfield account combinations for tax, adjustments, earned/unearned discounts, and finance charges.
• START_DATE / END_DATE, ENABLED_FLAG, DISPLAYED_FLAG — effective dating and usability flags controlling whether the tax code is active and selectable.
• ATTRIBUTE1–15 and GLOBAL_ATTRIBUTE_CATEGORY / GLOBAL_ATTRIBUTE1–20 — descriptive flexfield and global descriptive flexfield columns for extensibility.

Common Use Cases and Queries

Typical uses include enumerating active tax codes for a ledger, validating tax setup during implementation, and joining tax codes to invoice lines. Sample query to list enabled tax codes with their translated names:

• SELECT vat_tax_id, org_id, tax_code, printed_tax_name, tax_rate, tax_type, enabled_flag FROM ar_vat_tax_all_vl WHERE enabled_flag = 'Y' AND set_of_books_id = :ledger_id ORDER BY tax_code;
• SELECT tax_code, printed_tax_name, start_date, end_date FROM ar_vat_tax_all_vl WHERE org_id = :org_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
• SELECT tax_code, tax_account_id, adj_ccid, edisc_ccid FROM ar_vat_tax_all_vl WHERE tax_type = 'VAT';

Because the view resolves the session language, it is preferred over querying the base tables directly whenever a translated tax name must be shown. Reports and integrations should always filter on ENABLED_FLAG and effective dates to avoid returning obsolete tax definitions.