Search Results jtf_task_reference_codes

Overview

JTF.JTF_TASK_REFERENCES_B is the base (non-translated) table within the Oracle E-Business Suite Task Management schema that stores reference details for a given task. A task, as defined in JTF_TASKS_B, can be associated with external or internal business objects — such as a service request, an opportunity, a contact, or another entity — and JTF_TASK_REFERENCES_B records those associations. Each row represents a single reference holding an object type, an object name, an internal object identifier, and a reference code that classifies the context of the association.

The REFERENCE_CODE column draws its valid values from the lookup type JTF_TASK_REFERENCE_CODES, which makes the table extensible without schema changes; new reference contexts can be introduced by adding lookup codes. The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, while its indexes are placed in APPS_TS_TX_IDX, consistent with standard EBS transactional data and index separation practices.

From a Data Vault modeling perspective, the mined foreign-key structure suggests this object behaves as a link. It resolves many-to-many style associations between tasks and referenced objects and carries its own descriptive payload (OBJECT_DETAILS, ATTRIBUTE segments), which gives it light satellite characteristics. This classification is a heuristic suggestion, not an Oracle-declared designation.

Key Information Stored

The table is documented with 30 columns. The most significant are summarized below.

• TASK_REFERENCE_ID — The surrogate primary key (JTF_TASK_REFERENCES_B_PK) and the column behind the unique index JTF_TASK_REFERENCES_B_U1. It provides the single-column business-key candidate for uniqueness.
• TASK_ID — Foreign key to JTF_TASKS_B. Identifies the task that owns the reference. Indexed by JTF_TASK_REFERENCES_B_N2.
• OBJECT_TYPE_CODE — Reference object type, validated against JTF_OBJECTS_B. Part of the composite non-unique indexes N1 and N3.
• OBJECT_ID — Internal ID of the referenced object; also modeled as a foreign key to CS_INCIDENTS_ALL_B. Part of index N1.
• OBJECT_NAME — Descriptive name of the referenced object. Part of index N3.
• OBJECT_DETAILS — Free-form VARCHAR2(2000) field holding additional context about the referenced object.
• REFERENCE_CODE — Lookup code indicating the context of the reference, sourced from JTF_TASK_REFERENCE_CODES.
• OBJECT_VERSION_NUMBER — Sequential value used for optimistic locking under the HTML (OA Framework) user interface.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO columns; the user columns reference FND_USER.USER_ID and the login column references FND_LOGINS.LOGIN_ID.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-organization / security-group data partitioning.
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield (DFF) segments available for customer-specific extension.

Common Use Cases and Queries

The table is typically queried in two directions: from the task to find all of its references, or from a business object to find all tasks that reference it. Both patterns are supported by the existing indexes.

• All references for a given task — query on TASK_ID, using JTF_TASK_REFERENCES_B_N2.
• All tasks referencing a specific object — query on OBJECT_TYPE_CODE and OBJECT_ID, using JTF_TASK_REFERENCES_B_N1.
• Lookup by object name — query on OBJECT_TYPE_CODE and OBJECT_NAME, using JTF_TASK_REFERENCES_B_N3.
• Single-row fetch — query on TASK_REFERENCE_ID, using the unique index JTF_TASK_REFERENCES_B_U1.

A representative query joining tasks to their incident references might read: select r.task_reference_id, r.task_id, r.object_id, r.reference_code from jtf_task_references_b r where r.task_id = :task_id and r.object_type_code = 'INCIDENT'. Reporting extracts commonly join to JTF_TASKS_B for task attributes and to CS_INCIDENTS_ALL_B for incident attributes, and filter by REFERENCE_CODE to isolate a specific reference context.

Related Objects

• JTF_TASKS_B — Parent task table; joined on TASK_ID.
• JTF_OBJECTS_B — Object type definitions; joined on OBJECT_TYPE_CODE.
• CS_INCIDENTS_ALL_B — Service request / incident base table; joined on OBJECT_ID.
• FND_SECURITY_GROUPS — Security group definitions; joined on SECURITY_GROUP_ID.
• FND_USER — WHO-column user validation and audit reporting.
• FND_LOGINS — Login-level audit reference for LAST_UPDATE_LOGIN.
• JTF_TASK_REFERENCE_CODES — Lookup type supplying valid REFERENCE_CODE values.