Search Results jtf_task_date_types_b_u1

Overview

The table JTF.JTF_TASK_DATE_TYPES_B is a foundational setup (seed data) table within the Oracle E-Business Suite CRM schema, owned by the JTF (Java Task Framework) product. Its purpose is to define and store date types that extend beyond the basic date types hard-coded in the JTF_TASK framework. As documented, the table "Allows for the description of date types other than those included as basic date types within JTF_TASK. For example, a customer may want to use a date called ACTIVATED DATE." Because these date types are customer-extensible, the table is a lookup/validation source referenced by transactional task date records. It resides in the APPS_TS_SEED tablespace, consistent with its role as a seeded reference object.

The ETRM metadata classifies this object heuristically as hub-leaning in a Data Vault modeling context. This should be treated as a modeling suggestion rather than a canonical designation: the table carries a single-column surrogate primary key and stable, non-transactional descriptive attributes, which is characteristic of a hub entity surrounded by descriptive satellite attributes.

Key Information Stored

The table's central identity is its surrogate primary key, DATE_TYPE_ID, enforced by JTF_TASK_DATE_TYPES_B_PK. The same column is also the business-key candidate, documented as the unique index JTF_TASK_DATE_TYPES_B_U1 — the index referenced in the user's search. Additional meaningful columns include:

• DATE_TYPE_ID — Unique date type identifier and primary key.
• SEQUENCE — Controls display ordering of the date type.
• APPLICATION_REFERENCE — Indicates the application for which the date type is used, enabling scoping across products.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, providing row-level security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard "who" audit columns, with user references to FND_USER and FND_LOGINS.
• OBJECT_VERSION_NUMBER — Sequential number used for database locking control in HTML-based user interfaces (Oracle Application Framework).
• ATTRIBUTE1 through ATTRIBUTE15 and ATTRIBUTE_CATEGORY — Descriptive flexfield segments supporting customer-specific extensions.

Common Use Cases and Queries

Typical usage centers on validating and displaying task date types. A join between task date transactions and this base table resolves the identifier to its descriptive context:

• Listing all configured date types: SELECT DATE_TYPE_ID, SEQUENCE, APPLICATION_REFERENCE FROM JTF.JTF_TASK_DATE_TYPES_B ORDER BY SEQUENCE;
• Joining to transactional task dates: SELECT d.DATE_TYPE_ID, d.TASK_ID FROM JTF.JTF_TASK_DATES d JOIN JTF.JTF_TASK_DATE_TYPES_B b ON d.DATE_TYPE_ID = b.DATE_TYPE_ID;
• Security-scoped reporting: filtering on SECURITY_GROUP_ID to enforce data access boundaries.

Related Objects

The base table anchors two significant dependent objects and several referenced objects:

• JTF.JTF_TASK_DATE_TYPES_TL — Translation table; joins on DATE_TYPE_ID to provide language-specific names and descriptions.
• JTF.JTF_TASK_DATES — Transactional task date records referencing DATE_TYPE_ID.
• FND_SECURITY_GROUPS — Referenced via the SECURITY_GROUP_ID foreign key.
• FND_USER and FND_LOGINS — Referenced by the standard who columns.

Together these relationships establish JTF_TASK_DATE_TYPES_B as the configuration hub underpinning extensible task date semantics in Oracle EBS.