Search Results cug_sr_type_attr_maps_vl




Overview
Explore in AI Chat

Overview

APPS.CUG_SR_TYPE_ATTR_MAPS_VL is a multi-lingual (ML) view owned by the APPS schema and delivered as part of the CUG - Citizen Interaction Center product within Oracle E-Business Suite 12.1.1 and 12.2.2. Its role is to expose the configuration metadata that governs the Service Request Attribute capture form, specifically the mapping of Service Request attributes to a given Service Request (incident) type. The view supplies the translated, language-specific default value for each mapped attribute alongside the installation-independent setup data held in the base table.

Because it is a "_VL" view—Oracle's standard naming convention for a view that joins a "_B" base table with its "_TL" translation table—it returns exactly the set of rows whose translation matches the session language, determined through USERENV('LANG'). This makes it the appropriate object for reporting, form LOVs, and integration queries that must render attribute labels and default values in the runtime user's language without duplicating language-filtering logic in every consumer. The view status is documented as VALID in the ETRM for both releases.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through synonyms from APPS: CUG_SR_TYPE_ATTR_MAPS_B (the base table holding language-independent attribute mapping definitions) and CUG_SR_TYPE_ATTR_MAPS_TL (the translation table holding the language-specific text, including the attribute default value). The two are joined on SR_TYPE_ATTR_MAP_ID, and the translation side is further constrained by T.LANGUAGE = USERENV('LANG').

All non-translated columns are projected from the B table alias; only SR_ATTR_DEFAULT_VALUE is taken from the TL table alias (T). In addition, the view exposes B.ROWID as ROW_ID, which permits downstream tooling to identify the underlying base-table row. Because the join is an inner join between B and TL, a mapping record will not appear in this view unless a translation row exists for the current session language.

Key Columns

Common Use Cases and Queries

The view is typically used to render or audit the attribute capture configuration for a given Service Request type, to verify mandatory and displayed attributes, and to resolve language-specific default values in custom reports or integrations.

Listing the active attribute configuration for a specific incident type:

  • SELECT sr_attribute_code, sr_type_attr_seq_num, sr_attr_mandatory_flag, sr_attr_displayed_flag, sr_attr_default_value
  • FROM apps.cug_sr_type_attr_maps_vl
  • WHERE incident_type_id = :p_incident_type_id
  • AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE))
  • AND NVL(end_date_active, TRUNC(SYSDATE))
  • ORDER BY sr_type_attr_seq_num;

Identifying mandatory attributes required for close with their value lists:

  • SELECT sr_attribute_code, sr_attribute_list_name, reqd_for_close_flag, update_allowed_flag
  • FROM apps.cug_sr_type_attr_maps_vl
  • WHERE incident_type_id = :p_incident_type_id
  • AND sr_attr_mandatory_flag = 'Y'
  • AND reqd_for_close_flag = 'Y';

Because SR_ATTR_DEFAULT_VALUE is drawn from the translation table, any query filtering or grouping on default values is implicitly language-scoped to the session's USERENV('LANG') setting; consumers requiring a specific language must initialize the session language accordingly before querying the view.