Search Results jtf_terr_type_qual




Overview
Explore in AI Chat

Overview

The JTF_TERR_TYPE_QUAL view is a reporting and integration interface within the Oracle E-Business Suite CRM Foundation (JTF) module. Its purpose is to expose territory type qualifier configuration data — the rules that determine how territory types are qualified — to application code, reports, and external integrations. The view is a filtered projection over the underlying JTF_TERR_TYPE_QUAL_ALL table. As documented in the ETRM metadata, the description states it is "Same as JTF_TERR_TYPE_QUAL_ALL table," and its role is to present organization-scoped territory type qualifier records in a simplified, read-oriented form. In the Oracle EBS multi-org architecture, objects suffixed with _ALL store data across all operating units (filtered by ORG_ID), while the corresponding view without the suffix typically applies the session's organization context or presents the same columns for convenience. In this case, the view text performs a direct SELECT ... FROM JTF_TERR_TYPE_QUAL_ALL with no WHERE clause, meaning it exposes all rows and delegates any organization filtering to the caller. This distinguishes it from views that internally enforce a multi-org policy.

This view is relevant in Release 12.1.1 and 12.2.2. Note that the ETRM metadata records "Not implemented in this database" for implementation/DBA data, indicating the object may not exist in every environment or is seeded conditionally depending on the installed CRM/Territory Management configuration.

Underlying Base Objects

Per the view text, JTF_TERR_TYPE_QUAL is defined entirely over a single base object: JTF_TERR_TYPE_QUAL_ALL. No other base tables or joins are documented. The ETRM metadata lists referenced base objects as "none documented," but the view text explicitly names JTF_TERR_TYPE_QUAL_ALL as the source. The relationship is straightforward: the view is a column-for-column projection of the _ALL table, returning every row without additional filtering, joining, or aggregation. Consequently, any DML against these records should be directed at the base table (or the appropriate org-specific view), while this view is best treated as read-only for query and integration purposes.

Key Columns

The view exposes thirteen columns:

Common Use Cases and Queries

Typical uses include validating territory type qualifier configuration, supporting territory assignment diagnostics, and feeding integrations that need qualifier rules. A basic query retrieves active qualifiers for a given territory type:

  • SELECT TERR_TYPE_QUAL_ID, QUAL_USG_ID, TERR_TYPE_ID, IN_USE_FLAG, QUALIFIER_MODE, ORG_ID FROM JTF_TERR_TYPE_QUAL WHERE TERR_TYPE_ID = :p_terr_type_id AND IN_USE_FLAG = 'Y' ORDER BY TERR_TYPE_QUAL_ID;

Because the view does not enforce organization filtering, multi-org-aware queries should constrain ORG_ID explicitly, or use the org-striping mechanisms appropriate to the environment. Always confirm object existence in a given instance, since the metadata records it as not implemented in the documented database.