Results for “cug_tsk_typ_attr_maps_b”

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

Overview

CUG_TSK_TYP_ATTR_MAPS_B is a base table owned by the CUG schema (Citizen Interaction Center) in Oracle E-Business Suite 12.1.1 and 12.2.2. It defines the mapping between a task type and the individual attributes that apply to that task type. In effect, the table is a configuration repository: for each task type, it enumerates which attributes are available, whether they are mandatory or displayed, what default values they take, and the value list that constrains them. This strategic placement means that downstream task execution logic, service request processing, and UI rendering all derive attribute behaviour from records stored here.

Because the table carries descriptive, time-stamped, and attribute-driven data bound to a stable business identifier, a Data Vault modeling heuristic classifies it as hub-leaning. The heuristic is a modeling suggestion only and reflects the table's implied function as a store of distinct mapping entities referenced by satellites and link tables rather than as a pure junction or link.

Key Information Stored

The table contains 33 documented columns. The most significant are:

• TSK_TYP_ATTR_MAP_ID — the surrogate primary key (CUG_TSK_TYP_ATTR_MAPS_B_PK). It uniquely identifies each task-type-to-attribute mapping.
• TASK_TYPE_ATTRIBUTE_CODE — the code identifying the specific attribute being mapped. Together with TASK_TYPE_ID it forms the business-key candidate CUG_TSK_TYP_ATTR_MAPS_B_U2.
• TASK_TYPE_ID — the foreign key to JTF_TASK_TYPES_B, anchoring the mapping to a specific task type.
• TASK_ATTR_DEFAULT_VALUE — the default value applied to the attribute when no explicit value is supplied.
• TASK_ATTR_MANDATORY_FLAG — indicates whether the attribute must be captured for the task type.
• TASK_ATTR_DISPLAYED_FLAG — controls whether the attribute is surfaced in the user interface.
• TASK_ATTRIBUTE_LIST_NAME — names the value list used to validate or populate the attribute.
• START_DATE_ACTIVE and END_DATE_ACTIVE — bound the effective date range of the mapping.
• OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) segment used to extend the mapping without schema changes.
• SECURITY_GROUP_ID — the foreign key to FND_SECURITY_GROUPS, governing row-level access control.
• ZD_EDITION_NAME — supports the edition-based redefinition model used in Release 12.2 online patching. It also participates in the unique indexes CUG_TSK_TYP_ATTR_MAPS_B_U1 (TSK_TYP_ATTR_MAP_ID, ZD_EDITION_NAME) and U2.

Common Use Cases and Queries

Typical uses include reporting on task type configuration, validating that all mandatory attributes are defined before go-live, and troubleshooting why an attribute does not appear on a task form. A representative query joining the mapping to its task type is:

• SELECT m.TASK_TYPE_ID, m.TASK_TYPE_ATTRIBUTE_CODE, m.TASK_ATTR_MANDATORY_FLAG, m.TASK_ATTR_DISPLAYED_FLAG FROM CUG_TSK_TYP_ATTR_MAPS_B m WHERE m.TASK_TYPE_ID = :task_type_id AND SYSDATE BETWEEN m.START_DATE_ACTIVE AND NVL(m.END_DATE_ACTIVE, SYSDATE);

Additional patterns include locating resolved attribute values per service request by joining through CUG_SR_TASK_ATTR_VALS_B, and reporting on the effective configuration window using START_DATE_ACTIVE and END_DATE_ACTIVE.

Related Objects

The principal related objects, based on the documented foreign key relationships, are:

• JTF_TASK_TYPES_B — referenced by CUG_TSK_TYP_ATTR_MAPS_B.TASK_TYPE_ID; the parent task type definition.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for access control.
• CUG_SR_TASK_ATTR_VALS_B — references this table via TASK_TYPE_ATTR_MAP_ID, storing the resolved attribute values for service requests.
• CUG_TSK_TYP_ATTR_MAPS_TL — the translation table, joined on TSK_TYP_ATTR_MAP_ID, holding language-specific attribute labels.

Together these objects form the configuration and instance layers through which Citizen Interaction Center task attributes are defined, secured, translated, and applied at runtime.