Results for “old_related_group_id”

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

Overview

JTF_RS_GRP_RELATE_AUD is an audit table in the JTF (CRM Foundation) schema of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. It stores historical audit information for records held in the group relation entity, capturing before-and-after ("old" and "new") values whenever a group relation row is inserted, updated, or deleted. It is a child of JTF_RS_GRP_RELATIONS, joined through GROUP_RELATE_ID, and is owned by JTF with 20 documented columns.

Under a heuristic Data Vault classification mined from the foreign key structure, this table is satellite-leaning: it functions as an audit/descriptive satellite attached to a parent group-relation record (the implied hub or link), retaining the change history rather than serving as an integrating hub itself. This classification is a modeling suggestion, not a documented Oracle definition.

Key Information Stored

The surrogate primary key is GROUP_RELATE_AUDIT_ID, which is also documented as the unique index JTF_RS_GRP_RELATE_AUD_U1 (business-key candidate). The table's central grouping/business columns include:

• GROUP_RELATE_AUDIT_ID — surrogate primary key uniquely identifying each audit row.
• GROUP_RELATE_ID — foreign key to the parent JTF_RS_GRP_RELATIONS record being audited.
• NEW_GROUP_ID / OLD_GROUP_ID — the new and prior group identifiers on the relation.
• NEW_RELATED_GROUP_ID / OLD_RELATED_GROUP_ID — the new and prior related-group identifiers.
• NEW_START_DATE_ACTIVE / OLD_START_DATE_ACTIVE — new and prior effective start dates.
• NEW_END_DATE_ACTIVE / OLD_END_DATE_ACTIVE — new and prior effective end dates.
• NEW_RELATION_TYPE / OLD_RELATION_TYPE — new and prior relation type values.
• NEW_OBJECT_VERSION_NUMBER / OLD_OBJECT_VERSION_NUMBER — new and prior optimistic-locking version values.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting multi-tenant/security grouping.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording who created and last touched each audit entry.

The paired OLD_/NEW_ column pattern is the defining characteristic of this audit structure, enabling point-in-time reconstruction of changes.

Common Use Cases and Queries

Typical scenarios include change-history reporting, reconciliation, and compliance auditing of group relations. A representative query reconstructs the change set for a parent relation:

• SELECT GROUP_RELATE_AUDIT_ID, GROUP_RELATE_ID, OLD_GROUP_ID, NEW_GROUP_ID, OLD_RELATED_GROUP_ID, NEW_RELATED_GROUP_ID, LAST_UPDATE_DATE FROM JTF_RS_GRP_RELATE_AUD WHERE GROUP_RELATE_ID = :p_relate_id ORDER BY CREATION_DATE;
• Identifying relations whose effective dates or relation type changed, by comparing NEW_RELATION_TYPE against OLD_RELATION_TYPE.
• Filtering audit rows by SECURITY_GROUP_ID to honor row-level security boundaries.
• Joining back to JTF_RS_GRP_RELATIONS on GROUP_RELATE_ID to present current versus historical attributes in a single report.

Related Objects

• JTF_RS_GRP_RELATIONS — parent table referenced via JTF_RS_GRP_RELATE_AUD.GROUP_RELATE_ID; the primary source of audited records.
• FND_SECURITY_GROUPS — referenced via JTF_RS_GRP_RELATE_AUD.SECURITY_GROUP_ID, governing security group assignment.
• Standard WHO/audit concurrency and security infrastructure objects (for example FND_USER) implicitly underpin the CREATED_BY, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN columns.

Together these relationships position JTF_RS_GRP_RELATE_AUD as the historical companion to the live group-relation data in the CRM Foundation module.