Results for “cug_sr_task_attr_vals_vl”

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

Overview

CUG_SR_TASK_ATTR_VALS_VL is a multi-lingual (VL) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the CUG – Citizen Interaction Center product family. The view exposes the configuration data that drives the Service Request Type – Task Type attribute capture form, which governs how attribute values are presented toward citizens and agents during task handling. Because it is a VL view, it presents language-dependent descriptive content alongside language-independent base columns, resolving the appropriate translation row according to the current session language. In reporting and integration terms, this view is the standard, supported access path for querying task-type attribute values, since it abstracts the underlying base/translation table pair into a single flattened result set and shields consumers from having to join the two tables or resolve LANGUAGE manually.

Underlying Base Objects

The view is defined over two documented base objects, resolved through synonyms in the APPS schema:

• CUG_SR_TASK_ATTR_VALS_B — the base (language-independent) table holding the primary keys, foreign keys, and standard WHO/audit columns.
• CUG_SR_TASK_ATTR_VALS_TL — the translation table holding the language-specific descriptive attribute value.

The join is performed on SR_TASK_ATTR_VAL_ID, with the translation side filtered by T.LANGUAGE = USERENV('LANG'). This means the view returns exactly one row per attribute value for the language of the current session, falling back to the base row only if a matching translation exists. The view text aliases the base table as B and the translation table as T, exposing B.ROWID as ROW_ID and the base audit and identifier columns alongside T.TASK_TYPE_ATTR_VALUE from the translation table.

Key Columns

• ROW_ID — the ROWID of the base table row, retained for EBS framework operations such as updatable-view handling.
• SR_TASK_ATTR_VAL_ID — primary key of the task-type attribute value record; the join key between base and translation tables.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the EBS framework to detect concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE — standard WHO audit columns carried over from the base table.
• TSK_TYP_ATTR_DEPEND_ID — the identifier referenced by the search term. It links the attribute value to its dependency definition, expressing conditional relationships between task-type attributes.
• TASK_TYPE_ATTR_MAP_ID — foreign key to the task-type attribute mapping, tying the value to a specific task type attribute.
• TASK_TYPE_ATTR_VALUE — the translated, language-specific value displayed in the attribute capture form.

Common Use Cases and Queries

Typical usage includes reporting on configured attribute values for service request types, validating dependency configuration, and extracting attribute values for integrations that populate or interpret the capture form. A common query locates values tied to a particular dependency identifier:

• SELECT SR_TASK_ATTR_VAL_ID, TSK_TYP_ATTR_DEPEND_ID, TASK_TYPE_ATTR_MAP_ID, TASK_TYPE_ATTR_VALUE FROM CUG_SR_TASK_ATTR_VALS_VL WHERE TSK_TYP_ATTR_DEPEND_ID = :dependency_id;
• Joining to the mapping and task-type tables to trace which attribute values belong to a given task type.
• Auditing recently changed configuration using LAST_UPDATE_DATE and LAST_UPDATED_BY.

Because the LANGUAGE filter is applied internally, queries executed in a session running in a given language return the corresponding translation without further coding, making the view suitable for both concurrent-program extracts and ad hoc reporting.