Search Results function_call

Overview

AMV_D_ENT_ATTRIBUTES_VL is a translated (VL) view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the AMV (Marketing Encyclopedia System) product family and exposes entity attribute definitions in the language determined by the current session. The view joins a base table, which stores language-independent attribute metadata, to a translation table, which supplies the language-dependent descriptive text. This separation of base and translation data is the standard Oracle multi-language ("_B"/"_TL") pattern, and the "_VL" suffix indicates that the view returns a single row per attribute in the user's active language rather than one row per installed language.

In reporting and integration terms, the view provides a clean, denormalized source of entity attribute configuration without requiring the caller to resolve translation joins manually. It is the recommended read interface for concurrent programs, BI Publisher data models, and custom extensions that need attribute names and descriptions in the runtime language, since directly querying the two physical tables would expose all languages and require an explicit LANGUAGE predicate.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms in the APPS schema at the 12.2.2 level:

• AMV_D_ENT_ATTRIBUTES_B — the base (non-translated) table holding attribute identity, entity association, data type, validation, and status information.
• AMV_D_ENT_ATTRIBUTES_TL — the translation table holding ATTRIBUTE_NAME and DESCRIPTION per installed language.

The join is expressed as B.ATTRIBUTE_ID = T.ATTRIBUTE_ID combined with T.LANGUAGE = USERENV('LANG'). The USERENV('LANG') function returns the current session language code, so the view automatically filters the translation table to the caller's language. Because the query joins on the primary key of the base table and a single translation row, the view is effectively a key-preserved, row-per-attribute projection. All columns except the two translated columns originate from the base table B.

Key Columns

• ROW_ID / ROWID — the base table row identifier, exposed for reference; note the column appears as ROW_ID in the documented column list while the view text selects B.ROWID.
• ATTRIBUTE_ID — primary key of the attribute; the join key between base and translation records.
• ENTITY_ID — identifies the entity to which the attribute belongs, linking attribute definitions to their parent entity.
• DATA_TYPE — the data type expected for values supplied against the attribute.
• COLUMN_NAME — the underlying column name mapped by the attribute.
• VALIDATION_TYPE, RANGE_LOW_VALUE, RANGE_HIGH_VALUE, FUNCTION_CALL — describe how entered values are validated, including range limits and any function-based validation.
• STATUS — active/inactive state of the attribute definition.
• USAGE_INDICATOR — the attribute returned by the originating search; it carries the usage classification of the attribute and is a common filter predicate for callers that need to distinguish how an attribute is intended to be used.
• ATTRIBUTE_NAME, DESCRIPTION — translated, language-dependent text sourced from the _TL table.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

Typical usage includes listing attributes for a specific entity, filtering by usage or status, and driving dynamic attribute rendering in UI extensions. The view should be queried rather than the underlying tables whenever translated text is required.

Listing attributes for one entity:

• SELECT attribute_id, attribute_name, description, data_type, usage_indicator, status FROM apps.amv_d_ent_attributes_vl WHERE entity_id = :p_entity_id AND status = 'ACTIVE';

Isolating attributes by usage indicator:

• SELECT attribute_id, attribute_name, column_name, validation_type FROM apps.amv_d_ent_attributes_vl WHERE usage_indicator = :p_usage_indicator;

Inspection of validation configuration:

• SELECT attribute_id, attribute_name, validation_type, range_low_value, range_high_value, function_call FROM apps.amv_d_ent_attributes_vl ORDER BY attribute_name;

Because the view already applies USERENV('LANG'), callers cannot retrieve other languages from it; multilingual extracts must instead query AMV_D_ENT_ATTRIBUTES_TL directly with an explicit LANGUAGE predicate.