Search Results jtf_terr_qualifiers_v




Overview
Explore in AI Chat

Overview

JTF_TERR_QUALIFIERS_V is a read-only view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the JTF - CRM Foundation product family and is part of the Enterprise Territory Management (ETRM) data model. The view exposes the qualifiers that are used to define a territory, combining transaction-level qualifier assignment data with the underlying qualifier usage, seeded qualifier, qualifier type usage, and qualifier type definitions. Because it presents a denormalized, business-friendly projection across several ETRM configuration tables, it serves as a convenient reporting and integration surface for administrators and developers who need to understand how territories are qualified without joining the base tables manually.

Underlying Base Objects

The documented base objects referenced by this view are FND_GLOBAL (PACKAGE), FND_LOOKUPS (VIEW), JTF_QUAL_TYPES (VIEW), JTF_QUAL_TYPE_USGS (VIEW), JTF_QUAL_USGS (SYNONYM), JTF_SEEDED_QUAL (SYNONYM), and JTF_TERR_QUAL (SYNONYM). The principal transaction table is JTF_TERR_QUAL, aliased JTQ, which holds one row per territory qualifier assignment. It is joined to JTF_QUAL_USGS (JQU) on QUAL_USG_ID, to JTF_SEEDED_QUAL (JSQ) on SEEDED_QUAL_ID, and to JTF_QUAL_TYPE_USGS (JQTU) on QUAL_TYPE_USG_ID. JQTU is then joined to JTF_QUAL_TYPES (JQT) on QUAL_TYPE_ID. The view definition consists of a UNION ALL: the first branch selects rows where QUALIFIER_MODE IS NULL, and the second branch handles rows with a populated qualifier mode. FND_GLOBAL and FND_LOOKUPS support the multi-org (ORG_ID) and lookup-driven behavior of the underlying ETRM configuration rather than being explicit join targets in the excerpt.

Key Columns

Common Use Cases and Queries

Typical uses include auditing which qualifiers are attached to a given territory, extracting qualifier configuration for migration or comparison between environments, and feeding territory qualification data into custom reports or integrations. The following examples illustrate common access patterns.

  • Retrieve all qualifiers for a specific territory: SELECT terr_qual_id, qualifier_name, qualifier_type_name, qualifier_mode FROM jtf_terr_qualifiers_v WHERE terr_id = :p_terr_id;
  • List qualifiers by operating unit: SELECT terr_id, qualifier_name, org_id FROM jtf_terr_qualifiers_v WHERE org_id = :p_org_id;
  • Identify qualifiers that participate in generation: SELECT terr_id, qualifier_name FROM jtf_terr_qualifiers_v WHERE generate_flag = 'Y';

Because the view is a UNION ALL with ROWID-based columns, the same logical qualifier may appear via both branches depending on the QUALIFIER_MODE condition; queries intended to avoid duplicates should account for this behavior or filter on QUALIFIER_MODE explicitly.