Results for “jtf_rs_groups_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_RS_GROUPS_TL is the translation table for JTF_RS_GROUPS_B in the JTF (CRM Foundation) product of Oracle E-Business Suite. JTF_RS_GROUPS_B stores the base (language-independent) definitions of resource groups used across CRM modules — groups that collect sales agents, service agents, and other resource records for assignment, territory, and reporting purposes. Because a resource group carries a human-readable name and description, those attributes must be presented in each installed language. JTF_RS_GROUPS_TL holds the language-specific translations of those descriptive columns, enabling Multi-Language Support (MLS) so that users see group names and descriptions in their own session language regardless of the language in which the group was originally created.

The table resides in the JTF schema, is documented as VALID in ETRM for 12.1.1 and 12.2.2, and contains 11 columns. Under a heuristic Data Vault classification inferred from its foreign key structure, JTF_RS_GROUPS_TL is satellite-leaning. This is consistent with its role as a dependent table hanging off a base entity: the language-qualified descriptive attributes are functionally dependent on the GROUP_ID owned by JTF_RS_GROUPS_B, so a Data Vault model would typically place these descriptive columns in a satellite keyed by the parent hub's identifier plus LANGUAGE.

Key Information Stored

The table's primary key is JTF_RS_GROUPS_TL_PK, defined on (LANGUAGE, GROUP_ID). The LANGUAGE column is the Oracle language code identifying the translation's locale, and GROUP_ID is the surrogate identifier shared with the base table JTF_RS_GROUPS_B — together they form the composite primary key and uniquely identify one translated row per group per language. A secondary unique index, JTF_RS_GROUPS_TL_U1, is defined on (GROUP_ID, LANGUAGE), providing the reverse-ordered business-key candidate used for efficient lookup by group. The principal payload columns are GROUP_NAME and GROUP_DESC, which hold the translated name and description of the resource group. SOURCE_LANG records the language of the base (source) record from which the translation was derived, supporting the standard EBS MLS pattern. The standard audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN — track row creation and modification. SECURITY_GROUP_ID supports multi-tenant/operating-unit style data security partitioning, and it carries a foreign key to FND_SECURITY_GROUPS.

Common Use Cases and Queries

Reporting on resource groups is the most frequent use case: join the translation table to the base table and filter by the caller's current language to produce readable group lists. For example:

• Obtain group names in the session language: SELECT b.group_id, t.group_name, t.group_desc FROM jtf_rs_groups_b b, jtf_rs_groups_tl t WHERE b.group_id = t.group_id AND t.language = USERENV('LANG').
• Audit translation coverage by listing which groups lack a row for a given language, using an outer join on LANGUAGE.
• Reconcile multilingual data by comparing GROUP_NAME across SOURCE_LANG and translated rows for the same GROUP_ID.
• Populate or maintain translations through the standard MLS programmatic pattern: insert into the _TL table with GROUP_ID, LANGUAGE, SOURCE_LANG, GROUP_NAME, and GROUP_DESC, then update the corresponding _B row's LAST_UPDATE_DATE.

Because the primary key leads with LANGUAGE, queries that filter by language and group are the most efficient and will use JTF_RS_GROUPS_TL_PK. Always constrain on LANGUAGE to avoid returning duplicate rows for the same group.

Related Objects

The most significant related objects are:

• JTF_RS_GROUPS_B — the base table; joined on JTF_RS_GROUPS_TL.GROUP_ID = JTF_RS_GROUPS_B.GROUP_ID. This is the primary parent and the source of non-translated group attributes.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID, controlling which security group owns each translated row.
• JTF_RS_GROUP_MEMBERS — links resources to group definitions; joins to the base table rather than the translation table but is commonly used alongside it in group-membership reporting.
• JTF_RS_RESOURCE_EXTN / resource base tables — supplier of the resource records that group membership associates with groups.
• FND_LANGUAGES — validates the LANGUAGE value and provides the installed-language list for translation coverage queries.
• JTF_RS_GROUPS_VL — the MLS view that unions or joins the base and translation tables to expose group data in the caller's language; most application code queries this view rather than the table directly.