Search Results qualifier_type_name




Overview

The JTF_TERR_TRANSACTIONS_V view is a CRM Foundation (JTF) reporting object in the APPS schema that presents the transactions assigned to a territory. It is a denormalized, read-only projection whose purpose is to join the territory-qualifier assignment records with their underlying qualifier type usages and qualifier type definitions, so that a consumer can resolve not only which qualifier value drives a territory assignment but also the human-readable name and description of the qualifier type involved. It is owned by APPS and is documented as VALID in the E-Business Suite 12.1.1 and 12.2.2 releases.

Because the view is a pure SELECT join over three dictionary objects — JTF_TERR_QTYPE_USGS, JTF_QUAL_TYPE_USGS, and JTF_QUAL_TYPES — it carries no independent storage, no indexes of its own, and no triggers. Its role in EBS reporting and integration is to provide a stable, pre-joined interface that avoids repeated hand-coding of the qualifier resolution logic when building territory or assignment reports, extracts, and OBIEE/BIP data models.

Underlying Base Objects

The view is defined by the following FROM/WHERE clause, as documented:

  • JTF_TERR_QTYPE_USGS JTQU — the primary base object, holding each territory-to-qualifier-type-usage assignment. Joined on JTQU.QUAL_TYPE_USG_ID = JQTU.QUAL_TYPE_USG_ID.
  • JTF_QUAL_TYPE_USGS JQTU — the qualifier type usage definition, supplying SOURCE_ID. Joined on JQTU.QUAL_TYPE_ID = JQT.QUAL_TYPE_ID.
  • JTF_QUAL_TYPES JQT — the qualifier type lookup, supplying the type name and description.

The documented referenced base objects list JTF_QUAL_TYPES and JTF_QUAL_TYPE_USGS as views, JTF_TERR_QTYPE_USGS as a synonym, and FND_GLOBAL as a package (used for multi-org/session context). All joins are inner joins, so a territory qualifier usage row appears only when a matching qualifier type usage and qualifier type exist.

Key Columns

  • TERR_QTYPE_USG_ID — the primary identifier carried from JTF_TERR_QTYPE_USGS, uniquely identifying the territory qualifier-type usage assignment. This is the column most directly associated with the terr_qtype_usg_id search term.
  • ROW_ID — the ROWID of the underlying JTF_TERR_QTYPE_USGS row, useful for direct row addressing.
  • TERR_ID — the territory to which the qualifier usage is assigned.
  • QUAL_TYPE_USG_ID and QUAL_TYPE_ID — the qualifier type usage and the qualifier type definition behind it.
  • SOURCE_ID — sourced from JTF_QUAL_TYPE_USGS, identifying the qualification source record.
  • QUALIFIER_TYPE_NAME and QUALIFIER_TYPE_DESCRIPTION — descriptive attributes from JTF_QUAL_TYPES.
  • ORG_ID — the operating unit, enabling multi-org filtering (typically via FND_GLOBAL.ORG_ID).
  • Audit columnsCREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN from the base assignment row.

Common Use Cases and Queries

Typical scenarios include listing all qualifiers driving a given territory, tracing a specific TERR_QTYPE_USG_ID back to its qualifier type and source, and joining to territory or customer assignment facts to explain why an entity was assigned. A representative query is:

  • SELECT TERR_QTYPE_USG_ID, TERR_ID, QUAL_TYPE_ID, QUALIFIER_TYPE_NAME, SOURCE_ID, ORG_ID FROM APPS.JTF_TERR_TRANSACTIONS_V WHERE TERR_ID = :terr_id;
  • Filtering by operating unit using WHERE ORG_ID = FND_GLOBAL.ORG_ID for multi-org-safe reports.
  • Resolving a single record: WHERE TERR_QTYPE_USG_ID = :terr_qtype_usg_id.

Because all joins are inner joins, rows lacking a valid qualifier type usage or qualifier type definition are excluded; reports requiring orphan assignments should query JTF_TERR_QTYPE_USGS directly.