Search Results role_type_code




Overview
Explore in AI Chat

Overview

APPS.JTF_TTY_ALL_RESOURCES_V is a reporting view in the Oracle E-Business Suite CRM resource management schema. It presents a denormalized, flattened picture of telesales resources and the sales groups and roles to which they belong, joining resource master data to group membership and role assignments in a single query block. The view is a "TTY" (telesales) construct: it exposes only resources that are assigned roles of type SALES, TELESALES or FIELDSALES, and filters each join by the effective date ranges on the underlying records so that only currently active assignments appear.

Because it resolves all of the date-effective logic internally, the view is suitable for direct consumption by reports, concurrent programs, BI Publisher data models and integration extracts that need an "as of today" roster of telesales resources together with their group and role context. It is not a base entity for transaction processing; it is a read-only convenience layer for inquiry and reporting.

Underlying Base Objects

The ETRM metadata documents four referenced base objects, all of which are themselves views (VL variants expose translated or validated columns):

The joins are driven from JTF_RS_GROUP_MBR_ROLE_VL to the resource, group and role views on RESOURCE_ID, GROUP_ID and ROLE_ID respectively. The view therefore depends on the resource-to-group membership model being populated; a resource with no group role membership will not appear.

Key Columns

  • RESOURCE_NAME, RESOURCE_ID — the display name and primary key of the telesales resource.
  • GROUP_NAME, GROUP_ID — the sales group to which the resource is assigned for the active membership period.
  • ROLE_NAME, ROLE_CODE — the role held by the resource within that group, restricted to roles of type SALES, TELESALES or FIELDSALES.
  • MANAGER_FLAG — the flag carried on the role record (JTF_RS_ROLES_VL.MANAGER_FLAG) indicating whether the role is a managerial one. This is the column users typically search for when they want to separate manager-level resources from individual contributors in a group.

All effective-date columns from the base objects are consumed in the WHERE clause and are not projected, so the result set is implicitly "active as of SYSDATE".

Common Use Cases and Queries

Typical usages include building telesales organization charts, identifying group managers, validating role assignments prior to territory or lead routing changes, and feeding downstream extracts with a current resource-and-role mapping.

To list all active telesales resources with their group and role:

  • SELECT resource_name, group_name, role_name, role_code, manager_flag FROM apps.jtf_tty_all_resources_v ORDER BY group_name, manager_flag DESC, resource_name;

To isolate managers within a group:

  • SELECT resource_name, resource_id, group_name, role_name FROM apps.jtf_tty_all_resources_v WHERE manager_flag = 'Y' AND group_name = :p_group_name;

To count resources by role type per group:

  • SELECT group_name, role_code, COUNT(DISTINCT resource_id) resource_count FROM apps.jtf_tty_all_resources_v GROUP BY group_name, role_code;

Because date filtering is embedded, no additional SYSDATE predicates are required. Users should note that the view reflects only role types SALES, TELESALES and FIELDSALES and only active roles (ACTIVE_FLAG = 'Y'), which should be taken into account when reconciling against base JTF_RS_ROLES_VL data.