Results for “qualifier_mode”

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

Overview

JTF_TERR_TYPE_QUAL_ALL is a CRM Foundation (JTF schema) table within the Oracle E-Business Suite 12.1.1 and 12.2.2 distributions. It stores the qualifiers used to define a territory type, forming part of the Oracle Territory Manager (formerly Enterprise Territory Manager, ETRM) data model. A territory type establishes a reusable classification — such as a geography-based sales territory or a product-based account territory — and the qualifier records held in this table map that type to the specific qualification usages available for building territory definitions.

Under a heuristic Data Vault classification mined from the foreign key structure, this object is best modeled as a link table. Its purpose is to resolve associations between territory types and qualification usages rather than to act as an independent business hub or as a descriptive satellite. The presence of a dedicated ALL suffix, ORG_ID, and SECURITY_GROUP_ID columns indicates the table is org-striped and multi-org enabled, consistent with the broader JTF territory schema conventions.

Key Information Stored

The table's documented physical schema comprises 15 columns. The surrogate primary key is TERR_TYPE_QUAL_ID, enforced by the JTF_TERR_TYPE_QUAL_ALL_PK constraint. A second unique index, JTF_TERR_TYPE_QUAL_U1, operates on the composite of TERR_TYPE_QUAL_ID and ORG_ID, representing the business-key candidate and reinforcing the multi-org access pattern.

• TERR_TYPE_QUAL_ID — the system-generated surrogate identifier for each territory-type qualifier row; the PK and the leading column of the unique index.
• TERR_TYPE_ID — foreign key to JTF_TERR_TYPES_ALL; identifies the territory type being qualified.
• QUAL_USG_ID — foreign key to JTF_QUAL_USGS_ALL; identifies the qualifier usage that may be applied to the territory type.
• QUALIFIER_MODE — controls how the qualifier usage participates in the territory type definition.
• IN_USE_FLAG — indicates whether the qualifier assignment is currently active and available for use.
• EXCLUSIVE_USE_FLAG — specifies whether the qualifier usage is restricted (exclusive) to this territory type.
• OVERLAP_ALLOWED_FLAG — determines whether qualifier values may overlap across territories of this type.
• ORG_ID — the operating unit (organization) that owns the row, enabling multi-org data partitioning.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting data security by group.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Applications Framework (OAF) and concurrent updates.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard WHO audit columns present on every EBS transactional table.

Common Use Cases and Queries

Typical use is reporting and diagnostics around territory setup: determining which qualifier usages are attached to a given territory type, and which flags govern exclusivity and overlap. A representative join query is:

SELECT tqt.TERR_TYPE_QUAL_ID, tqt.TERR_TYPE_ID, tqt.QUAL_USG_ID,
  tqt.QUALIFIER_MODE, tqt.IN_USE_FLAG, tqt.EXCLUSIVE_USE_FLAG, tqt.OVERLAP_ALLOWED_FLAG
FROM JTF.JTF_TERR_TYPE_QUAL_ALL tqt
WHERE tqt.ORG_ID = :p_org_id
  AND tqt.TERR_TYPE_ID = :p_terr_type_id;

Administrators frequently filter on IN_USE_FLAG = 'Y' to list active qualifier assignments, and on EXCLUSIVE_USE_FLAG or OVERLAP_ALLOWED_FLAG to audit territory design rules. Because of the ORG_ID and SECURITY_GROUP_ID columns, any custom query must apply Multi-Org views or explicit org predicates, and must respect security-group scoping, or it will return rows belonging to other operating units.

Related Objects

• JTF_TERR_TYPES_ALL — parent territory type definition; joined on TERR_TYPE_QUAL_ALL.TERR_TYPE_ID = TERR_TYPES_ALL.TERR_TYPE_ID.
• JTF_QUAL_USGS_ALL — qualifier usage catalog; joined on TERR_TYPE_QUAL_ALL.QUAL_USG_ID = QUAL_USGS_ALL.QUAL_USG_ID.
• FND_SECURITY_GROUPS — security group reference for the SECURITY_GROUP_ID column.
• JTF_TERR_TYPES_ALL_PK / JTF_TERR_TYPE_QUAL_ALL_PK — primary key constraints defining row identity.
• JTF_TERR_TYPE_QUAL_U1 — composite unique index supporting org-scoped lookups.
• Territory Manager concurrent programs and OAF territory setup pages — the application tier logic that reads and writes these qualifier assignments.