Search Results jtf_rs_groups_vl

Overview

JTF_RS_GROUPS_VL is a Multi-Lingual Support (MLS) view owned by the APPS schema within the JTF – CRM Foundation product family. It exposes translated resource group definitions maintained by the Resource Manager (RS) subsystem, which underpins territory, resource, and group assignment functionality across Oracle E-Business Suite. The view is classified as VALID and is available in both Oracle EBS 12.1.1 and 12.2.2, with identical documented metadata in the 12.2.2 ETRM repository.

The view presents a denormalized, language-filtered projection of group header information by joining the base table JTF_RS_GROUPS_B to its translation table JTF_RS_GROUPS_TL. Its purpose is to deliver group records in the session language of the querying user, as determined by USERENV('LANG'). Because group names and descriptions are translatable, this view is the recommended access path for any reporting, integration, or concurrent program that must display group data in the user's operating language. Direct queries against the base tables would either return untranslated rows or require the caller to construct the MLS join manually.

Underlying Base Objects

The view definition references two objects, both resolved through APPS synonyms:

• JTF_RS_GROUPS_B — the base (non-translated) table holding the group identifier, group number, attributes, status flags, and audit columns.
• JTF_RS_GROUPS_TL — the translation table holding GROUP_NAME and GROUP_DESC keyed by GROUP_ID and LANGUAGE.

The view text selects all columns from JTF_RS_GROUPS_B (aliased B) and the two translatable columns from JTF_RS_GROUPS_TL (aliased T). The join predicate is B.GROUP_ID = T.GROUP_ID combined with the language filter T.LANGUAGE = USERENV('LANG'), which restricts the result set to the single active session language. Consequently, the row cardinality of the view matches the base table for a given language, but rows are returned only where a translation exists for the current language. A pseudocolumn ROW_ID is derived from B.ROWID.

Key Columns

• GROUP_ID — primary grouping identifier and the join key between the base and translation tables.
• GROUP_NUMBER — user-visible or system-assigned group number.
• GROUP_NAME / GROUP_DESC — translated name and description, sourced from JTF_RS_GROUPS_TL in the session language.
• EMAIL_ADDRESS — contact address associated with the group.
• EXCLUSIVE_FLAG — indicates whether the group is exclusive.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating window for the group.
• ACCOUNTING_CODE — accounting classification associated with the group.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J framework.
• TIME_ZONE — time zone attribute of the group.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 — the standard DFF (descriptive flexfield) context and segment columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ROW_ID — row identifier derived from the base table ROWID.

Common Use Cases and Queries

Typical uses include group list-of-values queries, resource group reporting, and integration extracts that require localized group labels. The following query retrieves all groups in the current session language with names and descriptions intact. Note that no WHERE clause on LANGUAGE is required, since the view already applies the USERENV('LANG') filter:

• SELECT group_id, group_number, group_name, group_desc FROM jtf_rs_groups_vl;
• SELECT group_id, group_name FROM jtf_rs_groups_vl WHERE exclusive_flag = 'Y';
• SELECT group_id, group_name, start_date_active, end_date_active FROM jtf_rs_groups_vl WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);
• SELECT g.group_name, g.email_address, g.time_zone FROM jtf_rs_groups_vl g WHERE g.accounting_code = 'DEFAULT';

Because the view is defined with the APPS owner and is read-only, DML must be directed at the base tables JTF_RS_GROUPS_B and JTF_RS_GROUPS_TL. The view is safe to use in reports and integrations across both 12.1.1 and 12.2.2, as its definition and referenced objects are unchanged between these releases.