Results for “contributor_attribute”

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

Overview

APPS.JL_ZZ_AR_TX_ATT_VAL_V is a reporting and integration view in the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 releases that exposes tax attribute values configured against Receivables tax categories. It is part of the JL_ZZ localization framework used for Latin American tax processing (for example, Argentina, Brazil, and Colombia) and is a primary access point for developers and analysts who need to resolve tax attributes to their descriptive lookup meanings. Because the view joins the attribute value table to AR_SYSTEM_PARAMETERS_ALL and resolves coded values through the JL_ZZ_AR_TX_LIB_PKG package, it presents tax attribute data in a decoded, business-friendly form rather than as raw identifiers. Users frequently encounter it when investigating the "transaction_attribute" lookup, which is one of the TAX_ATTRIBUTE_TYPE values the view distinguishes.

Underlying Base Objects

The view is defined over the following documented base objects:

• JL_ZZ_AR_TX_ATT_VAL_ALL — the transactional table that stores tax category attribute values. Aliased as VAL, it supplies nearly every column in the view.
• AR_SYSTEM_PARAMETERS_ALL — joined to VAL so that rows are restricted to the operating unit context, using NVL(VAL.org_id, -99) = NVL(SYS.org_id, -99). This makes the view operating-unit aware while tolerating null org_id rows.
• JL_ZZ_AR_TX_LIB_PKG — a package whose GET_LOOKUP_MEANING function is invoked inline to translate the stored value code and attribute value code into their lookup meanings.

Key Columns

• ROW_ID — the ROWID of the underlying attribute value row, useful for direct updates or diagnostics.
• TAX_CATEGORY_ID / TAX_CATEG_ATTR_VAL_ID — identifiers linking the attribute to its tax category and attribute value record.
• TAX_ATTRIBUTE_TYPE — classifies the attribute; values include TRANSACTION_ATTRIBUTE, CONTRIBUTOR_ATTRIBUTE, and TAX_AUTHORITY_CATEGORY.
• TAX_ATTRIBUTE_NAME / TAX_ATTRIBUTE_VALUE — the attribute name and its stored value, the latter decoded via the JLZZ_AR_TX_ATTR_VALUE lookup into ATTR_VAL_DESC.
• TAX_ATTR_VALUE_CODE — the coded value, decoded into TAX_ATTR_VALUE_MEANING using a lookup that varies by attribute type (for example, JLAR_TAX_AUTHORITY_CATEGORY for TRANSACTION_ATTRIBUTE).
• DEFAULT_TO_CLASS, ORG_ID, and the flexible ATTRIBUTE_CATEGORY / ATTRIBUTE1–15 and audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, and related fields).

Common Use Cases and Queries

A typical query retrieves the decoded transaction attributes for a tax category within the current operating unit:

• Validate configuration: SELECT tax_attribute_name, tax_attribute_value, attr_val_desc FROM jl_zz_ar_tx_att_val_v WHERE tax_category_id = :id; — confirms which attributes and values are set up.
• Resolve meanings: filter on tax_attribute_type = 'TRANSACTION_ATTRIBUTE' to isolate transaction_attribute rows and inspect TAX_ATTR_VALUE_MEANING.
• Operating-unit reporting: the AR_SYSTEM_PARAMETERS_ALL join constrains results to the session's org context, so the view can be queried directly in concurrent programs and BI Publisher data templates.