Results for “new_group_id”

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

Overview

JTF_RS_GROUP_MEMBERS_AUD is an audit (history) table in the JTF — CRM Foundation product schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It records change history for records held in JTF_RS_GROUP_MEMBERS, which defines the membership of resources and persons within resource groups used throughout CRM and resource-management flows. Each row captures a before-and-after image of a single membership record at the point of an insert, update, or delete, allowing the application to reconstruct who belonged to which group, when the change occurred, and which user performed it.

The table is owned by the JTF schema and is documented as VALID in ETRM. Its stated purpose is to store audit information for group members. Because only current values live in JTF_RS_GROUP_MEMBERS, this audit table is the authoritative source for historical membership state and is the object to query whenever point-in-time or change-tracking reporting on group membership is required.

From a Data Vault modeling perspective, the mined foreign-key structure suggests a satellite-leaning classification. The table is keyed on its own audit identifier and carries descriptive, time-stamped changes plus foreign references to the parent membership and to security groups, which is characteristic of a satellite attached to a business key rather than an independent hub or a pure link.

Key Information Stored

The table contains 16 documented columns. The most important are grouped below.

• GROUP_MEMBER_AUDIT_ID — the surrogate primary key, enforced by JTF_RS_GROUP_MEMBERS_AUD_PK and also backed by the unique index JTF_RS_GROUP_MEMBERS_AUD_U1. This is the audit row identifier, not a business key of the membership itself.
• GROUP_MEMBER_ID — foreign key to JTF_RS_GROUP_MEMBERS, tying the audit row back to the membership record whose lifecycle is being tracked.
• NEW_GROUP_ID / OLD_GROUP_ID — the group to which the member was assigned after and before the change.
• NEW_RESOURCE_ID / OLD_RESOURCE_ID — the resource identifier after and before the change, supporting resource-based membership.
• NEW_PERSON_ID / OLD_PERSON_ID — the person identifier after and before the change, supporting person-based membership.
• NEW_OBJECT_VERSION_NUMBER / OLD_OBJECT_VERSION_NUMBER — optimistic locking version values before and after, useful for detecting concurrent modifications.
• CREATED_BY, CREATION_DATE — who created the audit row and when.
• LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO columns recording the last modifying user, timestamp, and login session.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing multi-org/security-group data isolation.

Common Use Cases and Queries

The primary use case is auditing: reconstructing the membership of a group at a past date, or listing every change made to a membership record. A typical pattern joins the audit table to its parent:

SELECT a.group_member_audit_id, a.group_member_id,
       a.old_group_id, a.new_group_id,
       a.old_resource_id, a.new_resource_id,
       a.last_updated_by, a.last_update_date
FROM   jtf.jtf_rs_group_members_aud a
WHERE  a.group_member_id = :p_group_member_id
ORDER  BY a.last_update_date;

A second pattern filters on the change timestamp to produce a point-in-time or change-log report for a period, typically constrained by SECURITY_GROUP_ID to respect access control. A third pattern compares OLD_ and NEW_ values to classify the change as re-assignment (group change), resource swap, or person swap. Reporting tools such as Oracle BI Publisher and custom concurrent programs consume these queries for compliance and membership-history extracts.

Related Objects

• JTF_RS_GROUP_MEMBERS — the parent membership table; joined on JTF_RS_GROUP_MEMBERS_AUD.GROUP_MEMBER_ID = JTF_RS_GROUP_MEMBERS.GROUP_MEMBER_ID (documented foreign key).
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for data security.
• JTF_RS_GROUPS_VL / JTF_RS_GROUPS_B — group definition tables resolved through the OLD_GROUP_ID and NEW_GROUP_ID values.
• JTF_RS_RESOURCE_EXTNS / PER_ALL_PEOPLE_F — resource and person sources resolved through the OLD/NEW resource and person identifiers.
• JTF_RS_GROUP_MEMBERS_AUD_PK / _U1 — primary key constraint and unique index governing the audit key.
• JTF_RS_GROUPS_API and JTF_RS_GROUP_MEMBERS_API — public APIs that drive membership changes and therefore generate audit rows.