Search Results current_user_id




Overview
Explore in AI Chat

Overview

APPS.JTF_TTY_SRCH_MY_RESOURCES_V is a CRM Foundation (JTF) view used by the Telephony / Territory Management ("TTY") search infrastructure in Oracle E-Business Suite 12.1.1 and 12.2.2. It resolves the set of resources that the currently logged-in user is authorized to search, administer, or act upon as a sales manager, group administrator, or delegated proxy. The view is therefore central to "My Resources" style searches in the Telephony toolbar and related Resource Manager screens, where an agent or manager must be constrained to only those sales resources within their hierarchy.

The defining characteristic of the view is its use of CURRENT_USER_ID. This column is populated from mrsc.user_id (the resource extension row for the logged-in user) in the manager branch, and from dir.user_id in the base salesperson branch. External code and LOV queries frequently filter on this column to scope results to the session user, which explains why current_user_id is a common search term associated with this object.

Underlying Base Objects

The view is defined over the following documented base objects:

The body is a UNION ALL of a manager-oriented inline view (MY_GRPS) and a base salesperson branch, so a single row may represent either an administrated group or a directly owned sales group.

Key Columns

  • RESOURCE_ID — the resource belonging to the group, drawn from jtf_rs_resource_extns_vl.
  • GROUP_ID — the sales group through which the resource is reached.
  • ROLE_CODE — the role that grants visibility (for example, manager or member roles).
  • CURRENT_USER_ID — the user_id of the session user, used to constrain results to the logged-in individual.

Common Use Cases and Queries

Typical usages include driving "My Resources" LOVs, restricting telephony searches to a manager's subordinate resources, and validating whether a group is administered by the current user.

SELECT resource_id, group_id, role_code
FROM   apps.jtf_tty_srch_my_resources_v
WHERE  current_user_id = fnd_global.user_id;

Because the view already encodes hierarchy and role membership logic, callers should avoid re-deriving those relationships and should filter on CURRENT_USER_ID to enforce session scoping.