Search Results related_id1




Overview

JTF_QUAL_TYPES_ALL is a CRM Foundation (JTF) reference table that stores the different transaction types processed by territories within Oracle E-Business Suite 12.1.1 and 12.2.2. It acts as the master definition list of qualifier types — the "what" that territory assignment engines evaluate when matching transactions, customers, or other entities to territory rules. Each row defines a qualifier type together with the SQL fragments used to build its qualifying view, allowing the Territory Manager and related territory-assignment processes to treat different business objects (for example, customers, opportunities, or orders) uniformly.

From a modeling perspective, the metadata's heuristic Data Vault classification is hub-leaning. The table functions as the central anchor around which several dependent tables revolve, with QUAL_TYPE_ID serving as the stable business key. This classification should be treated as a suggestion rather than a design mandate; the native EBS implementation is a traditional relational reference table with multi-org and editioning considerations.

Key Information Stored

The table contains 21 documented columns. The most significant are:

  • QUAL_TYPE_ID — The surrogate primary key (JTF_QUAL_TYPES_ALL_PK). It uniquely identifies each qualifier type and is the column referenced by all dependent tables.
  • NAME and DESCRIPTION — The user-facing identifier and explanation of the qualifier type, typically shown when configuring territory rules.
  • SELECT_CLAUSE and WHERE_CLAUSE — The SQL fragments used to construct the qualifying query for the territory engine.
  • VIEW_NAME and VIEW_DDL_FILENAME — References to the database view that materializes the qualifier logic and the associated DDL file.
  • RELATED_ID1 through RELATED_ID5 — Generic flex columns used to carry additional context for the qualifier type, such as linked lookup codes or external identifiers.
  • ORG_ID — Multi-org operating unit identifier, indicating that qualifier definitions can be partitioned by organization.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling which security group the qualifier type belongs to.
  • OBJECT_VERSION_NUMBER — Optimistic concurrency control column used by the Oracle Application Framework.
  • ZD_EDITION_NAME — Editioning column supporting the EBS 12.2 online patching / edition-based redefinition architecture.
  • Standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.

The unique index JTF_QUAL_TYPES_U1 (QUAL_TYPE_ID, ORG_ID, ZD_EDITION_NAME) reflects the multi-org and editioned nature of the table and is the closest documented business-key candidate; QUAL_TYPE_ID alone remains the surrogate handle.

Common Use Cases and Queries

Typical scenarios include listing available territory qualifier types for a given operating unit, debugging the SQL used to resolve a specific qualifier, and tracing which usage definitions depend on a qualifier.

A common lookup pattern:

  • SELECT qual_type_id, name, description FROM jtf_qual_types_all WHERE org_id = :org_id ORDER BY name;
  • To inspect the generated qualifier logic: SELECT view_name, select_clause, where_clause FROM jtf_qual_types_all WHERE qual_type_id = :id;
  • To find usages: join to JTF_QUAL_TYPE_USGS_ALL on qual_type_id.

Reporting often requires joining this table to the usage definitions and territory results tables to determine which qualifier types drive assignment outcomes, or joining to FND_SECURITY_GROUPS via SECURITY_GROUP_ID to confirm security partitioning.

Related Objects

  • JTF_QUAL_TYPE_USGS_ALL — References JTF_QUAL_TYPES_ALL.QUAL_TYPE_ID; defines each usage of a qualifier type.
  • JTF_TERR_DENORM_RULES_ALL — References QUAL_TYPE_ID; holds denormalized territory rule rows.
  • JTF_TERR_RESULTS — References QUAL_TYPE_ID; stores territory assignment results per qualifier.
  • JTF_TERR_RESULTS_GT_MT — Global temporary / multi-table variant referencing QUAL_TYPE_ID.
  • JTY_WEBADI_QUAL_TYPE_HEADER — WebADI header table referencing QUAL_TYPE_ID for territory setup imports.
  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID for security group assignment.

These relationships establish JTF_QUAL_TYPES_ALL as the central definition point for territory qualifier behavior across the CRM Foundation territory engine.