Search Results logged_resource_in




Overview

APPS.JTF_TASK_SECURITY_V is a security-resolution view in the Oracle E-Business Suite CRM Foundation (JTF) schema that consolidates the effective task access assignments for the currently authenticated user. Rather than storing rows itself, the view is a runtime union that derives one row per security principal through which the logged-in user obtains access to task and resource data. In releases 12.1.1 and 12.2.2 the view is a core component of the Oracle Task Manager security model, feeding the access predicates used by task, calendar, and resource reporting. Its most frequently referenced attribute is the literal privilege value JTF_TASK_FULL_ACCESS, which appears in every branch of the UNION ALL and signals that the row represents full-access entitlement rather than a restricted grant. The view is owned by APPS and is therefore normally queried without an owner prefix in custom reports and integrations.

Because the view resolves identities from session context (notably FND_GLOBAL.USER_ID), its result set is user-specific and changes at runtime. This makes it suitable for embedded security filters in concurrent programs, OAF pages, and BI Publisher data models, but unsuitable as a static staging source.

Underlying Base Objects

The view is defined as a four-branch UNION ALL over the following documented objects:

All of the above are referenced as APPS synonyms in the ETRM metadata, so the view presents a unified security surface across the Resource Manager tables and thefunction security tables.

Key Columns

  • RS_ID — the identifier of the security principal (group, resource, team, or instance key from FND_GRANTS).
  • RS_TYPE — the principal category: 'RS_GROUP', 'RS_TEAM', the concatenated 'RS_'||CATEGORY value, or the function name from FND_FORM_FUNCTIONS for grant-derived rows.
  • PRIVELEGE — the privilege granted. All four branches emit the literal 'JTF_TASK_FULL_ACCESS', which is the term users typically search for.
  • LOGGED_RESOURCE_IN — the resource identifier of the currently logged-in user within the security context, expressed as a character value for the resource branches and as GRANTEE_KEY for the grant branch.

Common Use Cases and Queries

The view is most commonly used to determine which resources, groups, and teams the session user may act upon when listing or updating tasks. A representative unrestricted query is:

  • SELECT rs_id, rs_type, privelege, logged_resource_in FROM apps.jtf_task_security_v;

To confirm whether a specific privilege is present for the current user:

  • SELECT COUNT(*) FROM apps.jtf_task_security_v WHERE privelege = 'JTF_TASK_FULL_ACCESS';

To isolate team-based entitlements only:

  • SELECT rs_id, logged_resource_in FROM apps.jtf_task_security_v WHERE rs_type = 'RS_TEAM';

Because the view references FND_GLOBAL.USER_ID, queries must be executed in a session where FND_GLOBAL has been initialized; running it as a plain schema user without an EBS session returns an empty result set. Integrations should therefore invoke it from within an authenticated EBS context, such as a concurrent program or an OA Framework page, and should not persist its output as a materialized access list, since entitlement changes and session identity changes are reflected only at query time.