Results for “fnd_cat_desc”

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 integration object within the Oracle E-Business Suite tax configuration layer. It presents translated tax category definitions by joining the underlying tax category table (JL_ZZ_AR_TX_CATEG) to the Oracle Application Object Library lookup infrastructure (FND_LOOKUPS). The view's central purpose is to expose the human-readable description associated with each tax category code — the column aliased here as MEANING, sourced from FND_CAT_DESC.MEANING, which is the same element users encounter when searching for the term fnd_cat_desc. By resolving the internal lookup code (TAX_CATEGORY) against the JLZZ_AR_TX_CATEGRY lookup type, the view removes the need for report authors and integrators to reconstruct this join manually. It also enforces contextual validity: only lookups flagged as enabled are returned, and date-effectiveness on the lookup record must encompass the current system date, ensuring that obsolete or future-dated descriptions are excluded from results.

Underlying Base Objects

The view is defined over three documented base objects. JL_ZZ_AR_TX_CATEG (exposed via a synonym) is the primary transaction source supplying tax category identifiers and all configuration attributes. FND_LOOKUPS (a view over the lookup tables) supplies the descriptive MEANING for each category code and carries the ENABLED_FLAG and date-range predicates that govern visibility. AR_SYSTEM_PARAMETERS_ALL (synonym) participates solely through its GLOBAL_ATTRIBUTE13 column, which is equated to TXC.TAX_RULE_SET. This join constrains the output to the tax rule set configured for the operating unit in AR_SYSTEM_PARAMETERS_ALL. Multi-organization security is applied by matching TXC.ORG_ID to SYS.ORG_ID using NVL(...,-99) on both sides, so that records with null organization identifiers are also aligned. The FND_GLOBAL package is documented as a referenced object, consistent with the view's reliance on the session's organization context during execution.

Key Columns

The view exposes the full tax category attribute set plus the resolved description. Principal columns include:

• TAX_CATEGORY_ID and TAX_CATEGORY — the surrogate key and the lookup code identifying the category.
• MEANING — the descriptive text obtained from FND_LOOKUPS, the column most relevant to the fnd_cat_desc lookup.
• TAX_REGIME, TAX_CODE, TAX_RULE_SET, and TAX_AUTHORITY_CODE — regime and rule-set context defining where the category applies.
• TAX_INCLUSIVE, USED_TO_REDUCE, TAX_CATEG_TO_REDUCE_ID, TRIBUTARY_SUBSTITUTION — taxation behavior flags.
• MIN_AMOUNT, MIN_TAXABLE_BASIS, MIN_PERCENTAGE, THRESHOLD_CHECK_LEVEL, THRESHOLD_CHECK_GRP_BY — threshold configuration.
• ORG_TAX_ATTRIBUTE, CUS_TAX_ATTRIBUTE, TXN_TAX_ATTRIBUTE, MANDATORY_IN_CLASS — applicability controls.
• START_DATE_ACTIVE, END_DATE_ACTIVE, CREATION_DATE, LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — audit and effective-dating columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard extensibility flexfield columns.
• ORG_ID — the operating unit identifier used for multi-org filtering.

Common Use Cases and Queries

Typical uses include tax configuration reports, validation extracts for integrations, and diagnostic queries that explain why a tax category behaves in a particular way. A straightforward listing that pairs each category with its user-facing description can be written as:

SELECT tax_category, meaning, tax_regime, tax_code,
       tax_inclusive, start_date_active, end_date_active
FROM   apps.jl_zz_ar_tx_categry
WHERE  tax_regime = :p_regime
ORDER  BY tax_category;

Because the view already resolves FND_LOOKUPS by lookup type and enabled flag, consumers searching on fnd_cat_desc obtain the description without an additional join. Analysts may filter on USED_TO_REDUCE = 'Y' to isolate categories participating in tax reduction logic, or examine threshold columns to verify minimum-amount enforcement. For multi-organization deployments, results are automatically restricted by the ORG_ID predicate, so the query reflects the operating unit associated with the current session. When building custom reports, it is preferable to query this view rather than reimplement its join logic, since the view consistently applies the enabled-flag, date-effectiveness, rule-set, and organization predicates that determine which tax categories are currently valid.