Results for “cs_sr_tsk_tmpl_gp_map”

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

Overview

CS_SR_TSK_TMPL_GP_MAP is a Service (CS) module table in Oracle E-Business Suite Releases 12.1.1 and 12.2.2 that stores the mapping between a task template group and the service request attributes that qualify it: request type (incident type), product (inventory item) and product category. The table effectively answers the question "which task template group should be applied when a service request of a given type, product and category is created?" and is therefore central to the automatic generation of task templates and their associated tasks on service requests.

The object is owned by the CS schema and is documented as VALID with sixteen columns. Its primary key is CS_SR_TSK_TMPL_GP_MAP_PK, defined on TASK_TEMPLATE_GROUP_MAP_ID, and a unique index CS_SR_TSK_TMPL_GP_MAP_U1 exists on the same column. Foreign keys reference CS_INCIDENT_TYPES_B (via INCIDENT_TYPE_ID), JTF_TASK_TEMP_GROUPS_B (via TASK_TEMPLATE_GROUP_ID) and FND_SECURITY_GROUPS (via SECURITY_GROUP_ID). A heuristic Data Vault classification of this table is satellite-leaning: it carries descriptive, context-dependent attributes that qualify a parent template-group entity rather than representing an independent business hub.

Key Information Stored

The most significant columns, drawn from the documented physical schema, are:

• TASK_TEMPLATE_GROUP_MAP_ID — surrogate primary key of the table and the column carried by both the PK and the unique index U1.
• TASK_TEMPLATE_GROUP_ID — foreign key to JTF_TASK_TEMP_GROUPS_B; identifies the task template group being mapped.
• INCIDENT_TYPE_ID — foreign key to CS_INCIDENT_TYPES_B; the service request type for which the mapping applies.
• CATEGORY_ID — the product category qualifier for the mapping.
• INVENTORY_ITEM_ID and ORGANIZATION_ID — the product (inventory item) and the inventory organization that scope the mapping.
• PROBLEM_CODE — the problem code associated with the mapping.
• START_DATE and END_DATE — effective dating that determines when the mapping is active.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM layer.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-organization / data-security filtering.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns maintained by the application.

The surrogate key is distinct from the business-key candidate exposed by the unique index; however, the operational uniqueness of a mapping is effectively determined by the combination of TASK_TEMPLATE_GROUP_ID with the qualifying attributes INCIDENT_TYPE_ID, CATEGORY_ID, INVENTORY_ITEM_ID and ORGANIZATION_ID within the active date window.

Common Use Cases and Queries

The table is most often queried to resolve which template group applies to an incoming request, to audit template setup, and to troubleshoot missing or duplicated task generation.

• Resolve mappings for a given request type and product: SELECT m.task_template_group_id, m.incident_type_id, m.inventory_item_id FROM cs_sr_tsk_tmpl_gp_map m WHERE m.incident_type_id = :p_type AND m.inventory_item_id = :p_item AND TRUNC(SYSDATE) BETWEEN m.start_date AND NVL(m.end_date, SYSDATE);
• Reporting joins to template groups: SELECT g.name, m.* FROM cs_sr_tsk_tmpl_gp_map m, jtf_task_temp_groups_b g WHERE m.task_template_group_id = g.task_template_group_id;
• Data integrity checks for overlapping active windows against the same group and qualifying attributes.
• Security and multi-org validation by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

Key related objects, based on the documented FK relationships, include:

• JTF_TASK_TEMP_GROUPS_B — the task template group definition; joined on TASK_TEMPLATE_GROUP_ID.
• CS_INCIDENT_TYPES_B — the service request (incident) type; joined on INCIDENT_TYPE_ID.
• FND_SECURITY_GROUPS — security grouping used for data access; joined on SECURITY_GROUP_ID.
• JTF_TASK_TEMPLATES_B / JTF_TASK_TEMPLATE_TASKS — templates and individual tasks belonging to the resolved template group.
• CS_INCIDENTS_ALL_B — service requests against which the mappings ultimately drive task generation.
• MTL_SYSTEM_ITEMS_B and MTL_ITEM_CATEGORIES — master source of INVENTORY_ITEM_ID and CATEGORY_ID used in the mapping.