Results for “xnc_cs_sr_task_map”

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

Overview

XNC_CS_SR_TASK_MAP is a mapping table within the Oracle E-Business Suite product family XNC — Sales for Communications, a module documented as obsolete in EBS 12.1.1 and 12.2.2. Its stated purpose is to hold all information relating an Incident type to a task template group, thereby defining which set of standard tasks should be generated when a service request or incident of a given classification is created. The table functionally operates as an association entity between incident classification data and task-generation configuration data.

From a Data Vault modeling perspective, the heuristic classification of this object is a link. This classification is derived from the foreign-key structure: the table resolves a many-to-many style relationship between CS_INCIDENT_TYPES_B and JTF_TASK_TEMP_GROUPS_B rather than storing descriptive attributes about a single business entity. Note the ETRM metadata records that this table is not implemented in the reference database, so the object may exist only as a shipped definition or may be absent entirely in a given instance.

Key Information Stored

The documented column inventory is limited, and the following are the significant elements confirmed by the metadata:

• SR_TASK_MAP_ID — the surrogate primary key, defined by the constraint XNC_CS_SR_TASK_MAP_PK. This is a system-generated identifier carrying no business meaning.
• INCIDENT_TYPE_ID — the foreign key to CS_INCIDENT_TYPES_B, identifying the incident type (service request classification) being mapped.
• TASK_TEMPLATE_GROUP_ID — the foreign key to JTF_TASK_TEMP_GROUPS_B, identifying the task template group that supplies the default task set for that incident type.
• START_DATE_ACTIVE — the effective start date for the mapping record, supporting date-effective or versioned assignment of task template groups to incident types.

A second unique index, XNC_CS_SR_TASK_MAP_U1, is documented over INCIDENT_TYPE_ID and START_DATE_ACTIVE. This composite constitutes the principal business-key candidate: it enforces that a given incident type may hold only one active task-template-group assignment per effective date. The surrogate SR_TASK_MAP_ID should therefore never be exposed to end users as a business reference.

Common Use Cases and Queries

The primary functional scenario is configuration validation — confirming that each active incident type resolves to exactly one applicable task template group for a given date. A representative query joins the mapping to both parent tables and filters by the effective date:

• SELECT m.SR_TASK_MAP_ID, m.INCIDENT_TYPE_ID, m.TASK_TEMPLATE_GROUP_ID, m.START_DATE_ACTIVE FROM XNC_CS_SR_TASK_MAP m WHERE TRUNC(m.START_DATE_ACTIVE) <= TRUNC(SYSDATE) ORDER BY m.INCIDENT_TYPE_ID, m.START_DATE_ACTIVE DESC;
• Joining to CS_INCIDENT_TYPES_B on INCIDENT_TYPE_ID to retrieve incident type names alongside the assigned task template group.
• Joining to JTF_TASK_TEMP_GROUPS_B on TASK_TEMPLATE_GROUP_ID to list the task groups in use and detect orphaned or unused template groups.
• Exception reporting for incident types lacking any mapping row, which would indicate missing task-generation configuration.

Because the module is obsolete and the table is not implemented in the reference database, these patterns should be treated as reference or migration-oriented rather than as production reporting against a live 12.2.2 instance.

Related Objects

The following objects are the most significant dependencies, based on the documented foreign-key relationships:

• CS_INCIDENT_TYPES_B — referenced via XNC_CS_SR_TASK_MAP.INCIDENT_TYPE_ID; supplies the incident type definition.
• JTF_TASK_TEMP_GROUPS_B — referenced via XNC_CS_SR_TASK_MAP.TASK_TEMPLATE_GROUP_ID; supplies the task template group definition.
• XNC_CS_SR_TASK_MAP_PK — the primary-key constraint on SR_TASK_MAP_ID.
• XNC_CS_SR_TASK_MAP_U1 — the unique constraint on INCIDENT_TYPE_ID and START_DATE_ACTIVE.
• Related JTF task template entities (for example JTF_TASK_TEMPLATES_B and the corresponding _TL translation tables) that describe the individual tasks contained within each template group.
• The CS_INCIDENT_TYPES_TL translation table, used to obtain incident type descriptions for reporting.