Results for “attr_desc”

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

Overview

The view JL_ZZ_AR_TX_CAT_ATT_TN_V is an Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the JL – Latin America Localizations product family. It is a reporting and integration view over the Latin America tax category attribute configuration used by Receivables (AR). Its primary purpose is to expose transaction-level tax category attributes in a denormalized, human-readable form, resolving internal lookup codes into descriptive meanings so that downstream reports, extracts, and interfaces do not need to call lookup APIs directly.

The view is classified with a status of VALID and is documented in ETRM for both Release 12.1.1 and 12.2.2. Because it is a view rather than a table, it holds no data of its own; it derives every row at runtime from the underlying tax configuration tables and the Latin America localization library package. This makes it a convenient abstraction layer for parties needing transactional tax attribute metadata without joining multiple base objects manually.

Underlying Base Objects

The view is defined over four referenced objects documented in the ETRM metadata:

• JL_ZZ_AR_TX_CAT_ATT (synonym) — the primary source of tax category attribute rows, aliased as ATT in the view text.
• JL_ZZ_AR_TX_CATEG (synonym) — supplies the tax category header, aliased as CAT, and provides the TAX_CATEGORY name and the tax rule set link.
• AR_SYSTEM_PARAMETERS (synonym) — aliased as SYS and used to constrain the tax rule set to the currently configured global attribute value.
• JL_ZZ_AR_TX_LIB_PKG (package) — the localization library package that provides the GET_LOOKUP_MEANING function used to translate lookup codes into descriptive text.

The join logic links attributes to their category through ATT.TAX_CATEGORY_ID = CAT.TAX_CATEGORY_ID, and restricts the result set to the tax rule set currently active per AR_SYSTEM_PARAMETERS.GLOBAL_ATTRIBUTE13. A further filter limits rows to TAX_ATTRIBUTE_TYPE = 'TRANSACTION_ATTRIBUTE', so the view reflects only transaction-level configuration.

Key Columns

The view exposes the full set of attribute configuration columns plus several derived description columns. Notable columns include:

• ROW_ID — the underlying ATT.ROWID, useful for identifying source rows.
• TAX_CATEG_ATTR_ID and TAX_CATEGORY_ID — primary keys for the attribute and its parent category.
• TAX_CATEGORY — the category name from JL_ZZ_AR_TX_CATEG.
• TAX_ATTRIBUTE_TYPE and ATTR_TYPE_DESC — the attribute type code and its resolved lookup meaning, translated via GET_LOOKUP_MEANING against the JLZZ_AR_TX_CATEG_ATTR_TYPE lookup, truncated to 80 characters.
• TAX_ATTRIBUTE_NAME and ATTR_DESC — the internal attribute name and its translated description, the latter being the column most directly associated with the attr_desc search term.
• GROUPING_ATTRIBUTE, MANDATORY_IN_CLASS, DETERMINING_FACTOR, and PRIORITY_NUMBER — control flags governing grouping, mandatory entry, determining behavior, and precedence.
• Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN, LAST_UPDATED_BY) and the generic ATTRIBUTE_CATEGORY along with ATTRIBUTE1 through ATTRIBUTE15 for descriptive flexfield values.

Common Use Cases and Queries

Typical uses include reporting on tax category attribute definitions, validating configuration prior to transaction processing, and feeding downstream tax determination extracts. A representative query retrieving attributes with their descriptions for a given category follows:

• SELECT tax_category, tax_attribute_name, attr_desc, attr_type_desc, mandatory_in_class FROM jl_zz_ar_tx_cat_att_tn_v WHERE tax_category = :category_name;
• SELECT tax_category, priority_number, determining_factor FROM jl_zz_ar_tx_cat_att_tn_v ORDER BY tax_category, priority_number;
• SELECT attr_desc FROM jl_zz_ar_tx_cat_att_tn_v WHERE tax_attribute_name = :attribute_name;

Because descriptions are resolved through JL_ZZ_AR_TX_LIB_PKG, the returned text reflects the current lookup configuration, which supports audit and reconciliation activities in the Latin America localization.