Search Results jtf_rs_grp_relations_pk

Overview

JTF_RS_GRP_RELATIONS is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores hierarchical and associative relationships between resource groups defined in the Resource Manager schema. The table's documented purpose is to persist the links between groups, with RELATION_TYPE describing the nature of the association; the ETRM metadata cites 'PARENT_GROUP' as a representative value, indicating that group-to-group hierarchy is the primary modeled relationship. The table is owned by the JTF schema and is classified as VALID in the documented release.

The primary key is GROUP_RELATE_ID, enforced by the index and constraint JTF_RS_GRP_RELATIONS_PK. A unique index, JTF_RS_GRP_RELATIONS_U1, also exists on GROUP_RELATE_ID, making that column both the surrogate key and the documented business-key candidate. Under the heuristic Data Vault classification supplied in the metadata, the table is characterized as satellite-leaning: the foreign keys to JTF_RS_GROUPS_B and FND_SECURITY_GROUPS anchor it to external hubs, while the relationship attributes it carries behave like descriptive satellite payload rather than a pure many-to-many link.

Key Information Stored

The documented physical schema contains 30 columns. The most consequential are:

• GROUP_RELATE_ID — surrogate primary key and the unique-index column; the sole row identifier.
• GROUP_ID — foreign key to JTF_RS_GROUPS_B identifying the owning (subject) group in the relationship.
• RELATED_GROUP_ID — foreign key to JTF_RS_GROUPS_B identifying the counterpart group, typically the parent when RELATION_TYPE is 'PARENT_GROUP'.
• RELATION_TYPE — discriminator describing the semantics of the link between the two groups.
• START_DATE_ACTIVE and END_DATE_ACTIVE — effective-dating window controlling when the relationship is in force.
• DELETE_FLAG — soft-delete indicator used instead of physical row removal.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework during concurrent updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS supporting multi-tenant / operating-unit style data segregation.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) storage block.

Both group references are drawn from the same parent table, JTF_RS_GROUPS_B, so every row records a self-referencing association between two group records.

Common Use Cases and Queries

The table is consulted whenever group hierarchy must be resolved — for example, to determine the parent group of a sales or service resource group, to expand a group tree for reporting or territory roll-up, or to evaluate effective-dated relationships as of a given date. A typical hierarchy query resolves the parent group name:

• SELECT r.GROUP_RELATE_ID, r.GROUP_ID, r.RELATED_GROUP_ID, r.RELATION_TYPE FROM JTF_RS_GRP_RELATIONS r WHERE r.GROUP_ID = :group_id AND r.RELATION_TYPE = 'PARENT_GROUP' AND SYSDATE BETWEEN r.START_DATE_ACTIVE AND NVL(r.END_DATE_ACTIVE, SYSDATE + 1) AND NVL(r.DELETE_FLAG, 'N') = 'N';
• Join back to JTF_RS_GROUPS_B on both GROUP_ID and RELATED_GROUP_ID to display group names side by side.
• Filter on SECURITY_GROUP_ID when reports must respect data segregation.

Common reporting scenarios include active group hierarchy listings, orphaned-group detection (groups with no parent row), and audit comparisons against the history table JTF_RS_GRP_RELATE_AUD.

Related Objects

The most significant dependencies and joins are:

• JTF_RS_GROUPS_B — referenced twice, via GROUP_ID and RELATED_GROUP_ID; the definitive parent of every group referenced here.
• JTF_RS_GRP_RELATE_AUD — audit/history table keyed by GROUP_RELATE_ID, populated on changes to this table and used for change tracking.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security segmentation.
• JTF_RS_GRP_RELATIONS_PK / JTF_RS_GRP_RELATIONS_U1 — primary key constraint and unique index on GROUP_RELATE_ID.

Together these objects form the group-hierarchy backbone of the CRM Resource Manager data model.