Results for “task_template_group_id”

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

Overview

The view JTF_TASK_TEMP_GROUPS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema within the JTF – CRM Foundation product. Its purpose is to present task template group data in the language of the current session by joining the base (language-independent) table with its translation table. In Oracle EBS 12.1.1 and 12.2.2, this view serves as the primary read interface for forms, reports, concurrent programs, and integration components that need to display or reference task template groups with translated names and descriptions. Because it exposes the translated TEMPLATE_GROUP_NAME and DESCRIPTION alongside the operational columns of the base table, it abstracts the two-table MLS implementation away from consuming code, allowing queries to remain language-agnostic while respecting the user's session language.

Underlying Base Objects

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

• JTF_TASK_TEMP_GROUPS_B — the base table holding language-independent data, including the primary key TASK_TEMPLATE_GROUP_ID, who-columns, descriptive flexfield attributes, effective dating, and the object version number.
• JTF_TASK_TEMP_GROUPS_TL — the translation table holding TEMPLATE_GROUP_NAME and DESCRIPTION for each supported language.

The join is performed on TASK_TEMPLATE_GROUP_ID with the translation row restricted by T.LANGUAGE = USERENV('LANG'). This predicate is what establishes the view as an MLS view: it returns exactly the translation matching the language of the current database session, which in EBS is derived from the user's runtime language setting. The view is documented as VALID in ETRM, confirming it is compiled and usable in the supported release.

Key Columns

The view projects columns from both base objects:

• ROW_ID — the ROWID of the base table row, commonly used by Oracle Forms for row identification and locking.
• TASK_TEMPLATE_GROUP_ID — the primary key and join key between the base and translation tables.
• TEMPLATE_GROUP_NAME, DESCRIPTION — translated attributes from the TL table, displayed according to the session language.
• SOURCE_OBJECT_TYPE_CODE — indicates the source object type associated with the template group.
• START_DATE_ACTIVE, END_DATE_ACTIVE — effective dating that controls when the group is active.
• OBJECT_VERSION_NUMBER — used for optimistic locking and change detection in the business layer.
• APPLICATION_ID — the owning application of the row.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield segments.

Common Use Cases and Queries

Typical uses include populating list of values (LOVs) for task template groups, driving CRM task creation logic, and reporting on template group configuration. A standard query retrieves active groups for the session language:

• SELECT task_template_group_id, template_group_name, description FROM jtf_task_temp_groups_vl WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);
• Join to related task template and template group member tables on TASK_TEMPLATE_GROUP_ID to build template hierarchies.
• Filter by SOURCE_OBJECT_TYPE_CODE or by flexfield attributes for application-specific lookups.

When retrieving attributes not exposed by the view, developers should join back to JTF_TASK_TEMP_GROUPS_B rather than querying the TL table directly, since the view already resolves the correct language row.