Search Results seeded_qual_name




Overview
Explore in AI Chat

Overview

APPS.JTF_TERR_INHERITED_QUAL_V is a read-only database view in the Oracle E-Business Suite Territory Management (ETRM) module. It presents territory qualifier assignments together with the name of the immediate parent territory of each listed territory. This makes it possible to report on qualifiers in the context of the territory hierarchy without issuing additional joins in the calling query. The view is part of the APPS schema and is available in both release 12.1.1 and 12.2.2; the documented metadata is drawn from the 12.2.2 ETRM repository.

The view exposes a single hierarchy level per row. The HIERARCHY_LEVEL column is defined as a literal NULL, so no depth indicator is computed. Consumers needing full ancestry must traverse JTF_TERR.PARENT_TERRITORY_ID recursively or use the territory hierarchy APIs.

Underlying Base Objects

The view is defined over four sources: the JTF_TERR synonym (aliased twice, as J1 and J2), the JTF_TERR_QUAL synonym (J3), and the JTF_SEEDED_QUAL_USGS_V view (J4). The documented dependency list also includes the FND_ACCESS_CONTROL_UTIL and FND_GLOBAL packages, which are referenced indirectly through the seeded-qualifier usage view to apply security and session context.

The join conditions are:

  • J1.PARENT_TERRITORY_ID = J2.TERR_ID — links each territory to its parent.
  • J3.TERR_ID = J1.TERR_ID — restricts qualifier rows to the subject territory.
  • J3.QUAL_USG_ID = J4.QUAL_USG_ID — resolves the qualifier usage to a seeded qualifier definition.
  • J4.QUAL_TYPE_ID <> -1001 — excludes the internal qualifier type identified by the value -1001.

Because the join to J2 uses an inner join via the WHERE clause, territories whose PARENT_TERRITORY_ID is NULL or points to a non-existent parent are not returned. This is a material behavioural characteristic of the view.

Key Columns

  • QUAL_USG_ID — identifier of the qualifier usage record.
  • SEEDED_QUAL_NAME — name of the seeded qualifier associated with the usage.
  • QUAL_TYPE_ID — type identifier of the qualifier; the value -1001 is filtered out.
  • QUALIFIER_TYPE_DESCRIPTION — descriptive text for the qualifier type.
  • TERR_ID — identifier of the subject territory (from J1, via JTF_TERR_QUAL).
  • TERR_NAME — name of the subject territory.
  • PARENT_TERR_NAME — name of the immediate parent territory, taken from the second JTF_TERR instance (J2). This is the column most commonly searched for when validating inheritance relationships.
  • HIERARCHY_LEVEL — always NULL in the view definition.

Common Use Cases and Queries

Typical uses include validating that qualifiers are inherited correctly from a parent territory, building territory qualification reports, and supporting data-migration or configuration audits after territory setup changes.

Retrieve all qualifiers for a named parent territory:

  • SELECT terr_name, parent_terr_name, seeded_qual_name, qualifier_type_description FROM apps.jtf_terr_inherited_qual_v WHERE parent_terr_name = 'NORTH AMERICA' ORDER BY terr_name;

List qualifiers for a specific child territory:

  • SELECT seeded_qual_name, qualifier_type_description, parent_terr_name FROM apps.jtf_terr_inherited_qual_v WHERE terr_id = :p_terr_id;

Identify child territories that have qualifier usages absent from their parent, which can indicate broken or manually overridden inheritance:

  • SELECT v.terr_name, v.seeded_qual_name FROM apps.jtf_terr_inherited_qual_v v WHERE NOT EXISTS (SELECT 1 FROM apps.jtf_terr_inherited_qual_v p WHERE p.terr_name = v.parent_terr_name AND p.seeded_qual_name = v.seeded_qual_name);

Queries should always filter on indexed identifiers such as TERR_ID or QUAL_USG_ID where possible, since the view's multi-way join and its dependency on the access-control utility package can make unfiltered scans expensive in large territory hierarchies.