Results for “transaction_attribute”

46 results




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

Overview

The view APPS.JL_ZZ_AR_TX_CATEGRY_V is a localized (JL/ZZ prefix) reporting and integration view within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It presents tax category configuration data used by the Latin American (specifically Argentina-focused) tax solution built on the Oracle EBS Receivables and ETRM frameworks. The view consolidates tax category definitions, threshold-check rules, tax attributes, rates, and authority information into a single queryable structure, and it decodes internal lookup codes into human-readable meanings by calling JL_ZZ_AR_TX_LIB_PKG.get_lookup_meaning. Because the search term transaction_attribute appears among the columns exposed here, this view is frequently targeted when users need to inspect which transaction-level attribute drives a given tax category's threshold grouping or taxation logic.

Underlying Base Objects

The view is defined over the following documented base objects, all exposed as APPS synonyms:

  • JL_ZZ_AR_TX_CATEG and JL_ZZ_AR_TX_CATEG_ALL — the core tax category definition tables supplying tax_category_id, tax_category, thresholds, attributes, and dates.
  • AR_VAT_TAX and AR_VAT_TAX_ALL_B — the VAT/tax rate and regime tables supplying description, tax rate, and regime linkage.
  • AR_SYSTEM_PARAMETERS_ALL — organization and system parameter context, contributing org_id filtering.
  • JL_ZZ_AR_TX_LIB_PKG — a PL/SQL package whose get_lookup_meaning function is invoked repeatedly in the SELECT list to translate coded values into descriptive text.

The view performs a self-join on the tax category table alias cat to resolve tax_categ_to_reduce_desc, and joins the tax attribute/rate tables alias art for description and rate values.

Key Columns

The view exposes a broad set of configuration attributes. Noteworthy columns include:

  • tax_category_id, tax_category — identifier and code for the tax category.
  • threshold_check_level, threshold_check_grp_by — the threshold evaluation level and its grouping basis, with decoded meanings for LINE, DOCUMENT, or TRANSACTION.
  • txn_tax_attribute — the transaction tax attribute, decoded using the TRANSACTION_ATTRIBUTE lookup type; this is the field most relevant to the transaction_attribute search.
  • org_tax_attribute (ORGANIZATION_ATTRIBUTE) and cus_tax_attribute (CONTRIBUTOR_ATTRIBUTE) — parallel attribute dimensions.
  • min_amount, min_taxable_basis, min_percentage, tax_inclusive — threshold and calculation parameters.
  • tax_authority_code, tax_regime, tax_code, tax_rule_set — tax authority and regime configuration.
  • tax_rate, description — sourced from the VAT tax table.
  • Descriptive attribute1 through attribute6 and DFF context column attribute_category.
  • Standard Who columns: creation_date, created_by, last_update_date, last_updated_by, last_update_login, plus rowid.

Common Use Cases and Queries

Typical scenarios include auditing tax category setup, validating threshold-check behavior, and extracting decoded attribute meanings for integration or reporting layers.

Locate categories driven by a specific transaction attribute:

  • SELECT tax_category, txn_tax_attribute, tax_rate FROM jl_zz_ar_tx_categry_v WHERE UPPER(txn_tax_attribute) LIKE '%TRANSACTION%';

Review threshold configuration with decoded meanings:

  • SELECT tax_category, threshold_check_level, threshold_check_grp_by FROM jl_zz_ar_tx_categry_v WHERE org_id = :p_org_id;

Audit active categories and their authority/regime mapping by joining on tax_category_id and filtering on end_date_active IS NULL. Because the view encapsulates lookup decoding through JL_ZZ_AR_TX_LIB_PKG, it is preferred over querying the underlying JL_ZZ_AR_TX_CATEG table directly when human-readable output is required.