Search Results jtf_rs_dbi_mgr_groups




Overview
Explore in AI Chat

Overview

JTF_RS_DBI_MGR_GROUPS is a CRM Foundation (JTF) table in the Oracle E-Business Suite resource management schema. It functions as an association table that links a resource (or the user identity acting on behalf of a resource) to a manager group, establishing the membership relationship used by the Resource Manager and its Delegated Business Intelligence (DBI) grouping model. In practical terms, the table answers which resources belong to which manager group and, through the USAGE column, the capacity in which that membership applies. This is foundational data for resource hierarchy navigation, group-based access to resources, and reporting scopes that depend on a manager's span of control.

Heuristic Data Vault classification, mined from the foreign key structure, indicates a standalone object. From a modeling perspective, this suggests the table is best treated as a link-style association resolving two business entities — a resource/user and a group — rather than as a pure hub or satellite. Because no downstream foreign keys reference it, it behaves as a leaf association table.

Key Information Stored

The table is documented with ten columns. The most significant are:

  • DBI_MGR_ID — the surrogate primary key for each membership row; it uniquely identifies a given resource-to-group assignment.
  • RESOURCE_ID — the resource (typically an employee, partner, or party resource) whose group membership is defined. This is a key business identifier joining to the resource tables.
  • USER_ID — the application user associated with the membership, allowing the group assignment to be tied to a login identity rather than only to a resource record.
  • GROUP_ID — the manager group to which the resource or user belongs; the target of the association.
  • USAGE — a discriminator describing the purpose or context in which the membership is applied.
  • SECURITY_GROUP_ID — a foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant security group isolation across the row.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — the standard EBS audit WHO columns recording insert and update provenance.

The documented foreign key constraint identifies SECURITY_GROUP_ID as the sole incoming reference, pointing to FND_SECURITY_GROUPS. RESOURCE_ID, USER_ID, and GROUP_ID function as business-key candidates even though no unique index is documented; they carry the semantic identity of the row, while DBI_MGR_ID serves as the technical surrogate key.

Common Use Cases and Queries

Typical usage centers on determining group membership for a resource or revealing all members of a manager group. A representative query enumerates a group's members:

  • SELECT resource_id, user_id, usage FROM jtf_rs_dbi_mgr_groups WHERE group_id = :group_id;
  • SELECT group_id, usage FROM jtf_rs_dbi_mgr_groups WHERE resource_id = :resource_id;
  • Security-scoped extraction joining to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to limit results to the caller's security group.
  • Audit and data-quality reports comparing CREATION_DATE against LAST_UPDATE_DATE to detect recently modified memberships.

Reporting use cases include resource-utilization dashboards, manager span-of-control analysis, and CRM application logic that resolves which resources are visible to a given manager group. Because membership drives visibility, queries here are frequently embedded in views and concurrent programs rather than run ad hoc.

Related Objects

The following objects most directly interact with JTF_RS_DBI_MGR_GROUPS:

  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; enforces row-level security group isolation.
  • JTF_RS_RESOURCE_EXTNS / JTF_RS_RESOURCE_VL — join on RESOURCE_ID to resolve resource names and attributes.
  • FND_USER — join on USER_ID to resolve the login identity of a membership.
  • JTF_RS_GROUPS_VL / JTF_RS_GROUP_MEMBERS — related CRM Foundation grouping structures that complement manager-group membership.
  • JTF_RS_DBI_MGR_GROUPS reporting views and the Resource Manager APIs (JTF_RS_RESOURCE_PUB and group-related public packages) that create and maintain memberships.

Because the table is standalone with no outgoing references other than the security group, join logic flows primarily outward to the resource, user, and group masters.