Results for “jtf_rs_active_grp_mbrs_pk”

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

Overview

The JTF.JTF_RS_ACTIVE_GRP_MBRS table is a CRM Foundation (JTF) data object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores active group membership details for resources managed by the Resource Manager (JTF_RS) schema family. The table functions as a denormalized or filtered counterpart to JTF_RS_GROUP_MEMBERS, retaining only those membership records currently in an active state. This design supports runtime lookups of currently valid group membership without requiring status filtering against the full membership base.

The object is owned by the JTF schema and is marked VALID in both release levels cited. It comprises eleven documented columns and is bound by the primary key constraint JTF_RS_ACTIVE_GRP_MBRS_PK on GROUP_MEMBER_ID. Under the heuristic Data Vault classification mined from its foreign key structure, this table is classified as a link. This classification reflects its role as an associative object joining groups, resources, and membership records, rather than acting as a standalone hub or a descriptive satellite.

Key Information Stored

The most significant columns capture the identity of each active membership and its audit context:

• GROUP_MEMBER_ID — surrogate primary key and the column behind both the PK constraint and the unique index JTF_RS_ACTIVE_GRP_MBRS_U1, making it the business-key candidate for row uniqueness.
• GROUP_ID — identifies the parent group; foreign key to JTF_RS_GROUPS_B.
• RESOURCE_ID — identifies the member resource; foreign key to JTF_RS_RESOURCE_EXTNS.
• PERSON_ID — the person associated with the membership where the member is a person rather than a generic resource.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/Multi-Org Access Control (MOAC) visibility.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework (OAF) and PL/SQL APIs.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard "Who" audit columns populated by EBS concurrent and form processing.

The distinction between the surrogate key (GROUP_MEMBER_ID) and the business-key candidate is central: the unique index on GROUP_MEMBER_ID confirms each active membership row is uniquely identified by that single column in the shipped data model.

Common Use Cases and Queries

The table is typically queried to resolve current membership for assignment, escalation, and access-control logic. Representative patterns include:

• Listing active members of a group: SELECT RESOURCE_ID FROM JTF_RS_ACTIVE_GRP_MBRS WHERE GROUP_ID = :group_id.
• Determining whether a resource belongs to any active group: SELECT GROUP_ID FROM JTF_RS_ACTIVE_GRP_MBRS WHERE RESOURCE_ID = :resource_id.
• Joining to JTF_RS_GROUPS_B for group names and to JTF_RS_RESOURCE_EXTNS for resource attributes when building reporting views.
• Enforcing security context by always constraining on SECURITY_GROUP_ID in multi-org deployments.

Because the table holds only active records, consumers avoid the status predicates required when querying JTF_RS_GROUP_MEMBERS directly.

Related Objects

Foreign key relationships establish the primary dependencies:

• JTF_RS_GROUP_MEMBERS — joined on GROUP_MEMBER_ID; the source of membership records.
• JTF_RS_GROUPS_B — joined on GROUP_ID; provides group definitions.
• JTF_RS_RESOURCE_EXTNS — joined on RESOURCE_ID; supplies resource details.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs MOAC visibility.

These relationships define the object's associative role and its integration points across CRM Foundation and common EBS security infrastructure.