Results for “cug_tsk_typ_attr_deps_b”

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

Overview

CUG_TSK_TYP_ATTR_DEPS_B is a base (non-translated) table in the CUG — Citizen Interaction Center product family of Oracle E-Business Suite, available in both the 12.1.1 and 12.2.2 releases. It stores the dependency relationships between Task Types and Service Request Attributes that apply to a specific Service Request Type (modeled internally as an Incident Type). In operational terms, the table defines which Task Type is triggered, and under which attribute condition, when a citizen interaction or service request is created for a given request type. It is therefore a configuration and rules table rather than a high-volume transactional table, and its rows are typically maintained by administrators during implementation rather than by end users during daily processing.

The documented structure carries 30 columns, an OBJECT_VERSION_NUMBER for optimistic locking, the standard WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE), fifteen descriptive ATTRIBUTE columns with ATTRIBUTE_CATEGORY, and a SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS for multi-tenant data segregation. Translation coverage is provided by the companion table CUG_TSK_TYP_ATTR_DEPS_TL. Under the heuristic Data Vault classification mined from its foreign key structure, this table is hub-leaning: it holds a stable surrogate key with descriptive and conditional attributes, and it participates in relationships to two independent business entities (Task Type and Incident Type) plus dependent child tables.

Key Information Stored

• TSK_TYP_ATTR_DEP_ID — the surrogate primary key, enforced by CUG_TSK_TYP_ATTR_DEPS_B_PK and also carried by the unique index CUG_TSK_TYP_ATTR_DEPS_B_U1. This is the identifier referenced by all child tables.
• TASK_TYPE_ID — foreign key to JTF_TASK_TYPES_B, identifying the Task Type whose assignment is governed by the dependency rule.
• INCIDENT_TYPE_ID — foreign key to CS_INCIDENT_TYPES_B, identifying the Service Request / Incident Type to which the dependency applies.
• SR_ATTRIBUTE_CODE — the Service Request attribute on which the dependency condition is evaluated.
• SR_ATTRIBUTE_OPERATOR — the comparison operator applied to the attribute value when evaluating the rule.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the effective dating window controlling when the dependency is active.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing operating-unit or group-level data access.
• OBJECT_VERSION_NUMBER — concurrency control token used by the Oracle Application Framework layer.
• WHO audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, LAST_UPDATE_DATE) — standard accountability tracking.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — the standard flexfield-style descriptive columns available for customer-specific extensions.

The business key for reporting purposes is the pairing of TASK_TYPE_ID and SR_ATTRIBUTE_CODE within a given INCIDENT_TYPE_ID; TSK_TYP_ATTR_DEP_ID remains the technical key used by all referential joins.

Common Use Cases and Queries

Typical uses include auditing which Task Types are configured against a given Service Request Type, validating that effective dates do not overlap, and generating implementation documentation of the citizen interaction rule set. A representative query retrieves active dependencies for a request type:

• SELECT d.TSK_TYP_ATTR_DEP_ID, t.NAME, d.SR_ATTRIBUTE_CODE, d.SR_ATTRIBUTE_OPERATOR, d.START_DATE_ACTIVE, d.END_DATE_ACTIVE FROM CUG.CUG_TSK_TYP_ATTR_DEPS_B d, JTF.JTF_TASK_TYPES_B t WHERE d.TASK_TYPE_ID = t.TASK_TYPE_ID AND d.INCIDENT_TYPE_ID = :incident_type_id AND TRUNC(SYSDATE) BETWEEN d.START_DATE_ACTIVE AND NVL(d.END_DATE_ACTIVE, TRUNC(SYSDATE));
• Joining to CUG_SR_TASK_ATTR_VALS_B on TSK_TYP_ATTR_DEPEND_ID to list the attribute values that satisfy each dependency.
• Joining to CUG_TSK_TYP_ATTR_DEPS_TL to present translated descriptions in a multilingual or reporting-layer extract.
• Filtering by SECURITY_GROUP_ID to enforce operating-unit restrictions in custom concurrent programs and BI Publisher reports.

Related Objects

• JTF_TASK_TYPES_B — referenced via TASK_TYPE_ID; supplies Task Type definitions.
• CS_INCIDENT_TYPES_B — referenced via INCIDENT_TYPE_ID; supplies Service Request Type definitions.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs data access.
• CUG_SR_TASK_ATTR_VALS_B — child table joined on TSK_TYP_ATTR_DEPEND_ID; stores attribute values for the dependency.
• CUG_SR_TASK_TYPE_DETS_B — child table joined on TSK_TYP_ATTR_DEP_ID; stores Task Type detail rows.
• CUG_TSK_TYP_ATTR_DEPS_TL — translation table joined on TSK_TYP_ATTR_DEP_ID, providing language-specific text.

These relationships confirm that CUG_TSK_TYP_ATTR_DEPS_B acts as the central configuration hub linking Task Types, Service Request Types, and their attribute-level dependency values within the Citizen Interaction Center module.