Results for “lead_flag”

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

Overview

The view JTF_RS_GROUP_MBR_ROLE_VL is an APPS-owned database view within the JTF – CRM Foundation product module of Oracle E-Business Suite, valid in both 12.1.1 and 12.2.2. Its documented purpose is to support the member_roles block of the Define Group form, presenting the roles that have been assigned to individual group members within the Resource Manager group model.

In Oracle EBS, JTF_RS (Resource Manager) underpins resource groups, group members, and role relationships used throughout CRM applications such as TeleSales, Service, and Marketing. This view consolidates member-level role assignments into a single reporting-friendly result set, joining membership records with role definitions and role-to-resource relationships. Because it exposes a denormalized presentation of roles, effective dates, and role capability flags, it is useful for both operational reporting and integration logic that must determine which role a given group member holds, over what period, and with what privileges.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over three underlying objects:

• JTF_RS_GROUP_MEMBERS (SYNONYM) — the group membership table, aliased as MEM, supplying GROUP_MEMBER_ID, RESOURCE_ID, and GROUP_ID.
• JTF_RS_ROLE_RELATIONS (SYNONYM) — the role relationship table, aliased as RRL, supplying START_DATE_ACTIVE, END_DATE_ACTIVE, ROLE_RELATE_ID, and the ROLE_RESOURCE_TYPE / ROLE_RESOURCE_ID linkage.
• JTF_RS_ROLES_VL (VIEW) — the translated role definition view, aliased as ROL, supplying ROLE_ID, ROLE_NAME, ROLE_DESC, and the role capability flags.

The join conditions connect a member to its role relations via MEM.GROUP_MEMBER_ID = RRL.ROLE_RESOURCE_ID, restrict relations to RRL.ROLE_RESOURCE_TYPE = 'RS_GROUP_MEMBER', and link roles by RRL.ROLE_ID = ROL.ROLE_ID. Both the member and role relation records are filtered to exclude soft-deleted rows using NVL(...DELETE_FLAG, 'N') <> 'Y', ensuring the view returns only active assignments.

Key Columns

• GROUP_MEMBER_ID — identifier of the group membership record; the anchor of the assignment.
• RESOURCE_ID — the resource (person or resource) that is a member of the group.
• GROUP_ID — the resource group to which the member belongs.
• ROLE_ID / ROLE_NAME / ROLE_DESC — the role assigned to the member and its translated name and description.
• MEMBER_FLAG, ADMIN_FLAG, MANAGER_FLAG, LEAD_FLAG — role capability indicators describing the nature of the role (member, administrator, manager, lead).
• START_DATE_ACTIVE, END_DATE_ACTIVE — the effective period during which the role relationship is active.
• ROLE_RELATE_ID — the primary key of the underlying role relation record, useful for auditing and deduplication.

Common Use Cases and Queries

Typical uses include identifying which roles a member holds within a group, reporting active role assignments against current dates, and determining members holding administrative or lead privileges within a group. A representative query is:

SELECT group_id, resource_id, role_name, manager_flag, start_date_active, end_date_active
FROM apps.jtf_rs_group_mbr_role_vl
WHERE group_id = :p_group_id
AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

For integration or reconciliation, the view can similarly be queried by RESOURCE_ID to list every group and role combination assigned to a given resource, or joined back to JTF_RS_ROLE_RELATIONS on ROLE_RELATE_ID for transactional detail.