Search Results jtf_task_security_v




Overview

JTF_TASK_SECURITY_V is a VALID database view owned by the APPS schema in Oracle E-Business Suite, belonging to the JTF — CRM Foundation product family. Its documented purpose is to resolve the security model governing access to tasks and resources: it returns the group or team resources that grant full access to a given login resource, together with group, team, or employee resources that grant a defined level of access to that login resource. In effect, the view consolidates membership and grant information into a single, query-friendly projection that maps a logged-in resource to the privileges that resource holds.

Because the view encodes the security resolution logic rather than requiring callers to reimplement it, it plays a central role in CRM Foundation reporting and integration. Downstream components, concurrent programs, and custom reports can join the view to task or resource data without duplicating the complex UNION logic that combines resource group membership, resource extension attributes, team membership, and menu-based function grants. In EBS 12.1.1 and 12.2.2 the view remains available in the APPS schema and is referenced by synonym from the JTF application code.

Underlying Base Objects

The ETRM metadata for 12.2.2 lists the referenced base objects as synonyms resolved through APPS: FND_FORM_FUNCTIONS, FND_GRANTS, FND_MENUS, FND_MENU_ENTRIES, FND_OBJECTS, JTF_RS_GROUP_MEMBERS, JTF_RS_RESOURCE_EXTNS, and JTF_RS_TEAM_MEMBERS, with FND_GLOBAL referenced as a package.

The view definition is a four-branch UNION ALL. The first branch selects GROUP_ID from JTF_RS_GROUP_MEMBERS, tagging rows as RS_GROUP and granting the privilege JTF_TASK_FULL_ACCESS. The second branch selects RESOURCE_ID and a derived category from JTF_RS_RESOURCE_EXTNS, restricted by USER_ID = FND_GLOBAL.USER_ID, so it resolves the currently logged-in user via the FND_GLOBAL session context. The third branch draws TEAM_ID and TEAM_RESOURCE_ID from JTF_RS_TEAM_MEMBERS, again flagging JTF_TASK_FULL_ACCESS. The fourth branch joins FND_FORM_FUNCTIONS, FND_MENU_ENTRIES, FND_MENUS, FND_GRANTS, and FND_OBJECTS, filtering where OBJ_NAME = 'JTF_TASK_RESOURCE', and derives the resource identifier from FG.INSTANCE_PK1_VALUE with the privilege name taken from FFF.FUNCTION_NAME.

Key Columns

  • RS_ID — the resource identifier granting access; sourced from GROUP_ID, RESOURCE_ID, TEAM_ID, or the converted INSTANCE_PK1_VALUE depending on the UNION branch.
  • RS_TYPE — the type of the granting resource, such as the literal RS_GROUP, RS_TEAM, or a concatenation of 'RS_' with the resource category from JTF_RS_RESOURCE_EXTNS.
  • PRIVELEGE — the privilege granted, either the literal JTF_TASK_FULL_ACCESS or the function name obtained from FND_FORM_FUNCTIONS.
  • LOGGED_RESOURCE_IN — the logged-in resource the grant applies to, stored as a character representation of the resource identifier or the grantee key.

Common Use Cases and Queries

Typical scenarios include auditing which groups, teams, or employees hold full access over CRM tasks, validating menu-driven function grants, and driving row-level security in custom CRM reports. A representative query listing full-access grants is:

  • SELECT rs_id, rs_type, privelege, logged_resource_in FROM apps.jtf_task_security_v WHERE privelege = 'JTF_TASK_FULL_ACCESS';
  • SELECT rs_id, rs_type FROM apps.jtf_task_security_v WHERE rs_type = 'RS_TEAM';
  • SELECT logged_resource_in, COUNT(*) FROM apps.jtf_task_security_v GROUP BY logged_resource_in;

Because the second branch depends on FND_GLOBAL.USER_ID, results are session-sensitive; queries run outside an authenticated EBS session may return only the group, team, and menu-grant branches.