Results for “jlzz_ar_tx_attr_value”

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

Overview

JL_ZZ_AR_TX_GROUPS_V is an APPS-owned database view within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 globalization (ETRM / Latin American localizations) schema. It exposes the configured tax groups used by the JL_ZZ_AR_TX tax determination engine for Receivables and Order Management transactions, joining each group record to its owning tax category, to an optional "category to reduce," and to the associated tax rate and description. Because the underlying table JL_ZZ_AR_TX_GROUPS stores group rows keyed to a tax category, tax code, and a set of establishment, contributor, and transaction attributes, this view presents that configuration together with the denormalized lookup meanings that would otherwise require decoding via JL_ZZ_AR_TX_LIB_PKG.

Its role is primarily diagnostic and reporting-oriented: it allows localization administrators, tax analysts, and support engineers to inspect how tax groups are defined and to verify the "used to reduce" and "category to reduce" configuration that drives reduced-rate and exemption processing in Latin American tax regimes.

Underlying Base Objects

The view is defined over the documented base objects and synonyms AR_SYSTEM_PARAMETERS_ALL, AR_VAT_TAX, AR_VAT_TAX_ALL_B, JL_ZZ_AR_TX_CATEG, JL_ZZ_AR_TX_CATEG_ALL, JL_ZZ_AR_TX_GROUPS, and the package JL_ZZ_AR_TX_LIB_PKG. In practice the principal driving table is JL_ZZ_AR_TX_GROUPS (aliased tgr). It is joined on tax_category_id to JL_ZZ_AR_TX_CATEG_ALL (aliased cat), which supplies the tax category and its organization, contributor, and transaction attribute codes. A second, self-join of JL_ZZ_AR_TX_CATEG_ALL (aliased cat_reduce) supplies the category to be reduced. AR_VAT_TAX_ALL_B (aliased art) provides the tax rate and description for the tax code, and AR_SYSTEM_PARAMETERS_ALL (aliased sys) restricts both category joins to the active tax rule set via global_attribute13. The scalar sub-programs JL_ZZ_AR_TX_LIB_PKG.get_lookup_meaning decode the establishment type, contributor type, transaction nature, and the attribute columns to their displayable meanings.

Key Columns

• group_tax_id / tax_group_record_id / tax_category_id — identifiers of the group row, its record, and the owning tax category.
• tax_category / cat_reduce.tax_category — the category name and the reduced category name; the latter supports reduced-tax logic.
• used_to_reduce / tax_category_to_reduce_id — flags and links that indicate the group reduces another category.
• tax_code / tax_rate / base_rate — the tax code applied by the group and its rate values.
• establishment_type, contributor_type, transaction_nature — attribute conditions (with decoded meanings) qualifying the group.
• org_tax_attribute, cus_tax_attribute, txn_tax_attribute — category-level attribute codes with their meanings.
• min_amount, min_taxable_basis, min_percentage, tax_inclusive, tributary_substitution, compound_precedence — calculation controls.
• start_date_active / end_date_active — effective dating for the group.
• org_id, calculate_in_oe, attribute_category, attribute1–attribute15 — operating unit, Order Entry flag, and descriptive flexfield context.

Common Use Cases and Queries

Typical usage includes auditing tax group configuration for a given category, identifying groups that reduce a tax category, and reconciling configured rates against expected values. A representative query for reduced-category groups is:

• SELECT tax_code, tax_category, cat_reduce.tax_category reduced_category, tax_rate, used_to_reduce FROM apps.jl_zz_ar_tx_groups_v WHERE used_to_reduce = 'Y' ORDER BY tax_category;
• SELECT tax_code, tax_rate, start_date_active, end_date_active FROM apps.jl_zz_ar_tx_groups_v WHERE tax_category = :category AND org_id = :org_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Because all rows are constrained to the active tax rule set and to non-null tax codes, the view returns only currently applicable group definitions, making it suitable for ad hoc support queries and configuration comparisons across 12.1.1 and 12.2.2 environments. Note that its decoded columns are computed through package calls, so performance is best when filtered by tax_category, tax_code, or org_id.