Results for “current_user_id”

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

Overview

The view APPS.JTF_TTY_GEO_TERR_OWNER_LOV_V is an Oracle E-Business Suite database object owned by the APPS schema and delivered as part of the JTF (CRM Foundation) product family. It is classified as a VIEW and its documented status is VALID in both EBS 12.1.1 and 12.2.2. Its purpose, per the ETRM metadata, is to serve as a View for owners of Geography Territories — that is, a List of Values (LOV) source that resolves the sales resources authorized to own or administer a given geography territory.

This view is a reporting and integration convenience layer. Rather than requiring a custom SQL statement to join CRM Resource Manager (JTF_RS) and Territory Manager (JTF_TTY) tables, an application or report can query the view and filter by CURRENT_USER_ID to return only the territory owners relevant to the logged-in user. Because it is an LOV-oriented view, consumers typically drive it with a bind or predicate on the current user, giving high selectivity as noted in the view comments.

Underlying Base Objects

The documented base objects referenced by this view are:

• JTF_TTY_GEO_TERR (synonym) — geography territory definitions; source of GEO_TERR_NAME.
• JTF_TTY_TERR_GROUPS (synonym) — the association between territories and resource groups/owners.
• JTF_RS_GROUPS_DENORM, JTF_RS_GROUP_MEMBERS, JTF_RS_GROUP_USAGES, JTF_RS_REP_MANAGERS, JTF_RS_ROLE_RELATIONS, JTF_RS_ROLES_B (synonyms) — Resource Manager group hierarchy, membership, role and manager structures.
• JTF_RS_GROUPS_VL, JTF_RS_RESOURCE_EXTNS_VL, JTF_RS_ROLES_VL (views) — the translated resource, group and role views used for names and IDs.
• FND_PROFILE (package) — profile-option access used by the underlying logic (typically for current-user or security context).

The view joins the resource group hierarchy (manager-to-manager and child groups) to territory groups, producing the distinct set of resource owners. The embedded comment in the view text explains that DISTINCT is applied so duplicate geography territories are not returned when a single person manages two groups.

Key Columns

• RESOURCE_NAME — the name of the sales resource (manager/owner).
• DIR_USER_ID — the FND user identifier of that resource.
• CURRENT_USER_ID — the FND user ID of the currently logged-in user; this is the primary filter column and drives selectivity.
• GEO_TERR_NAME — the geography territory name, the column matched by the user's search term geo_terr_name.

Common Use Cases and Queries

The primary use case is populating an LOV or reporting query that lists geography territory owners for the current user's scope. A representative query is:

SELECT geo_terr_name, resource_name, dir_user_id FROM apps.jtf_tty_geo_terr_owner_lov_v WHERE current_user_id = :p_user_id;

Other scenarios include validating the territory ownership assigned to a salesperson, reconciling territory-to-group assignments during CRM configuration, and driving territory-based security in custom forms or concurrent programs. Because the view already encapsulates the JTF_RS and JTF_TTY join logic, it is preferable to embedding those joins manually and ensures consistent results with the delivered Territory Manager behavior.