Search Results jtf_r_rulesets_tl




Overview
Explore in AI Chat

Overview

The JTF_R_RULESETS_TL table is a translated (TL) child table within the JTF schema of Oracle E-Business Suite, belonging to the CRM Foundation product family. Its documented purpose is to store translated descriptions and names of rule set information, enabling multi-language support for rule set definitions consumed by CRM applications such as Oracle TeleSales, Oracle Marketing, and Oracle Field Service. In the Oracle EBS Two-Task and MLS (Multi-Lingual Support) architecture, a base table (JTF_R_RULESETS_B) holds language-independent attributes, while the _TL counterpart holds language-dependent attributes keyed by language code.

From a data modeling perspective, the mined heuristic classifies JTF_R_RULESETS_TL as satellite-leaning. This is a reasonable suggestion: the table does not own independent business identity — it depends entirely on JTF_R_RULESETS_B via the RULESET_ID foreign key, and it carries descriptive, language-specific attributes (NAME, DESCRIPTION) attached to that base entity. It therefore functions as a translation satellite of the base hub record rather than a hub or link in its own right.

Key Information Stored

The table’s documented physical schema at ETRM 12.2.2 contains 13 columns, of which the following are the most significant:

  • RULESET_ID — Surrogate identifier for the rule set. This column is the FK to JTF_R_RULESETS_B and forms part of both the primary key and the primary unique index.
  • LANGUAGE — The language code of the translated row. Together with RULESET_ID, it constitutes the composite primary key JTF_R_RULESETS_TL_PK.
  • NAME — The translated name of the rule set. Documented as the leading column of a unique index (JTF_R_RULESETS_TL_UK1 / JTF_R_RULESETS_TL_U1), making it a business-key candidate alongside LANGUAGE.
  • DESCRIPTION — The translated long description of the rule set; the principal reason the table exists per its documented description.
  • SOURCE_LANG — The source language of the base record, used by MLS to determine whether translation is required.
  • SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, enforcing Oracle EBS multi-org / data-security filtering at the row level.
  • OBJECT_VERSION_NUMBER — Optimistic locking column used by the Oracle Application Framework and OAF-based pages to detect concurrent updates.
  • CREATED_BY, CREATION_DATE, CREATED_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard WHO audit columns recording who created and last modified each translation row and when.

The surrogate primary key is thus (RULESET_ID, LANGUAGE), while the business-key candidate documented through the unique index is (RULESET_ID, LANGUAGE) under the U1 index, with NAME additionally constrained in the UK1 definition.

Common Use Cases and Queries

Typical usage involves joining the translated table to its base table to retrieve a display-ready rule set name and description in the session language, or reporting on translated content coverage for localization audits. For example, to list rule sets in English (US):

  • SELECT b.ruleset_id, t.name, t.description
  • FROM jtf.jtf_r_rulesets_b b
  • JOIN jtf.jtf_r_rulesets_tl t
  • ON t.ruleset_id = b.ruleset_id
  • WHERE t.language = USERENV('LANG')
  • AND b.security_group_id = :sgid;

Additional scenarios include detecting missing translations by comparing language rows against the base, auditing changes to rule set descriptions over time via LAST_UPDATE_DATE, and populating concurrent-program reports that must honor the MLS language of the requesting user. Because both NAME and LANGUAGE are indexed, lookup by name in a specific language is efficient.

Related Objects

The following are the most significant related objects and their join columns:

  • JTF_R_RULESETS_B — Base (language-independent) parent table; joined on RULESET_ID. Provides the authoritative identity of each rule set.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for org-level security filtering.
  • JTF_R_RULESETS_TL_PK — Primary-key constraint on (RULESET_ID, LANGUAGE).
  • JTF_R_RULESETS_TL_U1 / JTF_R_RULESETS_TL_UK1 — Unique indexes over (RULESET_ID, LANGUAGE) and NAME, supporting business-key and lookup performance.
  • JTF_R_RULESETS_VL (where present) — The MLS view that unions the base and translated tables for developer convenience.
  • JTF_R_RULESETS_B (WHO columns) — Inherited audit semantics shared across the pair.

Together these objects support localized rule set definition and administration within CRM Foundation.