Search Results jtf_task_custom_colors_u2

Overview

The JTF.JTF_TASK_CUSTOM_COLORS table belongs to the Oracle E-Business Suite Customer Relationship Management (CRM) foundation schema, JTF (Java Technology Foundation), and stores configuration data for custom task color rules. It is the persistence layer behind the Task Manager color-coding capability, allowing implementers to define visual rules that color task rows and assignment rows based on task attributes such as task type, task priority, assignment status, or escalation state. The table resides in the APPS_TS_SEED tablespace, which signals that its contents are treated as seed or configuration reference data shipped with, and maintained alongside, application setup rather than high-volume transactional data. The object is marked VALID and is registered under the FND Design Data namespace JTF.JTF_TASK_CUSTOM_COLORS.

From a Data Vault modeling perspective, the ETRM relationship metadata classifies this object heuristically as a standalone structure. In practice this suggests a hub-like entity: the table is keyed on a single surrogate identifier (RULE_ID) and does not itself act as a link between two or more parent hubs. Its foreign-key columns point outward to other reference entities, so the modeling suggestion is that JTF_TASK_CUSTOM_COLORS behaves as a primary rule hub with a small satellite of descriptive attributes (color values, flags, WHO audit columns), rather than as a junction or intersection table.

Key Information Stored

The physical schema documented for 12.2.2 contains sixteen columns. The most significant are:

• RULE_ID — the surrogate primary key, defined by JTF_TASK_CUSTOM_COLORS_PK. Each row represents a single color-determination rule.
• COLOR_DETERMINATION_PRIORITY — a mandatory unique value that controls the order in which rules are evaluated. This is a business-key candidate, enforced by unique index JTF_TASK_CUSTOM_COLORS_U2.
• RULE_ID with ZD_EDITION_NAME — the second business-key candidate, enforced by JTF_TASK_CUSTOM_COLORS_U1, and the column set that anchors the identity of a rule across edition-enabled lines.
• TYPE_ID — references the task type (IEO_SVR_TYPES_B), letting rules target specific task categories.
• PRIORITY_ID — the task priority that triggers the rule.
• ASSIGNMENT_STATUS_ID — references IRC_ASSIGNMENT_STATUSES, allowing rules to key off assignment status values.
• ESCALATED_TASK — a flag indicating whether the rule applies to escalated tasks.
• BACKGROUND_COL_DEC and BACKGROUND_COL_RGB — the actual display values applied to the task when a rule matches: a decimal color code and a 12-character RGB string.
• ACTIVE_FLAG — indicates whether the rule is currently valid and should be considered at runtime.
• OBJECT_VERSION_NUMBER — the standard optimistic-locking column used by the framework.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the WHO audit columns populated automatically by the audit framework.
• ZD_EDITION_NAME — the editioning discriminator that supports edition-based redefinition and multiple data lines.

Common Use Cases and Queries

The principal setup and support scenarios center on diagnosing and reporting task color behavior. A typical diagnostic query returns rules in the exact priority order the runtime engine uses:

SELECT rule_id, color_determination_priority, type_id, priority_id,
       assignment_status_id, escalated_task,
       background_col_dec, background_col_rgb, active_flag
FROM   jtf.jtf_task_custom_colors
WHERE  active_flag = 'Y'
ORDER BY color_determination_priority;

Useful variants include filtering to rules that target a specific task type or assignment status, joining TYPE_ID to the task type lookup when reporting rules and their textual descriptions, and auditing for duplicate or conflicting priority values when users report that colors appear inconsistently. A maintenance query such as SELECT rule_id, active_flag, last_updated_by, last_update_date FROM jtf.jtf_task_custom_colors WHERE rule_id = :id is useful for confirming whether a rule was recently deactivated by a setup change. Reporting use cases include an inventory of all active color rules for change-control documentation, and reconciliation of decimal versus RGB values to verify that both representations are populated consistently.

Related Objects

• IEO_SVR_TYPES_B — parent lookup for TYPE_ID; joined to describe the task type a rule targets.
• IRC_ASSIGNMENT_STATUSES — parent lookup for ASSIGNMENT_STATUS_ID; joined to describe the assignment status a rule targets.
• JTF_TASK_CUSTOM_COLORS# — the editioned underlying object that JTF_TASK_CUSTOM_COLORS references.
• JTF_TASKS and task assignment tables — these consume rule output at runtime when rendering colored task rows.
• JTF_TASK_PRIORITIES — logically related to PRIORITY_ID, used for priority descriptions in reporting.
• FND_STANDARD_DATE / WHO audit views — the framework objects that populate the audit columns present in this table.

Because the table is standalone in the Data Vault sense, join paths are driven by the foreign keys to the type and assignment-status lookups rather than by dependent child tables.