Results for “jtf_terr_type_qual_v”

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

Overview

The JTF_TERR_TYPE_QUAL_V view is a reporting and integration object within the JTF - CRM Foundation product of Oracle E-Business Suite 12.1.1 and 12.2.2. It resides in the APPS schema and is classified as VALID. The view presents the qualifier and qualifier type usage configuration associated with CRM territory types, exposing both the territory type qualifier assignments and the human-readable descriptions of the seeded qualifier types and qualifier names that those assignments reference.

Territory types in Oracle CRM define the structural template for territories — specifying which qualifiers (such as industry, geography, or account attributes) may or must be used when territories of that type are defined. Administrators configuring Territory Manager require visibility into these relationships, and this view consolidates the transactional qualifier configuration rows from the underlying territory type qualifier table with the seeded qualifier usage metadata. Because it joins the denormalized descriptive columns (qualifier type name, description, and seeded qualifier name) directly onto the assignment rows, it removes the need for consumers to perform their own lookup joins, which is the principal reason the view exists as a published APPS object rather than a private implementation detail.

Underlying Base Objects

The documented view text is defined over two primary objects:

• JTF_TERR_TYPE_QUAL (exposed in the data dictionary as a SYNONYM, aliased JTTQ in the view definition) — the base table holding one row per territory type qualifier assignment.
• JTF_SEEDED_QUAL_USGS_V (VIEW, aliased JSQU) — the seeded qualifier usage view supplying the qualifier type name, qualifier type description, and seeded qualifier name.

The two are joined on JTTQ.QUAL_USG_ID = JSQU.QUAL_USG_ID, so every row in the view represents a territory type qualifier that successfully matches a seeded qualifier usage definition. The ETRM metadata additionally lists FND_ACCESS_CONTROL_UTIL and FND_GLOBAL as referenced base objects. These packages are the standard multi-org and access-control mechanisms invoked by Oracle views to resolve the current ORG_ID and operating unit context, consistent with the presence of the ORG_ID column in the output.

Key Columns

• TERR_TYPE_QUAL_ID — Primary identifier for the territory type qualifier assignment row.
• QUALIFIER_TYPE — The qualifier type name derived from the seeded qualifier usage; this is the object a user searches for under the term "qualifier_type."
• QUALIFIER_TYPE_DESCRIPTION — Descriptive text explaining the qualifier type's purpose.
• QUAL_USG_ID — Foreign key to the seeded qualifier usage definition; the join key between the two base objects.
• QUALIFIER_NAME — The seeded qualifier name, i.e., the specific qualifier presented to users.
• TERR_TYPE_ID — Identifies the territory type to which the qualifier is attached.
• EXCLUSIVE_USE_FLAG, OVERLAP_ALLOWED_FLAG, IN_USE_FLAG — Control flags governing whether the qualifier is exclusive, whether overlap is permitted, and whether the configuration is currently active.
• QUALIFIER_MODE — Indicates the mode in which the qualifier operates for the territory type.
• ORG_ID — Operating unit (multi-org) context for the row.
• Creation/update audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical uses include diagnosing why a qualifier is unavailable when building a territory of a given type, auditing active qualifier usage across territory types within an operating unit, and feeding territory configuration data into downstream integrations or custom CRM reports.

Listing all qualifiers for a given territory type:

SELECT qualifier_type, qualifier_type_description, qualifier_name,
       exclusive_use_flag, overlap_allowed_flag, in_use_flag
FROM   apps.jtf_terr_type_qual_v
WHERE  terr_type_id = :p_terr_type_id
AND    org_id = :p_org_id;

Identifying seeded usage for a specific qualifier type (the "qualifier_type" search):

SELECT terr_type_id, qual_usg_id, qualifier_name, qualifier_mode
FROM   apps.jtf_terr_type_qual_v
WHERE  qualifier_type = :p_qualifier_type
AND    in_use_flag = 'Y';

Auditing all active qualifier assignments per operating unit:

SELECT org_id, qualifier_type, COUNT(*) assignments
FROM   apps.jtf_terr_type_qual_v
WHERE  in_use_flag = 'Y'
GROUP  BY org_id, qualifier_type
ORDER  BY org_id, qualifier_type;

Because the view already joins the seeded qualifier usage metadata, queries against it should be preferred over direct joins between JTF_TERR_TYPE_QUAL and JTF_SEEDED_QUAL_USGS_V.