Results for “az_api_pref_src_attributes_vl”

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

Overview

The view AZ_API_PREF_SRC_ATTRIBUTES_VL is an Oracle Application Object Library (FND) dictionary object owned by the APPS schema. It belongs to the ETRM (Enterprise Tax and Rules Management) family of application objects, where the AZ_ prefix denotes views and tables that support the configuration of rules, preferences, and source attributes. This particular view presents the translated, user-facing definition of preference source attributes that may be associated with an API preference definition.

Functionally, the view is a "_VL" (View Label) construct, a standard Oracle EBS pattern that joins a base (untranslated) table to its translation table and filters the translation rows to the session language. It therefore exposes exactly one row per logical record for the currently connected language. The view is read-only from the perspective of application code and is intended for reporting, LOV (List of Values) population, validation, and integration queries rather than for direct DML.

Underlying Base Objects

The view is defined over two documented base objects, both accessed through APPS synonyms:

• AZ_API_PREF_SRC_ATTRIBUTES_B — the base (language-independent) table holding the preference code, data source, attribute code, key flag, enable-report flag, five generic parameter columns, and the standard WHO audit columns.
• AZ_API_PREF_SRC_ATTRIBUTES_TL — the translation table that supplies the DISPLAY_NAME for each attribute in the installed languages.

The join condition links the two tables on the composite key PREFERENCE_CODE, DATA_SOURCE, and ATTRIBUTE_CODE, and then restricts the translation side with T.LANGUAGE = USERENV('LANG'). This guarantees that the display name returned matches the language of the current user session, while the remaining attribute metadata is drawn from the base table.

Key Columns

• PREFERENCE_CODE — identifies the parent preference definition to which the source attribute belongs.
• DATA_SOURCE — the source from which the attribute value is drawn; together with the preference code it scopes the attribute.
• ATTRIBUTE_CODE — the internal code of the attribute; the three preceding columns form the unique logical key.
• DISPLAY_NAME — the translated, user-visible label for the attribute, taken from the TL table for the session language.
• KEY_FLAG — indicates whether the attribute participates as a key attribute in the preference/source definition.
• ENABLE_REPORT_FLAG — controls whether the attribute is available for reporting purposes.
• PARAM1 through PARAM5 — five generic parameter columns used to store implementation-specific values associated with the attribute.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard Oracle WHO audit columns inherited from the base table.

Common Use Cases and Queries

Because the view resolves the language-sensitive display name automatically, it is the preferred object for any inquiry that must present attribute labels to an end user. Typical uses include populating LOVs on preference or rule configuration forms, generating reports that list the attributes available for a given data source, and validating configuration data during integrations.

Example: listing all source attributes for a specific preference and data source.

SELECT preference_code,
       data_source,
       attribute_code,
       display_name,
       key_flag,
       enable_report_flag
FROM   apps.az_api_pref_src_attributes_vl
WHERE  preference_code = :p_preference_code
AND    data_source = :p_data_source
ORDER  BY display_name;

Example: identifying key attributes only.

SELECT attribute_code, display_name
FROM   apps.az_api_pref_src_attributes_vl
WHERE  key_flag = 'Y';

Example: joining the view to a preference source definition to produce a fully labelled configuration report.

SELECT v.preference_code,
       v.display_name,
       v.param1,
       v.param2
FROM   apps.az_api_pref_src_attributes_vl v
WHERE  v.enable_report_flag = 'Y';

Queries should always reference the APPS synonyms rather than the underlying tables directly, so that language resolution and any future view changes are honoured consistently. As with all _VL views, no DML should be attempted against it.