Results for “role_relate_id”

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

Overview

The JTF_RS_ROLE_RELATIONS_VL view is a CRM Foundation (JTF) dictionary object owned by the APPS schema and shipped with Oracle E-Business Suite 12.1.1 and 12.2.2. It presents the relationships that associate Oracle CRM resource roles with resources — that is, the assignments that determine which role a given resource holds, together with the role's attributes and the effective date range of the assignment. In ETRM the object is documented as a VIEW with status VALID, and its description states that it "shows the listing of details of roles attached to resource."

Because the underlying tables JTF_RS_ROLE_RELATIONS and JTF_RS_ROLES are not exposed as clean, self-describing entities, this view serves as the canonical reporting and integration surface for role-to-resource assignments. Its name suffix _VL indicates it is a "value list" style view that internally joins translated lookup and role definitions so that consumers receive meaningful names and flags rather than raw codes. Report writers, concurrent programs, personalizations, and inbound/outbound interfaces that must resolve "who holds which role" against CRM resources consistently query this view instead of joining the base tables directly.

Underlying Base Objects

Per the ETRM 12.2.2 metadata, the view is defined over three referenced base objects:

• JTF_RS_ROLE_RELATIONS (referenced in the ETRM object list as a SYNONYM; the transactional base table holding one row per role assignment, including the role relate ID, resource type and ID, active date range, and delete flag).
• JTF_RS_ROLES_VL (the role definition view supplying ROLE_NAME, ROLE_CODE, ROLE_TYPE_CODE, and the member/admin/lead/manager flags).
• FND_LOOKUPS (the lookup view supplying the translated MEANING for the role type code from lookup type JTF_RS_ROLE_TYPE).

FND_GLOBAL (PACKAGE) is also listed as a referenced object, which is typical of JTF views that apply the Multi-Org / security context and current user or responsibility attributes at runtime. The view's defining text joins the three base objects, restricts rows with NVL(RRT.DELETE_FLAG,'N') <> 'Y', and equates RRT.ROLE_ID = ROL.ROLE_ID and ROL.ROLE_TYPE_CODE = FND.LOOKUP_CODE where FND.LOOKUP_TYPE = 'JTF_RS_ROLE_TYPE'. As a result the view is effectively a read-only, logically-deleted-filtered projection over the role relations table.

Key Columns

• ROLE_RELATE_ID — Primary key of the underlying relation row; uniquely identifies a resource/role assignment.
• ROLE_RESOURCE_TYPE and ROLE_RESOURCE_ID — Identify the party (e.g., resource, group, or user) to which the role is attached.
• ROLE_ID — Foreign key to JTF_RS_ROLES; links the relation to its role definition.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating of the assignment.
• ROLE_NAME, ROLE_CODE, ROLE_TYPE_CODE, and MEANING — Descriptive attributes of the role, with MEANING being the translated lookup value for the role type.
• MEMBER_FLAG, ADMIN_FLAG, LEAD_FLAG, MANAGER_FLAG — Behavioral indicators describing how the resource participates in the role.

Common Use Cases and Queries

Typical scenarios include auditing role assignments per resource, filtering active roles by date, and resolving role type descriptions for reporting. For example:

SELECT role_relate_id, role_resource_id, role_name, meaning,
      start_date_active, end_date_active
 FROM apps.jtf_rs_role_relations_vl
 WHERE role_resource_id = :p_resource_id
   AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE)
                AND NVL(end_date_active, SYSDATE);

Analysts also group by MEANING or ROLE_TYPE_CODE to produce role inventories, and check the *_FLAG columns to isolate administrative, lead, or manager assignments. Because the view hides the deleted rows and performs the lookup translation, it is preferred over direct queries against JTF_RS_ROLE_RELATIONS for any reporting or interface requirement.