Results for “jtf_task_temp_groups_vl”

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

Overview

The CSD_SC_TASK_TEMP_GROUP_V view is a reporting and integration object owned by the APPS schema within the Oracle E-Business Suite. It belongs to the CSD product family, which covers Depot Repair, and is documented as VALID in the ETRM reference for releases 12.1.1 and 12.2.2. Its stated purpose is to display the mapping between Service Codes and Task Template Groups.

In the Depot Repair data model, a Service Code identifies a type of repair work, while a Task Template Group bundles the individual task templates that must be applied when that service is performed. The view flattens this association into a single queryable row set, allowing report authors, concurrent programs, and external integrations to resolve which task template group supports a given service code without navigating the underlying relationship table directly. It is a read-only view and exposes no DML of its own; any maintenance of the Service Code to Task Template Group relationship must be performed against the base entities.

Underlying Base Objects

The view is defined over two documented objects:

• CSD_SC_WORK_ENTITIES (registered as a SYNONYM in APPS) — the driving table, aliased CSCWE. It stores the work entity records that link a service code to a specific work entity, in this case a task template group. The view is restricted to rows where WORK_ENTITY_TYPE_CODE = 'TASK'.
• JTF_TASK_TEMP_GROUPS_VL (a VIEW) — aliased JTT, the Task Template Groups base (VL) view in the JTF (Task Manager) module. It supplies the translatable name and description attributes for each template group.

The join is an inner join on CSCWE.WORK_ENTITY_ID1 = JTT.TASK_TEMPLATE_GROUP_ID, so only work entity rows that resolve to an existing task template group are returned. Because JTF_TASK_TEMP_GROUPS_VL is itself a view, the effective query path reaches the task template group base tables through that layer.

Key Columns

• ROW_ID — the ROWID of the underlying CSD_SC_WORK_ENTITIES row; useful for pinpointing the source record.
• SC_WORK_ENTITY_ID — primary identifier of the service code to work entity association.
• OBJECT_VERSION_NUMBER — optimistic locking version for the source row.
• SERVICE_CODE_ID — foreign key to the service code being mapped.
• TASK_TEMP_GROUP_ID — the task template group identifier resolved through the join; documented in the column list as TASK_TEMP_GROUP_ID.
• TASK_TEMP_GROUP_NAME — the translatable template group name sourced from JTF_TASK_TEMP_GROUPS_VL (aliased from TEMPLATE_GROUP_NAME).
• TASK_TEMP_GROUP_DESC — the template group description, sourced from the DESCRIPTION column of the VL view.
• Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include validating that every active service code has an associated task template group, populating repair order setup, and driving tasks automatically at repair creation. A representative query lists the mapping for a specific service code:

SELECT service_code_id,
       task_temp_group_id,
       task_temp_group_name
FROM   apps.csd_sc_task_temp_group_v
WHERE  service_code_id = :p_service_code_id;

To detect service codes missing a mapping, an outer join back to the service code source is required. To audit template group usage, aggregate on TASK_TEMP_GROUP_NAME:

SELECT task_temp_group_name, COUNT(*) mappings
FROM   apps.csd_sc_task_temp_group_v
GROUP  BY task_temp_group_name;

Because the view performs an inner join and a type filter, records present in CSD_SC_WORK_ENTITIES with other work entity types, or whose template group is absent from JTF_TASK_TEMP_GROUPS_VL, do not appear. Reports requiring those rows should query the base objects directly.