Search Results jtf_terr_qual




Overview
Explore in AI Chat

Overview

The JTF_TERR_QUAL view belongs to the JTF – CRM Foundation product family within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2. It exposes territory qualifier configuration data maintained by Oracle's Territory Management (also referenced under the ETRM framework for Enterprise Territory and Resource Management). In functional terms, territory qualifiers define the criteria — such as customer attributes, product lines, geography, or sales channel characteristics — that determine which customers, prospects, or transactions fall into a given territory. The view therefore plays a supporting role in the territory assignment engine used by modules including Trade Management, Sales, and Service.

Per the documented ETRM metadata, the view is described as "Same as JTF_TERR_QUAL_ALL table," indicating it is a reporting and integration layer that projects the multi-organization table content. Such views are commonly consumed by concurrent programs, territory assignment batch processes, and custom reporting or integration interfaces rather than as a directly maintained object. Notably, the ETRM 12.2.2 documentation states that this object is "Not implemented in this database" and lists no referenced base objects, meaning no physical instance or dependency graph is recorded for the captured environment; the definition is nonetheless preserved in the metadata for reference.

Underlying Base Objects

The documented ETRM metadata captures the view text as a direct, unfiltered selection from a single base object:

  • JTF_TERR_QUAL_ALL — the multi-organization (partitioned by ORG_ID) territory qualifier table from which every column of the view is sourced. The view performs no joins, filters, or transformations; it is a simple projection of the _ALL table.

Because the metadata records "Referenced base objects: none documented," the relationship to JTF_TERR_QUAL_ALL should be treated as documented only through the view text excerpt. In standard EBS deployments the _ALL table stores territory qualifier setup per operating unit, while a corresponding single-organization view (typically filtering on ORG_ID) may also exist for organization-specific access. Any reporting against JTF_TERR_QUAL therefore inherits the multi-org behavior of the underlying table.

Key Columns

The view exposes thirteen columns, each inherited verbatim from JTF_TERR_QUAL_ALL:

  • TERR_QUAL_ID — primary identifier for the territory qualifier record.
  • TERR_ID — foreign key to the territory definition (JTF_TERR) with which the qualifier is associated.
  • QUAL_USG_ID — identifies the qualifier usage, describing how the qualifier is applied to the territory.
  • USE_TO_NAME_FLAG — indicates whether the qualifier is used to name the territory derived from it.
  • GENERATE_FLAG — controls whether the qualifier participates in the territory generation/assignment process.
  • OVERLAP_ALLOWED_FLAG — determines whether territories sharing this qualifier may overlap during assignment.
  • QUALIFIER_MODE — specifies the qualifier evaluation mode (for example, usage context for the qualifier logic).
  • ORG_ID — the operating unit (multi-org) identifier governing the record's visibility and ownership.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN provide standard EBS who-column auditing.

Common Use Cases and Queries

Analysts and technical consultants query this view to audit territory qualifier configuration, troubleshoot assignment results, or feed territory data into custom integrations. Typical scenarios include reconciling qualifiers against territory definitions, verifying generation and overlap flags before running territory assignment, and extracting qualifier metadata for CRM or BI reporting.

Sample SQL:

  • SELECT tq.TERR_QUAL_ID, tq.TERR_ID, tq.QUAL_USG_ID, tq.GENERATE_FLAG, tq.OVERLAP_ALLOWED_FLAG, tq.ORG_ID FROM JTF_TERR_QUAL tq WHERE tq.TERR_ID = :p_terr_id;
  • SELECT tq.TERR_ID, COUNT(*) qualifier_count FROM JTF_TERR_QUAL tq WHERE tq.GENERATE_FLAG = 'Y' AND tq.ORG_ID = :p_org_id GROUP BY tq.TERR_ID ORDER BY qualifier_count DESC;
  • SELECT tq.TERR_QUAL_ID, tq.QUALIFIER_MODE, tq.LAST_UPDATE_DATE, tq.LAST_UPDATED_BY FROM JTF_TERR_QUAL tq WHERE tq.ORG_ID = :p_org_id AND tq.GENERATE_FLAG = 'Y';

Because the view is a direct projection of JTF_TERR_QUAL_ALL, all predicates on ORG_ID and qualifier flags apply with the same semantics as querying the base table directly. Consultants should confirm operating unit context via ORG_ID and note that in environments where the object is not implemented, queries will fail until the underlying territory qualifier tables are deployed.