Search Results jtf_qual_types_all




Overview
Explore in AI Chat

Overview

The JTF_QUAL_TYPES_ALL table is a core data repository within the Oracle E-Business Suite CRM Foundation (JTF) module. As defined in the ETRM documentation, its primary role is to store the different transaction types that are processed by territories. This table is fundamental to the territory management and resource assignment engine, enabling the system to categorize and qualify various business transactions—such as leads, opportunities, service requests, or orders—for assignment to specific sales or service territories. Its "ALL" suffix indicates it is a multi-organization table, meaning it can store data partitioned by operating unit (ORG_ID), a critical design for multi-org enabled instances in both EBS 12.1.1 and 12.2.2.

Key Information Stored

While the provided metadata does not list all columns, the documented primary key and foreign key relationships reveal the essential structure. The QUAL_TYPE_ID column is the unique primary identifier for each transaction type record. Based on its described purpose, typical columns would include a code (QUAL_TYPE_CODE) and name (NAME) for the transaction type, a description (DESCRIPTION), and an active flag (ACTIVE_FLAG or ENABLED_FLAG) to control usability. The ORG_ID column is implicitly present to support the multi-org architecture. The table acts as a reference lookup, defining the universe of transaction types that the territory qualification engine can evaluate against territory rules.

Common Use Cases and Queries

This table is primarily accessed for setup, maintenance, and reporting on territory-qualified transaction types. Administrators use it to define new transaction types or disable obsolete ones. Common reporting queries involve listing all active transaction types available for territory assignment or verifying the setup for a specific module. A typical SQL pattern would join this table to its usage table to see where a type is applied.

  • Listing active qualification types for a specific operating unit: SELECT qual_type_id, name FROM jtf_qual_types_all WHERE org_id = :org_id AND enabled_flag = 'Y' ORDER BY name;
  • Finding qualification types used in a specific territory rule setup (joining to JTF_QUAL_TYPE_USGS_ALL): SELECT t.name FROM jtf_qual_types_all t, jtf_qual_type_usgs_all u WHERE t.qual_type_id = u.qual_type_id AND u.territory_id = :territory_id;

Related Objects

The table has a direct and documented foreign key relationship, as per the provided metadata. The JTF_QUAL_TYPE_USGS_ALL table references JTF_QUAL_TYPES_ALL via the QUAL_TYPE_ID column. This relationship defines how a specific qualification type (from JTF_QUAL_TYPES_ALL) is used (USGS) within territory definitions or rules. This is the primary join for operational queries. The table is also likely referenced by various territory manager APIs and seeded data scripts within the JTF module. Understanding this relationship is key to tracing how a transaction type defined in JTF_QUAL_TYPES_ALL is ultimately applied to filter and assign transactions within the territory management system.