Results for “jl_zz_ar_tx_groups_v”

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

Overview

The JL_ZZ_AR_TX_GROUPS_V view, owned by the APPS schema, is a reporting and integration object within the JL – Latin America Localizations product family of Oracle E-Business Suite (12.1.1 and 12.2.2). It exposes the tax group configuration used by Latin American tax engines, consolidating tax category definitions, applicable tax rates, threshold rules, and contributor attributes into a single denormalized result set. The view supplies descriptive meaning for coded lookup values through calls to JL_ZZ_AR_TX_LIB_PKG.GET_LOOKUP_MEANING, so consumers receive readable labels rather than raw attribute codes. Because Latin American localizations rely heavily on category-driven tax determination, this view is the principal interface through which tax group records are surfaced for validation, reconciliation, and downstream reporting. It is registered with status VALID and functions as a read-only projection over the underlying transactional and setup tables.

Underlying Base Objects

The view is defined over the following documented base objects: JL_ZZ_AR_TX_GROUPS (aliased TGR), the primary source of tax group rows; JL_ZZ_AR_TX_CATEG_ALL (aliased CAT and CAT_REDUCE), which provides the tax category definition, organization, contributor, and transaction attributes and is joined twice — once for the group's own category and once for the category referenced in the reduction relationship; AR_VAT_TAX_ALL_B (aliased ART), which supplies the tax code description and tax rate; and AR_SYSTEM_PARAMETERS_ALL (aliased SYS), used to constrain the tax rule set to the global attribute. Supporting synonyms include AR_VAT_TAX and JL_ZZ_AR_TX_CATEG. The package JL_ZZ_AR_TX_LIB_PKG is invoked inline to translate stored lookup codes into display meanings. The joins anchor the group to its tax category, the category to the active rule set defined in system parameters, and the group to the associated tax code and rate, yielding the fully resolved tax group configuration.

Key Columns

• GROUP_TAX_ID, TAX_GROUP_RECORD_ID, TAX_CATEGORY_ID — primary identifiers linking the group, its record, and its category.
• TAX_CATEGORY — the category name for the group, and, via CAT_REDUCE, the category applied when a reduction occurs.
• ESTABLISHMENT_TYPE, CONTRIBUTOR_TYPE, TRANSACTION_NATURE — lookup codes with accompanying decoded meanings that classify the tax scenario.
• ORG_TAX_ATTRIBUTE, CUS_TAX_ATTRIBUTE, TXN_TAX_ATTRIBUTE — organization, contributor, and transaction attributes with decoded meanings.
• TAX_CATEGORY_TO_REDUCE_ID — the specific column underlying the user's search; it identifies the tax category to which a reduction applies, resolving through CAT_REDUCE to a category name.
• USED_TO_REDUCE — flag indicating whether the group participates in a reduction relationship.
• MIN_AMOUNT, MIN_TAXABLE_BASIS, MIN_PERCENTAGE, USE_TX_CATEG_THRESHOLDS — threshold controls governing when the tax applies.
• TAX_RATE, BASE_RATE, TAX_CODE, DESCRIPTION — rate and tax code details drawn from the VAT tax table.
• TAX_INCLUSIVE, TRIBUTARY_SUBSTITUTION, COMPOUND_PRECEDENCE, CALCULATE_IN_OE — calculation behavior flags.
• START_DATE_ACTIVE, END_DATE_ACTIVE, ORG_ID — effective dating and organizational context.

Common Use Cases and Queries

Typical uses include auditing tax reduction relationships, verifying effective-dated tax group configurations, and extracting tax rate and threshold data for reconciliation reports or external tax filings.

To inspect reduction relationships using the searched column:

• SELECT group_tax_id, tax_category, tax_category_to_reduce_id, used_to_reduce FROM jl_zz_ar_tx_groups_v WHERE used_to_reduce = 'Y';

To list active groups with rates for an organization:

• SELECT tax_category, tax_code, tax_rate, base_rate, start_date_active, end_date_active FROM jl_zz_ar_tx_groups_v WHERE org_id = :p_org_id AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);

To review contributor and transaction classifications with decoded meanings:

• SELECT contributor_type, transaction_nature, org_tax_attribute FROM jl_zz_ar_tx_groups_v WHERE tax_category = :p_category;

Because the view performs lookup decoding and multi-table joins, queries should be constrained by ORG_ID, TAX_CATEGORY, or date ranges to limit result sets on high-volume implementations.