Results for “tax_authority_code”

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

Overview

The APPS.JL_ZZ_AR_TX_CATEGRY view is a reporting and validation construct within the Oracle E-Business Suite Latin America Localizations (JL) product family. It surfaces tax category definitions used by the ETRM (E-Business Tax and Latin American tax reporting) engine for Receivables transactions. The view joins the transactional tax category table to FND_LOOKUPS to resolve a translated description and to AR_SYSTEM_PARAMETERS_ALL to enforce the active tax rule set for the operating unit. It therefore presents only tax categories that are both enabled in the lookup layer and aligned with the rule set configured for the current organization. Because the view is defined with a SYSDATE-based date range predicate on the lookup's active dates, it exposes the currently effective set of tax categories rather than a full historical record.

Underlying Base Objects

The view is defined in the APPS schema and is documented as referencing four base objects: AR_SYSTEM_PARAMETERS_ALL (synonym), FND_GLOBAL (package), FND_LOOKUPS (view), and JL_ZZ_AR_TX_CATEG (synonym). Its primary driving table is JL_ZZ_AR_TX_CATEG, aliased TXC, which stores the tax category definitions. FND_LOOKUPS, aliased FND_CAT_DESC, is joined on LOOKUP_TYPE = 'JLZZ_AR_TX_CATEGRY' and LOOKUP_CODE = TAX_CATEGORY, with ENABLED_FLAG = 'Y', to supply the descriptive meaning. AR_SYSTEM_PARAMETERS_ALL, aliased SYS, is joined on GLOBAL_ATTRIBUTE13 = TAX_RULE_SET and on organization, with NVL(ORG_ID,-99) matching between the two objects. FND_GLOBAL typically supplies the runtime ORG_ID context for multi-org security. The view text additionally constrains the lookup start and end dates against SYSDATE, so categories with expired or not-yet-active lookup rows are excluded.

Key Columns

The view exposes the full column set of the underlying tax category definition alongside the resolved lookup meaning. The primary identifier is TAX_CATEGORY_ID, with TAX_CATEGORY as the code and DESCRIPTION (the lookup MEANING) as the user-facing text. Tax computation attributes include THRESHOLD_CHECK_LEVEL, THRESHOLD_CHECK_GRP_BY, MIN_AMOUNT, MIN_TAXABLE_BASIS, MIN_PERCENTAGE, and TAX_INCLUSIVE. Behavior flags include ORG_TAX_ATTRIBUTE, CUS_TAX_ATTRIBUTE, TXN_TAX_ATTRIBUTE, TRIBUTARY_SUBSTITUTION, and PRINT_FLAG. The reduction-related columns USED_TO_REDUCE and TAX_CATEG_TO_REDUCE_ID identify whether the category is used to reduce another category and, if so, which category it reduces — this is the column pair most directly relevant to the reported search term. Additional governance columns include TAX_CODE, MANDATORY_IN_CLASS, TAX_AUTHORITY_CODE, TAX_RULE_SET, TAX_REGIME, ORG_ID, START_DATE_ACTIVE, END_DATE_ACTIVE, and standard WHO audit and descriptive flexfield columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, ATTRIBUTE_CATEGORY, ATTRIBUTE1–15).

Common Use Cases and Queries

Typical uses include validating which tax categories are active for an operating unit, confirming rule set alignment, and tracing reduction relationships between categories. A basic query listing active categories is:

• SELECT tax_category_id, tax_category, description, tax_rule_set, org_id FROM apps.jl_zz_ar_tx_categry WHERE org_id = :p_org_id;
• SELECT tax_category, tax_categ_to_reduce_id, used_to_reduce FROM apps.jl_zz_ar_tx_categry WHERE used_to_reduce = 'Y';
• SELECT c.tax_category, c.tax_categ_to_reduce_id, r.tax_category reduced_to FROM apps.jl_zz_ar_tx_categry c, apps.jl_zz_ar_tx_categry r WHERE c.tax_categ_to_reduce_id = r.tax_category_id;

For diagnostic purposes, querying the view with no ORG_ID predicate returns rows across organizations, which is useful when investigating configuration drift between operating units. Because the view filters on SYSDATE and lookup enablement, rows present in the base table JL_ZZ_AR_TX_CATEG may be absent here; when a category is unexpectedly missing from reports driven by this view, the underlying lookup definition (lookup type JLZZ_AR_TX_CATEGRY) and its date ranges should be checked, along with the GLOBAL_ATTRIBUTE13 rule set value on AR_SYSTEM_PARAMETERS_ALL.