Results for “jtf_rs_group_usages”

50+ results




Overview
Explore in AI Chat

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

Overview

JTF_RS_GROUP_USAGES is a foundation table in the JTF (CRM Foundation) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores the usage assignments that qualify resource groups — the classifications that determine how a group may be referenced and consumed by CRM applications such as Oracle TeleSales, Field Service, and Interaction Center. Each row links a resource group (identified by GROUP_ID) to a single USAGE value, allowing one group to carry multiple, distinct usages without duplication.

The table carries a surrogate primary key, GROUP_USAGE_ID, plus a business-key unique index (JTF_RS_GROUP_USAGES_U2) on the GROUP_ID and USAGE pair. A foreign key to JTF_RS_GROUPS_B establishes the parent group, and a foreign key to FND_SECURITY_GROUPS supports multi-org/security-group partitioning. The documented physical schema spans 26 columns, including the standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN), the OBJECT_VERSION_NUMBER for optimistic locking, fifteen ATTRIBUTE columns plus ATTRIBUTE_CATEGORY for extensibility, and SECURITY_GROUP_ID.

Using a heuristic Data Vault classification, this object is best modeled as a satellite-leaning entity: it hangs off the group hub (JTF_RS_GROUPS_B) and records descriptive usage context rather than acting as a pure intersection. It does behave partly like a link because it resolves a many-to-many-style relationship between groups and usages, but the presence of a surrogate key and WHO audit columns favors treating it as a dependent satellite.

Key Information Stored

The most significant columns are:

  • GROUP_USAGE_ID — the surrogate primary key (JTF_RS_GROUP_USAGES_PK); a system-generated identifier for each usage row.
  • GROUP_ID — foreign key to JTF_RS_GROUPS_B; the resource group to which the usage is assigned. Together with USAGE it forms the business key (unique index JTF_RS_GROUP_USAGES_U2).
  • USAGE — the usage value assigned to the group; the second component of the business key.
  • SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS; enforces security-group/operating-unit partitioning.
  • OBJECT_VERSION_NUMBER — supports optimistic locking during concurrent updates.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit (WHO) columns tracking creation and modification.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the flexible DFF/descriptive extensibility fields for customer-defined data.

Practically, GROUP_ID and USAGE drive all functional meaning; the remaining columns are administrative or extensibility-related.

Common Use Cases and Queries

Administrators and developers query this table to determine what usages a given group supports, to validate group configuration, and to drive CRM qualification logic. A typical lookup retrieves all usages for a group:

  • SELECT gu.usage FROM jtf_rs_group_usages gu WHERE gu.group_id = :p_group_id;
  • Reporting on usage distribution: SELECT usage, COUNT(*) FROM jtf_rs_group_usages GROUP BY usage;
  • Joining to the parent group for descriptive reporting: SELECT gb.group_id, gb.name, gu.usage FROM jtf_rs_group_usages gu, jtf_rs_groups_b gb WHERE gu.group_id = gb.group_id;
  • Security-scoped queries filtering by security_group_id in multi-org deployments.

Common scenarios include verifying that a group carries the required usage before it can be selected in a CRM responsibility, auditing configuration drift across environments, and building extracts that map groups to their allowed usages for downstream integration.

Related Objects

The most significant related objects are:

  • JTF_RS_GROUPS_B — the parent resource group table; joined on GROUP_ID. This is the primary dependency for this object.
  • JTF_RS_GROUPS_TL — the translation table for group names, joined on GROUP_ID.
  • JTF_RS_GROUP_MEMBERS — associates individual resources with groups, joined on GROUP_ID, often combined with usages for qualification logic.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security-group partitioning.
  • FND_USER / JTF_RS_RESOURCE_EXTNS — provide the resource and user context when group usages are evaluated in CRM runtime lookups.
  • Public APIs within the JTF Resource Manager layer (such as the group-management APIs) that create, update, or delete group usage assignments programmatically.

Because of the enforced unique constraint on GROUP_ID and USAGE, applications rely on this table as the authoritative source for which usages are active on a group.