Search Results jtf_task_date_types_b_pk

Overview

JTF.JTF_TASK_DATE_TYPES_B is a CRM Foundation base table in Oracle E-Business Suite (validated in 12.1.1 and 12.2.2). It defines an extensible catalog of date-type definitions that supplement the seeded date types built directly into JTF_TASK. The table exists because the standard task date model only accommodates a fixed set of basic date types, whereas business scenarios frequently require additional, customer-defined dates — for example a date called "ACTIVATED DATE" — that are not part of the seeded set. Records maintained here are consumed by JTF_TASK_DATES whenever a task instance records a value for a user-defined date type.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a hub-leaning classification. DATE_TYPE_ID is the sole component of the primary key (JTF_TASK_DATE_TYPES_B_PK) and is also the join key used by two dependent tables, which is characteristic of a hub holding a stable business key. Because the table also carries descriptive and audit columns in the same structure, implementers following Data Vault conventions may prefer to treat the descriptive attributes as satellite content in a separate table, while retaining this object as the reference hub for date-type identity.

Key Information Stored

The documented physical schema contains 26 columns. The most significant are:

• DATE_TYPE_ID — the surrogate primary key and the single business-key candidate (unique index JTF_TASK_DATE_TYPES_B_U1). Every downstream reference to a date type resolves through this column, which is also the self-referential component shown in the foreign-key metadata.
• SEQUENCE — ordering value used to control display or processing order of date types in list-of-values and UI presentations.
• APPLICATION_REFERENCE — identifies the owning application context, allowing the same catalog to serve multiple CRM Foundation consumers.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework to detect concurrent updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant/security-group partitioning of reference data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS WHO-column audit set, widely used in data lineage and reconciliation reporting.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard descriptive flexfield (DFF) columns, available for customer-specific extension without schema change.

The translatable name and description content is not held on this base table; it resides in the _TL companion, consistent with the EBS multilanguage design pattern.

Common Use Cases and Queries

The table is most commonly queried to resolve a date-type identifier into a meaningful name, either directly through the _TL join or indirectly when reporting on task dates.

• Populating lists of values for task date entry forms and OAF pages.
• Validating that a date type supplied by an interface or conversion program is defined before inserting into JTF_TASK_DATES.
• Auditing which custom date types have been introduced beyond the seeded set, and which security group owns them.
• Reconciling task date data against the defining catalog after a clone or upgrade.

A typical resolution pattern joins the base and translation tables on the shared key:

SELECT b.date_type_id,
       t.name,
       b.sequence,
       b.application_reference
FROM   jtf.jtf_task_date_types_b b,
       jtf.jtf_task_date_types_tl t
WHERE  b.date_type_id = t.date_type_id
AND    t.language = USERENV('LANG')
ORDER  BY b.sequence;

A usage-count query identifies which defined types are actually in service, joining to task dates on DATE_TYPE_ID and grouping by type.

Related Objects

• JTF_TASK_DATES — references this table via DATE_TYPE_ID; holds the per-task date values recorded against each defined date type. This is the principal transactional consumer.
• JTF_TASK_DATE_TYPES_TL — the translation companion, joined on DATE_TYPE_ID, supplying the language-specific name and description.
• JTF_TASK — the parent task entity whose basic date types this catalog extends.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; governs visibility of date-type rows across security partitions.