Results for “jtf_type_qtype_usgs_v”

20 results




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

Overview

The APPS.JTF_TYPE_QTYPE_USGS_V view is a CRM Foundation (JTF) reporting object in Oracle E-Business Suite 12.1.1 and 12.2.2 that exposes the relationship between territory types and the qualifier types assigned to them. As documented in the ETRM metadata, its stated purpose is to "show a Territory Type's qualifier type usage description." In practice, the view denormalizes the many-to-many using structures that link territory types, qualifier usages, and qualifier definitions, presenting a single flattened row per territory-type/qualifier-type usage combination.

Within the Oracle Territory Manager (part of CRM Foundation and shared by modules such as Oracle Sales, Service, and Trade Management), qualifier types define the attributes — such as customer, product, geography, or industry — against which territory rules are evaluated. This view therefore serves as a metadata dictionary for administrators and developers who need to understand which qualifiers are enabled for a given territory type, and how each qualifier is described. Because it is owned by APPS and marked VALID, it is safe to reference in custom reports, concurrent program queries, and integration extracts, subject to standard EBS security and ORG_ID considerations.

Underlying Base Objects

The view text joins three documented objects: JTF_TYPE_QTYPE_USGS, JTF_QUAL_TYPE_USGS, and JTF_QUAL_TYPES. In the 12.2.2 documented metadata, JTF_TYPE_QTYPE_USGS is exposed as a SYNONYM, while JTF_QUAL_TYPE_USGS and JTF_QUAL_TYPES are exposed as VIEWs; FND_GLOBAL (PACKAGE) is also referenced in the surrounding metadata, typically for ORG_ID resolution via FND_GLOBAL.ORG_ID in multi-org contexts.

The join path is:

Thus JTF_TYPE_QTYPE_USGS anchors the territory-type side, JTF_QUAL_TYPE_USGS bridges usage assignments, and JTF_QUAL_TYPES supplies the qualifier name and description. ORG_ID is carried through for operating-unit filtering.

Key Columns

Common Use Cases and Queries

Typical scenarios include auditing which qualifier types are enabled for a territory type, generating configuration documentation, and validating territory setup before rule definition. A representative query filters by territory type and operating unit:

  • SELECT qualifier_type, qual_type_description FROM jtf_type_qtype_usgs_v WHERE terr_type_id = :p_terr_type_id AND org_id = :p_org_id;
  • SELECT DISTINCT qualifier_type FROM jtf_type_qtype_usgs_v ORDER BY qualifier_type;
  • SELECT terr_type_id, qualifier_type, last_update_date FROM jtf_type_qtype_usgs_v ORDER BY terr_type_id, qualifier_type;

Because the view exposes only descriptive and key columns, it is best used as a lookup/dictionary source rather than for transactional reporting. For row-level territory rule data, join QUAL_TYPE_ID to the underlying qualifier rule tables.