Search Results jtf_qual_types




Overview
Explore in AI Chat

Overview

JTF_QUAL_TYPES is a VALID Oracle E-Business Suite view owned by the APPS schema and registered under the JTF – CRM Foundation product family. In both release 12.1.1 and 12.2.2, the object is documented as functionally identical to the JTF_QUAL_TYPES_ALL table, exposing qualification type definitions used by CRM applications for territory qualification and related rule-driven selection logic. Rather than storing its own data, the view presents a filtered, translated projection of the underlying qualification type records, resolving the descriptive meaning of each type through a join to the FND_LOOKUPS lookup view. This design places JTF_QUAL_TYPES at the intersection of CRM Foundation setup data and standard Oracle lookup configuration, making it a convenient read-only access point for reporting, data extraction, and integration interfaces that need qualification type metadata without navigating the multi-organization base table directly.

Underlying Base Objects

The view is defined over two principal sources. The first is JTF_QUAL_TYPES_ALL, referenced in ETRM as a synonym within the APPS schema, which holds the qualification type definitions including the selection and restriction criteria fragments and the operating unit context carried in ORG_ID. The second is FND_LOOKUPS, the standard lookup view, which supplies the human-readable meaning for each type. The join condition links JTF_QUAL_TYPES_ALL.NAME to FND_LOOKUPS.LOOKUP_CODE and constrains FND_LOOKUPS.LOOKUP_TYPE to the value 'JTF_TERR_QUAL_TYPES', ensuring only territory qualification type codes participate in the result set. Because the view text references organization-scoped data, its effective behavior is influenced by the session's organization context, and the documented metadata additionally references FND_GLOBAL (PACKAGE), consistent with the view's dependency on session-level environment functions.

Key Columns

The view exposes the standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) alongside functional attributes. QUAL_TYPE_ID is the primary identifier for each qualification type. NAME carries the lookup code, while DESCRIPTION is derived from the lookup MEANING rather than from the table's own column, which is the principal behavioral difference introduced by the view. SELECT_CLAUSE and WHERE_CLAUSE store the SQL fragments that define how qualifying records are selected and restricted. VIEW_NAME and VIEW_DDL_FILENAME identify the database view and DDL artifact associated with the qualification type. RELATED_ID1 through RELATED_ID5 provide five generic reference slots used for application-specific linkage. ORG_ID identifies the operating unit to which the definition belongs.

Common Use Cases and Queries

Typical usage includes validating that a qualification type is properly registered as a JTF_TERR_QUAL_TYPES lookup, auditing the selection and restriction logic attached to each type, and feeding qualification metadata into custom reporting or integration extracts. A basic listing query is:

  • SELECT qual_type_id, name, description, view_name FROM jtf_qual_types ORDER BY name;
  • SELECT qual_type_id, select_clause, where_clause FROM jtf_qual_types WHERE org_id = :p_org_id;
  • SELECT q.name, q.description, q.view_ddl_filename FROM jtf_qual_types q WHERE q.name = :p_lookup_code;

Because DESCRIPTION originates from FND_LOOKUPS, any type whose NAME lacks a corresponding lookup entry under LOOKUP_TYPE 'JTF_TERR_QUAL_TYPES' will not appear in the view. Integrations should therefore treat JTF_QUAL_TYPES as the reporting-friendly interface and JTF_QUAL_TYPES_ALL as the authoritative source when unregistered or internally generated type codes must be retrieved.