Results for “cug_sr_task_type_dets_b”

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

Overview

The CUG_SR_TASK_TYPE_DETS_B table is a base (non-translated) table owned by the CUG schema, which belongs to the Citizen Interaction Center product family within Oracle E-Business Suite. It stores additional configuration details about the task types that are associated with a given Service Request (SR) type. In practical terms, this object captures the rules, defaults, and scheduling parameters that govern how tasks are generated, assigned, prioritized, and scheduled when a service request of a particular type is created or progressed.

In the 12.1.1 and 12.2.2 releases this table participates directly in the SR-to-task automation flow, supplying task status, ownership, priority, and planned/scheduled offset information that drives task creation logic. The accompanying translation table, CUG_SR_TASK_TYPE_DETS_TL, holds the language-dependent descriptive columns.

From a Data Vault modeling perspective, the documented FK structure is satellite-leaning. The table carries descriptive attributes (status, priority, offsets, flags, flex attributes) attached to a parent task-type attribute dependency, rather than functioning as an independent hub. This classification should be treated as a modeling suggestion derived heuristically from the foreign key topology, not as a formally declared Oracle construct.

Key Information Stored

The table is defined with 41 columns. The most significant are:

• SR_TASK_TYPE_DET_ID — surrogate primary key of the table, populated via the CUG_SR_TASK_TYPE_DETS_B_PK constraint. This is the technical unique key referenced by the TL child table.
• TSK_TYP_ATTR_DEP_ID — foreign key to CUG_TSK_TYP_ATTR_DEPS_B, linking the detail row to a specific task-type attribute dependency and effectively acting as a business-context parent reference.
• TASK_STATUS_ID — foreign key to JTF_TASK_STATUSES_B, defining the status applied to the generated task.
• TASK_PRIORITY_ID — foreign key to JTF_TASK_PRIORITIES_B, defaulting the task priority.
• OWNER_ID — polymorphic owner reference that can resolve to JTF_RS_GROUPS_B, JTF_RS_RESOURCE_EXTNS, or JTF_RS_TEAMS_B depending on the owner type.
• OWNER_TYPE_CODE — disambiguates the entity type behind OWNER_ID (resource, group, team).
• ASSIGNED_BY_ID and ASSIGNEE_TYPE_CODE — capture the assigner and the type of the assignee.
• PLANNED_START_OFFSET, PLANNED_END_OFFSET, PLANNED_START_UOM, PLANNED_END_UOM — define planned scheduling windows relative to the SR, with unit-of-measure codes.
• SCHEDULED_START_OFFSET, SCHEDULED_END_OFFSET, SCHEDULED_START_UOM, SCHEDULED_END_UOM — the analogous scheduled-window parameters.
• PRIVATE_FLAG and PUBLISH_FLAG — control visibility and publication behavior of the resulting task.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group access.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard EBS descriptive flexfield (DFF) columns for customer-defined extensions.
• OBJECT_VERSION_NUMBER plus the standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) — provide optimistic locking and audit trails.

The primary key SR_TASK_TYPE_DET_ID is the only documented unique identifier. No separate business-key unique index is listed in the ETRM metadata, so no natural business key is formally enforced beyond the FK relationships.

Common Use Cases and Queries

Typical scenarios include auditing the configuration of task defaults per SR type, verifying ownership and priority assignments, and reporting on scheduling offsets that drive task due dates. A representative join query is:

• Join CUG_SR_TASK_TYPE_DETS_B d to JTF_TASK_STATUSES_B s ON d.TASK_STATUS_ID = s.STATUS_ID and JTF_TASK_PRIORITIES_B p ON d.TASK_PRIORITY_ID = p.TASK_PRIORITY_ID to resolve status and priority descriptions.
• Join to CUG_SR_TASK_TYPE_DETS_TL t ON d.SR_TASK_TYPE_DET_ID = t.SR_TASK_TYPE_DET_ID to retrieve translated names/descriptions for reporting.
• Filter by OWNER_TYPE_CODE and OWNER_ID to list all SR task configurations owned by a given resource group, team, or individual.
• Query the DFF columns (ATTRIBUTE_CATEGORY, ATTRIBUTE1–15) for customer-specific reporting requirements.

Because the table is configuration-oriented, it is commonly used in setup validation reports, migration scripts, and diagnostic queries that compare task behavior across environments.

Related Objects

• CUG_SR_TASK_TYPE_DETS_TL — translation table joined on SR_TASK_TYPE_DET_ID; the only documented child referencing this table.
• CUG_TSK_TYP_ATTR_DEPS_B — parent dependency table via TSK_TYP_ATTR_DEP_ID.
• JTF_TASK_STATUSES_B — status lookup via TASK_STATUS_ID.
• JTF_TASK_PRIORITIES_B — priority lookup via TASK_PRIORITY_ID.
• JTF_RS_GROUPS_B, JTF_RS_TEAMS_B, and JTF_RS_RESOURCE_EXTNS — resource-management tables resolving OWNER_ID by owner type.
• FND_SECURITY_GROUPS — security-group reference via SECURITY_GROUP_ID.

These relationships make the table a central configuration point connecting SR task types to resource, status, and priority master data within the Citizen Interaction Center module.