Results for “resource_type_name”

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

Overview

JTF_TERR_QLFY_RSC_DST_V is a CRM Foundation (JTF) database view owned by the APPS schema in Oracle EBS 12.1.1 and 12.2.2. It consolidates all active resources, groups, and teams into a single denormalized result set that is used by the territory qualification and resource distribution engines. The view resolves the various resource categories maintained across separate resource, group, and team entities into a uniform row format, allowing downstream territory assignment logic to treat every qualifying entity—whether an individual employee, a partner, a supplier contact, a party, a to-be-hired record, a resource group, or a resource team—as a single "resource" with a consistent identifier and type.

Because it is a view and not a table, JTF_TERR_QLFY_RSC_DST_V holds no data of its own. Its contents are generated at query time from its underlying base views, meaning results always reflect the current active status of the source records. This makes it particularly valuable in reporting and integration scenarios where an up-to-date, unified view of assignable CRM resources is required without duplicating data in a staging table.

Underlying Base Objects

The view is defined over three documented base objects:

• JTF_RS_RESOURCE_EXTNS_VL — the resource extension view supplying individual resources and their category (EMPLOYEE, PARTNER, SUPPLIER_CONTACT, PARTY, OTHER, TBH). The join condition filters rows where the resource is currently active.
• JTF_RS_GROUPS_VL — the resource groups view, contributing group records identified by GROUP_ID and GROUP_NAME, filtered by their active date range.
• JTF_RS_TEAMS_VL — the resource teams view, contributing team records identified by TEAM_ID and TEAM_NAME, filtered by their active date range.

The three sources are combined with UNION ALL, so each resource, group, and team appears as a distinct row. The view's structure therefore depends entirely on the availability and validity of these three underlying views, all of which reside in the APPS schema.

Key Columns

• RESOURCE_ID — the unique identifier of the resource, group, or team, sourced from RESOURCE_ID, GROUP_ID, or TEAM_ID respectively.
• RESOURCE_TYPE — a coded indicator derived via DECODE from the resource category, returning values such as RS_EMPLOYEE, RS_PARTNER, RS_SUPPLIER_CONTACT, RS_PARTY, RS_OTHER, RS_TBH, RS_GROUP, or RS_TEAM.
• RESOURCE_TYPE_NAME — the descriptive, user-facing label for the resource type, such as "EMPLOYEE RESOURCE", "PARTNER RESOURCE", "GROUP RESOURCE", or "TEAM RESOURCE". This is the column most commonly referenced by report filters and user searches.
• RESOURCE_NAME — the display name of the resource, group, or team.
• EMAIL, START_DATE_ACTIVE, END_DATE_ACTIVE, PHONE — additional resource attributes exposed for selection and reporting.

Common Use Cases and Queries

Typical use cases include territory qualification lookups, resource distribution reporting, and integration feeds that require a consolidated active-resource list. A sample query returning all resources of a given type is:

• SELECT resource_id, resource_type, resource_type_name, resource_name FROM jtf_terr_qlfy_rsc_dst_v WHERE resource_type_name = 'EMPLOYEE RESOURCE';
• SELECT resource_type_name, COUNT(*) FROM jtf_terr_qlfy_rsc_dst_v GROUP BY resource_type_name;

Because the view applies active-date filtering internally, queries need not re-apply date logic for the group and team branches. Reporting queries should account for the uniform column set, noting that EMAIL, START_DATE_ACTIVE, END_DATE_ACTIVE, and PHONE are populated only for the individual resource branch.