Search Results jtf_rs_default_groups




Overview
Explore in AI Chat

Overview

JTF_RS_DEFAULT_GROUPS is a CRM Foundation (JTF) resource management table in Oracle E-Business Suite 12.1.1 and 12.2.2. It records the default resource group assignments that determine which groups a resource or user is associated with by default within the Resource Manager and CRM group security model. The table holds 14 documented columns in the JTF schema and is classified as VALID in ETRM.

From a Data Vault modeling perspective, the mined FK structure classifies this table as standalone. This suggests treating it as an independent hub or reference entity rather than a strict link or satellite, since the only documented foreign key is a security-group reference to FND_SECURITY_GROUPS and there is no FK capture for the resource or group columns. Practically, it functions as an association table tying RESOURCE_ID / USER_ID to GROUP_ID with effective dating.

Key Information Stored

  • DEFAULT_GROUPS_ID — surrogate primary key uniquely identifying each default group assignment row.
  • RESOURCE_ID / RESOURCE_NUMBER — identifiers for the resource to whom the default group applies; RESOURCE_NUMBER is a denormalized human-readable reference.
  • USER_ID — the application user associated with the assignment, supporting user-level defaulting.
  • GROUP_ID — the group being assigned as a default (business-key candidate alongside RESOURCE_ID/USER_ID).
  • START_DATE / END_DATE — effective dating that governs the active window of each default assignment.
  • USAGE — usage classification qualifying the assignment.
  • SECURITY_GROUP_ID — the only documented FK, referencing FND_SECURITY_GROUPS; drives multi-tenant / operating-unit data segregation.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Business-key candidates (possibly backed by unique indexes) include the combination of RESOURCE_ID/USER_ID with GROUP_ID and effective dates; the surrogate DEFAULT_GROUPS_ID should be joined on wherever it is propagated.

Common Use Cases and Queries

Typical scenarios include determining the default group set for a resource, validating active assignments, and auditing group security coverage. A common pattern joins the assignment to its security group:

  • List active defaults for a resource: filter on RESOURCE_ID and use SYSDATE between START_DATE and END_DATE.
  • Resolve group names by joining GROUP_ID to the resource group definition table (JTF_RS_GROUPS_B / _TL).
  • Security audit: group by SECURITY_GROUP_ID joined to FND_SECURITY_GROUPS to spot resources lacking defaults.

A representative query:

SELECT d.DEFAULT_GROUPS_ID, d.RESOURCE_ID, d.GROUP_ID, d.START_DATE, d.END_DATE
FROM JTF.JTF_RS_DEFAULT_GROUPS d
WHERE d.RESOURCE_ID = :resource_id
AND SYSDATE BETWEEN d.START_DATE AND NVL(d.END_DATE, SYSDATE);

Related Objects

  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID; primary documented FK relationship.
  • JTF_RS_GROUPS_B / JTF_RS_GROUPS_TL — group definitions resolved via GROUP_ID.
  • JTF_RS_RESOURCE_EXTNS / JTF_RS_EMPLOYEES — resource master detail for RESOURCE_ID / RESOURCE_NUMBER.
  • FND_USER — joins on USER_ID for user-level defaults.
  • JTF_RS_GROUP_MEMBERS — related membership table supporting Resource Manager group logic.

The FK relationships above are drawn directly from the documented ETRM relationship data; additional joins on RESOURCE_ID and GROUP_ID are inferred from the column semantics rather than documented FK constraints.