Search Results jtf_cal_items_tl




Overview
Explore in AI Chat

Overview

JTF_CAL_ITEMS_TL is the translation (language-specific) table for Calendar Items within the JTF – CRM Foundation product of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It holds the translated, user-facing text attributes—item name and description—for records defined in the base table JTF_CAL_ITEMS_B, which stores the language-independent calendar item definition. The "_TL" suffix is the standard EBS multilingual designation: the base ("_B") table carries one row per logical entity, while the "_TL" table carries one row per (entity, language) combination, enabling the Resource Manager and CRM calendar functionality to render item labels in the session's language.

From a Data Vault modeling perspective, the mined FK structure classifies this table as satellite-leaning. Its primary key (CAL_ITEM_ID, LANGUAGE) makes it a descriptive, version-like satellite attached to the hub represented by JTF_CAL_ITEMS_B, rather than an independent hub or link. This classification is a heuristic suggestion derived from the foreign key topology, not a declared property of the object.

Key Information Stored

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

  • CAL_ITEM_ID – Surrogate foreign key to the parent calendar item in JTF_CAL_ITEMS_B. Part of the composite primary key JTF_CAL_ITEMS_TL_PK; not unique on its own.
  • LANGUAGE – The ISO language code identifying the translation. The second component of the composite primary key; combined with CAL_ITEM_ID it uniquely identifies each row.
  • SOURCE_LANG – The language of the source (base) text from which the translation was derived, supporting the standard EBS translation-maintenance process.
  • ITEM_NAME – The translated display name of the calendar item; the principal business attribute surfaced to users.
  • ITEM_DESCRIPTION – The translated long description of the calendar item.
  • APPLICATION_ID – Identifies the owning application, consistent with multi-org/MLS conventions across EBS.
  • SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, used for data security and filtering.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS WHO audit columns recording row creation and modification.

The surrogate composite primary key is (CAL_ITEM_ID, LANGUAGE). No separate unique business-key index is documented beyond this PK; the natural business key candidate is effectively the pair of the parent item and language.

Common Use Cases and Queries

Typical usage centers on retrieving localized calendar item labels and joining translations back to the base table for reporting. A standard query joins the two tables on CAL_ITEM_ID, filtering by LANGUAGE:

  • SELECT b.cal_item_id, t.item_name, t.item_description FROM jtf_cal_items_b b, jtf_cal_items_tl t WHERE b.cal_item_id = t.cal_item_id AND t.language = USERENV('LANG');
  • Reporting tools confirm translated content exists for all required languages by counting distinct LANGUAGE values per CAL_ITEM_ID.
  • Data-quality checks detect items missing a translation by comparing base rows to _TL rows via an outer join.
  • Security-scoped extracts filter on SECURITY_GROUP_ID against FND_SECURITY_GROUPS.

Related Objects

  • JTF_CAL_ITEMS_B – The base table; joined via JTF_CAL_ITEMS_TL.CAL_ITEM_ID = JTF_CAL_ITEMS_B.CAL_ITEM_ID. This is the documented foreign-key parent.
  • FND_SECURITY_GROUPS – Referenced by SECURITY_GROUP_ID for row-level security scoping.
  • JTF_CAL_ITEMS_TL_PK – The composite primary key index over (CAL_ITEM_ID, LANGUAGE).
  • CRM calendar and Resource Manager views and API packages that read translated calendar item names depend on this table indirectly through the base table.

Because the object is a translation satellite, all referential integrity flows inbound from JTF_CAL_ITEMS_B and FND_SECURITY_GROUPS; no child tables are documented as referencing it directly.