Results for “jtf_rs_chgd_role_relations”

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

Overview

The JTF_RS_CHGD_ROLE_RELATIONS table is a CRM Foundation (JTF) data object within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores relationship hierarchies between groups (roles) managed by the Resource Manager, capturing which groups are related to one another and the nature of that relationship. Structurally it mirrors JTF_RS_GRP_RELATIONS, with the significant addition of an OPERATION_FLAG column used to track the operation performed on a given relationship record during concurrent or staged processing. The table is classified as VALID and owned by the JTF schema.

From a Data Vault modeling perspective, the supplied metadata classifies this object as standalone. That is a heuristic suggestion rather than a prescriptive design: the object behaves largely as a link-like structure joining a role resource to a related role, with descriptive attributes (active dates, delete/operation flags) that would typically be modeled as satellites in a Data Vault implementation. Analysts should treat the classification as a starting point and validate it against actual query and ETL patterns.

Key Information Stored

The documented physical schema contains 14 columns. The most significant are:

• ROLE_RELATE_ID — the surrogate primary key, enforced by the JTF_RS_CHGD_ROLE_RELATIONS_PK constraint. This is the column referenced by the user search term "role_relate_id."
• ROLE_RESOURCE_TYPE and ROLE_RESOURCE_ID — identify the resource (typically a group or role) whose relationship is being recorded.
• ROLE_ID — identifies the role being related, i.e., the counterpart in the group-to-group relationship. Together with ROLE_RESOURCE_ID this defines the business association.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the date range during which the relationship is effective, supporting date-tracked hierarchy queries.
• DELETE_FLAG and OPERATION_FLAG — soft-delete and operation indicators distinguishing this table from its JTF_RS_GRP_RELATIONS counterpart.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• SECURITY_GROUP_ID — the multi-tenant security grouping column, referencing FND_SECURITY_GROUPS.

The documented metadata does not identify any unique index other than the primary key, so ROLE_RELATE_ID should be treated as the sole surrogate key, with the (ROLE_RESOURCE_TYPE, ROLE_RESOURCE_ID, ROLE_ID) combination serving as a plausible business-key candidate for validation.

Common Use Cases and Queries

Typical usage centers on resolving group hierarchies for reporting and access resolution. A common pattern resolves all related roles for a given resource:

SELECT role_id, role_resource_id, start_date_active, end_date_active
FROM jtf_rs_chgd_role_relations
WHERE role_resource_id = :resource_id
AND NVL(delete_flag, 'N') = 'N'
AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE);

Administrators and developers also use this table to audit which relationships were added, changed, or removed, leveraging OPERATION_FLAG. Extracts feeding downstream CRM or security models frequently join it to the role and group lookup tables to produce a flattened hierarchy view.

Related Objects

• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID; join on security_group_id.
• JTF_RS_GRP_RELATIONS — the structurally similar predecessor table without OPERATION_FLAG; useful for comparison and migration analysis.
• JTF_RS_GROUPS_VL / JTF_RS_GROUPS_B — provide descriptive attributes for the roles referenced by ROLE_ID and ROLE_RESOURCE_ID.
• JTF_RS_ROLES_B / JTF_RS_ROLES_TL — supply role names and translations for reporting.
• JTF_RS_RESOURCE_EXTNS — links role resource identifiers to broader resource attributes.

These objects are the primary join targets when reconstructing group hierarchies or rendering role-relationship reports from JTF_RS_CHGD_ROLE_RELATIONS.