Search Results jtf_tty_all_resources_v




Overview
Explore in AI Chat

Overview

JTF_TTY_ALL_RESOURCES_V is an APPS-owned database view within the JTF – CRM Foundation product family. It consolidates resource, group, and role information into a single denormalized result set intended to answer the question of which telesales, sales, or field sales agents belong to which resource groups under which role. The view is commonly used in Oracle E-Business Suite 12.1.1 and 12.2.2 reporting, CRM integration, and concurrent program extraction where a flattened, role-aware directory of resources is required.

The role_code column surfaced in this view is a frequent search target because it allows report developers and integration architects to filter resources by a specific CRM role, such as a telesales agent role, rather than querying multiple related tables directly. Because the view already joins resource, group, group membership, and role tables, it eliminates the need for consumers to reconstruct the CRM resource model manually.

Underlying Base Objects

The view is defined over four documented base views, all within the JTF resource (JTF_RS) schema family:

  • JTF_RS_RESOURCE_EXTNS_VL — provides the resource name, resource ID, and effective date range for each resource.
  • JTF_RS_GROUPS_VL — provides the group name and group ID used to organize resources.
  • JTF_RS_ROLES_VL — provides the role name, role code, role type, active flag, and manager flag, and is the source of the ROLE_CODE column.
  • JTF_RS_GROUP_MBR_ROLE_VL — the bridging object that links resources and roles to their groups, and supplies the effective date range for the membership-role relationship.

The joins enforce date-effectivity via SYSDATE BETWEEN ... AND NVL(...) clauses on the resource and group membership records, and restrict the result set to roles whose ROLE_TYPE_CODE is SALES, TELESALES, or FIELDSALES and whose ACTIVE_FLAG is 'Y'. This makes the view a point-in-time snapshot of currently effective, active sales-oriented resources.

Key Columns

  • RESOURCE_NAME — the display name of the resource (agent, employee, or party).
  • RESOURCE_ID — the unique identifier of the resource, useful for joins back to other resource-based views.
  • GROUP_NAME — the name of the resource group to which the membership belongs.
  • GRPS_GROUP_ID — the group identifier from the group membership join.
  • ROLE_NAME — the descriptive role name associated with the resource's group membership.
  • ROLE_CODE — the short, filterable code for the role; this is the column most often used in reporting predicates.
  • MANAGER_FLAG — indicates whether the resource acts as a manager for the associated role, supporting hierarchy-style reporting.

Common Use Cases and Queries

Typical uses include building a resource directory for telesales assignments, driving role-based routing logic, and populating LOVs or concurrent program outputs for CRM teams. Because the view already enforces active-role and sales-type filtering, it is well suited to operational rather than historical reporting.

A representative query listing all currently effective resources and their roles is:

  • SELECT RESOURCE_NAME, RESOURCE_ID, GROUP_NAME, ROLE_NAME, ROLE_CODE, MANAGER_FLAG FROM APPS.JTF_TTY_ALL_RESOURCES_V;

A targeted query filtering by a specific role code is:

  • SELECT RESOURCE_NAME, GROUP_NAME, ROLE_NAME FROM APPS.JTF_TTY_ALL_RESOURCES_V WHERE ROLE_CODE = 'TELESALES_AGENT';

Because the view exposes GRPS_GROUP_ID, it can also be joined back to other group-based CRM objects for extended reporting, while RESOURCE_ID supports joins to resource-specific tables. Consumers should note that historical rows are excluded by the SYSDATE-based predicates, so sourcing past-period data requires querying the underlying base views instead.