Search Results jtf_rs_groups_aud_b




Overview
Explore in AI Chat

Overview

JTF_RS_GROUPS_AUD_B is the base audit table in the JTF (CRM Foundation) schema of Oracle E-Business Suite, storing historical change records for resource groups maintained by the Resource Manager (JTF_RS) module. Every time an attribute of a group defined in JTF_RS_GROUPS_B is modified, the prior and resulting values are captured as OLD and NEW column pairs in this table, producing a full chronological audit trail. The object is owned by the JTF schema, is documented as VALID in both release 12.1.1 and 12.2.2, and is composed of 24 columns in the ETRM physical schema.

From a Data Vault modeling perspective, the FK structure suggests that JTF_RS_GROUPS_AUD_B behaves as a satellite rather than a hub or link. Its primary key, GROUP_AUDIT_ID, is purely a surrogate audit-record identifier with no independent business meaning, while the meaningful parent key SET (GROUP_ID → JTF_RS_GROUPS_B, SECURITY_GROUP_ID → FND_SECURITY_GROUPS) points outward to existing entities. This is characteristic of descriptive satellite history applied to a group hub.

Key Information Stored

The table captures attribute-level audit pairs. The most significant columns are:

Because every functional attribute is represented as a NEW/OLD pair, a single row is typically populated with a value in either the NEW or OLD side depending on whether the operation was an insert, update, or delete.

Common Use Cases and Queries

The table is primarily consumed for audit reporting, compliance, and troubleshooting "who changed what, when." Typical queries join back to the live group table and to FND_USER via the WHO columns:

  • Reconstructing the change history of a specific group: SELECT * FROM JTF_RS_GROUPS_AUD_B WHERE group_id = :p_group_id ORDER BY creation_date DESC;
  • Reporting changes within a date range for SOX or internal audit evidence: SELECT group_id, new_group_number, old_group_number, created_by, creation_date FROM JTF_RS_GROUPS_AUD_B WHERE creation_date BETWEEN :start_date AND :end_date;
  • Identifying which user performed a change: SELECT a.group_id, a.created_by, u.user_name FROM JTF_RS_GROUPS_AUD_B a, FND_USER u WHERE a.created_by = u.user_id;
  • Fetching translated descriptions of an audit row via JTF_RS_GROUPS_AUD_TL on GROUP_AUDIT_ID.
  • Cross-checking active-date or exclusive-flag edits by comparing OLD and NEW columns.

These patterns are commonly embedded in custom concurrent programs, OAF-based audit discovery pages, and BI Publisher extracts.

Related Objects

  • JTF_RS_GROUPS_B — the base (non-translatable) group table; joined on JTF_RS_GROUPS_AUD_B.GROUP_ID = JTF_RS_GROUPS_B.GROUP_ID.
  • JTF_RS_GROUPS_AUD_TL — the translation table for audit rows; references JTF_RS_GROUPS_AUD_B via GROUP_AUDIT_ID.
  • JTF_RS_GROUPS_TL — translation companion for the base group table, relevant when resolving names for reported audit records.
  • FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID, controlling data visibility.
  • FND_USER — resolved through CREATED_BY / LAST_UPDATED_BY for operator attribution.
  • FND_LOGINS — optionally joined on LAST_UPDATE_LOGIN for session-level tracing.
  • Resource Manager APIs (JTF_RS_GROUPS_PUB / JTF_RS_GROUP_UTIL) — the DML entry points whose changes are captured here.

Together these objects form the audit lineage for CRM resource groups, with JTF_RS_GROUPS_AUD_B acting as the central satellite fact of the group history.