Results for “task_attribute_list_name”

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

Overview

CUG_TSK_TYP_ATTR_MAPS_VL is a multilingual (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CUG – Citizen Interaction Center product family. Its purpose is to expose the configuration data that drives the Task Type Attribute capture form, which governs how attributes are presented and captured when agents create or update tasks against a given task type. Because the underlying configuration is stored in a translated (_TL) table, the view applies a language filter so that each runtime session sees only the rows matching its active language, retrieved via USERENV('LANG').

From a reporting and integration standpoint, the view presents a single denormalized row per task type attribute mapping, combining the language-independent base record with its translated default value. The view is marked VALID in ETRM for both 12.1.1 and 12.2.2. For users searching the term task_attr_default_value, this object is the authoritative source: the column TASK_ATTR_DEFAULT_VALUE is exposed only through this view and is not part of the base (_B) table.

Underlying Base Objects

The view is defined over two synonyms that resolve to the following tables:

• CUG_TSK_TYP_ATTR_MAPS_B — the base, language-independent table holding the mapping identity, task type reference, attribute code, mandatory/displayed flags, list of values name, WHO columns, and the 15 descriptive ATTRIBUTE columns plus ATTRIBUTE_CATEGORY.
• CUG_TSK_TYP_ATTR_MAPS_TL — the translation table holding TASK_ATTR_DEFAULT_VALUE per language.

The join is an equijoin on TSK_TYP_ATTR_MAP_ID between B and T, with the additional predicate T.LANGUAGE = USERENV('LANG'). A ROWID from the base table is surfaced as ROW_ID. The view text in ETRM lists only the two CUG tables, so no additional objects contribute to the result set. Note that the description metadata refers to joining the _B table twice; this is a documentation typo — the actual view text joins _TL to _B.

Key Columns

• TSK_TYP_ATTR_MAP_ID — primary identifier of the attribute mapping; the join key between the two tables.
• TASK_TYPE_ID — the task type to which the attribute mapping belongs.
• TASK_TYPE_ATTRIBUTE_CODE — code identifying the attribute being configured for capture.
• TASK_ATTR_DEFAULT_VALUE — the translated default value applied to the attribute; sourced from the _TL table and the column most relevant to searches on task_attr_default_value.
• TASK_ATTR_MANDATORY_FLAG — indicates whether the attribute must be captured.
• TASK_ATTR_DISPLAYED_FLAG — indicates whether the attribute is shown on the capture form.
• TASK_ATTRIBUTE_LIST_NAME — the list of values (LOV) associated with the attribute, if any.
• START_DATE_ACTIVE / END_DATE_ACTIVE — date-range effective dating for the mapping.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield storage columns.
• ROW_ID, OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard concurrency and audit columns.

Common Use Cases and Queries

Typical scenarios include auditing default values across task types, reproducing the capture-form layout during debugging, and integrating task attribute defaults into downstream reporting. The following query lists configured default values and flags for a task type:

• SELECT task_type_id, task_type_attribute_code, task_attr_default_value, task_attr_mandatory_flag, task_attr_displayed_flag FROM cug_tsk_typ_attr_maps_vl WHERE task_type_id = :p_task_type_id;
• SELECT tsk_typ_attr_map_id, task_type_attribute_code FROM cug_tsk_typ_attr_maps_vl WHERE task_attrr_default_value = :p_value;
• SELECT m.task_type_attribute_code, m.task_attr_default_value FROM cug_tsk_typ_attr_maps_vl m WHERE SYSDATE BETWEEN NVL(m.start_date_active, SYSDATE) AND NVL(m.end_date_active, SYSDATE + 1);

Because the view filters on USERENV('LANG'), results depend on the session language; integrations expecting a specific locale should set the language context explicitly or query the _TL table directly.