Search Results temp_section

Overview

HZ_TRANS_ATTRIBUTES_VL is a translatable (VL) view owned by the APPS schema in Oracle E-Business Suite Receivables (AR). It exposes the metadata that describes the extensible attributes available for TCA (Trading Community Architecture) party entities — the configuration rows that tell the application which descriptive attributes exist for a given entity, what they are called in the logged-in language, and how their values are sourced or derived. Rather than storing actual transaction attribute data, this view functions as a definition catalog: it is the runtime registry consulted by forms, APIs, and concurrent programs that render or validate attribute-driven fields on customer, contact, and related party records.

Because the view carries the _VL suffix, it joins a base table and a translation table and filters on USERENV('LANG'), returning each attribute definition only once, in the language of the current session. This makes it suitable for both multilingual reporting and integration logic that must present user-facing attribute labels consistently regardless of the underlying base language.

Underlying Base Objects

The view is defined over two documented TCA base objects, exposed to APPS through synonyms:

• HZ_TRANS_ATTRIBUTES_B — the base table holding language-independent attribute definitions, including the internal attribute name, owning entity, custom attribute procedure, and source table.
• HZ_TRANS_ATTRIBUTES_TL — the translation table supplying the user-facing USER_DEFINED_ATTRIBUTE_NAME per language.

The two are joined on ATTRIBUTE_ID, with the translation side additionally constrained by T.LANGUAGE = USERENV('LANG'). The view also exposes B.ROWID as ROW_ID, enabling row-identified access from forms and supporting update-through-view behavior where the B-table columns are concerned.

Key Columns

• ROW_ID / ATTRIBUTE_ID — row identifier and the primary surrogate key for the attribute definition.
• ENTITY_NAME — the TCA entity (for example, HZ_PARTIES or HZ_LOCATIONS) to which the attribute belongs.
• ATTRIBUTE_NAME — the internal, language-independent column name of the attribute (the DFF/CAF segment name).
• USER_DEFINED_ATTRIBUTE_NAME — the translated, user-facing label shown to end users in the session language.
• CUSTOM_ATTRIBUTE_PROCEDURE — the PL/SQL procedure or hook used to derive or validate the attribute value.
• SOURCE_TABLE — the table from which the attribute value is sourced when the definition is denormalized.
• DENORM_FLAG — indicates whether the attribute is denormalized into the source table for performance.
• TEMP_SECTION — the UI/detail section grouping used to organize attributes on the form.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE, LAST_UPDATED_BY, and OBJECT_VERSION_NUMBER for auditing and optimistic locking.

Common Use Cases and Queries

Typical scenarios include listing all configured descriptive attributes for a given entity, joining the catalog to attribute value tables, and building multilingual reports of attribute labels. A representative query returns the attribute catalog for a specific entity:

• SELECT attribute_id, entity_name, attribute_name, user_defined_attribute_name, source_table, denorm_flag FROM hz_trans_attributes_vl WHERE entity_name = 'HZ_PARTIES' ORDER BY attribute_name;
• SELECT attribute_name, user_defined_attribute_name FROM hz_trans_attributes_vl WHERE attribute_id = :p_attribute_id;
• SELECT entity_name, COUNT(*) FROM hz_trans_attributes_vl GROUP BY entity_name;

Because the view filters on the session language, integrations running under a different NLS_LANG return labels in that language, so queries should not be used to reconcile base-language values. Consumers requiring every translation should read HZ_TRANS_ATTRIBUTES_TL directly.