Search Results jtf_rs_grp_relations_u1

Overview

JTF.JTF_RS_GRP_RELATIONS is a resource-management table in the Oracle E-Business Suite JTF (Common Technologies / CRM Foundation) schema. It stores relationships between groups defined in the resource manager, most notably hierarchical associations where one group is designated as the parent of another. The table is documented as VALID in ETRM for releases 12.1.1 and 12.2.2 and is owned by the JTF schema under the FND Design Data reference JTF.JTF_RS_GRP_RELATIONS. It resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, while its indexes are held in APPS_TS_TX_IDX.

The primary key is JTF_RS_GRP_RELATIONS_PK, defined on GROUP_RELATE_ID. The documented relation types include 'PARENT_GROUP', where the RELATED_GROUP_ID column carries the parent group identifier. Based on the foreign-key structure — references outward to JTF_RS_GROUPS_B and to FND_SECURITY_GROUPS — the table exhibits a satellite-leaning Data Vault classification, suggesting it is best modeled as a satellite or relationship attribute store attached to the group hub rather than as an independent hub. This is a heuristic modeling suggestion derived from FK topology, not a prescriptive data model.

Key Information Stored

The table comprises 30 documented columns. The most operationally significant are:

• GROUP_RELATE_ID — surrogate primary key and the single column of the unique index JTF_RS_GRP_RELATIONS_U1; serves as the business-key candidate for uniqueness enforcement.
• GROUP_ID — foreign key to JTF.JTF_RS_GROUPS_B; identifies the group on the owning side of the relation.
• RELATED_GROUP_ID — foreign key to JTF.JTF_RS_GROUPS_B; when RELATION_TYPE is 'PARENT_GROUP', this holds the parent group.
• RELATION_TYPE — VARCHAR2(240) discriminator; documented example is 'PARENT_GROUP'.
• START_DATE_ACTIVE and END_DATE_ACTIVE — date-range validity window for the relation.
• DELETE_FLAG — logical delete indicator, supported by non-unique index N3.
• OBJECT_VERSION_NUMBER — sequential locking column used for optimistic concurrency control.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for multi-tenant / data-security partitioning.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE1–ATTRIBUTE15 and ATTRIBUTE_CATEGORY — descriptive flexfield (DFF) segments for customer-extensible data.

The non-unique indexes N1 (GROUP_ID, RELATED_GROUP_ID, RELATION_TYPE) and N2 (RELATED_GROUP_ID, RELATION_TYPE) exist to accelerate hierarchy traversal in both directions.

Common Use Cases and Queries

Typical scenarios include resolving group hierarchies for resource assignment, validating parent-child group structures during group administration, and reporting on effective-dated group membership. A representative query returning active parent groups for a given child group is:

• SELECT related_group_id FROM jtf.jtf_rs_grp_relations WHERE group_id = :child_group AND relation_type = 'PARENT_GROUP' AND delete_flag = 'N' AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);
• Reverse traversal for descendants uses index N2 on RELATED_GROUP_ID and RELATION_TYPE.
• Reporting on logically deleted relations filters on DELETE_FLAG using index N3.

Because the relation is effective-dated, historical reporting must be careful to include START_DATE_ACTIVE and END_DATE_ACTIVE predicates rather than assuming a current-only result set.

Related Objects

The following objects are directly coupled to this table through documented foreign-key or dependency relationships:

• JTF.JTF_RS_GROUPS_B — referenced twice, via GROUP_ID and RELATED_GROUP_ID; the primary join target for both sides of any relation.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; governs row-level security partitioning.
• JTF.JTF_RS_GRP_RELATE_AUD — audit table whose GROUP_RELATE_ID references this table's primary key, capturing change history.

Group hierarchy consumption also typically flows through resource manager APIs and views built on JTF_RS_GROUPS_B, which join to this table to materialize parent-child structures for downstream assignment and security logic.